Hey, does anyone think I can do this with the XBee’s
I want to try and hook up an XBee on the ABB and on to a SSC32 and on to my PC
I want the ABB to send and receive to/from the SSC32 and at the same time ( with flow control I guess ) to have the SSC32 rend receive to my PC.
IS this possible with these devices? ( I’m just trying to get a feel for the multi-point functions of the XBEE’s )
Yes, you can do this. My experience is with version 1 of the XBees running not in API mode. In this mode, the two XBEES on the BB2 and SSC-32 could both simply set their destination to the same number of the one on the PC. On the PC It would be easy to receive from both and depending on which one it wants to talk to, it would enter into command mode and set the destination. You can do this with a simple function like:
wNewDL var word
SetXBeeDL[wNewDL]:
pause 20 ; have to have a guard time to get into Command sequence
serout cXBEE_OUT, cXBEE_BAUD, "+++"]
pause 20 ; have to wait a bit again
serout cXBEE_OUT, cXBEE_BAUD,"ATDL ",hex wNewDL, 13, | ; Set the New DL
"ATCN",13] ; Exit command mode
return
Note this code assumes that you have set the command timeout modes to fast otherwise you have to wait for 2 seconds to enter into command mode. Also this code should be updated to get rid of the responses that come back from the XBEE. In this case I would expect three responses: OK
The reason why I put this code here is to show that to go back and forth between multiple destinations, requires some time in timeouts which may not work well in your case. Another approach is to have the XBEE go into API mode. In this mode you don’t send text string but instead build binary packets to send back and forth. A couple of advantages. 1) when your PC receives a packet it knows it is from (SCC or BAP) and 2) No time delay for switch who you are sending to. You simply build the packet with the destination you want and send out the packet. At some point I may try converting mine to that, but…
Kurt
Thanks Kurt,
What I’m after is to be able to have my Mini Hex Bot run as a normal " Xan code " bot with PS2 wireless for over-ride and also have Robot Realm doing some input/output with the connected camera.
A scenario would go something like this…
The bot is semi-auto right now with sensor feedback and ps2 control, as it’s walking around it may see a colored ball and what it I would like it to do is take control via the Robot-realm program and move towards, away, shoot or whatever I program the response to be and then give back the control to the ABB.
I know there is going to be some timing issuse but I think it can be worked out.
I will be using the V 2.5 2mw XBee’s ( I couldn’t cash in on the giveaway but I’m buying them anyways )
Any help?
Here’s the problem…I’ve finally got these devices and have been play with them on my SSC32 V1 to computer connection.
I’m having issues with the packet timing output “I’m guessing at this” because the SSC32 is receiving 8 bytes and then delaying for a bit then receiving again maybe a couple of bytes and so on.
I’m running the XBEE’s 2.5 version in supposed to be “transparent mode” and it does work accept for the delay.
here are my settings.
PAN ID , Node ID and such are correct I understand that part.
Baud = 115200
parity = no parity
Packetization timeout = 0 ( this has me troubled…according to the manual this setting should allow the data to pass straight through the radios to the device with no delay )
CTS flow control is enabled ( i’ve tried disabled also )
I’ve wired the module up to the SSC32 like the BlueSmirf with CTS and RTS connected to each other and also without being connected, and it made no difference.
any idea’s?
Dave
If I keep on talking to myself long enough I’ll figure this out…
in the meantime if anyone would like to step in that would be great…
I have the Xbee’s talking to each other in AT mode…the router/end device will stream data to the Coordinator device but the Coordinator is sending data out packetized and I don’t understand or seem to be able to change it so that I can stream out to the router/end device.
any help would be appreciated.
Hi Putt Putt,
Sorry I can not help very much as I have been using version 1s and not version 2.5s. I want to try my stuff out with 2.5s to see the differences but I bricked one of them… Also I am not with my XBEE setup right now so I can only give some general things that I would look at… On the societyofrobots.com forums someone else was having problems setting up a system 2.5 XBEE system and finally solved it and suggested the best site he found was: humboldt.edu/~cm19/XBee%20setup.pdf
I am not sure what adapter cards you are using to connect the XBEES to the different components. My guess is you are using the regulated explorer on the SSC-32 and the USB XBee explorer on the pc. My guess is your mentioning that you did not get the giveway…
I dont think RTS/CTS will help you here. Probably not needed on the PC side and on the SSC-32 you would then need to bring out another IO line. I mentioned this in the thread about converting the DIY remote control to XBEE. Also issues on how the CTS is processed…
Good Luck
Kurt
Thanks Kurte,
It’s only a matter of time and I’m sure that myself or someone will figure out these devices
I’m using the XBEE 24-BSIT rev C chips and yes the Sparkfun REG Explorere and Sparkfun USB
As I mentioned I have them connecting to each other but not a true transparent RS232 ( streams one way but packets the other ).
I’m going to keep at it and as more of these devices get out there there will be more info ( I hope )
and thanks for the link i’ll check that out.
Dave
UPDATE:
http://i219.photobucket.com/albums/cc277/Roboguy_2007/Robots/T-Hex006.jpg
This is my latest Hex Bot using three X-Bee’s ver 2.5 , SSC Ver 2, ABB Ver 2 , Atom Pro 28m and modified Phoenix code.
The bot also has a ping sensor, a 3 axis accelerometer and an IR sensor.
The robot is able to talk ,wireless, between the ABB and the SSC-32 and also the PC at the same time.
My reason for this is to be able to receive wireless video from the bot, process it with Robot Realm and then send serial data to the SSC-32 for say head tilt and pan while the bot is being controlled by the PS2 or it’s sensors. All the serial traffic control is handled by the X-Bee’s and works quite well.
