We are fighting an inconsistent SparkFlex Neo vortex issue and I wondered if anyone has solved this one, or if we should replace the motor. It seems to be two of the same motors.
We have the latest firmware in the SparkFlex.
When we power up sometimes or it actually happens more after a fresh code deploy, sometimes we get a Sensor fault on a SparkFlex as shown below, it’s not resetable until a power cycle, then it operates fine.
After we power cycle, the problem goes away on it’s own. We also get some error on deploy sometimes, previous to this behavior. Is this a solved issue or a known issue?
We’ve just encountered the same problem today. The SparkMAX was showing a Sensor Fault while connected to the Vortex. After substituting encoder wires, Sparks, and Vortexes, we found that the connection between the Vortex and Adapter (we used a Solo Adapter) must have experienced a misconnection. However, we could not find the exact misconnection. We just switched the Vortex and the Adapter after testing different Vortex/Adapter and Spark combos.
We are also going through this problem. I would like to say every single one of our vortexes has undergone this problem at least once. We are yet to find a solution.
The Vortex and Flexes in the photos CAN ID 4 and CAN ID 2, we replaced them. And so far…I have not seen any more issues with the sensor error in Rev Client. (knock on wood)… I have not heard back from Rev support after a couple of emails, so I don’t have any advice to give what they said other than replace the motors if you have some spares like we did at this point.
We are having this issue with a Vortex/Flex combo and submitted a support ticket but haven’t heard back in 2 days now. Hopefully there is a firmware fix being worked on.
Check to see if the docking connector for the sensor signals might be loose or misaligned. Half of this is on the motor, the other half on the controller. If those connections are intermittent, it could cause a sensor fault. And, it would be tied to a specific motor and/or controller.
Due to this problem only occurring when the Rio boots up, it inclines me to not think it is entirely an electrical fault. @Chris_Elston explaining that a new flex fixed the issue is slightly concerning, as that means we may need to get a bunch of replacement Flexes in the near future. We will take a thorough look at our wiring tomorrow, however.
I’ll get back to you when we do some more testing, but currently this is happening to us right now, its persistent across multiple spark flex + vortex combos. We are gonna try downgrading firmware and a few other things right now.
This has also happened to us 4 discrete times in 2 days, each on a different SPARK Flex. We are skeptical of a potential firmware issue here (especially given the recent changes to REVLib w.r.t reading encoder data), as nothing has changed electrically. Power cycling the controller fixes the fault, without touching the motor itself. We also have URCL running (trying to see if that’s a common variable) but I don’t think it’d be able to interact directly with the SPARK Flex.
We also had an issue with sensor faults on the spark flex. Our problem presented itself as the motor being fine on boot, but encountering a sensor fault if code was deployed, even when that robot code was identical to what was previously deployed. We tested extensively with spare motors, checking the can bus, (this is the only device on it besides the termination resistor in the PDH) updating the firmware to version 24.0.5, and running the motor from rev hardware client with no clear answer as to what the problem was. However, we noticed this issue only presented itself after we had switched from revlib 2024.2.0 to 2024.2.3. We were able to resolve it by downgrading our REVlib version back to 2024.2.0. We ran about 7 hours of robot practice today with zero issues. I believe our motor firmware is currently at 24.0.4.
We also experienced this for the first time yesterday. On 1 of out sparkflex’s, it happened twice. It also didn’t appear until after we upgraded to RevLib 2024.2.3 but still dont know if that’s coincidence. The sparkflex should be on the latest firmware but need to confirm that
Team 4453 at FIM event experienced sensor fault occurring on enable. It appears to follow the CAN Id. We took the advice and downgraded revlib from 2024.2.3 to 2024.2.0 and so far it has resolved the issue. We made it to finals on three wheels. Ugh, and, Thank you.
Same problem for us at northern lights. Two of our six vortex flex combos would boot up sensor fault and only a power cycle would solve it. We had to train or field placement members to check the status lights on field boot up.
