Turn on No Reply Events for remotes — stop responding

To turn on No Reply event for a remote — stop responding

• To set Individual remotes to stop responding, issue a PUT using the following URL format:

  http://localhost:<portnumber>/Remote/<remotename>/StopResponding

  Where:

  • portnumber is the port specified in the RTU (Remote Terminal Unit) Player configuration file.

  • remotename is the name of the remote to set in a No Reply state.

  Note: The command is idempotent and will always return an OK status if received by the web Application Program Interface (API), even if the remote does not exist or is already in a No Reply state.

The following example details an issued No Reply for Remote1 with the RTU Player configured to listen on port 63280 using a curl command line utility:

curl -X PUT -I -H "Content-Length: 0" -H "X-HMISCADA: RTUPlayer" http://localhost:63280/Remote/Remote1/StopResponding

Note: The custom header value of "X-HMISCADA: RTUPlayer" is case-sensitive and must be supplied in order to receive an OK status response.

The response should return as follows:

HTTP/1.1 200 OK

Content-Length: 0

Server: Microsoft-HTTPAPI/2.0

Content-Security-Policy: default-src 'none'

Date: Mon, 29 Jan 2024 15:14:34 GMT

Note: The specific values will be different based on the operating environment.