stephenblackwasalreadytaken/wixel-xdrip

Allow a wixel to function as Dexcom Reciever

wixel-xdrip's Issues

sdcc El Capitan

Should be /usr/local...

fault during compiling apps in command prompt

sorry for my english, but i have problem with compiling apps for wixel 1337.
please look to my topic in polish forum with that problem
thanks in advance
link:
http://www.elektroda.pl/rtvforum/topic3098109.html#15050102

What are acceptable values of the elements of Dexcom_packet?

Trying to test my Wixel without a transmitter, so I'm using another Wixel to send it a packet that looks like a Dexcom_packet. Except I'm not really sure what values to use to make a realistic simulation. Any references you have on the subject would be very helpful.

Buffer missed packets

It'd be nice to improve the wixel->bt->phone comms to buffer dexcom packets that are received by the wixel, but missed by the phone.

Port wixel-DexDrip onto Android phone's native bluetooth chip...

If the wixel-DexDrip packet receiver ran natively on the Android phone's own bluetooth receiver, then the Wixel hardware could be eliminated and DexDrip would be available to a much broader audience. Would this need to be done in Android/Linux bluetooth driver land?

Parakeet - data roaming problem

We are using Parakeet for almost a year without any problem with the EU gprs roaming (we were several times in Slovenia, Italy without any data roaming problem ) but on our last trip - last weak we had the huge problem with the EU data roaming (nevertheless, sms worked normally). I am not sure that the general problem started exactly last week (we are not traveling so often) but we noticed the problem last week on our trip to Slovenia, Austria and Germany. The problem was that when changing a country (roaming to a new country) the parakeet could not initially connect to the internet in any new country, although there was NO problem with the ISP money/account/subscription - that was 100% ok. The problem could be resolved only by taking out the sim from parakeet and inserting the sim in the regular smartphone and than start the phone with the parakeets sim inside and then put the sim back to parakeet. After that everything started to work again. That was repeated each time we changed a country and there was no solution beside mentioned dismounting the parakeet, taking out the sim, putting it in the smartphone and starting the smartphone with that sim inside and then put the sim back to parakeet, when all starts to work without problem. So, to sum-up, after changing a country it is impossible to use the internet on sim in the parakeet without first starting that sim in the regular phone.
My understanding is that the parakeet can not accomplish some "new initial procedure" that is required from the GPRS operators and after "that procedure" is accomplished using any regular smartphone (but unfortunately not the parakeet itself) the GPRS internet starts to work normally (even in the parakeet), until you change that country. To be sure, I tried with 2 different sim cards (I have the reserve one) and the issue was exactly the same. When we turned back to home county everything worked without the problem (taking out the sim from parakeet was not necessary any more). This is probably because it is the home country of the sim. Any help would be very appreciated!

Compile Issue

I'm getting compiler errors when using the makefile on Ubuntu 16.04 LTS.
The code is the latest from the master branch as of February 12, 2017.

make error:

Compiling libraries/src/usb/usb.rel
libraries/src/usb/usb.c:292: error 146: two or more storage classes in declaration for 'usbStandardDeviceRequestHandler'
Makefile:172: recipe for target 'libraries/src/usb/usb.rel' failed
make: *** [libraries/src/usb/usb.rel] Error 1

