Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

small fixes to framework to be able to compile with sdcc 3.5.0 #21

Open
wants to merge 19 commits into
base: master
Choose a base branch
from

Conversation

savek-cc
Copy link
Collaborator

Some modifications from the most up-to-date original wixel-sdk in order to compile with sdcc 3.5.0.
The original current wixel-sdk compiles with sdcc 3.5.0 without issues.

@jstevensog
Copy link
Owner

Hi Timm,
I will not merge this into my repo just yet. I am still using the old sdcc and I don't want to break anything while I am working on the new channel scanning code.
I will try and set up a branch for sdcc 3.5.0 and pull it into there for now.
Later, once I have finished the coding and upgraded my sdcc, I can merge it in from that branch.
Thanks for the fixes.
Cheers

@savek-cc
Copy link
Collaborator Author

savek-cc commented Jun 1, 2016

Sure - if you want, I can give you a minimal diff to fix the non-matching function declarations (static vs. non-static). This way, only actually wrong declarations are fixed and the code could be compiled with sdcc 3.5.0 by removing the joystick app.

@jstevensog
Copy link
Owner

That would be great Timm.
I have downloaded the new SDK, will install it soon and give it a go. I
really should remove the other apps from my repo, but I left them there for
educational purposes. Still, a joystick app is probably not going to teach
you any more than the other apps ;).
The important thing for me would be for them to fix up the radio MAC code.
But I am doing that anyway.
Cheers

On Wed, Jun 1, 2016 at 5:29 PM, Timm Korte notifications@github.com wrote:

Sure - if you want, I can give you a minimal diff to fix the non-matching
function declarations (static vs. non-static). This way, only actually
wrong declarations are fixed and the code could be compiled with sdcc 3.5.0
by removing the joystick app.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#21 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AIQs8y5szCyY4zScbOl0IYVkYQsqXK21ks5qHTTQgaJpZM4Iq5UR
.

John Stevens
"You are how you live, not what you have."

@moimemecloud
Copy link

Hi everybody,
I am going to put up the xdrip classical version with a HM-10, I noticed that there is new devices added to the system - HM-1X ( Xbridge2!!), would you mind tell the functionality and the advantages of the Xbridge2, HM-1X please?
Thank you very much!
Best,
Moimeme

@jstevensog
Copy link
Owner

Hi Moimeme,
The classic circuit is deprecated (do not use, unless you are prepared to maintain it).
HM-1X means either a hm-10 or hm-11, so you can use the hm-10.
xBridge2 has the following advantages over the classic circuit and program.

  1. Dexcom transmitter ID is set in xDrip settings. You do not need to modify the source code, build, and load the app every time you change transmitter.
  2. monitors the bridge battery, displayed in xDrip.
  3. greater battery life. Turns off the HM-1x module when the wixel is sleeping between packets.
  4. LEDs can be turned off to save more battery.
  5. better packet capture algorithm.

The sleeping of the HM-1x module can upset some Android phones. You can tell xBridge2 to keep it powered on if this is a problem, but battery life will be impacted. Unfortunately, this setting and the LED setting must be set through a terminal connected to the wixel. A future version will allow these settings to be at from xDrip.

Hope this helps.
Cheers

---- KARIM AZZAZ wrote ----

Hi everybody,
I am going to put up the xdrip classical version with a HM-10, I noticed that there is new devices added to the system - HM-1X ( Xbridge2!!), would you mind tell the functionality and the advantages of the Xbridge2, HM-1X please?
Thank you very much!
Best,
Moimeme


You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@moimemecloud
Copy link

Hi John,
Thank you very much for your advice!
I have the HM-10, the Wixel, the Micro usb charger and the 2 metal film resistors - 2.2k 1/4w and 1/4 1/4w.
If I understood your message the Xbridge2 is a code update which can be downloaded from which website please, is it used and transfered via the Wixel Utility driver please?
Would you mind show me which longer duration battery should I buy please? I have bought a 3.7V, 500mAh but I think it won't last more than one day!?

Thank you very much for your help!

Kindest regards,
Moimeme

@jstevensog
Copy link
Owner

