I used 3 anchors and 1 Tag based on DWM1001c module. for now, I have the range from the tag to each anchor and the know positions of the three anchors in a backend server with flask.
I would like to compute the estimated value of the tag. I found this in wikipedia
yes, that is the most appropriate for the use case of exactly three anchors.
least square is an optimisation method that requires an initial estimate, and the iteration count depend on that, it is also way more calculations compared to the cartesian method. You need optimisation method if you have more than three anchors, because then, you no longer have a single possible solution but need to take an average.
Remember that you can take many measures of each range to improve accuracy, and you can also average across time, or sliding window filter
I recently posted a survey of range to position techniques
The way i would do triangulation for 4 points is like this. So the distance from each anchor (red) to the tag (blue) u have: r1, r2, r3, and r4. and u know the xy coordinate for each anchor. U can write out the equation for the circular path for each anchor. and then compute for x and y. this example is for 2d only.
my question has always been that, the way u guys are doing it now, does the tag itself computes it’s location or the anchors report their distance to the tag to a centralized system that does the computation?
I did not work on a ready implementation yet for 4 or generic case.
For 4 or more, Least square makes sense, at worst, you implement both, and compare for the same number of samples which one needs more cpu time and provide better result. In case multilateration only works with 3 and you have 4 that’s how AndyA explained in the forum, you repeat 4 times with different set of 3, not ideal.
@uni it depends on the architecture you need to implement.
for me, it is not a perfect architecture to compute the location on the tag becauz it will consume a lot of power which is not perfect specially when your tag is powered with a battery, so I just send the data from anchor to a backend server which is my pc and did the trilateration there.
if you don’t care about the energy consumption, you can add a report msg if u use DS-twr and do the trilateration on the tag and if you use SS-twr you already have the ranging on the initiator (tag) itself so just do the trilateration on it.
ok, that’s what i thought. although at first, i thought if the tag doesn’t hav to send the pulse signals, it would consume less energy just by listening. bc transmitting would consume more power. it’s possible if the calculation is simple, it would consume less energy computing it on the tag. but u are right its depends on the architecture bc it would make sense to do something like this on a mobile phone instead of a low battery power operating device.
ok, it occurs to me that if the anchors do some of the computations themselves. as edge devices, they can off load the central device and may produce better outputs. bc with uwb rf, devices can operates as much higher throughput. u cant transmit that much data on regular 2.4ghz band. so it maybe better to do the averaging on the anchors. bc even if the central device has more than enough computing power to compute the raw throughput, it cannot receive data as fast as the anchors do. it would create a lot of stress on the network.