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

Question: OPENBCI_BOP vs PCKT_START. Why? #86

Open
SeeJayDee opened this issue Nov 23, 2017 · 0 comments
Open

Question: OPENBCI_BOP vs PCKT_START. Why? #86

SeeJayDee opened this issue Nov 23, 2017 · 0 comments

Comments

@SeeJayDee
Copy link

SeeJayDee commented Nov 23, 2017

This isn't an issue, just a question. Not sure if this is the place to post it but anyway ---

Does anybody know - was there any particular rationale for using 'A' (0x41) as the packet header for streaming from PIC32 to RFDuino, but 0xA0 for streaming from RFDuino to PC?
The OpenBCI_Radios repo seems to cater for this difference of headers when relaying packets to the computer. However, if one connects a USB-serial bridge directly to the PIC microcontroller's serial lines, communication with the OpenBCI GUI or Python libraries is no longer possible, because the headers sent by the PIC are not what the computer expects.

In OpenBCI_32bit_Library_Definitions.h both PCKT_START (0xA0) and OPENBCI_BOP ('A') are defined, although PCKT_START is never actually used in the library.

My question is: is this usage just a carry-over from some miscommunication between PIC firmware contributors and Radio firmware contributors (maybe confusing "A" with "0xA0"?), or is there some special purpose?

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