Dang it. I've flashed this thing 15 times and it still comes up as ver 1.8.
I've used different computers, different FTDI cards. Different usb cables, different usb ports. Each time I flash it, is says Done! Like it was successful.
Then all I get is; ArduCam OSD and Waiting for MAVLink Heartbeat, at the top it says v1.8.
I'm using the Sparkfun FTDI card as I like it best, and it powers the OSD. I have the 5v bridged (no 12v input).
TX from the APM2 connected to the RX on the OSD. No connection on the OSD TX since I should be adding the 3dr radios soon.
I'm powering the copter with my lipo, no USB, and I took it outside and waited for a GPS lock. No change.. Waiting for MAVLink heartbeat.
I'm sure this is because it says v1.8, not 1.9, but I've tried the files from the package, and I tried the 1.9 .hex file. It's still v1.8.
How the heck do you flash this thing? Because using OSDConfig doesn't seem to work.
Ah, one more bit of info.
I edited the screen using OSD Config, and saved it to the OSD, then on another computer, I read it back into the editor., So I know reading and writing is working. I almost think the firmware files on the download site are the wrong version or something.
The documentation is wrong.
You hook it up tx - tx and rx - rx.
Wish I knew this 7 hours ago.
I got it to work first by flashing the firmware from here:
And by connecting the tx line, and reversing it with the rx line.
And it looks amazing btw......
Are you using the plastic housing that ships with the APM2? If so the Tx and Rx labels on the plastic housing are reversed, that could have been your problem.
*sigh* - Yep. You guessed it.
Eddie: I just noticed that, too. It's correct on the APM 2.5 enclosure, which is the current one, and if people use the standard telem cables they won't have to pay attention to that labeling, but I'm sorry for the confusion it caused!
No problem Chris. I connected everything up before I put it in the case&plane. When I reconnected it in the case I had to double check but it only took me a few seconds. :)
Bill, sorry about the confusion! If you can let me know what to correct in the manual, I'd be happy to do it.
Chris, it's the case labeling, so the docs are right....