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

Not an issue--trying to help #1

Open
benjsmi opened this issue Feb 22, 2015 · 0 comments
Open

Not an issue--trying to help #1

benjsmi opened this issue Feb 22, 2015 · 0 comments

Comments

@benjsmi
Copy link

benjsmi commented Feb 22, 2015

Hello @iphands ... I have ordered a CMS 50D+ (http://www.amazon.com/gp/product/B00B8L8ZXE/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1) and also am getting ready to hack it from a Debian Linux system.

Your write-up on your site (http://ian.ahands.org/progs/pulseox/) says that you aren't sure about how they are using byte 4 to represent pulses > 127, and similarly that you have "pins" or bytes that don't seem to make sense (byte 3).

I found this blog post, by a fellow tinkerer who is mostly complaining about the 5-byte protocol you describe, but in his complaining, he does a great deal of explanation about how the protocol for the CM50D+ works!

http://www.tranzoa.net/~alex/blog/?p=371

He even has a link to a PDF spec that he dug up from somewhere that indicates what each bit in the sequence represents.

https://www.tranzoa.net/~alex/blog/images/Communication%20protocol.pdf

Let me know if this helps at all.

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

No branches or pull requests

1 participant