top of page

Acrel CT-Powered Temperature Sensors: Verify Freshness During Low Load

2 days ago
4 min read

A switchgear temperature tile still shows a reasonable value while the circuit is lightly loaded. Is that a current measurement, or the last value received before updates stopped? With a CT-powered wireless sensor, electrical loading belongs in the monitoring-availability review as well as the thermal investigation.


The practical answer is to check the exact sensor’s power requirement, retain the last-update time and verify how the receiving system marks missing data. A plausible temperature must not silently become evidence of a healthy connection when its age is unknown.


Start with the ATE400’s documented power condition


Acrel’s ATE-series product information identifies the ATE400 as CT-powered, with a starting-current requirement of at least 5 A. The same table lists 15-second sampling and transmission intervals for that model. Those are model-specific specifications; they are not a guarantee that a dashboard will always receive a new reading every 15 seconds.


The ProSense Instruments catalogue identifies the pictured CT-powered sensor as PS-ATE400. Its power arrangement is different from battery-powered ATE models. Before ordering, confirm the exact sensor, receiver, regional radio variant and application suitability with ProSense; do not infer Australian approval or receiver compatibility from a generic ATE family photograph.


Acrel ATE400 CT-powered temperature sensors in green, yellow and red housings with metal fixing bands
Acrel ATE400 CT-powered wireless temperature sensors in the ProSense Instruments catalogue photograph (SKU PS-ATE400). These are product photographs, not a customer switchgear installation.

A starting specification is not a complete dropout model


The published starting-current value does not, by itself, specify an exact shutdown threshold, hold-up time or recovery delay after every load change. Do not turn it into a claim that all devices stop at precisely 4.99 A or resume immediately at 5.00 A. Obtain model-specific guidance and verify behaviour under the application’s approved test conditions.


Consider minimum operating load, standby, shutdown and restart separately from normal production load. A circuit that carries ample current during a busy shift may have a very different overnight duty. That creates an application question: is fresh temperature information required during those low-load periods, and what evidence shows it will remain available?


Do not assume that a missing update proves insufficient sensor power either. Radio delivery, receiver operation, configuration and the application’s own polling or display behaviour can also interrupt the visible record. Correlate the evidence before attributing a fault.


Keep temperature, freshness and load evidence separate


For each monitoring point, retain the sensor identity, last accepted temperature, last-update timestamp, receiver or application health indications and an authorised source of circuit-load information where available. State what each timestamp means: a receiver receipt time should not be presented as the original measurement time unless that relationship is established.


Agree an application-specific stale-data rule with the responsible engineering team. A receiving application should distinguish a current normal value, a current high value and an unavailable or stale point. This is a design requirement to verify, not a claim that every Acrel receiver or software package provides these states automatically.


When a reading becomes stale, preserve it as historical evidence and make its age clear. Do not replace it with zero degrees, continually refresh its displayed timestamp, or allow an old low reading to clear a current investigation. A flat trace should remain distinguishable from a sequence of newly received identical measurements.


An acceptance test that does not require live access


  1. Write down the operating states to be covered: normal load, low load, stopped equipment and restart. Define the required monitoring availability in each state before choosing a sensor power arrangement.

  2. Have competent personnel plan any hardware testing using a suitable controlled test arrangement and the current manufacturer instructions. Do not open energised switchgear, change protection or create an artificial production load to follow this article.

  3. Use authorised historical records, a suitable bench arrangement or isolated application test data to compare load-state changes with received updates. Record gaps and recovery timing without inventing a universal timeout.

  4. Test the receiving application independently by withholding new test records. Confirm the agreed stale indication, retained last-update time and treatment of any existing high-temperature event.

  5. Document which observations demonstrate sensor operation, which demonstrate radio delivery and which demonstrate application behaviour. Repeat the affected acceptance checks after configuration changes.


Worked example: a reassuring value with no recent evidence


In a hypothetical review, a point last reported 42 °C at 17:00. By 17:20 the circuit is in a low-load operating state and the application still displays 42 °C, but no subsequent sensor update is recorded. These are illustrative values, not alarm limits or a field test.


The defensible interpretation is “last received 42 °C at 17:00; current temperature unverified”. Check the load history alongside receiver and communications evidence. If the application continues to label the point healthy, correct and retest its freshness handling. Do not declare that the connection cooled, that the sensor failed, or that low load was the cause without supporting evidence.


Choose the next action from the coverage requirement


If fresh measurements are required when the monitored circuit cannot provide the documented starting conditions, ask for a power arrangement and monitoring design suited to that duty. Changing the temperature alarm limit cannot resolve a gap in measurement availability.


Keep electrical design, installation and validation with appropriately qualified people. SafeWork SA’s electrical-work guidance addresses licensed workers, risk assessment and de-energised work. Apply the current requirements for the installation’s jurisdiction. Wireless temperature trending is not, by itself, a certified electrical protection or safety function.


Need help with your application?


ProSense Instruments - discuss the exact sensor, receiver and low-load monitoring requirements: sales@prosenseinstruments.com.au or 1800 560 854.


ProSense Solutions - discuss complete monitoring and automation requirements: sales@prosense.com.au. ProSight Software - discuss software requirements: info@prosightsoftware.com. Device integration must be confirmed for your application.


Comments


bottom of page