PCBA PARTNER
EN
English中文Deutsch日本語Français

COLDGUARD · CG-WIFI-A01

Commercial freezer monitoring

Retrofit temperature, door and power monitoring for freezers, chilled cabinets and small cold rooms. Two probes, local alarms, battery-backed recording and Wi-Fi replay connect on-site events with remote oversight.

ColdGuard enclosure exterior
2 × DS18B20
Independent temperature channels
2.4 GHz
Wi-Fi · HTTPS telemetry
5 V + 1S
Adapter & backup power path
270 × 220 × 78
mm · enclosure main body

Applications

Retail display & chest freezers

Place an air probe in the storage zone and a second probe in a thermally buffered reference. Track cabinet temperature, prolonged door opening and supply loss during sales and restocking. Keep the display probe away from the evaporator outlet and heated door frame.

Restaurant & catering equipment

Retrofitting prep refrigerators, upright freezers and ingredient storage cabinets gives kitchen staff local audible alerts and operators a history by device. Chilled ingredients and locked stock require different high/low limits, recovery hysteresis and opening delays.

Small cold rooms

Use T1/T2 for two representative positions, such as a warm return-air zone and a shelf away from the cooling unit. A two-probe device provides local observations; larger rooms need additional devices and a temperature-mapping plan for spatial coverage.

Equipment service & chain stores

Assign a device identity to each asset, compare alarm history and separate store connectivity from cabinet failures. A service team can use repeated probe, door, clock or storage faults to plan maintenance and document corrective action.

Defrost and loading workflows

Air temperature reacts rapidly when a door opens or defrost starts. A buffered reference responds more slowly. Compare both histories with planned operating windows, and choose delay settings long enough for the normal cycle while preserving alarms for persistent excursions.

Power interruptions

Sense the low-voltage output of the monitored adapter before the battery-backed power path. The battery supports the monitor after supply loss. Immediate remote delivery also requires the Wi-Fi router and upstream connection to remain powered; otherwise events are recorded locally for later upload.

Two probes, one cabinet story

Independent 1-Wire channels

Two powered DS18B20 probes use separate data lines on GPIO4 and GPIO5, each with a pull-up to 3.3 V. The digital interface carries a unique ROM identity and CRC-protected readings. Independent channels simplify probe identification and prevent one shared-bus fault from masking the other channel.

Air vs buffered reference

T1 can follow cabinet air; T2 can follow a suitable buffered reference or a second cabinet location. A reference container needs compatible food-area materials, tracked fill and secure placement. Its reading is a proxy for thermal response, not a direct measurement of the food core.

Range, accuracy and calibration

The DS18B20 chip specifies −55 to +125°C measurement range and ±0.5°C accuracy from −10 to +85°C. Colder freezer operation needs calibration and an error budget for the complete probe assembly. Apply separate T1/T2 offsets from a traceable comparison at the intended operating points.

Local alarm logic

Delay, hysteresis and recovery

Temperature limits use continuous-duration gates and 1°C recovery hysteresis to reduce repeated switching around a threshold. Invalid probe readings create probe-fault alarms rather than ordinary temperature excursions. Alarm raise and recovery edges are captured immediately, alongside periodic telemetry.

Audible alert and mute

The active buzzer is driven through a transistor; a green LED communicates local operation. The push button temporarily mutes audible output without clearing the underlying alarm or stopping data capture. Mute behavior belongs to the local device, so connectivity is not needed for on-site handling.

Profiles for each use

The firmware example uses frozen-storage limits. A chilled cabinet requires a different compiled alarm profile; high/low limits and timing are defined in the alarm-core source. An operator should not assume that the example locked profile suits a chilled product or a regulated storage specification.

Frozen-storage firmware profile

EventRaise conditionDelay / recovery
High temperature · each probe> −12°C180 s; clear at ≤ −13°C
Low temperature · each probe< −25°C180 s; clear at ≥ −24°C
Probe faultInvalid / missing reading15 s; valid reading restores
Door openContact indicates open60 s; closing clears
Power lossAdapter sense absent3 s; supply restoration clears
Low battery< 3.4 V30 s; clear at ≥ 3.5 V
Storage / clock faultHealth flag falseImmediate health reporting

