Quick Started

This chapter will guide you to setup the SenseCAP T1000 Tracker via SenseCAP Mate APP.

User Guide

Device Functions

Work Mode

To apply to different scenarios, there are several different working modes on the SenseCAP T1000 tracker, which you can choose according to your needs.

Work Mode	Description	Scene
Standby Mode	Only heartbeat packets are uploaded, just includes battery info. The location can be obtained using the LoRa downlink command.	If you need to locate the device for a long time and the device can run for a long time before being charged, the cloud platform can issue a location request command to locate the device.
Periodic Mode	Set an interval at which the device periodically uploads location and sensor data.	This mode is recommended for most scenarios.
Event Mode	Adjust the upload interval according to the temperature, light and acceleration sensor of the tracker, including temperature event, light event, motion event, motionless timeout, and shock event.	It can be used in complex scenarios, such as monitoring the transportation of important items. But the power consumption increases a lot.

Sensor Function

The SenseCAP T1000 Tracker is equipped with 3 sensors: Temperature sensor, Light sensor and 3-Axis Accelerometer. You can choose enable or disable these sensors:

• Turn off all sensors, but you can also choose a version without sensor to reduce costs.
• Only the temperature and light sensors are enabled to monitor data periodically with low power consumption.
• When temperature, illumination and accelerometer are used as trigger conditions, the sensor will always be powered, and the device consumes a lot of power.

Sensor	Description
Temperature	This is an onboard independent temperature sensor with an accuracy of ±0.5~1℃. It should be noted that there may be some temperature measurement delay here, because it is separated from the shell. Range: -20 to 60℃; Accuracy: ± 1℃(min 0.5℃, max 1℃); Resolution: 0.1℃
Light	The light sensor is not the actual lumen value monitored, but a percentage of the light from dark to amount. Mainly can be used for anti-demolition monitoring and some light sensitive monitoring. Range: 0 to 100%, (0% is dark, 100% is brightest)
3-Axis Accelerometer	By setting the value of acceleration, motion event and shock event are triggered.

Data Cache

The device can cache data, which can be enabled through Bluetooth configuration by opening "GNSS Data Cache". The device uploads confirmation packets. When the LoRaWAN signal coverage is weak or there is no network coverage, the device cannot receive an ack when uploading data. In this case, the data will be saved and entered the next cycle. When the device successfully uploads data at some point, it will send offline data. The maximum number of data that can be cached is 1000 records.

Button Function

Actions	Description	LED Status	Buzzer
Press button and hold for 3 seconds	If the tracker is powered off, press and hold the button for 3 seconds to turn it on. The Bluetooth pairing will be activated automatically, and the user can use the app to scan and connect.	The LED flashes once a second.	Melody of rise
	If the device is powered on, press and hold the button for 3 seconds to activate Bluetooth pairing.	The LED flashes once a second.	None
Press button and hold for 9 seconds	Power off.	None	Melody of descent
Join LoRa network	After exiting the Bluetooth settings, try to join the LoRaWAN network.	The breathing light flashes when trying to access the network, and flashes quickly if the network is successfully joined	A quick and cheerful melody when the network is successfully joined
Press once	Get location/sensor data, upload data, and trigger the "Press once" event immediately.	The LED is bright for 2 seconds	A sound will beep when the data is uploaded successfully.
	If Bluetooth pairing is turned on, press once can be turned off Bluetooth.	The LED will off	None
Press twice continuously	If the SOS is set to single-shot mode, double-clicking the button will activate the single-shot SOS mode and upload the location/sensor data and SOS events once.	Twinkle with the sound	3 seconds of alarm sound
	If the SOS is set to continuous mode, double-click the button to activate the continuous SOS mode. The location, sensor data, and SOS events will be uploaded once every minute, and the mode will automatically end after 30 times.	Twinkle with the sound	A constant alarm sound
	Double-click twice to exit SOS mode	None	None

Note

