A VIS.T installation was connected on a local network through an Ethernet-to-RS485 interface converter. Direct Modbus TCP polling from Rapid SCADA did not produce coherent values, while the manufacturer-supplied OPC server successfully transferred device data. Use the checks below to determine whether a Rapid SCADA Modbus template is viable or whether the integration requires an OPC or custom-driver path.
Separate Confirmed Results from Open Questions
| Item | Evidence-based status | Engineering decision |
|---|---|---|
| Device configuration | The reported installation did not require reconfiguring the VIS.T device. | Concentrate initial work on the interface converter and Rapid SCADA request definition. |
| Current values | The protocol description reportedly uses standard Modbus commands except for archived data. | A Rapid SCADA Modbus template may be suitable after validating addressing and value encoding. |
| Archived values | Archives cannot be read through ordinary templates according to the available evidence. | Plan for a dedicated driver when archived data is required. |
| Direct Modbus TCP | Testing produced Rapid SCADA values that differed from known device values despite trying multiple combinations. | Do not commission the template until one register has been proven against a known device reading. |
| OPC path | The manufacturer-supplied OPC server transferred data successfully in the reported installation. | Use OPC as the verified fallback while direct Modbus remains unresolved. |
Validate One Modbus Value Before Building the Template
The unresolved variables are the register base, numeric width, and byte order. The evidence identifies possible zero-based or one-based addressing, float or double values, and an unknown byte permutation. It also notes that the template can express addresses in decimal or hexadecimal form; select the form used by the device documentation without changing the underlying register location.
- Disable every request except one current-value request whose live value is independently known.
- Enter the documented address in decimal or hexadecimal as required by the documentation.
- Test whether the documented address must be interpreted with a zero-based or one-based register origin.
- Decode the response using the documented floating-point width; determine whether the variable is float or double rather than assuming either format.
- Test byte or word permutation only after the address and width are established.
- Compare the decoded result with the known device value. Add further registers only after this comparison passes.
A plausible number is not sufficient verification. Record the request, raw response, selected address origin, data width, and permutation so the result can be reproduced before expanding the template.
Choose Between Modbus, OPC, and a Dedicated Driver
Use a Modbus template for current data only after the single-value test succeeds. If current values remain inconsistent, capture the converter settings and raw request-response exchange before concluding that the device itself is at fault; the evidence does not establish whether the Ethernet-to-RS485 unit performs transparent transport or protocol conversion.
Use the manufacturer-supplied OPC DA 3.0 server when reliable live data is more important than completing the direct Modbus path. The reported server ran on Windows 10 and had a last update in 2023, while manufacturer support was reported as unavailable since 2016. Treat remote OPC access from a separate virtual machine as an unverified architecture until network connectivity, permissions, client compatibility, reconnect behavior, and data quality are tested.
Verify the Planned Device Count Under Load
The project target is 100 to 200 VIS.T devices at one location, but the evidence provides no proven capacity, polling interval, timeout, or recovery limit. Stress-test the chosen OPC or Modbus path at the intended device count and request set. Verify update latency, stale-data indication, communication recovery, resource usage, and agreement between SCADA values and known device readings before deployment.
FAQ
Why does VIS.T Modbus data differ from the device display?
Check the register origin, float-versus-double width, and byte or word permutation. Isolate one known current value and prove its raw response and decoded result before polling additional registers.
Can Rapid SCADA read VIS.T archive data with a Modbus template?
Not according to the available evidence. Standard template polling may cover current values, but archived data requires a dedicated driver.
Can the VIS.T OPC DA 3.0 server handle 100 to 200 devices?
The reported OPC path transferred data, but capacity for 100 to 200 devices was still awaiting stress testing. Validate latency, stale data, recovery, resource usage, and value accuracy at the full planned load.