We have four spark maxes connected to neos for a test drivetrain and they keep blinking blue or blinking magenta which according to the documentation means no signal. There are no can faults according to the driver station. We’ve checked the can bus wiring and we know for sure that they are connected right. No matter what we try the same issue persists. One thing to note is that when we plug in the usb into a motor controller the only electrical components that show up on the client are the pdh and the motor controller itself.
Edit. After testing a bit more the fault just disappeared but we’ve identified a new problem. When we try to identify the motor controllers all of them start blinking. We’re assuming this is because of all motor controllers having the same can id but we’re unsure how to change them as we only see one motor controller (the one which is the usb is plugged into) in the hardware client.
We have seen an issue where spark max’s show gate driver faults when not powered by a battery, and just connected to USB C. That screenshot with the rev client, is the spark max powered via battery? If so that could be a red hearing.
Yes the spark max was powered by a battery. After testing a bit more the fault just disappeared but we’ve identified a new problem. When we try to identify the motor controllers all of them start blinking. We’re assuming this is because of all motor controllers having the same can id but we’re unsure how to change them as we only see one motor controller (the one which is the usb is plugged into) in the hardware client. I’ve edited the post to reflect this development
You’ll to have robot powered off, unplug the Spark MAX from the CAN bus, and then change CAN id and click burn flash. You should repeat this for all of them while the robot is powered off.
