JF1R6-CR3-4I MaxStream, JF1R6-CR3-4I Datasheet - Page 55

Wireless Accessories 2.4Ghz ant U.FL fem to RPSMA fem cable

JF1R6-CR3-4I

Manufacturer Part Number
JF1R6-CR3-4I
Description
Wireless Accessories 2.4Ghz ant U.FL fem to RPSMA fem cable
Manufacturer
MaxStream
Datasheet

Specifications of JF1R6-CR3-4I

Technology/ Type
Cable Assembly
Lead Free Status / RoHS Status
Lead free / RoHS Compliant
For Use With
XBee Modules
XBee/XBee‐PRO™ OEM RF Modules ‐ 802.15.4 ‐ v1.xAx [2007.05.031]
3.4.2. API Types
Checksum
Modem Status
Data bytes that need to be escaped:
Note: In the above example, the length of the raw data (excluding the checksum) is 0x0002 and
the checksum of the non-escaped data (excluding frame delimiter and length) is calculated as:
0xFF - (0x23 + 0x11) = (0xFF - 0x34) = 0xCB.
To test data integrity, a checksum is calculated and verified on non-escaped data.
To calculate: Not including frame delimiters and length, add all bytes keeping only the lowest 8
bits of the result and subtract from 0xFF.
To verify: Add all bytes (include checksum, but not the delimiter and length). If the checksum is
correct, the sum will equal 0xFF.
Frame data of the UART data frame forms an API-specific structure as follows:
Figure 3‐03. UART Data Frame & API‐specific Structure:
The cmdID frame (API-identifier) indicates which API messages will be contained in the cmdData
frame (Identifier-specific data). Refer to the sections that follow for more information regarding
the supported API types. Note that multi-byte values are sent big endian.
API Identifier: 0x8A
RF module status messages are sent from the module in response to specific conditions.
Figure 3‐04.  Modem Status Frames
Example - Raw UART Data Frame (before escaping interfering bytes):
0x11 needs to be escaped which results in the following frame:
0x7E 0x00 0x02 0x23 0x7D 0x31 0xCB
© 2007 MaxStream, Inc.
• 0x7E – Frame Delimiter
• 0x7D – Escape
• 0x11 – XON
• 0x13 – XOFF
0x7E 0x00 0x02 0x23 0x11 0xCB
Start Delimiter
Start Delimiter
0x7E
(Byte 1)
0x7E
MSB
Length
LSB
MSB
API Identifier
(Bytes 2-3)
0x8A
Length
API-specific Structure
0 = Hardware reset
1 = Watchdog timer reset
2 = Associated
3 = Disassociated
4 = Synchronization Lost
5 = Coordinator realignment
6 = Coordinator started
LSB
(Beacon-enabled only)
Frame Data
API Identifier
cmdID
Identifier-specific Data
Status (Byte 5)
cmdData
API-specific Structure
Checksum
Frame Data
(Bytes 4- n)
1 Byte
Chapter 3 ‐ RF Module Configuration
Identifier-specific Data
cmdData
(Byte n + 1)
Checksum
1 Byte
     55

Related parts for JF1R6-CR3-4I