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
Hi All,
Here is an update concerning the possible bug in the ArduRover2 v2.45 active braking beta code generated around 4/7/2014.
Last night Tridge updated the Pixhawk firmware so that if there is a loss of the FMU, the I/O section will put the servo outputs to neutral (1500us for the rover throttle) to prevent a runaway.
This afternoon I was able to duplicate the runaway condition without the rover actually running away during testing on my Home Depot test course.
For those of you how are interested in this firmware troubleshooting here is where you can view the discussion posts: rover crash bug
Regards,
TCIII ArduRover2 Developer
Sparkfun AVC 2014 Course Preview posted earlier today:
https://www.youtube.com/watch?v=5rgl8qSMnCg
@RoboBill,
You can report a new issue here or add on to a previous issue post: drones-discussion You have to join the Group to post.
Regards,
TCIII ArduRover2 Developer
@TCIII
Thanks for the bug alert... So is there a preferred sub forum where we can report problems with a latest firmware version(s) and also make suggestions?
Thanks
**********************ArduRover2 Firmware Alert*****************************
There is a possible bug in the v2.45 beta code generated after 3/30/2014 that affects both the APM and the Pixhawk and may cause the rover to runaway unexpectedly at random times both in the MANUAL and AUTO Modes. The only way to recover is to cut the power to the APM/Pixhawk to shut it down. Sorry about the inconvenience.
TCIII ArduRover2 Developer
The blank screen you see is because your current params are the same as the ones you are loading. I think. It's a compare params screen.
Try changing something, say WP_Radius, write to APM/Pix, then try loading from the dropdown again. The WP_Radius change should be there, showing the change you made as current, and the loaded params WP_RADIUS as the change.
Mike
@RoboBill,
You might want to try here: GCS Discussions
Regards,
TCIII ArduRover2 Developer
I too have run across this issue. What forum/group is the best place to ask questions and submit suggestions for the mission planners(s)?
@emile,
I have always used the full parameter list, however I was on the ground floor with the ArduRover2 development and know my way around. I would look at the ArduRover Wiki and Wiki parameter list to see what is germane to what you want to have control over or leave at the default value.
TCIII
Thank you Thomas. Yes I have advanced view checked but still get same results.
Here is a screen shot:
My assumption, which is probably wrong, is that by selecting the rover.params I would get only those params that apply to a rover.
What is the best way to modify parms? Work from beginner to Advanced or work through the full param list?
Thanks