Discussions

I have been trying about everything, and if you search for this in a few days I think everyone will start flaming me for posting on about every discussion group I can find on the same discussion.

Personally I like finding my information on this Board so I will update my progress...

6/22/2014

Successful flights with the MinimOSD v1.1 runing Minim OSD Extra 2.4, latest beta as of that date, no more freeze after arm, (connected to Pixhawk 3.1.5)

6/28/2014

Installation of the same system on a Deadcat Frame, Crius aiop v2 Running Megapirateng 3.01 R4

(in checking versions for this post I noticed now there is a 3.1.5 R2 for the Crius... plan on flashing it, really hesitant however since the loiter function was flaky last flight, only alt hold, stabilize were proper, however think it was a mag sensor error due to a Ferraro Mag getting to close, will post after update)

upon power up interference on the screen, some horizontal dashes, mostly a gray screen, disconnected and then figured that the firmware was incompatible. 

Connected to computer, via FTDI cable (Yes I know to power from the Video Side, first, then 5v side then camera, the then camera seemed not as important on my setup) No I get video, then black/blank screen with a tiny bit of video maybe 3-4 lines on the bottom, flashes for a second to video, the blank, checked video feed, and I can get that fine, seems that the board works as if I re do my steps I can get it to:

load firmware

load character set

both will complete however during this time I do not see a boot on the fpv/video screen, just the same blank/black screen

I was able to hit rest during power up and noticed certain combinations such as the order of power could disable the black screen however I would not get a overlay.

I am suspecting I have a video chip problem on the minimosd v1.1 and trying to diagnose the problem.

6/29/2014

Using a volt meter I checked the votage of both my ftdi cable and it was reading 5 v power, and 3.3 v tx rx;

At this point I had tried every other cobinations that I was able to get it to come to life before also see I posted on the steps prior, as I was having issues when it was new, and as the other post somewhere say the wiki is skinny.

I then tested the Crius inputs ( please not temerity is working, and gps, both of the first 2 serial ports, connecting the minim osd to the 3rd serial on the crius, tx to rx, ( this is well documented) however and should have testing this first the tx and rx voltages on the Crius AIOP v2 and as I suspected they are all 5.5.v

This is where I am confused, is this a firmware thing? immediately I remembered when I was connecting to the Pixhawk this:

TELEM1, TELEM2 ports

What do I need help with?

Does the MinimOSD v1.1 have a voltage regulation that messes it up if rx/tx from the board is greater than 3.3v? (Premise Pixhawk that worked with the same board and setup)

Anyone with this configuration with a Crius AIOP v2 please let me know if you have this working, which ports and what version of firmwares.

If it loads firmware, etc, and you get a black screen, can you recover from it? 

Is my board a goner? Seems strange that all the functions still work, as far as the board booting at least to either read value, save values (config or panels), load firmware and or character set.

Will be ordering a few more boards, but will not be connecting anyting to the Cirus until at least the voltages match the pixhawk I guess... seems like somethign that other would have documented if this is indeed the issue. 

Notes : What I hope is there is a way to rest the video chip, reprogram it, change a setting or do something as it seems that this is a common problem, happens often, and should have a fix, especially if everything else loads, it seems more like a setting thing 

Sometimes if you get a failed to connect to bootloader, do not try and read first, if nothing on the screen, try these steps...

Connect Video side, then computer ftdi, then first try and load a hex firmware, when done do not click it before you disconnect the usb to minimosd, then plug it back up, it should load, you then do the same method for the character... I can get confirmations on the computer, the video monitors shows a video feed and the black screens as noted above for me, however going though prior notes the responses in timing to load, and everything else suggests that I am booting just having a issue with the video overlay.