XBIB-U Digi International/Maxstream, XBIB-U Datasheet - Page 54

no-image

XBIB-U

Manufacturer Part Number
XBIB-U
Description
BOARD USB ZIGBEE MOD PRO
Manufacturer
Digi International/Maxstream
Datasheets

Specifications of XBIB-U

Design Resources
XBIB-U Shematic
Accessory Type
Interface Board
For Use With/related Products
XBee and XBee Pro Radios
Lead Free Status / RoHS Status
Lead free / RoHS Compliant

Available stocks

Company
Part Number
Manufacturer
Quantity
Price
Part Number:
XBIB-U-DEV
Manufacturer:
DIGI
Quantity:
20 000
XBee/XBee‐PRO™ OEM RF Modules ‐ 802.15.4 ‐ v1.xAx [2007.05.031]
3.4. API Operation
3.4.1. API Frame Specifications
API Operation (AP parameter = 1)
API Operation - with Escape Characters (AP parameter = 2)
By default, XBee/XBee-PRO RF Modules act as a serial line replacement (Transparent Operation) -
all UART data received through the DI pin is queued up for RF transmission. When the module
receives an RF packet, the data is sent out the DO pin with no additional information.
Inherent to Transparent Operation are the following behaviors:
As an alternative to the default Transparent Operation, API (Application Programming Interface)
Operations are available. API operation requires that communication with the module be done
through a structured interface (data is communicated in frames in a defined order). The API spec-
ifies how commands, command responses and module status messages are sent and received
from the module using a UART Data Frame.
Two API modes are supported and both can be enabled using the AP (API Enable) command. Use
the following AP parameter values to configure the module to operate in a particular mode:
Any data received prior to the start delimiter is silently discarded. If the frame is not received cor-
rectly or if the checksum fails, the data is silently discarded.
When this API mode is enabled (AP = 1), the UART data frame structure is defined as follows:
Figure 3‐01. UART Data Frame Structure:
When this API mode is enabled (AP = 2), the UART data frame structure is defined as follows:
Figure 3‐02. UART Data Frame Structure ‐ with escape control characters:
Escape characters. When sending or receiving a UART data frame, specific data values must be
escaped (flagged) so they do not interfere with the UART or UART data frame operation. To escape
an interfering data byte, insert 0x7D and follow it with the byte to be escaped XOR’d with 0x20.
© 2007 MaxStream, Inc.
• If module parameter registers are to be set or queried, a special operation is required for
• In point-to-multipoint systems, the application must send extra information so that the
• AP = 0 (default): Transparent Operation (UART Serial line replacement)
• AP = 1: API Operation
• AP = 2: API Operation (with escaped characters)
transitioning the module into Command Mode.
receiving module(s) can distinguish between data coming from different remotes.
API modes are disabled.
MSB = Most Significant Byte, LSB = Least Significant Byte
MSB = Most Significant Byte, LSB = Least Significant Byte
Start Delimiter
Start Delimiter
(Byte 1)
(Byte 1)
0x7E
0x7E
MSB
MSB
(Bytes 2-3)
(Bytes 2-3)
Length
Length
LSB
LSB
Characters Escaped If Needed
API-specific Structure
API-specific Structure
Frame Data
Frame Data
(Bytes 4-n)
(Bytes 4-n)
Chapter 3 ‐ RF Module Configuration
(Byte n + 1)
(Byte n + 1)
Checksum
Checksum
1 Byte
1 Byte
     54

Related parts for XBIB-U