Editing SimTX API v24/Limits and errors (section)

== Diagnosing a silent close ==
When a connection closes with no explanation, check in this order:
# '''Is the decoder aligned?''' A packet read with one byte too many or too few makes every later packet look like garbage, and the client will report nonsense IDs before the server ever closes anything.
# '''Strings.''' <code>UTF</code> fields have a <code>u16</code> length; TLV and NEC strings have an <code>i32</code> length supplied by their container. See [[SimTX API v24/Data types#Strings|Strings]].
# '''Values.''' Latitude in −90 to 90, longitude in −180 to 180, finite floats, non-negative noise figure and frequency, positive bandwidth and sample rate, callsign of 1 to 64 printable characters.
# '''Packet order.''' A receiver may send only ReceiverRetune after its request. A control session accepts only control requests.
# '''Limits.''' Too many receivers from one address, a wideband request over budget, or control requests too fast.