How much does it cost to develop a GNSS IoT tracker integrated with Amazon AWS?
Project Context & System Requirements
The client approached WizzDev to develop a GNSS (Global Navigation Satellite System) IoT tracker that would be compact, energy-efficient, and capable of real-time location tracking. The device needed to store sensor data locally and support communication via GSM/GPRS, SigFox, and LoRa. It also required secure over-the-air (OTA) firmware updates, integration with Amazon AWS, and robust debugging tools. With ultra-low power consumption as a key constraint, power optimization was prioritized from day one.
Current Key Pain Points Identified
These challenges required a flexible and well-structured hardware and firmware approach to ensure reliable communication, efficient power use, and future-proof connectivity. The following components were selected to address the project’s technical and operational requirements.
Hardware Stack
Firmware Stack
Solution Overview
To develop a GNSS IoT tracker that met strict requirements for power efficiency and modularity, WizzDev designed a tailored firmware architecture focused on long-term maintainability. The system featured a real-time, thread-safe logging tool, hard-fault handlers, and assertion mechanisms to ensure traceability and stability. Each communication driver GPS, GSM/GPRS, and UNB was implemented as a standalone module for clean integration and streamlined testing. A dual-layer memory system (RAM and external Flash) enabled safe buffering and storage of sensor and location data prior to transmission.
Project Duration Estimate
| Stage | Description | Min h | Max h |
|---|---|---|---|
|
Project setup & documentation review |
Reviewing technical documentation, evaluating modules (GPS, GPRS, UNB), and preparing the development environment. |
18 |
30 |
|
Project planning & design |
Defining architecture, component interactions, and milestone planning. |
18 |
30 |
|
Debug tools (logger, assertions, fault handlers) |
Setting up thread-safe logging, assertion handlers, and fault recovery mechanisms for robust development. |
18 |
30 |
|
SPI communication with protocol parsing |
Implementing SPI interface with protocol parser, checksum validation, and secure data exchange. |
24 |
40 |
|
GPS driver implementation |
Developing the GNSS driver and integrating support for ephemeris data storage and parsing. |
56 |
112 |
|
GSM/GPRS driver with networking |
Integrating cellular communication with network stack and data routing logic. |
112 |
224 |
|
Flash over SPI |
Enabling data storage and retrieval via SPI-connected external Flash memory. |
32 |
48 |
|
SigFox/LoRa (UNB) driver |
Developing communication drivers for ultra-narrowband (UNB) networks: SigFox and LoRa. |
112 |
168 |
|
Battery charger integration & testing |
Implementing battery management and running charging and discharge tests. |
56 |
112 |
|
Power optimization |
Tuning power usage through peripheral control, sleep modes, and runtime measurement. |
42 |
70 |
|
OTA with fallback (external flash) |
Developing firmware update mechanism with rollback support using external Flash. |
56 |
168 |
|
AWS integration |
Enabling data transmission to the AWS cloud and configuring basic IoT infrastructure. |
56 |
112 |
|
Documentation |
Creating internal and technical documentation covering architecture, code, and user instructions. |
16 |
40 |
|
Final testing & QA |
Performing integration testing, validating communication, and power performance. |
56 |
112 |
|
PM |
Project management |
100 |
140 |
|
Summary time for project: |
|
720 |
1290 |
Risk Assessment
| Risk | Description | Min h | Max h |
|---|---|---|---|
|
Protocol Complexity (SPI) |
Custom parsing issues or unstable comms |
0 |
16 |
|
OTA Failure Recovery |
Fallback logic, testing delays |
0 |
32 |
|
AWS Cloud Unreadiness |
API or access issues |
0 |
16 |
|
Power Tuning |
Missed targets, hardware variance |
0 |
16 |
|
Integration Testing Delays |
Conflicts or retesting loops |
0 |
32 |
|
Total risk estimates: |
|
0 |
112 |
