We have a Vortex on our shooter that doesn’t want to respond to commands when placed into velocity following mode.
Our shooter is comprised of 2 sets of wheels, one set of top and one set of bottom wheels. Each set of wheels are powered by one Vortex, with no gear reduction.
When placed into percentage vbus mode, the both motors work. When place into velocity mode, both motors work when first we launch code and trigger the shooter, but on a second time of triggering shooter, the bottom motor stops responding. The top motor is working. We believe something is causing that bottom motor to become responsive. The lights on the motor do not indicate anything abnormal. We think it might be because of a sudden change in command that is surging current or voltage that is causing the motor to become disabled or unresponsive.
Subsequent testing has shown that when the velocity command is slowly ramped up and down, the bottom motor is less likely to become unresponsive. But eventually, within 6 or 7 triggers, that bottom motor does become disabled.
The lights do not show a error in the CAN bus.
When the bottom motor is disabled, we will change gains and the motor will respond again but the motor is now spinning in the opposite direction.
We did re-assign the CAN ID of the top and bottom motor, keeping the code the same to test to see if the code itself was the issue. The bottom motor remained the motor that became unresponsive.
My sense is that the motor controller is malfunctioning and needs to be replaced. We have 2 spare and will be trying them out tomorrow. The motor is buried and wired fully into our finished robot. Is there anything else we can try to diagnose this?
REV support has been contacted but I thought I would poke CD to see if anyone had any suggestions.
Thanks