A digital input module is the card that tells a controller whether something is on or off - a pump running, a level switch tripped, a limit reached, a hatch open. It has no interest in how much; it only reports a binary state for each channel. This guide takes the practical hardware view: how a discrete input card senses contacts, why dry and wet contacts are wired differently, what input filter time does and why you would adjust it, and how channels are grouped by voltage. These details decide whether a field signal reads reliably or chatters and lies.
Digital Input Module in one line: A digital input module (discrete input card, or DI card) is a PLC or RTU module whose channels each sense a single on/off condition from a field device such as a switch, contact, or proximity sensor. It detects whether current is flowing in each channel, applies a filter to reject noise and contact bounce, and reports each channel to the processor as a clean logical 1 or 0.
Each channel of a digital input module contains a circuit that decides whether an input is present. For a DC input, current flowing into the channel above a threshold voltage reads as on, and below it as off, with an isolation stage - often an optocoupler - separating field wiring from the module's internal logic so a field fault cannot reach the processor. AC input modules do the same job for line-voltage contacts. The channel is deliberately built with a defined on-threshold and off-threshold so a marginal signal does not flicker unpredictably around the boundary.
A key distinction in wiring is dry versus wet contacts. A dry contact is a bare switch with no voltage of its own, so the input module or an external supply must provide the power that flows through the closed contact. A wet contact already carries a voltage when closed, such as the output of a relay or a powered sensor, and the module simply senses that voltage. Knowing which you have determines how the loop is powered and whether you tie the field common to the module's positive or negative rail. Getting it backward is a classic cause of an input that never turns on, or one that appears stuck on.
Real field contacts are messy. Mechanical switches bounce when they close, sending a burst of rapid make-and-break transitions before settling, and long field cables pick up electrical noise. Digital input modules apply an input filter - a short configurable delay, often adjustable in milliseconds - that requires the input to stay in a new state for the filter time before the module accepts the change. A longer filter rejects bounce and noise reliably but slows the response to genuine fast events; a shorter filter responds quickly but risks counting noise as real transitions. Matching the filter to the signal, longer for a chattery mechanical limit switch and shorter for a clean electronic proximity sensor, is part of good input configuration.
Channels on a DI card are usually organized into groups that share a common terminal and, often, a single input voltage. This is why a card is specified for, say, 24 VDC or 120 VAC inputs, and why you cannot mix arbitrary voltages across channels on a group that shares a common. Grouping keeps wiring tidy and lets an installer land many field commons on one terminal, but it also means a group's shared common becomes a single point that affects every channel tied to it. Planning which signals share a group, and keeping a spare channel or two, saves rework when a plant adds instruments later.
Digital inputs generate much of the status and alarm information a SCADA system relies on. Run/stop confirmation, high-level and low-level switch trips, ESD activation, gate and hatch positions, and equipment fault contacts all arrive at the controller through DI channels before being polled up to a platform like Merobix. When an operator sees a pump status flip to running or a tank high-level alarm appear on a dashboard, a discrete input channel changed state to make that happen.
Because these signals often drive alarms, input quality directly affects alarm quality. An unfiltered or poorly wired discrete input that chatters can flood a SCADA alarm list with a switch that toggles hundreds of times an hour, burying real events. Correct filtering at the module, sound dry- versus wet-contact wiring, and good grounding are therefore not just hardware hygiene - they are what keeps remote monitoring trustworthy, so an operator watching an unmanned site can believe that a status change on the screen reflects a real change in the field.
A dry contact is a plain switch that carries no voltage of its own, so the input module or an external supply must provide the power that flows when it closes. A wet contact already has a voltage present when closed, such as a relay or powered sensor output, and the module just senses it. The two require different wiring for the input to read correctly.
It is a short delay that requires an input to hold a new state before the module accepts the change, rejecting contact bounce and electrical noise. A longer filter is more immune to chatter but slower to react to fast events, while a shorter filter reacts quickly but may pass noise. You match the filter to how clean and how fast the signal is.
No. A digital input only senses on or off - whether a contact is open or closed. To measure a continuous quantity like level, pressure, or temperature you need an analog input module instead. A discrete input can, however, tell you that a level switch has been reached, which is a threshold event rather than a measurement.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.