We can run all Falcon 500s, no problem or any other mix of motors, no problem. but when we try to run Falcons on the same robot with Talon-controlled motors, we get an “Inconsistent Firmware” message.
I’m pretty sure our programming team uses the latest firmware available.
Has anyone else experienced this problem?
Are you referring to the entry in the Driver Station version list?
If so, this is a side effect of both controllers (Talon SRX and Talon FX for Falcon) being “Talons”. When the devices are detected on the bus they’re both interpreted as ‘Talons’, and since the firmware versions are different (latest firmware version for SRX and FX are not the same) it’s reported as “inconsistent”.
This does not affect the functionality of the devices at all, it’s just an issue with the message in the DS. This may be something we can fix in the future but no ETA on if or when that will happen.
If you look at the devices in Phoenix Tuner they will appear as separate, correctly labelled devices as normal.
Yes, it’s working OK, but we were worried an overzealous inspector might not like seeing that error message.
The manual hasn’t required a minimum firmware for a few years now.
There has never been an item on the checklist to look at the DS logs, inspectors should not be worrying about what’s listed there. Aside from helping teams to debug issues when the CSA’s were all busy, I haven’t even looked at the logs.
We are experiencing the exact same thing. This seems to pop up randomly and everytime it does, we have to restart our robot code.
It’s not in the logs. It’s part of the diagnostic tab where all firmware versions are listed, with the roboRIO image version (which I’ve never had an inspector not check).
From 2015 until I believe 2017, Talons had a minimum firmware version listed in the manual that was also checked. If the Talons do not all match, it says “inconsistent firmware” instead of a version number. Under the old rules, that’d be a problem, even if everything was legal.
Under the old rules, if it said inconsistent firmware, inspectors were supposed to check each speed controller individually on the web dashboard, and ask a CSA if they needed help. Although it certainly made it easier for the inspectors if there was a single version shown on the diagnostics tab.
What Omar describes shouldn’t pop-up randomly and shouldn’t be fixed by restarting robot code, nor should it cause any operational problems.
Don’t do that. As others have pointed out, the “inconsistent” DS message doesn’t matter. You can ignore this. Use Tuner to confirm firmware versions once and move on.
Will do. I got a similar (but different) error message in the DS logs and if I can reproduce it later today, I’ll create my own thread about it and mention you.
If you want fast answers, contact support email (http://www.ctr-electronics.com/contacts-us).
That goes to the entire team, including me. I don’t check CD at a consistent rate.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.