Copyright © 2012 Open Geospatial Consortium.
29 Remove all power from instrument, wait 10 seconds, then reapply power. Verify that
instrument recognizes and processes non-PUCK native instrument commands.
f. Valid PUCK baudrates test
confrs232valid-baudrates-test Requirements addressed: reqrs232cmdspuckvb, reqrs232cmdspucksb,
reqrs232softbreak, reqcorecmdsnull-puck Issue PUCK soft break at common bauds to establish connection with instrument in
PUCK mode. For each common baud rate:
Issue “PUCKVB b\r”, where ‘b’ is the baud rate. If PUCK responds “YES”, note ‘b’ as a valid PUCK baud
For each valid PUCK baud as determined above: Issue “PUCKSB b\r” to set PUCK baud rate to ‘b’
Set host port’s baud to ‘b’, issue “PUCK\r” and verify “PUCKRDY” response IP PUCK Tests
This section describes compliance tests that are specific to IP PUCK implementations.
g. ZeroConf compliance test
confipzeroconf-test Requirements addressed: reqipaddress, reqipmulti-dns, reqipdiscovery,
reqippuck-port, reqiptcp For this test, run a ZeroConf browser e.g. Bonjour Browser on the instrument test
network. Power up instrument, then connect to IP network via Ethernet connection. Using
ZeroConf browser, verify that instrument PUCK service appears on network with service type _puck._tcp, with a link-local address, and that instrument has human-readable
name. Verify that PUCK commands are recognized on a TCP connection established on the
PUCK port specified by the DNS SRV request response.
h. Exclusive PUCK port access test
confippuck-port-test Requirements addressed: reqipexclusive-access
30
Copyright © 2012 Open Geospatial Consortium.
While one peer has a TCP connection to the PUCK port, run a second peer that attempts to connect; the second peer should receive TCPIP error 10061 connection refused.
i. PUCK port timeout test
confippuck-port-timeout-test Requirements addressed: reqipaccess-timeout, reqcorestartup
Power-cycle PUCK-enabled device, wait 4 seconds then attempt to establish connection to PUCK port, issue “PUCK\r”, verify “PUCKRDY” response; verify that connection
establishment and processing of commands on PUCK port is achieved within 5 seconds of device power-up. Do not issue further commands on PUCK port, and verify receipt of
“PUCKTMO” from port after 120 seconds followed by disconnection. Verify that peer can immediately reconnect to PUCK port.
j. Native instrument port test
confipnative-port-test Requirements addressed: reqipcmdspuckip
Peer connects to PUCK port, issues “PUCKIP\r” to retrieve “native instrument protocol port” number.; peer connects to the native port,; verify that native protocol is recognized
on that port.
