Hi Everyone. Above is an intro video to the minimosd. It still needs a tiny bit of tailoring but I figured I would send it out to the community for review. A video series like this could be beneficial for our community to grow in the future. Open to adding on a distributor logo for some help supporting my own hobby/builds.

Of course the video is open to criticism and input. They are compiled from scratch in Adobe After Effects/Premiere.

Andrew

Views: 4890

Comment by Mario bernard on April 11, 2012 at 10:24pm

hi Sandro

I seem to have a similar problem that Owen has. . I followed the wiki and the video.and all was fine ,except that i had a message when powering up the board during initialisation (load charset).and it kept stopping there everytime. I then tried to press the reset button on the osd..and all was fine untill the next connection, but i had to press that button everytime.for the initialisation to continue. I figured that maybe the Charset needed to be reloaded,so i did. Since that last reload and many more attemps, i have nothing but a grey screen without any text on it as video output.when no camera is connected. Of course i get an image when i plug the camera, but no osd overlay..Also, i dont get the OSD initialisation text either..I can connect to the board,  uploard firmware and Charset, save and load configurations, but cant get any OSD overlay. I checked all my soldering and wiring, but all seems to be fine. Any ideas ??


Developer
Comment by Sandro Benigno on April 12, 2012 at 5:54am

@Mario: Your case sounds to be simple to solve. You told me what I was trying to listen from Owen and f5pql69 with the step-by-step above.

If is the CharSet Update who goes wrong, in 99.9% of cases it's because the board was not feed sufficiently by the USB from your PC. It happens because of faulty cable or a too long one as well as a port giving too lower voltage on load. Well... whatever...

You can just feed your board with a battery during the CharSet Update process. You board should be fine after that.


Developer
Comment by Sandro Benigno on April 12, 2012 at 6:00am

@Mario: Are the stages of your MinimOSD tied or not? (those two jumpers on each side).

Comment by Mario bernard on April 12, 2012 at 8:57am

Sandro,  Yes they are as specified in the wiki. 

Comment by Owen Booth on April 12, 2012 at 12:12pm

Yeah, sorry Sandro, I'll send my wife out so I can get some alone time with my toys this weekend, try your suggestion out, and get back to y'all. I'm using the standard DIYDrones FTDI cable to power/data APM input side.

cheers

Comment by Mario bernard on April 12, 2012 at 1:47pm

Sandro, i am getting the following msg..   while trying to upload the miniosd19.mcm file 

error entering font mode.-no data


Developer
Comment by Sandro Benigno on April 12, 2012 at 1:50pm

@Mario: looks like your file is corrupted. I think you need a fresh one from here.

Comment by Mario bernard on April 12, 2012 at 6:55pm

Sandro, i figured that this could be the case, so i had already done that. I just tried again anyway, but same result.

Comment by Owen Booth on April 13, 2012 at 1:02am

Hey guys,

Erasing the EEPROM with Arduino (solid yellow light), and reloading the firmware, charset etc, several times ("Done!"), I've finally got it so it'll give the overlay ""waiting for mavlink heartbeats" when it's powered through the FTDI cable, and 12v from video in end.

Turn it all off however, and try again with APM plugged in, & 12v in at VidIn & I get video but no overlay. Then, if I go back to the FTDI cable again, it still won't work. Seems sporadic.

Some questions:

1/ Is there a boot up, power up sequence that we should use? Ie. Plug in APM feed end before the VidIn power?

2/ What is the voltage range we should get at the two separate ends? I'm getting 4.9v at APM input end, and 11.3v at VidIn end

3/ Should we be pressing the Reset button for a certain duration? 

4/ If I saved a layout pre-firmware upgrade, and then loaded it after the upgrade, will this corrupt it?

5/After the update processes, are we supposed to press "save to OSD", or hit the reset button or anything special? Or do we just do a reset?

I think I've exhausted all possibilities so far, and would like to send it back for testing. But 3DR still aren't responding to my emailed request for support. Any ideas?

thanks for your efforts so far Sandro. I'm sure, like us, you're getting tired of this!!!

regards,

Owen

 

Comment by Mario bernard on April 16, 2012 at 12:47pm

Sandro

I ' am also interested in the answers to Owen,s questions.

Thanks for your support. 

Comment

You need to be a member of DIY Drones to add comments!

Join DIY Drones

© 2019   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service