AT86RF230-ZUR Atmel, AT86RF230-ZUR Datasheet - Page 89
![no-image](/images/manufacturer_photos/0/0/78/atmel_sml.jpg)
AT86RF230-ZUR
Manufacturer Part Number
AT86RF230-ZUR
Description
TXRX LOW POWER 2.4GHZ 32VQFN
Manufacturer
Atmel
Datasheet
1.AT86RF230-ZU.pdf
(98 pages)
Specifications of AT86RF230-ZUR
Frequency
2.4GHz
Modulation Or Protocol
802.15.4 Zigbee, 6LoWPAN, RF4CE, SP100, WirelessHART™, ISM
Applications
Industrial Monitoring and Control, Wireless Alarm and Security Systems
Power - Output
-17dBm ~ 3dBm
Sensitivity
-101dBm
Voltage - Supply
1.8 V ~ 3.6 V
Current - Receiving
15.5mA
Current - Transmitting
16.5mA
Data Interface
PCB, Surface Mount
Antenna Connector
PCB, Surface Mount
Operating Temperature
-40°C ~ 85°C
Package / Case
32-VQFN Exposed Pad, 32-HVQFN, 32-SQFN, 32-DHVQFN
Number Of Receivers
1
Number Of Transmitters
1
Wireless Frequency
2405 MHz to 2480 MHz
Interface Type
SPI
Noise Figure
6 dB
Output Power
20 dB
Operating Supply Voltage
1.8 V to 3.6 V
Maximum Operating Temperature
+ 85 C
Mounting Style
SMD/SMT
Maximum Supply Current
16.5 mA
Minimum Operating Temperature
- 40 C
Modulation
OQPSK
Protocol Supported
802.15.4
Operating Temperature (min)
-40C
Operating Temperature (max)
85C
Operating Temperature Classification
Industrial
Operating Supply Voltage (min)
1.8V
Operating Supply Voltage (typ)
3V
Operating Supply Voltage (max)
3.6V
Lead Free Status / RoHS Status
Lead free / RoHS Compliant
Memory Size
-
Data Rate - Maximum
-
Lead Free Status / Rohs Status
Lead free / RoHS Compliant
Available stocks
Company
Part Number
Manufacturer
Quantity
Price
Company:
Part Number:
AT86RF230-ZUR
Manufacturer:
ATMEL
Quantity:
1 000
Appendix B - Errata
AT86RF230 Rev. B
AT86RF230 Rev. A
5131E-MCU Wireless-02/09
No known errata.
1. Data frames with destination address=0xFFFF is acknowledged in RX_AACK
2. Frame upload in RX_AACK
3. TX_ARET returns TRAC_STATUS=SUCCESS even though transaction failed
1.
2.
According to IEEE 802.15.4-2003 data frames with destination address=0xFFFF
(broadcast) should not have the acknowledgment request subfield set in the frame
control field. If such a non-standard compliant data frame arrives, a device in
RX_AACK state acknowledges that frame.
Fix/Workaround
Use only standard compliant frames, i.e. do not initiate frames with destination
address=0xFFFF (broadcast) and the acknowledgment request subfield set.
The following frames are not uploaded:
(1) Data frames and command frames with destination PAN ID=0xFFFF and
extended destination addressing mode
(2) Beacon frames, when the PAN ID of the receiving node is set to 0xFFFF.
Fix/Workaround
(1) Use Basic Operating Mode for orphan scanning
(2) Use Basic Operating Mode for network scanning
It might happen that under very special conditions (e.g. noisy network environment)
the status bit TRAC_STATUS (register 0x02) after transmission of a frame is
SUCCESS even though the transaction failed.
Example
A node transmits a frame with the acknowledgment request subfield set to logic high
and waits for an incoming ACK. If no frame is received at the end of the ACK wait
period (54 symbols), but a valid preamble is detected (e.g. jammer/interferer signal),
the TX_ARET procedure is finished immediately. A TRX_END interrupt is generated.
The TRAC_STATUS is not updated and thus shows the default value SUCCESS.
Fix/Workaround
The workaround comprises two changes:
Set
retransmissions in the TX_ARET procedure. The frame retransmission has to
be implemented in S/W. A retransmission does not require a frame download
again, only TX_START command is necessary.
Control of the TX_ARET procedure should follow these steps:
o
o
o
register
TRX_STATUS == TX_ARET_ON
set TRX_CMD = TX_START and download frame
poll for TRX_STATUS == BUSY_TX_ARET
bits
MAX_FRAME_RETRIES
to
0.
AT86RF230
This
prevents
any
89