Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    fidoman
    @efidoman
    @ElyeM - my guess is the tslim pump is using the primary bt channel from the tx. Does xdrip-plus have the option to change which tx bt-channel it uses? If so, then xdrip-plus could use the alternate bt channel and both would likely work.
    dvdv
    @dvdv_gitlab
    Unfortunately, the extended restart did not help me - I did see a jump. However, I am suspecting that it might be because I calibrated the sensor within the first 10 days.
    JamOrHam
    @jamorham
    @ElyeM Are you only using the SW3 as the collector (eg never the phone?) If so then set the option Only use Wear would fix it. If you're trying to use 3 different devices to talk with the transmitter then that wont really work.
    dvdv
    @dvdv_gitlab
    @jamorham BTW, thanks for adding the restart notification!
    AdrianLxM
    @AdrianLxM
    Fun-Fact: xDrip (without plus or anything) still has 65 daily users.
    jroth-haj
    @jroth-haj
    @AdrianLxM how old is xDrip (without plus)? What' ist ist supporting? Only G4?
    Antony
    @acron0
    Looking for some advice... I had a G5 until today when I got a G6. I thought it was just a case of ticking 'G6 Support' in the Settings and changing my Hardware Source but apparently not. 2 hours after sensor starting still no data from G6 and all UI still referencing G5. So, I re-installed xDrip+ and went through the Start Sensor process (again) and now the Data Source is correctly reading 'G6 Native' but even once I put in all the details the 'Start Sensor' prompt keeps coming up....the sensor should already be started...
    Screenshot_20190821-002359_xDrip+.jpg
    Screenshot_20190821-002356_xDrip+.jpg
    Antony
    @acron0
    No idea how to remedy this loop. Once I hit 'Start Sensor' input the time and calibration code, it says 'Code Accepted' but then nothing happens. As soon as I go back to Home it hits me with the prompt again.
    JamOrHam
    @jamorham
    @acron0 make sure to run a recent nightly of xDrip+ as your sensor is 8Gxxx version. Long press the xDrip icon on the top of the screen and then enable source wizard, then select G6 and try starting sensor again after that if still not working.
    Antony
    @acron0
    Downloading Nightly now, thanks
    @jamorham Exactly the same behaviour :(
    Screenshot_20190821-004224_xDrip+.jpg
    This is a G6, although I did use a G5 up until today
    Antony
    @acron0
    Would there be any state left over after a reinstall that's confusing it?
    Ok, I think I know the problem
    Antony
    @acron0
    It's 1am here and I've been saying I started the sensor TODAY, and putting in the time I really inserted it, 8pm
    I just noticed an error on the screen 'Started time in the future'
    Pebkac
    AdrianLxM
    @AdrianLxM
    @jroth-haj it had initial G5 support but only for the early batches of transmitters. And the Limitter was also in.
    jroth-haj
    @jroth-haj
    Never change a running system. ;-)
    CaroGo
    @CaroGo
    @acron0 you should not put in a time of sensor start that's different to the actual time.... G6 doesn't allow setting back the insertion time...
    davorcro
    @davorcro
    Hi, is any (nightly) version of xDRIP ready for Miao Miao2? I am trying to connect it but with no success. thx
    aceholgi
    @aceholgi
    @CaroGo Ahhh, that's interesting, I didn't know that! My calibration attempts were turned down with "older than an hour"...
    Jon
    @jonprogers
    @ElyeM I've only been a tslim user for 7 days so far but it is working OK with xDrip+ so it looks like tslim uses the alt channel leaving the primary for a phone app (dex or xdrip+). I have seen a 2-3% drop in realtime xdrip collection with both devices dropping a reading or two every so often which appears to be reduced when the phone and pump are kept a bit further apart (opposite sides of the body) so it could be some form of bt clash but it's way too soon to be sure... How are you finding the tslim?
    Heiner1
    @Heiner1
    If we could integrate the patched Libre2 smooth function in the 640G / Eversense plugin it would be a big advantage, what do you think about? @jamorham @AdrianLxM
    viq
    @viq
    @davorcro oh, is miao2 available already?
    dabear
    @dabear
    I have the mm2. IT Will be available soon for the general public
    viq
    @viq
    Ah, cool
    Kinda speaking of, any news on updated Libre OOP with their new algorithm?
    AdrianLxM
    @AdrianLxM
    @Heiner1 the eversense app (Esel) hast it's own smoothing function.
    Also: Libre sends data every minute. It's not necessarily a perfect fit. Did you play with the smoothing settings in Esel?
    Antony
    @acron0
    @CaroGo What do you mean? If I put a sensor in, then wait 10 mins before starting it in xDrip, what time do I put in?
    CaroGo
    @CaroGo
    @acron0 I don't wait to start it... And just put in the correct actual time... I think it does not accept time difference larger than 5min.... Not sure about this, just my observation....
    Jon
    @jonprogers
    @CaroGo I'll second that, always struggled to get a G6 to start well if not entering the current time - hadn't twigged the thing about it having to be in the same 5 minute sleep window though but that certainly fits with observations...
    old-square-eyes
    @old-square-eyes
    Does xDrip still send calibrations to a started G5s Native, if using xDrip algo?
    I see logs and get warnings if I accept after 1hr than it can't be sent to Native.
    So I assumed so, but not much in status
    Heiner1
    @Heiner1
    @AdrianLxM Hi Adrian, yes I played with it, but still not the best; I'm impressed by the results of smoothing function for the libre2 plugin, looks better than smoothed readings from ESEL. To integrate it into NSEmulatorReceiver would be a nice idea, what do you think about, is it possible?
    flo-doc
    @floriancgm
    Did anybody become problems with combo pairing? After updating xdrip nightly 2019-08-21. last morning I lost combo connection, up to now I could not manage new ruffy pairing. Have the bluetooth conditions changed?
    birdfly
    @birdfly
    @Heiner1 My experience with Libre2,when the reading has noise ,Librelink always said “sensor error,wait for 10 mins”
    birdfly
    @birdfly
    image.png
    Kichul Kim
    @nic2mit
    @floriancgm i am on xdrip+ nightly 8/20/2019. My combo/ruffy works fine. I am using oneplus 7 pro. I would keep try to delete/pair combo pump using ruffy. I would read and follow some tips from https://m.facebook.com/groups/127507891261169?view=permalink&id=253865378625419&refid=18&ref=bookmarks
    dvdv
    @dvdv_gitlab
    @jamorham Thanks for your efforts to crack the 2.x firmware! I do wonder if these changes are also significantly driven by dexcom's collaboration with apple. In a video, the Dexcom CEO mentions that they had to update the firmware for the apple watch: https://www.youtube.com/watch?v=ozoVpPULySo&t=4m50s
    btw, any updates?
    keencave
    @keencave
    @birdfly What was your setup with the L2? Simply reading via the patched LibreLink app? Have you checked the logs? Please enable "xdrip libre_receiver:v". Then you can check the minutewise readings from the app. Are those readings also very noisy?
    Heiner1
    @Heiner1
    @birdfly I haven't seen such noisy readings within my first 14 days of L2 experience. And only for a while, looks like triggered by a BG limit.
    flo-doc
    @floriancgm
    @nic2mit ThankyouKim,I could pair the combo in "red characters" but crosstalk with AAPS is not possible. I Think the mobile bluetooth is somehow broken. nothing to do with xdrip bluetooth
    swissalpine
    @swissalpine
    .