Choose Ethernet or serial for a Kinco HMI from the PLC’s available service and the machine’s connection requirements. Ethernet, RS232, RS485 and RS422 identify interfaces, while the selected driver determines the supported protocol and addressing. Preserve the working route on an existing machine before proposing changes. Keep computer project transfer separate from the HMI-to-PLC link and verify the chosen route with a known value.
Record the PLC Service and Working Connection
Identify the complete PLC CPU code, firmware and communication module. Record which port the machine currently uses and what service is enabled there. An Ethernet socket might serve an engineering tool through one protocol while the HMI needs another. A serial connector might expose several electrical options or a dedicated programming function. The actual configuration determines the usable route.
For replacement work, retain the accepted HMI source, driver and channel assignment. Photograph cable ends and save the serial or network worksheet before removing the old panel. Ask whether the existing route must remain available during maintenance and whether another device shares it. These constraints can matter more than the apparent convenience of changing interfaces.
Electrical Interface Versus Driver Protocol
RS485 describes an electrical interface, not a guarantee of Modbus RTU. Ethernet identifies a network connection, not universal PLC compatibility. Confirm the device protocol, connection role and driver support in the software release used for the target. If that evidence is missing, selecting more panel interfaces does not resolve the application requirement.
The communication port and download guide helps inventory the physical functions. Use that inventory with the PLC manual and Kinco driver help, keeping each source tied to the actual CPU, module and panel code.
Compare Serial and Ethernet Installation Requirements
Choose the route by comparing the work needed to make it reliable and maintainable on the specific machine. An existing serial link can remain suitable when its driver, wiring and required data behavior are understood. Ethernet can be appropriate where the PLC exposes the required service and the site can maintain its addressing and permitted network path. Neither choice is automatically preferable for every installation.
| Decision item | Serial review | Ethernet review | Evidence to retain |
|---|---|---|---|
| PLC service | Supported serial mode and device role | Enabled service and transport | CPU or module instructions |
| Wiring | Electrical standard, pinout and bus | Cable, switch and approved route | Installed connection drawing |
| Maintenance | Channel, station and cable identification | Endpoint and network ownership | Accepted service worksheet |
| Change work | Existing channel and driver retained or revised | PLC configuration and project changes | Named actions and responsible owner |
| Verification | Known value through the intended channel | Known value through the intended service | Observed result and project copy |
Use the equipment documentation for cable arrangements, shielding, termination and applicable limits. A generic distance figure cannot establish suitability across different serial standards, data rates or cabinet environments. Likewise, adding a network switch does not resolve an unsupported PLC protocol or an unapproved plant route.
Serial Pinout and Communication Parameters
Before reusing a cable, compare both devices’ pin assignments and the exact channel involved. A connector fitting mechanically is insufficient. Record station, baud rate, parity, data bits, stop bits and protocol mode from the working configuration. Review termination and grounding against the actual bus and equipment instructions. Keep cable identity visible on the drawing so another technician can reproduce the arrangement.
Select Ethernet HMI Models by Full Code
GL070 and GL070E illustrate why the full code matters: the E variant adds Ethernet within that model group. Use the GL070 and GL070E per-code record rather than interpreting the group’s available interfaces as present on both codes. The G070, G070E and G070E-CAN record similarly requires a variant review when the connection requirement changes.
Start a Kinco Ethernet HMI shortlist with three questions: does the exact code provide the required port, does the PLC expose the intended service, and does the applicable software release provide the required driver? Screen size can then be assessed alongside cabinet fit, supply and operator needs. It cannot substitute for these connection checks.
For larger candidates, compare single-port and E2 entries in the G2100E variant record. Use the per-code port count and documented behavior rather than assuming every suffix shares the base model’s network arrangement. Two Ethernet ports do not automatically establish independent networks, bridging or a particular topology. Their documented function must fit the machine plan.
The Ethernet HMI directory supports model browsing. Keep the final selection tied to the product’s specific interface and software record, and request the applicable manual for unresolved port behavior. A directory filter identifies candidates; it does not validate a PLC project.
Changing a working serial connection to Ethernet can require PLC service configuration, new HMI driver settings, revised addresses and a network ownership review. Record those actions before treating the change as a simple cable substitution. The installation should have a defined test and recovery route if the proposed arrangement does not yet meet acceptance.
Separate Project Transfer from PLC Data
The engineering computer may download an application over USB while the HMI reads the PLC over serial. Alternatively, both tasks may use Ethernet but involve different endpoints and services. Keep separate records for computer-to-panel transfer and panel-to-controller data. A successful download establishes only the relevant transfer result.
After transfer, confirm the project target and active communication channel. Display a known PLC value and compare it with the engineering tool under an understood machine condition. Check address interpretation, type, signedness, scaling and word order. A familiar screen appearing on the panel does not establish that its displayed values are live or mapped correctly.
Only after known reads pass should the team review controlled writes. Use an approved commissioning variable and maintenance condition, confirm PLC interlocks and read-back, and keep the PLC responsible for control and safety logic. Do not use an operator command as a general test of whether Ethernet is working.
Test Physical Access and Application Communication
For a serial first-read record, identify the panel channel, electrical mode, cable drawing, PLC port, protocol settings and test address. Establish whether a valid response is received, then whether its value matches the engineering reference. If every request fails, inspect the channel and protocol before changing an entire screen’s objects.
For a network first-read record, identify the HMI endpoint, controller service, approved route, driver and chosen variable. Establish physical access and correct addressing before evaluating the application response. Retain the device identity so a reachable but unintended controller cannot be mistaken for the target.
Network Reachability Versus Valid PLC Values
A link indication or ping can help locate a physical or addressing issue. Neither proves that the required service accepts the driver’s requests. A valid protocol response then needs a separate meaning check: compare the same variable in the engineering tool and verify update behavior. Receiving a plausible number from another accessible address is not acceptance.
If some values work, compare their device areas, widths and permissions with the failing ones. If failures occur only during particular machine activity, record that condition and the installed wiring or network arrangement before changing parameters. Use the PLC No Response diagnostic guide to organize the observed failure stage.
Document the Preferred Route and Open Checks
State the selected route, the reasons it fits the actual machine, and the changes still required. Keep the full panel code, PLC identity, software release, driver, wiring or network references and first-read results together. Name the owner of unresolved service, cable or target questions. This makes selection reviewable before a hardware order or changeover.
Interface Choice Questions
Should an existing serial PLC link be changed to Ethernet?
Decide from supported services, maintenance needs and required changes. A working serial route can remain appropriate when it meets the machine requirements.
Does a successful Ethernet download prove PLC communication?
No. Verify the HMI-to-PLC driver, service and known values separately from computer-to-panel transfer.
Which evidence is needed before reusing a serial cable?
Keep both pin assignments, electrical mode, channel identity and accepted serial settings. Confirm the installed bus and wiring against their applicable instructions.
