Maybe using a buzzer instead of a servo signal could be the solution. The servo_test(); function is included in the system_ini(); so replacing this function with a buzzer function and defining it through an analog port can do the…"
Could be possible to implement a second battery voltage reading through Mavlink protocol? Will be necesary a second voltage reference for an improvement reading?
I have emptied three onboard video batteries with an obvious result of a…"
Is there any plans for implement a second battery voltage & current readings?
I have modified the libraries for do it, but for now I have too much problems with the params file.
The base of this change is…"
Make sure that you have aspd_enable ==1 and aspd_use ==1. By default I had both of them equal to 0, so airspeed (pitot tube) did not worked for me until I changed these values.
Regards from Spain!
@Andrew: What about include in code voltage readings for RSSI and a secondary battery voltage? Could be this request studied?
Now I am taking my RSSI and battery voltage reading from two ADC ports on my Remzibi.
The best would…"
I submit an enhancement request about RSSI readings. For example, my RX gives 0.5V for minimum signal and about 1.0 V for maximum. The analog read is linear.
This is the request in the arduplane…"
After spending a few days out of my city, I have finally been able to test the OSD in flight.
It is simply amazing!
Thanks to Hazy for offering this great update to our outdated Remzibi.
@Hazy:Thanks to the information you gave…"
I couldn't test the code yet because I'm still in college examinations.
I'll check the code concerning Mavlink to see if your problem may be due to a syntax error between versions 0.9 and 1.0.
I do not know how to compile…"
New minor bug:
Satcount is not working with MAVLINK 1.0.
Satcount shows satellites used by aircraft´s GPS. In APM Planner I can see them, so I think the problem concerns with Mavlinks statements (see…"
New ConfigTool.exe does not work for me. Open file makes an error and program goes down.
I have tried it on two machines, one with Windows 7 x32 and the other with Windows 7 x64, on both PCs occurs the same.
Regards from Spain,
Can be updated this enhancement to MAVLINK 1.0 without any complicated sentences?
The new mavlink protocol makes that osd shows wrong values.
In Mavlink 0.9 GPS ID is: MAVLINK_MSG_ID_GPS_RAW
and in Mavlink 1.0 GPS ID is:…"