Talon SRX Firmware 2.0 Problem Encountered

[Beaker]

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?

[ozrien]

There are no known limitations upgrading from 1.4 to 2.0. You should probably send your code and explanation of your setup to support@crosstheroadelectronics.com

[pribusin]

Are you using CAN or PWM to drive the Talons? If you use CAN you may need to re-address them. Check the GUI on the RoboRio for proper device IDs. We've not upgraded ours yet but I know sometimes a f/w upgrade can wipe out configuration data.

[ozrien]

A firmware update should not cause any settings to reset. See section 16.20 in the Talon SRX software reference manual.

[Beaker]

Originally Posted by pribusin

Are you using CAN or PWM to drive the Talons? If you use CAN you may need to re-address them. Check the GUI on the RoboRio for proper device IDs. We've not upgraded ours yet but I know sometimes a f/w upgrade can wipe out configuration data.

We are using CAN, but the Device IDs stayed the same. It was interesting, because there were no CAN errors when diagnosing the issue.

Originally Posted by ozrien

A firmware update should not cause any settings to reset. See section 16.20 in the Talon SRX software reference manual.

It didn't seem like the settings reset, everything stayed the same except for the firmware version.

[system201]

Our Team Updated And Everything Went Nicely...

We Found Our Image Here

http://www.ctr-electronics.com/talon...ical_resources

[sraque]

Are you using the standard Talon VI's or your custom ones? I know you had a folder of your own custom VI's in the code release.

[ozrien]

Hey All,
Bringing this thread to a close: root-cause is the LabVIEW team project had forked implementations of some Talon-centric VIs, but not all. The VIs were forked for performance reasons. So updating to 2016 meant the application used some old (forked) VIs and some new VIs, effectively breaking Talon-use.

I generally recommend to teams to always use the stock Talon VIs - BUT, if you REALLY need to make changes to be successful, you should kit all related VIs so future RIO updates don't lead to a mixed bag of things.

[pribusin]

Originally Posted by ozrien

Hey All,
Bringing this thread to a close: root-cause is the LabVIEW team project had forked implementations of some Talon-centric VIs, but not all. The VIs were forked for performance reasons. So updating to 2016 meant the application used some old (forked) VIs and some new VIs, effectively breaking Talon-use.

What do you mean by 'forked VIs'? I'm not familiar with that term.

[Arhowk]

Originally Posted by pribusin

What do you mean by 'forked VIs'? I'm not familiar with that term.

It meant that OP copied over the source code of the can talon.vi and edited It.