G6 / Missing reading after missed reading

[robertrub]

Hi

Using last dev but had this kind of problem before too. I think it is an xDrip bug or might be a G6 transmitter bug too.

Was away from phone 9 minutes and missed a BG. At 10 min, last BG arrived but not the one before last. Attached the screenshots after 10 min.

And the screenshots at 15 min. The missing BG hole is filled.

Don't know if it's relevant but I'm using an Anubis transmitter.

[Navid200]

There are too many screenshots here many of which are not from xDrip. That does not help if you don't explain what they are.
There are screenshots from xDrip that show a missing reading. There are other screenshots from xDrip that show no missed reading.
How is one supposed to know what you are showing?

[robertrub]

I'll try to explain in another way.

Reading n° 1 has arrived to xDrip.

xDrip waits for next reading (number 2) but the transmitter doesn't answer, is not available.

xDrip waits for reading n°3 but, as it knows that n°2 was missing, it can send the command send past BG and send new BG at the same time.

[Navid200]

For an experiment, I put my phone in the microwave to intentionally cause missed readings. After, I made a screen recording to show exactly what happens.

screen-20250125-121735.mp4

After xDrip gets the new reading, it requests a backfill right away and the backfill appears right away. Only for a moment, there is only the new reading visible.

Do you see the same thing in xDrip or do you see something different?
If you see the same behavior in xDrip, we can then talk about what happens in AAPS. But, if you do not see this in xDrip, please let me know.

[Navid200]

It seems the period during which the old readings are missing after the new reading has arrived lasts about 2 seconds.

[robertrub]

Tnx for the video. It helped. We're getting near the problem ;) I waited on xDrip screen and it was similar to yours.

The reaction is different on AAPS screen. Last BG is shown immediately but the one before last is shown 5 min later.

So the problem is NOT with xDrip receiving the BGs.

Next step : how does xDrip propagate these BGs received in "inversed" order ? It received BG n°3 and then received BG n°2 seconds later. Does it send BG 3 and then BG 2 seconds later ?

I have to see how xDrips sends and how AAPS acts on the way xDrip sends BGs to find how the BGs can arrive to AAPS as they arrive to xDrip.

[robertrub]

Very strange. Tested again this morning and all is working... 🤔

Filmed the xDrip UI. 2 lost BGs. At +20 min, the last BG arrived and 2 sec later as it should.

Screen_Recording_20250126_120925_xDrip+.mp4

I looked at the xDrip tab in AAPS and all the readings were there, no holes...

I suppose that you can close this discussion. No idea what went wrong and why it's working again.