Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    JamOrHam
    @jamorham
    @roycesimpson yes thats all in there too
    Royce Simpson
    @roycesimpson
    My goodness. That takes me from "maybe g6 isn't where I want to go yet" to "hell yeah!" thanks @jamorham
    JamOrHam
    @jamorham
    G6 is very good, hats off to dexcom
    Royce Simpson
    @roycesimpson
    in googling all this I did see that they may allow the sensors to go 14 days here in the next 6 months or so
    which is about what I get on average anyway.
    they being Dexcom
    CaroGo
    @CaroGo
    So, is it absolutely necessary to use native mode with g6 then?
    old-square-eyes
    @old-square-eyes
    Good question
    Also has anyone managed a battery replacement on the G6?
    LMGTFM
    Gr├ęgory Beloncle
    @gregorybel
    @dansuk Looks like a bug, which version of xdrip? when did you buy your Blucon? can you delete your second screenshot?
    dansuk
    @dansuk
    @gregorybel It's version d1d4887-2018.09.08 (1809080944) - I bought Blucon back in January. I can reshare a link without the second screenshot if that helps? Let me know if you need anything else.
    old-square-eyes
    @old-square-eyes
    @dansuk I think it's just that your second screenshot has unnecessary info and maybe too much info in the logs.
    dansuk
    @dansuk
    @gregorybel @old-square-eyes no problem, I've created a new link here: https://photos.app.goo.gl/zdSs9ezdYkZKKJry9 (sorry, can't work out how to remove from the original link!)
    nsghub
    @nsghub
    @jamorham Maybe this issue can be fixed before the next release?! NightscoutFoundation/xDrip#492
    n0rbertg
    @n0rbertg
    @CaroGo No, you don't have to use native mode with g6 if you don't want to
    CaroGo
    @CaroGo
    @norbertgaal thanks... So, it is just the same as with G5?
    n0rbertg
    @n0rbertg
    @CaroGo I believe so (although I haven't used G5). You can use native mode and it'll restart the sensors automatically or just go without native mode and leave it as long as it runs. You also have the option to reset the transmitter if you'd like to go with native
    JamOrHam
    @jamorham
    You have to enable engineering mode to use G6 without native mode I think
    CaroGo
    @CaroGo
    @jamorham @norbertgaal... Ok.. Engeneering mode is enabled. With G5 I just leave it running,that is the easiest way and works fine. Why should I want to reset the transmitter
    ?
    JamOrHam
    @jamorham
    @CaroGo we don't know if G6 dynamics with raw data might be different, your mileage may vary. With native mode you get backfill.
    CaroGo
    @CaroGo
    @jamorham ok.. That would have been the next question... ­čśĆ... Any other difference apart from enabling smb in AAPS?
    sethgagnon
    @sethgagnon
    what does native mode actually mean again?
    JamOrHam
    @jamorham
    It means it uses the built in algorithm inside the transmitter instead of xDrip using the raw sensor data and its own calculations
    sethgagnon
    @sethgagnon
    @jamorham thanks for the info. by any chance is there a comparison between native and raw for g6 to see the which one performs better?
    CaroGo
    @CaroGo
    I just set a new sensor and changed to native, just to give it another try (still on G5)... Is it normal that sensor status shows "sensor stopped '? When changing to normal mode (xdrip Algo) it shows the usual sensor running status..?
    Raymond Richmond
    @PedanticAvenger
    @sethgagnon It's a case of YMMV. Many find the "calibration" better in xdrip but no backfill (which admittedly is nice for me) without native. And for openAPS applications often native is a must.
    CaroGo
    @CaroGo
    Sorry, but I would like to ask again:is this message OK when using native mode? https://i.imgur.com/3K4I6Qa.jpg the system works... But I don't like this status.. ­čśĆ
    keencave
    @keencave
    @dansuk @old-square-eyes @gregorybel The unknwon command seems to be the getMultipleBlock command answer. It is used in the getTrendData and getHistoricData commands. @tzachi-dar OOP uses it for reading the complete blucon FRAM content at once. We found out that this is a generic command where at byte 5 and 6 contains starting block and ending block. I guess there must be an error in the state machine caused by <unknown>. I think we need the full sequence containing the command sent to the blucon.
    keencave
    @keencave
    Funny that: In the log I see sometimes a one block answer for the multipleBlock Command. I didnt remember that the protocol uses that command for a one block read. For the OOP algo it is used but there the anwers contains only blocks with an even number (0,00, 0x02, 0x06, 0x08, ...). In the log are also odd numbers visible: 8bdf0302... (where 0x03 is th starting block number). I cannot see any code in blokon.java which should cause this. @dansuk Maybe you can post an extended log where we can see the starting point?
    Ivica Suran
    @isuran
    I'm getting NO BG? couldnt find slope! error when I try to use huawei 2 smartwach as collector, it worked without problems until yesterday. I supose there are empty values, when phone is used as a collector it works good. Tried to install last nightly build and reinstall watch but error states the same. Any clues?
    dansuk
    @dansuk
    @keencave @old-square-eyes @gregorybel @tzachi-dar could you let me know where I can find the xdrip log on the device and I'll try and get a more complete example? It does make sense what you say about the historic data and libre trend functions as I had used both of those (and since switching off the get historic Libre data haven't had the issue since)
    Gr├ęgory Beloncle
    @gregorybel
    @dansuk @keencave yes it Looks like a bug! @dansuk can you enable more debug: less common settings / Extra loggings settings / Extra Tags for loggings and add Blukon:v then reproduce issue and send logs within Xdrip and ask @jamorham to provide us the logs
    to send logs: "upload logs"
    keencave
    @keencave
    :+1:
    dansuk
    @dansuk
    @gregorybel @keencave @jamorham ok, I will give it a go!
    dansuk
    @dansuk
    @gregorybel @keencave @jamorham I have sent the logs. The unknown command issue is present in the logs. I couldn't reproduce the constant sequence of unknown commands that I reported initially and subsequent lack of readings but if I get that again I will send another set of logs. After enabling the debugging, I allowed two readings to be retrieved normally and then removed blucon from libre and waited about 30 minutes before reconnecting with the libre history option selected. I then allowed more readings and also displayed the Libre trend graph. You will see the unknown command errors. Let me know if you need anything further.
    JamOrHam
    @jamorham
    I have the logs, where should I send them to?
    Gr├ęgory Beloncle
    @gregorybel
    keenkave and me @jamorham
    Ivica Suran
    @isuran
    @isuran I have cleaned cache of phone and watch, all working now
    Karim Azzaz
    @moimemecloud
    Hi there, is anyone who tried the xdrip+ with poctech please ? Thank you if yes ,, what was your experience please ?
    nicoleloop
    @nicoleloop
    @jamorham I recently started using a new G5 transmitter, and I am using my SW3 as the collector (Ob1G5 not native). Everything seems to be working fine, except that the info on my Status page doesn't show the correct info, as is shown in the link below... https://drive.google.com/file/d/13CAu4GPhfk5Mng75osqGywbq8KjFp0XW/view?usp=drivesdk What could cause this issue?
    RalfCGM
    @RalfCGM
    @CaroGo it's the collector on the g5 which isn't started. You probably still get readings because xdripcollector interprets raw data from g5.
    CaroGo
    @CaroGo
    @RalfCGM... Ok, thanks. So, what do I have to do?
    Restart collector does not seem to solve this
    RalfCGM
    @RalfCGM
    @CaroGo for me a also first experiences on g5 native. But as far as I understand, g5 transmitter doesn't start in native mode after xx days (I thought 90?). I think you should be able to stop and restart as usual. I sometimes takes a while for the commands to reach the g5. You see the command que in the screenshot you send earlier. So: stop transmitter. Wait for command que to get empty. Start again and wait again for command que to empty. After that the transmitter should perform as usual.
    CaroGo
    @CaroGo
    @RalfCGM ok..thanks for the info... I will try that. It is only strange... If I switch native off everything works just fine... With the xdrip Algo no sensor stopped anymore...
    RalfCGM
    @RalfCGM
    @CaroGo that's expected behavior. When switched off on xdrip there's no info displayed from the g5 receiver, while for example internally it's still in stopped (or started or error) state. If you turn on native mode, it should display the same message as when you turned it off.