woo another NZer
when i programmed mine the other day i had ground and +5v connected as well as the rest of the necessary wires.

is only i have problem with colors when connect osd?
color cam looks like BW then osd connected

Originally Posted by cardboardboks

woo another NZer
when i programmed mine the other day i had ground and +5v connected as well as the rest of the necessary wires.

Maaate !!

Did you power the board seperately ?

Originally Posted by Joern

I flew several times with the G-OSD II and the stock gps module. All worked verry well including home vector, distance and so on. Because of this I think the GPS module is fully functional. I changed the firmware to show the coordinates during the flight, so I can record the coordinates in case the plane might go lost. Now I tried to put the coordinates in Google Maps (#define GPS_GOOGLE_FORMAT, both backslashes are deleted). The location of this coordinates are nearly 70KM north of my location. I had a stable fix with six sattelites.

Has anyone tried to put the coordinates into google before? Could this be an error in calculating the coordinates?

Regards
Joern

I had a similar problem. The first digit after the '.' had to be '0' for properly show the location in google maps - however the leading zero is not printed. I submitted a patch to fix it by email to cl-osd@googlecode.com on the 22/11/11 but so far I haven't received a reply.

Originally Posted by chatch15117

do you have circular polarized or just a patch?

Circular ... so it's CL/SPW combo on 5.8Ghz. However the Video-TX is a bit noisy so pic-quality is not as good as it could be

Revision 88:

"Working current sensor using ACS758LCB-100U-PFF-T.
Only tested on bench so far...
Alarms for high current and high mAh.
Some sensor and text print rework."

Note that in order to get good values on current sensor you will have to sacrifice RSSI. Or move RSSI to voltage 2.

Originally Posted by callelj

Revision 88:

"Working current sensor using ACS758LCB-100U-PFF-T.
Only tested on bench so far...
Alarms for high current and high mAh.
Some sensor and text print rework."

Note that in order to get good values on current sensor you will have to sacrifice RSSI. Or move RSSI to voltage 2.

does the current sensor show current and mah only, no voltage ?

ALso, can the G-OSD show main pack voltage (V1), current sensor (V2) and RSSI (V3) ?

Voltage is available already since r1...
New is current and mAh.

In theory but the resolution will suck...
Either move RSSI to voltage 2 and that resolution will suck....
Or remove the voltage divider on voltage 2 and change some defines.

Originally Posted by callelj

Voltage is available already since r1...
New is current and mAh.

In theory but the resolution will suck...
Either move RSSI to voltage 2 and that resolution will suck....
Or remove the voltage divider on voltage 2 and change some defines.

what i meant is for my E-OSD converted to CL-OSD, can i display 1 voltage(main lipo) + RSSI + Amps/mah ?

Nope.

(You could if you solder a wire to adc2 (pin 25) and change the code a bit...)

Originally Posted by callelj

Nope.

(You could if you solder a wire to adc2 and change the code a bit)

Can you explain how to do this ?
can the G-OSD converted to CL-OSD support what i asked ?

Originally Posted by i3dm

Can you explain how to do this ?
can the G-OSD converted to CL-OSD support what i asked ?

1. Solder a wire to pin 25.
2. Connect that wire to your current sensor output pin.
3. Add "#define ANALOG_IN_3 2" to line 62 in hardware.h

Might work...

Yes, the G-OSD can support all three but either RSSI or current sensor will be a bit low in resolution.

Nice work on the current sensor.
What update was the 2Hz refresh added on, I cant see it? Or was that someone's personal side project?

Opt: Thanks!
You can see all the changes I have made here: http://code.google.com/p/cl-osd/source/list

Originally Posted by callelj

Yes, the G-OSD can support all three but either RSSI or current sensor will be a bit low in resolution.

can you explain why please?