|
| From: | Edixon Giraldo |
| Subject: | RE: [Paparazzi-devel] Xbee pro modules won't communicate |
| Date: | Mon, 9 Aug 2010 22:09:17 -0500 |
|
Hi Nathan, thank you for the information. Unfortunately, I don't have that type of modem, so, I don't think it will work. I have the Xbee Pro 900 MHz model XBP09-DP and it won't let me select which one is the end device or the coordinator at. It is a mesh system and it won't have an option to input a PAN number either. I am already tired of messing with this modem. I checked the airframe files and it is exactly as it is supposed to be according to the wiki and forums. I am using the PPRZ Transport and not the XBEE in the airframe. I already checked so many times the baud rate in the airframe code and in XTCU to make sure. Verified also the control panel.xml to match the baud rate. I changed pin locations also and nothing. FYI, I am using the Sparkfun USB transport to connect the ground modem and the Sparkfun regulator to connect the air modem. For the regulator board, I have connected the 3.3V, GND, DOUT, and DIN pins and plugged in directly to the TWOG. It is very exhausting! I ran out of options. I might be in the code. Maybe I have to use the XBEE uplink instead of the PPRZ serial transport. Thanks. Eddie. From: address@hidden Subject: Re: [Paparazzi-devel] Xbee pro modules won't communicate Date: Tue, 10 Aug 2010 09:41:11 +1000 To: address@hidden Hi Eddie, Please see this piece of information that David from PPZUAV sent me about configuring my modems. After doing what he said, they just worked. I asked about the OS because the auto stuff isn't as supported on Linux. So X-CTU will run under Linux but don't expect the auto-read of the modem config to work. So I ask because if you're on Windows I don't need to bother explaining all the stuff for Linux. Just know the BPS default is 9600 so in X-CTU you must setup the PC interface to be using 9600. Don't change anything else. Then in the modem config window set the modem type as XBP24-B I think. The only menu you need to change is the Modem and then the Function set to the right of that. There are 2. One for each. Wire Antenna: Select ZNET 2.5 ROUTER/END DEVICE AT RPSMA: Select ZNET 2.5 COORDINATOR AT The reason is you have modems capable of providing digi-mesh networking. You can fly multiple aircraft at the same time. You would just set all the wire antenna ones as ROUTER/END DEVICE modems. The AT is important. Using the "TRANSPARENT" Protocol in the configuration means you're interfacing with the modem using standard AT command set. As sent from the factory I think they are all END DEVICE but using non-AT (API) command set. So you would need to change your aircraft config to support that. But then the FTDI / serial wouldn't work. So just set them up as AT first. You're not going to need the API mode unless you fly multi-aircraft. Do the Write ... if you get a dialog read it. The LED should go out as you are writing to the modem. If when you plug in the modem you don't get a light then you will for sure get a message. What you do is set everything. Then click write...after a few seconds a dialogue pops up. Essentially just telling you to remove the modem and replace it. On placing it in the socket the dialogue should go out and it should start programming. Kindest regards, Nathan Aherne Reddog Technology Web: www.reddog.com.au Email: address@hidden Mob: 0402 555 080 On 10/08/2010, at 2:44 AM, Edixon Giraldo wrote: _______________________________________________ Paparazzi-devel mailing list address@hidden http://lists.nongnu.org/mailman/listinfo/paparazzi-devel |
| [Prev in Thread] | Current Thread | [Next in Thread] |