Hi CaScAdE,

perfekt, danke!



Specky

Hallo zusammen,

hab ein Problem mit meinem EPI-OSD.
Hab es gerade das erstemal in Betrieb genommen. Das OSD ist an dem Debug-Port von der Navicontrol angeschlossen.
Wenn ich den Copter einschalte bekomme ich erstmal garnichts zu sehen. nach ein paar sekunden piept der copter einmal (ich denke mal für die navicontrol) und danach bekomme ich den "C-OSD init screen" wo mein aktuelles setting die akkuspannung und zellenanzahl angezeigt wird.
Die Komunikation mit der Nav-control scheint also zu funktionieren.
Kann dann auch ins Menü vom EPI-OSD gehen und alle möglichen Dinge on oder off schalten...

Das wars dann aber auch schon. Ab wann sollten denn eigentlich Live-Daten auf dem screen angezeigt werden? Muss ich irgendetwas noch dafür aktivieren?

Bitte um Hilfe.

noch eine zusätzliche Info:
hab das EPI-OSD von Immersionsflug.de. Die spielen von sich aus die C-OSD Software auf. Software war also schon drauf. hab also nichts mehr flashen müssen oder so. Oder hätte ich doch noch irgendwas machen müssen?

Hast du noch irgendwas zwischen DEBUG und OSD heaengen? Wi232 oder BlueTooth?
Im menu muesste nur passive OFF sein und HUD ON.. Dann sollte was kommen...

GOOOOOIIIIIIIIIILLLLLLL!!! Lüppt jetzt.

Hatte "passive" auf ON stehen wie alles andere auch.

Jetzt auf OFF gestellt und ich bekomme alles mögliche angezeigt.

Super ! Danke !
Dickes Danke auf für diese tolle Software. Hoffentlich bleibt das Wetter morgen noch so nett, dann werde ich mal den ersten Testflug mit OSD machen

Wünsche noch einen schönen Abend.

Have a new c-osd, everything is hooked up but led 3 and 4 are solid green, can navigate the menu but never get a hud.

leds 1 and 2 never light up

nav controller and flight controller are communicating fine, running a single ribbon cable across the 3 boards on the fc inputs


also tried navi fc port to fc and navi debug to osd same thing

Any ideas?

ca you communicate to the ods with the MK-USB board?

In the menu: What about "FULL HUD" and "PASSIVE"?
Some people swap the NTSC/PAL option when trying and always setting them back to the wrong choice... But as long as you can see the menu when exiting this should be ok.
Which software is on the OSD? (and the NC/FC) Depending on which OSD-software: FC-ONLY or normal you need to connect the OSD directly to the FC (FC-ONLY) or to the debug port of the NC (normal version).

You can try to connect to OSD "to FC" port to the MK-USB "x2" port with a cable where pin 1 and 9 are crossed/swapped. Then you should see the OSD requesting the OSD-Dataset in a terminal with 57600-8N1...

tried full hud on/off ntsc/pal do not know which software on the osd as it does not show up anywhere, ordered an avr programmer so i can check it out

did not check the passive option

nc & fl are the latest software, osd came pre flashed & built

Just to be sure: Could you post a picture of your setup?
The fact that the LEDs are constantly on and the other two are constantly off keeps me a bit confused...

externer Link:


so

fc plugged to nc
nc debug plugged to osd fc in

gps removed for pic

got menu and video feed but no hud

Actually I do not see some obvious mistake right now.

The OSD is powered by a full LiPo? 3s or 4s?

Did you try to measure the RX/TX path? From the mega162 on the OSD (pin 42/43) to the arm9 on your NC 2.0 (pin 39/38 ). And make sure GND is connected as common reference...

powered by a fresh 3s, yeah will check the traces double check the connector seems fine, i know the debug port is good on the nc cause i can access it through the computer. will let you know about the traces tonight

It all works cold solder i guess redid all my pins

only thing is letters have a fuzzy background

wonder if anyone has looked into audio telemetry for the eztracker?

I saw a similar problem on the latest build. My unit is connected to the Debug port on the NC. I could get the setup screen, however, the EXIT is off the screen at the bottom (this is with NTSC).

Then, I was not getting the HUD at all no matter what the setting. I have 1 channel connected to the PPM connector. If I pulsed that channel, the HUD would come up and disappear.

So, I went back 2 versions and I was then able to get the HUD display up and running.

Mike (reading the translated German)

delete

1 more comment.

I could ONLY get the SERCON working on a native RS232 port. I tried 3 USB/RS232 ports and I was not able to get PonyProg to recognize the SERCON. I know that this has been stated before, however, I wanted to make sure that others knew that.

Mike

