I was just wondering if the Remzibi has been updated at all to work with APM2.0. I was previously trying to get a minimOSD, but those are out of stock at the moment. Also if anyone knows how the rangevideo OSD works with the APM2.0 too that would be good to know as I have access to a used one of those.
Jdrones has a version of the MinimOSD that's in stock now. I would stick with MinimOSD range rather than others, since it's the only one whose firmware will be constantly updated to keep up with APM changes. (For example, APM is moving from MAVLink 0.9 to MAVLink 1.0 soon, and the OSDs will have to be able to read that).
What are the advantages of APM Minim over the jD MiniOSD ? I see the jD is a few dollars less.
I don't know--I've never used the Jdrones one. The 3DR one has a new and improve power supply, but I haven't compared it to the Jdrones one.
But then you don't recommend the 3DR (Remzibi) anyway. It looks like the jD also has an improved p/s (SMPS now vs. old linear). I just didn't want to purchase the jD one and then find out the APM one had more or better features.
The MinimOSD is back in stock at 3D Robotics.
Well, that certainly answers my question :) Very cool !
As far as you know, will the APM Minimosd work OK with high resolution cameras??
I saw some people having trouble using the Minimosd with high resolution cameras such the GoPro. Maybe they just haven't learned how to use it correctly.
I was having some problems when trying to use it on the ground side rather than the normal way where you put it in the plane. The logic was that if it was on the ground and you lost video signal you could still see the OSD overlay since Xbee has such a long range. Turns out it just doesn't work and lead to all kinds of problems.
Putting it back in the plane worked much perfectly so I would recommend doing it that way.
The OSD can be a little flaky when you plug in the camera. You will generally need to hit the reset button before flying to make the OSD overlay appear, so make sure you put the board somewhere accessible. Not sure if this is a hardware or software issue.
James, I salute your inventiveness - it was based on a good idea and you learned from the experience. Thanks for sharing it.
Using these open-source h/w & s/w devices is certainly a challenge (part of the fun for me,actually). I've struggled with AP Mega s/w and with AP Mission Planner and the HIL simulator. New s/w comes out almost daily, along with new features (and new bugs :) And if you've invested a lot of dough in an aircraft, you sure don't want to lose it due to one of those bugs. So like you, I'm looking for ways to have more reliability through redundancy. I already had Xbee but have now ordered the 3DR radios, due to 2x power output but at same power input, and what looks like might be better s/w support for use with APM.
I expect it will be good to have the Mission Planner HSI & moving map, plus have the OSD on the video. Not to mention, a 48 hour RF beacon if it does decide to fly away.
Since you've been using it, does MinimOSD provide a way to turn the overlay off and continue passing the camera video to the VTx? If not, I want to hack into it and use one R/C channel to control it. I'd probably set it up to failsafe to the OSD enabled state.
Also, have you thought about putting a remote controlled switch on the OSD reset in case things go awry?
Where can one find the s/w details in order to create the mavlink packet to do this? I don't yet know much of anything about mavlink. Turning off overlays wouldn't already be a standard cmd, right? You would have to know how to address the port that the osd is connected to and then look up the MAX7456 info to see what data to send it and then get the info that tells you how to format the mavlink cmd in order to get the bits into the 7456 in the right order. Is that the process?