Engineering Scope
The development of low-power pulse meter reading collector is oriented to the usage requirement of "the existing meter needs to be plugged in for collection without changing the original measurement core", and the 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 pulse input, debounce, low-power counting, magnification configuration, data storage and centralized reporting.
Power Supply and State Scheduling
Maintain necessary counting links, save cumulative values periodically, centrally upload and record confirmation status.
Data and System Integration
Clarify the connection and data format around pulse level, maximum frequency, counting magnification and input protection, and define recording, transmission, confirmation and abnormal status.
Prototypes, Testing and Deliverables
Form the counting circuit and firmware, magnification configuration, power-off storage scheme and pulse replay record, focusing on verifying the maximum input pulse frequency, missing counts during sleep, power-off storage and external interface leakage.
System Architecture and Operation
Maintain necessary counting links, save cumulative values periodically, centrally upload and record confirmation status.
- Interface composition: pulse level, maximum frequency, counting magnification and input protection.
- 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
External modifications need to be checked for compatibility with the original interface and the impact on the original equipment.
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 | Stock meters need to be plugged in for collection without changing the original measurement core; typical usage procedures, sampling and upload times, target battery life and response requirements are provided. |
| Product interface and structure | Pulse level, maximum frequency, counting magnification and input protection; 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 | Counting circuit and firmware, magnification configuration, power-down storage scheme and pulse playback record; the scope of hardware, source code and third-party components are clearly stated in the statement of work. |
| Functional verification | Maintain necessary counting links, save cumulative values periodically, centrally upload and record confirmation status; record the input, output and recovery results of each status. |
| Power consumption verification | Maximum input pulse frequency, leakage during sleep, power-off storage and external interface leakage. 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.
Low-Power MCU Selection and Board Adaptation
Low-power MCU selection and main board adaptation development services, checking the resources reserved in each power mode, adapting the driver and starting the target board, delivering selection comparison, board-level code, construction instructions and function records. The scope of the project is determined based on the target equipment, existing data and acceptance conditions.
Explore the ScopeSpecialist EngineeringLow-Leakage Hardware and PCB Development
Low-leakage hardware and PCB development services, checking static paths, protection devices, level translation and device quiescent current, delivering schematics, PCB source files, BOM, manufacturing files and node current 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 EngineeringFirmware Programming and Production Testing for Low-Power Products
Low-power product programming and production test development services, development of programming, identity writing, sleep check, dynamic current detection and traceability, delivery of tooling software, operating procedures, limit configuration and batch recording format. The scope of the project is determined based on the target equipment, existing data and acceptance conditions.
Explore the ScopeFrequently Asked Questions
How to prevent pulse leakage when the main controller is in sleep mode?+
Counting paths should be selected that can operate continuously in the target power mode and cover maximum frequency, jitter, and brownout scenario testing.
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 level, maximum frequency, counting magnification and input protection, and then determine the modification and regression testing scope.
How to determine the cost and period of this project?+
The evaluation is split based on the delivery items such as counting circuit and firmware, magnification configuration, power-down storage solution and pulse replay record; the prototype materials, structure, platform, external testing and new functions are listed separately, and the quotation and milestones are formed after the requirements and interfaces 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