Firstly if this is the wrong sub forum to post this then I apologise and am happy to take it else where.
Gday, I purchased some second hand gear and really need a hand indentifying it and working out the best software/firmwar version I should be using and how best to eliminate my first setup issues.
Ive attached pics of the two boards. I think I can see there is a V1.4 board with a 2560 chip.
And the IMU I'm not sure about. On the back is printed HOTEL1.0
I also have a MinimOSD which seems to be pretty standard.
My initial issue is that when firing the gear up I get the 'Waiting for MAVLink Heartbeat' message. I feel I have the cabling correct as there is only one cable and using the wiki I can see that all wires in the header plug go to and from the correct pins of both the OSD and main board. That leads me to a maybe firmware mismatch, or faulty board.
I have fired the main board up in Mission planner and it seems to be ok although I havnt doen any radio cal or major setups yet.
I have fired the OSD up using the Config tool and it is able to receive a setup template and I can also retrive from the board and like I said it is passing video and giving the MAVLink Heartbeat message. Does it need to be outside to get a GPS lock before it will continue maybe?
I'd initially like to know how I can check the firmware of each board and move on from there. I believe there is limitations based on the 2560 chip. Im not after any upgrades or super duper options. Id just like to see it working. I was primarily afer the OSD but this was a bit of a bargain... or was it :(
Any assistance would be much appreciated.
Scott
You need to be a member of diydrones to add comments!
Replies
Make sure the match the black wire on the FTDI cable with the 'gnd' pin on the red board each time you plug it in.
As for the miniosd, you may need to upgrade it. When correctly wired to the telemetry port, and when telemetry is started after connecting from the ground station, the issue you report should go away.... However, only if the mavlink protocol used on the miniosd and the APM match.
A few months ago, the community moved from mavlink 0.9 to version 1.0. As such, some versions of firmware/osd are 0.9, and some are 1.0.
Upgrade both to a currency release.
In summary:
- buy and ftdi cable.
- assemble the boards
- attach the cable such that it slips over the pins that stick out the side, but make sure to line up the black colored wire with the 'gnd' pin, and red with the +5vcc pin. It will fit reversed, but it is very bad for the gear.
- read the wiki and setup for apm1. Other than what I said above, you will be just like the wiki, just follow along. Push new firmware from mission planner to the APM. Download the miniosd configuration tool and update it also.
Enjoy! Try HiL before flying for real.