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 Timestamps
- 7.2 Status
- 7.3 Serial Interface
- 7.3.1 Serial Handshake Protocol
- 7.3.2 Mote Command Data Types
- 7.3.3 Mote Commands
- 7.3.3.1 Command 0x80 Serial Payload Sent to Mote Serial
- 7.3.3.2 Command 0x81 Unacknowledged Serial Payload Received from Mote Serial
- 7.3.3.3 Command 0x82 Acknowledged Serial Payload Received from Mote Serial
- 7.3.3.4 Command 0x84 Time/State Packet
- 7.3.3.5 Commands 0x87 and 0x88 Set Parameter Request/Response
- 7.3.3.6 Commands 0x89 and 0x8A Get Parameter Request/Response
- 7.3.3.7 Command 0x8C Mote Information
- 7.3.3.8 Command 0x8D Reset Mote
- 7.3.4 Mote Get/Set Command Parameters
- 7.3.5 HDLC Packet Processing Examples
- 8.0 Packaging Description
- 9.0 Regulatory and Standards Compliance
- 10.0 Ordering Information
Interfaces
M2135-1/M2030-1 MOTE DATASHEET DUST NETWORKS™ 13
CONFIDENTIAL
7.3.1.3.4 Timing Values
7.3.2 Mote Command Data Types
Table 15 defines the command data types used in the commands.
7.3.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 microcontroller and the mote are encapsulated in the HDLC format
(RFC
1662) and have the following 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.
The frame checksum (FCS) is calculated based on the 16-bit FCS computation method (FCS-16, RFC 1662). The mote checks
the FCS and drops packets that have FCS errors. There is no mechanism for the mote to tell the microcontroller 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.3.5 provides an example of HDLC packet construction and
HDLC packet decoding.
Table 14 Timing Values
Variable Meaning Min Max Unit
interbyte_delay The time between consecutive data bytes cannot exceed this
time.
0 7 ms
interpacket_delay The sender of an HDLC packet must wait at least this amount
of time before sending another packet.
N/A 20 ms
ack_delay The max time delay between the MT_RTS and the receivers
acknowledge,
SP_CTS.
0 500 ms
time_ack_timeout The mote responds to all TIME pin activation requests within
this time.
N/A 100 ms
diag_ack_timeout The mote responds to all requests within this time. N/A 125 ms
min_strobe_length The length of the strobe signal. 500 ns
boot_delay The time between mote power up and serial interface
availability.
250 ms
Table 15 Command Data Types
Data Type Description
ULong Unsigned long: 4 bytes
UShort Unsigned short: 2 bytes
UChar Unsigned character: 1 byte character
Command
(Byte 1) (Bytes 2—n)
Command Type Message Content
Start Delimiter
(Byte 0)
Data Frame
(Bytes 1—n)
Frame Checksum
(Bytes n + 1, n + 2)
End Delimiter
(Byte n + 3)
0x7E HDLC Packet payload FCS-16 (2 Bytes) 0x7E
PRELMINARY