User's Manual
Table Of Contents
- 1.0 Absolute Maximum Ratings
- 2.0 Normal Operating Conditions
- 3.0 Electrical Specifications
- 4.0 Radio
- 5.0 Pinout
- 6.0 Mote Boot Up
- 7.0 Interfaces
- 7.1 Status LED Signal
- 7.2 Discrete Input/Output (I/O)
- 7.3 Deep Sleep
- 7.4 Serial Interface
- 7.4.1 Serial Flow Control
- 7.4.2 Mote Command Data Types
- 7.4.3 Mote Commands
- 7.4.3.1 Command 0x80 Serial Payload Sent to Mote Serial
- 7.4.3.2 Command 0x81 Unacknowledged Serial Payload Received from Mote Serial
- 7.4.3.3 Command 0x82 Acknowledged Serial Payload Received from Mote Serial
- 7.4.3.4 Command 0x84 Time/State Packet
- 7.4.3.5 Commands 0x87 and 0x88 Set Parameter Request/Response
- 7.4.3.6 Commands 0x89 and 0x8A Get Parameter Request/Response
- 7.4.3.7 Command 0x8C Mote Information
- 7.4.3.8 Command 0x8D Reset Mote
- 7.4.4 Mote Get/Set Command Parameters
- 7.4.5 HDLC Packet Processing Examples
- 8.0 Packaging Description
- 9.0 Regulatory and Standards Compliance
- 10.0 Ordering Information
Interfaces
M1030-2 MOTE DATASHEET DUST NETWORKS™ 13
CONFIDENTIAL
7.4.2 Mote Command Data Types
Table 14 defines the command data types used in the commands.
7.4.3 Mote Commands
The mote command interface provides a way to send and receive network packets, access local configuration and diagnostics,
and receive time stamps. All packets between the microprocessor and the mote are encapsulated in the HDLC format
(RFC
1662) and have the following structure (see Figure 11).
Figure 11 HDLC Packet Structure
The command type indicates which API message is contained in the message content. The message content for each command
type is described within the following sections.
FCS is calculated based on 16-bit FCS computation method (RFC 1662). The mote checks the FCS and drops packets that
have FCS errors. There is no mechanism for the mote to tell the microprocessor that a packet has been discarded, so the
applications layer must implement reliable delivery, if desired. All numerical fields in a packet are in big endian order (MSB
first), unless otherwise noted. Section
7.4.5 provides an example of HDLC packet construction and HDLC packet decoding.
Table 15 provides a summary of mote commands, which are described in detail in the following sections. For error handling,
all other packet types should be ignored. The Destination column indicates whether the packet is sent (or received) through the
network or processed locally by the mote.
Table 14 Command Data Types
Data Type Description
unsigned long 4 bytes
unsigned short 2 bytes
unsigned char 1 byte
Table 15 Mote Command Summary
Command Type (HEX) Direction Destination Description
0x80 Microprocessor to mote Network Packet destined for the network
0x81 Mote to microprocessor Network Unacknowledged packet received from the
network and destined for microprocessor
0x82 Mote to microprocessor Network Acknowledged packet received from the
network and destined for microprocessor
0x83 -- – Reserved
0x84 Mote to microprocessor Local Time and mote state information
0x85 -- – Reserved
0x86 -- – Reserved
0x87 Microprocessor to mote Local Set Parameter request
0x88 Mote to microprocessor Local Set Parameter response
0x89 Microprocessor to mote Local Get Parameter request
0x8A Mote to microprocessor Local Get Parameter response
Command
(Byte 1) (Bytes 2—n)
Command Type Message Content
Start Delimiter
(Byte 0)
Data Frame
(Bytes 1—n)
Checksum
(Bytes n + 1, n + 2)
End Delimiter
(Byte n + 3)
0x7E HDLC Packet payload FCS (2 Bytes) 0x7E