Replies: 1 comment
-
Thank you @3djc for fulfilling that TODO I forgot... I committed your #10 but you have to consider that there are many, many details which we have to take into account to determine correctly the trend delta which I am computing with a simple subtraction now. The Libre 2, for example, sends every minute not the last seven trend values but the ones at the indexes [0, 2, 4, 6, 7, 12, 15]. When you scan a Libre 2 via NFC a 0 raw value is sent and you have to reinterpret the temperature field as an error code, typically Line 78 in bc03894 DiaBLE/DiaBLE/MainDelegate.swift Line 310 in 0eee45f The Libre 3 sends every minute two packets of 15 + 20 = 35 bytes. The payload is made of 29 bytes and relates only to just a single measurement: I am outlining the subfields in Lines 147 to 160 in 0eee45f There is a clear distinction between the 1-minute “clinical” data and the 5-minute “historical” values and the sensor itself reports the rate of change. Trident continuously amends the glucose curve and there is a latency of exactly 17 minutes before the historical values (the ones with a Line 869 in bc03894 From LibreLinkUp you can get the trend arrow already computed correctly, anyway… ;-) |
Beta Was this translation helpful? Give feedback.
-
Libre 1min trend are really quite useless, DiaBLE provides 5 min trends that are much more relevant. Suggest using those on calendar notification for watch use.
When you start the app, it needs time to build up the stats
Then when ready you have the trend
Beta Was this translation helpful? Give feedback.
All reactions