Engineering Scope
GNSS Intermittent positioning and motion wake-up were developed to solve specific engineering problems in low-power projects. The work starts from the customer's existing design and business requirements, arranges positioning startup, auxiliary information, timeout and mobile wake-up, handles invalid positions; delivers positioning scheduling code, status messages and environment classification test records according to the agreed modules.
Check input with baseline
Check the GNSS module, antenna, movement status, location update requirements and environment, and clarify the measurement and modification scope.
Implementation and adaptation
Arrange positioning startup, auxiliary information, timeout and mobile wake-up, handle invalid positions, record solution choices and dependency conditions.
Target environment joint debugging
Check the success rate, first positioning time, error and single positioning energy respectively to confirm the business behavior after parameter changes.
Document and record delivery
Provide positioning scheduling code, status messages and environment classification test records, explaining the version, construction or usage method.
Project Workflow
- Enter confirmation: GNSS module, antenna, mobility status, location update requirements and environment.
- Implementation method: Arrange positioning startup, auxiliary information, timeout and mobile wake-up, and handle no valid position.
- Stage review: Check the success rate, first positioning time, error and single positioning energy respectively.
- Project delivery: positioning scheduling code, status messages and environment classification test records.
Design Conditions and Functional Limits
It is necessary to consider the next positioning startup conditions and allowable delay, evaluate the cost of retaining the state and complete power outage, and then set static and mobile work strategies.
Special services take the agreed module as the implementation boundary. When hardware modifications, third-party agreements, overall platforms or external tests are involved, the interfaces, workload and responsibilities are confirmed separately, and local modifications are not directly used as conclusions on the performance of the complete device.
Project Inputs
- GNSS Module, antenna, mobility status, location update requirements and environment.
- Existing prototypes and reproducible problems, or new project functionality and power consumption targets.
- Modified design, source code and third-party dependencies are allowed; functionality and compatibility need to be maintained.
- Delivery list, target environment, sample scope, project milestones and acceptance methods.
Delivery and Acceptance
| Delivery content | Check method |
|---|---|
| Positioning scheduling code, status messages and environment classification test records | Check the editability, version, usage instructions and dependencies by file list. |
| Implementation verification | Check the success rate, first positioning time, error and single positioning energy respectively, and retain the corresponding working conditions and results. |
| Comparison of functions and power consumption | Fixed applicable hardware, software, battery, temperature and business cycles, accounting for changes in conditions and their impact. |
| Reproduction and follow-up maintenance | Provide build or run steps, known limitations, parameter ranges, and uncovered cases. |
Frequently Asked Questions
Is it appropriate to completely close GNSS after coming to rest?+
It is necessary to consider the next positioning startup conditions and allowable delay, evaluate the cost of retaining the state and complete power outage, and then set static and mobile work strategies.
What information do I need to prepare before starting the project?+
This work focuses on the GNSS module, antenna, mobile status, location update requirements and environment. When the data is incomplete, first determine the scope that needs supplementary testing or sorting out, and then proceed to implementation.
Can it be implemented together with the complete device development project?+
It can be used as a work package in the overall project, or it can be implemented separately for existing products. It is necessary to explain the interfaces with other modules, versions and final machine verification responsibilities.
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