G6 sensor errors #674
Comments
|
The g6 will report that until it starts getting acceptable values again. Turn on the xdrip algo fallback option if u need to see values. |
|
Worked for a bit, bit keeps automatically reverting to "G6 Native Mode"
then the box is no longer checked.
…On Mon, Nov 5, 2018, 7:23 PM gitanO0 ***@***.*** wrote:
The will report that until it starts getting acceptable values again. Turn
on the xdrip algo fallback option if u need to see values.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#674 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AdZL3ive1GXxVyn6mm2skgYz41vzU5VXks5usNaPgaJpZM4YPhEV>
.
|
|
Which xDrip version are you using? |
|
I am having this issue too.. Using latest build (2 nov) |
|
I get this all the time.. thank god for the xdrip algo fallback option. Nothing u can do about that g6 cutting the feed and sending that sensor errors message. That seems to be a "feature" of the g6. |
|
Oh you are referring to the reverting to native mode thing? Yeah that's odd. Happens to m too. |
|
Note.. After toggling Bluetooth off and back in, restarting collector and restarting my phone a few times (to not success) I checked the 'fallback to xdrip' option and after a few minutes it kicked back in.. Went back into settings and it had unchecked (I imagine this is to do with being in native mode) |
|
I'm using version 1809080944 currently with a new sensor; I was using the
nightly build (11-02 I believe) when I had the issues.
Everything was fine for the first few days, then would start getting sensor
errors. Fallback worked for a day, then total sensor failure after 7 days.
…On Tue, Nov 13, 2018, 2:32 PM Jaykeydj ***@***.*** wrote:
Note.. After toggling Bluetooth off and back in, restarting collector and
restarting my phone a few times (to not success) I checked the 'fallback to
xdrip' option and after a few minutes it kicked back in..
Went back into settings and it had unchecked (I imagine this is to do with
being in native mode)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#674 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AdZL3oYl1K7UyF7xqn0LOjRwPI-mq2dLks5uux42gaJpZM4YPhEV>
.
|
|
We're you using native mode at the time? |
|
Might I add that after a night of no readings.. I entered enigerring mode and checked fallback to xdrip.. I have had readings all day since this step.. But I am still running in native mode.. Error message 'sesnosr failed in the collector status bar at the bottom. Of. My screen... Don't want to switch sensor as I would like to try fault find this issue and I am down to my last sensor with my only transmitter being at around 75 days (hard reset via spike ios app a few days back) |
|
@QuadAlpha If the problem has been resolved, would you please close the issue? |
|
Please consult with other users as well for questions about how to use xDrip. |
Getting G6 "sensor errors" and no BG results. Reboot, restart sensor not working.
The text was updated successfully, but these errors were encountered: