| TOP | BOTTOM |
 |
 |
Sub-G Solar Power Asset Tracker uses AxDen's Aggregator Platform to collect key information required for asset tracking such as temperature, acceleration, and GPS location.
This is an example that provides a quick test for various service scenarios that require long-distance communication of 1Km or more or 2G/3G/4G communication.
Related hardware kits can be purchased from the Naver Smart Store.
Purchase Link : naver smart store
You can purchase it by contacting [email protected] or www.axden.io
| MCU | Description |
|---|---|
| CC1312R1 | TI ROTS, EasyLink |
* Low-power technology with TI Sensor Controller is available in the Production version family.
| Sensors | Description |
|---|---|
| BMA400 | 3-Axis acceleration sensor |
| SI7051 | temperature sensor |
| L70 | GPS sensor |
| NEO-M8N | GPS sensor |
| BG95/96 | 4G (LTE-M, Cat-M1) |
| SARA-U2 | 2G, 3G |
| SPV1050 | Solar battery charger (Max charge current 80mA) |
| Solar | On board |
| Battery | 3.7V Lithium Battery |
The Sub-G Solar Power Asset Tracker example collects key information necessary for asset tracking, such as temperature, acceleration, and GPS location, and charges the battery using solar charging.
Transmit the collected information to Sub-G or 2G/3G/4G communication.
Interwork with AXDEN Aggregator Platform to check sensor information on the web and mobile whitout building infrastructure such as server and DB
Learn Edge AI using sensor information stored in the AXDEN Aggregator Platform.
If you have an AA-MB-05 board, you can check the communication through the terminal.
Connect the AA-MB-05 board to the PC.
If you have a TCP server, you can check it through the server.
In this example, the IP and Port number of the example server provided by AXDEN are temprarily set.
| RF RX Sub-G example terminal | RF RX 2G/3G/4G Server example log |
 |
 |
As shown in the image below, you can check the amount of battery charging current using sunlight using a multimeter.
Register the MAC Address of the device after signing up as a member on the AXDEN Aggregator Platform website.
Enter COMPANY ID nad DEVCIE ID provided on the AXDEN Aggregator Platform website into COMPANY_ID and DEVCIE_ID in the Protocol.h header file.
#define COMPANY_ID 0
#define DEVICE_TYPE 0
Complie and flash.
Check whether COMPANY_ID and DEVICE_ID are applied correctly through the terminal
Sensor information can be found on the Web or Mobile as shown in the image below
IP and Port can be changed in the set_bg96_socket_connect function of the bg96_tcp_data_upload function of the bg96.c file.
IP and Port can be changed in the sara_u2_tcp_data_upload function of the set_sara_socket_connect function of the sara_u2.c file
Module replacement is possible in the Protocol.h file.
#define BG96
#define SARA_U2
#define QUECTEL_GPS
#define UBLOX_GPS
When BG95/96 is used, -> #define SARA_U2 / Annotated
Same as the image below.Set UART Pin in syscfg file
When SARA-U2 in used, -> #define BG96 / Annotated
Same as the image below.Set UART Pin in syscfg file
When L70 in used, -> #define UBLOX_GPS / Annotated
When NEO-M8N in used -> #define QUECTEL_GPS / Annotated
You can check in the board_define.h header file.