AeroComm Corporation AC4490 Benutzerhandbuch
9
T H E O R Y O F O P E R A T I O N
www.aerocomm.com
specifying various vital parameters used to control radio settings and packet routing on a packet-by-packet basis.
The API features can be used in any combination that suits the OEM’s specific needs.
The API features can be used in any combination that suits the OEM’s specific needs.
R e c e i v e A P I P a c k e t
Implemented in v6.3 of the firmware and later. Receive API Packet can be enabled to determine the sender of a
message. This causes the radio to append a header to the received packet detailing the length of the data packet and
the sender’s MAC address. The Receive API Packet will follow the following format.
message. This causes the radio to append a header to the received packet detailing the length of the data packet and
the sender’s MAC address. The Receive API Packet will follow the following format.
A P I T r a n s m i t P a c k e t
Implemented in v6.7 of the firmware and later. API Transmit Packet is a powerful command that allows the OEM Host
to send data to a single or multiple (broadcast) transceivers on a packet-by-packet basis. This can be useful for many
applications; including polling and/or mesh networks. Refer to the API Appendix for further details.
API Transmit Packet is enabled when bit-1 of the Enhanced API Control byte is enabled. The OEM Host should use
the following format to transmit a packet over the RF.
to send data to a single or multiple (broadcast) transceivers on a packet-by-packet basis. This can be useful for many
applications; including polling and/or mesh networks. Refer to the API Appendix for further details.
API Transmit Packet is enabled when bit-1 of the Enhanced API Control byte is enabled. The OEM Host should use
the following format to transmit a packet over the RF.
1
If the OEM Host does not encode the header correctly, the transceiver will send the entire string (up
to 80 bytes) and will look for the header in the next data.
to 80 bytes) and will look for the header in the next data.
2
Although the 7 bytes of overhead are not sent over the RF, they are kept in the buffer until the packet
is sent. Keep this in mind so as not to overrun the 256-byte buffer.
is sent. Keep this in mind so as not to overrun the 256-byte buffer.
3
Setting the MAC to 0xFF 0xFF 0xFF will broadcast the packet to all available transceivers.
A P I S e n d D a t a C o m p l e t e
Implemented in v6.7 of the firmware and later. 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 OEM
Host). If an acknowledgement is not received, the packet will be retransmitted until one is received or all retries have
been used.
API Send Data Complete is enabled when bit-2 of the Enhanced API Control byte is enabled. The transceiver sends
the OEM Host the following data upon receiving an RF acknowledge or exhausting all attempts.
indicator. When a radio sends an addressed packet, it will look for a received acknowledgement (transparent to OEM
Host). If an acknowledgement is not received, the packet will be retransmitted until one is received or all retries have
been used.
API Send Data Complete is enabled when bit-2 of the Enhanced API Control byte is enabled. The transceiver sends
the OEM Host the following data upon receiving an RF acknowledge or exhausting all attempts.
1
RSSI* is how strong the local transceiver heard the remote transceiver.
2
Successful RF Acknowledge updates the Success/Failure bit.
3
A success will always be displayed when sending broadcast packets after all broadcast attempts
have been exhausted.
have been exhausted.
A P I R e c e i v e P a c k e t
Implemented in v6.7 of the firmware and later. 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
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
0x83
Payload
Data
Length
Sender’s
MAC
Payload Data
0x81
Payload Data
Length
(0x01 - 0x80)
Aerocomm
Use
Transmit
Retries/Broadcast
Attempts
Destination
MAC (2,1,0)
Payload
Data
0x82
Aerocomm
Use
RSSI*
0x00: Failure
0x01: Success