Don't forget our early-access features: if you are interested in trying them, please reach out to LDARtools Support.
• Auto Tours - Automatically build tours on a recurrence schedule. (Beta).
• Dashboard - Redesigned operations dashboard with new compliance and performance widgets. (Beta).
✦ What’s New |
|---|
Chateau |
|---|
Resources
Noon and EOD drifts can now be added to a SpanBox daily calibration. A daily calibration that came from a SpanBox was locked completely, so recording a manual noon or end-of-day drift against it meant contacting LDARtools Support. The Daily Calibration tab stays locked, because that record still comes from the analyzer, but the Noon Drift and EOD Drift tabs are now open so a drift can be added by hand.
Drift readings now show their own source. The Daily Calibrations grid has new Drift 1 Source and Drift 2 Source columns, so a session that pairs a SpanBox daily calibration with a manually entered drift shows where each reading came from. |
GeneralNew users now open the main grids with a standard set of columns. A user opening Chateau for the first time was shown every available column on the Components, Open Leaks, All Leaks, Open DORs, Closed DORs, Inspections, OGI Inspections, Attempts, Current Tours, Schedule and Tour Details grids. Those grids now open with a standard set of columns and the rest hidden; every column is still available from each grid’s column menu. This applies only to users who have not saved a column layout of their own — an existing layout is left untouched. |
Chateau Mobile |
CalibrationsConfirmation entry is now one continuous workflow. Apply each cylinder’s gas, watch the live PPM settle and tap Capture, then mark that cylinder Pass or Fail — the entry advances to the next cylinder automatically, with a brief Undo to step back. Every cylinder is saved together as a single confirmation record.
The reading source is chosen once per session. Analyzer or Manual is picked on the setup screen and applies to every cylinder, so there is no per-cylinder source to confirm again. A single cylinder can still be switched to manual entry without changing the rest of the session or discarding a reading already captured.
Cylinders can be managed without leaving the flow. The cylinder list is pre-filled from the analyzer’s last confirmation and ordered by concentration, and cylinders can be added or removed as you go — either one already in the system or a brand-new one. Adding a new cylinder requires a certification date in the past and an expiration date in the future.
A third drift method, VVa §60.485a, joins Standard and VVa. It takes one reading per cylinder and checks it against both the confirmation and the cylinder.
Precision calibrations can now be recorded on the handheld. Precision Calibration is now its own option on the Calibrations menu, taking three timed readings per cylinder one test at a time, each response time recorded by the timer.
Calibration records can be reviewed and corrected on the handheld. The new View / edit records screen lists every calibration held on the device, grouped by day and filtered to Confirmations, Drifts or Precision. A record entered on that device can be reopened and corrected — including each individual drift — and one cylinder can be saved without stepping back through the others. Records synced from a SpanBox are locked. |
✦ Bug Fixes & Improvements |
Chateau |
Emissions
Fixed emission credits not applying to some components. Some component properties record a plain yes or no — whether a component is part of a Closed Vent System, for example — but a component could be created without that property ever being set, leaving it blank rather than "no." A credit configured to apply to components answering "no" only matched an actual "no," so a component left blank did not receive it, even though a blank effectively means the same thing. Every component now carries a definite yes or no, so those credits are applied as configured, and Net Reportable Emissions for the components concerned is lower than previously reported. |
Porches
Fixed the drill-down on Valve + Nonconnectors alerts listing the wrong inspections. The alert is raised on the combined total of valves and every other non-connector component type, but the drill-down looked at one component type at a time — so it listed only that type’s inspections, and where no single type reached the maximum on its own, none at all. It now lists every inspection that contributed.
Fixed the misleading label on Valve + Nonconnectors alerts. The alert read "Excess Valves Only per Hour," as though valves alone were counted. It now reads "Excess Valve + Nonconnectors per Hour," matching its pace setting under Settings, and the audit’s help text explains how connectors are identified.
Fixed component types being matched by Value alone on the Excess Inspections Audit. A site can use the same Value for both a component type and a sub-type, and the audit could score a component against whichever of the two it read. It now always uses the top-level type, the same way the other audits do. |
Components
Fixed activating a component out of a TUx profile giving it a new initialization date. A component that had been Active, was moved to a TUx profile and then set back to Active — through the TUx Log’s Activate Selected Components action or by approving a profile change — was given a fresh initialization date, and Chateau reads that date as the day the component entered service. The component was therefore scheduled as though it were new and given an initial monitoring requirement, which reported as a missed inspection once it came due; it now keeps its original date. |
Rules
Fixed the nightly rules run timing out. The final step of the nightly run had too little time to complete, and when it failed, the day’s inspection schedule was never rebuilt — leaving technicians with nothing new to check out against until it ran successfully. That step now runs to completion.
Fixed skipped components after a failed nightly run. A failed run caused the following run to start from the wrong point, silently skipping every component approved since the last successful run — those components were not scheduled for their next inspection, even though the run reported success. Only a completed run now moves that starting point forward. |
GeneralGeneral bug fixes and stability improvements. |
Chateau Mobile |
Sync
Fixed check-in failing when an analyzer was used only for water blank tests. Before each check-in the handheld trims out analyzers that are not attached to a component inspection. A water blank test is not a component inspection, so an analyzer used only for water blank work was trimmed out while the reading naming it was kept, and Chateau then rejected the whole check-in rather than that one reading — on every retry, including the automatic ones. Chateau now identifies the analyzer from the reading itself.
Fixed check-in failing over a slow connection. Chateau closed the connection whenever a technician’s upload speed dropped below a fixed floor. On a slow or broken-up connection it could also begin reading the uploaded file from the wrong point and report it as compressed in an unsupported format, although the file was intact. Chateau now keeps receiving for as long as the upload takes, and reads the file in full before opening it. |
GeneralFixed Chateau Mobile closing on launch on Android 9 and older. The app checks the Wi-Fi connection at start-up for the OGI camera, using a method that is not available on Android 9 and below, and closed as soon as Wi-Fi became available. Launching with Wi-Fi switched off only delayed it until the technician turned Wi-Fi on to sync. The check now uses a method those versions support. General bug fixes and stability improvements. |

Comments
0 comments
Please sign in to leave a comment.