So far MinimOSD is a big FAIL, I'm completely unimpressed.
It seems to have a mind of its own sometimes, today it decided to load a panel that I've never seen, couldn't make any sense of it and I couldn't get it to go away with resets and reboots. Had to reconnect to OSD Config to fix it.
The OSD toggle option doesn't work. I configured and uploaded both Panels in OSD Config. I set it to Channel 8, then assigned CH8 on my radio to a switch and recalibrated in MP. When I flip the CH8 switch on my radio it usually does nothing but it once switched to a screen that said my airspeed was 100 and showed "Overspeed" and that was all.
Still can't get RSSI to read correctly always shows 1%. I posted this problem last week but I'm not holding my breath waiting for a reply.
My icons show differently live than what the Panel shows in the OSD Config tool. Tried to upload the new character set but it doesn't exist in the MinimOSD downloads section.
The battery percentage indicator always shows 100% even when my battery is sitting at 50%. I'm running a 4S setup and have 14.8v set as my minim batt voltage and 10% as warning level. Am I missing something here?
This board is fresh from 3DR, and I've uploaded the latest firmware as well. I'm running it on a new APM2.5 also with the latest firmware. Also using the 3DR power cable.
Is there a return policy on these things? So far I feel like I've been robbed.
Replies
Just found this thread too...
I basically like the OSD so far. I use r590 of the copter-extra.
So far I have only one issue. I set the stream rates with mission planner and saved them but when I reboot the APM, it doesn't send any stream. The OSD is not requesting the streams itself like the old 0.20 version, so I always have to use mission planner. That makes the OSD essentially useless to me as I don't have a laptop to take with me in the field and start the streams manually, all the time. I think, the OSD should wait for X seconds and if it doesn't get a stream by then, request the streams by itself.
I just found this thread today. Is it really a problem to use a common ground? I have one hooked up that way v1.1 and it's never had a problem andthe wiki isn't clear that it IS a problem. At least if it's going to kill the board, it should be something in red letters. Even the diagram doesn't clearly show the grounds need to be separate even though it doesn't show them joined either. I'm powering my APM2.5 via power module with 3S and using the balance plug to power the immersionrc which then steps down to 5V which is what I power the minimOSD with. Still the ground is common.
Is this a problem and why does one of mine work that way. I also I read on the post that someone else used it like that without a problem.
I can use a separate battery but this paticular quad is quite small so didn't want to have to use 2 batteries. Well 15 minutes of video 600mW should be a small battery.
So is this why I get the black screen? Does anyone know what gets burned in that situation?
Update... reburned bootloader on both boards. Then I tried uploading your eeprom sketch and on one it took, the other gave the error I posted earlier about being out of sync. The one that took your sketch had the 1Hz flashing yellow and now has solid yellow, like you had in your sketch. On the board that took your sketch it gets "failed to talk to bootloader" error in CT2.3 trying to upload 552r. The other board that would not take your sketch and has a 4Hz pulsing yellow also gives same error.
One of these boards took the FW last night but neither are today. These boards are starting to seem hopeless!
Sandro, thanks for the help yesterday. All that you asked me to do went ok except when I run the EEPROM.write sketch I get this error on both boards.
avrdude: stk500_getsync(): not in sync: resp=0x00
When I connect one of the boards to diydrones FTDI I get a 4Hz pulsing from the yellow light. That same board also gives "failed to talk to bootloader" error and will not upload FW. I'm trying the original FW now but I've tried the latest beta also.
The other board just gives a solid yellow but also gives the failed to talk error.
Now one of these boards last night took the latest FW and charset. I don't remember which one but today if I try to do the same thing on both boards, they both fail. I'm going to reburn the bootloader again.
I've got a solid 12v on video side so it shouldn't be a problem with that. Both red lights are bright.
Are there any other tests I can run with avrdude?
Sandro in the end I was able to get CT to upload the firmware to one of the boards after writing the bootloader to both of them. One the one board that took the firmware and charset upgrade, it still doesn't output video and I still get the EEPROM error whe I try to read from the board.
On the second board I did the bootloader process again, thinking that something might have went wrong but it passed that fine and verified 100% but I get the "failed to talk to bootloader" error in CT.
Not sure where to go from here or this really indicates a hardware error. All the lights seem fine on both boards and the one I can upload firmware and charset without a problem.
On the one that I can upload fw to, I tried going back to CT 2.1.2.0 and FW 20 and when I do that, it allows me to read from the board without getting the EEPROM error.
I ran your EEPROM erase sketch and the board that is better and doesn't give the bootloader error in CT, took the sketch. The other board that also passes the bootloader reburning but doesn't accept FW in CT is also not accepting the sketch. It gives this error:
stk500_getsyunc(): not in sync: resp-0x00
OK I'm getting somewhere with one of the boards. I went back to ArduCAM OSD Config 2.1.2.0 and uploaded the v2.0 hex and for the first time the EEPROM problem got solved. I saw it update and now I can finally READ from the board but I still don't have any video output.
The only thing I didn't do was update the charset because I wasn't sure which one to upload. It should have the latest charset from the r552 but that's probably not what should be there? What charset should I upload to it?
So it seems there is some problem with the r552 CT??? I was never able to solve the EEPROM issue with that.
If I could get this working with 2.0 I would try to upgrade again to minimextra but still I need to get the video working first.
I'm having a problem with a minimOSD board. I uploaded the latest copter firmware (in minim extra) and then after updating the character set, it stopped outputting video. Other than that the board is ok but I just get the blue screen on my monitor.
If I try to read from it, I get an EEPROM error. I have another board that took the FW and char set update fine but also has this EEPROM error if I try to read from the board. I have a Jdrones 1.0 board and I'm powering the video side with 5V but have also tried it with 3S battery.
Any idea what could have happened? Also the red light on the video side is about 25% the brightness of the ftdi side. On my working board the lights have the same intensity so it seems something is not working right on the video side and pulling too much power or not getting enough?
I've been playing with my MinimOSD all day yesterday. I am just getting started too. Looks like I came in a few days after the wiki updates, so I haven't been having nearly as bad of a time :)
That being said, I did find a few things to watch out for. Most notably is that the Config Tool (CT) by default has some fields overlapping others. For example, the throttle percent is overtop the clime rate. That happened with the code from here: http://code.google.com/p/arducam-osd/downloads/list
I then tried out the minimosd-extra http://code.google.com/p/minimosd-extra/downloads/list pre release version r458 and it looked like that had been resolved. I did notice the multi-screens on this pre-release version did not seem to be working. I have 'mode change' as my screen switch mode, and when I went to screen 2, I only see the ham callsign, not a single other field. Also, when booting up while the APM is already on, it will show the boot progress bar and 9 out of 10 times, it will just not show a single overlay on the screen, just the original video (AVR crashing?). When I boot the APM and OSD at the same time, this seem to never happen.
For my purposes it has been working great though! Keep up the good work!
I've implemented all of the changes to the data stream rates and insured that I had the latest Charset and firmware. I've actually gone to the OSD extra firmware.
My Panel 2 option is still not functioning, when I switch panels, it just goes to the video feed with no overlay at all now. Not critical to me at this point though.
I am happy with my Battery % indicator now; it appears to reset itself back to 99% whenever you reboot APM regardless of battery charge state. It then counts down based off of current flow. (I'm guessing it bases this off of mAh that is set in Mission Planner). As long as you boot on a fresh battery this seems to work well.
After learning that RSSI is not implemented in ArduCopter 2.8.1, I've unselected the option in my panel. Hopefully this will be working some day as this is a very important feature.
Thanks again for the help Chris, Sandro and Gabor.
Elvis
Chris, Sandro, and Gabor,
Regardless of whether this thing works or not, this type of support makes me glad that I purchased it and I would gladly purchase from 3DR again. I'll try all of your recommendations and report back with my results.
Thank you guys so much for the help,
Elvis
-
1
-
2
of 2 Next