Engineering Scope
The development of low-power liquid level telemetry terminals is oriented to the usage requirement of "pipe networks and rivers need to periodically collect liquid levels, and increase the frequency when abnormality occurs". 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
Adapt selected liquid level probes and develop hierarchical sampling, over-limit reporting, data caching and remote parameter configuration.
Power Supply and State Scheduling
Wake up the measurement regularly, increase the sampling or reporting frequency during abnormal stages, and return to the inspection mode after recovery.
Data and System Integration
Clarify the connection and data format around the digital or analog interface of the liquid level probe, probe power supply and installation range, and define recording, transmission, confirmation and abnormal status.
Prototypes, Testing and Deliverables
Form joint debugging records of probe drivers, alarm rules, cache programs and liquid level changes, focusing on verifying the probe operating current, abnormal duration, and communication retries in underground or blocked locations.
System Architecture and Operation
Wake up the measurement regularly, increase the sampling or reporting frequency during abnormal stages, and return to the inspection mode after recovery.
- Interface composition: liquid level probe digital or analog interface, probe power supply and installation range.
- 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
The power supply budgets of the probe and communication module need to be measured 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 | Pipe networks and rivers need to periodically collect liquid levels, and increase the frequency when abnormalities occur; provide typical usage procedures, sampling and upload times, target battery life, and response requirements. |
| Product interface and structure | Liquid level probe digital or analog interface, probe power supply and installation range; 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 | Probe drivers, alarm rules, cache programs and joint debugging records of liquid level changes; the scope of hardware, source code and third-party components are clearly stated in the statement of work. |
| Functional verification | Wake up the measurement regularly, increase the sampling or reporting frequency during the abnormal stage, and return to the inspection mode after recovery; record the input, output and recovery results of each state. |
| Power consumption verification | Probe operating current, abnormal duration, communication retries in underground or obscured locations. 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 EngineeringLow-Power Sensor Acquisition Driver Development
Sensor low-power acquisition driver development service, develop single measurement, FIFO, interrupt and power supply control, retain the necessary stabilization time, and deliver driver source code, parameter description, sampling record and exception handling. 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
How to avoid continuous power consumption when the signal at underground points is poor?+
Record the search and sending time, set the deadline for a single task and hierarchical backoff; save the data after reaching the limit and try again at the agreed time.
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 digital or analog interface of the liquid level probe, the power supply of the probe and the installation range, 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 deliverables such as probe driver, alarm rules, cache program and liquid level change joint debugging record; the prototype material, 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 power saving mode needs to check the network grant and the actual entry state, and the network search and retry under weak coverage should be measured separately. Cellular Power Consumption Analysis Reference
Online
Phone
WeChat
Top