Engineering Scope
The development of low-power smart water meter electronic modules is oriented to the use requirement of "dispersed water meters need to be automatically read and reduce manual meter reading". Collection, processing, communication and power supply are designed as one set of products. The project can start from new main board development, existing firmware modification or designated module integration. The development scope is confirmed based on the target function, existing foundation and delivery requirements.
Interfaces and Product Integration
Develop counting or readings, data freezing, scheduled reporting, abnormal events and battery status management according to the selected metering interface.
Power Supply and State Scheduling
Continuously retain counts, freeze data periodically, and read downstream tasks after waking up for communication.
Data and System Integration
Clear connections and data formats around the original metering core's pulse or digital interface, storage and optional valves define recording, transmission, confirmation and abnormal status.
Prototypes, Testing and Deliverables
Develop the metering interface firmware, meter reading snapshot format, valve control acknowledgment and reading test, focusing on verifying the continuous metering link energy consumption, reading integrity, reporting and valve action energy.
System Architecture and Operation
Continuously retain counts, freeze data periodically, and read downstream tasks after waking up for communication.
- Interface composition: pulse or digital interface of the original metering core, storage and optional valves.
- Work scheduling: Determine each status based on sampling, interaction and reception requirements, indicating which circuits continue to run.
- Exception handling: Define deadlines, bounded retries, and recovery behaviors for applicable communication, sensing, or execution tasks.
Design Conditions and Functional Limits
Module development and entire meter metering performance verification are agreed separately.
Define power targets together with functional requirements. Battery-life estimates must specify the battery, temperature, operating cycle, event frequency and network conditions. Keep estimates separate from continuous-operation test results.
Project Inputs
| Data category | Startup data |
|---|---|
| business work cycle | Distributed water meters need to read automatically to reduce manual meter reading; provide typical usage procedures, sampling and upload times, target battery life and response requirements. |
| Product interface and structure | Pulse or digital interface, storage and optional valves of the original metering core; for existing products, provide schematics, a bill of materials (BOM), firmware and prototypes. |
| Batteries and site conditions | Provide battery model, power supply range, cut-off voltage, temperature, installation method and communication conditions. |
| Delivery and Responsibility | Clarify the scope of source code and design files, platform docking, number of prototypes, test conditions and third-party work. |
Delivery and Acceptance
| Delivery project | Verification method |
|---|---|
| Design and implementation | Measurement interface program, frozen record format, valve control acknowledgment and reading test; the scope of hardware, source code and third-party components are specified in the statement of work. |
| Functional verification | Continuously retain counts, freeze data periodically, and read downstream tasks after waking up for communication; record the input, output, and recovery results of each state. |
| Power consumption verification | Continuously measures link energy consumption, reading integrity, reporting and valve action energy. Fix the battery side measurement point to record the energy from the full task cycle until the device returns to sleep. |
| Exceptions and retesting | Covers applicable situations such as low battery, continuous triggering, loss of connection or restart, and retains original logs, waveforms and versions. |
Specialist Engineering Services
Select the required modules based on the existing product. Interfaces and responsibilities are defined in the project scope.
Power Domain and Peripheral Power-Gating Development
Multi-power domain and peripheral power-off control development services, split power domains, design switches, signal isolation and recovery timing, and deliver power trees, timing diagrams, switching circuits, drive and shutdown test records. The scope of the project is determined based on the target equipment, existing data and acceptance conditions.
Explore the ScopeSpecialist EngineeringMCU Sleep and Wake-Up Firmware Development
MCU Sleep wake-up firmware development service, develops sleep entry conditions, wake-up determination, clock recovery and driver reconstruction, and delivers state machine, firmware, wake-up timing and function regression records. The scope of the project is determined based on the target equipment, existing data and acceptance conditions.
Explore the ScopeSpecialist EngineeringLow-Power State Machine and Fault Recovery Development
Low-power state machine and exception recovery development services, design failure exit, bounded retry, persistence and restart recovery, delivery of state diagrams, code, configuration and fault injection records. The scope of the project is determined based on the target equipment, existing data and acceptance conditions.
Explore the ScopeSpecialist EngineeringNB-IoT/LTE-M Power Saving Mode Integration
NB-IoT/LTE-M power saving mode adaptation service, requesting and checking power saving parameters, linking sampling reporting and downlink windows, processing mode is unavailable, delivering module configuration, state machine, network log and corresponding current waveform. The scope of the project is determined based on the target equipment, existing data and acceptance conditions.
Explore the ScopeSpecialist EngineeringSystem Power, Battery Life and Environmental Validation
Complete machine power consumption, battery life and environmental verification services, measuring state current, event energy, peak voltage drop and long-term business operation, delivering original waveforms, logs, calculation sheets, test reports and coverage. The scope of the project is determined based on the target equipment, existing data and acceptance conditions.
Explore the ScopeFrequently Asked Questions
Will meter reading communication failure affect the cumulative reading?+
The measurement and communication tasks should be separated during design, and unconfirmed readings and time information should be saved; the cumulative amount and supplementary transmission results should be checked separately after network disconnection, power failure, and recovery.
Is it possible to develop only part of an existing product?+
Module development or power consumption optimization can be carried out according to the existing interface and modifiable range. For this product, you first need to check the pulse or digital interface, storage and optional valves of the original measurement core, and then determine the scope of changes and return.
How to determine the cost and period of this project?+
The evaluation is split based on the delivery items such as measurement interface program, frozen record format, valve control acknowledgment and reading test; the prototype material, structure, platform, external testing and new functions are listed separately, and the quotation and milestones are formed after the requirements and interface are confirmed.
Engineering References
The configuration of GPIO should be checked together with the external circuit, sleep mode and wake-up status; the actual parameters are subject to the target chip data and the whole board test. GPIO and power state design reference
Online
Phone
WeChat
Top