Transmission from AT to API radios and format data

XBee & XBee Gateway XBee - Zigbee
1

Hi

I bought a couple of XB24-Z7CIT-004 radios and a book from Robet Faludi to begin, but I have some troubles, let me explain it.

I configured one radio like coordinator with ZIGBEE COORDINATOR API(2170 Version) function set and the other one like ZIGBEE ROUTER AT (2270 version) and:

Base(Coordinator API)
ID=3332
SH=0013A200
SL=40614388
DH=0013A200
DL=40692C1C
BD=3

Remote(Router AT)
ID=3332
SH=0013A200
SL=40692C1C
DH=0013A200
DL=40614388
BD=3

The Router(AT) is conected to PC through XBee xplorer (sparkfun) and the Coordinator(API) to Aruino duemilanove through XBee Shield, plus a LCD to check the data recived.

I´m sending some data through X-CTU terminal to test…

The question is ¿who creates the packet? the router or the coordinator.? or how the router send the data?

And how recibe the data the coordinator? I mean, ¿what base?, Hex, Dec or ASCII?

because I can´t read the data correctly in LCD

finally

if I have the same configuration but add to router the next comands:

ATJV1
ATD02
ATIR64

to get an analog signal through analog input D0 and send it automatically each 100 milliseconds to coordinator.

The router send just the data from ADC and the coordinator form the final packet?

if so, How the data from ADC are send , in DEC, Hex o what format?

Thanks in advance and sorry for my bad English.

2

Because you have API on the coordinator (which is good), using XCTU is impractical. Write a small Python, C or VBasic code on a PC and talk via the serial port.

You need to form the API frames sent serially into the API Coordinator (again, this is what you want - harder upfront but easier once you have multiple remote XBee).

The AT Router will just talk raw serial, so sending an ‘A’ will cause the ASCII code for ‘A’ to show up as payload from the API Coordinator.

Everything received via the APi Corodinator will be pure binary, so a ‘terminal’ program will not be useful.