Nearly every I/O card lives in two electrical worlds at once, and confusing them is a fast way to damage a module or spend a day chasing a channel that will not turn on. On one side is the logic power that runs the module's own electronics, drawn from the chassis. On the other is the field power that energizes the sensors, valves, and loops out in the plant. They are separated on purpose, usually by an isolation barrier, and they are sized, fused, and wired independently. This guide explains what each domain does, how isolation keeps them apart, and how to size and protect the field supply so a panel works reliably and a field fault stays on the field side.
Field Power vs Logic Power in one line: Logic power, also called backplane or system power, comes from the chassis power supply and runs the I/O module's internal electronics - its processor, backplane interface, and channel circuitry. Field power, also called field-side power, is a separate supply that energizes the actual field devices: it drives the loops that power sensors, the coils and lamps on outputs, and the sensing circuits on inputs. The two are typically kept apart by an isolation barrier inside the module, and the field supply is sized and fused independently of the logic supply.
Think of an I/O module as having a brain side and a muscle side. The brain side is the logic domain: the little processor, the backplane communications interface, and the low-level circuitry that reads channels and reports to the controller. This side draws its power from the chassis backplane, which is fed by the system power supply that also runs the CPU and the other modules. It consumes a modest, well-defined amount of current, and it is what keeps the module alive and talking even when no field device is doing anything. Losing logic power means the module goes dark and the controller sees it disappear from the backplane.
The muscle side is the field domain: everything that connects to the real world. On a digital output card, field power is what the card actually switches out to a solenoid or lamp, so without field power the outputs cannot energize anything even though the module's logic is perfectly healthy and the controller thinks it is commanding them. On a digital input card, field power provides the sense voltage that a closing contact returns to the input. On analog cards, field power often runs the loops that power two-wire transmitters. The field domain carries the real load current and the real hazard, and it is entirely separate from the tidy, low-current logic domain - which is exactly why a module can be online and responsive while its outputs do nothing, because the logic side is fed and the field side is not.
Between the two domains most modules place an isolation barrier - optical, transformer, or capacitive - so that the field side and the logic side do not share an electrical connection. The signal crosses the barrier as information, not as a direct wire, so a fault, surge, or ground difference on the field side has no galvanic path into the backplane and on to the controller. This is why a lightning-induced spike on a field wire, or a miswired output that shorts field power, can destroy the field side of a module while the rest of the rack keeps running: the barrier confined the damage. Isolation is one of the main reasons quality I/O cards cost what they do, and it is doing exactly this job even when nothing is going wrong.
The barrier also frees the two domains to sit at different voltages and references. The logic side runs at whatever the backplane provides, while the field side can be 24 VDC, 120 VAC, or whatever the loads require, referenced to the field grounding scheme rather than the control system's. This separation is what lets you fuse and switch the field supply on its own, kill field power for maintenance on the loads without dropping the module off the network, and keep field-side ground loops out of the sensitive logic. The practical wiring consequence is that you must feed both domains: a module with logic power but no field power is alive and confusing - it reports healthy, it accepts commands, and yet its field side does nothing, which is one of the most common panel head-scratchers for someone who does not realize there are two supplies.
Because the field domain carries the real load current, its supply has to be sized and protected for that current, independently of the logic supply. Add up what the field side actually draws: the coil and lamp currents on output points, including inrush surges that briefly exceed steady-state, the loop currents feeding transmitters on analog inputs, and the sense currents on digital inputs. Size the field power supply for that total with margin, and remember that inrush from incandescent lamps and inductive coils can momentarily demand several times the running current, so a supply chosen only for steady state can sag or trip when several loads energize together. Then fuse the field side appropriately - often per group or per point where the module supports it - so a shorted valve or a faulted lamp clears its own fuse instead of collapsing the whole field supply or damaging the module.
Field power loss is a particularly sneaky failure because the module and controller stay perfectly healthy while every field device on that card goes dead, and on a remote unmanned site nobody is standing there to notice the outputs stopped working. This is where cloud SCADA is valuable: many modern I/O modules provide a field-power-present or field-supply status bit, and a platform such as Merobix can surface that flag alongside the process so a blown field fuse or a tripped field supply raises an explicit alarm rather than presenting as a puzzling situation where the logic commands outputs that never move. Being able to see, from anywhere, that a specific card has lost its field side lets an operator distinguish a power problem from a device problem and send a technician with the right fix instead of troubleshooting healthy logic in the dark.
The most common cause is missing field power. An output module's logic side can be perfectly healthy - online, accepting commands, and reporting the point as on - while its field side has no power, in which case there is nothing to actually energize the load. Check the field supply feeding that card and its field-side fuse. Because logic power and field power are separate domains, a module can look completely healthy on the network while its outputs do nothing.
You need a field supply that is sized and fused for the field load, but whether it is a physically separate unit depends on the design. The chassis power supply feeds the logic side; the field side draws the real load current for coils, lamps, loops, and sense circuits, and that current must be provisioned and protected on its own. Many panels use a dedicated field supply so the field side can be sized for inrush, fused independently, and switched off for maintenance without dropping modules off the backplane.
The isolation barrier separates the field domain from the logic domain so there is no direct electrical connection between field wiring and the backplane. It passes the signal as information rather than as a wire, so a surge, short, or ground difference on the field side cannot reach the controller, and it lets the two sides run at different voltages and references. It is why a field-side fault can damage the field side of a module while the rest of the rack keeps running.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.