Environmental test chamber HMI: one screen holds the climate, one program runs the cycle

An HMI built into the chamber panel: the industrial PC and the PAD run identical features, and the Android app adds a standby screen plus manual shortcuts. 15 modules run from device monitoring and temperature-humidity curves all the way to program editing, PID and EEV parameters, upkeep and logs; analogue channels reach 64 inputs and 32 outputs; terminals talk to one platform layer, which talks to the PLC and the vendor API.

Industry
Environmental test equipment · temperature-humidity chambers
System type
Device-side HMI: industrial PC / PAD + Android app + platform integration
Key technology
PLC point mapping · closed-loop PID · EEV expansion valves · program step engine · live curve rendering · 64-in / 32-out analogue · multilingual · one-click backup
Jiding scope
Requirements, prototype and UI design, three clients, platform and PLC integration, testing and training, upkeep
15modules on the panel: from device monitoring to DI/DO configuration
3clients: industrial PC, PAD (identical features) and an Android app
12PID parameter sets: heat, cool, humidify and dehumidify, each split by mode
64analogue inputs at the ceiling, 32 outputs — channel count set at initialisation

The Screen

System overview: a screen bolted to the chamber is the whole console

Operators do not walk over with a laptop; they stand at the machine and work on the panel. So the first constraint is not feature count but standing-room usability — a left rail hides 15 modules, a top bar carries language, date, user and lighting, and a floating ball in the corner holds the occasional jobs: screenshots, walkthroughs, videos and alarm logs.

Chamber HMI restored: left rail + top bar + floating ball, every action standing at the machine SYSTEM T-ENV 2026-11-19 13:05 EN Lamp Book Dim operator ▾ MODULES Monitor Curves Programs Operation Upkeep Initial setup Parameters PID setup EEV setup Logs CHAMBER TEMPERATURE 23.5 °C SP 25.0 dev −1.5 CHAMBER HUMIDITY 45.2 %RH SP 50.0 dev −4.8 LIVE CURVE · LAST 2 HOURS Compressor Heat Humidify Dehumidify Fan Link Mode: fixed setpoint · program 03 step 2 of 5 · 03:12:40 remaining Main rail 15 modules one screen Floating ball: screenshot, guide, video, alarm log, home Panel shown as illustration; mounting varies with the machine, and interface colours are de-identified.
The screen: rail + top bar + floating ball, with the two readings first and curves second

Why two big numbers come first

The question every chamber gets is "what is it at now". This is not a reporting tool, it has to be readable from a metre away through the door glass — so the landing view gives two cards: measured value large, setpoint small, deviation flagged in red. Curves and lamps sit below, second tier.

Why navigation splits three ways

The rail answers "where do I go", the top bar answers "who am I, what language, is the lamp on", the ball handles "something quick right now". Three layers keep any one menu from growing to twenty items; with gloves on, the ball beats digging through a tree.

Three Clients

Three clients: PAD mirrors the panel, the app covers what the panel cannot

The specification is blunt: "PAD features are identical to the industrial PC". That is not laziness — a supervisor walking up with a tablet must see exactly what the panel shows, or the two of them are not talking about the same machine. The app goes the other way: it drops high-risk configuration and adds a standby screen plus manual shortcuts.

Capability Panel PAD Android app
Sign-in and accounts✓✓✓
Device monitoring (run / state / faults)✓✓✓
Curves (current / history / list / export)✓✓✓
Logs (operations / alarms / door events)✓✓partial
Upkeep (parts / maintenance dates)✓✓✓
Program editing✓✓—
Operation settings (run / schedule / fixed)✓✓—
Initialisation / parameters / PID / EEV✓✓—
DI/DO configuration and debug mode✓✓—
Standby screen (climate at a glance)——✓
Header shortcuts (manuals / alarm highlight)——✓

▲ Per the specification: panel and PAD align exactly; the app keeps monitoring, curves, upkeep and logs, with configuration left on the machine.

Addedwhat only the app does

  • Standby screen: after a period without input it takes over, showing measured and setpoint climate plus a period curve — a walk-round needs no tapping
  • Header shortcuts: maintenance and operation manuals are re-fetched from the server on entry, so updates need no app release; alarms are highlighted

Removedwhy the app carries no parameters

One wrong PID or EEV value can scrap a whole batch inside the chamber. Leaving configuration on the machine keeps the "on site, facing the box" bar in place; the app is for watching and chasing, not tuning. That boundary was set in requirements, not cut later.

Monitoring & Curves

Monitoring and curves: measured hugging setpoint is the only proof of control