va3mw meinte

I saw a similar problem on the latest build. My unit is connected to the Debug port on the NC. I could get the setup screen, however, the EXIT is off the screen at the bottom (this is with NTSC).

Then, I was not getting the HUD at all no matter what the setting. I have 1 channel connected to the PPM connector. If I pulsed that channel, the HUD would come up and disappear.

So, I went back 2 versions and I was then able to get the HUD display up and running.

Mike (reading the translated German)

yep my exit is off the screen also

Now if only i can free up some time to dig into the code mainly a pic man but it's all c in the end

I reloaded the latest version and it seems to be working fine now. Very strange. Not sure what happened.

Can you explain what is supposed to happen when I hook up the PPM to a channel? Mine is on channel 6, but when I toggle channel 6 on or off nothing happens on the screen.

In my MK bird with 2.0 ESC's I don't get current readings (I think). Am I supposed to see total current consumed. I have yet to test that.

Many thanks for all the hard work on this. I have yet to have my true first fpv flight but that is coming up soon. I just need to build 2 of OMM's 1.2ghz circularly polarized Omni video antennas http://www.rcgroups.com/forums/showpost.php?p=18377029&postcount=224

Mike

Since chrispol and va3mw got their OSDs working I assume there is not bug to hunt currently?

The EXIT off the screen happens for NTSC user... I must admit that I did not test the NTSC part that much because my test-OSD is solderer to a cheap PAL cam and I am too lazy to rip off the cam everytime

va3mw: The PPM part is working for some people and for some not but I did not figure out why because here it worked ever since I implemented it... The only thing happening is that the COSD_FLAG_HUD is toggled causing the OSD to be drawn or not.

va3mw: The current measurement is taken from the OSD-Debug-Struct sent by the NC. Do you have correct values when using the MK-Tool?

chrispol: As you said, it is all C in the end and you should not have to struggle with the AVR related stuff in the code to do most changes.

Very unusual on the first time when it would not work and I suspect that it has to do with the PPM stream as it would show for a few frames of video and then disappear. Does there have to be a PPM signal for the HUD to work at all? I gather I can run without it.

Many thanks, and I will do some more testing on the PPM stuff. It isn't a big deal for me, just thought I would let you know. I can scope the line and see what I get. Don't spend any time on it unless you have a reason to.

I will do more testing on the Current as well and see if it matches the MKTools readings.

Most of my questions are me just getting it going for the first time. I really do appreciate all the effort you have invested.

regards, Mike

Let me add some notes for first time users. I know that these sound pretty simple now, but when I first got the board, it was the details I struggled with for a few hours

OSD can connect to the FC or NC with FC - watch polarity of 10 pin cable. On my board, the FC pins are NOT above the debug port for the NC and there is a slight offset. If you mount the board upside down, then the pins line up, but the you have to twist the cable

3S or 4S is OK. For 4S add a heatsink on the 7805 voltage regulator--this doesn't have to be anything special. I just soldered in about 2 square cm of tin

You can power your camera from the 12v or 5v line on the board, but be careful of the amount of current you need. I believe the 12v line is actually the battery voltage and is not regulated

In NTSC, the Exit for the configuration screen is off the bottom of the display... not a problem, just go down 1 more and select it

PPM signal is not required (I need to confirm this)

With valid data from the NC or FC, the screen will either show HUD or Statistics

For me to get the SERCON working, I had to use it connected to a Hardware Serial port (not a USB/RS232 port). This is with PonyProg. Make sure you check your fuse bits (lots of info on that already... thanks!)

Past that, there are some fancy features you can now play with.

I hope that helps some of the newer people.

cheers... mike

va3mw meinte

PPM signal is not required (I need to confirm this)

True.

va3mw meinte

OSD can connect to the FC or NC with FC - watch polarity of 10 pin cable. On my board, the FC pins are NOT above the debug port for the NC and there is a slight offset. If you mount the board upside down, then the pins line up, but the you have to twist the cable

That is the reason why I solder the "WSL 10G" from Reichelt instead of just pin headers...

va3mw meinte

With valid data from the NC or FC, the screen will either show HUD or Statistics

For me to get the SERCON working, I had to use it connected to a Hardware Serial port (not a USB/RS232 port). This is with PonyProg. Make sure you check your fuse bits (lots of info on that already... thanks!)

Isn't that what is mentioned in the README and the FAQ?

Yes, it is.. my brain just seemed to miss some of the obvious. Or, I was hoping that it wasn't EVERY RS232/USBS adapter. LOL

AFAIK there are some adapters out there which are based on FTDI chips and they have all the needed signals...
The cheap ones only supply RX/TX and that is not enough to programm with ISP....