Not many people know but we have an piece of open source software for controlling an Antenna Tracker. It's been built by Tridge (Arduplane lead developer) for use in the outback challenge.
Sadly we have no documentation and, as far as I know, nobody except Tridge has used it. Still given Tridge's track record on building great software I suspect it works well and if it doesn't, I'm sure we can fix it. So to not let this piece of code go to waste, I'd like some help from people who are interested to give it a try and help me figure out how it works.
Here's the little that I know:
- It runs on any of our supported board (APM1, APM2, PX4, Pixhawk, Flymaple and perhaps VRBrain)
- For APM1/APM2 users building the code is as easy as opening our hacked ArduinoIDE and selecting File > SketchBook > Tools > AntennaTracker and then building in the normal way. For PX4/Pixhawk, our autobuilder doesn't automatically build a binary but I can provide one if people are interested.
- It can control a Pan and Tilt gimbal like this or this found on servocity.com.
- It may or may not require a GPS
- It must somehow receive vehicle position updates from the ground station which has the telemetry radio that is connected to the vehicle. Maybe through a USB cable. Tridge probably uses the python ground station, MAVProxy, to passthrough the vehicle position data to the AT but perhaps we can get MichaelO to build out a similar feature in Mission Planner.
- I imagine this antenna tracker could also be used to keep a camera focused on the vehicle which might be good for easing the burden on creating videos of our vehicles.
So if you want to give it a try please do and stick any findings, questions or issues below. Alternatively Issues can go into the issues list.
I'll start sticking things into the wiki as they become clear.
Replies
One other observation on the 2nd telemetry link from the AT to GCS. If the MRC is unpowered so that there is no primary telemetry link from the AT to MRC then the 2nd telemetry link from the AT to GCS seems to connect rather quickly. This seems to add to the MavLink collision theory. Both my telemetry links use the same frequency but different net IDs.
I tested 0.7.1 firmware today and pitch indeed doesn't work. I set up a simulation environment (as simple as following a howto on ardupilot.com) and PITCH stays at +45 degrees (my fork). On official 0.7.1 it will most likely stay at 0 degrees. I am working on a fix and I am quite determined, since I want to fly my plane tomorrow morning :) I will report back as soon as I have some results.
Randy,
I've seen that you added readme.txt into master and I feel called to the whiteboard - I will try to write something in there when I'm done with the fix :)
After some investigation it turned out, that !nav_status.manual_control_pitch doesn't return 1 anymore and that caused the problem. It is now fixed. I may have broken something in manual operation but I can't test this mode since I have CR servos.
I already submitted a pull request: https://github.com/diydrones/ardupilot/pull/2633
If you can't wait - I attached the latest builds.
AntennaTracker-0.7.2-Pixhawk.px4
AntennaTracker-0.7.2-APM1.hex
AntennaTracker-0.7.2-APM2.hex
Thanks Jakub for the builds, tomorrow morning I'm going to test my AT first time in the field.
Huge thanks! I'll check it out with my students as quick as I can!
how does one slow the servos down
It depends on what type of servos you use. With official firmware and classic servos I don't think you can do this. With CR servos you can simply limit RC_MIN/MAX values.
Max servo speed (based on angular velocity) is on my todo list.
Hello guys,
today I put into service AT loaded with firmware build from Jakub Oller (thanks Jakub again). I set it somehow (indeed not optimal PID settings) but it works, ugly but works. Not tested it in the field yet, perhaps in the weekend. Now I would like to know what application I can use in the field since I have only android tablet. On the bench I connected it with MissionPlanner on PC and it works well - I can switch between MRC and AT, data from MRC flows well through AT to MissionPlanner. So I hope in the field it will work. But In the field I can only use Android tablet. When I tested it with andropilot and droidplanner on Android it didn't work.It works only when I connect Android application directly to MRC via telemetry link without AT in between.
Have somebody any hint on another application I can use on Android? Guess GCS doesn't work on Android.
I bought a Dell e4300 for 150€, bright non-glossy screen, readable outside on a sunny day. I just added a SSD and it now boots to Window7 desktop in about 20s.