So we have everything updated, from what I can tell. Talon’s are at 3.3, used the latest phoenix installer to update the roborio, everything looks good on versions from what I can tell.
We copied over the arcade drive example from the ctre example’s, but nothing’s happening… we tried to control just a single controller using controller.set, but nothing. We plugged in an old victor over pwm using the same code and it worked just fine. So I’m looking for suggestions on what to check next? I’ve walked through all the documentation, examples, and what not, but something still isn’t right. Anyone have any clues? Thanks!
The lights don’t change when the motors are supposed to move… I believe it is just the steady flashing amber light. (I’m not in front of the robot anymore, so I’m probably getting the color wrong, but it’s the usual steady flashing when nothing is moving)
The talon’s were working yesterday. This morning the rio was updated to the latest firmware and that’s when things stopped working. After the rio was updated, the can libraries were reinstalled to the rio, not sure if we missed something else in that process.
And I may be getting the color wrong… we can see all 4 talon’s in the web interface and run the self test on all 4, everything comes back good. They do show as enabled in self test when the robot is enabled. We did run the phoenix lifeboat utility, it said everything was good on that end.
Yea, that’s kind of what we did… the code I posted above was using the arcade drive function, but we tried it with calling the set function on one of the talon’s as well. Same result At this point, I might just reset the rio and start from scratch, maybe something got messed up on it.
We had a similar problem to this, but if you held down the joystick for long enough, it would accelerate.
We were doing configOpenloopRamp(60, 0) on each of our motors, and the 60 used to represent the amount of volts the motors would ramp up each second. But it was changed to be the amount of seconds the motor takes to go from 0 volts to max, so our motors were accelerating very slowly.
Changing the 60 to 0.5 solved our problem
So we’ve narrowed it down to a problem with our talon’s… we have 2 new talons that we got through first choice this year, they both work fine. The 4 talon’s we got in the off season won’t work. All 6 were flashed to the same firmware version using the same firmware file… the 4 were flashed when they were all connected together, the 2 new ones were flashed when they were the only device on the can bus. So our first step today is going to be reflash them and assign new id’s one at a time. Unless there are other suggestions? From what I can tell, all 6 are the same hardware revision…
It beats me… the motors wouldn’t run. We ran the process where we held the little button down as we applied power, the lights flashed green, then we left off the button. Reflashed the firmware and everything started working after that. Just flashing the firmware alone didn’t fix things, it was only after we did the reset procedure.
Ah, gotcha My student was doing most of the work, I was bouncing around between things, I thought I heard something about calibration, so I figured that’s what it was they did. I’d still be curious as to what we did to begin with that caused them to do that, but we’re back up and running now, so it’s all good. I appreciate the help looking into things
One possible reason for the Talon SRX not working is that you had limit switches enabled with normal close on the Talon possibly from previous season. It bite us a few times. We had repurposed Talons from previous year that were used in an elevator which had upper and lower limit switches to our drive train and the robot was not running. After some debugging, we found that the limit switches on the Talon was enabled with normal close, so without the limit switches connected, the motor will not run.