Hardware & interfaces

Controller and modular connections

ESP32-S3-DevKitC-1-N8R8 provides the controller, 8 MB flash, 8 MB PSRAM and 2.4 GHz Wi-Fi. DS3231 maintains a local time base; a 3.3 V microSD interface stores pending records. Digital inputs cover door position and adapter supply; ADC measures battery voltage with a divider and calibration coefficient.

Firmware task separation

Local sensing and alarm evaluation are separated from SD who owns the files and HTTP upload. Only the storage task accesses SD. Bounded queues and explicit storage/clock faults make a stalled network or write failure visible without relying on an unbounded retry in the sensing loop.

Retrofit electrical scope

The monitor observes temperature, door and power events; it does not switch the refrigeration compressor. Bring only SELV low-voltage wiring into the enclosure. Door input uses a passive contact with debounce; route signal cables separately from compressor and defrost power wiring.

FunctionGPIOInterface
T1 / T24 / 51-Wire · 3.3 V
Door contact / supply sense6 / 7Digital input · low-voltage only
Buzzer / status LED / mute8 / 9 / 10Transistor drive / LED / push button
Battery divider1ADC
DS323117 / 18I²C · SDA / SCL
microSD11 / 12 / 13 / 14SPI · CS / MOSI / CLK / MISO

PCBA images & schematics

The system combines controller and power modules, a dedicated charge-control PCB, and front-panel daughterboards. The KiCad PCBA assembly view below shows charge control A04, followed by PCB routing views for the indicator and buzzer daughterboards. Schematics cover charge permission and system module wiring.

ColdGuard charge-pcba PCBA assembly view
Charge-control PCBA · A04 CAD assembly view. Reference, comparators, logic, supply monitoring and CE control. J1: RAW 5V / GND / CE; J2: battery NTC; J3: inhibit; J4: arm. · Open full-size image

Zoomable circuit drawings

Same-name net labels connect circuit nodes. References, values and terminal names map to the BOM and assembly tables. Open either preview as a vector PDF to inspect pins and net names. The base system harness drawing shows module interconnections; module internal circuits are outside its scope. Use it together with charge-control A04 and the A05 wiring delta table.

Charge-control schematic A04 · temperature window, supply conditions and CE permission
Charge-control schematic A04 · temperature window, supply conditions and CE permission
System wiring schematic v0.8 · ESP32-S3, dual probes, door contact, RTC, microSD and backup power
System wiring schematic v0.8 · ESP32-S3, dual probes, door contact, RTC, microSD and backup power

A05 wiring delta table ↓

Power path & charge control

Adapter, power path and boost

A 5 V adapter feeds the BQ24074 power-path charger. Its OUT rail feeds the MiniBoost stage, nominally 5.2 V, then a resettable fuse and disconnect switch before the controller 5 V input. A protected 1S 2,000 mAh lithium cell connects to the battery input. Nominal charge current is set to 0.5 A.

Temperature-gated charging

The optional charge-control circuit uses two Semitec 103AT-2 NTCs on the battery surface, analog comparators, hysteresis and a power-on supervisor. Its permit chain controls charger CE and is separate from the firmware. Nominal thermal switching points are about 10.2°C and 34.8°C; component tolerance, NTC attachment and thermal gradients belong in the final trip-point calculation.

Voltage telemetry and autonomy sizing

Battery voltage is reported in volts; it is not a state-of-charge percentage. Estimate runtime from usable cell energy and measured average load: runtime ≈ usable Wh × conversion efficiency / average W. Include Wi-Fi retries, buzzer duty, SD writes, temperature and the low-voltage cutoff; capacity alone does not define a guaranteed backup duration.

ModuleSelected deviceRole
MCUEspressif ESP32-S3-DevKitC-1-N8R8Control, sensing and Wi-Fi
Probes2 × Adafruit 381 / DS18B20Powered waterproof probe assembly
Door contactAdafruit 375Passive magnetic contact
RTCAdafruit 3013 / DS3231Timestamp & backup coin cell
microSDSparkFun BOB-005443.3 V SPI storage
ChargerAdafruit 4755 / BQ24074Power path and charging
BoostAdafruit 4654 / MiniBoostNominal 5.2 V output
CellAdafruit 2011 · 1S 2000 mAhProtected cell; verify connector polarity
Thermal sensing2 × Semitec 103AT-2Separate charge permit inputs

