Reacties geplaatst door Gabzz

4 Reacties

Tim
TimAllesweter
geplaatst in LoRa Forum

LoRa | Geolocation

[user=8294]Rick S.[/user] THX Perhaps it's me but I find the wording ambiguous: "but this will be reversed by the time-stamp DevLocTime (and the absence of an update)." Means that neither an update is used nor the time-stamp is updated (to the failed computation time) in the next "data-message". In that case the response is accurate and consistent. Do I understand well? Sorry, it's an old man typing here ;-)

59
Rick S.
Community manager
6 jaar geleden
Tim
TimAllesweter
geplaatst in LoRa Forum

LoRa | Geolocation

[user=227]Tim[/user] Sorry for not being clear enough. What I wanted to say is: Is there a situation where the backend needs more than one transmissions to compute a location? I suppose the answer is yes because my device might be able to send data but TDoA might fail because of harsh multi path environment (i.e. a densely built area for example). If the gateways gets numbers that are totally banana the backend might decide to treat them as outliers and not compute. The result from the user PoV is that data is safely transmitted but no new location is computed (and the location timestamp remains the old one). If, by chance, the backend decides instead to use a Last known location and, yet, it updates the Location Calculation timestamp or, worse, it sends a location message out, that is quite against criteria of data accuracy, consistency and timeliness. I am sorry for this wordy response but I can't make it simpler. :-[

59
Rick S.
Community manager
6 jaar geleden
Tim
TimAllesweter
geplaatst in LoRa Forum

LoRa | Geolocation

[user=11455]rharte[/user] Well put. That's an additional aspect I wanted to tackle. I have the impression we can't possibly correlate location with a data transmission (that explains also why it's advertised for stationary objects). For example, a JoinRequest might trigger a position update, yet no data payload is sent. The device might move, in the meanwhile, and end in a zone where multipath prevents location data to be computed effectively (i guess some kind of outlier filter is implemented). However the last known position would still be the one computed at JoinRequest time. Am I completely off path? One wonders if a LinkCheck might thus trigger a location update.

59
Rick S.
Community manager
6 jaar geleden
Tim
TimAllesweter
geplaatst in LoRa Forum

LoRa | Geolocation

[user=227]Tim[/user] A quick question: Supposing my sensor is well within range of loc-enabled stations, could it be possible that I am not guaranteed to receive an update on each transmission because, for instance, the backend hasn't quality data to compensate for external factors (e.g issues of multi path or whatever the DTOA issue might occur). My question boils down to understand if more than one transmission might still be required even in optimal network coverage of location-based gateways. THX

59
Rick S.
Community manager
6 jaar geleden

Badges

Toon alle badges
Forumvoorwaarden