Next steps

MATLAB

Now that the coordinator is receiving the packets, how do we read them in Matlab?

1. Start with the RPI Matlab code
1. Count how many bytes to get to the data
2. Display data values - are they hex, string, uint?
3. Convert 4 bytes to float for x,y,z, a_x, a_y, and a_z
2. Plot in real time

More XBEES and BNO055's

1. Add another sensor/xbee/arduino combo
2. Do we see multiple RX frames in the XCTU console?
3. Interestingly, it doesn't seem to matter the DL setting on the coordinator.  That's nice as we can send a message to multiple end device xbees at once.
4. Will our BNO055's always be close to each other?  If so, the delay in receiving the signal to start from the coordinator should be negligible.

Reading from sensor

1. Google tells me that Series 1 xbees have a 100 byte buffer.  If we read the sensor once, we have an API packet that is 29 bytes:  5 + 24 bytes of data.  Therefore, we can only read the sensor 3 times for each API packet.  Can we squeeze one more byte in there to get 4 reads per api frame?
2. Do we want to consider using the I/O frames instead of the TX/RX frames?  Do the I/O frames have fewer than 5 extra bytes?
3. I have a delay of 100 ms in void loop in the arduino.  How fast can we go?
4. Can we minimize the arduino code to decrease clock time between reads?
5. De we really need the x,y,z values as often as accel values?