Recent Changes - Search:

Wiimote Whiteboard

PmWiki

Troubleshooting

WiimoteWhiteboard.Troubleshooting History

Show minor edits - Show changes to markup

January 22, 2012, at 07:50 PM by Uwe -
Added line 1:

(:nogroupfooter:)

January 22, 2012, at 07:45 PM by Uwe -
Changed line 1 from:

Moved to a place that nobody can find lol, good luck trying to solve your problems now! HAHA.

to:

Moved to FAQ.

July 29, 2011, at 06:58 AM by John Smith -
July 29, 2011, at 06:58 AM by John Smith -
Changed line 1 from:

Moved to the place that nobody can find lol, good luck trying to solve your problems now! HAHA.

to:

Moved to a place that nobody can find lol, good luck trying to solve your problems now! HAHA.

July 29, 2011, at 06:56 AM by John Smith -
July 29, 2011, at 06:56 AM by John Smith -
Changed line 1 from:

Moved to FAQ.

to:

Moved to the place that nobody can find lol, good luck trying to solve your problems now! HAHA.

April 24, 2011, at 11:31 PM by Uwe -
Changed line 1 from:

Moved to FAQ.

to:

Moved to FAQ.

April 24, 2011, at 11:30 PM by Uwe -
Changed lines 1-73 from:

(:if userlang en:) (:title Troubleshooting:)

Linux

To use the program on Linux you need to download an additional GPL'd library yourself: bluecove-gpl. I can't distribute this library with my software for legal reasons (as far as I understand).
The procedure is explained in detail in this post, the only change is that you can now download the final release bluecove-gpl-2.1.0 instead of a 2.0.3 snapshot.

User note: even after following the instructions linked above, I still had problems getting this to run on an Asus Eee PC running Ubuntu 10.04 (Lucid). I received the following errors when running in debug mode (java -Dbluecove.debug=true -jar WiimoteWhiteboard.jar):

13:22:30.901 error Can't load library file java.lang.UnsatisfiedLinkError: /tmp/bluecove_james_0/libbluecove.so: libbluetooth.so: cannot open shared object file: No such file or directory

com.intel.bluetooth.NativeLibLoader.loadAsSystemResource(NativeLibLoader.java:314) java.lang.UnsatisfiedLinkError: /tmp/bluecove_james_0/libbluecove.so: libbluetooth.so: cannot open shared object file: No such file or directory

Aug 4, 2010 1:22:31 PM org.uweschmidt.wiimote.whiteboard.WiimoteWhiteboard startup

SEVERE: Error on startup

java.lang.IllegalStateException: Bluetooth failed to initialize. There is probably a problem with your local Bluetooth stack or API.

I found that I had to create a symbolic link as follows:

sudo ln -s /usr/lib/libbluetooth.so.3.5.0 /usr/lib/libbluetooth.so

Log

You can check the Log for error messages (accessible via Help → Log) which can be really helpful if you run into problems. Please do always include relevant output from the Log when reporting about problems.

IR Sensitivity

In case

  • the Wiimote can't see your IR pen at all or only at short distance.
  • you experience jagged and broken lines when moving the mouse or drawing.

Press the "Reset" button to re-initialize the Wiimote's IR camera; it sometimes solves the above problems. If you have consistent problems it may be an issue with your IR pen (e.g. not bright enough). It has also been reported that the IR sensitivity seems to be generally worse when running on Windows.

You may also use the IR Camera Monitor or have a look at the Calibration Details to find a better position for the Wiimote(s).

Bluetooth

The programs relies on the Bluetooth library BlueCove. You can find a list of BlueCove-compatible Bluetooth stacks here.

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. Check out this post if you're using Windows Vista. Linux users should use the BlueZ stack.

The program sometimes crashes at startup due to Bluetooth errors. It may also happen at startup that the Wiimote is found but no IR data is received (check "Visible IR dots"). Whenever this happens, try the "Reset" button, connect again or simply restart the program. Once the program was working, I never had any problems later on (like lost connections).

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."

Source Code

If you get an error that the class JaiI18N couldn't be found then you don't have Java Advanced Imaging installed. JaiI18N is actually only required to compile the software. The easiest way to fix the problem is to install Java Advanced Imaging.

TUIO/OSC (Multi-touch)

Regarding Flash multi-touch apps: I had some difficulties with the latest version of flosc, but success with the version included here. Also make sure that you add the Flash apps you want to run in the browser to the list of trustworthy locations.

Startup Time

In case it takes really long for the software to start up, the included update check might be the problem. To turn it off, simply disable Check for updates on startup under the General tab in the preferences.

(:ifend:)

to:

Moved to FAQ.

