For a small Rapid SCADA installation, select the architecture by separating monitoring from autonomous control. Directly connected I/O can remove an unnecessary PLC from a read-only system, while a PLC remains appropriate when control must continue after the SCADA computer fails.
Separate Data Acquisition from Autonomous Control
If the system only collects measurements and displays them in Rapid SCADA, connect compatible analog or discrete I/O modules directly to the SCADA host. The evidence identifies ICP DAS M-7017 modules communicating through Modbus as one field-proven implementation, but it provides no channel count, electrical range, or wiring specification; verify those details against the selected module documentation.
If the project is progressing toward unattended machine control, treat that function separately. A direct-I/O architecture makes the computer part of the control dependency. Use a PLC where loss of the computer must not stop required local logic, subject to a project-specific failure and consequence assessment.
Select the Architecture by Failure Consequence
| Engineering condition | Supported architecture | Required check |
|---|---|---|
| Read measurements and display them in SCADA | Direct analog or discrete I/O connection | Confirm that Rapid SCADA can communicate with the module through an existing driver or a developed driver. |
| Instrument uses a supported Modbus interface | Direct Modbus polling | Verify the device register map and establish successful reads before removing an existing PLC. |
| Computer failure has no serious operational consequence | PLC may be unnecessary | Document what data and functions are lost when the computer is unavailable. |
| Control must continue without the computer | PLC-based local control | Prove that the required logic operates independently of Rapid SCADA. |
| Instrument uses a proprietary protocol | Driver or programmable gateway function required | Confirm that the selected platform can implement the protocol; do not assume every controller supports suitable text-based programming. |
Implement and Verify Direct Acquisition
- Inventory each signal and classify it as a direct I/O point, a Modbus value, or a value carried by a proprietary protocol.
- Confirm whether Rapid SCADA already has the required communication path. If it does not, define and test a driver before committing to a PLC-free design.
- Connect one representative device or I/O module and verify stable polling, correct value decoding, and recovery after a deliberate communication interruption.
- Test the effect of stopping or disconnecting the SCADA computer. Retain direct acquisition only when the observed loss of function is acceptable.
- For autonomous control, move the required logic into a PLC and verify operation while Rapid SCADA is unavailable.
Diagnose Ethernet Faults Before Replacing the PLC
The evidence contains conflicting site reports about OWEN Ethernet stability: one installation reported communication interruptions about ten times per week, including with a direct PC connection, while other installations reported no network faults. This supports a diagnostic path, not a product-wide conclusion. Check the network and controller condition before selecting a replacement.
Confirm the switch port configuration and test a 100 Mbps port when a 100 Mbps controller interface is connected to a gigabit-capable port. If faults also occur through a serial connection, inspect the controller and installation rather than attributing the problem solely to Ethernet. Record fault frequency before and after each change so the result distinguishes a network correction from an intermittent device fault.
FAQ
Do I need a PLC just to read values into Rapid SCADA?
No, provided Rapid SCADA can poll the instrument or I/O module directly and computer failure has no serious consequence. Direct Modbus polling or a suitable driver can remove the PLC from a read-only data path.
Can Rapid SCADA communicate directly with an ICP DAS M-7017?
The evidence identifies an M-7017 installation connected directly through Modbus. Verify the selected module's register map, electrical specifications, and Rapid SCADA communication configuration before deployment.
How should I troubleshoot repeated PLC Ethernet disconnects?
Check the network configuration, test a 100 Mbps switch port for a 100 Mbps controller interface, and compare the result with a direct connection. If serial communication also fails, investigate controller condition and installation faults instead of treating Ethernet as the confirmed root cause.
