Custom LoRaWAN Pulse Counter Manufacturer for Smart Meter Retrofit

2026-09-04 22:59:14 · Views 22

Replacing every mechanical water, gas or electricity meter with a completely new smart meter can be expensive and disruptive. Many installed meters are still mechanically reliable and already provide a pulse, reed-switch, open-collector or dry-contact output that represents consumption.

A custom LoRaWAN pulse counter can connect these existing meters to a long-range wireless network. It records incoming pulses, converts them into usable consumption data and sends the results to a remote management platform.

This approach allows system integrators, utilities, property managers and industrial operators to modernize existing metering infrastructure without immediately replacing every meter.

For companies planning an OEM product, selecting a custom LoRaWAN pulse counter manufacturer requires more than comparing enclosure size and battery capacity. The project must account for input compatibility, pulse accuracy, local data retention, communication recovery, LoRaWAN regional settings, platform integration and the physical conditions of the installation site.

What Is a LoRaWAN Pulse Counter?

A LoRaWAN pulse counter is a wireless IoT terminal that counts electrical or mechanical pulses generated by a meter, switch or industrial machine.

The basic system architecture is:

Meter or Sensor → Pulse Counter → LoRaWAN Gateway → Network Server → Application Platform

Each input pulse represents a predefined quantity. Examples include:

One liter of water
Ten liters of water
One cubic meter of gas
One watt-hour or kilowatt-hour
One machine cycle
One pump start
One product passing a sensor
One opening or closing event

The relationship between pulses and the measured quantity is determined by the connected meter. The pulse counter records the number of events and applies the configured pulse coefficient before sending the resulting consumption or event data to the platform.

Which Existing Devices Can Be Connected?

A custom wireless pulse counter may be developed for many types of field equipment.

Water Meters

Mechanical or electronic water meters may provide a reed-switch, dry-contact, open-collector or dedicated pulse output.

A LoRaWAN module can collect these pulses and transmit water-consumption records to a central platform. This can support:

Residential submetering
Commercial buildings
Industrial water management
Agricultural irrigation
Apartment complexes
Schools and campuses
Remote pumping stations
Municipal water projects

The meter documentation must be checked before connection because pulse voltage, output type and pulse value vary between models.

Gas Meters

Some gas meters provide a low-frequency pulse output for remote reading. A compatible LoRaWAN counter can collect the pulses without requiring an individual cellular connection for every meter.

Gas-related installations may be subject to additional electrical, enclosure and safety requirements. The installation environment must therefore be clearly defined before hardware development.

Electricity and Energy Meters

Many electricity meters, heat meters and energy analyzers provide pulse outputs proportional to consumption.

A wireless pulse reader can be used for:

Tenant energy allocation
Factory energy monitoring
Building energy analysis
Solar generation monitoring
Equipment-level power measurement
Sustainability reporting

For electricity-meter installations, input isolation and protection requirements should be evaluated according to the meter interface and wiring environment.

Flow Meters

Pulse-output flow meters are commonly used in industrial water, irrigation, chemical processing and production systems.

A LoRaWAN pulse counter can transmit totalized flow values and interval consumption. The platform can then identify unusual usage, compare different production areas or generate alarms based on predefined rules.

Industrial Machines

A pulse counter is not limited to utility meters. It can also count:

Machine operating cycles
Production quantities
Conveyor events
Pump starts
Door operations
Switch transitions
Equipment runtime pulses
Rain-gauge tipping events

This makes the same core hardware useful for industrial monitoring, preventive maintenance and production-data collection.

Why Use LoRaWAN for Meter Retrofit?

Retain Existing Meters

A retrofit pulse counter adds wireless communication to compatible meters that are already installed and working.

This can reduce the need to interrupt water, gas or energy services during a digitalization project. It may also allow a customer to modernize selected sites in phases.

Compatibility must still be verified meter by meter. A pulse counter cannot automatically read every mechanical dial unless the meter provides a suitable output or an additional sensing adapter is developed.

Long-Range Communication

LoRaWAN is designed for small data packets transmitted over relatively long distances with low power consumption.

