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
If the grounds on the input/output side are all connected, you could always split out the signal wires on the pan/tilt and connect those to the gimbal ports and then plug the 5V/GND into the output that is powered by an external BEC.
Hey guys, might be getting a E-Revo in the near future, can it be converted to ArduRover usage? i.e does it have the space ? Or do I have to add stacks to add the APM?
Hi Austin,
i would try the new version.
2.4 has a lot of enhancements and should work way better although the release is not fully tested yet.
look here for more information.
http://diydrones.com/group/ardurover-user-group/forum/topics/apmrov...
Regards,
Linus
All out code base predate the .pde to .ino extension change
There is no content change for a .pde vs .ino file
They simply chose to change the default extension name, but we chose to stay with the .pde (for now)
The "new" IDE will try to change the file names, but we ignore that. The extension name change has nothing to do with why we require the more recent IDE versions, that extension change is immaterial to us. Hope this helps.
AVC 2013 info posted! https://avc.sparkfun.com/2013
Gregory, There is a new user manual wiki being created currently. The Rover section will need lot's contributions from the members of this group for sure. Stay tuned, an announcement will be made once the basic structure is in place.
I personally think the rovers will be a huge part of all this business!
Gregory -
A slight alternative to option 1 would be using a motor controller that can parse the signal to differential. The Sabertooth series do this (check out the datasheet) - although the biggest they have is 60 amps I think.
http://www.dimensionengineering.com/products/sabertooth2x60
And I don't know much about CAN messages in relation to arduinos in general, but modifying the firmware is going to be tricky. There is no easy place to step into the code and make the kinds of modifications you're talking about, I believe.
Hi Tom,
After we finished up our dev call on Friday I did a bunch more work on the sonar code, and added support for both inverted and hyperbolic sonars.
The key is a new parameter SONAR_FUNCTION, which has this explanation in the code:
// @Param: FUNCTION
// @DisplayName: Sonar function
// @Description: Control over what function is used to calculate distance. For a linear function, the distance is (voltage-offset)*scaling. For a inverted function the distance is ((5.0-voltage)-offset)*scaling. For a hyperbolic function the distance is scaling/(voltage-offset). The functions return the distance in meters.
// @Values: 0:Linear,1:Inverted,2:Hyperbolic
AP_GROUPINFO("FUNCTION", 3, AP_RangeFinder_analog, _function, 0),
I think that should work for your Sharp 2D12 sensor, but please test it! If needed we can add more SONAR_FUNCTION values for different mappings between voltage and range.
Cheers, Tridge
-
17
-
18
-
19
-
20
-
21
of 30 Next