Discussion archive for uweschmidt.org
-
Catching up
Hey guys!
P.S….will a higher output IR LED allow for the wiiremote to be placed further away from the board? I currently can only have it about 1.5 meters away. Anything further than that and it doesn’t work.
I suggest you have a look at the wiimoteproject.com forums, this post is especially good. The Wiimote can also apparently “see” some wavelengths better from further away. I’m be no means an expert on that. I just remember having read it somewhere.
I still only can see IR sources if I run the application via the command line using “java -jar …”. Running the application (on the mac) or double clicking the jar starts the program, but I can’t seem to detect the IR pen.
That’s odd. You mean the program starts up fine and successfully connects but no IR dots are detected? Did you do that like ten times in a row and always the same behavior?
… with your software I am back to the situation I had with less bright LEDs…jagged and broken lines when drawing and loosing windows when I move them. Using Johnny Lees app eliminates these problems totally.
Johnny’s app doesn’t really do any magic :) It could have something to do with his Wiimote library. It’s unlikely but I haven’t looked at the code. But here comes a general thing:
The communication with the Wii Remote is undocumented and not fully understood. All that is known has been found out by members of the community through reverse engineering.
Just consider this quote from Wiibrew:
After these steps, the Wii Remote will be in one of 3 states: IR camera on but not taking data, IR camera on and taking data and half sensitivity, IR camera on and taking data at full sensitivity. Which state you end up in appears to be pretty much random. Repeat the steps until you’re in the desired state.
So far I’m not aware of a way to query the IR camera’s state. That’s the reason why the program behaves differently sometimes. A future version of the software will have some “Reset Camera” function that re-initializes the IR camera. So please test several times before thinking it always works like on first try.
… Other than that it is great software !!! - but I´m back to the long startup with Bluetooth connecting …
The current version (0.9.1) always does a bluetooth device discovery and will connect to the first Wiimote that is found. I’m planning to include the option of connecting to a specific Wiimote by using its Bluetooth address. It is much quicker and has the advantage that nobody else can interfere with another Wiimote (like in a classroom) and beeing connected first.
… and imouse or Dmouse as free rightclick apps running too.
Why aren’t you using the built-in right click function? If it’s because it doesn’t work well in Windows, that will be fixed in the next version (already implemented, see Julien’s post).
I finally figured out that although I am getting the message, I can still calibrate and successfully move forward with my experiment.
Which message? And are you using the latest version?
Can anyone articulate the best way to place a remote so that is it is appropriately angled for the whiteboard?
I certainly can not, but try the wiimoteproject.com forums. One help with calibration are the Visible IR dots in the GUI. Point at each corner of the screen while moving the Wiimote around so that it can just see the light.
Uwe
Licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Germany License.