One or more gateways can collect data from counters distributed across buildings, industrial sites, farms or utility networks. Actual coverage depends on:

Building materials
Meter location
Underground installation
Antenna position
Gateway height
Radio interference
Regional frequency limits
LoRaWAN data rate
Payload and reporting frequency

Meters installed in metal cabinets, basements or underground pits require particular attention during site testing.

No SIM Card in Every Counter

The counter communicates with a LoRaWAN gateway rather than connecting directly to a mobile network.

The gateway uses Ethernet, Wi-Fi or cellular backhaul to forward data to the server. This architecture can simplify connectivity management when a project contains hundreds or thousands of field devices.

For network planning, review Jinshengchang’s industrial LoRaWAN gateway selection guide.

Battery-Powered Operation

Pulse counting usually requires relatively little energy, but actual service life depends on the complete operating profile.

Important factors include:

Input circuit design
Pulse frequency
Reporting interval
LoRaWAN spreading factor
Confirmed-message retries
Downlink activity
Local display or indicator use
Temperature
Signal strength
Battery chemistry
Data-storage frequency
Alarm frequency

An OEM supplier should calculate the power budget from the required operating conditions instead of providing an unsupported battery-life promise.

Critical Pulse Input Requirements

Input compatibility is one of the most important parts of a custom project.

Dry Contact and Reed Switch

A dry-contact input detects whether two electrical contacts are open or closed. Reed switches are frequently used in mechanical meters and magnetic sensing systems.

The firmware and input circuit may need configurable debounce filtering to prevent one physical event from being counted multiple times.

Open-Collector Input

An open-collector output requires an appropriate pull-up circuit and compatible voltage levels.

Before development, the customer should provide the meter’s interface documentation, including maximum voltage, pulse width, output current and wiring diagram.

Active Voltage Pulse

Some meters generate an active voltage pulse. The input circuit may require voltage scaling, isolation, polarity protection or surge protection.

Connecting an unknown active signal directly to a low-voltage MCU input can damage the device or produce unreliable counts.

Pulse Width and Frequency

The manufacturer needs to know:

Minimum pulse width
Maximum pulse frequency
Active-high or active-low logic
Minimum interval between pulses
Contact bounce characteristics
Maximum accumulated count
Required number of channels

A device designed for slow water-meter pulses may not be suitable for a high-frequency industrial counter without hardware and firmware changes.

Preventing Counting Errors

A useful pulse counter must continue recording data accurately even when wireless communication is temporarily unavailable.

Input Filtering

Electrical noise, contact bounce and interference can generate false pulses. Hardware filtering and firmware debounce rules can reject signals that do not meet the configured duration.

The filter must not be so aggressive that legitimate short pulses are lost.

Non-Volatile Count Storage

The accumulated counter value should not disappear after a battery change, reset or unexpected power interruption.

A robust design can periodically save the count to non-volatile memory. However, excessive memory writing can reduce flash endurance, so the saving strategy must balance data protection and memory life.

Rollover Handling

The firmware should define what happens when the internal counter reaches its maximum value. The payload decoder and platform database must use compatible rollover logic.

Duplicate and Missing Packet Management

LoRaWAN frame counters, message timestamps and device sequence numbers can help the server detect repeated or missing transmissions.

The business system should distinguish between:

A duplicated radio packet
A retransmitted historical record
A new meter pulse
A device restart
A manually reset counter

Without clear logic, consumption reports may contain gaps or duplicate values.

Local Data Logging and Recovery

Wireless networks may be temporarily interrupted by gateway maintenance, interference, internet failure or equipment relocation.

A custom LoRaWAN meter-reading module can store interval records locally and upload them after communication is restored.

The project should define:

Number of records to store
Recording interval
Timestamp source
Storage behavior when memory is full
Historical-data upload sequence
Duplicate-record prevention
Gateway-loss detection
Rejoin strategy
Maximum recovery traffic

Sending a large backlog immediately may overload the network. Recovery uploads should normally be distributed over time and coordinated with normal reporting.

Recommended LoRaWAN Payload Data

