Comparing Transparent and API modes
The XBee®-PRO 900HP RF Module can use its serial connection in two ways: Transparent mode or API operating mode. You can use a mixture of devices running API mode and transparent mode in a network.
The following table compares the advantages of transparent and API modes of operation:
| Feature | Description |
|---|---|
| Transparent mode features | |
| Simple interface | All received serial data is transmitted unless the device is in Command mode |
| Easy to support | It is easier for an application to support Transparent operation and Command mode |
| API mode features | |
| Easy to manage data transmissions to multiple destinations |
Transmitting RF data to multiple remote devices only requires the application to change the address in the API frame. This process is much faster than in Transparent mode where the application must enter Command mode, change the address, exit Command mode, and then transmit data. |
| Each API transmission can return a transmit status frame indicating the success or reason for failure | Because acknowledgments are sent out of the serial interface, this provides more information about the health of the RF network and can be used to debug issues after the network has been deployed. |
| Received data frames indicate the sender's address | All received RF data API frames indicate the source address |
| Advanced addressing support | API transmit and receive frames can expose addressing fields including source and destination endpoints, cluster ID, and profile ID |
| Advanced networking diagnostics | API frames can provide indication of I/O samples from remote devices, and node identification messages. |
| Remote Configuration | Set/read configuration commands can be sent to remote devices to configure them as needed using the API |
| Simultaneous Commands |
Query or set a configuration parameter while a pending command like ND is in progress. This cannot be done in Command mode. It is available in firmware versions 9009 or newer. |
PDF
