Hi All,
I have ArduPilotMega 1.x hardware and I have repeated problems with bricking zigbee modules that are connected when powering up (about 1 out of 4 power ups will brick my zigbee). I have seen suggestions to keep the zigbee unplugged until ArduPilotMega is powered up and then plug in zigbee. This is a pain in the butt!
I assume the problem is somehow in signals to the zigbee boot loader when powering up.
So my questions are: Is this problem solved in ArduPilotMega 2 hardware?
Or even better, is there a simple solution for ArduPilotMega 1.x hardware?
Thanks!
Replies
I haven't had any bricking problems in quite a long while with APM1 (2560) hardware [ I'm about to be jinxed].
The reason for the bricking is because radio's pin#3, the data in pin, has a shared function. When held low during power up it is a CONFIG pin. If it starts in configuration mode and there is a data stream present there is a better than zero chance that the radio will become RE-configured or populated with corrupted parameters.
The only simple, guaranteed, way to prevent this with the x-bee is to keep the Din [pin#3] disconnected until the radio is powered and has been powered for a moment. I have not found the time length stated in the data sheet but were talking less than 200mSec for sure.
I have upgraded my Bee's in the past with no problem. I got them from digi direct. The base is from DIY works perfect with it.
Yes, it's not an issue with APM 2. Very few people see the issue with APM 1 anymore, either. Are you using the latest code?