BleckyI finally got the time to put together a demo video:
The client is connected to the laptop with a USB connection. However, the client does all the positioning calculations, the laptop is just displaying the node positions and the current client position.
Averaging is turned right up which is why it takes a little while to update the position. This is because I live in an apartment block with lots of 2.4GHz RF flying about, so this helps to cope with that. I am integrating an accelerometer on the client to provide better intemediate updates when averaging is turned up too. But as you can see, it's pretty spot on in terms of accuracy.
Discussions
Become a Hackaday.io Member
Create an account to leave a comment. Already have an account? Log In.
Hi @Blecky, great work!
About the interference issue; did you know the transceiver you are using (AT86RF233) supports frequencies down to 2.360MHz? It's probably not legal to operate in these bands for general purpose applications but I think you can cheat a little for research purposes.
Are you sure? yes | no
[this comment has been deleted]
Ops, I think he means 2.360GHz.
Are you sure? yes | no
Ha yeah, but I've tried to use it how it should be used appropriately so others know what to expect. My apartment is probably a worst case scenario, so it's been good to test those conditions. It helps you write more resilient code too :P
Are you sure? yes | no