Exception 04 (0x04) — Server Device Failure

An unrecoverable error occurred inside the server while it was performing the requested action. Unlike 01-03, the request itself was well-formed — the device failed to service it.

Start free Modbus → canonical

Diagnosis

When you hit this

A gateway lost its downstream serial link, so the register exists but cannot be populated.
The device is in a fault state and refuses I/O until the fault is cleared.
A hardware fault on the module backing that address range.

Resolution

How to fix it

Separate the device from the link
Read a register you know is served locally by the gateway. If that works and the target fails, the downstream link is the problem.
Check the device's own fault state
Exception 04 frequently accompanies an active alarm on the controller. Clear the alarm, then re-read.
Do not hammer it
Repeating a failing request at full rate delays recovery on many devices and can mask the underlying fault in your logs.

Normalization

What Forge does about it

This is a transport failure, so there is nothing for Forge to normalize: the reading never arrives. What Forge does is refuse to let the gap look like good data. The read-time dropout check flags a field that fell to zero and recovered as a communication glitch rather than a real measurement, and the stuck-sensor check fires when a value repeats for 20 consecutive readings — which is what a cached or last-known value looks like after a link drops. Forge does not retry or reconnect for you; that is your client's or your gateway's job.