You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As per my understanding, you are using multilateration for localization. I am able to localize my mobile phone with multilateration up to an extend. Are you using any Time of arrival (TOA) technique inside multilateration? LeastSquaresOptimizer.Optimum optimum = Multilateration.findOptimum(pos-arr, dis-arr); double[] result_pos = optimum.getPoint().toArray();
I am sending x,y coordinate in pos-arr and corresponding distance in dis-arr . is this method correct for performing multilateration?
The text was updated successfully, but these errors were encountered:
Are you using any Time of arrival (TOA) technique inside multilateration?
I think I don't get the question. The input for our multilateration are positions and distances, as you pointed out. I don't see how TOA is related to that. I guess you could use TOA to calculate these distances (e.g. from cell towers or satellites), but that's not applicable to Bluetooth signals.
Is this method correct for performing multilateration?
Keep in mind that the positions are expected to be in a special format (ECEF - Earth-Centered-Earth-Fixed). You can use SphericalMercatorProjection.locationToEcef(location) to get these values.
Steppschuh
changed the title
Multilateration for localisation
Is multilateration using time of arrival?
Sep 10, 2020
As per my understanding, you are using multilateration for localization. I am able to localize my mobile phone with multilateration up to an extend. Are you using any Time of arrival (TOA) technique inside multilateration?
LeastSquaresOptimizer.Optimum optimum = Multilateration.findOptimum(pos-arr, dis-arr); double[] result_pos = optimum.getPoint().toArray();
I am sending x,y coordinate in pos-arr and corresponding distance in dis-arr . is this method correct for performing multilateration?
The text was updated successfully, but these errors were encountered: