LimiTTer
LimiTTer copied to clipboard
JoernL
LIMITTER
Hola mi nombre es Pedro y soy padre de un niño Diabetico que usa el freestyle libre. Primero quisiera darle mi enhorabuena por el desarrollo del proyecto ya que llevábamos tiempo buscando algo parecido. Estoy deseando que comparta su diseño para poder probarlo en mi hijo sobre todo por la utilidad de guardián nocturno. Gracias por su tiempo y dedicación estoy convencido que seremos muchos los padres que se lo agradeceremos. Espero tener pronto noticias suyas
I speak a little spanish - here is a rough translation:
Hi, my name is Pedro and I am the father of a Diabetic boy that uses the Freestyle Libre. First I want to give my congratulations for developing the project since we have been waiting some time for something like this. I want you to share the design for us to be able to use it with my boy, above all, for the overnight watch. Thanks for your time and dedication. I am convinced that there will be many of us parents that thank you. I hope we have more updates from you soon.
Congratulations for developing such as great project. I ordered some of the components of the limitter in aliexpress.com, except the BM019 NFC2Serial. Is there any other NFC2serial compatible dongle to replace it? Many thanks
Jeers, is there any trick to pair with Android? I use same parts as you do. I have Nexus with Android 6 and can't pair, not with the default pin or any other, can't see it in xDrip, any ideas?
To see the name "Limitter" in Settings-> BT, I had to change the code to: ble_Serial.write("AT+NAMELimitter");
Thanks Mike. I'll try that. I can see the HMSoft device in xDrip without that mod and it pairs, although it didn't transmit any data. Do you have the correct baud rate set?
Sent from my iPhone
On 26 Apr 2016, at 13:23, libxmike [email protected] wrote:
Joern, is there any trick to pair with Android? I have Nexus with Android 6 and can't pair, not with the default pin or any other, can't see it in xDrip, any ideas?
To see the name "Limitter" in Settings-> BT, I had to change the code to: ble_Serial.write("AT+NAMELimitter");
— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub
Hello,I am a T1D for six years and user of a free style libre,I just wonder that LimiTTer(the hardware )could interpretate the Tag-data or transmit the raw data to xDrip directly.For I have used several libre apps ,the value they read are different from the official reader.
Okay, my progress so far is that I've built the LimiTTer, and that all the components communicate. I can confirm the Arduino is speaking to the HM10 as, with the earlier tweak, I was able to get the module renamed correctly.
The assembly then connects to xDrip on the phone successfully.
At the five minute intervals, the NFC card comes to life and I am assuming it scans, and I see the green LED flash on the Arduino. What I don't get is anything in xDrip. Nothing is showing up.
I welcome any ideas on what I might need to change. The baud rate is set to 9600 as is the default on my HM10. Just not picking anything up and transmitting it.
Sent from my iPhone
On 26 Apr 2016, at 15:05, JoernL [email protected] wrote:
Settings -> Apps -> xdrip -> permissions. Enable location services.
— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub
You are not able to start a sensor in xdrip? The 2 start readings don't come in?
That's right. Whilst xDrip sees the Bluetooth and connects, and I see the BM19 trigger, I'm not seeing anything come in on the two start readings. I'm running android 5.1.
Sent from my iPhone
On 26 Apr 2016, at 23:47, JoernL [email protected] wrote:
You are not able to start a sensor in xdrip? The 2 start readings don't come in?
— You are receiving this because you commented. Reply to this email directly or view it on GitHub
The Hardware Data Source in xDrip settings must be set to "Bluetooth Wixel". Maybe you have changed this?
@birdfly as yet, it only reads the last saved reading from the sensor and send it to xDrip, which modify the raw value through a slope and an intercept and then displays it at it's graph. I'm working on it now to find out how the original reader can precalculate the readings when glucose rising fast? At this moment, the raw reading is nearly the same but the LibreReader shows a very higher value. Maybe a hidden dynamically slope multiplier in the tag? Didn't find it yet.
Joern,
I commend your work and find it most interesting. My own feeling is that I think I prefer to see a raw reading from the Libre, with a simple adjustment to put it into mmol/ml. I think the need for predictive algorithms is perhaps not as great as the stress that some put on them.
My take on it is that knowledge and context are the most important thing. I know that the interstitial glucose level lags behind BG as measured with a finger stick. This in itself lags behind venous level. Just as we are all used to the lag in BG fingerstick readings, maybe we should all get used to the lag in interstitial readings.
If I see that the Libre raw reading is fairly constant, then I can have good confidence that it reflects the reality. Constantly high, maybe I need to take a small amount of insulin. Level of 4.0 for half an hour and I'm about to exercise then maybe a little glucose is in order.
If the Libre reading is rising fast, I can judge for myself if there is a single reading that is a little out of step or if there is a trend. If there is a trend, then I can see how sharp the trend is, and for how long it has been there. I can look a the picture and let my brain fathom it out using its massive parallel processing power and pattern recognition abilities in order to understand what is happening. An actual, predicted level that matches a BG fingerstick I don't believe is my ultimate objective. I can guess at what it might be and it will probably be as correct as any complex multiple derivative based algorithm.
Perhaps the trouble with the algorithm is you don't quite have a grasp of what the algorithm has done. At least with raw data I can use my experience.
Likewise when BG is dropping. I see that the raw data is plunging from 13 to 10 to 7 to 5 in 25 minutes. I think I'm not concerned that I don't have a predictive current value equivalent to BG fingerstick. I want some glucose please, NOW. Even though it says 5. My experience tells me what is going to happen next. Not that I have such dramatic incidents too often, but it can happen.
So adjustment of data with slope and intercept yes, but predictive algorithm like the built in one - kinda looks good but not necessary.
As you know occasionally the Libre refuses to give you a reading. Wouldn't you just love to know what the raw values are that led to that decision. Well I guess we do now with the BM019 but I've yet to see it for myself.
Sorry - not trying to put you off - its good to have a predictive algorithm too. The more info the better.
Cheers
Bernie
(edited to just remove a typo)
Definitely set to the correct source. That's what is so odd.
Sent from my iPhone
On 27 Apr 2016, at 12:29, JoernL [email protected] wrote:
The Hardware Data Source in xDrip settings must be set to "Bluetooth Wixel". Maybe you have changed this?
— You are receiving this because you commented. Reply to this email directly or view it on GitHub
Tim- have you tried using a Bluetooth tool like Adafruit Bluefruit LE or BLE ( I use the ones for iOS) to confirm the BLE packets? And have you successfully paired the BLE in both android settings and xDrip? I haven't had issues with getting the data to display on xDrip, just that the mmol conversion needed to be added in.
Joern- which algorithm are you using to retrieve the current BG value? Is it debased on LiApp or Glimp? The Glimp calculation makes the process much clearer and provides the previous 15 values showing how trend can be predicted. Would be useful to be able to send BLE request to bm019 to "fill the gaps" and provide previous values too.
I've not tried to pair it in android settings as experience with xDrip in the past was that you just paired from xDrip. That can easily be rectified though, just not this weekend!
Sent from my iPhone
On 27 Apr 2016, at 19:43, SugarBots [email protected] wrote:
Tim- have you tried using a Bluetooth tool like Adafruit Bluefruit LE or BLE ( I use the ones for iOS) to confirm the BLE packets? And have you successfully paired the BLE in both android settings and xDrip? I haven't had issues with getting the data to display on xDrip, just that the mmol conversion needed to be added in.
Joern- which algorithm are you using to retrieve the current BG value? Is it debased on LiApp or Glimp? The Glimp calculation makes the process much clearer and provides the previous 15 values showing how trend can be predicted. Would be useful to be able to send BLE request to bm019 to "fill the gaps" and provide previous values too.
— You are receiving this because you commented. Reply to this email directly or view it on GitHub
@tim2000s, there is no need to pair it in Android settings.
@SugarBots, i only take the latest (recent) raw value and send it to xDrip's slope. I have a test version of xDrip installed to find out the best slope setting of that raw value. I have find out that a fixed slope of 1.15 works best by now. What about a second version of the LimiTTer sketch which pre-calculates more agressive based on the last 15minutes? So you can decide oneself's favour.
Can I use this to get it smaller. :) Only missing nfc now. :)
Martin Den 28 apr 2016 1:31 em skrev "JoernL" [email protected]:
@tim2000s https://github.com/tim2000s, there is no need to pair it in Android settings.
@SugarBots https://github.com/SugarBots, i only take the latest (recent) raw value and send it to xDrip's slope. I have a test version of xDrip installed to find out the best slope setting of that raw value. I have find out that a fixed slope of 1.15 works best by now. What about a second version of the LimiTTer sketch which pre-calculates more agressive based on the last 15minutes? So you can decide oneself's favour.
— You are receiving this because you commented. Reply to this email directly or view it on GitHub https://github.com/JoernL/LimiTTer/issues/1#issuecomment-215394540
Forgot link. http://m.ebay.co.uk/itm/Digispark-Kickstarter-Attiny85-USB-Development-Board-for-Arduino-BEST-/141672395445?nav=SEARCH Den 28 apr 2016 1:31 em skrev "JoernL" [email protected]:
@tim2000s https://github.com/tim2000s, there is no need to pair it in Android settings.
@SugarBots https://github.com/SugarBots, i only take the latest (recent) raw value and send it to xDrip's slope. I have a test version of xDrip installed to find out the best slope setting of that raw value. I have find out that a fixed slope of 1.15 works best by now. What about a second version of the LimiTTer sketch which pre-calculates more agressive based on the last 15minutes? So you can decide oneself's favour.
— You are receiving this because you commented. Reply to this email directly or view it on GitHub https://github.com/JoernL/LimiTTer/issues/1#issuecomment-215394540
@holmberg81 I have one of this, will see if the code will fit the memory.
Not Enough IO? How many do you need? You can Drive the bm019 via uart like the hm10. An example lib can be found here https://github.com/SandraK82/bm019-library/blob/master/mbed/ble-bm019-uart/bm019.cpp https://github.com/SandraK82/bm019-library/blob/master/mbed/ble-bm019-uart/bm019.cpp which is not yet Ported to arduino.
On 28.04.2016, at 15:36, LibCGM [email protected] wrote:
@holmberg81 https://github.com/holmberg81 but I there is not enough GPIO's
— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/JoernL/LimiTTer/issues/1#issuecomment-215424838
Hello people, I write from Italy and I have a boy ten years old with diabetes. He use freestylelibre and I have many interest to build LIMITTER. Thanks.
@sean75 , you're welcome.
@all, the current code produces moderate readings. The next update will be more aggresive and faster in rising up and down - like the original reader.
for some reason it worked just once, xDrip receiving data from LimiTTer, do I need to stop/start if I test with another/different old sensor?
I use the HM-11 but will this work with HM-06 and BLE off?
@LibCGM , do you use Android 4.x and the BLE OFF circuit? BLE OFF only works with Android > 5. You don't have to stop/start a new sensor in xDrip. The LimiTTer will scan every sensor. If you program new code to the Arduino, it's best to hit "forget device" in system status and make a new BTScan + Connection. Not necessary to stop the sensor in xDrip. Yes, you can try it with your HM-06 and the BLE OFF circuit. Maybe you should increase sleep time a little bit for max power saving. But Android 5 or 6 only ;)
@JoernL I use Nexus 5 with Android 6, I will try today with HM-06, it is just BT 2.1.
I did all what you write with my current setting with HM-11, forget device, new BTScan etc, HM-11 ist connected but xDrip not receiving data, in console (on mac over USB) I see the BM019 reads the sensor.
still nothing, not with HM-06 or HM-11, in System Status says connected but noting received