How-to
Where to save C-more panel IP settings in the project
Short answer
The C-more project does store the panel's IP address and subnet mask: enter them under Setup > Touch Panel Network > Ethernet Port and save the project. That entry is a record, not a lock — the panel's System menu can still change the live values — and it is separate from the PLC destinations, so a controller address change still means editing each affected project and re-transferring it to every panel.
On this page
The place you are looking for exists. In a C-more EA9 project, the panel's own IP address and subnet mask are saved under Setup > Touch Panel Network > Ethernet Port: enter them there once and they travel with the project file instead of living only in the panel's System menu. Two boundaries come with that entry. It is a record, not a lock — the System menu on the panel can still change the live values. And it has nothing to do with the PLC destination addresses the project uses to reach controllers, so a controller address change is always a project edit plus a re-transfer to every affected panel.
Save the panel's network values in the project #
- Open the machine's project in the C-more editing software.
- Go to Setup > Touch Panel Network > Ethernet Port.
- Enter the panel's IP address and subnet mask exactly as they should exist on the network.
- Save the project.
- Archive the saved file with the machine documentation, labeled with the panel it belongs to and the controller it serves.
The archived project is now the as-programmed reference. The next technician opens one file and reads the panel identity, instead of trusting a note taped inside the cabinet door.
What the project entry does not do #
It does not lock the panel. The System menu on the panel remains the live configuration, and whoever stands at the machine can change the address there regardless of what the project says. Treat the Ethernet Port entry as documentation and build the discipline around comparison: after commissioning, after maintenance, and after any network change, read the panel's live values and make the two sides agree. When they disagree, decide which address is correct for the network as built, then correct the other side — never overwrite the panel just because the project file is handy.
The panel's address and the PLC destination are different settings #
The panel's IP address and subnet mask identify the HMI itself on the network. A PLC destination address identifies the controller the project communicates with, and it lives in the project's controller communication configuration, where each PLC configured in the project is selectable for the Ethernet connection. Changing one never changes the other.
| Setting | What it identifies | Where it is set |
|---|---|---|
| Panel IP address and subnet mask | The HMI's own identity on the network | Setup > Touch Panel Network > Ethernet Port |
| PLC destination address | The controller the project polls | The project's controller communication configuration |
This separation is where most of the wasted time lives. Re-typing the panel's own IP does nothing to a stale PLC destination, and editing a destination does not document the panel's address. Identify which side changed before you edit anything.
Check the subnet before you transfer anything #
Worked example — illustrative numbers, real arithmetic. Suppose the Ethernet Port tab carries a panel at 192.168.1.10 with subnet mask 255.255.255.0, and the controller sits at 192.168.1.50:
- 192.168.1.10 AND 255.255.255.0 → 192.168.1.0
- 192.168.1.50 AND 255.255.255.0 → 192.168.1.0
Same network, so the panel reaches the controller directly. Under a 255.255.255.0 mask the last octet offers 256 addresses, of which 2 are reserved (network .0 and broadcast .255), leaving 254 assignable: 192.168.1.1 through 192.168.1.254.
Now the controller is renumbered to 192.168.10.50, mask unchanged:
- 192.168.10.50 AND 255.255.255.0 → 192.168.10.0
- 192.168.10.0 ≠ 192.168.1.0
Different subnets. With no gateway between them, nothing typed into a PLC destination field closes that gap. The decision: give the panel an address on 192.168.10.0 — for example 192.168.10.10, one of its 254 usable addresses — in Setup > Touch Panel Network > Ethernet Port, or route between the two subnets. Routing is a network design change, not an HMI setting, so on a flat machine network the panel moves.
Handle a PLC address change across every panel #
When a controller's address changes, the work is bigger than one screen. A typical case: IT renumbers the controller, and two HMI projects each need an edit and a walk out to their panel over USB. Plan for that shape every time.
- Inventory every HMI project that references the affected controller — not just the panel nearest the cabinet.
- In each project, update the controller's destination address in the project's controller communication configuration.
- While each project is open, confirm the panel's own address still lands in the controller's subnet, as in the example above.
- Save each project and transfer it to its panel; USB is a sound choice for a walk-around of a few panels. An edited project reaches the hardware only through a fresh runtime download — read why an HMI edit needs a new runtime download if a panel keeps running the old behavior.
- Record the change: panel identity in the Ethernet Port entry, controller destination with the equipment it serves.
Do the transfer between production runs with the machine in a safe state, because a panel mid-transfer has no live control view.
If a panel still shows stale data after its transfer, work through HMI comms errors after a PLC IP address change before touching any more addresses.
Verify both sides before you call it done #
- Reopen each saved project and confirm the Ethernet Port entry holds the intended address and mask, and that the controller destination matches the renumbered PLC.
- Read each panel's live values in its System menu and compare against the project record.
- Test HMI-to-controller communication on every panel, not just the first one that came up.
- Glance at the hardware link: the RJ-45 port carries green and yellow LEDs, and the yellow LED indicates network speed — off means 10 Mbps.
- Archive the final projects with the panel and controller each file serves, keeping the panel address and the PLC destination as separate entries.
Close-out decision: if project and panel agree and every panel talks to its controller, you are done. If one panel disagrees, that panel is running an old project or an old address — fix that panel, not the network.
Questions asked
Does saving the IP address in the project stop changes from the panel's System menu?
No. Saving the values under Setup > Touch Panel Network > Ethernet Port stores them with the project file; it does not restrict the panel's System Setup screens, which stay live on the unit. The practical cost of that shows up during faults: a panel quietly re-addressed at the machine looks like a network failure, and you can lose the first hour chasing cabling before anyone compares the live address against the project record.
Our PLC's IP address changed. Do the panels' own IP addresses need to change too?
Only if the new address puts the controller in a different subnet than the panels. Compare the network portions: a panel at 192.168.1.10 and a controller at 192.168.1.50 under mask 255.255.255.0 both sit on 192.168.1.0, so no panel address changes. A controller moved to 192.168.10.50 under the same mask sits on 192.168.10.0, so each panel needs an address on that subnet — or a routing path — in addition to the destination edit inside every affected project.
How do I open the panel's setup screens to see the live IP address?
Press and hold the extreme upper-left corner of the display area for three seconds. That opens the main menu of the panel's System Setup screens, where the live network values are shown. Compare what you read there against the Ethernet Port entry in the saved project before changing anything, because the live values are the ones the network is using right now.
Can I put the PLC's IP address on a password-protected screen so the client can change it without a project transfer?
Not as a documented feature of the project software. The supported path to a new controller destination is a project edit followed by a transfer to each panel. If a client's IT department may renumber the controller, plan for it at design time: get the address range agreed in writing, keep a standing inventory of every HMI project that references the controller, and expect a USB walk-around to each panel when the change lands.
Do newer C-more CM5 panels use the same setting location?
The same concept carries over: the CM5 documentation shows a Panel Network section with an Ethernet Port setup page. The hardware differs — CM5 panels have different numbers of Ethernet ports depending on the model, and every model has at least one. When a model carries more than one port, confirm which physical jack your cable uses before you blame addressing for a dead link.