Laird Connectivity is now Ezurio/filters:background_color(white)/2024-12/RM024-P50-C-01_web.png)
/filters:background_color(white)/2019-06/ramp-ism-module_0.png)
/filters:background_color(white)/2024-12/CL4490-Image.png)
/filters:background_color(white)/2024-12/Embedded-Wireless-ConnexLink-CL4790-1000.png)
Answer
The API features in the RAMP radios allow for dynamically addressing packets (TX API), getting the sender's information when receiving a packet (RX API), and knowing when a packet was successfully transmitted (Send Data Complete). TX API and RX API both append a header to transmitted or received data while Send Data Complete is a separate message that gets sent to the transmitting radio's host when the packet that was transmitted is received successfully at the other end. The Laird Configuration and Test Utility Range Test does not account for these additional headers or packets when 'Create Data' is used in the 'Transmit Packet Selection' field. It will not append headers to the transmitted data so if TX API is enabled all packets for transmission will be tossed because of the lack of a header. It will not account for the additional header that is added to the received packet when RX API is enabled so all packets received will be received as "Data Error". It will not account for the extra packet sent to the transmitting radio's Host when Send Data Complete is enabled so anytime this message is sent it will be seen as a "Data Error". In order to work with the API features on the RAMP radios you should use the scripting feature to write an API script and load it in the 'Transmit Packet Selection' field as 'Load File'.
More information about scripting can be found in Appendix 1 of the Laird Configuration and Test Utility Software - RAMP Modules.pdf