hello good afternoon. We are having problems with loss of communication and teleOP being suddenly deactivated. Has anyone gone through something similar? Or do you have any idea what we can do to solve this problem?
Thank you very much in advance.
I think you’re missing too much info to get help with your specific situation.
What devices are losing communication? You mention teleop being disabled, does that mean you’re running the driver station? The MK4 swerve modules themselves don’t communicate. Their motors may, or their motor controllers. You’ll need to be more specific
Our radio keeps turning off while the base moves, in addition, the Driver Station is disabling, by itself, the teleOp while the robot is moving. We thought it might be the battery power spike (because the motors were using full throttle and the battery didn’t hold enough power, but after that,
Driver Station continued to disable itself)
Sounds like a loose wire somewhere that’s getting disconnected when the robot moves. Without more information I can’t be more specific about where to check, so just start checking everywhere.
We looked at every possible cable and none seemed to be loose. To be more specific, our problems are: The Station driver is disabling out of nowhere while the robot is being piloted (There is no loss of communication, just the disable on the DS). The other problem is that the radio restarts during training,
This problem seems to have to do with the peak current generated by the motors, since every time it restarts the current exceeds 80A. If you know of any way to check the possible causes of the problem, we would be grateful.
The robot code shouldn’t be able to disable itself unless the robot disconnects. Maybe it’s disconnecting and reconnecting very quickly? If you can post a copy of your driver station logs that might be helpful to figure out what’s going on.
This is the data generated in our last training, I don’t know if this is what you wanted DSLogs.zip (546.2 KB)
We’re fighting/fought through 4 comm issues.
- comms fail for about 30 seconds with the wifi connection dropped on the DS. This is usually a radio power issue (radio reboot). For us, the problem was bad power conditioning on the Rev radio power module. Replacing the module fixed the issue.
- rio dropping out for about 10-20 sec. This was a loose power connector to the Rio, so the rio was rebooting.
- comms fail for about 1 or 2 seconds. DS reconnects immediately and we can re-enable the robot immediately. There’s an issue thread on the wpilib github page: error report: "internal issue with print and error tags." on the FRC Driver Station. · Issue #6174 · wpilibsuite/allwpilib · GitHub. Discussion indicates that NI will be releasing an update to the Game Tools to fix this one.
- Comms lost due to ?? We’re still diagnosing this one. The most reliable symptom here is that the ssh service dies, and requires a Rio power cycle to fix. I’ll start a new thread asking for help on this one when we can give some decent diagnostics.
I hope this helps particularly if your symptoms are in the first few categories.
2 Likes
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.