Справочник Пользователя для AeroComm Corporation 2510100
LAIRD TECHNOLOGIES www.lairdtech.com
API O
PERATION
7
API Operation is a powerful alternative to the default Transparent operation of the LT2510 and provides dynamic packet
accounting abilities to the OEM Host without requiring extensive programming by the OEM Host. API operation utilizes specific
packet formats. The API features can be used in any combination that suits the OEM’s specific needs and can be different between
radios operating on the same network.
accounting abilities to the OEM Host without requiring extensive programming by the OEM Host. API operation utilizes specific
packet formats. The API features can be used in any combination that suits the OEM’s specific needs and can be different between
radios operating on the same network.
A P I S E N D D A T A C O M P L E T E
API Send Data complete can be used as a software acknowledgement indicator. When a radio sends an addressed packet, it will
look for a received acknowledgement (transparent to the OEM Host). If an acknowledgement is not received, the packet will be
retransmitted until one is received or all retries have been exhausted.
look for a received acknowledgement (transparent to the OEM Host). If an acknowledgement is not received, the packet will be
retransmitted until one is received or all retries have been exhausted.
For applications where data loss is not an option, the OEM Host may wish to monitor the acknowledgement process using the API
Send Data Complete. If an acknowledgement is not received (Failure), the OEM Host can send the packet to the transceiver once
again.
Send Data Complete. If an acknowledgement is not received (Failure), the OEM Host can send the packet to the transceiver once
again.
API Send Data Complete is enabled when bit-2 of the Control 2 (Address 0xC1) byte is enabled. The transceiver sends the OEM
Host the data shown in Figure 1 upon receiving an RF acknowledge or exhausting all attempts.
Host the data shown in Figure 1 upon receiving an RF acknowledge or exhausting all attempts.
F i g u r e 1 : S e n d D a t a C o m p l e t e p a c k e t f o r m a t
A P I R E C E I V E P A C K E T
By default, the source MAC is not included in the received data string sent to the OEM Host. For applications where multiple
radios are sending data, it may be necessary to determine the origin of a specific data packet. When API Receive Packet is enabled,
all packets received by the transceiver will include the MAC address of the source radio as well as an RSSI indicator which can be
used to determine the link quality between the two.
radios are sending data, it may be necessary to determine the origin of a specific data packet. When API Receive Packet is enabled,
all packets received by the transceiver will include the MAC address of the source radio as well as an RSSI indicator which can be
used to determine the link quality between the two.
API Receive Packet is enabled when bit-0 of the Control 2 (Address 0xC1) byte is enabled. Upon receiving a RF packet, the radio
sends its OEM Host the data as shown in Figure 2 below.
sends its OEM Host the data as shown in Figure 2 below.
Data
Request
0x82
Start Delimiter
Data
Byte 2: Transmit RSSI
Byte 3: Receive RSSI
Byte 4: Success
Byte 3: Receive RSSI
Byte 4: Success
0x00: Fail
0x01: Success
0x01: Success