Gateways are media converters.
My T1000 works with any gateway, Microtik, Multitech
Gateways are media converters.
My T1000 works with any gateway, Microtik, Multitech
The tracker setup has various pre-configured configs, and one of them is āSensecap for TTNā - this is the config I am referring to here, it only works if the gateway is a sensecap one (some sort of auto config built into sensecap devices I believe)
The hidden detail in this is that the tracker uses the LR1110 radio module. This does NOT have a full GNSS on it, the data has to pass through a service provided by Semtech to get the location out of the message so it makes sense that it only works with appropriately connected gateways - that is one that passes the data to a backend that can make use of the special decoder.
I suspect that when they say TTN compatible, they mean that you can use it as a standard device on TTN but unless you hook it up to the LoRaCloud integration you wonāt get the results you expect.
The location accusation are via
Location
GNSS Constellation T1000-A/B: GPS/GLONASS/Galileo/ BeiDou/QZSS
T1000-C/D: GPS/ BeiDou
GNSS Sensitivity -145dBm cold start / -160 dBm Tracking
GNSS Location Accuracy ~1m CEP, GPS, -130dBm
Wi-Fi Positioning Passive scanning, uploads the scanned 4 MAC addresses
Bluetooth Positioning uploads the scanned 3 best signal MAC addresses of Beacon
Data Cache Cache 1000 data when there is no LoRaWAN network
This is data from my T1000
"decoded_payload": {
"err": 0,
"messages": [
[
{
"measurementId": "4200",
"measurementValue": [],
"motionId": 0,
"timestamp": 1729779428000,
"type": "Event Status"
},
{
"measurementId": "4197",
"measurementValue": 33.771592,
"motionId": 0,
"timestamp": 1729779428000,
"type": "Longitude"
},
{
"measurementId": "4198",
"measurementValue": 39.8264,
"motionId": 0,
"timestamp": 1729779428000,
"type": "Latitude"
},
{
"measurementId": "3000",
"measurementValue": 78,
"motionId": 0,
"timestamp": 1729779428000,
"type": "Battery"
}
]
],
"payload": "0900000AAAAAABBBBBBCCCBBBBAAAABBBAAA",
"valid": true
},
If your RSSI is low and the packets are not received by the gateway you are going to be missing data (Dropped packets)
low RSSI - yes I know, but my issue is that Iāve never seen this device upload ANY of its cached locations as advertised even when near a gateway. Have you had any success with this ?
Please keep in mind the device doesnāt know it is near a gateway. Itās not like WiFi where devices connect to the gateway,
Only after the network server sends the ADR command to switch to a higher data rate the device will get a notion it can transmit more data in the available time.
IIRC the default behaviour of the T1000 is to send confirmed uplinksā¦
I thought this too which is why Iāve tried many times around multiple different ones.
Of course thereās no real way for an end user to know what gateway will it connect to and where and how strong of a signal so its guess work. I asked Seeed if the signal strength can be displayed in the data reports but its only saved to the backend and not displayed anywhere in the frontend. It cannot track in my country in 2024 is the conclusion Iāve made with this device. Maybe in 2040 when thereās gateways everywhere it might be useful, if we ever get to that saturation. But for now its just a toy to me.
Also thank you Nick for the explanation about the T1000ās GNNS capabilites, very interesting. Iāll move onto other lora things, but Iām giving up on tracking for now. Thanks all for your inputs.
LoRaWAN is not WiFi or 5G. What I mean is that an end device just transmits and hopefully there is at least one gateway that receives the transmission and forwards it to TTN. There might well be multiple gateways and in that case TTN collates/deduplicates the packets from all gateways and forwards them to the application.
A small PS for those finding this thread, the Store &. Forward feature is part of the LoRaCloud system that the location services uses. So that has to use the special processing as well.
OK got it. Thanks for highlighting that Jac, much appreciated.