• It's recommended to power off the device if it's not in use.
• When first turned on, it is recommended to test it outdoors, as the GPS needs to update the time via satellite.
• Please make sure the frequency band matches your gateway frequency.

Get Started

Connect to SenseCAP Mate App

• Step 1: Download SenseCAP Mate App

SenseCAP Mate App is used to config LoRa parameters, interval, bind devices to your account and check device basic information.

• For iOS, please search for “SenseCAP Mate” in the App Store and download it.
• For Android, please search for “SenseCAP Mate” in the Google Store and download it.

• Step 2: Add Device

Login to the SenseCAP Mate APP. Click 'Add Device' tab on the top right, then scan the QR code on the device label.

Press the button for 3 seconds, and select device by SN.

There are 2 configuration mode:

• Quick Configuration:For quick start, you can select quick config the basic parameters
• Advanced Configuration: To set more parameters please check the following steps.

Quick Configuration

For Quick Configuration, you only need to setup the following parameters:

• Frequency:it should be same as your gateway.
• Uplink interval: The uplink interval of Periodic Mode (default mode), you can set other mode via “Device Bluetooth Configuration” on “User” page.

Tracker will try to join LoRaWAN network, the breathing light flashes when trying to join the network, and flashes quickly if the network is successfully joined with a quick and cheerful melody.

Advanced Configuration

• Press button and hold for 3 seconds to turn it on, then turn on the Bluetooth pairing automatically, user can use the app to scan and connect.
• Open the App and click the “Tracker T1000”. Select the “Setup” to config the tracker.
• Select the device by S/N (S/N is on the label of the device). Then, the basic information of the sensor will be displayed after entering.

Click the “Measure”, then you will get the sensor values:

Temperature	Range: -20 to 60℃; Accuracy: ± 1℃(min 0.5℃, max 1℃); Resolution: 0.1℃
Light	0 to 100%, (0% is dark, 100% is brightest)

LoRa Parameters Setup

Trackers are manufactured to support universal frequency plan from 863MHz~928MHz in one SKU. Every single device can support 7 frequency plans.

Platform

Platform	Description
SenseCAP for The Things Network	Default platform. It must be used with SenseCAP Gateway. SenseCAP builds a proprietary TTN server that enables sensors to be used out of the box when paired with an SenseCAP gateway. SenseCA Outdoor Gateway SenseCA Indoor Gateway
SenseCAP for Helium	When there is the Helium network coverage, data can upload via Helium. Devices run on a private Helium console of SenseCAP. Users do not need to create devices on Helium console, out of the box with SenseCAP Mate App and Portal. Helium Coverage
Helium	Connect device to your public Helium console
The Things Network	Connect device to your TTN(TTS) server
Other Platform	Other LoRaWAN Network Server

Parameters	Description
Frequency Plan	EU868 / US915 / AU915 / KR920 / IN865 / AS923-1 / AS923-2 / AS923-3 / AS923-4	Default EU868
Packet Policy	1C	LoRaWAN use confirm packet
LoRaWAN ADR	Default open	LoRaWAN parameters, default open is recommended
Restore LoRa Configuration	When “Platform” switches back to SenseCAP from another platform, LoRa parameters (EUI/App EUI/ App Key etc.) need to be restored	You can use this function when you need to restore LoRa parameters to factory defaults

The sensor supports two network access modes, OTAA by default.

Parameter	Description
OTAA (default)	Over The Air Activation, it joins the network through Device EUI, App EUI, and App Key.
ABP	Activation By Personalization, it joins the network through DevAddr, NwkSkey, and AppSkey.

The device uses OTAA to join the LoRaWAN network by default. So, it can set the device EUI, App EUI and App Key.

Parameter	Type
Device EUI	16, hexadecimal from 0 ~ F
App EUI	16, hexadecimal from 0 ~ F
App Key	32, hexadecimal from 0 ~ F

Note

