AT86RF231 Atmel Corporation, AT86RF231 Datasheet - Page 59

• Manufacturer Part Number: AT86RF231
• Manufacturer: Atmel Corporation

Specifications of AT86RF231

• Max. Operating Frequency: 0 MHz
• Crypto Engine: AES
• Operating Voltage (vcc): 1.8 to 3.6
• Frequency Band: 2.4 GHz
• Max Data Rate (mb/s): 2
• Antenna Diversity: Yes
• External Pa Control: Yes
• Power Output (dbm): 3
• Receiver Sensitivity (dbm): -101
• Receive Current Consumption (ma): 13.2
• Transmit Current Consumption (ma): 14.4
• Link Budget (dbm): 104

8111C–MCU Wireless–09/09
Table 7-10.
There are two different options for handling reserved frame types.
Short Acknowledgment Frame (ACK) Start Timing
Register bit AACK_ACK_TIME (register 0x17, XAH_CTRL_1), see
defines the symbol time between frame reception and transmission of an acknowledgment
frame.
1.
2.
3.
0x2E
0x2E
0x2E
AACK_UPLD_RES_FT = 1, AACK_FLT_RES_FT = 0:
Any non-corrupted frame with a reserved frame type is indicated by an
IRQ_3 (TRX_END) interrupt. No further address filtering is applied on those frames. An
IRQ_5 (AMI) interrupt is never generated and the acknowledgment subfield is ignored.
AACK_UPLD_RES_FT = 1, AACK_FLT_RES_FT = 1:
If AACK_FLT_RES_FT = 1 any frame with a reserved frame type is filtered by the
address filter similar to a data frame as described in the standard. This implies the
generation of the IRQ_5 (AMI) interrupts upon address match. An IRQ_3 (TRX_END)
interrupt is only generated if the address matched and the frame was not corrupted. An
acknowledgment is only send, when the ACK request subfield was set in the received
frame and an IRQ_3 (TRX_END) interrupt occurred.
AACK_UPLD_RES_FT = 0:
Any received frame indicated as a reserved frame is discarded.
RX_AACK Configuration to Receive Reserved Frame Types (Continued)
7:6
3
4
AACK_I_AM_COORD
AACK_DIS_ACK
AACK_FVN_MODE
0: device is not PAN coordinator
1: device is PAN coordinator
0: Enable generation of acknowledgment
1: Disable generation of acknowledgment
Controls the ACK behavior, depending on FCF
frame version number
0x00: acknowledges only frames with version
number 0, i.e. according to IEEE 802.15.4-2003
frames
0x01: acknowledges only frames with version
number 0 or 1, i.e. frames according to
IEEE 802.15.4-2006
0x10: acknowledges only frames with version
number 0 or 1 or 2
0x11: acknowledges all frames, independent of
the FCF frame version number
Table 7-11 on page
AT86RF231
60,
59