Things finally got worked out, the copter is a blast to fly, Everything is working as it should. There were some problems when the copter arrived, I had it built and supposedly configured by the folks at 3DR and the basic copter was set up but all the options had to be completed by me like the OSD, Sonar, Radio (also purchased from 3DR) and a couple of other things that I can't remember. This site was fantastic for all the support needed and I complement everyone involved.
Sincerely and very pleased,
Replies are closed for this discussion.
Hey Steve, what was the issue with the OSD?
It's likely your unit came with a MinimOSD board with outdated firmware. I had to order an FTDI adaptor in order to update the firmware with the Arducam utility. After updating to 2.0 firmware it could decode the Mavlink data stream.
If you wish to use a single laptop in the field for GCS and FPV/OSD you'll probably want to order two more things:
- An adaptor to power the barrel connector on your FPV receiver from an extra LIPO.
- A USB adaptor to receive and display the NTSC video.
It displays but not information is updated you see everything but it's like it isn't seeing any of the data changing...
As Rich mentioned, you may need to update the firmware and the Character set (Char Set) on the minimOSD.
FTDI cable- useful to have for future updates as well.
OSD Config tool- This is the software interface for updating firmware and character set
Important note before proceeding:
Defective and fuzzy chars are the result of a faulty character updating. Max7456's internal memory is really picky about voltage level during a charset update. Usually it happens with some PCs with lower USB voltage. The only way to fix that is updating the charset by feeding the board properly. Just making sure it has around 5V there.
I hope this solves the problem for you.
Steve, there is an issue with the "y" cable.
You'll notice that the white signal line on the regular servo connector is attached to the middle line of the df13 connector.
It needs to be attached to the line next to the red 5v line on the df13 connector.
We identified the mistake in MFG, and it was corrected as of two weeks ago. We are in the process of shipping new cables to those that were affected.
You can do a quick fix yourself, and I will make sure your cable goes out today.
We have also updated our test procedures from the visual check we were doing on the OSD output to validating that data was available and changing on the display.
Also keep in mind that because the OSD only uses the Rx line, you need to connect to the mission planner with the wireless telemetry before the data will start being transmitted out to the "y" for both OSD and telemetry devices.
I apologize for the inconvenience on the cable. Please let me know if you have any questions.
Ordered a RTF on the same premise, crossing my fingers I don't have to send anything back as I live on the other side of the globe in the middle of nowhere.
We'd love to hear how it goes at feedback[at]3drobotics.com
Let me know what happens, I will be glad to give you my knownlege on how to fix issues that aren't complete on an RTF product. If you didn't order a TX, OSD, FPV, Sonar or Gimbal you should have any issues, but on mine every add-on was not configured or setup.
See my updated edits to the thread at the top for more information.
Steve, i would be very disappointed as well. That sounds like an "epic fail". Besides this the motorshafts are way too long and will increase vibration and stress to the motor ball bearings especially when used with "heavy" APC SF props. That seems to me like a real design flaw. General Tip: Always check your propellermounts loosing a prop is never fun...
Have fun anyway and happy landings!
Richard can you give me a little more info on using just one laptop.
I'm not clear on exactly what adaptor for the FPV receiver or the USB adaptor?
Can you tell me were I can get these?