August 04, 2010, at 09:45 PM by James Brown - notes on fixing Ubuntu problem w/ libbluetooth.so not found
Added lines 9-24:

User note: even after following the instructions linked above, I still had problems getting this to run on an Asus Eee PC running Ubuntu 10.04 (Lucid). I received the following errors when running in debug mode (java -Dbluecove.debug=true -jar WiimoteWhiteboard.jar):

13:22:30.901 error Can't load library file java.lang.UnsatisfiedLinkError: /tmp/bluecove_james_0/libbluecove.so: libbluetooth.so: cannot open shared object file: No such file or directory

com.intel.bluetooth.NativeLibLoader.loadAsSystemResource(NativeLibLoader.java:314) java.lang.UnsatisfiedLinkError: /tmp/bluecove_james_0/libbluecove.so: libbluetooth.so: cannot open shared object file: No such file or directory

Aug 4, 2010 1:22:31 PM org.uweschmidt.wiimote.whiteboard.WiimoteWhiteboard startup

SEVERE: Error on startup

java.lang.IllegalStateException: Bluetooth failed to initialize. There is probably a problem with your local Bluetooth stack or API.

I found that I had to create a symbolic link as follows:

sudo ln -s /usr/lib/libbluetooth.so.3.5.0 /usr/lib/libbluetooth.so
August 20, 2009, at 10:13 PM by Uwe -
Changed line 8 from:

The procedure is explained in detail in this post, the only change is that you can now download the final release bluecove-gpl-2.0.3 instead of a snapshot.

to:

The procedure is explained in detail in this post, the only change is that you can now download the final release bluecove-gpl-2.1.0 instead of a 2.0.3 snapshot.

October 22, 2008, at 12:05 AM by Uwe -
Added line 1:

(:if userlang en:)

Added lines 56-57:

(:ifend:)

October 17, 2008, at 02:52 AM by Uwe -
Changed lines 44-54 from:

If you get an error that the class JaiI18N couldn't be found then you don't have Java Advanced Imaging installed. JaiI18N is actually only required to compile the software. The easiest way to fix the problem is to install Java Advanced Imaging.

to:

If you get an error that the class JaiI18N couldn't be found then you don't have Java Advanced Imaging installed. JaiI18N is actually only required to compile the software. The easiest way to fix the problem is to install Java Advanced Imaging.

TUIO/OSC (Multi-touch)

Regarding Flash multi-touch apps: I had some difficulties with the latest version of flosc, but success with the version included here. Also make sure that you add the Flash apps you want to run in the browser to the list of trustworthy locations.

Startup Time

In case it takes really long for the software to start up, the included update check might be the problem. To turn it off, simply disable Check for updates on startup under the General tab in the preferences.

October 16, 2008, at 12:18 AM by Uwe -
Added lines 1-44:

(:title Troubleshooting:)

Linux

To use the program on Linux you need to download an additional GPL'd library yourself: bluecove-gpl. I can't distribute this library with my software for legal reasons (as far as I understand).
The procedure is explained in detail in this post, the only change is that you can now download the final release bluecove-gpl-2.0.3 instead of a snapshot.

Log

You can check the Log for error messages (accessible via Help → Log) which can be really helpful if you run into problems. Please do always include relevant output from the Log when reporting about problems.

IR Sensitivity

In case

  • the Wiimote can't see your IR pen at all or only at short distance.
  • you experience jagged and broken lines when moving the mouse or drawing.

Press the "Reset" button to re-initialize the Wiimote's IR camera; it sometimes solves the above problems. If you have consistent problems it may be an issue with your IR pen (e.g. not bright enough). It has also been reported that the IR sensitivity seems to be generally worse when running on Windows.

You may also use the IR Camera Monitor or have a look at the Calibration Details to find a better position for the Wiimote(s).

Bluetooth

The programs relies on the Bluetooth library BlueCove. You can find a list of BlueCove-compatible Bluetooth stacks here.

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. Check out this post if you're using Windows Vista. Linux users should use the BlueZ stack.

The program sometimes crashes at startup due to Bluetooth errors. It may also happen at startup that the Wiimote is found but no IR data is received (check "Visible IR dots"). Whenever this happens, try the "Reset" button, connect again or simply restart the program. Once the program was working, I never had any problems later on (like lost connections).

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."

Source Code

If you get an error that the class JaiI18N couldn't be found then you don't have Java Advanced Imaging installed. JaiI18N is actually only required to compile the software. The easiest way to fix the problem is to install Java Advanced Imaging.

HomeSearchRecent Changes | EditHistoryPrint
Some rights reserved — Page last modified on January 22, 2012, at 07:50 PM