Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is multilateration using time of arrival? #177

Open
jasirjasir opened this issue Sep 8, 2020 · 1 comment
Open

Is multilateration using time of arrival? #177

jasirjasir opened this issue Sep 8, 2020 · 1 comment
Labels

Comments

@jasirjasir
Copy link

jasirjasir commented Sep 8, 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?

@Steppschuh
Copy link
Contributor

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 Steppschuh changed the title Multilateration for localisation Is multilateration using time of arrival? Sep 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants