PeterH:
yan5619:
Thank you for your swift reply.
I need a real time monitoring GUI, that is why I am streaming the data over the serial port (via Bluetooth) into Processing (and then plotted into a graph).The term 'real time' means different things to different people. What does it mean to you? What sort of update frequency and latency are you trying to achieve? How much data needs to be transferred at each update? If you are only displaying the values on a screen then you can probably afford to update them considerably slower than 100Hz. In that case you might want to separate the sensor handling code from the output code so that you can perform them at different frequencies - you probably want to do your inertial extrapolation as frequently as possible to minimise cumulative errors and you don't need to pass all that data through the bottleneck of your serial port.
Please allow me to explain my project.
It is a wireless inertial sensor network as mentioned on the first post, with three acce/gyro sensors.
I need a data sampling rate of at least 100Hz, best if 200Hz can be achieved.
After collecting the data from the sensor, it should be streamed to my computer (which within my limited knowledge, serial port would be the way), and displayed on the screen by plotting a graph (by using Processing, the only program I am a little familiar with). Furthermore, for analysis purposes, the data that is streamed to my computer must be logged, therefore 100Hz-200Hz is still necessary.
The frequency will be fixed, so any frequency from 100Hz will be fine.
Finally, each sensor will output 6 sets of 2 bytes data (ax,ay,az,gx,gy,gz).
Thank you.