Power-generation and process skids often must present CompactLogix diagnostics, Caterpillar ATS/generator data, and other serial citizens to an Emerson DeltaV controller that offers only one RS-485 Modbus RTU master port. CompactLogix has no native Modbus stack on Channel 0 DF-1, Caterpillar devices frequently speak Modbus ASCII, and ASCII versus RTU cannot share a wire without a translator. The durable pattern uses a Miille-class DF-1/Modbus bridge at the engine tier and a ProSoft MVI69-MCM (or equivalent) so DeltaV polls one coherent RTU map.

Inventory every node’s physical layer, frame type, and master/slave role before the first RS-485 splice.

Protocol inventory

Mixing ASCII and RTU on one segment produces intermittent framing errors because the silence rules and character encodings differ. A converter that re-encodes frames is mandatory.

Reference architecture

1. Miille MARC Omnii-Comm DIN266 masters Caterpillar ASCII devices on RS-485 and presents DF-1 to CompactLogix CH0
2. CompactLogix maps mirrored registers into controller tags / integer files
3. ProSoft MVI69-MCM exposes a Modbus RTU slave image to DeltaV on a dedicated RS-485 trunk
4. DeltaV remains the sole master on that trunk; CompactLogix does not compete as a second master

ProSoft MVI69-MCM essentials

Port 2: Modbus RTU Slave
Slave ID: unique (e.g., 1) — no clash with field devices
Baud: 19200 8-N-1 (match DeltaV)
Inter-message delay: ≥3.5 character times
Backplane: AOP input/output assemblies (e.g., 250 words)
PCB configuration under revision control

Terminate and bias the RS-485 trunk; floating idle voltage is a commissioning red flag.

RS-485 trunk practice

• Belden 3106A-class 120 Ω shielded twisted pair
• 120 Ω termination at both physical ends only
• Stubs under ~1 m; total length within baud-dependent limits (~1200 m at low baud)
• Shield grounded at one end (typically DCS cabinet)
• Fail-safe bias if the master does not provide it

Miille DIN266 role

Configure the DIN266 as Modbus master toward the Caterpillar RS-485 devices and as DF-1 peer toward CompactLogix CH0. Power is typically 10–30 VDC on DIN rail. Serial parameters on both ports must match the field devices and CH0 exactly—baud, parity, and duplex. Internal maps are project-specific; never assume a default profile matches EMCP 4.x holding registers without opening the vendor configuration utility and exporting the map into the turnover package.

Register map discipline

Publish a signed table: device, Modbus address (clarify 40001 vs zero-based), data type, scale, update rate, and write authority. Example pattern: ATS 40001–40050 → N10:0–49; generator 40051–40150 → N11:0–99; critical coils write-through only where operations approved. Commission with a known pattern register before enabling process values. Commands from DeltaV should land in CompactLogix first, then forward through the translator so the DCS never dual-masters the Caterpillar trunk.

Master loading and parity end-to-end test

1. Scope or meter A–B idle bias; confirm terminations
2. Poll one holding register end-to-end from DeltaV
3. Prove ASCII devices respond through Miille before enabling writes
4. Watch ProSoft status words for timeout counters
5. Forbid a second Modbus master “temporarily” on the DeltaV trunk
6. Document slave IDs on the cabinet door; duplicate IDs create intermittent ghosts

Cross-platform links still depend on spared converters and controllers under PLC/PAC standards—treat gateway configuration as controlled firmware, not tribal knowledge on a laptop.