Offline records & Wi-Fi upload

Capture, persist, acknowledge

Periodic telemetry is captured every 10 seconds; alarm edges are captured between periodic samples. Each record carries device ID, boot counter and sequence number. SD records use CRC and temporary-file rename; grouped storage holds up to 16,384 pending records. At a purely periodic 10-second rate this is about 45.5 hours; alarm edges also consume queue entries.

Ordered replay and duplicate protection

Upload the oldest pending record first. The server treats the device/boot/sequence tuple as an idempotency key and returns an acknowledgement before the device retires a record. A lost acknowledgement therefore leads to a safe retry. The dashboard separates capture time, server receive time and connectivity freshness.

Clock and storage health

DS3231 provides timestamps when a valid clock is available, with NTP synchronization after connectivity returns. When a timestamp is unavailable, retain boot/sequence/uptime and mark clock health explicitly. Storage faults and lost-record counters are telemetry fields, so gaps remain visible.

Transport and device identity

Use HTTPS ingest with an explicit trusted root CA and a per-device token. Empty CA configuration disables HTTPS upload; plain HTTP is restricted to an explicitly enabled lab mode. Provision each device with its own Wi-Fi credentials and identity, and keep real tokens outside downloadable examples.

  1. Sense & alarm
  2. Persist on SD
  3. Send via HTTPS
  4. Idempotent ingest
  5. Retire after ACK
  6. History & notify

Record fields

GroupFieldsMeaning
Identitydevice_id / boot / seqDevice identity and replay ordering
Timecaptured_at / uptime_msCapture time and local elapsed time
Measurementst1 / t2 / battery_vTwo temperatures and battery volts
Statedoor_open / mainsDoor and adapter availability
Healthstorage_ok / clock_ok / lost_log_recordsStorage, time and visible record loss
Eventsalarms / changesActive alarms, raise and recovery edges

Monitoring software & remote notification

Device fleet and history

A Python/SQLite service stores telemetry and alarm edges, with device registration, latest readings, offline state and per-device history. Operators can inspect both temperatures, door/mains state, battery volts and storage/clock health. Use the history to distinguish a transient opening from a persistent excursion.

Notification outbox

Alarm notification is decoupled from ingest through an outbox and worker. Configure an approved email or HTTPS webhook channel, credentials and recipients at deployment. Retries, delivery errors and duplicates are handled independently from receiving device telemetry; remote delivery is checked through provider receipts.

Service deployment and maintenance

The application listens on loopback by default. Put an authenticated TLS reverse proxy in front of operator access, retain device-token protection on ingest and separate demo data from operational records. Back up SQLite consistently, document restore steps and review device freshness and notification failures during maintenance.

Enclosure structure & installation

Case and mounting dimensions

The main case is 270 × 220 × 78 mm with a warm-white lid and graphite base. A removable carrier, battery tray and aluminium backplate support servicing. Allow 90 mm total depth for the case, rear mounting and front-button seal space; bottom glands project another 22 mm before cable bends. Mount the electronics outside the refrigerated space in a dry location.

Cable glands and complete jackets

Four bottom ports serve T1, T2, door contact and 5 V. LAPP SKINTOP STR-M 53111300 M12 × 1.5 glands accommodate 2–5 mm cable diameters and pair with 53119100 nuts. A Ø22 mm inner spotface leaves a 2 ± 0.1 mm local wall target for the 8 mm thread and 5 mm nut. Each gland clamps one intact round jacket; select probe-jacket diameter accordingly. Use LiYY 0028302 for the room-side door extension and 0028402 for a 5 V extension no longer than 1 m.

Removable front accessories

A Kingbright WP710A10GD green LED sits on a 26 × 14 × 1.6 mm daughterboard with 2.6 mm POM spacers and DIN 7991 M3 × 16 screws. The PUI AI-1223-TWT-3V-2-R buzzer sits on a 34 × 30 × 1.6 mm board with 8.7 mm spacers and M3 × 20 screws. Its 7.5 mm nominal body height gives a 1.2 mm nominal sound-face gap behind the lid. Four Ø3.4 mm mount holes use Ø6.2 mm, 90° countersinks, 1.4 mm deep; screw heads must sit flush. These are drawing targets, including the tolerance stack in the assembly manual.

