Blogs

Developer

ArduPilot Config Tool Source Code Released!

Posted by Jordi Muñoz on July 5, 2009 at 9:30pm
The utility was written in Visual C#. I hope somebody familiar with C# is able to test the code in his failing setup and figure out the problem, nothing else, please don't ask me about of how integrate this code to another project because certainly I'm not an expert in C#. This code is intended for dudes that really have a basic knowledge in programming and believe can help. Just remember this code works perfectly in my PC, running Vista and using the Official FTDI cable.ArdupilotConfigTool.zip
E-mail me when people leave their comments –
Follow

You need to be a member of diydrones to add comments!

Join diydrones

Comments

  • Developer
    Jordi Muñoz July 6, 2009 at 9:04am
    Excellent Damon, the theory was correct. Sparkfun swap the the CTS pin for DTR. SO we just have to control both pins, this what arduino IDE does... =)

    Thank you very much!. =)
  • Damon Pipenberg July 6, 2009 at 8:54am
    Jordi,
    Thanks for posting the source. I changed the function restart_Ardupilot in form.cs to the following, and now both of my FTDI cables work properly - I have a 5V sparkfun cable and a the TTL-232R-3V3 cable. I didn't mess around with different delays too much. I imagine the delay could be shorter and would still work.

    I've attached an executable with this fix in it. If you are having problems uploading, please test and report back.

    private void restart_Ardupilot()
    {
    serialPort1.Open();
    serialPort1.DtrEnable = true; //Restarts ardupilot
    serialPort1.RtsEnable = true;
    Thread.Sleep(1000);
    serialPort1.DtrEnable = false;
    serialPort1.RtsEnable = false;
    serialPort1.Close();
    }

    ArduPilotConfigTool_Fix1.zip
  • 3D Robotics
    Chris Anderson July 6, 2009 at 3:20am
    Just a note from following the discussion in other threads: if you're having trouble with your setup, check the following:

    --Double-check your solder joints with a continuity checker, especially if you're using round pin connectors
    --Make sure you're using the latest FTDI drivers
    --Try it without the GPS connected.
This reply was deleted.