Engineering Scope
The development of low-power battery thermostat is oriented to the usage requirement of "HVAC systems requiring temperature control panels without wiring", 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 temperature acquisition, display, buttons or knobs, control strategies, wireless commands and connection status prompts.
Power Supply and State Scheduling
Periodically measure the temperature and update the control status, refresh the interface during interaction, and confirm the instruction execution results.
Data and System Integration
Clear connections and data formats around temperature sensors, displays, buttons or knobs, and HVAC control interfaces, and define recording, transmission, confirmation, and abnormal status.
Prototypes, Testing and Deliverables
Form temperature control logic, display driver, wireless protocol and lost connection status tests, focusing on verifying screen refresh, interactive response, command confirmation and local behavior when disconnected.
System Architecture and Operation
Periodically measure the temperature and update the control status, refresh the interface during interaction, and confirm the instruction execution results.
- Interface composition: temperature sensor, display, buttons or knobs, HVAC control interface.
- 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 protection logic and power supply responsibilities of the thermostat and controlled equipment need to be clearly defined respectively.
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 | The HVAC system requires a temperature control panel without wiring; typical usage procedures, sampling and upload times, target battery life and response requirements are provided. |
| Product interface and structure | Temperature sensor, display, buttons or knobs, HVAC control interface; 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 | Temperature control logic, display driver, wireless protocol and disconnection state testing; the scope of hardware, source code and third-party components is clearly stated in the statement of work. |
| Functional verification | Periodically measure the temperature and update the control status, refresh the interface during interaction, and confirm the instruction execution results; record the input, output, and recovery results of each status. |
| Power consumption verification | Screen refresh, interactive response, command confirmation and local behavior when disconnected. 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.
MCU 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 EngineeringThread/Zigbee Sleepy End Device Development
Thread/Zigbee dormant terminal development service, develops dormant terminal polling, message reception, network drop detection and rejoining, and delivers node firmware, network configuration, gateway dependency and timing records. The scope of the project is determined based on the target equipment, existing data and acceptance conditions.
Explore the ScopeSpecialist EngineeringLow-Power Display and Actuator Control
Display and actuator low-power control development services, control refresh, backlight, motor or valve timing, handle execution failures and power surges, deliver driver code, circuit modifications, parameters and single-action energy records. The scope of the project is determined based on the target equipment, existing data and acceptance conditions.
Explore the ScopeSpecialist EngineeringManagement Platforms and Clients for Sleeping Devices
The dormant device management platform and client development services manage sleep status, command queue, expiration processing, power trends and execution acknowledgments, and deliver device models, server and client code, API and joint debugging records. 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 receive parameter adjustment when the thermostat is sleeping?+
The receiving window and effective time should be defined according to the link used, the client displays the pending and executed status, and verifies expired commands.
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 temperature sensor, display, buttons or knobs, and HVAC control interface, 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 temperature control logic, display driver, wireless protocol and disconnection state test; the prototype materials, structure, platform, external tests 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