Electrical drive and service harness

The LED daughterboard receives LED_A from GPIO9 through the existing R12 1 kΩ resistor and GND. The buzzer receives 3V3 and BUZZ_LOW from the existing Q1 collector, retaining the transistor and protection circuit. Daughterboards use two-layer 1.6 mm FR4 and 1 oz copper; KiCad sources, Gerbers and separate plated/non-plated drill files are supplied. Insulate each exposed lead individually and leave service slack so opening the lid does not pull solder joints.

Button, backplate and access

The APEM ISP3SAD200 mute button uses a double-flat Ø13.6 mm cutout with 12.9 mm flat width in the 3 mm lid. A 3 mm 5052-H32 aluminium backplate uses 6 mm rear spacers and recessed DIN 7991 M4 × 20 fasteners. Use suitable brackets and mounting surfaces, avoiding blind drilling into refrigeration cabinets. The 234 × 184 mm carrier separates controller, power, clock and storage; the battery envelope is 68 × 44 × 16 mm.

Radio, acoustic and cleaning conditions

Keep the controller antenna toward the enclosure edge and the recommended 15 mm RF region clear of metal and wiring. Check the installed signal path near metal cabinets. The open buzzer outlet and LED opening suit dry external installation; gland component ratings do not establish a whole-device ingress rating. Sites exposed to spray or condensation need a sealed acoustic/indicator arrangement, compatible materials and a cleaning-specific enclosure design.

Installation workflow

Survey and place sensors

Identify the storage range, usual opening duration, defrost cycle and Wi-Fi coverage. Place both probes consistently, mount the door magnet within its specified switching distance and label each cable. Keep cable exits from compromising the door seal; use existing service routes or approved feedthroughs.

Wire and provision

Follow the endpoint list for signal, power and common ground. Check battery connector polarity before connecting. During USB flashing disconnect the external 5 V and battery power path. Provision 2.4 GHz Wi-Fi, root CA, device ID/token and calibration offsets, then choose the application alarm profile.

Exercise events and retain records

Check both probes against a reference, opening/closing state, audible mute, supply loss and restoration. Interrupt Wi-Fi to observe local recording, restore it and compare sequence continuity in the server. Use the supplied UART recording tools to save timestamps, identity and status for installation handover.

Procurement and service connectors

One purchasing entry

The consolidated A05 table contains 130 unique items and two-unit totals including spares. The 32 populated charge-control positions use exact manufacturer part numbers. Use the grouped MPN table for buying and the per-position BOM for assembly; do not add both quantities or historical BOMs together.

Precision divider and capacitors

R14/R15/R16 are YAGEO RT0805BRD07100KL / RT0805BRD07499RL / RT0805BRD0710KL: 100 kΩ / 499 Ω / 10 kΩ, 0.1%, 25 ppm/°C. C1–C3/C4 are KEMET C0805C104K5RACTU / C0805C102K5RACTU: 100 nF / 1 nF, X7R, 10%, 50 V. Preserve precision, temperature coefficient and package when reviewing substitutes.

Connectors and service envelope

Harwin M20-9990345 / M20-9990245 headers pair with M20-1060300 / M20-1060200 housings and M20-1180042 contacts. Mark pin 1 because the housings are unkeyed. Reserve the modeled wire-service region to Z47 mm. The upper header-pin tolerance exceeds the housing range by 0.05 mm; check actual engagement and retention rather than forcing full seating.

Crimp and charge-permit interfaces

Use the Harwin Z20-320 tooling or qualified crimp service for the low-current 26 AWG branches. Manufacturer targets include 0.9–1.6 mm insulation diameter, 3–4 mm strip, 0.72 ± 0.03 mm conductor crimp height and 18 N specimen pull retention. J4 is unpopulated by default; retain the permanent R20 and independent TH1/TH2. Power cables follow their separate current requirements.

Enclosure CAD and manufacturing route

Finished parts and molded stocks

