DL250 Remote Analog Reads: Choose a Reliable Data Path

Read the DL250 analog value at one PLC, then transfer the value over a communications link; splitting the field signal is only appropriate after checking the signal type, input wiring, and source drive capacity. For remote access, choose the communication path the remote facility can support rather than assuming a particular modem or network arrangement will work.

Stop trying quick fixes that leave the signal path uncertain

Adding a second PLC input or swapping in a cheaper modem can appear faster than designing the data path, but neither resolves the underlying compatibility question.

Attempt	Why it can fail	Better first check
Connect two PLC analog inputs directly to one signal	The inputs may load the source, alter the measurement, or require a different loop topology. The result depends on whether the signal is voltage or current and on the source's drive capability.	Identify the signal type, source, input type, and total load before wiring a second input.
Use a low-cost, non-supported modem at the PLC end	Modems can differ in compatibility and setup behavior. Past use of a non-vendor modem had periodic problems, and the PLC-side modem was not supported by the PLC vendor in that account.	Check current official compatibility and support information before substituting a modem.
Assume an internet connection alone makes the register available	A communication module, a configured data path, and a suitable remote access arrangement are still required. A network connection does not by itself identify which PLC data the computer should read.	Plan the PLC-to-computer communications path and verify the data mapping.

For a production restore, return to a known-supported PLC-side communications device and a single PLC reading of the analog signal. Treat an unsupported modem or improvised signal split as a test, not a dependable repair.

Choose the remote link from the facility’s available connection

The practical choice depends on what communications service exists at the remote facility. The described options are an ECOM card in a 205 base when the remote site has an internet connection such as DSL or T1, or a modem when the site has a phone line. These are options, not plug-and-play recipes: confirm the module, PLC, software, and remote computer support for the actual installation.

• Network available: Evaluate the ECOM-in-205-base approach and confirm the PLC can expose the required data to the remote application.
• Phone line only: Evaluate a modem connection and confirm both ends can establish and maintain the intended link.
• Unknown or changing connectivity: Have the site network owner document the connection type, addressing, routing, and access controls before selecting hardware.

When using an internet-connected PLC, do not expose the controller directly to an untrusted network. Have the network owner provide an approved remote-access route, with firewalling and authentication appropriate to the site. Do not assume a modem or Ethernet module includes those protections.

The specific historical hardware recommendations are dated. Check current manuals and official support for module compatibility, supported software, modem requirements, and current security guidance; do not buy a device based only on an old description.

Keep one PLC responsible for the analog measurement

The least ambiguous architecture is to wire the analog instrument to one PLC input and distribute the measured value to the other controller through a communications link. This avoids making the field transmitter drive multiple analog input circuits and keeps the measurement path easy to diagnose.

1. Identify the analog source and its output type, such as voltage or current, from the instrument and wiring documentation.
2. Confirm the receiving PLC input is configured and wired for that signal type.
3. Read the value in the PLC that owns the input, then map and transmit that value through a shielded communication cable or another supported PLC-to-PLC link.
4. Configure the receiving PLC or remote application to consume the transmitted value, and define how the system should detect stale or missing data.

The evidence identifies shielded communication cable for transferring the value between PLCs but does not specify a protocol, cable pinout, register address, or data format. Use the manuals for the actual hardware to select those details. Keep analog scaling and units consistent at the receiving end; verify whether the transferred value is a raw input count or an already scaled engineering value before using it in control logic.

Check signal type and loading before wiring two PLCs

Do not treat “analog signal” as a wiring specification. A voltage output and a current loop respond differently when a second input is added, and the source instrument’s ability to drive the connected load determines whether direct sharing is viable.

Signal case	What to check	Decision
Current signal	Confirm that the instrument output and both PLC input circuits support the intended current-loop topology. For a series arrangement, calculate the load from the input impedances and wire resistance, then check it against the source’s drive capability.	Series connection may work if the source can drive the total load and the input wiring is compatible. Do not wire by assumption.
Voltage signal	Check the source output impedance, each input impedance, common/reference requirements, and whether the two inputs can share the same reference without creating a grounding problem.	Direct parallel connection can load the source or create reference issues. Use a suitable signal distribution or isolation device if direct sharing is not supported.
Signal type or source capability unknown	Read the instrument and input specifications; measure the field signal under normal operation and consult the wiring diagrams.	Do not connect the second input until the topology and load are known.

For a current loop, the total burden includes the input burden and wiring resistance. Compare that total with the transmitter’s allowable load at the loop supply voltage. If the source cannot drive the total load, use a properly selected signal isolator or splitter, or keep one PLC as the measurement owner and pass the value digitally. Confirm the device supports the loop’s signal range and required isolation before installation.

Configure the modem path without guessing compatibility

For a phone-line installation, the cited arrangement used a vendor-supplied modem on the PLC side and allowed a more standard modem on the computer side. The recommendation reflected a support and reliability tradeoff, not a guarantee that every modem pair will connect. The reported non-vendor modem experience included periodic problems.

1. Confirm the PLC-side modem is approved for the exact PLC and communications hardware, using current official documentation.
2. Confirm the PC-side modem and communications software support the required connection method.
3. Record the configured communication settings at both ends and match them to the hardware and software documentation; do not substitute guessed values.
4. Test connection establishment, data reads, and reconnection after a dropped call before relying on the link for operations.
5. Keep a known-compatible spare for the PLC side and, where practical, the PC side so troubleshooting can separate a failed modem from a PLC or line problem.

Historical experience described the vendor PLC-side modem as supportable and a non-vendor replacement as a gamble. Treat that as a reason to verify compatibility—not as a current product endorsement. If the approved modem is unavailable, ask official support to confirm a substitute before putting it into service.

Verify the value from instrument to remote screen

A successful connection is not proof that the remote computer is displaying the correct analog value. Check each stage so that wiring, PLC scaling, data transfer, and display errors do not look like one another.

1. Compare the instrument’s output at the PLC terminals with the input channel’s live value. Use the correct meter mode and the instrument documentation for the expected signal.
2. Check the PLC channel configuration and scaling. Confirm the displayed engineering units and range against the instrument’s configured range.
3. Read the value locally at the PLC that owns the analog input before troubleshooting remote communications.
4. Compare the locally observed value with the value received by the second PLC or remote computer while the process is stable, then repeat while the signal changes.
5. Interrupt or disconnect the remote path only during an approved test. Confirm the application indicates stale or unavailable data rather than silently presenting an old value as current.

If the local PLC value is already wrong, stay on the instrument, wiring, input configuration, and scaling path. If the local value is correct but the remote value is wrong or absent, investigate the communications path and data mapping instead of rewiring the analog source.

Escalate when compatibility or measurement integrity remains unclear

Stop and contact official support if the PLC-side modem or ECOM hardware compatibility is uncertain, if a proposed signal split exceeds the source’s load capability, or if the local analog reading changes after connecting a second input. Provide the PLC and module identification, instrument output type, input specifications, wiring diagram, communication hardware, and the local-versus-remote readings. Keep the single-PLC measurement and supported data-transfer path in service until the replacement design is verified.

Frequently asked questions

Stop before changing field wiring or commissioning an unsupported communications device if the signal topology or compatibility is unresolved. Escalate to official support with the hardware identifiers, signal specifications, wiring details, and test readings.