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:
Code:
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<CR>
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