A practical payload may contain:

Device ID
Input-channel number
Accumulated pulse count
Interval pulse count
Converted consumption value
Pulse coefficient
Input state
Alarm flags
Battery voltage
Signal or diagnostic information
Record sequence number
Timestamp or time offset
Firmware version
Tamper status

Payload design should remain compact. LoRaWAN is not intended for unnecessarily large or highly repetitive messages.

The server decoder must also define byte order, field length, scale, signed values, alarm bits and firmware compatibility.

Useful Alarm Functions

Depending on the connected meter and application, the pulse counter can support several alarm types.

Abnormal Consumption

The platform can generate an alert when interval consumption exceeds a configured threshold.

This may help identify:

Water leakage
Unusual night consumption
Unexpected gas usage
Excessive irrigation
Production anomalies

The device or platform should avoid treating a single unusual pulse as a confirmed leak without appropriate persistence rules.

No-Flow Alarm

If a pump or valve is expected to operate but the pulse counter records no flow, the system may detect an empty pipe, blocked line, failed meter or equipment malfunction.

This function normally requires integration with pump, valve or operating-state data.

Reverse or Dual-Direction Flow

Some meters provide separate forward and reverse pulse outputs. Supporting these signals requires defined input channels and platform calculation rules.

Tamper Detection

An enclosure switch, magnetic sensor or cable-monitoring circuit may be used to detect opening, removal or disconnection.

The exact tamper mechanism should be designed for the meter and installation method rather than treated as a universal function.

Low-Battery and Offline Alerts

The platform should display battery status and last communication time. An offline alarm must allow for the normal reporting interval and possible network delays.

Hardware Options for an OEM Pulse Counter

A custom product may include:

One or multiple pulse inputs
Dry-contact input
Reed-switch input
Open-collector compatibility
Active-voltage pulse interface
Input isolation
Local flash memory
Replaceable or fixed battery
External DC power
Status LED
Magnetic activation switch
NFC or Bluetooth configuration
Tamper input
External antenna or internal antenna
Indoor or outdoor enclosure
Wall, pipe or meter mounting
Customized cable and connector
Printed customer logo and serial number

Not every project needs every feature. Adding unnecessary interfaces increases component cost, enclosure size, firmware complexity and power consumption.

Firmware Configuration

The embedded software can provide configurable settings such as:

Pulse coefficient
Measurement unit
Reporting interval
Input debounce time
Minimum accepted pulse width
Alarm threshold
Historical storage interval
LoRaWAN activation mode
Regional frequency settings
Confirmed or unconfirmed uplinks
Adaptive Data Rate
Rejoin behavior
Battery warning level
Channel enable or disable
Counter reset authorization

Jinshengchang’s custom LoRaWAN firmware development service covers sensor interfaces, low-power control, LoRaWAN communication, remote parameters and factory-test functions.

Integration With Valves and Irrigation Systems

Pulse data becomes more useful when it is connected with control equipment.

For example, an irrigation system may compare expected water volume with actual flow. If a valve is open but no pulses are received, the system can report a possible water-supply or meter problem. If consumption exceeds the expected quantity, the platform can identify a possible leak or damaged pipe.

The pulse counter may therefore operate alongside a LoRaWAN smart water valve as part of a larger water-management system.

Automatic valve shutdown should only be implemented after evaluating operational safety, sensor reliability and manual override requirements.

Platform and API Requirements

A meter-management platform should provide more than a current counter value.

Useful platform functions include:

Device and meter registration
Meter-to-customer association
Consumption history
Hourly, daily and monthly reports
Multi-site dashboards
Abnormal-consumption alarms
Battery and offline status
Data export
API access
User permissions
Billing-system integration
Device configuration records
Maintenance logs

For OEM projects, the customer should decide whether the data will be sent to the lora8 platform, a customer-owned server or a third-party LoRaWAN application.

Regional Frequency and Compliance Planning

The counter and gateway must use the frequency plan permitted in the destination market.

Common LoRaWAN regional plans include:

EU868
US915
AU915
AS923
IN865
CN470
KR920
RU864

