Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    keencave
    @keencave
    Will check it once back at my desk.
    keencave
    @keencave
    Looks that on the HM17 side all connections are correct. The soldering looks OK, no need to trim the wires after soldering. Please crosscheck on the Arduino side the RX/TX connections and measure if the HM17 module gets power of 3.3V after program start.
    keencave
    @keencave
    Here is the wiring of my prototype board_
    20190620_173948.jpg
    keencave
    @keencave
    Just released the latest Arduino LBridge code version 1.1.02 supporting Libre Pro.
    Arik
    @3ThriftyTrinket_twitter
    Oh! Awesome!
    Arik
    @3ThriftyTrinket_twitter
    I'll do that after I get home, thank you!
    Arik
    @3ThriftyTrinket_twitter
    @keencave I got it to momentarily "work" again! Work meaning that I got it to connect to Xdrip but not to send data. I'm trying to get it to connect to my computer now via putty so I can figure out what's going on.
    keencave
    @keencave
    Can you post the startup messages with your current setup? When BT is OK I recomend to resolder the BM019 module. You should see a misfunction in the serial monitor.
    Arik
    @3ThriftyTrinket_twitter
    Well, I messed up my arduino the other day so I picked up a new one from Sparkfun and finally got it working! Only issue is I didn't realize LimiTTer doesn't work with the US version so... yeah.
    Thank you for all your help keencave.
    NFCole
    @NFCole
    @3ThriftyTrinket_twitter try the latest version of Lbridge 1.1.02 it should work
    Arik
    @3ThriftyTrinket_twitter
    @NFCole Thank you but that's what I was using
    keencave
    @keencave
    We can only detect a US Libre version but dont understand the data format. It is encrypted.
    leo lee
    @leoleezoom
    👍
    Madhukar S Holla
    @madhukar01
    Got my components and have built my LBridge..
    Was wondering if it is possible to read the full history from the sensor instead of just the last reading? @keencave @JoernL
    keencave
    @keencave
    On the libre1 lbridge will send the last 8h history to xdrip+.
    Madhukar S Holla
    @madhukar01
    Sorry, this is FSLibre Pro
    14 days sensor
    keencave
    @keencave
    I have to implement that feature for the pro. At the .oment missing.
    nigelkeirross
    @nigelkeirross
    @keencave @JoernL Hi, about 18 months ago I built a couple of limiTTers (arduino pro-mini 3v 8MHz, BM019, HM-17), running LBridge_Arduino_170716_1950.ino. One has now stopped working (Not yet debugged), so I am looking to build a replacement. I see that HM-19 is available and is claimed to be compatible with the HM-17. I wondered if that was the case in this context, and what experiance people had?
    keencave
    @keencave
    I have not tested a hm19 nor have heard sbout that. But i guess it should work. If needed it is easy to change some command sequences. I need a trace for that.
    nigelkeirross
    @nigelkeirross
    @keencave OK thanks. Will try next time.
    c9679
    @c9679
    Congrats on the Droplet @MarekM60 :)
    Marek Macner
    @MarekM60
    :) Thanks
    momofomo
    @momofomo
    @keencave - tried running the newest code: LBridge_Arduino_V1.1.02_190502_2120.ino and I'm receiving a similar error to @Ericcarbonn . I'm currently using Freestyle Libre from Canada. The output from the serial monitor in Arduino (using 1.8.9):
    19:27:24.512 -> [.][0][02]003 ------------------------------------------------------------------
    19:27:24.617 -> [.][0][02]029 --- LBridge starting ---
    19:27:24.650 -> [.][0][02]079 --- BLE Name: LimiTTerLx ---
    19:27:24.717 -> [.][0][02]134 --- Version: V1.1.02 from 190502_2120 ---
    19:27:24.784 -> [.][0][02]202 --- avail. mem: 417 ---
    19:27:24.852 -> [.][0][02]251 --- queue size: 4 h
    19:27:24.886 -> [.][0][02]294 ------------------------------------------------------------------
    19:27:24.987 -> [.][0][02]388 setup HM-1x, determining baudrate
    19:27:25.021 -> [.][0][02]447 trying 9600
    19:27:25.055 -> [.][0][02]484 ->(AT) <-> OK
    19:27:25.541 -> [.][0][03]023 got OK
    19:27:25.574 -> [.][0][03]023 baudrate set to 9600
    19:27:27.573 -> [.][0][05]038 ->(AT) <-> OK
    19:27:28.060 -> [.][0][05]544 ->(AT) <-> OK
    19:27:28.583 -> [.][0][06]046 ->(AT+NOTI1) <-> OK+Set:1 <-(+Set:1) -
    19:27:29.171 -> [.][0][06]642 ->(AT) <-> OK
    19:27:29.685 -> [.][0][07]145 ->(AT+NAMELimiTTerLx) <-> OK+Set:LimiTTerLx <-(+Set:LimiTTerLx) -
    19:27:30.280 -> [.][0][07]754 ->(AT) <-> OK
    19:27:30.804 -> [.][0][08]255 ->(AT+VERR?) <-> HMSoft V605 <-(HMSoft V605) -
    19:27:31.350 -> [.][0][08]812 ->(AT) <-> OK
    19:27:31.868 -> [.][0][09]316 ->(AT+ADDR?) <-> OK+ADDR:A810871D105D <-(+ADDR:A810871D105D) -
    19:27:32.465 -> [.][0][09]914 ->(AT) <-> OK
    19:27:32.965 -> [.][0][10]418 ->(AT+RESET) <-> OK+RESET <-(+RESET) -
    19:27:34.071 -> [.][0][11]532 ..... initial wake up, waiting 40s fixed for BLE, time for a xDrip+ BT scan if needed
    19:28:14.250 -> [.][0][51]583 entering main loop next_normal_wakeup = 300
    19:28:14.318 -> [.][0][51]587 battery level : 5068
    19:28:14.352 -> [.][0][51]630 calibrate PWR DOWN sleep timer (2048 ms) ...
    19:28:16.403 -> [.][0][53]729 calibv = 979.36, tt1 = 52699, tt2 = 54728
    19:28:18.427 -> [.][0][55]757 NFCProtocolSelect error
    19:28:40.636 -> [.][1][17]902
    failed getting UID, clearing UID
    19:28:40.705 -> [.][1][17]904 non sensor
    19:28:40.740 -> [.][1][17]935 NFC read error, wait 3 s
    19:28:45.753 -> [.][1][23]018
    NFCProtocolSelect error
    19:29:07.983 -> [.][1][45]163 failed getting UID, clearing UID
    19:29:08.018 -> [.][1][45]165
    non sensor
    19:29:08.089 -> [.][1][45]195 NFC read error, wait 3 s
    19:29:13.092 -> [.][1][50]279 NFCProtocolSelect error
    19:29:35.302 -> [.][2][12]424
    failed getting UID, clearing UID
    19:29:35.370 -> [.][2][12]426 non sensor
    19:29:35.406 -> [.][2][12]456 NFC read error, wait 3 s
    19:29:38.390 -> [.][2][15]514 did not receive a pkt with 0 pkts in queue
    19:29:38.494 -> [.][2][15]516
    no data to send
    19:29:38.528 -> next_normal_wakeup 300 s, current time 135 s, var_sleepTime set to 164
    19:29:38.596 ->
    loop time is 135 s, sleep for 164 s, all complete 299 s, cons loops w/o BLE 1
    19:29:38.705 -> [.][2][15]729 ->(AT) <-> OK
    19:29:39.667 -> [.][2][16]769 === goToSleep for [164], calibrate call para of goToSleep() with [0.98] to 161.62
    19:29:39.769 -> 0x0 ~~~~.
    19:32:23.473 ->
    19:32:23.473 -> [.][4][59]000 === loop 1 === NORMAL V1.1.02 190502_2120
    19:32:23.544 -> run time: 299 s, Arduino On: 45.76%, BLE ON: 45.74%, NFC: 24.26%
    19:32:23.616 ->
    total loops: 1, normal: 1, 1st resend: 0, 2nd resend: 0, battery voltage: 5068 mV
    19:32:23.889 -> [.][4][59]430 battery level : 5068
    19:32:25.918 -> [.][5][01]458 NFCProtocolSelect error
    19:32:48.143 -> [.][5][23]603
    failed getting UID, clearing UID
    19:32:48.210 -> [.][5][23]605 non sensor
    19:32:48.246 -> [.][5][23]636 NFC read error, wait 3 s
    19:32:53.277 -> [.][5][28]719
    NFCProtocolSelect error
    Any suggestions on how I can fix this?
    momofomo
    @momofomo

    also, @Ericcarbonn - did you find a way to get your LimiTTer device working on your apple phone (iOS)? I looked into Spike and noticed that there's a new installation process (with the need to renewal your certificate every 7 days). Have you gotten your LimiTTer working on any iOS apps? Someone mentioned xDripiOSReader - has anyone tested the new code with this app (also, where do I find the newest version of xdripiosreader)?

    I'm open to anyone's input/feedback. Been trying to get my LimiTTer working on an apple device for a while now. It'd be great to not have to carry around an Android device for the sole purpose reading my LimiTTer :)

    EricCarbonn
    @Ericcarbonn
    @momofomo I did not find a way to have the limitter work with Spike and it will not work with iOSxdrip. The UUID of the HM-1x in the limitter is not in the app code and can only be added by the developer of Spike. I gave up and got a MiaoMiao. I needed something to work with iOS to start with Loop. Now I would probably go with the Droplet for Marek.
    momofomo
    @momofomo
    Hi @Ericcarbonn - thanks so much for the quick response! How do you like the MiaoMiao? I was looking into getting one. I was told by a MiaoMiao rep that the shipping time can take 10-15 days (or more). How long did it take for you to receive the MiaoMiao (and did you need to pay for customs/duties)?
    What is the droplet?
    Also, it's disappointing to learn that LimiTTer didn't end up working with in iOS app. Thanks for letting me know -- that's a huge time saver for me! Also, to add my previous post - I'm also living in Canada (BC) (hence the question for how long it took the MiaoMiao to reach you). :)
    EricCarbonn
    @Ericcarbonn
    @momofomo The miaomiao for me is working fine. Using it with Spike/Loop/Omnipod and I have had issues yet. The Droplet is a new transmitter sold by @MarekM60. Smaller form factor, works with Spike and android apps. https://droplet.rocks/en/ The MiaoMiao took about 3 weeks to get to the Montreal area no duties or customs. Personally I would choose the Droplet over the MiaoMiao now that it is available.
    momofomo
    @momofomo
    Thanks, @Ericcarbonn! I do agree that the Droplet seems like the preferable option.
    Congrats @MarekM60! The Droplet looks great!! I’d like to order a droplet. Do you ship to Canada? I tried ordering one from your web store but can’t seem to find canada in the drop down list of countries.
    keencave
    @keencave
    @momofomo "NFCProtocolSelectError" from the log messages sounds unusual. Will have a look in the sources soon.
    What battery are you using? More than 5 V?
    Marek Macner
    @MarekM60
    @momofomo :smile: now Canada exists - was Kanada
    momofomo
    @momofomo
    CP2102 USB to UART connection
    @keencave
    I disconnected the lipo battery and was getting power for the device from my computer’s USB port
    keencave
    @keencave
    Is it possible to enable
    #define SHOW_NFC_ERROR        // uncomment to log NFC communication
    #define SHOW_NFC_CMD          // uncomment to log NFC errors
    to see more NFC communication? The error from the log seems to be a generic communication error between Arduino and the NFC chip. It may help to resolder the connections between both chips.
    NFCole
    @NFCole
    Does anyone know if there are requirements for using the patched Librelinkapp with xdrip+. I tried different versions of both apps but it is not working...
    JulienBub
    @JulienBub
    @NFCole use latest nightly of xdrip... there is a collector called Libre 2 patched
    You also have to start a new sensor with patched app... but before you start the sensor you should enable app permissions for storage
    NFCole
    @NFCole
    @JulienBub thanks, but I did all of it. Two times I got the notification directly after starting the sensor, that xDrip+ was stopped
    JulienBub
    @JulienBub
    @NFCole Strange... Im currently looping with this