EM260-RTY Ember, EM260-RTY Datasheet - Page 50

• Manufacturer Part Number: EM260-RTY
• Description: IC ZIGBEE SYSTEM-ON-CHIP 40-QFN
• Manufacturer: Ember

Specifications of EM260-RTY

• Frequency: 2.4GHz
• Data Rate - Maximum: 250kbps
• Modulation Or Protocol: 802.15.4
• Applications: ZigBee™
• Power - Output: -32dBm ~ 3dBm
• Sensitivity: -97dBm
• Voltage - Supply: 2.1 V ~ 3.6 V
• Current - Receiving: 30mA
• Current - Transmitting: 34mA
• Data Interface: PCB, Surface Mount
• Antenna Connector: PCB, Surface Mount
• Operating Temperature: -40°C ~ 85°C
• Package / Case: 40-QFN
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Memory Size: -
• Other names: 636-1003

EM260
50
120-1003-000D
EmberStatus
EMBER_INVALID_SECURITY_LEVEL
EMBER_MOVE_FAILED
EMBER_ORPHAN_SCAN_FAILED
EMBER_NETWORK_BUSY
EMBER_NODEID_INVALID
EMBER_INVALID_ENDPOINT
EMBER_BINDING_HAS_CHANGED
EMBER_CHANNEL_NOT_CALIBRATED
EMBER_STACK_AND_HARDWARE_MISMATCH
EmberEventUnits
EMBER_EVENT_INACTIVE
EMBER_EVENT_MS_TIME
EMBER_EVENT_QS_TIME
EMBER_EVENT_MINUTE_TIME
0x95
0x96
0x97
0xA1
0xA2
0xA3
0xA4
0xA5
0xB0
0x00
0x01
0x02
0x03
The chosen security level (the value of EM-
BER_SECURITY_LEVEL) is not supported by the
stack.
After moving, a mobile node's attempt to re-
establish contact with the network failed.
In the tree stack, an attempt to rejoin the net-
work using an orphan scan failed. The stack will
still come up but tree routing will not be possible
because this node's parent is not responding.
A message cannot be sent because the network is
currently overloaded.
A Datagram was sent to a node and the EUI64
address in the datagram did not match the node's
EUI64 address. The NodeId was invalid.
The application tried to send a message using an
endpoint that it has not defined.
The application tried to use a binding that has
been remotely modified and the change has not
yet been reported to the application.
The application tried to use a radio channel that
has not been calibrated.
A critical and fatal error indicating that the
version of the stack trying to run does not match
with the chip it is running on. The software (stack)
on the chip must be replaced with software that is
compatible with the chip.
The event is not scheduled to run.
The execution time is in approximate millisec-
onds.
The execution time is in 'binary' quarter seconds
(256 approximate milliseconds each).
The execution time is in 'binary' minutes (65536
approximate milliseconds each).