Discussions

corrupt Xbee

Posted by Greg Fletcher on March 29, 2010 at 7:07pm
First of let me say I know not to power up the system with the Tx to the Xbee connected. I have bricked mine several times during testing. I installed a dip switch just for this. I am putting my Ardustation in a nice DIY box and was going to instal a switch on the Tx to the Xbee--Then it hit me(ouch)..
Why doesn't the same thing happen to my Ardustation. It has the Tx connected in case you want to use it. After a zillion power ups the GS never had this problem. I am going to put a delay first thing in the      < void init_ardupilot() > in the  <system>  tab and add this   <delay(200);>
The only difference is the Ardupilot starts sending data right away on start up. The ardustation doesnt send any data on start up.
Couldn't hurt. Haven't tried it yet cause I have soldering to do. Any brave souls who nkow how to recover from this, give it a try and let us know how it works out. I will try it soon.

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

Join diydrones

Email me when people reply –
Follow

Replies

  • Developer
    Jason Short March 29, 2010 at 10:41pm
    I wonder if the power-on bricking isn't caused by the +++ in the telemetry stream.
  • 3D Robotics
    Chris Anderson March 29, 2010 at 10:15pm
    Sounds good--let us know if that does the trick and we'll incorporate it into the main code.It really is a pain, I know. In the meantime, I assume you're gotten good at unbricking the Xbees by following the instructions in the manual?
This reply was deleted.

Activity