Records, not alarms
QA systems should store the decoded Celsius value with the timestamp. Air temperature in a cold room is a different measurement; this probe is for product core or soft matrices as specified on the datasheet.
Confirm food-contact material and wash-down limits on the datasheet before first use. Cleaning steps stay in the site SOP.
Commissioning checklist
Join with OTAA, paste the PS-610 codec, and confirm temperature_c matches a reference thermometer in a controlled bath or known product matrix. Record probe lot, food-contact confirmation, wash-down SOP reference, and DevEUI in the QA commissioning pack.
Store decoded Celsius with timestamps in the system your HACCP plan already uses. Set report intervals to balance audit density against battery life. Flag probe_ok failures as maintenance, not as temperature excursions.
Limits and related kits
This decoder supplies product-core temperature. It does not certify compliance, replace statutory controls, or measure cold-room air — use ambient kits or the cold-room pattern when air is the target. Cleaning chemistry and food-contact limits stay on the datasheet and site SOP.
Pair with facility leak kits around wash-down areas if condensate trays matter. Process and food-chain design lives on the food-chain solution page; order from the PS-610 product page.
Integration notes
Export temperature_c with ISO timestamps into the same store auditors already pull. Keep probe_ok visible beside the chart so a failed tip is not mistaken for a perfect cold hold. Clone the PS-610 profile across identical needles; never paste soil or ambient codecs.
For RFQs, cite the food-grade needle measurement, wash-down limits, and this field map. Destination documentation stays a quote line. Pair wash-down floors with leak kits when condensate trays sit under the same process line.
Named fields
| Field | Type | Notes |
|---|---|---|
| temperature_c | number | Product temperature in degrees Celsius |
| probe_ok | boolean | Probe-health flag from the kit |
| battery_mv | integer | Battery millivolts |
| fcnt | integer | Frame counter |
Example after decode
{
"temperature_c": 4.2,
"probe_ok": true,
"battery_mv": 3100,
"fcnt": 55
}Byte offsets live in the decoder file shipped with the kit. If the first uplink disagrees with this example, trust the shipment file and the factory functional-test record.
Related pages
FAQ
Does this decoder certify HACCP compliance?
No. It supplies a timestamped Celsius value your plan can store. Limits and corrective actions stay with the site.
Battery life at the scheduled interval?
Up to about two years at the datasheet interval. Faster spot checks shorten that window.
Where is the cold-room design page?
The cold-room solution page describes the monitoring pattern. Order the probe from the product page.
Can I reuse a soil decoder on PS-610?
No. Moisture and EC fields are not temperature. Use the PS-610 profile only.
What temperature range does the decoder assume?
Use the probe range on the datasheet. Out-of-range tips should raise probe_ok or saturate per the kit firmware — treat that as maintenance.
Can I log PS-610 into a BMS?
Yes after decode. Map temperature_c and timestamp into the points your QA or BMS already uses for HACCP exports.