Open CoryNessCTR opened 1 year ago
I've seen this behavior with CAN Spark Maxes too since at least 2020 (C++). I can't remember past that.
It looks like this is caused by slow initial string concatenation in java, combined with MotorSafety being enabled by default on the drive classes. The string concatenation blocks the thread on the first invocation, which causes MotorSafety to time out and disable the motors.
Describe the bug The first time you DS-Enable (after power-cycle or code deploy), the motors drive for a split second before disabling for about a second, then resuming. Subsequent enables do not reproduce this.
To Reproduce Steps to reproduce the behavior:
Expected behavior Motors should not disable-blip
Desktop (please complete the following information):
Additional context Issue originally reported in CD thread https://www.chiefdelphi.com/t/canivore-stops-communicating-with-devices-after-first-enable/425891