The exact channel configuration, transmit power and duty-cycle behavior must be configured for the target country.

Product compliance requirements depend on the market, enclosure, battery, radio configuration and intended application. Certification should be planned and verified for the final production design.

OEM Development Process

1. Meter Interface Analysis

Collect datasheets, wiring diagrams, pulse values, voltage levels, connector information and sample meters.

2. Product Requirement Definition

Confirm the number of channels, battery target, reporting interval, enclosure, installation environment and server interface.

3. Hardware and Firmware Design

Develop the input protection, MCU, LoRaWAN radio, antenna, memory, power supply and embedded software.

4. Prototype Testing

Test pulse accuracy, debounce rules, power consumption, data storage, radio performance and platform decoding.

5. Meter Compatibility Test

Connect the prototype to representative water, gas, electricity or flow meters under normal and abnormal conditions.

6. Pilot Deployment

Install a limited number of devices at the actual project site to evaluate radio coverage, pulse reliability and installation procedures.

7. Design Verification

Complete long-duration counting, reset recovery, gateway-loss, battery, temperature and enclosure testing according to the agreed requirements.

8. Production Preparation

Finalize factory programming, device credentials, test fixtures, labels, packaging and traceability procedures.

Information Required for a Quotation

Send the following information to receive a useful OEM evaluation:

Meter brand and model
Meter output type
Pulse voltage and pulse width
Pulse value or coefficient
Number of input channels
Expected pulse frequency
Reporting interval
Local storage requirement
Indoor, outdoor or underground installation
Power or battery preference
Destination country
LoRaWAN Network Server
Platform or API requirements
Expected prototype quantity
Estimated production quantity
Branding and enclosure requirements

A meter datasheet and wiring diagram are particularly valuable. Without them, input compatibility cannot be confirmed reliably.

Frequently Asked Questions

Can a LoRaWAN pulse counter work with any water meter?

No. The meter must provide a compatible pulse output, or a suitable external sensing adapter must be developed. The output type and pulse coefficient must be confirmed from the meter documentation.

Can the device keep counting when the gateway is offline?

It can be designed to continue counting and store records locally. The required storage duration and recovery-upload method must be defined during development.

Can one device read several meters?

A multi-channel design can monitor more than one compatible meter, but the number of inputs, cable distances, pulse frequencies and installation layout must be evaluated.

Can the counter detect water leaks?

It provides consumption data that can support leak-detection rules. Reliable leak detection generally requires time-based analysis, thresholds and knowledge of normal usage patterns.

Does every pulse need to be transmitted immediately?

Usually not. The device can count pulses locally and send accumulated or interval values according to a configured schedule. Critical alarms may be transmitted separately.

Can the pulse coefficient be changed remotely?

Remote configuration can be developed, but sensitive parameters should use authentication and controlled permissions to prevent incorrect consumption calculations.

Is LoRaWAN suitable for meters installed underground?

LoRaWAN can provide useful penetration, but underground pits, metal covers and wet environments can significantly reduce signal strength. An on-site coverage test is necessary.

Can the product use the customer’s logo and platform?

OEM branding, labels, payload protocols and platform integration can be evaluated according to the project requirements.

Conclusion

A LoRaWAN pulse counter offers a practical way to connect compatible legacy meters and industrial pulse-output equipment to a modern IoT platform.

The success of the project depends on much more than wireless range. Accurate pulse detection, input protection, data retention, recovery logic, battery design, gateway coverage and platform calculations must all be designed as one system.

Shenzhen Jinshengchang Technology Co., Ltd. can evaluate custom LoRaWAN pulse-counter projects covering hardware, firmware, enclosure, gateway communication, API integration, prototype development and OEM production.

Request a Custom LoRaWAN Pulse Counter Proposal

Send your meter datasheet, pulse-output specification, installation environment, required quantity and platform requirements for technical evaluation.

Shenzhen Jinshengchang Technology Co., Ltd.

WhatsApp: +86 134 8088 1974
Phone: +86 134 8088 1974
Phone: +86 177 2242 0256
Email: 397017470@qq.com