Use part-selection.csv for the five finished primary parts and molded-selection.csv for the three molded stocks. The A05 assembly STEP combines the lid, base, carrier, battery tray and backplate. The lid locating-lip inner root uses R0.4 while preserving the external mating profile. CAD is in final-part dimensions; material-specific shrink compensation belongs in the reviewed tooling design.

Mount positions and clearances

The battery tray uses a +2.5 mm X placement; carrier tray holes are X118.5/206.5, Y112/134, Ø3.4 mm. Tray M3×12 and charge-board M3×20 screws enter from beneath the carrier. The closest nominal screw-to-board lateral clearance is 1 mm; physical assembly targets at least 0.3 mm. Keep the RF, battery and opening-service regions clear.

Draft and secondary machining

The structure uses drafted walls and distinct molded/finished models. The four cable-gland axes tilt 2° from +Y toward +Z; the local seat target is 2.0 ± 0.1 mm wall thickness measured normal to the sloped wall. Front-board holes are Ø3.4 with Ø6.2, 90°, 1.4 mm-deep countersinks. XY visible-face profiles and the XZ root section are separate drawings, all in millimetres.

Material, tooling and inspection inputs

PC/ABS Bayblend FR3010 HI is a material candidate, with warm-white and graphite color direction. Tooling inputs cover resin/color, shrink, parting and steel responsibility, gate flow, cooling/warpage, ejection/venting, thin-lip filling and secondary-operation fixtures. Keep dimensional, fitting and T0/T1 records in the supplied matrices. Component ratings do not establish whole-device ingress or fire ratings.

HTTPS deployment and maintenance

Separated administration and ingestion

The source backend uses Python and SQLite. The private-LAN Caddy gateway accepts only POST /api/ingest, with an 8192-byte request limit and explicit upstream Host. Monitor, export and maintenance remain on loopback or an approved SSH management path. The public website supplies code and instructions, while each installation runs its own private service.

Per-device authentication and TLS

Each device has an independent 256-bit random token bound to its ID; the database retains token hashes. Firmware embeds the selected CA certificate, validates the server identity and requires reliable device time. Keep filled Wi-Fi/device configuration, private keys and operating backups outside public resources. Rotate or revoke credentials explicitly when devices are replaced.

Persistent operation and restart

The bench supervisor checks ports and private-directory responsibility before startup, retains keys/database/CA on restart, and stops backend and gateway together. Missing keys or conflicting state require explicit recovery. The source includes registration, backup/restore and audit commands; use a separate software-fixture database for synthetic tests.

Remote notifications and site continuity

The notification worker is explicitly enabled for an authorized receiver, with retries, leases, ordering and durable deduplication requirements. HTTPS receipt is distinct from receiver delivery. Site-wide outages require router and upstream backup for immediate remote delivery; otherwise local alarms and SD records continue, with replay after networking returns.

Technical downloads

PCBA images & schematics

The complete bundle includes integration A05, system v0.8, exact-MPN charge control, assembly CAD, front PCBs, wiring, molding handover, serial commissioning and HTTPS backend source. Use the consolidated A05 procurement table; historical tables are for traceability, not additive quantities. Engineering notes are primarily Chinese, with shared component, interface and code identifiers.

Complete resources

Electronics and purchasing

Wiring and assembly

CAD and interface drawings

Manufacturing and review

Firmware, software and tools

Application questions

Can the unit control the compressor?

This architecture monitors the cabinet and records events. Compressor control requires a separate controller and a specified switching/protection circuit.

Can it serve chilled and frozen storage?

The sensor interface serves both ranges; the alarm profile, probe assembly, placement and calibration must match each storage specification. The displayed example is a frozen-storage profile.

Will alerts arrive during a site-wide outage?

The monitor battery supports local operation. Remote delivery also needs a powered router and upstream network. With no network, records stay in the SD queue and replay after reconnection.

How does it scale to multiple stores?

Register independent device identities and tokens, deploy enough measurement points and group assets operationally by store. Size server retention, backup frequency and notification routing for the device count.

Discuss a cold-storage project

Share the cabinet type, storage temperature range, probe positions, door behavior, defrost cycle, Wi-Fi conditions, backup needs and fleet size. These inputs define the electronics, harness, enclosure, firmware profile and monitoring service.

Discuss a cold-storage project ↗

Technical references