COM_GET_VALUES truncates at 67th byte; thus excludes CRC and stop byte about bldc HOT 5 CLOSED

p.s. I traced the bldc source all the way to system function calls, and didn't see the problem - so if it really is a problem an the vesc side and not my side, it's someplace inside the OS buffering code I guess. I'm using hardware 410.

from bldc.

This is working over both USB and UART with the NRF5x chips, even with the 400+ bytes mc_configuration. I haven't tested with a higher baud rate though, and will give it a try.

from bldc.

I just gave it a try with a CP2102 USB-to-UART adapter, and 250000 works fine. 460800 also works perfectly, but 921600 is a bit unreliable.

Can you give it a try with a USB-to-UART adapter?

from bldc.

Thanks heaps for checking this (and sorry I wasted your time!!) - looks like the Arduino "serialEvent()" function is not really an event, but an end-of-loop-poll, so I expect the fault is on my side after all!
At least this mistake found another bug that's now fixed though, right?

FYI - I'm building an open-source full-feature remote and motor-orchestrating-controller with emphasis on safety, so skate-board-riders (and others) in future can save battery by "phasing out" unused motors under light load, and not experience cut-outs or brake failures on low-battery or other faults, etc...

from bldc.

No problem, and as you said it is good that you found the other bug which is fixed now :-)

from bldc.