Open nexulm opened 8 years ago
6 3 0 is a good idea, as I have no clue what happens when a new sequence overwrites a running one, but nevertheless this crash is a bug
It seems to occur only if you use the same CAN-ID. If I used another one the firmware doesn't crash and the command prompt is coming up. If the root cause isn't the same CAN-ID maybe the delay time was an issue!?!
Firmware init sequence:
No further command prompt and input command possible as firmware seems to be broken???
Maybe misuse do to "p 6 3 0" command should be performed before changing the delay time of the same CAN frame and content!?!