May be dropping signals from messages with too many signals

[peplin]

Discussion: https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/openxc/sX0P1IBssIs/REDLCUPL1o0J

[peplin]

The first step is to create a test that sets up 2 CAN messages with 8 signals each as in the example posted in the group, and see if it can parse all of them. If it works in a unit test, write a functional test to see if it's hardware-specific issue.

[peplin]

I wasn't able to reproduce this issue via USB, but I did find one problem when using UART (Bluetooth) on the reference VI:

{"timestamp": 1412909913.019663, "name": "signal1", "value": 5.7}
{"timestamp": 1412909913.020916, "name": "signal2", "value": 0.1}
{"timestamp": 1412909913.021835, "name": "signal3", "value": 16.4}
{"timestamp": 1412909913.025014, "name": "signal4", "value": 0.3}
{"timestamp": 1412909913.026139, "name": "signal5", "value": 8.1}
{"timestamp": 1412909913.028094, "name": "signal6", "value": 0.3}
{"timestamp": 1412909913.028597, "name": "signal7", "value": 5}
{"timestamp": 1412909923.24624, "name": "signal10", "value": 0.3}
{"timestamp": 1412909923.252771, "name": "signal11", "value": 5.2}
{"timestamp": 1412909923.25356, "name": "signal12", "value": 0.3}
{"timestamp": 1412909923.254341, "name": "signal13", "value": 20.200001}
{"timestamp": 1412909923.255105, "name": "signal14", "value": 0.1}
{"timestamp": 1412909923.262961, "name": "signal15", "value": 22.4}
{"timestamp": 1412909923.264086, "name": "signal9", "value": 17.9}

it's dropping signal8 and signal16, the last signal in each set of 8. That's not exactly what the original bug stated, but perhaps fixing that will fix the other problem too.

[peplin]

I belive I've fixed this - there was a race condition with UART on the LPC17xx where you could lose outgoing data. I wasn't ever able to reproduce it as seriously as in the original bug report (i.e. missing a full 7 signals from a message) but I think that's because I was sending the 2 CAN messages with some delay in between. I'll re-open this ticket if it's still a problem after the next release.