After the sensor output type, input-module wiring, and Node-RED channel are matched, each beam interruption produces a repeatable digital state change that can be forwarded through MQTT to the database. A working dashboard button proves the downstream function, MQTT, and database path; it does not prove that the physical input is wired or addressed correctly.
Hardware and signal-path identification
Start at the field terminal and trace one signal path through the input module, SIMATIC IOT2040, Node-RED flow, MQTT connection, and database. The I/O module shown with the gateway is a separate electrical interface. Its input specification—not the gateway name alone—determines the accepted voltage range, input current, common-terminal arrangement, and compatibility with sourcing or sinking sensors.
Record the embedded-board order number. The two candidates identified for this installation are 6ES7647-0KA01-0AA2 and 6ES7647-0KA02-0AA2. Then read the attached I/O module label and terminal diagram. Do not select a GPIO channel merely because its software number resembles a terminal number.
- Record the gateway order number and the complete I/O-module identification.
- Locate the module's digital-input terminals, input common, supply terminals, and channel numbering in its manual.
- Trace the selected physical terminal to the channel exposed by the installed Node-RED node.
Check 1: Expect one documented chain from the sensor output terminal to one input-module channel and one Node-RED channel. Stop commissioning if the module identity or terminal mapping remains unknown.
Sensor output classification
The term PNP output here means a sourcing transistor output: when active, it supplies current toward the load. The term NPN output means a sinking transistor output: when active, it draws current from the load toward the reference conductor. These types require different input circuits and common connections.
Read the photoelectric sensor's complete model code and wiring diagram. Omron sensor families can contain electrically different variants, so brand and housing appearance do not identify the output type. Record whether the output is PNP or NPN and whether its operating mode is light-on or dark-on. Light-on and dark-on determine whether beam interruption activates or deactivates the output; they do not change an NPN output into PNP or vice versa.
Also distinguish a transistor output from a relay or dry-contact output. A transistor output requires correct polarity and a compatible load path. A dry contact does not source its own sensing voltage and must be connected through the input circuit prescribed by the I/O-module manual.
- Find the sensor model code on its label.
- Use the matching sensor wiring diagram to identify supply, reference, output, and any control wires.
- Confirm the output type and operating mode from the model-specific documentation.
Check 2: Expect the sensor documentation to state one definite output type—PNP, NPN, or relay—and to identify every conductor used. Do not infer conductor function from color without the model-specific diagram.
Electrical compatibility and field wiring
Connect the sensor only after comparing its supply and output ratings with the digital-input specification. The sensor supply must fall within the sensor's rated range, and the active output must remain within the module input's permitted electrical limits. The sensor reference and input-module reference must form the return path required by the selected input topology.
| Sensor output | Active-state behavior | Required input relationship | Common mistake |
|---|---|---|---|
| PNP, sourcing | Drives the output toward the positive supply | The input circuit must accept sourced current and provide the documented return path | Connecting it to an input intended only for sinking outputs |
| NPN, sinking | Pulls the output toward the reference conductor | The input circuit must provide current that the sensor output can sink | Using a common arrangement intended for PNP wiring |
| Relay or dry contact | Opens or closes an isolated contact | The module's prescribed sensing circuit must supply the input current | Treating the contact as a powered transistor output |
With power removed, wire the sensor supply and input-module common according to both diagrams. Connect the sensor output to one known input terminal. Restore power, then measure the output relative to the input reference in both beam states. Use the module's specified thresholds to classify those measurements as inactive or active; no universal threshold can be assigned without the module specification.
Check 3: Expect two stable electrical states at the selected terminal when the beam is clear and interrupted. If the sensor indicator changes but the terminal measurement does not, correct the sensor wiring or output configuration before working in Node-RED.
Node-RED channel configuration
The installed palette name must match the node actually placed in the flow. The installation referenced both node-red-contrib-IoT2000-gpio and node-red-contrib-iot2000-gpio; capitalization differences in a written package name do not demonstrate that either node is configured for the attached I/O module. Inspect the node's package identity, configuration dialog, channel selection, and deployment status.
- Create a minimal test flow containing only the SIMATIC IOT2000 input node and a debug node.
- Select the channel mapped to the wired input terminal.
- Deploy the flow and set the debug view to display the complete received message.
- Interrupt and clear the beam repeatedly while watching message arrival, payload value, and timestamp.
- If no messages arrive, test whether the node emits only on state changes or requires a configured polling mode. Read the node's local help instead of assuming continuous updates.
Trying every software pin obscures the fault because it mixes mapping, wiring, and configuration changes. Commission one documented terminal-channel pair and hold that mapping constant.
Check 4: Expect the debug node to show two repeatable logical states corresponding to the two terminal measurements. The logical sense may be inverted by light-on/dark-on operation; repeatability matters before polarity is normalized.
Layered signal-path commissioning
Separate the field-input test from the application flow. A button that writes a “tick” to the database validates the flow downstream of the button: its function processing, MQTT publication, PC-side Node-RED path, and database write. It bypasses the photoelectric sensor, I/O terminal, hardware driver, and input-node mapping.
| Observation | Fault boundary | Next action |
|---|---|---|
| Sensor indicator does not change | Optical alignment, target, sensor power, or sensor setup | Correct the field device before measuring the input |
| Indicator changes, terminal does not | Sensor output, conductor assignment, common, or electrical compatibility | Compare both wiring diagrams and measure at the terminal |
| Terminal changes, debug does not | Channel mapping, node configuration, driver, or deployment | Test the minimal input-to-debug flow |
| Debug changes, database does not | Function logic, MQTT path, PC-side flow, or database mapping | Compare the sensor message with the working button message |
If the sensor state is opposite to the required production meaning, normalize it once in the function logic. Define explicit states such as beam clear and object detected rather than relying on an unexplained 0 or 1.
Check 5: Expect the same physical event to produce the same named state in debug on every cycle, with no channel changes or manual injections.
End-to-end production verification
- Clear the beam and record the terminal reading, Node-RED payload, MQTT value, and database record.
- Interrupt the beam and record the same four points. Expect every layer to change to the defined object-detected state.
- Clear the beam again. Expect every layer to return to the original state without restarting Node-RED or changing channels.
- Repeat several crossings at the production sensor position. Expect one defined transition sequence per crossing and matching database entries.
- Restart the gateway and redeploy only if required by its normal startup process. Expect the configured input channel and logical interpretation to remain unchanged.
If rapid objects are missed, compare the physical pulse duration with the input module's filtering, the node's sampling or event behavior, the Node-RED processing interval, and the MQTT/database path. Read those values from the installed module and software configuration; a brief pulse can occur entirely between samples.
Check 6: Expect the field terminal, local debug output, MQTT message, and database entry to agree for beam clear, beam interrupted, and beam restored.
Frequently asked questions
What happens if I connect an NPN sensor as though it were PNP?
The input may remain permanently inactive or fail to reach a valid logic threshold because the required current path is missing. Rewire the input common and sensor output according to the NPN diagram and the I/O module's accepted input topology.
What happens if the sensor LED changes but Node-RED stays at 0?
Measure the selected input terminal relative to its documented common in both beam states. If the electrical state changes, correct the channel mapping or node configuration; if it does not, correct the field wiring or output compatibility.
How do I verify the complete SIMATIC IOT2040 signal path?
Clear, interrupt, and restore the beam while checking the terminal, debug payload, MQTT value, and database record in that order. The final verification passes only when all four points show the same defined state transition for every crossing.