Frozen Temp and Baro Altitude on G5.1

[HF_ATL]

I have a PZ0420 and don't have any problem also using it.

[Alex Villa]

Mine was sent back for repair.

I think is different issues

It's not clear to me that this is a hardware problem with the OSD, more than an incompatibility with some parameter of this particular camera. I wish I had an oscilloscope to measure the signal output for Alex to see. Alex Villa - if you really want I can mail you the camera for testing..

There have been reports that if the camera is powered after the OSD, it goes screwy? I wonder if there's a particular delay after the OSD sends the camera power before the camera actually sends signal, and that's what is causing the problem.

I have another one of these PZ0420 cameras, which is broken; unfortunately, but I don't recall it causing the same issue..

Send me a PM with your paypal. I will buy the camera from you and test.

[BloomingtonFPV]

Routing the power through the OSD to the camera did not solve the problem with the slow AHI. However, turning on the camera 10 seconds after osd boot did solve the problem. So my sequence is: power the osd, wait 10 seconds, turn on the camera, turn on 14v battery monitor.

I guess one question is whether the initialization sequence needs to see the voltage from the 14 volt main supply in order to correctly calibrate. My current sensor is always plugged in. I just have a switch on the 14v supply.

Edit: ok, this issue is intermittent. Back in the shop I plugged everything in all at once and it initialized fine. Very strange. I'll try to debug.

[ke123]

Alex, i have altitude display now when im flying (using that other el cheapo cam that doesnt cause the baro lock problem) but still my landing summary tells me the wrong max altitude (like 3x higher than i went) and the wrong speed. Any idea why that is?

Also the rvosd in question is a 5.1 that i preordered in june. The vibration indicator doesnt work on the debug page (i use the bouncy ahi indicator instead) but a friend just got a 5.1 and his vibration indicator in the debug menu does work. Is there a newer version of the firmware that i can flash to my 5.1?

[ke123]

Any ideas on the above?

[Alex Villa]

Can you post a video that shows the wrong summary display? never had reports on that.
There is a new firmware that shows the vibration indicator bars. However this is only useful if you really have vibrations affecting the AHI. I don't think it worth the update procedure just because of this(needs firmware update for both main and graph boards plus need to unlock the firmware).

[ke123]

I'll get a video for you next time I'm out at the field. Actually I've had that issue with a wrong report with rvosd5.0 as well when I had altitude set to gps+baro.

On my rvosd5.1 in my wing, I'm having severe issues with vibration and the AHI. However, if you don't think it's worth flashing the FW I'll just keep doing what i can to cut the vibes and see if it helps in actual flight.

Did you get the cam I sent yet? Could you reproduce the baro lock issue?

Cheers
Kris