I understand. Thank you very much, by the way, for all the detail on the history and internals of sysId. When it works, it’s indeed very useful. And while I’ve run into issues like having to “deploy” twice or maybe just restart the robot a couple of times to get it into the sweet spot, it eventually worked OK in setups with 1 to 4 Falcon motors.
1 Like
This fixed the issue with “No Robot Code” and the NT not connected. Thanks!
It’s probably unrelated to that particular change. The tool needs to be 2022.3.1 or later to work with the v4.0 image.
2 Likes
Do we have to manually download the 2022.3.1 version from github? When I use vscode to update wpilib, the tool has stayed 2022.1.1. I noticed the PR and downloaded that version to get it working.
1 Like
Yes, the global tools are only updated when you run the full installer from GitHub.
I am unsure if it is related to the issue reported above but it seems similar. Using SysID with 6 NEOs the following error appears in console
ERROR -111 Error: Loop 0.005000s overrun PrintLoopOverrunMessage
Warning at Main: Warning: Watchdog not fed within 0.005000s
Warning at PrintEpochs: Warning: LiveWindow::UpdateValues(): 0.000006s
Because of this the motor controllers are not being updated causing them to brake for an instant often. Any help with this would be appreciated.
2 Likes
Update on this: That message is being sent when we disable so it is not the watchdog that is causing the issue. (I figured this out by changing the sysid loop to 20ms and the error message went away while the issue did not). The neos are still sputtering and making a kind of train noise when run
We resolved this issue by writing our own SysID logger ( which can be found here. No idea what was causing the original issue…
1 Like
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.