LibrePilot Forum
General Category => General Discussion => Topic started by: Spz0 on January 04, 2017, 08:13:06 pm
-
Hey all.
I'm running a revolution mini, first off,with latest gcs (black rhino) installed.
I've flashed my minimosd with the correct firmware from the lp wiki on minimosd. I have telemetry enabled on main port and baud set to 56700,yet when I power up, I get stalled on "waiting for mavlink heartbeat".
I have tried flashing all 4 firmwares listed on the wiki and all have the same issue. I have successfully ran a minimosd micro on the same flight controller so I am confident it's not an issue with the fc.
I'm running all this on a pdb detached from a frame (escs installed but not motors).
This is the osd I'm trying to program.
http://www.ebay.com/itm/131844427099
Does anyone have any insight as to what could be wrong?
Thanks in advance!
Sent from my SAMSUNG-SM-N920A using Tapatalk
-
Hi,
If you see "waiting for mavlink heartbeat", the MinOPOSD firmware is not flashed.
Just running the original APM fimware flashed by default.
You should try the MWOSD as a firmware replacement, not depended from the release/uavo set:
https://librepilot.atlassian.net/wiki/display/LPDOC/MWOSD+Setup
-
Interesting. The fw flasher indicates a successful flash. Let me reflash it again and report.
Sent from my SAMSUNG-SM-N920A using Tapatalk
-
Flash successful again (with mwosd this time). Will test in a few hours when I'm home and report back.
Sent from my SAMSUNG-SM-N920A using Tapatalk
-
OK, so the arducam osd config tool is showing it uploading correctly, but it's not uploading. Will not flash charset either, even though u get pop ups stating the flash was successful.
Any clues?
Sent from my SAMSUNG-SM-N920A using Tapatalk
-
In addition, I can adjust settings in the config tool and they write just fine (call sign for instance). Save them, unplug then replug and it will read the data pulled correctly.
I am really confused as to why it isn't flashing.
Sent from my SAMSUNG-SM-N920A using Tapatalk
-
Trying the arduino software is worse. Lol I error out
(http://uploads.tapatalk-cdn.com/20170105/ca8a72aa33ba33fdaef0a09fc5020e13.jpg)
Sent from my SAMSUNG-SM-N920A using Tapatalk
-
Be sure you keep the "#" in front
#define MINIMOSD
#define LIBREPILOT
** Using MinmOPOSD the callsign should not be stored in config (not used)
Seems you are not able to flash firmware and the issue should be same for MWOSD.
You can simply try to send MavLink teleletry (set the port you use for OSD with Mavlink) without osd firmware changes and get some OSD indications.
-
@f5soh thanks a lot for coming in and helping me troubleshoot this issue. :-) I the comments slashes out but I also took the hash out as well. I guess I'm used to Java programming. I will put the hash back in and reflash and report back
Sent from my SAMSUNG-SM-N920A using Tapatalk
-
Here's a silly question, what board is this? Arduino pro?
Sent from my SAMSUNG-SM-N920A using Tapatalk
-
I think information is here:
https://librepilot.atlassian.net/wiki/display/LPDOC/MWOSD+Setup#MWOSDSetup-UsingArduino
-
I think information is here:
https://librepilot.atlassian.net/wiki/display/LPDOC/MWOSD+Setup#MWOSDSetup-UsingArduino
Yeah, I've followed that tutorial already. It's straight forward unless something goes wrong. Lol.
I'm ony way home and will flash this damn thing again tonight. Will report back. Thanks man!
Sent from my SAMSUNG-SM-N920A using Tapatalk
-
OK, so I left the # in this time. It compiled alright AFAIK, but uploading is a different story.
See attached pic
(http://uploads.tapatalk-cdn.com/20170106/b615ca75a96bf4e086964c7dad351f0b.jpg)
Sent from my SAMSUNG-SM-N920A using Tapatalk
-
Looks like you added lines instead of modifying lines that were already there. That would explain why INFO_AIRCRAFT is 0 in one place and 1 in another place.
Then you have verify errors when you flash. That means it tried to write the new program, and then read it back to make sure it was written correctly, but there was a difference. You did not get a good flash.
-
Looks like you added lines instead of modifying lines that were already there. That would explain why INFO_AIRCRAFT is 0 in one place and 1 in another place.
Then you have verify errors when you flash. That means it tried to write the new program, and then read it back to make sure it was written correctly, but there was a difference. You did not get a good flash.
Funny thing is, that I did not add any lines to the code. I followed the tutorial on Librepilot wiki to a tee - downloaded all the files it stated and linked to.
I will go over and upload the config file in a couple hours when I have some free time.
It's interesting I'm having so many issues with this Arduino version, when I've owned 3 micros in the past that have all worked and flashed flawlessly (with config tool mind you, this is the first time I've used the arduino software only because config tool is proving unsuccessful on this particular chip). :-(
Sent from my SAMSUNG-SM-N920A using Tapatalk
-
You can simply download and flash the hex files form the page, using the ConfigTool.
But seems you have also flashing issues :P
-
Yes that is what I tried first because in the past that's all I have used is the config tool and Associated hex files. The config tool States a successful Flash , but when I booted up and plug it in to my display it has not Flashed. It's the same Ardu copter 2.0 firmware that came stock with the board
Sent from my SAMSUNG-SM-N920A using Tapatalk