Table of Contents
Advertisement
LT2510
Wireless Module
SPECIFICATIONS
www.lairdtech.com
6
TABLE 5: TIMING SPECIFICATIONS
PARAMETER
SERVER/CLIENT
Power on to CTS Low
EEPROM Read
EEPROM Write
Power on to In Range
Client only,
server will go
in range in less
than 13ms
Hop Period In Range
Hop Period Out of Range
Client only
Reset Pulse
PWM Output Period
Restore Default EEPROM
Command
Non Specific AT Command
Write Flash
Read Flash
Decrypt Image
RF HOP FRAME
The LT2510 will hop every 13.19ms and can be configured for two different RF Data Rates to provide
options for range or throughput. During each hop, the LT2510 reserves a certain amount of time for
overhead, such as the synchronization beacon, internal messaging and user data transmission. The
diagrams below outline the various transmissions that occur during a hop. These transmissions are
transparent to the user sending data, but may be useful for applications that require critical timing.
User data is only transmitted during the data slots and after the Interface Timeout or RF Packet
Size criteria has been met. Data transmission will only begin at the beginning of a data slot. When
configured for Full Duplex, data slot 1 is reserved for the Server and data slot 2 is shared by all Clients
for transmissions.
RF Data Rate = 500kbps
RF Data Rate = 500kbps
RF Data Rate = 500kbps
RF Data Rate = 500kbps
RF Data Rate = 500kbps
RF Data Rate = 280kbps
RF Data Rate = 280kbps
RF Data Rate = 280kbps
RF Data Rate = 280kbps
RF Data Rate = 280kbps
MIN
TYP
5ms
10ms
800us
1ms
20ms
30ms
13ms
600ms
13.19ms
38.4ms
250ns
315.077uS
10ms
38ms
1ms
10ms
1.19ms
4.89ms
1.19ms
4.89ms
1.19ms
4.89ms
1.19ms
4.89ms
1.19ms
4.89ms
1.19ms
4.89ms
1.19ms
4.89ms
1.19ms
4.89ms
1.19ms
4.89ms
1.19ms
4.89ms
MAX
NOTES
N/A
The first boot after a FW upgrade will
require more than the typical amount
of time for CTS to toggle Low.
2ms
Measured from last byte of
command to first byte of response:
870us for 1 byte
1.1ms for 80bytes
1.4ms for 256bytes
40ms
Measured. EEPROM writes will
cause the radio to resyncrhonize
1700ms*
*Maximum time assuming all
beacons are heard, RF interference
could extend the maximum time
indefinitely
Restore command also initiates
a soft reset, so monitoring CTS is
the best indication of a completed
command
Some AT Commands could wait
indefinitely for a response
For FW Upgrade
4.89ms
4.89ms
4.89ms
4.89ms
4.89ms
4.89ms
4.89ms
4.89ms
4.89ms
4.89ms
13.19ms
13.19ms
13.19ms
13.19ms
2.22ms
2.22ms
2.22ms
2.22ms
2.22ms
2.22ms
2.22ms
2.22ms
2.22ms
2.22ms
Laird Technologies
Advertisement
Table of Contents
