INDUSTRIAL THERMAL IMAGING INTEGRATION GUIDE

How to Integrate Thermal Cameras with PLCs, SCADA and Industrial Networks

A Practical Guide Using the IRSX Smart Thermal Camera

Leslie M. Tack, Ph.D. | CTO, Pembroke Instruments, LLC | September 23, 2026

Fixed thermal cameras can provide continuous temperature measurements, alarm states and thermal trends—turning periodic thermographic inspections into automated condition monitoring. This guide covers IRSX-I640 and IRSX-I336 integration with PLC, SCADA, historian and IIoT systems.

Why Integrate Thermal Cameras?

Many electrical and mechanical faults change temperature before visible damage occurs. Integration lets fixed thermography become continuous condition monitoring.

For reliable trends, control or record load, airflow, angle, distance, emissivity and reflected energy. Gate measurements using equipment operating state where appropriate.

IRSX Camera and Interface Overview

The IRSX is a smart radiometric LWIR camera that measures temperature, evaluates ROIs and raises alarms on board. IRSX-I640 provides finer spatial detail; IRSX-I336 provides compact fixed monitoring.

View IRSX Thermal Cameras →

Recommended Integration Architecture

1. Use one owner per decision; do not re-threshold the same alarm differently in camera and PLC.
2. Hardwire critical signals that must survive a network fault.
3. Match data rate to the asset: about 1 s polling for PLC data and 10–60 s for trends.
4. Gate measurements using a running/load signal.

Protocol Integration Guidance

Modbus TCP

Give the camera a static IP or DHCP reservation on the controls VLAN. Enable Modbus TCP (default TCP 502). Map ROI outputs to registers, configure the PLC as client, poll with FC03/FC04 every 500–1000 ms, and verify decoding against the web interface. Confirm 32-bit float/scaled-integer format, word order and 0- versus 1-based addressing.

PROFINET

For Siemens S7-1200/1500 systems, install the IRSX GSDML in TIA Portal, add the camera to the PLC PROFINET network, assign the physical device name with DCP, insert I/O modules for ROI values/alarms, set update time and verify the device is green in online diagnostics. A 32–128 ms update time is already faster than thermal faults develop.

OPC UA

Enable the OPC UA server (default TCP 4840). In production use Sign & Encrypt with Basic256Sha256 or newer, exchange trusted certificates, use a read-only historian account, create monitored-item subscriptions rather than repeated polling, and store engineering units and source timestamps.

MQTT

Use MQTT for cloud dashboards, IIoT gateways and predictive-maintenance platforms. Prefer TCP 8883 with TLS. Use a unique per-camera client ID, publish trends every 10–60 seconds and alarm events on change with QoS 1, and configure retained status plus Last Will.

REST API / OpenAPI and HTTPS

Use REST for configuration management and on-demand data rather than continuous control. Typical jobs include configuration backup/restore, ROI and emissivity changes, alarm-triggered radiometric snapshots and CMMS attachments. Use HTTPS and restrict Administrator access to engineering staff.

GigE Vision + GenICam

Use image streaming when onboard ROI analysis is not enough. Discovery/control uses GVCP (UDP 3956); streaming uses GVSP. Use a dedicated GigE NIC, jumbo frames and adequate receive buffers. Request radiometric 16-bit pixels and apply GenICam temperature scaling. Keep streaming traffic off the PLC network.

Digital I/O and Lua Scripting

Hardwire signals that must work during a network fault. A critical alarm can feed a PLC input or relay; a load/running input can enable measurement. Confirm voltage levels and sourcing/sinking requirements before wiring. Lua can implement phase-to-phase ΔT, rise over ambient, 30–60 s persistence and load gating.

ROI Data Model and Alarm Thresholds

Draw ROIs over the component rather than surrounding background. Aim for at least 3×3 pixels and preferably 10×10. Pair monitored ROIs with a reference ROI, set emissivity per ROI, and allow camera warm-up before enabling alarms.

For electrical assets, use ΔT-based criteria and load-aware measurements. For mechanical/process assets, establish limits from a normal baseline and equipment-manufacturer limits. Add 2–3 °C hysteresis and 30–60 s persistence to reduce nuisance alarms; latch critical alarms until acknowledged and include the Valid flag in alarm logic.

Network, Cybersecurity and Environment

• Place cameras in an OT zone/VLAN and allow access only from required systems.
• Use static addresses or DHCP reservations before controls handover.
• Separate GigE Vision streaming from fieldbus traffic.
• Synchronize camera, PLC and historian time with NTP.
• Change default passwords and disable unused protocols.
• Keep firmware current and back up ROIs, configurations and Lua scripts.
• Do not expose the web interface or Modbus directly to the internet.

Commissioning Checklist

• ☐ Confirm target, working distance and pixels-on-target.
• ☐ Mount and focus camera; fit air purge/shield if needed.
• ☐ Verify 24 VDC and I/O wiring.
• ☐ Set static IP/reservation and NTP.
• ☐ Change passwords and disable unused protocols.
• ☐ Complete warm-up and set emissivity, window transmission and range.
• ☐ Draw measurement/reference ROIs and validate readings.
• ☐ Load and back up Lua logic if used.
• ☐ Verify Modbus decoding or PROFINET status.
• ☐ Verify OPC UA subscriptions or MQTT topics.
• ☐ Force-test alarms through PLC, HMI, historian and work-order path.
• ☐ Test network/power failure behavior.
• ☐ Log a baseline under normal load and review thresholds after 2–4 weeks.
• ☐ Export configuration with as-built documentation.

Troubleshooting

Related Thermal Imaging Resources

• Thermal Imaging for Industrial Preventive Maintenance
• How to Set Up an IRSX Thermal Camera
• How to Select a Thermal Camera
• Industrial Thermal Imaging Cameras & Applications

Technical note: Protocol port numbers and client configuration steps follow the source guide. Confirm IRSX-specific register maps, GSDML, OPC UA node IDs and I/O ratings against the manufacturer's firmware documentation.