top of page

LHT65N Battery Reads 52 V? Separate Status Bits from Millivolts

Nov 13
3 min read

An LHT65N battery value near 52 V is a reason to inspect the decoder before arranging a battery replacement. In the ordinary BAT-field format documented by Dragino, the two-byte word carries status flags as well as a voltage. Converting the entire word to volts includes those flags in the measurement. The correction belongs in the interpretation of the message, after confirming that the packet actually uses that format.


Illustrative separation of wireless sensor battery status flags and the numeric voltage field.
Original illustrative concept; not an exact product drawing or customer installation.

Key takeaway — Confirm the payload layout before masking status bits from the ordinary battery word. Decode voltage and status separately; some message layouts have no voltage field.



1. Establish which message you received


Start with the model label, installed firmware, application port, external-sensor mode and a saved raw payload. Preserve the received bytes before changing a decoder or dashboard expression. A field called “battery” in an application is only a label; it does not establish what the underlying bytes mean.


Dragino’s LHT65N/S manual assigns bits 15–14 of the ordinary BAT word to battery status and bits 13–0 to the millivolt value. Its timestamp payload layouts instead provide battery status without the voltage field. Select the matching layout first; do not apply the ordinary BAT formula to every LHT65N message.


White Dragino LHT65N temperature and humidity sensor housing with model label and blue connector cover
LHT65N housing - product photograph from ProSense Instruments’ external-probe listing. It does not show an installed application or establish the device’s firmware or radio variant.


Worked BAT-word example: mask 0xCBA4 with 0x3FFF to obtain 2980 millivolts, while retaining status 3 separately.
Original technical diagram. Apply only to the documented ordinary BAT-word layout.

2. Separate the flag from the measurement


For a confirmed ordinary BAT word, use a bit mask to retain the lower fourteen bits: voltage_mV = BAT_word & 0x3FFF. Divide that result by 1,000 for volts. Extract the two-bit status separately: status_code = (BAT_word >> 14) & 0x03. Keep both outputs clearly named rather than replacing one with the other.


As a worked decoding example, take 0xCBA4. Reading the entire unsigned word gives 52,132; dividing by 1,000 produces the misleading 52.132 V. Masking gives 0x0BA4, or 2,980 mV: 2.980 V. The upper two bits are binary 11. This arithmetic example follows the manufacturer’s documented word; it is not a field measurement or a battery-life test.


3. Find the point where the value changed


Trace one saved packet through the receiving system. Compare the raw bytes, decoder output, stored field and displayed value. Record the name and unit at each stage. If the decoder already outputs volts, a second conversion downstream will introduce another error. If it outputs millivolts, the display needs an explicit, documented conversion.


Do not repair the screen by dividing every battery result by an arbitrary factor until it looks believable. That approach can hide a wrong byte offset, a different message format or a duplicate transformation. Check several saved packets from the same confirmed layout, then include other supported layouts in the acceptance set.


4. Use an isolated acceptance checklist


Before releasing a change, keep the previous decoder and mapping configuration so the team can restore the known state. Work with sanitised message samples; device security keys are unnecessary for this calculation and should not appear in a support screenshot.


  • Confirm the sample belongs to the exact model, firmware and message layout being tested.

  • Compare the calculated millivolts and separate status code with the documented fields.

  • Check the application stores the agreed numeric unit, without a second scale conversion.

  • Test a message that lacks battery voltage: the application should retain that distinction rather than manufacture a zero-volt reading.

  • Check trend labels, exports and any maintenance rule using the field, then record the decoder revision and test evidence.


5. Keep decoding evidence separate from maintenance decisions


A correctly decoded voltage resolves a data-interpretation question. It does not establish remaining service life, prove the sensing installation is healthy or validate every downstream alarm. Avoid inventing a percentage from one voltage reading. Use the exact device’s maintenance documentation and the application’s service requirements when deciding what action follows.


If raw bytes, firmware identification and the manual cannot be reconciled, leave the proposed decoder change out of operational service and seek clarification. Send ProSense the exact model, firmware, port, external-sensor configuration and a sanitised payload, together with the expected units and the current output. That evidence helps distinguish a message-layout fault from a dashboard mapping fault without changing the physical sensor unnecessarily.



Need help with your application?


ProSense Instruments - explore instruments, sensors, data loggers and test equipment.


ProSense Solutions - discuss complete monitoring and automation systems.


ProSight Software - explore cloud dashboards, alarms and reporting. Device integration must be confirmed for your application.



Project enquiries: sales@prosense.com.au. Software enquiries: info@prosightsoftware.com.

Comments


bottom of page