Lumaspec-rt analysis software

Begin with the required camera count and then check whether the application needs live viewing, quantitative analysis, automated alarms, archiving or plant-control functions. The range includes Viewer, Basic, Analyzer and Control packages, with Analyzer Multi 6 and Control Multi versions for 6, 12 or 24 simultaneous cameras. The numbered Multi designation gives the maximum simultaneous camera count for that package, while the standard package names do not state a numbered multi-camera limit. Function availability also differs between package levels, so communications, alarm and data-handling requirements should be confirmed before ordering. This prevents a system from meeting the camera-count requirement but lacking the required analysis or automation functions.

LumaSpec RT is designed for a 32-bit or 64-bit Windows computer with at least a dual-core 1.5 GHz processor and 4 GB RAM. The minimum graphics requirement is a dedicated card with 1 GB of 900 MHz DDR3 dedicated memory, while storage is listed as a 7200 rpm hard drive with a 16 MB buffer on a 3.0 GB/s SATA bus. The network interface must be Gigabit Ethernet and support jumbo packets up to 9014 bytes. These values establish a minimum operating baseline rather than a storage-retention calculation. For multi-camera recording, the workstation and storage plan should therefore be sized against the selected cameras, frame rates, archive duration and alarm-recording policy.

All package versions are compatible with MCS640, MC320 and MCL640 thermal cameras, and the software also supports pyrometer integration. A standalone installation can connect a camera and pyrometers directly to a Windows desktop or laptop over Ethernet. Larger systems can place multiple instruments on a common or dedicated network through switches, with programmable output devices connected where required. The selected Multi package sets the simultaneous camera ceiling, up to 24 cameras for Control Multi 24. During design, engineers should check network capacity, jumbo-packet support and the required I/O architecture rather than treating each camera connection as an isolated point-to-point link.

Integration can be implemented through OPC, Modbus or physical I/O, depending on the selected software package and optional interface modules. Modbus support covers serial and Ethernet connections, while physical I/O can include relays and analogue outputs. Inputs may originate from image-analysis conditions, OPC, Modbus or physical I/O, and processed results or alarms can be returned to a DCS or PLC. This arrangement supports monitoring, supervisory logic and closed-loop control where the plant system makes the final control decision. Engineers should define signal direction, update requirements, alarm latching and fail-safe behaviour during system design, because protocol support alone does not determine the control philosophy.

Each camera can process up to 32 ROIs, with point, line and area region types available for temperature display. ROI calculations can include minimum, maximum, average and standard-deviation values derived from the pixels within the selected region. Additional tools include histograms, isotherms, line profiles, orthogonal X-Y profiles, 3D profiles, trend charts and hot and cold spot detection. Alarm conditions can be combined with AND/OR logic, while computation channels can evaluate relationships between selected regions or points. In practice, this allows an engineer to trigger on a meaningful thermal pattern rather than relying on a single temperature value at one location.

Thermal records can be stored at different rates for normal and alarm conditions, and pre-buffered trigger logging can retain data from before an event. Images can be saved as JPG or BMP, recorded thermal video can be exported as AVI, and measurement data can be sent to Excel or text and CSV files. This combination supports event review, process documentation and external reporting without limiting analysis to the live workstation. No fixed archive capacity or retention period is stated, so those values depend on the host storage and the chosen recording policy. Storage calculations should include camera count, frame rate, alarm frequency, pre-buffer duration and the required retention period.

Automatic restart is intended for monitoring systems that must recover after an unplanned PC or server shutdown. When configured, the software can start, reconnect to cameras and load saved settings for frame rate, ROIs, analysis tools, alarms and communications. This reduces the amount of manual reconfiguration needed before thermal monitoring resumes. The function is particularly relevant to unattended multi-camera installations and process-safety applications where a stopped workstation would create a monitoring gap. It should still be combined with suitable power protection, host operating-system management and alarm handling for cases where the workstation or network cannot recover automatically.