SDCC -v output (in case it's useful):

SDCC : mcs51/z80/z180/r2k/r3ka/gbz80/tlcs90/ds390/TININative/ds400/hc08/s08/stm8 3.5.0 #9253 (Mar 24 2016) (Linux)
published under GNU General Public License (GPL)

A little guidance?

I have to say I am absolutely impressed with all they people working to make living with diabetes even as little easier.
My wife was diagnosed Nov 2014, she just got her Vibe pump with built in G4, no share, we don't have that in Canada. I have to use xDrip Wireless bridge add the receiver did not come with it ($700 to buy). My question is this, will I be able to check her bg if I have set up installed on my phone? Do I have to set up Night Scout in order to view the cgm on pebble watch? I have been searching all over and I haven't found the answers yet. This is what I am hoping to have accomplished after building the bridge:
Wife can check her bg on phone or pebble
I can check her bg on my phone or my pebble

Is the bridge the only thing I need paired with the app?

Thanks for your help in advance.

Cant pair with bluetooth

The device shows up at BT05 on my phone and when I try to pair with it I see "Pairing rejected by BT05".

I'm using code from master as of right now, the only thing that is different to the specs is teh bluetooth module is the CC41 instead of the HM10 however it sounded like the code now supported this?

Any ideas here, do I have to try and flash the CC41 or do something else?

It all appears to be working with LEDs blinking etc on both the wixel and the ble module but I just can't pair with it.

Voltage mensurement not showing on Nightscout

I did modification that was discribed, and can not find data for battery. I do have data for uploading mobile, bit not for xDrip instalation.
Should I make some modifications in Azure, or what am I missing.
Thanks

Caching sensor readings

Would it be possible to implement some sort of sensor reading cache in the wixel part of this system? I know there is a cache in the xDrip App, but it would be really nice to have a cache in the wixel as well. This would (at least for me) improve the reliability of the system, not to be dependent on having two devices attached to my 4 year old at all times.

I know such thing might increase the traffic on BT and thus decreasing battery life, but being a software engineer myself I know there are ways to make such cache pretty efficient.

xdrip usb only

Is it possible to connect the xdrip to either a pc (windows) or a raspberry pi and have that upload the data to nightscout, I have plenty of pi's and a few pcs that i use during the day I'd like to have a wixel wifi mesh working with without having to go out and buy android mini-pcs.

I'm not 100% sure how nightscout operates, can it accept just the raw data that is read from the wixel or does it have to go through some processing in xdrip first?

I guess I could write something to read the com data that is sent via usb when connected but it seems like someone might of already done this, I'm just having trouble piecing the various pieces of peoples work together.

Disable usb support if usb is unplugged

Using if(usbPowerPresent()) instead of the previous constants should do the trick

thanks for the setup steps

Thanks for the setup steps!
Looking forward to trying this.

Dexcom transmission

How is the dexcom transmitter sending its values over the air, ant/bluetooth etc? Is there any guidance on frequencies etc

MAKE error

I have never compiled a C program and the make command is giving me an error:

Compiling apps/dexdrip/dexdrip.rel

(null):2: syntax error: token -> ':' ; column 2
sdcpp.exe: fatal error: when writing output to : Invalid argument
make: *** [apps/dexdrip/dexdrip.rel] Error 1
You may now close this window.

Any help getting my Wixel code compiled would be appreciated.

Receiving very large numbers for dex_(ppkt->raw)

Using the wixel as the receiver, I have been getting very weird numbers for my glucose values. My settings:

• RTS/CTS hardware flow control
• \n termination char
• baud rate of 9600

I added another part to print_packet that shows ppkt->raw. So my output is: 'ppkt->raw dex_num_decoder(ppkt->raw TRANSMITTER_BATTERY WIXELBATTERY'

A couple readings and their associated G4 values:

98: n/a 117888 215 0
89: 36298 141920 215 0
86: 19848 148000 215 0

Am I just not interpreting the values right?

Help with Wixel app

I built my Wixel and soldered everything, connected the battery and to my surprise it started lighting up! I connected to my Mac and the Wixel configuration utility even recognized it! Wow this going to be easy.... but for the life of me I can't build the app. The command to install sdcc didn't work so I found a command that did and install it.
When I run the make command I get:
Russs-MacBook-Air:wixel-xDrip-master russ$ make
Compiling apps/dexdrip/dexdrip.rel
apps/dexdrip/dexdrip.c:43: syntax error: token -> 'FHMT' ; column 56
make: *** [apps/dexdrip/dexdrip.rel] Error 1

I'm pretty sure more files were put in the Dexdrip folder, but no app.
Any thought would be appreciated.

Where is the wixel in the data abstraction?

Is it transmitter -> BLE receiver -> wixel -> usb -> computer?

Or is it transmitter -> wixel -> BLE transmitter -> android -> xDrip?

Is it possible to have the packets be read into a computer instead of an android phone?

BLE stopped working

I built an wixel-xDrip a few weeks ago and it has been working with no problems. Yesterday all of a sudden it seems like the bluetooth module stopped working. I have an HM-10 hooked up to it. Is there anyway to troubleshoot the BLE device (bootup, errors, etc.) before I just scrap it and buy another one?