Adding Ethernet to a PLC-5 is not a matter of inserting a communication card into any open chassis slot. The 1785-ENET is a sidecar module that mechanically and electrically attaches to a compatible processor. The processor-and-interface combination then occupies the left side of the 1771 chassis. Treating it as an ordinary I/O card can damage connector pins, create a placement conflict, or leave the plant without a working engineering route.

The installation succeeds only when processor compatibility, two-slot chassis space, connector alignment, Channel 3A configuration, and recovery are verified together.

Understand what the 1785-ENET changes

The original Rockwell Automation manual describes the 1785-ENET as a single-slot interface that attaches to the side of an enhanced PLC-5 Series B or later processor. With an enhanced processor it adds Ethernet without consuming the existing DH+ or Remote I/O communication ports. The combined assembly is installed in the left-most chassis positions.

This distinction affects the whole work plan. The sidecar needs physical space beside the processor, a supported processor and firmware revision, programming software that can configure Channel 3A, and an Ethernet transceiver arrangement suitable for the installed module revision. Verify every catalog suffix and series marking from the actual hardware.

Useful spares and controller categories can be checked in PLC & PAC Systems, while related adapters and network hardware are organized under Communication & Networking.

Survey the chassis before shutdown

Record the chassis catalog number, power-supply type, processor catalog and series, firmware revision, installed modules, occupied slots, addressing method, and all active communication channels. Photograph the processor switches, cabling, terminal labels, and front-panel indicators. Export the PLC program and document the present upload and download path.

Confirm that the two left-most positions can accept the attached processor and interface. An existing module may need relocation, and that move can affect I/O addressing, block-transfer instructions, documentation, and field wiring. Do not relocate any module until the addressing consequences have been traced in the program and drawings.

Check the power-supply load for the final chassis arrangement. A supply that has operated for years near its limit should not be assumed to accept another module. Include normal input voltage, ambient temperature, and startup behavior in the assessment.

Protect the processor-side connector

Shut off chassis power and follow the site’s electrical isolation procedure. Rockwell explicitly warns that installing the module with chassis power on will damage it. Use ESD controls and place the processor on a clean, flat surface.

The connector header must be aligned carefully with the processor and interface. Bent pins can produce a dead module or intermittent sidecar-to-processor transfer faults. Press evenly, do not use excessive force, and tighten the captive screws as instructed. When removing the interface, lift the connected modules together, loosen the side screws, and separate them evenly rather than prying one corner.

Inspect the header under good lighting before installation. If a pin is bent, plating is damaged, or the captive hardware is missing, stop. Straightening a damaged high-density connector in the field can turn an observable defect into an intermittent failure.

Prepare Channel 3A and addressing offline

The interface uses Channel 3A. Confirm that the programming package supports its configuration and that the processor firmware meets the manual’s compatibility requirements. When configuration is performed online with the sidecar attached, Channel 3A can be recognized automatically; an offline project must designate the channel correctly.

Reserve the IP address, subnet mask, and gateway under the plant network plan. Check for duplicates before connecting the cable. The legacy manual describes BOOTP as enabled by default and also supports manual configuration after BOOTP is disabled. Use the plant’s current address-management process rather than relying on an undocumented temporary server.

Assign the Channel 3A diagnostics file before commissioning. The manual specifies an unused integer file number from 10 through 999 and creates a 44-word file. Search the existing program and HMI references before choosing the file. Reusing a file that appears empty can overwrite application data or make diagnostics unreliable.

Define the traffic and security boundary

Decide why Ethernet is being added. Programming access, PLC messaging, HMI polling, and historian collection create different loads and failure modes. List each approved source, destination, service, and expected update rate. A new network path should not become an unrestricted bridge into a legacy controller.

Place the PLC-5 segment behind managed industrial networking equipment and restrict access with the available network controls. Do not expose the controller to the public internet. Legacy controllers were designed before current security expectations, so segmentation, monitored engineering access, backups, and physical control remain important.

Commission in observable stages

Apply power with the Ethernet cable initially disconnected. Confirm the processor returns to the expected mode, existing I/O operates, and the sidecar indicators match the manual. Review Channel 3A diagnostics and processor fault information before introducing network traffic.

Connect the interface to a controlled segment and test basic reachability from one approved engineering station. Perform a read-only browse and upload first. Compare the uploaded project with the saved baseline. Then test approved messages or HMI clients one at a time while watching scan time, communication errors, diagnostics, and the behavior of existing DH+ or Remote I/O channels.

Do not declare success after one ping. Test a cold restart under the approved outage procedure, engineering reconnection, program upload, message recovery, and restoration after a disconnected cable. Verify that a duplicate IP or failed transceiver produces a diagnosable condition rather than unexplained controller disruption.

Keep a rollback path

Before the outage, define the exact point at which the installation will be reversed. Preserve the original processor position, engineering cable, network settings, project file, and known-good communication method. If the sidecar or connector fails, the team should be able to remove it and restore the former arrangement without improvising.

Record the final module series, processor firmware, IP configuration, diagnostics file, chassis layout, cable route, switch port, and test results. Update drawings and the spare-parts list. Ethernet improves service access, but it does not remove the lifecycle risk of the PLC-5 platform. Use the project to create a measured migration path rather than treating the sidecar as modernization by itself.