![]() |
Problem With Talon SRX Enabling
Hello, I am Lord Supreme Programmer at Team 1410, and I need some help with a rather large problem. We are currently testing out our electronics board and we have found that if we connect through USB and enable our robot everything works fine and all of the 14 Talon SRXs change from flashing orange to solid, but when we connect over Wi-Fi and enable the robot only 8 random Talon SRXs will change from flashing to solid, the rest will stay flashing, which is a huge problem. Does anyone else have this problem/does anyone have a way to fix this?
|
Re: Problem With Talon SRX Enabling
Sounds like a cabling issue that has revealed itself after you started driving it around (on WiFi).
Or the robot is genuinally disabling due to network packet loss. Check the driverstation for packet loss. Did you update the talons to 1.1 or greater? |
Re: Problem With Talon SRX Enabling
Quote:
|
Re: Problem With Talon SRX Enabling
Can you post a picture of where you have the D-Link mounted? It's a radio and is susceptible to interference from nearby motors, wires, speed controllers, and switching voltage regulators, as well as simple metal structures.
|
Re: Problem With Talon SRX Enabling
1 Attachment(s)
Quote:
|
Re: Problem With Talon SRX Enabling
Quote:
Quote:
|
Re: Problem With Talon SRX Enabling
Quote:
|
Re: Problem With Talon SRX Enabling
What program language are you using?
What happens if you start with 7 talons enabled and then add one at time and verify that they work? I didn't see or understand, does using an ethernet cable behave the same as using the usb cable ? Also, when you switch to wi-fi, make sure you have all the other network inter-faces disabled. Also, do you have an another wi-fi network interfering with your wireless? You can use a network display tool to see how many wi-fi signals are around you. |
Re: Problem With Talon SRX Enabling
Quote:
|
Re: Problem With Talon SRX Enabling
When I said disabling the Talons, I meant within the software -- just define a limited set to initialize and use. I did not mean removing them from the electrical connections.
|
Re: Problem With Talon SRX Enabling
When you send a picture, please make sure there is a good view of the power wiring between the radio and the VRM.
Please also send a screen shot of the driver station log viewer, showing a run of the robot where you're experiencing the problem. There's nothing wrong with using Ethernet to program the roboRIO. I do recommend connecting the tether to the radio, rather than directly to the roboRIO, so that when someone trips over the tether it wrecks the cheaper device. |
Re: Problem With Talon SRX Enabling
Have you gone on the webpage for the roboRIO and ID'ed the Talons properly? If you go there and you have less than 14 Talons on your left sidebar, they aren't ID'ed properly. Also try opening the error log while testing.
|
Re: Problem With Talon SRX Enabling
To the last three posters:
I will do that instead of removing them physically. Pretty sure I just heard my electrical engineer sigh with relief. Also the problem with using an Ethernet to connect to the roboRIO to deploy code is that if it's the first time connecting drivers will not be automatically installed. I have had this happen multiple times. And, just to be fair, 80% of our deploy problems went away when we switched to USB, so I think it's safe to say USB is the better option. The picture I sent was a hand drawn screenshot at 2AM, and I am also not an electronics guy, so sorry there is no wiring. I know it is a standard router is plugged into the VRM, I think that's what you called it, through the included power cable that has been cut. For the driver station I do not have a photo right now, but I will tell you that usually we get 70% packet loss for the first 10 seconds or so and then it holds steady around 20% loss. This does not change based on router. We have ID'ed each Talon properly, many times. If we had any conflicts then they would be flashing red. We should probably try connecting the roboRIO WebDashboard through WiFi, but have not done so yet. And to all people trying to help, just to be clear: all Talons work when tethered through USB. It is only over WiFi that 6 out of 14 Talons will stay blinking while Teleop is enabled, the other 8 turn solid and will drive. Thanks for all the help. |
Re: Problem With Talon SRX Enabling
Your computer should not have to install any drivers to get working with the ethernet. If it does you should install the drivers for your ethernet adapter or get a working usb ethernet dongle.
If you are having issues with your ethernet port, you will need to get them fixed, or you will not be able to control your robot because you will not be able to connect to the field at competition. |
Re: Problem With Talon SRX Enabling
Quote:
|
Re: Problem With Talon SRX Enabling
Quote:
|
Re: Problem With Talon SRX Enabling
Oh! I just remembered what we figured out yesterday! The only Talons that enable during the Teleop over WiFi were the ones used in a command that is set as a default command. We have verified this by changing the default commands and the Talons do switch around. But for us this is not feasible as then the only command for an elevator moves it up and we can't have it constantly moving up.
|
Re: Problem With Talon SRX Enabling
Quote:
|
Re: Problem With Talon SRX Enabling
This seems like a programming problem then.
Just like PWM, you need to tell every speed controller what speed it should be running at all the time. Even if the speed is zero, you are responsible for continuously updating every speed controller. |
Re: Problem With Talon SRX Enabling
Quote:
|
Re: Problem With Talon SRX Enabling
Quote:
|
Re: Problem With Talon SRX Enabling
Quote:
The short story: 2 of our SRXs wouldn't enable with the rest of them. One was in follower mode, the other in closed loop (but wasn't the master of the follower). This only happened when the robot was power-cycled. If we, like OP says, restarted the robot code, all SRXs enabled as expected. It was repeatable for the code we had at the time. We had to make some changes and the issue disappeared. (Un?)fortunately it went away before I could fully debug it and didn't get a commit at that point. I know it kind of stinks, but our workaround was just to restart the code whenever we power cycled. That reliably fixed the issue. |
Re: Problem With Talon SRX Enabling
Hey Jefferson, I think I have it figured out. Seems like calling joystick routines in the disabled loop has the undesired effect of causing the RIO's backend to crash/restart on power boot. It only happens once and doesn't affect much since the robot is booting up anyway. But there is a moment where when the CANTalon's object constructor's set up their messages, there is no one listening at the other end.
If you're grabbing joystick values in disabled() and using CAN Actuators I recommend calling one of the setXXX() routines on each CAN Actuator in the disabled loop. That way if this problem occurs, the code will periodically signal to the back end that those CAN objects exist and should be enabled. I reproduced your problem and tested the workaround. So for your two CANTalons (or just do all of them), try calling set(0) in the disabled loop so that on-power-boot they get reregistered ok. |
Re: Problem With Talon SRX Enabling
Quote:
Thanks! Just to make sure: calling a Get() function should be enough, right? I'd rather not disturb some of the position control with a Set() function. |
Re: Problem With Talon SRX Enabling
Gotta be a set. It will not disturb anything because it's in the disabled loop. It updates the control frame bytes, which aren't sent until after you enable.
|
Re: Problem With Talon SRX Enabling
Quote:
|
Re: Problem With Talon SRX Enabling
Try it to at least rule it out.
|
Re: Problem With Talon SRX Enabling
More info at Talon SRX Software reference Manual section 21.18
|
| All times are GMT -5. The time now is 02:41. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi