The C-more simulator does not communicate with PLC tags, so pairing it with the Do-more simulator will not reproduce a live PLC-to-HMI connection. The workable test path described for this setup is to connect the Do-more simulator to an actual C-more EA9 HMI.
Stop trying to connect the two simulators directly
Restarting either simulator or repeatedly changing connection settings will not add a communications capability that the C-more simulator lacks. The reported limitation is specific: C-more simulation does not read PLC tags and has no built-in communications.
- Do not treat a blank or stale simulated tag as proof of a Do-more logic fault. The C-more simulator is not reading the simulated controller.
- Do not assume two running simulators behave like a PLC and HMI. The Do-more simulator can communicate with an actual C-more HMI, but that does not establish simulator-to-simulator support.
For an HMI tag test, switch to an actual C-more EA9 panel. If hardware is unavailable, use the simulators separately for the functions they support rather than troubleshooting a nonexistent combined link.
Separate HMI simulation from controller simulation
The key distinction is the communications endpoint. In the described arrangement, the simulated Do-more controller uses the PC's IP address and can operate toward an actual C-more HMI like a Do-more CPU. The C-more simulator, by contrast, does not provide the communications path needed to read PLC tags.
This is an asymmetric test arrangement: a simulated controller may serve an actual HMI, while the simulated HMI cannot serve as the client for simulated PLC tags. Do not infer a protocol, port, or driver from the fact that the simulator uses the PC's IP address; select the PLC communication settings supported by the specific HMI and controller configuration.
Connect the Do-more simulator to an actual EA9 panel
- Identify the PC running the Do-more simulator and read its active IP address. The simulator uses the PC's address as its network endpoint.
- Connect the EA9 HMI and the PC to a reachable network. Confirm they can address one another; check subnet settings, routing, and any network filtering if communication fails.
- In the C-more project, configure the PLC device communication settings for the Do-more controller, using the PC IP address as the target. Use the applicable driver and settings from the installed C-more and Do-more software documentation; do not guess protocol or port values.
- Download or run the project on the actual EA9 panel, then start the Do-more simulator. Monitor a known PLC tag from the HMI.
Keep addresses distinct where the network configuration requires unique host addresses. If the simulator and HMI are on different subnets, verify that routing permits traffic between them rather than changing random project settings.
Verify the communication path before changing logic
Test one simple, known tag first. Confirm that its controller value changes in the Do-more simulator and that the EA9 display reflects the same value. Then test a write from the HMI only if the tag and project are configured for writing.
| Observation | Check next |
|---|---|
| HMI shows no value with the C-more simulator | Use an actual EA9; the simulator does not read PLC tags. |
| Actual EA9 cannot reach the simulated controller | Confirm the PC's active IP address, HMI target address, network reachability, and selected device settings. |
| Communication works but a tag is wrong or unchanged | Confirm the tag reference, data type, direction, and that the simulator logic changes that tag. |
Change one variable at a time and retest. A successful network path does not prove that the HMI tag mapping is correct, and a correct mapping does not prove the panel can reach the PC.
Keep the temporary test separate from production repair
Using the Do-more simulator with a real EA9 is a bench-test arrangement, not a way to make the C-more simulator read PLC tags. Record the simulator PC address and the HMI project settings used for the test so they can be removed or replaced with production controller settings later.
Do not carry the simulator PC address into a production project unless that PC is intentionally the required controller endpoint. Before returning equipment to service, restore the intended PLC target and verify the HMI against the actual controller.
FAQ
Why does the C-more simulator not show Do-more simulator tags?
The C-more simulator does not read PLC tags or provide built-in communications. Use an actual C-more EA9 HMI to test tags from the Do-more simulator.
Can the Do-more simulator connect to a C-more EA9?
Yes, the described setup uses the PC's IP address for the simulated Do-more controller and an actual EA9 HMI. Configure the HMI target and verify the network path.
Why does the EA9 still fail to communicate with the simulator?
Check the active IP address on the simulator PC, the HMI's target address, network reachability, and the selected PLC communication settings. Then verify that the test tag exists and changes in the simulator.
When should I stop troubleshooting and escalate?
Stop if the EA9 cannot communicate after you verify its project settings, the PC address, and network reachability, or if the required driver and settings are unclear. Contact official AutomationDirect support with the EA9 project, Do-more configuration, software versions, and observed communication diagnostics.