tobiasbales / playuavosd Goto Github PK

Tobias, I don't do coding using Arm and so don't have the toolset installed. Is there any chance you could provide a compiled version with your release files? Thanks, Paul A

Hi Tobi,

Wonder if you can help? I have had this issue since I first used PlayUAV board and it persists. I have 2 cameras connected - 1st is a Sony 600tvl board camera, and 2nd is a GoPro Hero 4 Silver. When the copter is powered, the feed from the Sony 600tvl board camera initially appears on my goggles - but no OSD overlay appears - just the clean video feed. I then flick the switch so the PlayUAV switches to the GoPro, and the OSD displays fine with this camera. I switch back to the board camera and no OSD again!
I then re-power the hexacopter, and this time the OSD works fine on both cameras!

This seems to happen every time I go flying this copter. Could this perhaps be a video sync issue with the board camera??

Hello

I see there are some icons on the osd. But I don't see them. Instead I see signs.

Is there a bin version with icons?

Thanks

https://vimeo.com/183227708/4ab9609c49

This is run from a compile of master as of about 9-15-2016.

And yes, I did check the source log file from ArduPlane. It looks fine:

when mapping its important to know that the camera shutter is being triggered properly, its very annoying to find after an hours flight that its done nothing due to some little issue,

a dot that flashes when the camera shutter is triggered would be enough.

on the osd you can configure link quality and RSSI but from what i can tell they do the same thing.

I would like to have RSSI for the receiver RSSI and the link quality for the 3DR telemetry radio link quality.

A panel which is shown after the plane has landed would be nice.

Things that might displayed on the panel:

• max distance
• max altitude
• max speed
• avg Amps
• max amps
  and so on....

I have gone fly a few times and once the plane is above some urban areas, the osd restart infinitely. Can someone help me with the problem?

Running the PlayUAVOSD with a PX4 I do mostly get correct data to be displayed, but sadly the flight mode display just says "Unknown".
Could you add PX4 flight modes please :)?

Bascially, PX4 sends it's flight mode in a custom data format px4_custom_mode via the custom_mode variable in the mavlink heartbeat message.

For more info, see how it's sent and how it's encoded.

You can take a look at this issue from QGroundStation:

mavlink/qgroundcontrol#4449

And then the fix:

PX4/PX4-Autopilot@1c42cea

But the comment is that we are ignoring the error on the PX4 side rather fixing it in the PlayUAVOSD.

It is some standards that are not met I understand by the comment regarding the MAVlink.

Could it this be related to the fact that PlayUAVOSD recieves the mission from the px4?

Hi! I collected this an OSD based on the information placed by you. But after assembly, careful check of iron, and record of the program for address 8004000, it wasn't launched. Can eat errors in PCB or the program?
I can collect and program but unfortunately I is weak in the code.
There is a strong wish to revive this project.

Hi guys,

I have trouble with the Homelocation not showing up correctly based on the compiled FW here ().
While it shows ok in the map mode, the "radar" shows it is a somewhat random direction (south when it should be north etc...). I saw this is a known bug in the main branch but had hopes that it was addressed by you already Tobias.

Thanks !

currently only baro altitude is supported but i would like to see when the rangefinder sees the ground and what altitude its measuring, this is important for a few reasons,

first it tells you when your sonar /optical flow is working on copter since it kicks in when the rangefinder can detect the ground

The second is for when terrain following or landing with a plane knowing your hight above ground is critical, a low altitude warning would work much better with the rangefinder too.

At the moment the numerical vario is almost useless because the output is to noisy. (Values fluctuate strongly even if the plane is on the ground) Some kind of Filter should help