3.1r1: 9.5.3, UDP Unsolicited, and 9.5.4, unsolicited with UDP and TCP

[jadamcrain]

The last part of 3.1r1's section 9, after #51 and #52: every 3.1r1 network test is now implemented.

Tests

• 9.5.3.1 and 9.5.3.2 (Unsolicited Null 20000 / Not 20000):
  • after a restart, the null unsolicited response must come over UDP to the port set up, and not again once confirmed;
  • these tests set only where the null goes, and route everything else as the device can (to port 20000, or to the port the null was confirmed from).
• 9.5.3.3 to 9.5.3.5 (Data Filled Messages to Port 20000 / to Originating Port / to a Fixed Port Other Than 20000):
  • every message after the null must come to the port the test expects: port 20000, the port the harness confirmed the null from, or a fixed port other than 20000 that the device also listens on;
  • that covers the master's initialization (clear IIN1.7, a poll of every input, then enable unsolicited) and an unsolicited response with events.
• 9.5.4 (Unsolicited with Both UDP and TCP):
  • the null must come over UDP until a TCP connection is made, and over TCP only after that;
  • the events must come over TCP only;
  • a read over UDP must still be answered over UDP while the TCP connection is open.

Harness

• A UDP socket stays bound through close(), so datagrams the device sends while it restarts still arrive.
• After the null following a restart is read, the harness also reads any retries already waiting and confirms the newest. A manual restart can leave several queued, and an old one mustn't look like a retry sent after the confirmation.
• connect can keep the current connection open, so the harness can use TCP and UDP at once and switch back to an earlier connection.
• drainDatagrams counts what has arrived at a UDP socket that isn't current. In 9.5.4, datagrams that arrive while the TCP connection is being made are logged but not counted against the device.
• The runner closes everything at the end with shutdown().
• Waits for unsolicited events include unsolicited.holdOffMs.

Options

• network.udp.unsolicited, which also needs supports.unsolicitedResponse;
• network.udp.unsolicitedTo20000 and network.udp.unsolicitedToOriginatingPort (the null tests need one or the other);
• network.udp.unsolicitedNullOtherPort, with network.udp.unsolicitedPort;
• network.udp.fixedOtherPort;
• network.udpAndTcp.

The configuration check requires the "other" ports to differ from 20000.

The 2.7 -describe output is unchanged.