How to zero and align a SICK DustHunter T100: the field procedure
A hands-on field procedure for technicians and CEMS operators running a SICK DustHunter T100 double-pass transmissometer — the optical dust monitor we install on biomass boilers. It covers the routine zero and alignment performed in SICK’s SOPAS ET software: what to measure first, how to centre the optics, how to set the reference, and how to confirm the result before you sign off.
Zeroing is the check that keeps an optical dust monitor honest. A transmissometer doesn’t measure milligrams — it measures light, and every mg/m³ it reports to DOE is derived from how much of its beam survives the trip across your stack. If the instrument no longer knows what a clean path looks like — because the optics have drifted, or the sender and reflector are no longer aligned — then every reading downstream is off by that error. Zeroing re-establishes the 100 % transmission reference; alignment makes sure the beam is actually landing where it should before you set it. Done together, on a smoke-free path, they are the practical core of the QAL3 drift check every operator owns.
Do this on a smoke- and dust-free path only. Zeroing sets the instrument’s reference for a perfectly clean beam. If there is dust or smoke in the path while you zero, that contamination is baked into the reference and every later reading is biased. Perform it during a genuine shutdown with clean air in the duct, or on SICK’s normalisation set-up (adjustment mounts or a waste-gas-free tube). Follow your site’s confined-space, isolation and purge-air procedures throughout.
The zero-and-align procedure at a glance
● Six stages. Only stage 5 writes the new reference — everything before it exists to make that reference correct, and everything after it protects the record.
Before you start
Gather these before you open SOPAS — a zero attempted with a missing value or a fouled path is a zero you’ll be redoing:
- SOPAS ET installed on your laptop, with the correct device driver versions for both the MCU (control unit) and the DHT T100 sensor, plus the connection cable.
- Authorized operator login for SOPAS. The password is SICK’s standard operator-level password, documented in the official SICK DustHunter manual — we don’t reproduce it on this public page; use the value from your device documentation.
- The two path measurements from Stage 1 (flange-to-flange and the optical measuring distance).
- From your latest stack sampling report: the actual dust concentration (mg/m³), and the corresponding extinction value read from the MCU. These are the application inputs the instrument needs to relate light to mass.
- A confirmed smoke- and dust-free path — shutdown clean air, or SICK adjustment mounts / a waste-gas-free tube.
- Certified filter glasses if you are also performing a span check (optional to a routine zero, but good practice).
Stage 1 — Measure the geometry
Extinction accumulates along the beam, so the path length is a calibration parameter: the same dust load gives a different reading on a wider duct. Measure it before anything else.
- Flange-to-flange = stack (duct) diameter + the flange length from the flange face to the sender/receiver reference point (A) + the flange length to the reflector point (F, taken at the middle of the rubber seal). In short: the distance A → F.
- Optical measuring distance = the chimney opening the beam actually crosses (the “CD” value).
Write both down. They go into the application parameters in Stage 3, and a wrong path length quietly biases every reading the system will ever report.
Stage 2 — Connect, log in, and enter maintenance
- Open SOPAS ET and load the matching driver versions for the MCU and the DHT T100. Connect to both.
- Log in on each as Authorized operator.
- Work on the MCU first. Under the Maintenance folder, tick the box to activate maintenance mode, and wait until the orange maintenance indicator appears — this signals the instrument has stopped reporting live data to DOE and is safe to adjust.
- Save the current parameters before you change anything. Under Protocol, save the existing (“default”) parameter set for the MCU. This is your rollback point.
- Now repeat for the DHT T100: log in, tick maintenance, wait for the orange indicator, and save its current parameters under Protocol too.
Always capturing the “before” state first means a mistake costs you a reload, not a site revisit.
Stage 3 — Set the parameters
With both units in maintenance:
- Confirm the selected variant matches the sensor actually installed, and enter the mounting location so the record is unambiguous.
- Under Overview Screen Setting, set Bar 1 & 2, the Value, and the Range Low & High to the values your site requires.
- Under Application Parameters, enter the path length from Stage 1, then the two calibration inputs from your stack sampling report: the actual dust (mg/m³) and the extinction value from the MCU. This is what lets the instrument translate its optical signal into a reportable concentration.
Stage 4 — Align the optics
Before you set any reference, the beam has to be landing where it should. The optical axes of the sender/receiver and the reflector must coincide, so the returning spot sits dead centre on the alignment target. A zero set on a misaligned beam is a zero set on the wrong amount of light.
Stage 5 — Zero the instrument
Now set the reference, on the confirmed smoke- and dust-free path.
- Under Transmission, choose Set reference.
- Follow the SOPAS steps to run the zeroing. The instrument measures the light across the clean path and sets that transmission as 100 % — the anchor every future reading is measured against.
- Re-check the alignment (Stage 4) is still centred before you confirm — this is your last chance to catch a nudged mount.
Stage 6 — Verify and save
- Check the MCU display. Because you zeroed on a clean path, dust and opacity should read at or near their floor and then track the live process once it’s running. A zero that leaves a stubborn offset is a sign the path wasn’t clean or the alignment slipped — investigate before signing off.
- Under Protocol, save the new parameter set for both the MCU and the DHT T100. Unsaved, the whole job is lost on the next power cycle.
- Close the record. Complete your service/QAL3 form, capture the before/after parameters, and get the signature and stamp your site requires. An unrecorded zero is, for compliance purposes, a zero that didn’t happen.
The zero-and-align routine on one page
Where this fits in compliance
A zero and alignment is drift control, not calibration. It re-establishes the optical reference and confirms the geometry — but it does not re-derive the mg/m³ scale. That scale comes from the QAL2 calibration function, built against gravimetric stack sampling, and only a fresh QAL2 or the Annual Surveillance Test can change it. Zeroing keeps that calibration valid between those campaigns.
How often? The rule follows the instrument’s certificate: zero-and-span checks must happen at least every QAL1 maintenance interval — three months for the DustHunter T100 — but DOE recommends every four weeks, and expects shorter intervals on high, dirty dust loads where the optics foul faster. If you’re plotting these on a QAL3 control chart and the zero keeps wandering, that’s the chart doing its job — telling you to look at purge air, mounting or fouling before it becomes an exceedance.
If you’d rather have this done for you — or want your technicians trained on it on your own stack — talk to us. Keeping optical dust monitors reading true between QAL2 campaigns is core to what we do.
This is a general field guide for the SICK DustHunter T100 as we install and service it, condensed from our internal procedure. It doesn't replace the manufacturer's operating instructions or your site's safety procedures — always work to the current SICK manual and your own permit-to-work.
← All insights