FAQ
Location Related
GPS Positioning Accuracy
GPS satellites broadcast their signals in space with a certain accuracy, but what you receive depends on additional factors, including satellite geometry, signal blockage, atmospheric conditions, and receiver design features/quality.
Many things can degrade GPS positioning accuracy. Common causes include:
- Satellite signal blockage due to buildings, bridges, trees, etc.
- Indoor or underground use
- Signals reflected off buildings or walls ("multipath")
Therefore, in a wide unobstructed area you will get a better GPS signal, thereby getting more accurate positioning results.
Why there is no GPS location data?
-
GPS location may not be available when the tracker is indoors. GNSS positioning requires an open outdoor environment. If you're indoors, the GPS location may be time out due to the weak signal. Make sure the device is placed outdoors for GPS accuracy.
-
Ensure proper device installation by orienting the device with its front facing upward to prevent obstruction of the antenna's position
If your T1000 does not provide GNSS location data, please follow the troubleshooting steps below to check the device configuration, installation environment, and GNSS positioning status.
1. Check the Device Installation Environment
GNSS performance can be affected by the device installation environment.
Please make sure that:
- The front side of the T1000 is not obstructed.
- The device is not placed inside a metal enclosure or surrounded by materials that may significantly block GNSS signals.
- There are no metal objects close to the device.
- The device is tested in an open outdoor environment with a clear view of the sky.
2. Increase the GNSS Scan Time
The GNSS Scan Time determines how long the T1000 searches for GNSS satellites during a positioning operation.
If the GNSS Scan Time is too short, the device may not have enough time to obtain a valid GNSS fix, especially when the device is being tested for the first time or in an environment with relatively weak GNSS signals.
Please open the General settings of the T1000 in the SenseCraft App and increase the GNSS Scan Time.
The maximum GNSS Scan Time is 120 seconds.
Tip: For troubleshooting, we recommend using a longer GNSS Scan Time first to determine whether the issue is related to the available time for satellite acquisition.
3. Check the GNSS Positioning Status in the LoRaWAN Uplink Payload
If the T1000 still does not provide a location, please check the raw LoRaWAN uplink payload.
The uplink payload contains the positioning result and positioning status. By checking the raw payload, you can determine whether:
- GNSS scanning timed out;
- Another positioning method was used;
For example, the following payload is an example of a GNSS scan timeout:
110100000064a763a0014100002f
In this example, the first byte 11 indicates the Positioning Status and Sensor Packet, and the second byte 01 indicates that the GNSS scan timed out and failed to obtain the location. You can find more details in the T1000 Payload Format documentation.
4. Provide the Raw LoRaWAN Uplink Payload
If the issue persists after checking the above items, please provide several raw LoRaWAN uplink payloads from the T1000 and contact our techsupport team at [email protected].
Why doesn't Wi-Fi or Bluetooth location display on the SenseCAP App map?
-
Wi-Fi location requires a third-party map parsing service, which must be invoked by users for parsing. Currently, the Mate App supports GNSS positioning display only.
-
Bluetooth positioning relies on Bluetooth beacons and their respective locations for accurate tracking. block the position of the antenna.
Network Related
Helium Network
For users operating with the EU868/RU864 region:
It is not recommended to set the upload interval to less than 4 minutes.
If you set an upload interval of less than 4 minutes, you may notice a timestamp misalignment between the device's uplink and the current time.
Here's the rationale:
Given the 1% duty cycle constraint in EU868, the device must patiently wait approximately 4 minutes for each uplink transmission. Additionally, the Helium network initiates data-rate and power corrections only after accumulating 20 consecutive uplink packets marked with the ADR bit set to 1.
So if the upload interval you set is less than 4 minutes, real-time data will be temporarily stored in RAM and held until the Helium network triggers data rate and power corrections before uploading.
How to get the keys
On the settings page, select a platform other than SenseCAP to obtain the keys.
Button Related
Join Network
Press and hold the button for 3 seconds, the green light will flash slowly, then press the button once, the green light will breathe, and then the device will try to join the loRaWAN network.
Force reboot
Press and hold the button, then connect the charging cable, release the button after connecting, the green light will breathe, and then the device will be forced to restart.
Battery Related
Battery Life
Battery life depends on factors such as uplink interval, sensor usage, LoRa transmission distance, and operating temperature. Predicted battery life is based on a typical working environment (25°C) and serves as a reference. Actual battery life may vary.
EU868(1C/SF12)
| Upload Interval | 1 minute | 5 minutes | 60 minutes | 1 day |
|---|---|---|---|---|
| Battery Life(day) | 2.62 | 27.21 | 106.78 | 209.3 |
US915(1C/SF9)
| Upload Interval | 1 minute | 5 minutes | 60 minutes | 1 day |
|---|---|---|---|---|
| Battery Life(day) | 3.02 | 37.52 | 117.32 | 210.7 |
For detailed battery life calculations, refer to the Battery Life Calculation Form.
Charge Status
| Status | Indicator |
|---|---|
| Charging | The LED will flash once every 3 seconds. |
| Fully charged | The LED will stay always on. |
| Charging anomaly | When the device is charged below 0 ° C or above 45 ° C, the device will enter the charge protection state and cannot be charged. The LED will flash rapidly. |
If the indicator flashes quickly while charging, it may be that the power voltage is insufficient or poor contact.
Please check your power supply or try another power adaptor.
How long does it take to fully charge?
It typically takes about 2 hours to fully charge.
Can it continue uploading data while charging?
Yes, it can continue uploading data while charging.
Sensor Related
No sensor data
To save power, the temperature/light sensor function is disable by default, so you need to enable it on the SenseCAP Mate APP first.
Cache Data
How does it work
When the LoRaWAN signal is weak or there is no network coverage, the data will be saved in the device. When the device returns to an area with the LoRaWAN network coverage, it will send the real-time data first, and then upload the cache data.
During each upload period, it will upload the latest location first, and then the cache data. Only a few packets of historical data are uploaded per cycle, so this will not affect the duty cycle.
Note
Since the device can only cache about 1,000 offline data, if you are in a place without LoRaWAN network coverage for a long time, when the offline data reaches the limit, some old data will be overwritten by new data, so you may 'lose' some data.
How to batch configure
Please check the Quick Start to setup the first device, and then click the Template module in the upper right corner.
Click Save as Template, name your template and then click Confirm.
When you configure other devices later, you can directly select the template you saved.
If you want to share your template to others, you can choose Copy Link to Share or Download Template.
Other users can choose to use your template by copying the shared URL or importing the template file.
How to exit DFU mode
After a firmware upgrade failure, the device may enter DFU mode. You can see the device name SENSECAP_GR_DFU_XXXX in the SenseCraft app and the LED lights continue to flash.
-
In DFU mode, the device will automatically exit after 3 minutes of inactivity.
-
If you wish to exit immediately, you can press and hold the button for 3 seconds, and the device will reboot and return to normal operation.
If you find that the device cannot exit DFU mode despite pressing once, pressing and holding for 3 seconds, or pressing and holding for 10 seconds, please follow these steps:
Step 1: Connect the Device in the SenseCraft APP
Follow the previous steps to access the Bluetooth configuration page on the T1000, connect the device then you can see the page below:
Step 2: Upload Firmware File
Click Upload Firmware File, choose the bin file to flash the firmware.
For the lastest firmware file, please contact [email protected]
Timestamp error
If you found the timesatmp in the payload is wrong, please upgrade the firmware to the latest version.
Check Firmware Upgrade and Release Note for more details.
Application error
Can I view the device status and data in the SenseCraft App?
If the device is connected to SenseCAP Cloud, you can view the device’s status and data, such as online status, sensor data, and positioning information, directly in the SenseCraft App.
If the device is connected to another LoRaWAN cloud platform, the device information and data will not be synchronized to the SenseCraft App. In this case, you should check the corresponding device status and uplink data on the LoRaWAN platform you are using.
Integration
Integrating an application can be done in a variety of ways, depending on your needs and goals. Here are some common integration options:
- SenseCAP API:
Using an Application Programming Interface (API) is a common way to allow your application to communicate with other applications or services, you can connect your device to SenseCAP Cloud and then use the SenseCAP API to get the data.
SenseCAP API is for users to manage IoT devices and data. It combines three types of API methods: HTTP protocol, MQTT protocol, and WebSocket protocol.
Check SenseCAP API for more details.
- LoRaWAN Network Server：
You can use the SenseCAP M2 Multi-Platform gateway, then you can directly use the built-in LoRaWAN Network Server for integration.
Check the LNS Configuration for more details.
How to reset the DevNonce on the T1000
A DevNonce issue can occur when the device has made repeated OTAA join attempts.
After long-term repeated join attempts, the DevNonce counter may reach its limit and the device can no longer join normally.
A typical case is:
- The device has been used for a long time, but one day it fails to join the network successfully, even though the device frequency plan matches the gateway frequency plan.
- When checking the device logs on the server side, repeated DevNonce overflow errors are observed.
If the T1000 cannot join the LoRaWAN network because of a DevNonce issue, please contact the Seeed technical support team([email protected]). We can provide a dedicated firmware to clear or reset the DevNonce, allowing the device to join the LoRaWAN network normally again.