Monitoring splits into running state and status, with faults shown flat and as a list; curves split into energy and climate. The one thing users actually stare at is whether the measured line hugs the setpoint line — hug means the PID is right, drift means go check an actuator.

Curves: measured solid, setpoint dashed — overshoot, band and drift at a glance 100°C 40°C 0°C −40°C temp °C overshoot 4.2°C band ±0.5°C ****RH 50% 0% 0h 2h 4h 6h 8h Energy curve for the same window (historical power) Ramp-up and pull-down draw the most power, holding falls away — the energy curve is the evidence on whether these parameters are efficient Four curve abilities Current curve Drawn live from the API feed History curve Replayed by time range List view Partial rows, tap for detail Export PDF / Excel
Climate curves: measured solid against setpoint dashed, with overshoot and band marked on the chart
Running state Device status Faults flat view Fault list Fault date Description End time Energy curve Climate curve

▲ Faults come in two views: flat answers "how many are broken now", the list answers "when did it start and when did it clear".

Program Editor

Programs: one recipe, five steps, two loop levels

A program is the soul of a chamber. Customers are not buying "a box that gets cold"; they are buying "a box that runs this curve for eight hours and then three more times". So the editor has to express three things per step — where to go, how long to stay, and when the clock starts — then stack two levels of looping on top.

Program curve: one polyline is one recipe — steps, loops and signals all live on it +85C +25C -20C -40C S1 ramp S2 hold 4h S3 cool S4 hold 2h S5 return signal 1 · at temp signal 2 · step change loop whole ×3 0h 2h 4h 6h 8h Step editor Program 03 · cyclic damp heat S1 25 → 85C 1.5C/min · go at temp S2 85C / 60%RH 4h · wait: band ±0.5C S3 85 → -40C 1.0C/min · go at temp S4 -40C held 2h · wait: band ±1.0C S5 -40 → 25C 1.0C/min · stop after Step loop: S2 ⇆ S3 alone ×5 Values are illustrative; rates, tolerances and hold times come from the test standard and are typed per program. "Go at temp" versus "in-band timing": one starts on reaching the target, the other once climate settles inside the band.
Program curve: five steps, whole-loop ×3 and a step loop S2⇆S3; purple lines are time-signal outputs

Steps

Each step records target climate, ramp rate and hold time; steps can be added and edited, and the detail view lists every parameter of that step — changing a recipe means changing one step, not re-laying the program.

Loops

Two levels: program loop repeats the whole recipe, step loop repeats one segment. A damp-heat cycle that swings hot to cold fifty times is one loop count, not fifty copied rows.

Signals and waits

Time signals close a digital output at a given node to drive a recorder or a linked machine; the wait setting decides when the clock starts — on reaching temperature, or once inside the tolerance band. That single choice decides whether a test is compliant.

Why the wait setting deserves more care than the hold time: a standard says "hold four hours after the specimen reaches temperature", not "four hours after the step starts". If timing begins during the ramp, the specimen is under-tested — in-band timing excludes the ramp, and the report stands up.

PID & EEV

Control parameters: four actuators, four tempers

Temperature and humidity fight each other: cooling strips moisture out, humidifying puts heat in. So heat, cool, humidify and dehumidify each get their own PID set, and each set splits again into single-temperature mode and climate mode — controlling temperature alone should not have to humour the humidity loop. On the cooling side sits an EEV stage metering refrigerant.

Closed loop: setpoint, error, PID, four actuators, chamber, sensors, back to the sum Setpoint temp / RH Σ PID control P · I · D terms two mode sets Heat · elements Cool · compressor Humidify · boiler Dehumidify · reheat EEV stage main · hot / cold bypass Chamber air circulation · specimen area · window dry bulb / wet bulb · viewport · outlet Sensors · measured temp / RH / wet bulb Four PID sets, because no single setting tames heating elements, a compressor, a humidifier and reheat at once
Closed loop: error drives four PID branches, with an EEV stage on the cooling side
Branch Set one Set two Set three Why separate
Heat Heating PID, single temp Heating PID, temp + RH — Elements respond fast and overshoot; single-temp mode can take a firmer setting
Cool Cooling PID, single temp Cooling PID, temp + RH — Compressors have start delays and lag; settings stay soft to avoid short cycling
Humidify Non-linear PID Linear PID Anti-runaway PID Boiler and ultrasonic behave differently; anti-runaway caps single-shot output
Dehumidify Non-linear PID Linear PID Energy-saving PID Cooling and reheat must cooperate; the saving set trims reheat once target is met
EEV valves Main valve max/min steps in cool and climate modes Hot bypass: start-stop, EEV and solenoid parameters Cold bypass: start-stop, EEV and solenoid parameters Two compressors each carry an EVD set (Rst0–Rst3); step limits stop over-travel

▲ 12 PID and 11 EEV parameters, all editable, storable and traceable on the panel — tuning is a parameter change, not a code change.

I/O & Initialisation

I/O and initialisation: channels first, meaning second

Every sensor and actuator in a chamber ends up on one PLC point. Initialisation decides how many channels this machine has; parameter setup decides what each channel means — get either wrong and the numbers coming up are just digits.

Point matrix: channel count set at initialisation, meaning explained in parameter setup Analogue inputs · max 64 temp / RH / pressure / current Filled = enabled (14 shown); grey = reserved Analogue outputs · max 32 valve position / VFD / power Outputs pass through offset compensation before they go out Parameters tied to points Dry bulb 8 offsets + 8 references (from PLC) Rel. humidity RH with T1 / T2 / T3 references Outlet wet bulb temperature calibration Viewport heating power, anti-condensation EVD 2 compressors, Rst0–Rst3 Analogue input offsets read per point Three more initialisation duties Chamber limits · analogue input and output maximum / minimum Compressor and run-mode parameters · licence code · run-time reset One-click backup: parameters and data saved, restored after a swap Point counts are ceilings; how many are live depends on the sensors and actuators on this machine. Illustrative, point tags de-identified.
Point matrix: 64 inputs / 32 outputs enabled at initialisation, then interpreted by parameter setup
64analogue inputs at the ceiling; channel count is a field in initialisation
32analogue outputs, carrying valve position and power commands
8 + 8dry-bulb offsets and references, references read from the PLC
2compressors, each with an EVD set (Rst0–Rst3) and run-mode parameters

Why offsets and references are stored apart

A sensor at the outlet reads two degrees below the specimen area — normal. The reference is what this chamber ought to read; the offset is what we add to make it read that. Storing them separately means calibration only moves the offset, and later you can still answer "what standard was this set against".

Why one-click backup rates a button

Tuning a chamber can take days, and a backup is those days preserved. Swapping a controller, flashing firmware or suspecting a mis-edit, one click gets you back to a known state; before shipping, it freezes the tuned set so on-site installation just restores it.

Upkeep & Logs

Upkeep and logs: the screen tells you when to service it

A chamber runs for days at a time; compressors, heaters and humidifier boilers all have service lives. Upkeep records where this machine has got to; logs record what has happened to it — one looks forward, one looks back.

Forwardupkeep, three time scopes

  • Parts: file each component, log every service, set the next date with a reminder
  • Service log: component name, service time, notes and next due date in one list
  • Machine maintenance: whole-machine records, with the next date also reminded

The granularity is deliberate: parts answer "which component is due", the machine answers "this unit needs a day offline". Two lines running together means neither small parts nor the whole unit slips.

Backwardlogs, seven trails

  • Operation log: who did what and when, list plus detail
  • Alarm setup / types: set ranges and types, content per type
  • Alarm list / statistics: detail on click, charts for trends
  • Sign-in log: who logged in and when
  • Door events: when the door opened and for how long
  • Fire log: deferred this phase, the interface slot is reserved
Log type What it answers Presentation Typical use
Operation logwho changed a parameterlist + detailreplay what preceded a fault
Alarm listwhen which alarm firedlist + detailalign times with a complaint
Alarm statisticswhich fault recurspie / linefeed model improvements
Sign-in logwho was on the machinelistattribute on a shared unit
Door eventswas the door opened mid-runlist + detailjudge whether data was disturbed
Why door events are part of the test data: open a chamber mid-run and the climate collapses; the specimen stops seeing the specified conditions. Recording the timestamp is a footnote on the curve — the report can say "this dip was a door opening, not a control failure", and when a customer questions the data, that record is firmer than any explanation.

Standby Screen

Standby screen: when nobody is touching it, the screen reports

Walk a workshop floor and the question is always "what is this one at". The app switches to a standby page after a period without input, putting measured, setpoint and a period curve together so it reads from two metres — no tapping every machine on the round.

Standby screen: measured large on top, setpoints beneath, period curve underneath SYSTEM· T-ENV 13:05 CHAMBER TEMP 23.5 C CHAMBER RH 45.2 % SETPOINT TEMP 25.0 C SETPOINT RH 50.0 % LAST 4 HOURS · MEASURED VS SETPOINT RUNNING · PGM 03 · STEP 2/5 · 03:12:40 LEFT Enters after 3 minutes idle; a touch returns to the previous page Trigger and exit No input for a while → standby Touch the screen → back to the page Data keeps refreshing meanwhile Why in the app, not the panel The panel is on the machine A tablet can stand in the aisle One glance covers a row Four standby items Measured climate Large type, readable from afar Setpoint climate Beside measured, for deviation Measured period curve Trend tells you if it settled Setpoint period curve Overlaid, the gap is obvious
Standby: measured large, setpoints beside, period curve below — idle in, touch out

Platform Integration

Platform: terminals never touch the PLC directly

One line in the specification matters: "terminal operations go to the platform server first, then to the vendor API". That layer is not overhead — it lets three clients share one interface and keeps a PLC point change from rippling through every client.

Three tiers: clients only know the platform interface, which talks to PLC and vendor API Industrial PC panel on the chamber PAD identical features Android app standby screen, manuals future client same interface, no rewrite Platform server · one interface layer Vendor API integration Interface development, all clients Data distribution Database, multilingual Display data · read only climate, state, alarms, energy read from points PLC point → platform → clients Operation data · writable setpoints, start-stop, parameters written back every write lands in the operation log Vendor API joint debugging with their engineers Multilingual went into the schema from day one: the fields carry room for languages, so switching the UI never touches the tables.
Platform: clients → interface layer → PLC and vendor API, reads and writes split, writes logged

Why the layer exists

If three clients each talked to the PLC, "set a temperature" would be written three times, and a point change would mean three edits. With a layer between, the point map lives once and clients only know the interface; new models, new points, new third parties are server changes, not client releases.

Why reads and writes split

A wrong read shows a stale number; a wrong write can disturb a running test. Display data takes a read-only path, operation data gets its own writable path, and every write lands in the log — who moved the setpoint from 85 to 25 is answerable afterwards. That boundary is what separates industrial software from a reporting back office.

FAQ & Delivery

Four common questions

How is chamber HMI software different from a generic device back office?

Three ways. Position: the HMI is mounted on the machine and the operator stands at it, so buttons are large, hierarchy is shallow, and mis-taps are expensive — the floating ball and top bar both have to work with gloves on. Real time: climate, state and faults follow PLC points, and curves draw as they sample rather than refresh every few minutes. Authority: the panel not only reads, it writes — PID, EEV, compressor mode, fixed values and schedules — and a wrong write spoils the specimens inside, so every change needs confirmation and a record.

What do steps, loops, time signals and wait settings actually do?

A program is a test recipe: several steps in sequence, each with a target climate and hold time, added or edited individually. Loops come in two levels — a program loop repeats the whole recipe, a step loop repeats one segment, so an alternating test needs no manual re-entry. Time signals close a digital output at a node to drive external equipment or mark a record point. The wait setting decides when the clock starts: on reaching temperature, or once climate settles inside the tolerance band, so a specimen is not timed before it is at condition.

Why does each of heat, cool, humidify and dehumidify get its own PID?

Because the physics differ. Heating runs on elements — fast, prone to overshoot. Cooling runs on a compressor and expansion valve — lagging. Humidifying climbs slowly whether by boiler or ultrasonic. Dehumidifying needs cooling plus reheat and oscillates most easily. One setting across four branches will always fail one of them. So each branch keeps its own set, and each set splits into single-temperature and climate modes: controlling temperature alone need not humour the humidity coupling.

How do the three clients divide the work from the platform?

The industrial PC and PAD are identical — they are the machine's own operating surface, where on-site work happens. The Android app adds what the panel cannot: monitoring, curves, upkeep and logs, plus a standby screen that reports climate after a period idle, and header shortcuts for manuals and alarm highlighting. The platform is not a client at all: terminals call the platform server, and the server handles PLC point mapping and the vendor API, with data distribution and schema owned centrally. Multilingual was designed into the schema from the start.

MORE CASES

More Related Cases

Environmental test chamber HMI system
System Integration OMIntelligent manufacturing, intelligent inspection

Environmental test chamber HMI system

An HMI built into the chamber panel: the industrial PC and the PAD run identical features, and the A...

View Details →
Low-altitude logistics multimodal management system
System Integration OMLow-altitude logistics, fully automated distribution

Low-altitude logistics multimodal management system

A low-altitude logistics multimodal management system for campus and community scenarios: an on-site...

View Details →
Smart fire-safety platform for residential communities
System Integration OMSmart fire protection, community fire protection IoT

Smart fire-safety platform for residential communities

A fire-safety management platform for property managers and district fire supervision: admin console...

View Details →

View All Cases →

Planning a similar production line or enterprise system?

Start with our pricing logic, then let's talk requirements — cost structure, technology comparison and acceptance criteria, all laid out in the open.