-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Expansion Hubs unresponsive after ESD event until opmode is stopped #702
Comments
I literally was just looking at possibly this very thing. Are you using run to position mode? |
I was able to catch the gamepad disconnecting from the driver station during the ESD event in the act in a log! Notice this line in the log:
Here's the full log:
|
Yes I am, for more than one motor actually. |
Make sure you always assign a position to the motor before putting it in run to position mode. Do you still see the issue when fixing that? |
This issue is pretty hard to reproduce, it might take me a while to determine the answer to that... |
Also, here's the DS's log of the gamepad disconnect during the ESD event. (Not sure if it shows anything the RC log doesn't)
|
It doesn't sound like the |
I'm doing some ESD testing with our robot and just ran into an extremely strange issue. After driving around the field and zapping the lander, the Expansion Hubs became unresponsive to the gamepads and the robot began stalling out against the playing field wall. However, no comms errors showed up in the log, and upon pressing the stop button, the robot immediately stopped. What the heck?
Here's the log in case there's anything of interest that I missed, but I don't see anything:
Also, in a previous test, the gamepad disconnected from the driver station at the exact moment of the ESD event on the robot. Coincidence? Somehow I think not. Unfortunately I do not have the logs for that encounter because they were overwritten by the log from another test.
Both Expansion Hubs are running firmware 1.8.2
The text was updated successfully, but these errors were encountered: