Red Lion Crimson HMI — Comms Failure & Tag Errors

Red Lion · intermediate · 25 min

When a Red Lion Crimson HMI (CR1000/CR3000/G3) shows a device offline or stale tags, the cause is usually the comms driver, not the panel. Learn how Crimson scans a device, why one bad tag can stall a whole block, and how to prove the link with IsDeviceOnline().

ℹ️ On a Crimson panel, a communication error, timeout, or negative reply makes Crimson stop scanning that device and start over — and if the first item it reads is invalid, it stops reading the rest of that device. One bad tag can look like a total comms loss.

How Crimson talks to a device

Red Lion Crimson (the software behind CR1000, CR3000, Graphite and the older G3 panels) polls each external device — PLC, drive, meter — over its configured driver. Understanding the scan explains most "HMI not updating" calls:

• On a communication error, timeout, or negative reply, Crimson stops scanning that device and starts the scan over.
• Critically, if the first item it attempts to read is invalid, it will not attempt to read any other items from that device. A single bad address at the top of the block can make the whole device look dead.

So "all my tags are stale" often isn't a dead cable — it's one mis-mapped tag stalling the block.

Prove the link with IsDeviceOnline()

Before chasing wiring, confirm comms state in software. Crimson exposes IsDeviceOnline(), which returns ON or OFF depending on whether the panel has communications with that device. Put it on a diagnostic page (or read it while debugging) to know definitively whether the panel thinks the device is reachable.

Serial link checklist

For a serial (RS-232/RS-485) device that won't come online:

• Verify the cable connection end to end.
• Confirm the port is configured with the right communications driver and the correct settings (baud, parity, data/stop bits, protocol address) for that device.
• Check the port isn't damaged — swap to a known-good port/panel to isolate.

Ethernet link checklist

For an Ethernet device:

• Make sure the cable is in the correct Ethernet port on the unit.
• Remember that older products (DSP, CSMSTR, G3, PTV) have no auto-crossover detect, so a direct panel-to-device connection needs a crossover cable (through a switch, straight-through is fine).
• Verify IP address, subnet and the protocol (e.g. Modbus TCP unit ID / slave address) match the target device.

Step-by-step

1. Read IsDeviceOnline() for the device — ON or OFF?
2. OFF → check the physical layer (serial cable/port/settings, or Ethernet port/crossover/IP) using the checklists above.
3. ON but tags are stale/blank → suspect the tag map. Look for an invalid first item in the block (wrong data type, out-of-range register, address the PLC rejects) that stops the rest of the reads.
4. Fix the offending address, re-download the Crimson database, and confirm the tags update.
5. For software error messages in Crimson itself, check the Crimson 3.x error-message reference for the exact text.

Never do this

Don't "fix" stale data by hiding it behind a default value or a cached tag — that puts stale process values in front of an operator. Find why the device or the tag went offline and restore the real read.