Replies: 5 comments 11 replies
-
btw, I believe for the floating point data 35 is a better multiplier than 34 - using 35 the results for the same resistances are a closer match to the values I see on a 80xxxx transmitter (which uses 34.) |
Beta Was this translation helpful? Give feedback.
-
What would be the reason for using raw values with a G6? |
Beta Was this translation helpful? Give feedback.
-
this is uploaded by logger/xdrip-js, not xdrip+ but it shows what you are asking. raw is always sent by the tx, even for temporary session errors and sensor stopped/warmup... |
Beta Was this translation helpful? Give feedback.
-
this discussion can be closed, @jamorham has made the change in c5eb162 |
Beta Was this translation helpful? Give feedback.
-
I have an anubis transmitter and cannot read raw data with xdrip+, instead I get "Raw: -0.13" in the bg data table.
I looked at the sensor rx messages using xdrip-js and it looks to me like my transmitter uses floating point for the unfiltered, filtered fields. here is my decoding of the messages I looked at when given controlled input from resistors:
it looks like xdrip+ is using an integer calculation to come up with its unfiltered result (SensorRxMessage.java only reads in integer values, and they are used in https://github.com/NightscoutFoundation/xDrip/blob/master/app/src/main/java/com/eveningoutpost/dexdrip/G5Model/RawScaling.java) - from my calculations this will not give the same results, e.g., for 400mg/dl the unfiltered will read approx 230mg/dl - this would be fine for calibration if the result was linear but since the exponent is not decoded the integer calculation currently in xdrip+ will not be linear.
i still don't understand why my raw was -0.13, but i believe there is at least one xdrip+ issue here.
my anubis transmitter is at firmware version 2.27.2.103, and my xdrip+ is at version 2022.04.06 (variant 3).
Beta Was this translation helpful? Give feedback.
All reactions