Hi All,
Before posting an issue or a problem in the ArduRover Discussion Forum, please check the wiki table of contents, review the firmware release notes in the subforum, and search that subforum for existing answers to your question. Help avoid duplicate threads by finding other members with the same issue and their solution.
When formulating your post, use a descriptive title such as "rover will not navigate to waypoints in the Auto mode" (not "HELP!" or "Problem").
Please include the following information to help diagnose your query:
- Describe the problem you are having. What is the expected verses the observed behavior?
- Provide hardware information such as the brand and version of your autopilot, GPS, radio, and compass, as well as any other pertinent details about your rover setup.
- What version of the APM: ArdurRover2 firmware version are you running?
- For navigation issues, provide your tlog and/or dataflash log. Click here for instructions on retrieving a dataflash log.
TCIII
Comments
Did some testing at Boulder Resevoir. This is what the starting line currently looks like
http://imgur.com/ICLmSDd
My car may have tried to wedge itself underneath one of the porta-potties...
Thanks Thomas!
I'll give it a try. You find a longer reply here.
Best regards,
Thorsten
@Thorsten,
That command does work as I have inadvertently tested it before I knew of its existence. I had a curb strike during the Auto Mode that stopped my rover so I went to Manual and drove the rover back to the start and went to the Auto Mode. The rover, instead of starting the mission again, tried to go back to the last waypoint before the curb strike and complete the mission:-) I presently have the MIS_RESTART set to 1. It is normally set to 0.
Regards,
TCIII ArduRover2 Developer
Hi Linus,
thanks a lot! Great!
I'll give it a try and report!
Best regards,
Thorsten
@Linus,
Nice catch. I remembered about that later, but you beat me to it:-)
Regards,
TCIII ArduRover2 Developer
Hi Thomas,
it depends on what you have MIS_RESTART set to.
0 = Resume Mission and 1 = Restart Mission.
So if you want to just pause a mission set MIS_RESTART to 0 and your rover should resume your missions.
Regards,
Linus
Hi Thomas,
thanks for the link!
What is not clear to me is if the Start/Stop function can be used to pause+continue Auto missions or if it can only be used to (re-)start a mission from the beginning (a function to resume a mission from last active command seems to be available in AC3.2-rc1 only).
Any kind of help is highly appreciated!
TIA,
Thorsten
@Thorsten,
The Start/Stop function has been available on the APM for quite a while and is now working on the Pixhawk. Details on how to use the Start/Stop function can be found here: Start/Stop
Regards,
TCIII ArduRover2 Developer
Hi Thomas,
I am new to rovers and just starting to put pieces together.
I am looking for a way (if possible without mavlink) to stop a rover at some point while in Auto mission and to proceed the mission after some external input. Hence, the Start/Stop auto_trigger function sounds interesting. Can you provide some details about it?
My idea is to use something like CAM_TRIGG_DIST (which can easily be set in a CGS). Then after it is triggered and the signal is send to an embedded computer (RasPi, BBB, etc.) a Stop signal is send back to stop Auto Mode and, after some processing is finished, a Start signal is send to resume the Auto mission.
Is something like this possible. I already posted here and here but no replies so far. Then I saw your post about the ArduRover 2.46 beta :-)
TIA and best regards,
Thorsten
Hi All,
ArduRover 2.46 beta is now available for use:Rover Latest This beta release version has been updated for proper sequential triggering of dual sonars and has had the Start/Stop auto_trigger function verified for starting and stopping the rover in the Auto Mode (Sparkfun AVC requirement) without the use of an R/C receiver.
Regards,
TCIII ArduRover2 Developer