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
That is good news.
I still haven't found a cause to MAVLink duplicates. I haven't even confirmed, that it is actually the duplicates that cause the problem. What I know for now is that in some setups (usually when tracker is inbetween MRC and Mission Planner) we get a lot of "Already got param" errors and the cononection time is very long if it connects at all. I solved it by using MAVProxy to divide MAVLink stream into 2 separate ouptuts - one for tracker, one for Mission Planner.
I wonder if the MAVLink issue could be related to the message forwarding in the MAVLink_routing class. Maybe some messages are bouncing around amongst the vehicle and GCS unnecessarily. Not sure, it's just a guess.
Hi guys,
I have attached below a picture of my AT based/connected to a pixhawk. I've tested 0.72 firmware yesterday and it looks ok for YAW but the pitch. For some reason I can not have pitch working. Actually it never worked before in my AT. If I go to test sliders, i can send command to pitch servo without a problem. The issue is when I put the AT in AUTO mode or SCAN. Pitch does not work.
Any thoughts or hints you guys can give to me, please.
I appreciate your help.
regards
Didi
Didi_AT2.jpg
Didi_AT1.jpg
If your PITCH doesn't work in SCAN mode then you probably have something wrong in your setup. Usually problems with pitch were only visible in AUTO mode, all other modes were working fine. I will test it later using SITL.
I have tested 0.72 in the field and pitch was working for me. With 0.71 pitch did not work in scan mode, either.
Yes, I verified it in the code and SCAN mode couldn't have worked in 0.7.1
IIdemir,
Ok, so that indicates that the pitch fix in 0.72 hasn't worked. :-(. I tested in the sim (although perhaps not thoroughly enough) and thought it was working... but perhaps not.
I tested both my firmware (posted above) and official firmware. In both cases PITCH is working fine.
Randy,
I did at least 5-6 hours of testing using SITL and it worked perfectly. I am not sure if I tested my version of fix or yours and it may be the only difference. I will test in the evening and report back.
Thanks Randy,
I will do more tests over the weekend. Perhaps I did something wrong too. Still investigating...keep u posted.