Rapid SCADA: Configuring SILINES Relay Read and Control

Integrate the SILINES Ethernet relay with Rapid SCADA as two separate paths: use SNMP to acquire relay states and use the device HTTP GET/POST API to issue control commands. The available evidence confirms that SNMP control is not supported; UDP exists but is unnecessary when HTTP control is practical.

Separate monitoring from control

Do not design an SNMP write path for this device. The device manufacturer confirmed that SNMP currently exposes relay states for reading only.

Configure SNMP state acquisition

1. Create a communication line in Rapid SCADA Communicator.
2. Select the DrvSNMP driver.
3. Configure the device credentials. The supplied configuration uses login admin and password admin; verify these against the actual device configuration before commissioning.
4. Add the required OIDs with matching data types. The reported system-object OID is .1.3.6.1.2.1.1.2.0 with type OID, while .1.3.6.1.2.1.1.3.0 is configured as Int64.
5. Add relay-state points from .1.3.6.1.4.1.61858.3.1.1.0 through .1.3.6.1.4.1.61858.3.1.8.0. The captured response reports these as integers.

The captured SNMP response returned relay values of 1 for channels 1 and 2 and 0 for channels 3 through 8. Treat these as observed values, not a guaranteed mapping of numeric values to energized or de-energized states; confirm that mapping by operating each relay and observing its OID.

Implement HTTP relay control

Send commands through the relay's HTTP GET/POST API. One proposed Rapid SCADA implementation is a custom HTML user page whose links contain the required API command. A proxy script was also proposed, but the evidence does not define its deployment, security model, or request format.

If relay commands must originate from Rapid SCADA formulas rather than an operator page, the evidence does not establish a completed mechanism. An HTTP notification driver was mentioned only as a test driver. Before implementation, determine whether the formula environment can invoke that driver or another HTTP-capable component, then map the formula result to the exact device API request defined by the device documentation.

Commission and verify the integration

1. Read all eight relay OIDs and record their initial integer values.
2. Operate one relay through the embedded web interface or HTTP API.
3. Poll the corresponding SNMP OID again and confirm that only the intended point changes.
4. Repeat for every relay to validate the channel-to-OID mapping.
5. Issue a command through the chosen Rapid SCADA HTTP path, then confirm execution independently through both the SNMP state and the physical relay output.

A successful SNMP poll proves monitoring only. Accept the control integration only when an HTTP command changes the intended physical output and the subsequent SNMP read reflects the resulting state.

FAQ