One Mitsubishi R Series PLC communicates with four GOT2000 operator terminals, but only the first terminal updates normally; the other three communicate while updating in a visibly intermittent manner. Because the evidence does not identify the network type or current connection definitions, diagnose the shared PLC-side configuration before treating the symptom as an HMI performance fault.
Observed Behavior and Configuration Gaps
| Item | Evidence | Engineering implication |
|---|---|---|
| Controller | One Mitsubishi R Series PLC | All four terminals share one controller. |
| Operator terminals | Four GOT2000 terminals | The application uses a 1:N PLC-to-HMI arrangement. |
| Performance | The first GOT updates normally; the other three stutter. | Communication exists, but successful data exchange alone does not confirm that every terminal has a complete connection definition. |
| Unknowns | Network type and communication settings were not supplied. | Do not assume Ethernet or select an Ethernet-specific correction until the actual interface is confirmed. |
Check the PLC External Device Configuration
If the four GOT terminals use Ethernet, open the PLC project and inspect Module Parameter > External Device Configuration. Confirm that the configuration contains a separate GOT communication entry for each of the four terminals. The evidence specifically identifies adding all four GOT connections in this configuration as the corrective action to evaluate.
If the connection is not Ethernet, this menu path is not established as the applicable fix. Record the actual interface and existing PLC and GOT communication settings before changing the project.
Configuration Procedure
- Confirm whether the GOT-to-PLC connection uses Ethernet. Also compare the communication configuration of the normally updating GOT with each stuttering GOT.
- If Ethernet is confirmed, open Module Parameter > External Device Configuration in the PLC project and verify that four distinct GOT communication entries exist.
- Add or correct missing GOT entries, apply the project through the normal engineering workflow, and then retest all four terminals.
Verify the Result
Exercise screens that read live PLC data and observe all four terminals during simultaneous operation. The correction is verified only when the second, third, and fourth GOT terminals update continuously like the first while communication remains established.
If stuttering remains after all four Ethernet entries are confirmed, preserve the test result and collect the network type, PLC module configuration, GOT communication settings, and connection definitions. The available evidence does not support assigning a firmware, bandwidth, scan-time, or hardware cause without those details.
FAQ
Why do three GOT2000 terminals lag while the first one works?
The confirmed symptom shows that communication exists, but the supplied configuration is unknown. If Ethernet is used, first verify that the PLC External Device Configuration contains a communication entry for every GOT.
Where do I configure four GOT2000 connections in an R Series PLC project?
For the Ethernet case described in the evidence, inspect Module Parameter > External Device Configuration and configure four GOT communication entries.
How do I verify the GOT2000 1:N communication fix?
Operate all four terminals simultaneously and monitor live PLC data screens. Confirm that the three previously stuttering terminals now update as continuously as the first.