Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Sandra Keßler
    @SandraK82
    @c9679 I studied software engineering. Not application development. So I got a Good Fundation in engineering concepts. Additionally the it folks where originated from the electrical engineers, math and mechanical engineers. Therefore I had to do many studies in broader engineering and mathematics. Further I was always interested in mechanical stuff. Today I have no real specialization. I use the tools and languages as I need them and technical problems of my customers required me to go deeper into building prototypes. The real devices are constructed by the appropriate engineers, often based on my designs or including ideas I had
    NFCole
    @NFCole

    I have a problem with my LimiTTer, I can connect it with xDrip but I dont receive any values. I tested it with an dead L2 sensor and get this in serial monitor, but for me it looks like everything works. Any idea what is wrong?~~~~~.....

    [.][4][59]000 === loop 1 === NORMAL V1.1.01 190502_1317
    run time: 299 s, Arduino On: 22.79%, BLE ON: 134.60%, NFC: 0.94% total loops: 1, normal: 1, 1st resend: 0, 2nd resend: 0, battery voltage: 4062 mV
    [.][4][59]431 battery level : 4062
    [.][4][59]596 Sensor Version: LIBRE2, Sensor SN: 0MH000CD97D - done (0)
    [.][5][00]293 crc FRAM: 0x85D5 dead L2 sensor, skip
    [.][5][00]303 did not receive a pkt with 0 pkts in queue
    [.][5][00]371
    no data to send
    next_normal_wakeup 600 s, current time 300 s, var_sleepTime set to 299 loop time is 1 s, sleep for 299 s, all complete 300 s, cons loops w/o BLE 2
    [.][5][00]584 ->(AT) <->
    [.][5][01]620 === goToSleep for [299], calibrate call para of goToSleep() with [0.88] to 264.07
    ~~~~

    NFCole
    @NFCole
    works again, seems it was a phone problem...
    keencave
    @keencave
    @NFCole Seems that you disabled the USE_DEAD_SENSOR option which is needed to get values from a dead L2 sensor. Logfile said: "no data to send" so LBridge is not sending anything in that case to the xDrip+.
    keencave
    @keencave
    Have to review the code as the S/N in your log is from a Libre 1. Maybe not proper initialiesed for the first loop.
    Arik
    @3ThriftyTrinket_twitter
    Ugh, just messed up the solder point on my bluetooth module. Any tips for soldering such difficult points?
    keencave
    @keencave
    Use a sharp solder tip. Use Isopropylalcohol to clean the solder pin. Presolder the solder pin before soldering the wire.
    You will find some youtube videos when searching for "xdrip" or "wixel".
    Arik
    @3ThriftyTrinket_twitter
    Thank you! Now to wait for another board -_-;
    keencave
    @keencave
    You can try to solder the damaged board by removing the the coverage of the wiretrace near the solder point with abrasive paper or a glasfiber brush.
    Arik
    @3ThriftyTrinket_twitter
    I tried but I'm not the greatest at soldering. Thank you though!
    Arik
    @3ThriftyTrinket_twitter
    It lives!
    Arik
    @3ThriftyTrinket_twitter
    Hrm... perhaps not. It's connected in bluetooth and I started the sensor but it's not getting data?
    Arik
    @3ThriftyTrinket_twitter
    Just checked the github, I'll retry soldering my wires and let ya'll know what happens.
    Arik
    @3ThriftyTrinket_twitter
    No luck. It seems to be stuck trying to figure out the baud rate on the hm-17 thanks to your Lbridge software @keencave .... I've checked and double checked all of the wires, I can't figure out what's wrong.
    keencave
    @keencave
    Wrong HM1x module?
    Arik
    @3ThriftyTrinket_twitter
    I mean, I suppose it's possible? I bought this https://www.amazon.com/dp/B07GP2WZ2J/ref=cm_sw_r_cp_apa_i_dzrbDbAKMK6CQ and even dug up the datasheet from their website. Pins match up and the default baudrate is the 9600 one. Is it possible the chip worked for a minute before dying or shorting out? It was there at first and I connected to it but now it's gone.
    Arik
    @3ThriftyTrinket_twitter
    I'm really not sure what to do, I mean, should I buy a different HM1x module?
    keencave
    @keencave
    Your model looks correct. Not sure what happened. You could try to order another module and try again. You could also try to directly connect the HM17 module to your PCs serial port (Serial to USB converter). The you could try to connect via putty with 9600 baud.
    Arik
    @3ThriftyTrinket_twitter
    I'll have to figure out Putty when I get a chance, thank you. I'm hesitant to buy from the same person again though. Any suggestions for the US as most of the places I've found are shipping from china and would take quite a while to arrive? Maybe I'm just being impatient....
    Arik
    @3ThriftyTrinket_twitter
    So here's what I'm getting, it repeats this three times before trying to reset the module several times and it just doesn't appear to be getting any response. I'm sure you know what the code looks like so I'm trying to avoid posting a massive block of text but yeah....
    [0][02][002](626) ------------------------------------------------------------------
    [0][02][027](668) --- LBridge starting ---
    [0][02][072](660) --- RELEASE version settings ---
    [0][02][127](678) --- BLE Name: LimiTTer ---
    [0][02][177](679) --- Version: 0716_1950 ---
    [0][02][226](676) --- avail. mem: 708 ---
    [0][02][271](676) --- queue size: 5 h
    [0][02][314](660) --- spike removal option enabled
    [0][02][369](626) ------------------------------------------------------------------
    [0][02][459](660) setup HM-1x, determining baudrate
    [0][02][514](686) trying 9600
    [0][02][549](670) ->(AT) -
    [0][04][083](686) trying 19200
    [0][04][085](670) ->(AT) -
    [0][05][593](686) trying 38400
    [0][05][595](670) ->(AT) -
    [0][07][102](686) trying 57600
    [0][07][104](670) ->(AT) -
    [0][08][611](686) trying 115200
    [0][08][613](670) ->(AT) -
    [0][10][121](686) trying 4800
    [0][10][127](670) ->(AT) -
    [0][11][634](686) trying 2400
    [0][11][644](670) ->(AT) -
    [0][13][152](686) trying 1200
    [0][13][158](670) ->(AT) -
    [0][14][665](686) trying 230400
    [0][14][667](670) ->(AT) -
    [0][16][175](645) Could not detect baudrate of HM-1x, setting 9600
    [0][16][179](631) reset BLE, power down - 1000 ms - power up - 1000 ms0
    keencave
    @keencave
    Seems that the module is either dead or not connected properly. Can you post a photo of the soldered module?
    Arik
    @3ThriftyTrinket_twitter
    Not sure how to add a picture in gitter so here you go. https://twitter.com/3ThriftyTrinket/status/1141307540875010048?s=09
    I know I need to trim the leads on it but it makes it easier to solder
    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):