I am using your code to send data from my xbeepro2b coordinator to a xbeepro2b router.
When I change the pic you selected to PIC18F4550 I get the following errors:

Clean: Done.
Executing: “C:\MCC18\bin\mcc18.exe” -p=18F4550 “USARTio.c” -fo=”USARTio.o” -D__DEBUG -Ou- -Ot- -Ob- -Op- -Or- -Od- -Opa-
C:\Users\Puchito\Desktop\Senior Project\New folder\Project\New folder\API\USARTio.c:60:Error [1205] unknown member ‘RA7′ in ‘__tag_33′

C:\Users\Puchito\Desktop\Senior Project\New folder\Project\New folder\API\USARTio.c:60:Error [1118] scalar type expected in ‘while’ statement

C:\Users\Puchito\Desktop\Senior Project\New folder\Project\New folder\API\USARTio.c:129:Warning [2054] suspicious pointer conversion
Halting build on first failure as requested.

Any advice to fix these errors?
What should I configure to fit the program to PIC18F4550?

I have a problem triggering digital output (like DO0) on the remote ZigBee.

Case 1:
I know I can trigger it like this:
- setting digital input on the base ZigBee
- setting digital output on the remote ZigBee (DO LOW)
- and if configured right the input state on the base ZigBee is transferred to the digital output on remote ZigBee

I managed to do that, but I would like to trigger it via data packets.

Case 2:
So I tried with setting API packets that set the digital output on the remote ZigBee. I managed to change the digital output on remote ZigBee with commands ATD0=4 (DO LOW) ATD0=5 (DO HIGH).

DO LOW API command:
7E 00 10 17 05 00 13 A2 00 40 08 C9 80 00 02 02 44 30 04 21

DO HIGH API command:
7E 00 10 17 05 00 13 A2 00 40 08 C9 80 00 02 02 44 30 05 20

Problem:
But the problem I have is that sometime the communication between the base and remote might be lost. And if the digital output on the remote ZigBee is set to 3,3V (DO HIGH) and the communication is lost, the digital output would stay at the 3,3V. I want it to “reset” to 0V. In “case 1″ when I tried to trigger the digital output with digital input, you can set the reset timer for that digital output (command ATT0) and it did the work (the digital input reset to value 0V), but you can’t use that in the case 2.

Question:
Does anybody know what is the API format of the packet to simulate case 1 – I/O line passing (case 1 data packets)?
Do you have any other ideas how to “reset” the digital output to 0V.

thanks for your tuto.

I try to develop a network with one coordinator and four end-devices.

in a first time, i send at command to switch adress destination, but this was very very too slow. ( about 2s)

So i decided to use API mode:

1- I send the At command ATAP 1 to enable API on coordinator module without change module firmware (10A1)

2- So when end-device send data to the coordinator ( with X-CTU, or a C function), coordinator can received a API sentence with the data.

3-But when coordinator send data in API sentence ( with mine or your function) to a end-device, none data are sending. I use a RS232 analyser to be sure.

4- When coordinator send AT command with API sentence, xbee module put the corresponding answer.

So my questions is :

A) Does it REALLY necesary to load Coordinator firmware on coordinator zigbee to send API sentence to end-device?

B) When i try to load API firmware ( ZIGBEE PRO COORDINATOR API (BETA) version 8114 for coordinator or ZIGBEE PRO ROUTERAPI (BETA)version 8314 for End-Device ), i always have a Big problem, when X-CTU want to send AT parameter whereas i check API enable: It stop with a failed message. X-CTU can’t recognised the module, and i can’t do anything!!Have you any suggestions?

C) If coordinator with API Enable can receive data from end-device with API Disable, Does End-Device with API Disable can receive data from coordinator module with API Enable ?

Best Regards

If my USART pin (RC6/RC7) already using for connect with the MCP2551 (can bus transmitter), how can i connect with xbee?