Hi.
I’m having trouble with updating the SparkMax controller to the new firmware.
I am using the new Rev SparkMax Client (ver 2.1.0) and I can’t even connect to the controller.
the Client shows me one of the two errors:
“Device ID 20524 does not match any of the 0 devices currently found”
something about the backend server.
When I installed the Client software one of the two drivers failed to install:
I don’t know if it is the cause of that but I mentioned it anyway.
We ran into the same thing last night. Students completely uninstalled the prior version of SmarkMax Client, then reinstalled the new version. Worked fine after that. Good luck.
We got the error you listed the first time when the old version was till there, and couldn’t connect to any of the controllers. We we reinstalled the 2nd time we didn’t get the error message you are showing about the drive not installing. The client worked that time. I don’t know if that was the actually problem, but that was our experience.
We had that issue last night as well. We had some success after (not necessarily in this order):
Restarting the computer
Double checking firmware on PDP, rio, etc. was up to date
Checking CAN loop was complete and correct
Powering off the robot while updating firmware (target Spark Max received power from the USB-C)
Running the Rev client as an Administrator
Disconnecting CAN from the target Spark Max
Having the computer running Rev client connected to the internet
We also found it seemed to work better if the client was closed completely between updating Spark Maxes. So update SM 1, disconnect SM 1, close client, connect SM 2, update SM 2.
Not sure which, if any, helped with the problem, or if it was just chance, but eventually we got all Spark Maxes updated. Once they were all on 1.5.1, we were able to reconnect CAN, power-up the robot, and see all SparkMaxes on the CAN network (and configure them) simultaneously from the client largely without issue.
Unfortunately we didn’t have the time (or desire) to figure out the root cause. Our hope is now that they’re updated we won’t encounter this issue again.
