Configuration Parameters#
Several parameters stored as manufacturing tokens control the operation of the ASH protocol. The values are optimized for operation at 115,200 bps using RTS/CTS flow control, or 57,600 bps when using XON/XOFF software flow control.
Silicon Labs has tuned the ASH protocol to operate best with the configurations listed in the following two tables. While you can change these configurations through manufacturing tokens, doing so may degrade performance. To learn how to change the configurations, contact customer support at https://www.silabs.com/community.
| Parameter | Value | Units | Description |
|---|---|---|---|
| T_RX_ACK_INIT | 1.6 | sec | Initial value of t_rx_ack, the maximum time the NCP waits to receive acknowledgement of a DATA frame |
| T_RX_ACK_MIN | 0.4 | sec | Minimum value of t_rx_ack |
| T_RX_ACK_MAX | 3.2 | sec | Maximum value of t_rx_ack |
| T_TX_ACK_DELAY | 20 | msec | Delay before sending a non-piggybacked acknowledgement |
| T_REMOTE_NOTRDY | 1.0 | sec | Time from receiving an ACK or NAK with the nRdy flag set after which the NCP resumes sending callback frames to the host without requiring an ACK or NAK with the nRdy flag clear |
| Parameter | Value | Description |
|---|---|---|
| BAUD_RATE | 115200 (RST/CTS) / 57600 (XON/XOFF) | Transmit and receive baud rate |
| TX_K | 5 | Maximum number of DATA frames the NCP can transmit without having received acknowledgements |
| ACK_TIMEOUTS | 4 | Maximum number of consecutive timeouts allowed while waiting to receive an ACK before going to the FAILED state. The value 0 prevents the NCP from entering the error state due to timeouts. |
| RANDOMIZE | enabled | Enables randomization of received and transmitted DATA frame Data Fields; can be disabled for debugging |