I'm testing a NodeRed (1.2.7) Flow with data from an acceleration sensor with 2000Hz. The custom sensor-node has several outputs, which deliver data for acc_x, acc_y, acc_z.
The sensor sends data packages of 16 values per axis every 8ms. The packages get unpacked and send individually over the node outputs.
So something like:
send first value
send second value
send third value
send sixteenth value
next 16 values
it seems the nodes after the sensor node get overrun in a strange way. For the output that sends data first over the first registered connection to a next node, the next node (for example a file node to check the values) receives 16 times the 16th value. But if the same output is also connected to another node, this node receives values 1-16...
2khztest1 displays 16 times value 16
2khztest2 displays values 1-16
2khztest3 displays values 1-16 for the 3 joined messages from acc_x,y and z
it also seems to make a difference which node i connect first to the output. so if i connect accelerationx first, 2khztest2 will display 16 times values 16, if i connect 2khztest1 first it will behave as explained above.
I believe it isn't an issue with the custom node because NodeRed is able to get the correct values of the same output.
Did something like this occur to others? It just happens at high frequency, same flow with 10 Hz has worked fine. Are 2000Hz too much for NodeRed?
Thanks in advance for your answers