Hello, everyone. My experiences are similar to @
sgm14 when my glucose level is below 120.
But when it's above 140-150, it's a big problem for me. If you eat a lot of carbohydrates at once, it will go down, but it may take an hour or much longer (2, 3, or even 4 hours). But if I eat only a few (for example, if my breakfast is 6 carbohydrates and my glucose is at 160), my glucose will never reach an optimal level for eating. Because I use the pump in Guardian mode, and as soon as it sees an insulin bolus, it stops injecting basal insulin, and of course, the amount for the bolus disappears and is used as basal insulin. So what do I do? I wait to see if it goes down somehow. But when it's at 160, it stops injecting basal for a long time, and then there's no insulin left from the bolus I injected to eat.
Also, in Guardian mode, when I am administering insulin for a meal, if I exceed 10-12 carbohydrates, it starts reducing the dose. Sometimes it gives me less than 50% of the insulin planned for that amount. After the meal, it takes a lot of time trying to bring the glucose down to a lower level (because, in my opinion, it made more reductions than necessary in the amount of insulin to be injected for that particular meal) and finally (7 hours later) it ends up asking me for blood. But it doesn't inject more insulin neither. Maybe It is not learning.
Today, I have hardly eaten anything, and my glucose has remained around 160 for many hours. And after 7 or 8 hours, it asks me for a blood glucose test. In non-Guard mode, I would have lowered it, but my endocrinologist have been told to let it learn, although I don't know if what I am doing is teaching it bad habits.
Rather, it seems that it does not believe the values it obtains from the sensor. And today, the sensor values and blood glucose values differed by only 1. That's what I call a good sensor.
Best regards to all of you.