We are experiencing command lag after switching from auton to teleop ONLY in a competition setting. FTA’s had nothing, and dumping the scheduler after transitioning into teleop seemed to be a temporary fix. I’m new to the new command based, I did mainly Iterative/Timed Robot when I was a student. Is there anything we can do to debug/fix these issues without rewriting the code to avoid commands?
While I was mentoring my former team (non-command based), they basically always had competition-specific wireless lag issues starting from 2012 that didn’t happen at home.
As far as I can tell, it’s just a combination of router placement on the robot and 802.11 congestion in the venue. There’s a reason no one uses 802.11 (aka Wi-Fi) in industrial real-time robotics applications. We use it because the COTS hardware is cheap and available.
To be clear, I don’t know if your issue is a software or hardware one, but there are underlying technology issues to be aware of.
Can you share your source code with us? A link to something like Github would be ideal.
Are you using colour sensors? If so, how are they wired?
How are you using the ports on the radio? Can you add a photo?
Edited to add: Have you looked at your DS logs? Can you share them?
Are you experiencing loop overrun warnings? Are there any specific error messages you are receiving? Like user bovlb said above source code would be great along with what electronics are being used.
A few things:
- can you elaborate a bit more on what you mean by “command lag”?
- have you tested with Practice mode (through the DS)?
- assuming that by “dumping the scheduler” you mean calling
teleopInit(), that’s the recommended behavior. The few frames of disabled mode during the auto/teleop transition might affect the way your commands run (and you might be expecting different behavior).
- others have said this, but I’ll reiterate that a link to a github repo or something with your code would make help much more effective.
- After Autonomous mode (in which the robot performed fine) in Teleop our shooter was pretty much unresponsive, while the drive train functioned fine. Shooter would shoot, but several seconds after buttons were pressed.
- Yes, it functioned perfectly.
- Yes, that is what we did.
- No error messages AT ALL
- @Fletch1373 was our FTAA and didn’t see anything unusual in the DS
Thanks so much guys!
I saw the original post and was wondering if this was the same team.
For everyone else, this issue appears to match the pattern of a command (group in this case) being delayed because another command is active and requires one of the subsystems that this command needs. I couldn’t find any obvious instance where this was the case, but we ran out of time trying to debug.
@kelmalon, I left a list of troubleshooting steps with someone on your team. Have you had a chance to follow them?
In the shooter constructor, you’re setting a ramp time of 1.5s, which seems quite large, and which might appear as a control lag.
We have implemented them, and will be testing at our next competition this weekend! Thank you for your help!
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.