Econotag Network byte order issues

ProjectRipple / Mock-Ripple-Device

Code for running Ripple devices in simulation

0 stars 0 forks source link

Econotag Network byte order issues #2

Open adamrenner opened 10 years ago

adamrenner commented 10 years ago

(for econotag) 0x4000 is appearing between the header and sequence values of every message I've observed. Those are the real extra bytes in the message.

Example: ECG data stream received from aaaa::205:c2a:8c92:f828. d214 4000 0000019f [samples]

ECG data stream received from aaaa::205:c2a:8c92:f828. d214 4000 000001a0 [samples]

JWest126 commented 10 years ago

This was worked around in commit 1c845441d1e9438a24047e78b973804cf618c2c1 by adding these phantom bytes to the ripplecomm_ecg struct. This lets us address these bytes on the econotag and adds them on other platforms so that the message is consistent between platforms.