Subscribe
This program allows you to use the Wii Remote (Wiimote) to turn any surface into a Low-Cost Interactive Whiteboard. It is based on Johnny Lee’s original WiimoteWhiteboard program that is written in C# and available for Windows only. My program uses Java to allow for (some) platform-independence. I also provide a Mac-only version since I’m a Mac user and this is, up to my knowledge, currently the only such program for the Mac.
For Windows only, Boon Jin has enhanced Johnny’s software and created the shareware program Smoothboard. There is also a SourceForge project that provides other implementations, but it is not getting much attention.
Check out the video and the other cool projects at Johnny Lee’s page if you have no idea what I’m talking about 
.
Features in a nutshell
- Open source
- Runs on Mac OS X, Windows, and Linux
- Simple User Interface available in English, Estonian, French, German, Italian, Polish, Portuguese, Russian, Slovene, and Spanish
- Camera Monitor and Calibration Details for better Wiimote placement
- Auto-connects up to 2 Wiimotes
- Right-click support, double-click assistance
- Mouse cursor smoothing
- Screen selection
- Touchpad Mode
- Update notification
- TUIO/OSC support for multitouch applications
More details in the Wiki.
Download (1.0.2)
Documentation & Support
You can post your comments, bug reports, feature requests, etc. at the bottom of this page. The latest documentation is available in the Wiki. You can also find out how you can help.
The wiimoteproject.com forums are a great resource for everything Wiimote. You may use this subforum to discuss everything related to my software. The Smoothboard Wiki also contains useful information for setting up your interactive whiteboard.
Infrared pens
You need a source of infrared (IR) light to use the software. Many people build their own IR pens for that purpose, usually by retrofitting some sort of marker. You’ll find all you need to know here. I started with a simple IR pen made from a battery clip.
There are also IR pens for sale if you don’t want to build one yourself. Several vendors sell different models, the IR Pen marketplace is a good place to get an overview.
You can use the coupon code uwe if you buy from IRPensOnline.com. This will give you a discount of $2 and I’ll get $1.
Compatibility
I only heard of few problems on Mac OS X, using the built-in stack. I also got reports from users who got the program running on Windows using either the Widcomm or BlueSoleil stack. It seems like Widcomm works better, see this post about BlueSoleil. You need to use the BlueZ stack on Linux, see the Wiki or this post for further instructions.
Issue on PowerPC Macs (excerpt from the WiiRemoteJ-README):
Note for Mac OS X PowerPC (PPC) users: you will have to delete the Wii Remote from your previous devices list in System Preferences->Bluetooth->Devices after each connection (every time you connect a given Wii Remote). Even then, the outgoing connection will still fail every other time. There is some sort of bug relating to HCI devices and Apple’s library. Luckily, it was fixed for the Intel Macs.
Further details can be found in the Wiki or the help files bundled with the application.
Hi,
would defenitely like to try the program but on my macbook pro it alwas ends up with the message “Bluetooth failed to initialize.There ist prob……” I can’t figuere out a solution since “DarwiiRemote”, for example, works fine….
Does anybody has a solution for this?
thanks
malte
> “it says it can’t see a bluetooth device”
I had this problem twice while trying out the various BT drivers out there.
Turned out that at times a driver wouldn’t fully uninstall and lock up the BT device.
So I would advise to go hunt for all BT related software and remove it enitrely before you try a new driver.
If yours is a USB BT device shutting it down (’safely remove’ in Wndws), unplugging it, rebooting and reinstalling it might also help.
My experience with changing the BT driver(s) is that it takes a lot of work (and reboots) to get a driver really uninstalled. Often Wndws sees the device and (secretly) reinstalls the driver you just removed.
See also my post and the link therein on Widcomm Broadcom driver installation under Vista above.
Anne.
Yesterday, I’ve installed the latest version of Ubuntu Linux and got the software to work. You need to have BlueZ installed (see detailed information), and do the following:
For example:
Uwe
Hi malte,
I won’t be able to help you unless you provide more information. Download the cross-platform version of the software and start it at the command line by typing java -Dbluecove.debug=true -jar WiimoteWhiteboard.jar
That will print lots of debug messages on the command line.
Uwe
Hallo Uwe,
it seems that somehow the bluecove libs/jars can’t be found but I have no idea why not and where this directory comes from: /private/tmp/bluecove_cambridgei_0/libbluecove.jnilib
and I don’t no why he can’t find the jnilib….
here are the debug messages:
aranea:whiteboard cambridgei$ java -Dbluecove.debug=true -jar WiimoteWhiteboard.jar(WiiRemoteJ.java:49)(WiimoteDataHandler.java:95)(WiiRemoteJ.java:49)(WiimoteDataHandler.java:95)(WiiRemoteJ.java:57)(WiimoteDataHandler.java:95)(WiiRemoteJ.java:49)
15:46:17.469 Java 1.4+ detected: 1.6.0_04-dp; Java HotSpot(TM) 64-Bit Server VM; Apple Inc.
com.intel.bluetooth.UtilsJavaSE.getLocation(UtilsJavaSE.java:84)
15:46:17.489 error Can’t load library file java.lang.UnsatisfiedLinkError: /private/tmp/bluecove_cambridgei_0/libbluecove.jnilib:
com.intel.bluetooth.NativeLibLoader.loadAsSystemResource(NativeLibLoader.java:311)
java.lang.UnsatisfiedLinkError: /private/tmp/bluecove_cambridgei_0/libbluecove.jnilib:
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1822)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1702)
at java.lang.Runtime.load0(Runtime.java:770)
at java.lang.System.load(System.java:1005)
at com.intel.bluetooth.NativeLibLoader.loadAsSystemResource(NativeLibLoader.java:308)
at com.intel.bluetooth.NativeLibLoader.isAvailable(NativeLibLoader.java:197)
at com.intel.bluetooth.BlueCoveImpl.loadNativeLibraries(BlueCoveImpl.java:382)
at com.intel.bluetooth.BlueCoveImpl.detectStack(BlueCoveImpl.java:437)
at com.intel.bluetooth.BlueCoveImpl.access$600(BlueCoveImpl.java:69)
at com.intel.bluetooth.BlueCoveImpl$1.run(BlueCoveImpl.java:970)
at java.security.AccessController.doPrivileged(Native Method)
at com.intel.bluetooth.BlueCoveImpl.detectStackPrivileged(BlueCoveImpl.java:968)
at com.intel.bluetooth.BlueCoveImpl.getBluetoothStack(BlueCoveImpl.java:961)
at javax.bluetooth.LocalDevice.getLocalDeviceInstance(LocalDevice.java:77)
at javax.bluetooth.LocalDevice.getLocalDevice(LocalDevice.java:97)
at wiiremotej.WiiRemoteJ.
at org.uweschmidt.wiimote.whiteboard.WiimoteDataHandler.
at org.uweschmidt.wiimote.whiteboard.WiimoteWhiteboard.startup(WiimoteWhiteboard.java:76)
at org.jdesktop.application.Application$1.run(Application.java:171)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:300)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:210)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:200)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:195)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:187)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)
JarClassLoader: Warning: Unable to load native library: java.lang.NullPointerException
15:46:17.499 error Library bluecove not loaded java.lang.UnsatisfiedLinkError: no bluecove in java.library.path
com.intel.bluetooth.NativeLibLoader.tryload(NativeLibLoader.java:220)
java.lang.UnsatisfiedLinkError: no bluecove in java.library.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1753)
at java.lang.Runtime.loadLibrary0(Runtime.java:823)
at java.lang.System.loadLibrary(System.java:1030)
at com.intel.bluetooth.NativeLibLoader.tryload(NativeLibLoader.java:217)
at com.intel.bluetooth.NativeLibLoader.isAvailable(NativeLibLoader.java:201)
at com.intel.bluetooth.BlueCoveImpl.loadNativeLibraries(BlueCoveImpl.java:382)
at com.intel.bluetooth.BlueCoveImpl.detectStack(BlueCoveImpl.java:437)
at com.intel.bluetooth.BlueCoveImpl.access$600(BlueCoveImpl.java:69)
at com.intel.bluetooth.BlueCoveImpl$1.run(BlueCoveImpl.java:970)
at java.security.AccessController.doPrivileged(Native Method)
at com.intel.bluetooth.BlueCoveImpl.detectStackPrivileged(BlueCoveImpl.java:968)
at com.intel.bluetooth.BlueCoveImpl.getBluetoothStack(BlueCoveImpl.java:961)
at javax.bluetooth.LocalDevice.getLocalDeviceInstance(LocalDevice.java:77)
at javax.bluetooth.LocalDevice.getLocalDevice(LocalDevice.java:97)
at wiiremotej.WiiRemoteJ.
at org.uweschmidt.wiimote.whiteboard.WiimoteDataHandler.
at org.uweschmidt.wiimote.whiteboard.WiimoteWhiteboard.startup(WiimoteWhiteboard.java:76)
at org.jdesktop.application.Application$1.run(Application.java:171)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:300)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:210)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:200)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:195)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:187)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)
Native Library bluecove not available
15:46:17.504 java.library.path .:/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java
com.intel.bluetooth.NativeLibLoader.isAvailable(NativeLibLoader.java:209)
java.lang.IllegalStateException: Bluetooth failed to initialize. There is probably a problem with your local Bluetooth stack or API.
at wiiremotej.WiiRemoteJ.
at org.uweschmidt.wiimote.whiteboard.WiimoteDataHandler.
… …
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:187)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)
Caused by: javax.bluetooth.BluetoothStateException: BlueCove library bluecove not available
at com.intel.bluetooth.BlueCoveImpl.loadNativeLibraries(BlueCoveImpl.java:383)
… ….
at javax.bluetooth.LocalDevice.getLocalDevice(LocalDevice.java:97)
at wiiremotej.WiiRemoteJ.
… 11 more
2008-06-23 15:46:17.553 java[1909:80f] Can’t cache image
maybe you can figure out the Problem now
Hi malte,
that seems to be a known issue with the Bluetooth library I use:
BlueCove does not work with Mac OS 10.5.x, Java 1.6.0 – 64 Bit
Sorry, no solution yet. Maybe you could help out by fixing the problem (details on the page)…
Uwe
Hi Uwe
I rebuilt my IR pen to be more comfortable to hold. It looks really slick now.
Then I fired up the whiteboard with one wiimote. The calibration looks cooler in the new version. But actually the accuracy seems to have degraded. Not sure if this is the new version or some other factor – since I had to replace my LED… who knows, maybe that is an issue.
Anyway, in my previous tests, using 2 wiimotes actually was more accurate. Now, something weird is happening. Using 2 wiimotes, one wiimote does not seem to recognize ANY click at all. I don’t know what’s up with that. I even placed wiimote2 in the same place as wiimote 1, and it was not recognizing clicks. (yes, it did definitely connect to bluetooth). Interestingly, the screwed up wiimote seemingly has >100% battery life. That is also kinda weird.
I don’t know what is wrong here. I hope to figure it out, but help would be great.
Also: calibration with 2 wiimotes uses more than 4 points, and with 1 wiimote uses only 4 points. I think it would better to calibrate with more points even for 1 wiimote, because then perhaps the accuracy issue would improve.
Ideas?
Daniel
Daniel,
The IR Led is an important factor in this equation.
Try to use one with tech. specs. corresponding to Vishay TSAL 5300 or TSAL6400:
http://www.vishay.com/ir-emitting-diodes/list/product-81011/
See my IR Pen:
http://clinik.net/wiimote/wiimote_info_my_pen_2.php
But in your case, I suppose in there are something more strange happening…
Cheers
Hi Uwe,
first of all, thanks you for porting the whiteboard app to mac. And I am even more thankfull
that you also included the TUIO Message option, which really helps my work on flash multitouch apps.
I work with a rear projection setup, which normally uses a camera to track the fingers (Diffused Illumination, like reactivision). The biggest drawback is that I have to work with windows, since most
tracking apps are win only. Now I can work in my “normal” osx, and develop/ test apps fast, without constantly rebooting into windows… great!
Anyway, I found a very strange bug when using my setup…
I set my laptop screen as my main screen, while the projector uses the expanded one. So during calibration I choose the external (projector) screen and calibrate succesfully. But the TUIO
messages are somehow incorrect for the x axis, which is always 1.0. The y axis works perfectly, as does the mouse function. Again, this only happens when the calibration screen is NOT set as the main screen.
Maybe you could look into it, could be an easy fix I hope
My workaround for now is to set the external screen as the main, then start your app, calibrate and while still running your app, switching the screens back again. It works, but not pretty…
thanks again for your great job!
tim
Hi Tim,
I found the bug that caused the problem and sent you an email with the bug-free version. I’ve not uploaded the updated version to this website since most users won’t encounter the bug. The fix will obviously be included in the next “regular” release. If you can’t wait till then, just tell me and I’ll be happy to send you the fixed version.
Uwe
Hi Daniel,
What do you mean by “accuracy”? Also see this previous post.
Did you try using “Reset” button several times or restarting the program?
That is indeed weird.
The calibration doesn’t work that way. Calibrating 2 Wiimotes can either take 4,6,8, or 9 points, depending on Wiimote placement (more explanations in this thread). And there are exactly 4 points needed for each Wiimote to do a perspective transformation (see this thread for more information).
Uwe
I am a technology trainer for a public school system in the Denver, CO area. I have been using,sharing,and training teachers on building and using the wiimote whiteboard for several months now. I just returned from presenting at a teachers technology conference for which I developed a site for wiimote whiteboard users to learn and share. Please visit my site at http://sites.google.com/site/wiiattie/
If you would like to collaborate on the site just let me know and I will send you an invitation.
Dave Tarwater
Hi Dave,
it is a good idea to tell teachers about the opportunity to cheaply build their own interactive whiteboard.
I don’t know what you exactly mean by “collaborate”, but I have a few suggestions:
* I like the Interactive Resources page, and I’d add the excellent Java software Jarnal.
* I’d appreciate if you don’t classify my software as Mac-only. Many people, presumably Windows-users, are downloading and using the cross-platform version as well. I also recently added instructions for Linux.
* The title “What Wii needs” is somewhat strange to me. On the page, the column Cost appears twice in the table.
Uwe
Uwe,
Thanks for all your great work, I would like to buy you a drink.
Thanks for your comments to my post, I have edited my site, http://sites.google.com/site/wiiattie/, regarding your program as Mac only and added the Java based Jarnal to the interactive resources page. Teachers and students around the world will benefit from your efforts.
Dave
Hey
Have you developed the app for headtracking .. i can’t run the desktop VR by jhonny on my MacBook, it crashes as soon as i launch it (i am using parallel windows) i was able to use your app for whiteboard easily (which seems pretty cool)
Let me know if you have the app ready
Thanks in advance
Hi Uwe
By accuracy, I mean that the position on the screen is not the same as the position of the pen. I have seen a strange accuracy problem: the mouse consistently is to the right of where I point. Now I can see how it may be because the IR camera angle matters here, but the calibration points should have canceled this issued out. I click exactly over the calibration points. If the camera angle was an issue, I should have needed to click to the side of them.
I hope there is a simple solution to the accuracy issue, because it renders the pen totally unusable in this present problem.
I tried clicking the reset button many times and restarting and removing the wiimotes from the bluetooth settings. After all that, things began to improve. Related or not, the battery life on one of my wiimotes was >100, but it began to get less and less the more testing I did. When it was around 100ish, then it started behaving more correctly.
I read the links you recommended. Those are helpful for understanding the purpose of the control points. I think what is problematic, at least in my case, is that the calibration does not seem to result in accurate mouse placement. This is true for 1 or 2 wiimotes.
What can be done?
I hope we can solve this,
Thanks
Daniel
Also, on the subject of my pen, I think it shouldn’t be a problem.
It looks nice, has an IR led that came from radioshack. It is not visible to my eye, but is visible to my digital camera. And of course, to the wiimote.
Daniel
hi uwe,
great job on developing this tool for all to use! it’s a blessing you’re spending all this effort on this project. kudos to you!
i’m a high school physics teacher and am thinking of ways to put this in the classroom and have kids interact with it. as i don’t have a wii controller, i’ve asked a couple of my students to bring theirs (voluntarily, of course). i’m downloading your software and will try it out when my kids bring in their remotes. i’m using a mac, and run windows xp through parallels. i enjoy the program, microsoft physics illustrator, which allows the user to make simple diagrams, and include conditions similar to the physical world (gravity, friction, etc) and animate their creations to see how they would actually behave… it was designed for use with tablet pcs, but a workaround was achieved that allows the program to run on regular windows pcs, using the mouse instead of the touch interface of a tablet pc. i’m excited about the idea of using physics illustrator and the wiimote together: imagine, kids can come up to the whiteboard and draw objects and with a click see how they behave following physical principles!
i want to know if anyone has tried using these together… specifically, since physics illustrator only runs on windows, i have to run it through parallels (i don’t have a bootcamp installation, but if that’s what it’s going to take, i just might do it.). if i could get my mbp to connect to the wiimote, would that connection stay when i run parallels?
again, thanks and more power to you!
cheers,
adrian (philippines)
In Windows you can change the double click sensitivity. I think TweakXP or http://www.pctools.com/guides/registry/detail/341/ can be of help.
Do you mean that you made the front tip flat instead of round? (Or in hat shape terms, more like a “top hat” than a “derby”/”bowler”?)
One idea is to have a look at the software you use to draw the diagonal / staircase lines. Some graphics programs smoothen your lines, depending on which paint-tool and settings (antialias). I know Microsoft Paint does not help with smoothing, while Photoshop surely can.
No, I just made the surface matte or milky.
Hi Dave,
thank you for “buying me a drink”. You’ve just doubled the number of donations I received
.
Uwe
Hi Ankit,
I haven’t ported the head-tracking app and I currently don’t intend to do so. See my “latest” blog post for the reason.
Uwe
Hi Daniel,
Why should the calibration points cancel this out?
That’s exactly right. When you’re calibrating a certain point, you need to “click” the IR pen at the position that will later cause the mouse cursor to be moved where the calibration point is. I hope that’s understandable…
Uwe
Hi Adrian,
As far as I understand, Parallels is just another program on your Mac that happens to emulate other operating systems. I don’t see a reason why it shouldn’t work if you don’t give control over your bluetooth device to Parallels (if that’s even possible). Maybe someone actually running Parallels can say more about that…
Uwe
I have gotten it to work in Parallels. But my situation was different.
This was back when I was trying to get Uwe’s version to work and hadn’t worked out how to fix the accuracy (restart).
I had to make sure that the VM owned my external USB BT stick by checking it in Devices.
Then I installed Widcomm drivers.
Then I ran Johnny’s version.
So it sounds like you’re doing something different than I am. I’d test it at work tomorrow, but school’s out for the summer, and I am all busy in classes for a while.
When I launch the mac version or the cross platform version I get a Bluetooth failed to initialize error. Does the wiimote need to be paired up before launching the whiteboard, or after. I have been able to get my iMac (leopard) to recognize the wiimote with bluetooth setup but it doesn’t seem to pair. I used the option “Do not use passkey” when setting up the Bluetooth device.
Uwe’s program does the pairing for you. You shouldn’t have to use OSX’s pairing at all.
Hi everybody
I have install the widcomm programm as describe here : http://www.dev-toast.com/2007/01/05/uncrippling-bluetooth-in-vista-rtm
Everything went ok.
now I try to connect my wiimote and get these messages in the wiimoteWhiteboard log :
FINE 13:06:21 WiiRemoteJ: Found Nintendo RVL-CNT-01 (001E3548CFA4)(WiiRemote.java:214) (BluetoothL2CAPClientConnection.java:33) (WiiRemote.java:214)
FINE 13:06:21 WiiRemoteJ: Nintendo RVL-CNT-01 is a WiiRemote.
INFO 13:06:22 WiiRemoteJ: btl2cap://001E3548CFA4
SEVERE 13:08:22 WiiRemoteJ: Error getting device!
java.io.IOException: WiiRemote failed to connect!
at wiiremotej.WiiRemote.construct(WiiRemote.java:301)
at wiiremotej.WiiRemote.
at wiiremotej.WiiRemoteDiscoverer.getWiiRemote(WiiRemoteDiscoverer.java:94)
at wiiremotej.WiiRemoteJ.findRemote(WiiRemoteJ.java:208)
at wiiremotej.WiiRemoteJ.access$100(WiiRemoteJ.java:22)
at wiiremotej.WiiRemoteJ$2.run(WiiRemoteJ.java:284)
at java.lang.Thread.run(Unknown Source)
Caused by: javax.bluetooth.BluetoothConnectionException: Connection timeout
at com.intel.bluetooth.BluetoothStackWIDCOMM.l2OpenClientConnectionImpl(Native Method)
at com.intel.bluetooth.BluetoothStackWIDCOMM.l2OpenClientConnection(BluetoothStackWIDCOMM.java:796)
at com.intel.bluetooth.BluetoothL2CAPClientConnection.
at com.intel.bluetooth.MicroeditionConnector.openImpl(MicroeditionConnector.java:401)
at com.intel.bluetooth.MicroeditionConnector.open(MicroeditionConnector.java:510)
at javax.microedition.io.Connector.open(Connector.java:95)
at wiiremotej.WiiRemote.construct(WiiRemote.java:295)
… 6 more
FINE 13:08:26 WiiRemoteJ: Found Nintendo RVL-CNT-01 (001E3548CFA4)
FINE 13:08:26 WiiRemoteJ: Nintendo RVL-CNT-01 is a WiiRemote.
INFO 13:08:27 WiiRemoteJ: btl2cap://001E3548CFA4
SEVERE 13:08:27 WiiRemoteJ: Error getting device!
java.lang.IllegalStateException: cannot open system clipboard
at sun.awt.windows.WClipboard.openClipboard(Native Method)
at sun.awt.datatransfer.SunClipboard.getClipboardFormatsOpenClose(Unknown Source)
at sun.awt.datatransfer.SunClipboard.isDataFlavorAvailable(Unknown Source)
at org.jdesktop.application.TextActions.updateTextActions(TextActions.java:132)
at org.jdesktop.application.TextActions.access$400(TextActions.java:47)
at org.jdesktop.application.TextActions$TextComponentCaretListener.caretUpdate(TextActions.java:115)
at javax.swing.text.JTextComponent.fireCaretUpdate(Unknown Source)
at javax.swing.text.JTextComponent$MutableCaretEvent.fire(Unknown Source)
at javax.swing.text.JTextComponent$MutableCaretEvent.stateChanged(Unknown Source)
at javax.swing.text.DefaultCaret.fireStateChanged(Unknown Source)
at javax.swing.text.DefaultCaret.changeCaretPosition(Unknown Source)
at javax.swing.text.DefaultCaret.handleSetDot(Unknown Source)
at javax.swing.text.DefaultCaret.setDot(Unknown Source)
at javax.swing.text.DefaultCaret.setDot(Unknown Source)
at javax.swing.text.JTextComponent.setCaretPosition(Unknown Source)
at org.uweschmidt.wiimote.whiteboard.gui.LogWindow$LogHandler.publish(LogWindow.java:101)
at java.util.logging.Logger.log(Unknown Source)
at java.util.logging.Logger.doLog(Unknown Source)
at java.util.logging.Logger.log(Unknown Source)
at java.util.logging.Logger.info(Unknown Source)
at wiiremotej.WiiRemote.construct(WiiRemote.java:294)
at wiiremotej.WiiRemote.
at wiiremotej.WiiRemoteDiscoverer.getWiiRemote(WiiRemoteDiscoverer.java:94)
at wiiremotej.WiiRemoteJ.findRemote(WiiRemoteJ.java:208)
at wiiremotej.WiiRemoteJ.access$100(WiiRemoteJ.java:22)
at wiiremotej.WiiRemoteJ$2.run(WiiRemoteJ.java:284)
at java.lang.Thread.run(Unknown Source)
WARNING 13:08:27 WiiRemoteJ: Error finding remotes.
java.lang.IllegalStateException: cannot open system clipboard
at sun.awt.windows.WClipboard.openClipboard(Native Method)
at sun.awt.datatransfer.SunClipboard.getClipboardFormatsOpenClose(Unknown Source)
at sun.awt.datatransfer.SunClipboard.isDataFlavorAvailable(Unknown Source)
at org.jdesktop.application.TextActions.updateTextActions(TextActions.java:132)
at org.jdesktop.application.TextActions.access$400(TextActions.java:47)
at org.jdesktop.application.TextActions$TextComponentCaretListener.caretUpdate(TextActions.java:115)
at javax.swing.text.JTextComponent.fireCaretUpdate(Unknown Source)
at javax.swing.text.JTextComponent$MutableCaretEvent.fire(Unknown Source)
at javax.swing.text.JTextComponent$MutableCaretEvent.stateChanged(Unknown Source)
at javax.swing.text.DefaultCaret.fireStateChanged(Unknown Source)
at javax.swing.text.DefaultCaret.changeCaretPosition(Unknown Source)
at javax.swing.text.DefaultCaret.handleSetDot(Unknown Source)
at javax.swing.text.DefaultCaret.setDot(Unknown Source)
at javax.swing.text.DefaultCaret.setDot(Unknown Source)
at javax.swing.text.JTextComponent.setCaretPosition(Unknown Source)
at org.uweschmidt.wiimote.whiteboard.gui.LogWindow$LogHandler.publish(LogWindow.java:101)
at java.util.logging.Logger.log(Unknown Source)
at java.util.logging.Logger.doLog(Unknown Source)
at java.util.logging.Logger.log(Unknown Source)
at wiiremotej.WiiRemoteDiscoverer.getWiiRemote(WiiRemoteDiscoverer.java:100)
at wiiremotej.WiiRemoteJ.findRemote(WiiRemoteJ.java:208)
at wiiremotej.WiiRemoteJ.access$100(WiiRemoteJ.java:22)
at wiiremotej.WiiRemoteJ$2.run(WiiRemoteJ.java:284)
at java.lang.Thread.run(Unknown Source)
I have the four leds of the remote lighting. What did I do wrong ? What should I do ?
I run vista 32 bits on a toshiba P200.
Thanks for your help
Pascal