Engineering Scope
LoRa/LoRaWAN low-power nodes are developed to solve specific engineering problems in low-power projects. The work starts from the customer's existing design and business requirements to implement sending, receiving windows, confirmation, retransmission and network access recovery; the firmware, network parameters, message records and field test reports are delivered according to the agreed modules.
Check input with baseline
Check the adopted protocol, frequency band parameters, packet length, reporting period and gateway conditions, and clarify the measurement and modification scope.
Implementation and adaptation
Implement sending and receiving windows, confirmation, retransmission and network access recovery, and record solution choices and dependency conditions.
Target environment joint debugging
Check the air interface duration, downlink aging, packet loss recovery and overall machine energy, and confirm the business behavior after parameter changes.
Document and record delivery
Provide firmware, network parameters, message records and field test reports, describing versions, construction or usage methods.
Project Workflow
- Input confirmation: adopted protocol, frequency band parameters, packet length, reporting period and gateway conditions.
- Implementation method: Implement sending, receiving windows, confirmation, retransmission and network access recovery.
- Phase review: Check air interface duration, downlink aging, packet loss recovery and overall machine energy.
- Project delivery: firmware, network parameters, message records and field test reports.
Design Conditions and Functional Limits
The scope of the LoRa wireless link is different from that of the LoRaWAN network protocol. You need to confirm whether it is a custom protocol or a standard network before designing the network access and reception process.
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
- The adopted protocol, frequency band parameters, packet length, reporting period and gateway conditions.
- 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 |
|---|---|
| Firmware, network parameters, message records and field test reports | Check the editability, version, usage instructions and dependencies by file list. |
| Implementation verification | Check the air interface duration, downlink aging, packet loss recovery and overall machine energy, 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
Are LoRa and LoRaWAN directly interchangeable?+
The scope of the LoRa wireless link is different from that of the LoRaWAN network protocol. You need to confirm whether it is a custom protocol or a standard network before designing the network access and reception process.
What information do I need to prepare before starting the project?+
This work focuses on the protocols, frequency band parameters, packet length, reporting cycle and gateway conditions that need to be adopted. 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 reception category will affect the downlink timeliness and equipment energy consumption, and should be selected and verified according to the control requirements. LoRaWAN receive window reference
Online
Phone
WeChat
Top