EM260-RTY Ember, EM260-RTY Datasheet - Page 48

• 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
48
120-1003-000D
EmberStatus
EMBER_ERR_TOKEN_EXISTS
EMBER_ERR_TOKEN_INVALID_SIZE
EMBER_ERR_TOKEN_READ_ONLY
EMBER_ERR_BOOTLOADER_TRAP_TABLE_BAD
EMBER_ERR_BOOTLOADER_TRAP_UNKNOWN
EMBER_ERR_BOOTLOADER_NO_IMAGE
EMBER_TOO_MANY_CONNECTIONS
EMBER_CONNECTION_OPEN
EMBER_CONNECTION_FAILED
EMBER_CONNECTION_CLOSED
EMBER_CONNECTION_CLOSING
EMBER_DELIVERY_FAILED
EMBER_BINDING_INDEX_OUT_OF_RANGE
EMBER_INVALID_BINDING_TERMINAL
EMBER_INVALID_BINDING_INDEX
EMBER_TERMINAL_HAS_MULTIPLE_BINDINGS
EMBER_INVALID_CALL
EMBER_COST_NOT_KNOWN
EMBER_MAX_MESSAGE_LIMIT_REACHED
0x4C
0x4D
0x4E
0x58
0x59
0x5A
0x60
0x61
0x63
0x64
0x65
0x66
0x69
0x6B
0x6C
0x6F
0x70
0x71
0x72
Could not create new flash token because it
already exists.
An incorrect size was specified when retrieving
token data.
Couldn't write token because it is marked read-
only.
The bootloader received an invalid message
(failed attempt to go into bootloader).
Bootloader received an invalid message (failed
attempt to go into bootloader).
The bootloader cannot complete the bootload
operation because either an image was not found
or the image exceeded memory bounds.
The EMBER_TRANSPORT_CONNECTION_COUNT
limit has been reached.
A connection has either been opened or is already
open.
A connection experienced a catastrophic error.
The connection is now closed and messages may
have been lost.
The transport layer successfully closed a connec-
tion.
The transport layer is in process of closing a
connection (waiting for a response from the
remote device).
The transport layer attempted to send or deliver a
message, but it failed.
This binding index is out of range of the current
binding table.
Could not set or find a binding index given the
specified terminal.
An invalid binding table index was given to a
function.
Multiple binding table entries were found for the
specified terminal.
The API call is not allowed given the current state
of the stack (for example, opening a connection
from a sleepy node.).
The link cost to a node is not known.
The maximum number of in-flight messages (i.e.
EMBER_TRANSPORT_PACKET_COUNT) has been
reached.