Beaker
24-01-2016, 11:11
Yesterday when we were testing some motors on our offseason testbed, we decided that we wanted to update our Talon SRX motor controllers from v1.4 to v2.0. The update went fine, we connected to the roboRIO web interface and loaded the firmware located in C:\Users\Public\Public Documents\.
However, after we tried driving the bot, the drivetrain would either stay stationary, or only one side would move (it was not always the same side). At first we chalked this up to a programming error, but after disabling all the code that was not pertinent to the drivetrain, the behavior continued. I reverted to last night's code and even our Feed Forward Code that we developed in the offseason, both of which worked wonderfully the day prior, but to the same effect. Of course, we restarted all the things (LabVIEW, Computer, Robot), but that did not work either.
Only after reverting to v1.4, were we able to get the desired behavior from the testbed.
Is there something wrong with the way we updated the firmware, or is there a known issue with v2.0 that we missed?
However, after we tried driving the bot, the drivetrain would either stay stationary, or only one side would move (it was not always the same side). At first we chalked this up to a programming error, but after disabling all the code that was not pertinent to the drivetrain, the behavior continued. I reverted to last night's code and even our Feed Forward Code that we developed in the offseason, both of which worked wonderfully the day prior, but to the same effect. Of course, we restarted all the things (LabVIEW, Computer, Robot), but that did not work either.
Only after reverting to v1.4, were we able to get the desired behavior from the testbed.
Is there something wrong with the way we updated the firmware, or is there a known issue with v2.0 that we missed?