Program a MicroLogix 1500 LRP without unplugging the HMI

The answer: two ports, one cable, no swapping

An LRP carries two serial ports. Channel 0 is the DF1 channel the panel driver talks to, and it stays exactly as commissioned. The second port sits on the left end of the controller, and the product literature lists it as a programming/HMI port in addition to Channel 0. The controller's user manual, publication 1764-UM001, shows the serial connection from the computer to the controller. One null-modem cable on that port gives you a permanent programming path, and the panel link never comes down between visits.

The left-end port can carry more than the programming link. If a later job puts a Modbus configuration on the LRP and runs into a firmware issue with it, the ML1500 LRP Modbus configuration firmware fix page is the reference.

Recommendation: If the controller is a MicroLogix 1500 LRP, fit a null-modem serial cable from the programming computer to the left-end port and leave it fitted. Keep the panel on Channel 0 with its DF1 settings untouched, and program beside it. On a base 1500 with a single serial port, plan the cable swap into each programming visit, because there is no second port to use.

What you need

• A null-modem RS232 serial cable long enough to reach from the computer, or its adapter, to the left end of the controller. For a computer on the cabinet door, a 6 ft cable usually reaches; a laptop on a bench 10 ft away needs 15 ft.
• A serial port on the programming computer, or a USB serial adapter. An adapter works for programming; if a download times out through one, the USB serial adapter timeout fix covers the usual causes.
• The controller program file and the panel project, so both stay in step.
• Put the machine in a safe state before you open the panel. The serial ports are low voltage; the power terminals are not.

Steps

1. Confirm the second port. Look at the left end of the controller. The two-port model is the LRP; its catalog number reads 1764-LRP. A base 1500 has one serial port and no connector on the left end. If the port is missing, skip to the last section.
2. Leave Channel 0 alone. Note which connector the panel cable uses, then keep hands off it. Nothing in the channel configuration changes for this job.
3. Connect the cable. Run the null-modem cable from the computer's serial port, or from the USB adapter, to the left-end port.
4. Point the software at the cable. In the programming software, select the DF1 driver for the serial port the cable uses. If the driver lists COM1 through COM4 and the adapter sits above that, the article on remapping a USB serial adapter COM port shows the move.
5. Go online and download as usual. The programming path runs beside Channel 0, so no channel edit is part of this job.

How to check it worked

Two checks, one per path.

Programming path: go online from the computer. The software reads the program and the controller status over the null-modem cable. If the link stays dead, work through the last section before touching any settings.

Panel path: stay online and watch the panel for a minute. Values that move on their own, a clock word or an accumulating counter, show the DF1 link on Channel 0 still runs. If the panel freezes, reseat the Channel 0 connector at both ends first; the programming job gave you no reason to change the panel's driver settings.

Example: 6 downloads in a commissioning week

The inputs, with where each comes from:

• One MicroLogix 1500 LRP with two serial ports, Channel 0 and the left-end port. The port list is documented for the LRP model.
• One HMI panel on Channel 0 over DF1, already running. That is the job's starting point.
• 6 online programming sessions in the week, and each swap of a shared connector takes about 2 minutes unplugged plus 2 minutes back. Those swap times are the example's assumption, from a typical crowded cabinet.
• One shared port would mean 2 connector moves per session, unplug the panel cable and reconnect it, with the panel link down for the whole session, roughly 30 minutes of panel outage per 60-minute session.

The rule in words: with one port serving both devices, every session costs two connector moves and one panel outage; with the left-end port carrying the computer, every session costs no moves and no outage once one cable is fitted.

The arithmetic:

• Shared: 6 sessions × 2 moves = 12 connector moves; 6 sessions × 1 outage = 6 panel outages, about 180 minutes of panel downtime in the week.
• Left-end port: 6 sessions × 0 moves = 0 moves; 0 outages; 1 cable fitted once, about 5 minutes of work.

The result: 12 moves and 6 outages drop to 0 and 0, and every session runs with the panel live.

The decision: one visit after the panel is live is a wash. From the second visit on, the left-end port wins. Fit the null-modem cable once and leave it for the life of the job.

When the controller has only one port

A base 1500 gives the panel and the computer a single serial port between them. Two rules keep that workable:

• Take turns on purpose. Schedule programming for changeovers or breaks, and keep each swap short. The routine is the same one described in sharing one HMI programming cable with the PLC link.
• No splitters. A DF1 serial port answers one initiator at a time, and a Y cable carries no traffic control, so the two streams collide and both links fail. The same failure is why two HMI panels fail on one PLC serial port.

If programming becomes a weekly job, spec the two-port model into the next panel revision. That second port is the whole difference between the two controllers.

If the programming link will not connect

Check in this order:

1. Port identity. The cable is seated in the left-end port of the LRP, and the panel cable still sits in its own connector. On a crowded panel the two are easy to confuse.
2. Cable type. Null modem. The transmit and receive lines cross; a straight-through serial cable leaves each end listening where only it transmits.
3. Driver and port. The software's DF1 driver points at the serial port the cable actually uses.
4. Adapter. Swap in a different USB adapter, or test the cable and adapter pair on another machine.
5. Everything else. When the computer side checks out and the link sits dead anyway, the article on an HMI programming link dead while the PLC link still works lists the remaining causes in the order to try them.

Then the decision, for each case. LRP fitted and the cable seated in the left-end port: program beside the panel and stop swapping cables. Base 1500: schedule the swaps for changeovers and spec the second port at the next revision.

Questions