When using the SenseCAP platform, the EUI, APP EUI and APP Key are fixed and are the same as the sensor label.
When the sensor is selected to be used with a public platform such as Helium or TTN, the EUI will not change, and the sensor will generate a new fixed App EUI and App Key for network access.
To obtain EUI information in batches, please contact our sales team.

Frequency	Common Name	Sub-band
EU863-870	EU868	--------
US902-928	US915	Sub band from 1 to 8 (default sub-band 2)
AU915-928	AU915	Sub band from 1 to 8 (default sub-band 2)
KR920-923	KR920	--------
IN865-867	IN865	--------
AS923-1-TTN	AS1	Frequency plan for TTN
AS923-2-TTN	AS2	Frequency plan for TTN
AS923	AS923-1	Frequency plan for Helium
	AS923-2
	AS923-3
	AS923-4

Note

Different countries and LoRaWAN network servers use different frequency plans.
For Helium network, please refer to: Helium-frequency-plans
For The Things Network, please refer to:TTN-frequency-plans

Work Mode Setup

Please setup the work mode according to your needs.

Parameters	Description
Heartbeat Interval	When no data is uploaded by the device within the heartbeat interval, a heartbeat packet will be triggered. This packet only contains battery information.	Default 720 minutes.
Enable Temp&Light	If this switch is turned on, temperature and light will be collected and uploaded, but it will increase power consumption.	Off by default.
SOS Report Mode	Single	If SOS is set to single mode, double-clicking the button will enable the single-shot SOS mode and upload the location/sensor data and SOS events once
	Continuous	Default use continuous. If SOS is set to continuous mode, double-click the button to open the continuous mode of SOS, and upload location, sensor data and SOS events once in 1 minute, and automatically end after 30 times
Work Mode	Standby Mode	Upload heartbeat packets (battery level only) based on the heartbeat interval.
	Periodic Mode	Location and sensor data are uploaded according to the upload interval.
	Event Mode	Set threshold trigger conditions according to measured values such as temperature, light, and movement, and adjust the upload interval after trigger.
Uplink Interval (min) – Periodic Mode	Periodically locate and upload data.	Default 60 minutes. The higher the frequency, the higher the power consumption.
Restore All Settings	Restore all configuration parameters to factory Settings, includes LoRa, Work Mode and Geolocation.

For Event Mode, there are five events:

Event Mode	Description
Uplink Interval – Non-event (min)	This is the upload interval when no events are triggered.	Default 60 minutes. Range: 1~10080 min.
Shock Event	When the shock event is enabled, the shock of the tracker will trigger a data report, including the shock event, location, and sensor data.	Off by default.
	3-Axis Motion Threshold (mg)	Default is 300. When the acceleration exceeds 300mg, the shock event is triggered.
Motion Event	When the acceleration exceeds the set value, the device starts to move, and when there is no movement for 2 minutes, the device movement stops. Set the upload interval according to the start movement and stop movement.	Off by default.
	3-Axis Motion Threshold (mg)	Default is 30. When the acceleration exceeds 30mg, determine that the device is in motion, when it is 2 minutes below this value, determine that the device is in motionless.
	Uplink Interval on Motion(min)	Set the upload interval for the current state when the device is in motion.
Motionless Event	When the device is stationary in a location for more than a certain amount of time, a stationary timeout event is triggered.
	Motionless Timeout(min)	Default is 360 minutes.
Temperature Event	If the temperature event is enabled, you can set the upload interval based on the temperature.	For example, Uplink Interval=10, Value≥30, if the temperature is higher than 30 ° C, device will upload the location at 10 minutes interval.
	Sample Interval (s)	Default 30 seconds. The temperature is detected every 30 seconds. When the threshold is triggered, upload location and sensor data.
	Uplink Interval (min)	When the temperature exceeds the threshold, the location and sensor data are uploaded according to this interval.
	Value Rule	One of the four threshold rules can be set.
