I am not in a position right now to check that particular test vector out but i wonder if the payload itself is in the correct format.
If you are getting the location of the GW returned then that suggests that the Skyhook lookup failed and Collos is resorting to location based on the next best thing and with a reception by only one GW that is the location of the GW.
It is interesting that the query works fine from Collos directly. I will try to take a look myself in the morning. Are you performing a simulated uplink or is this actually the payload you see in TTN console?
I am not sure to catch where it does not work for you:
1, 2, 3: Test vector seems to be fine and successfully parsed.
4: With that vector I have the location in close to Boston (42.2961366,-71.2368669) in Cayenne.
So, could you please check that in the console you have the fields correctly set ?
Then confirm that you do not get any results in Cayenne ? Do you see no GPS map, or coordinates located on your gateway instead of Boston ?
Also, could you please take a screenshot of Cayenne integration in TTN ?
Which gateways are TDOA compatible with collos?
As far as I know, none of the first gen gateways, even those with GPS, can use the TDOA feature. Is this right?
Hello guys.
One question about Collos location. I already did the regestration and i get tle location of my device (arduino with LoRa Shield). It shows at The Things Network console.
So my question is: Is there any possible ways to export the location (longitude & latitude) and store this two numbers to somewhere? I need these two numbers only. Any hints? Maybe another integration?
I hope guys you can help me beacuse i am really stuck here.
Right, first gen gateways are not able to put TOA, even with a GPS. Every gateway based on Semtech V2 reference design are compatible.
For example Kerlink iBTS or Cisco, but there should be other manufacturers…
Thanks for your response.
I did the HTTP integration to my test server and on that server i get payload data with latitude and longitude. But this coordinates are of my gateway not my device.
Did you mean something like that?
I do not understand what exactly you would like to explain to me here
I think u didn’t get me right or do you know what my question is?. Yeah I followed these steps and integretion is working OK. I get the location with Collos of my device. But now i want to parse these numbers (latitude & longitude) to somewhere (file or something like that). And i dont know how to do that
Is it working or not ? On your previous post you said you only get gateway’s coordinates. So yes, I do not get it
If so what does mean "I did the HTTP integration to my test server and on that server i get payload data with latitude and longitude. " ?
I wrote some thing a little bit confused xD Yes it is working OK. In my console i see the location of my device.
So there is see coordinates of my device shown be side the map. So my main question is how to store or parse or something like that coordinates which are shown be side the map?
I think I should not even mention the HTTP integration because there is no connection here. Let’s just leave that behind.
TTN receives the uplink from one or more GWs and instead of throwing away duplicates it keeps the meta-data from each one (primarily that is RSSI and SNR plus TOA if it is available).
If you have a payload that included WiFi sniff data for example then a payload script can be used to create the WiFi query format for WiFi base location.
TTN then forms a query with all the meta-data plus andy WiFi data that is available.
The Query is posted to the endpoint in Collos that you specify and Collos responds with a location.
TTN console then looks at the locations coming back and, if there are multiple, it posts the most accurate one to the console location.
The Cayenne integration is pretty dumb- firstly you need to add a Cayenne integration to the app (for the rest of the data such as the payload and signal strength etc.) Secondly, when you define the integration you get the option to specify a Cayenne channel number. It will quite simply, place the location returned from that particular endpoint in Collos to Cayenne to mimic a GPS device on the channel number that you specify in the integration.