Shop OBEX P1 Docs P2 Docs Learn Events
Receive problem with Xbee! — Parallax Forums

Receive problem with Xbee!

MicrocontrolledMicrocontrolled Posts: 2,461
edited 2010-02-22 20:33 in Propeller 1
I can't seem to get this. I just got my Xbee's and got the loopback working with X-CTU. I then used X-CTU on this program attached to transmit. It worked. Then I got it to recieve it and put the output on a display. No go. Checked all connections and I have it in AT (not API) mode so the PUB routines should run fine. However when I type into the terminal on the X-CTU program then I get nothing on the prop. No connections changed from the time of the transmit test, just nothing. Can someone please tell me what is wrong? I am using TX as DIN and RX as DOUT. Programs are attached. Thanks in advance.

Micro

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Don't click on this.....

Comments

  • edited 2010-02-21 10:49
    Hi microcontrolled, I don't know if this helps at all, but the code you attached works fine when the AT commands are removed, (I'm using a pair of easyPROPs). I'm just starting to play with XBEE myself, good luck - let us know how it goes.

    TonyF
  • MicrocontrolledMicrocontrolled Posts: 2,461
    edited 2010-02-21 13:19
    THANKS A LOT!!! It works perfect now!!!!! smile.gif

    Micro

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    Don't click on this.....
  • mugurmugur Posts: 105
    edited 2010-02-21 21:41
    microcontrolled, can you post the working code please?

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    images-team.ro
  • MicrocontrolledMicrocontrolled Posts: 2,461
    edited 2010-02-22 18:16
    Here is the working code

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    Don't click on this.....
  • kalmkalm Posts: 1
    edited 2010-02-22 20:33
    I ran into similar issues when I tried to use the AT_ConfigVal() method. I switched mine to use the following type of setup:

    
      XB.start(7, 6, 0, 9600)
      XB.AT_Init
      XB.AT_Config(string("ATID 5555, MY 0, DL 1"))
    
    
    



    I was able to get some simple 2-way communication working between props this way by specifying the MY and DL numbers between the devices. This way you can string multiple commands at once and this appeared to work for me.

    Keep in mind, if you don't specify the AT commands in your program then your XBee has to be configured with the X-CTU software instead. These settings do not match what X-CTU will show since I'm not writing these values to the permanent storage. I think if you issues the "ATWR" command it will store these settings permanently, but I prefer to have the propeller set it up each time.
Sign In or Register to comment.