PM replied to with hosting info.
As long as the thing samples fast enough and its A/D converter has enough steps, then accuracy only comes down to calibrating the thing.
Until reading this post I didn't know what a Wii was, but I've formed an idea from all the discussion. As a games device it would have to have reasonable resolution or it would be annoying to use in a game. (I also never play computer games btw). +/- 20% accuracy has been mentioned. That may be so, but I'm pretty sure it would be consistent and linear - that is the nature of electronic devices. For a cheap item that is just for games, it doesn't matter if it is 20% different than another one in the shop, as long as it is consistent and smooth.
Calibration couldn't be easier - while hooked up and recording as per klee's instructions, just hold it level on its base (ie, rest it on the kitchen table) for a few seconds, then repeat for face down, left edge down, right edge down, nose down and bum down. Each time you are applying 1G or -1G. You can then compare this to your saved data in Excel and work out the appropriate corrections.
For a correction factor (one you multiply) you compare LEFT minus RIGHT to 2G. For a zero correction (one you add or subtract) you compare LEFT plus RIGHT to 0G.
I know I am telling some people how to suck eggs and others won't know what's going on, but hopefully this is useful for someone. Maybe klee can incorporate the calibrations into his/her spreadheet.
PS I found this post via http://www.autospeed.com.au. I used to read the 16V forum religously - that's why I could log in to respond.
thats pretty awesome dude, first thing i did after reading it was go out and buy a bluetooth thingy.
I set it all up..
Everything works perfectly =D
But i have a few questions...
Why do you multiply the var.t thing by 86400?
and when i leave my wiimote still it has a reading of 1.10 on the y axis, yet i thought it should be 1, would there be a way to add an offset so that it made it into 1 or is it right how it is now?
If you use this method in your GlovePIE code and you run the program multiple times within one sitting, the data keeps adding on to the output.txt file (so you will have a file that has all the runs that you did). Is there any method that will erase the previous data once you press "run" so that the data does not get added on?
Since output.txt is a text file open the file using notepad. Select All [CTRL A] then press DEL. Save the file and quit. The file is empty.
Or read the glovepie documentation and figure out how to erase an existing file.
Somebody is going to have to do it why not you?
Just through that in because it seems nobody really wants to read.
The guy who started the post put in his time and effort so why just copy?
This is awesome I want to do it also. I bought a wii remote. But i am unable to know if glovepie detected the wiimote or not ? In the output file, first column is time, but all I see is zeros in the last three columns.
Please if anyone has a step by step procedure..please send me. I want to really try this.
If you need any help with the math/software/hardware/calibration issues let me know. I'm a navigation engineer.
The best thing you can do with a low-grade accel is constantly calibrate it when you're stopped. If you can have some software to zero it out when you stop, you'll be all set