No. The panel's USB port loads the panel project, and its serial link to the PLC carries the application data the screens display; this class of panel has no pass-through function, so a PLC download needs its own cable to the PLC port. Plan the run against the commonly cited RS-232 figure of 15 m, about 50 ft.
No, and retrying will not change it. The USB cable that loads a project into the touch panel programs the panel. The serial cable from the panel to Port 1 on the PLC carries the application data the screens display. A PLC program download is a third connection, laptop straight to the controller, and the common small touch panels offer no pass-through that bridges it: the documented answer is to connect the programming cable directly to the device you want to program. Below, the two links separated, what each symptom on the machine points to, and the recovery with the cable run planned against the RS-232 length limit.
Two links, two jobs
The laptop-to-panel USB link exists to move the panel project: screens, tags, what the operator sees. The USB 2.0 specification allows a 5 m cable segment, which is why that cable reaches from a laptop at the cabinet door. The panel-to-PLC serial link on Port 1 runs the application protocol, polling registers at the baud and station address the project set. Neither endpoint is a bridge. The panel holds no translator between its USB port and its serial port, so traffic addressed to the PLC has nowhere to go.
Some panel families sell pass-through as a listed feature: you connect to the panel over the network and reach the controller behind it. When a panel has it, the feature list says so. When the documentation is silent, the panel has no route, and no cable arrangement, port swap, or settings change adds one. For the general question, see whether you can program a PLC through an HMI pass-through.
What each symptom points to
- The panel project download finishes and the machine runs exactly as before. You wrote the panel. The panel project holds the screens; the PLC program holds the logic. Two files, two destinations, and a success dialog on one says nothing about the other.
- The PLC software searches and finds no controller through the panel. Expected result. There is no path from the panel's USB port to Port 1 inside the panel. Ten retries give the tenth identical answer.
- The panel shows live values from the PLC. Good news, and the wrong door if you read it as a way in. It tells you the application link, its settings, and the cable path are healthy, which makes that port a safe bet for a direct programming cable.
- The panel shows a comm error while you work at the PLC. Its cable came off Port 1, or the port settings changed. Refit the cable and restore the recorded settings.
- Settings you changed to force a route broke the panel's data too. Both ends must match. Put back what you recorded before anything else.
Checks before you move any cable
Write down the panel link configuration before anything comes unplugged: the port number, baud rate, data bits, parity, stop bits, and station address. A small-PLC serial port commonly defaults to 9600 bps, 8 data bits, no parity, 1 stop bit, and the panel link may run faster if the project sets it. Label the panel cable and the port it came from.
Confirm the programming cable or interface from the PLC documentation for the exact CPU and port. The panel's serial cable working on Port 1 tells you the port is alive; it tells you nothing about the internal wiring of a programming adapter or the supply voltage some ports carry on one pin, so check the programming cable power pin before a different cable goes into a port the panel owns.
If the CPU has a second serial port, skip the swap entirely: leave the panel on Port 1 and use the second PLC serial port for the session, and the panel keeps its data throughout.
Keep the laptop within reach of the port. The USB lead to the panel works inside its 5 m segment; a longer haul needs an active approach, the subject of extending a USB programming cable past 15 feet.
The fix: a direct connection to the PLC port
- Record the panel link settings and label the panel cable and its port.
- Get the programming cable or interface the PLC documentation names for your CPU. If it is not on site, arrange it; loading another panel project is no substitute for PLC logic while you wait.
- Connect to a free port if the CPU has one. With one port only, move the panel cable off Port 1 and put the programming cable on that port. Expect a comm error on the panel for the duration.
- Open the programming software, establish communications, and confirm it reports the exact controller on the nameplate before any transfer.
- Back up the program already in the controller.
- Download the intended program following the documented transfer and operating-mode procedure.
- Verify the controller status, then refit the panel cable on its port with the recorded settings. The panel's live values return once the link is back.
- Run the first start under the site's authorization and lockout procedure with the area clear.
Step 3 is the whole reason the panel route looked tempting: one port, two cables. One at a time, settings recorded first, is the whole trick.
Example: covering an 18 m route to the PLC port
The inputs:
- Panel link working on Port 1, the situation on the machine; the panel displays data.
- Laptop to panel today over USB, inside the 5 m segment the USB 2.0 specification allows.
- One work surface for the laptop, an 18 m cable route from the cabinet. That distance is this example's given; measure yours along the tray.
- RS-232 planning limit of 15 m (50 ft), the commonly cited EIA/TIA-232 figure for runs at 9600 bps.
- RS-422 conversion reach, commonly cited at 1200 m at low data rates.
The rule in words: keep the total RS-232 cable at or under 15 m. Every meter past the figure trades against baud rate and cable quality, so a longer route needs the laptop closer or the link converted.
The arithmetic:
- Overrun: 18 m route - 15 m limit = 3 m.
- 3 m is 9.8 ft, call it 10 ft.
- Move the laptop 3 m closer: 18 - 3 = 15 m, exactly at the figure.
The result: at 15 m the direct cable runs 9600 bps with margin. At 18 m it sits 3 m past the commonly cited limit, the small-overrun case where a careful extension can still work.
The decision: 15 m or less, plain RS-232 to the port. About 10 ft over, follow the cable and baud practice in extending an RS-232 cable by 10 feet. Many meters over, convert the link; RS-232 to RS-422 cable distance covers the converter pair and the distances each data rate supports.
Verify before the machine runs
Three things prove the job: the programming software's controller status matches the nameplate, the backup of the old program is saved where you can find it, and the panel's live values return after its cable goes back on Port 1. Write down the date, the controller identity, and the backup filename; the next person at that machine will want all three.
A new program can move the machine on its first start. Bring it back under the site's authorization and lockout procedure, with the area clear and the operators told, before you call the transfer done.
If direct communications fail after the controller identity and the documented settings are confirmed, stop before repeated downloads or wiring experiments. The fault is then in the cable, the adapter, or the port, and each has a test: swap the cable, bench-test the adapter, or move to the second port.
The short version
Recommendation: Stop retrying the panel as a bridge the moment the PLC software finds no controller; that result is the panel working as documented, and no setting adds the route. Get the programming cable the PLC documentation names, keep the RS-232 run at 15 m or less by moving the laptop when the route is longer, and record the panel link settings before anything comes off Port 1. Use the second serial port when the CPU has one, and the panel never notices the session.
Questions
Can I download a PLC program through the HMI panel's USB port?
No. The USB port on the panel accepts the panel project. The PLC program is a separate file for a separate target, and this class of panel has no pass-through function that bridges the two. Some larger HMI lines list pass-through as a feature; when it is in the feature list it exists, and when the documentation is silent it does not. The PLC download needs its own cable to the PLC port.
The panel still shows live PLC data. Does that give me a way in?
No. Live data tells you the panel-to-PLC application link is running its protocol at its settings. A programming session talks a different protocol to a different endpoint. Use the working link as a diagnostic asset: it tells you the PLC port is alive and the cable path is good, so a direct programming cable on that same port should communicate once the settings match.
How long can the direct RS-232 programming cable be?
Plan on 15 m, about 50 ft, as the commonly cited EIA/TIA-232 figure at rates such as 9600 bps. Keep the run shorter where you can, use shielded low-capacitance cable, and drop the baud before you lengthen the cable. Well past that, convert the link to RS-422, commonly cited at 1200 m at low data rates.
Why did the panel lose its data while I was programming the PLC?
Because the panel cable came off the port, or the port settings changed. With one serial port, the programming cable and the panel cable take turns, and the panel reports a comm error while it is unplugged. Restore the recorded settings, put the panel cable back on its port, and the live values return.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.