search

bubgum / crw-cmu

Automatically exported from code.google.com/p/crw-cmu
0 stars 0 forks source link

Thruster stopps during navigation to a waypoint #33

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Connect the client to the server running on the phone.
2. Open the Debug panel and  create a bot.
3. Manually set a pose from the map and assign a path/area/waypoints.
4. Keep creating new waypoints after 20sec or so.

What do you see instead?
The thruster stops during navigation to a waypoint. The Amarino monitoring log 
shows that the thruster values are being sent. The logcat also shows the same. 
The Rudder works fine though. There is no change in state if you try to assign 
an area or a path at this time (Thruster does not start). The thruster 
starts/spins if you assign a waypoint by holding the ctrl and clicking. The 
thruster also starts if you manually control it from the debug panel after 
disabling the autonomous mode. The thruster value send is 1725, same as the 
value that was sent when the motor stopped. The LED on the ESC is red, 
indicates normal run mode. No errors or exceptions show up in any of the logs. 
Log is attached.

Original issue reported on code.google.com by abhinav....@gmail.com on 1 Sep 2011 at 12:39

Attachments:

GoogleCodeExporter commented 9 years ago 
I think we diagnosed this to be an ESC issue, and so far, using the SS-35 
controllers appears to resolve the issue.  We'll see how things go over the 
next few deployments.

Original comment by psi...@gmail.com on 2 Sep 2011 at 4:48