Discussions

Replies

  • 3D Robotics
    Chris Anderson May 20, 2011 at 12:13am
    For anyone still have trouble connecting via Xbee, please ensure that you're powering APM with an ESC/Lipo, not just USB. USB power is not enough for both APM and an Xbee. (You can sometimes tell that you're browning out because you just get the red C LED blinking dimly and slowly.)
  • Moderator
    John Church May 12, 2011 at 5:51pm
    Funny... All was good with the initial release. I've now updated and see the issue stated in this thread LOL!  I've filed an issue and will start hunting...
  • madhuran wilson May 12, 2011 at 8:06am

    yea i guess im ok with CLI with USB only, it was like that with the NG code too,

     

    Pid seems to be working and that is what is most important  for me right now. the charts are laggy, but im sure in time it will be fixed..

     

    happy flying

  • Christopher Cooper May 12, 2011 at 5:59am
    Ok, I'm using the latest trunk code now and the Mavlink mission planner stuff seems to work through both USB and the xbees now. CLI is only USB but I can live with that.

    However the sensor data is still read in at a much slower rate over xbees, almost 1Hz. I see a lot of bad packets in the text window.
  • madhuran wilson May 11, 2011 at 4:54pm
    YES.. ok i just installed through MP and the PID works... buuuutt.  still getting giberish data thru the AC2 setup, initial set up window...
  • Developer
    Michael Oborne May 11, 2011 at 4:34pm
    Try uploading a new firmware now, this should fix the alt and xbee issues.
  • Vincent Mees May 11, 2011 at 11:21am

    I just did an svn update of the 2.0.2 code and also the MP.

    Loaded the 2.0.2 code with arduino.

    Did setup with MP and noticed there is a line "xbee" added when you get the choice betweeb setup en sensor.

    After setup I connected with USB to the sensor pages and everything looked fine.

    Then I switched to Xbee (900) at 57600 and it works!!!!

    I can go into sensors, PID settings, HK GCS, ...

    One thing I noticed is that the graph in the GCS MAVLINK doesn't get any info.

     

    Thx guys, keep up the nice work 

     

    Ok now lets get this thing in the air!!!!

     

  • madhuran wilson May 11, 2011 at 10:40am

    i'm having similar issues as well, my quad worked with the pirate code so i know hardware is good.

     

    i could get the sensor data but when i try the terminal i get giberish, and the pid tuning i get the above mentioned error.

     

    when i use the mission planner to load the code where is that code stored so that i can go in and try modifying it?

  • Russell B. Sutton May 10, 2011 at 10:03am
      I have tired with the trunk updates,  different baund rates, I've even tried mixing it up a lil with different defines and baund rates. The most it will do is connect but no data.   USB connects to everything well.
  • Developer
    Michael Oborne May 9, 2011 at 6:53am
    that error message indicates there was dataloss, during the connection.
This reply was deleted.

Activity