Light Event	If the light event is enabled, you can set the upload interval based on the temperature.	For example, Uplink Interval=10, Value≥30, if the temperature is higher than 30 %, device will upload the location at 10 minutes interval.
	Uplink Interval (min)	When the light exceeds the threshold, the location and sensor data are uploaded according to this interval.
	Value Rule	One of the four threshold rules can be set.

Geolocation Mode Setup

The tracker supports positioning via GNSS, Wi-Fi, and Bluetooth.

• GNSS: The longitude and latitude can be directly obtained through GPS and other satellite positioning, then upload data via LoRa.
• Wi-Fi: Passive scanning, uploads the scanned 4 MAC addresses via LoRa.
• BLE: Uploads the scanned 3 best signal MAC addresses of Beacon via LoRa.

Geolocation	Description
Geolocation Strategy	Only GNSS	Default use GNSS. Only GNSS is used for position.
	Only Wi-Fi	Only Wi-Fi scans are used for position.
	Wi-Fi+GNSS	Use Wi-Fi before GNSS. If Wi-Fi fails, then use GNSS in one geolocation cycle.
	GNSS + Wi-Fi	Use GNSS before Wi-Fi. If GNSS fails, then use Wi-Fi in one geolocation cycle.
	Only Bluetooth	Only Bluetooth scans are used for position.
	Bluetooth + Wi-Fi	Use Bluetooth before Wi-Fi. If Bluetooth fails, then use Wi-Fi in one geolocation cycle.
	Bluetooth + GNSS	Use Bluetooth before GNSS. If Bluetooth fails, then use GNSS in one geolocation cycle.
	Bluetooth + Wi-Fi + GNSS	Use Bluetooth, Wi-Fi and GNSS for positioning in turn (switch to the next type of positioning after one type of positioning fails)
GNSS Timeout	The maximum time to spend waiting for the GNSS to get a coarse position fix	Default is 60s. It is not recommended to modify, the longer of the time, the bigger of power consumption.
GNSS Data Cache	When it is not possible to upload data through LoRa, the data is saved locally and uploaded when the LoRa signal is recovered.	Off by default.

After all parameters are configured, click “Send”. If no parameter needs to be modified, exit Bluetooth configuration, and return to the home page. At this point, the device initiates a LoRa network access request.

Device Data View

SenseCAP Mate App

Check the Location on the APP.

SenseCAP Portal

The main function of the SenseCAP Portal is to manage SenseCAP devices and store data. It is built on Azure, a secure and reliable cloud service from Microsoft. Users can apply for an account and bind all devices to this account. The SenseCAP Portal provides a web portal and API. The web portal includes Dashboard, Device Management, Data Management, and Access Key Management. The API is open to users for further development.

• Dashboard: Including Device Overview, Announcement, Scene Data, and Data Chart, etc.
• Device Management: Manage SenseCAP devices.
• Data Management: Manage data, including Data Table and Graph section, providing methods to search for data.
• Subaccount System: Register subaccounts with different permissions.
• Access Key Management: Manage Access Key (to access API service), including Key Create, Key Update, and Key Check.

Device Data View

Log in SenseCAP Portal

If you have created an account through the APP, you can log in directly.

1) Select register account, enter email information, and click "register", the registered email will be sent to the user's mailbox

2) Open the "SenseCAP…"Email, click the jump link, fill in the relevant information, and complete the registration

3) Return to the login interface and complete the login

Check SenseCAP Portal User Guide for more details.

SenseCAP API

SenseCAP API is for users to manage IoT devices and data. It includes 3 types of API methods: HTTP protocol, MQTT protocol, and Websocket protocol.

• With HTTP API, users can manage LoRa devices, to get raw data or historical data.
• With MQTT API, users can subscribe to the sensor's real-time measurement data through the MQTT protocol.
• With Websocket API, users can get real-time measurement data of sensors through Websocket protocol.

Please check API User Guide for more details.