Hi Moimeme,
The xBridge2.wxl and xBridge2.pdf are located here.
https://github.com/jstevensog/wixel-sdk/tree/master/apps/xBridge2
Do not use the 2.2k and 1k resistors of the classic circuit. These are
also a source of battery drain. Read the xBridge2.pdf and use the wiring
and components there.

You will not need to change the battery you have, unless you want longer
than 3-4 days of operation. I use a 1Ah and 1,2 Ah batteries in my
production and development bridges. These last me a minimum of 5 full
days, and I have run them for almost 7 days in total before they go flat.
Cheers

On Sun, Jul 17, 2016 at 4:45 AM, KARIM AZZAZ notifications@github.com
wrote:

Hi John,
Thank you very much for your advice!
I have the HM-10, the Wixel, the Micro usb charger and the 2 metal film
resistors - 2.2k 1/4w and 1/4 1/4w.
If I understood your message the Xbridge2 is a code update which can be
downloaded from which website please, is it used and transfered via the
Wixel Utility driver please?
Would you mind show me which longer duration battery should I buy please?
I have bought a 3.7V, 500mAh but I think it won't last more than one day!?

Thank you very much for your help!

Kindest regards,
Moimeme


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#21 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIQs83i31w4h04tfXz8dGojPkSLtlz3gks5qWSbGgaJpZM4Iq5UR
.

John Stevens
"You are how you live, not what you have."

@moimemecloud
Copy link

Hi John,
Thank you very much for your guidance!
One last question about my data storage : can I use only the xBridge2 (xDrip)+ my Dexcom (sensor + transmitter) without using Nightscout cloud.
I have an Andoid smartwatch ( Moto 360 V2) and I installed Nightwatch and Xdrip applications( on phone+ smartwatch), and I would like to see my glycemic results ( glycemic fluctuations) on my face watch and record/store all my glycemic data directly on my phone micro SD card without sending/storing all the packets in the Nightscout Cloud please?

Thank you very much!
Best regards,
Moimeme

@jstevensog
Copy link
Owner

Hi,
I am not sure about how night watch and xDrip communicate, as I do not use night watch. I use a Pebble watch with the xDrip watch face. This definitely does not need a Nightscout site, and operated without any requirement for internet or cloud.
You would be best to ask that question in the CGM in the Cloud Facebook page.
Sorry I can't help with that.

My main focus in creating xBridge2 and the xDrip Pebble watch face was to ensure I could have my blood glucose readings on my wrist without the need for internet and cloud.
Cheers

---- KARIM AZZAZ wrote ----

Hi John,
Thank you very much for your guidance!
One last question about my data storage : can I use only the xBridge2 (xDrip)+ my Dexcom (sensor + transmitter) without using Nightscout cloud.
I have an Andoid smartwatch ( Moto 360 V2) and I installed Nightwatch and Xdrip applications( on phone+ smartwatch), and I would like to see my glycemic results ( glycemic fluctuations) on my face watch and record/store all my glycemic data directly on my phone micro SD card without sending/storing all the packets in the Nightscout Cloud please?

Thank you very much!
Best regards,
Moimeme


You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@moimemecloud
Copy link

Hi John,
So If I delete night watch and use the Xdrip app as a watch face on my smartwatch Moto 360 v2, is it feasible please?
Thank you,

Best,
Moimeme

@jstevensog
Copy link
Owner

No. It is not possible to run a Pebble watch face on an Android wear watch.
Cheers

---- KARIM AZZAZ wrote ----

Hi John,
So If I delete night watch and use the Xdrip app as a watch face on my smartwatch Moto 360 v2, is it feasible please?
Thank you,

Best,
Moimeme


You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@tzachi-dar
Copy link

What is the status of capture packets queue? I have built a new xbridge and really need this feature.

@jstevensog
Copy link
Owner

Hi Tzachi,
Sorry for the VERY long delay in responding. I am currently working on merging this into xBridge3, and adding the support to xDrip+. Hopefully will be done soon. I am currently out of a job, so have some time.
Cheers

@tzachi-dar
Copy link

Good to see that you are back with the community (although sad to hear that you are out of a job).

By the way, Issac, is working on a new board that should be much better than the wixel. He already have a prototype, and should have something better soon.

Tzachi

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants