Sponsors of Wiimoteproject.com
IR Pens for Wiimote Whiteboard
Wiimote Project†Ľ†Wiimote Projects†Ľ†Wiimote Interactive Whiteboard†Ľ†Wiimote Java Whiteboard†Ľ†Cannot calibrate, camera view seems wrong.
Pages: [1] 2
Print
Author Topic: Cannot calibrate, camera view seems wrong.  (Read 7348 times)
0 Members and 1 Guest are viewing this topic.
*
Karma: +0/-0
Posts: 8
Offline Offline
View Profile
« on: February 26, 2011, 10:00:31 PM »

Running Mac OS X 10.6.4, and using the .dmg packaged version of WiimoteWhiteboard.

The wiimote connects fine to the application, but I cannot calibrate.  When I use my IR pen, the program reports Visible Dots 2 and 3 visible, but they do not show up anywhere in the IR Camera Monitor.  If I move the pen to a certain place (which appears to be well within the wiimote's visible area), I can get Visible Dot 2 to appear on the top border of the Camera Monitor area, but moving the pen around makes the dot disappear.  As if the Camera Monitor area only shows a part of what my Wiimote is actually seeing.

Judging by where on my projection screen I can get Visible Dots 2 and 3 active, I have an idea of where on my projection screen the wiimote can see, but this has absolutely no correlation to the Camera Monitor's interpretation.  If I try to calibrate, nothing happens no matter where I point with the pen.

Has anybody else had this problem, or would anyone know what might be the issue here?  Is it possible that the bluetooth communication isn't going through right?  And out of curiosity, why might it be seeing dots 2 and 3, but not 1?
Logged
*
Karma: +0/-0
Posts: 8
Offline Offline
View Profile
« Reply #1 on: March 01, 2011, 03:23:31 AM »

I've been working with this a bit over the weekend, and I noticed a couple new things.  No matter what batteries I have in the Wiimote, the software always reports the battery level as 56%.  Also clicking the Reset button makes Visible light 1 active, which shows up in the Camera Monitor on the very top border, a little bit from the right corner.  This happens no matter where the Wiimote is and even if it is moved. 

This leads me to think that this is a communication problem between software and Wiimote.  Maybe I have an older model of Wiimote that doesn't work with the WiimoteWhiteboard software?  Or maybe the Mac OS default bluetooth stack isn't compatible?  This is a MacBook with a Cambrige Silicon Radio internal bluetooth card (not sure if that's relevant info). 

By the way, I've tried the .jar version of the software and it won't start up.  All I get is a box that says, "Bluetooth failed to initialize. There is probably a problem with your Bluetooth stack or API," and a window with a Java exception trace, but I can't select any text to copy or scroll to the top to read it.

I'm trying different ideas to hopefully get this working, including looking for alternative software, but no luck yet.  Any ideas for troubleshooting or other Mac OS software would be much appreciated.
Logged
*
Karma: +0/-0
Posts: 9
Offline Offline
View Profile
« Reply #2 on: March 17, 2011, 01:54:45 PM »

Hey there,


I have exactly the same issue.  Battery life 56%.  
IR dots visible, 2 and 3 flashes and sometimes 4 will join the party.  
Go to calibrate, nothing...very frustrated.  I bought the TSAL 7400 IR leds on ebay (only 4 bucks) and they do the same thing as the cheap ones I got on the street (I am in Hong Kong).  

Is this a software problem?  Should I give up?  Input would be appreciated.

Here are my specs:
Using a Mac book Pro
OS X 10.6.6
Done all my updates. 

Thanks
Jason
« Last Edit: March 17, 2011, 03:16:55 PM by Jdubya » Logged
*
Karma: +0/-0
Posts: 9
Offline Offline
View Profile
« Reply #3 on: March 18, 2011, 08:09:41 AM »

This is the what the log is producing if it helps diagnose the problem:

 SEVERE     13:07:14  WiiRemoteJ: Error discovering device.
java.io.IOException: The remote device can not be contacted
   at com.intel.bluetooth.BluetoothStackOSX.getRemoteDeviceFriendlyName(Native Method)
   at com.intel.bluetooth.RemoteDeviceHelper.getFriendlyName(RemoteDeviceHelper.java:400)
   at javax.bluetooth.RemoteDevice.getFriendlyName(RemoteDevice.java:130)
   at wiiremotej.WiiDeviceDiscoverer.deviceDiscovered(WiiDeviceDiscoverer.java:63)
   at com.intel.bluetooth.BluetoothStackOSX$1.deviceDiscoveredCallback(BluetoothStackOSX.java:390)
   at com.intel.bluetooth.BluetoothStackOSX.runDeviceInquiryImpl(Native Method)
   at com.intel.bluetooth.BluetoothStackOSX.access$200(BluetoothStackOSX.java:44)
   at com.intel.bluetooth.BluetoothStackOSX$1.runDeviceInquiry(BluetoothStackOSX.java:368)
   at com.intel.bluetooth.DeviceInquiryThread.run(DeviceInquiryThread.java:103)
   FINE     13:07:14  WiiRemoteJ: Found admin MacBook (58B03586C006)
   FINE     13:07:14  WiiRemoteJ: admin MacBook is NOT a known device.
   FINE     13:07:14  WiiRemoteJ: Found adminís MacBook (60334B06940E)
   FINE     13:07:14  WiiRemoteJ: adminís MacBook is NOT a known device.
   FINE     13:07:14  WiiRemoteJ: Found admin MacBook (9027E4F9EC60)
   FINE     13:07:14  WiiRemoteJ: admin MacBook is NOT a known device.
   FINE     13:07:14  WiiRemoteJ: Found Nintendo RVL-CNT-01 (005A1A424E31)
   FINE     13:07:14  WiiRemoteJ: Nintendo RVL-CNT-01 is a Wii Remote.
   INFO     13:07:15  WiiRemoteJ: btl2cap://005A1A424E31
  FINER     13:07:16  WiiRemoteJ: Initial connection complete.
  FINER     13:07:17  WiiRemoteJ: Calibrating accelerometer...
  FINER     13:07:17  WiiRemoteJ: Accelerometer successfully calibrated
  FINER     13:07:17  WiiRemoteJ: Initialization complete.
 FINEST     13:07:18  WiiRemoteJ: Data write finished.
 FINEST     13:07:18  WiiRemoteJ: Data write finished.
 FINEST     13:07:18  WiiRemoteJ: Data write finished.
 FINEST     13:07:18  WiiRemoteJ: Data write finished.
 FINEST     13:07:19  WiiRemoteJ: Data write finished.
 FINEST     13:07:19  WiiRemoteJ: Data write finished.
 FINEST     13:07:19  WiiRemoteJ: Data write finished.
   FINE     13:07:24  WiiRemoteJ: Found admin MacBook (9027E4F9EC60)
   FINE     13:07:24  WiiRemoteJ: admin MacBook is NOT a known device.
   FINE     13:07:49  WiiRemoteJ: Found adminís MacBook (60334B06940E)

and this is my specs

Hardware Overview:

  Model Name:   MacBook Pro
  Model Identifier:   MacBookPro5,5
  Processor Name:   Intel Core 2 Duo
 
« Last Edit: March 18, 2011, 08:14:35 AM by Jdubya » Logged
*
Karma: +0/-0
Posts: 8
Offline Offline
View Profile
« Reply #4 on: March 19, 2011, 09:38:07 PM »

The one I've got is
MacBook
MacBook3,1
running 10.6.4.  I'm helping someone else try to set up this whole whiteboard deal, so it's not my computer, and I don't often get a chance to fiddle around with this.

We built a pen ourselves with a 100mA, 940nm led from RadioShack, but the led's aren't the problem here.  The only thing left would be a problem with the Bluetooth stack on Mac OS X 10.6.  Or at least an incompatibility with Uwe's software and the Mac OS bluetooth stack.  Still looking into that though.  We've tried using our Wiimote with an actual Wii, just to be sure that it isn't faulty.  It works fine.
Logged
*
Karma: +0/-0
Posts: 9
Offline Offline
View Profile
« Reply #5 on: March 20, 2011, 05:05:09 AM »

Hey Tim,

I am pretty sure my LEDs are not the problem either...and my Wii remote should be legit, I will check with another Wii remote but I really doubt there will be any difference.  I agree that it is some kind of communication problem between the Wiimote and the mac.
I will update here if I find anything that helps. 

J
Logged
*
Karma: +0/-0
Posts: 8
Offline Offline
View Profile
« Reply #6 on: March 20, 2011, 11:29:06 PM »

This software uses the bluecove library to do its bluetooth communication.  I wonder if there is a problem between bluecove and the Mac OS X bluetooth stack.  I get this weird behavior (IR lights 2 and 3, 56% battery) from the .dmg package of Uwe's program, but the .jar version doesn't run at all.  Running  "java -Dbluecove.debug=true -jar WiimoteWhiteboard.jar" in the terminal produces the following (emphasis added to what I think is interesting):

15:12:15.378 Java 1.4+ detected: 1.6.0_20; Java HotSpot(TM) 64-Bit Server VM; Apple Inc.
     com.intel.bluetooth.UtilsJavaSE.getLocation(UtilsJavaSE.java:123)
15:12:15.391 Use stack ClassLoader
     com.intel.bluetooth.NativeLibLoader.loadAsSystemResource(NativeLibLoader.java:272)
15:12:15.420 error Can't load library file  java.lang.UnsatisfiedLinkError: /private/var/folders/vf/vfPNaSzYHE4kVvZC+STfY4uqqNY/-Tmp-/bluecove_e030658_0/libbluecove.jnilib:  no suitable image found.  Did find:  /private/var/folders/vf/vfPNaSzYHE4kVvZC+STfY4uqqNY/-Tmp-/bluecove_e030658_0/libbluecove.jnilib: no matching architecture in universal wrapper
     com.intel.bluetooth.NativeLibLoader.loadAsSystemResource(NativeLibLoader.java:314)
java.lang.UnsatisfiedLinkError: /private/var/folders/vf/vfPNaSzYHE4kVvZC+STfY4uqqNY/-Tmp-/bluecove_e030658_0/libbluecove.jnilib:  no suitable image found.  Did find:  /private/var/folders/vf/vfPNaSzYHE4kVvZC+STfY4uqqNY/-Tmp-/bluecove_e030658_0/libbluecove.jnilib: no matching architecture in universal wrapper
   at java.lang.ClassLoader$NativeLibrary.load(Native Method)
   at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1823)
   at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1699)
   at java.lang.Runtime.load0(Runtime.java:770)
   at java.lang.System.load(System.java:1020)
   at com.intel.bluetooth.NativeLibLoader.loadAsSystemResource(NativeLibLoader.java:311)
   at com.intel.bluetooth.NativeLibLoader.isAvailable(NativeLibLoader.java:198)
   at com.intel.bluetooth.BlueCoveImpl.loadNativeLibraries(BlueCoveImpl.java:380)
   at com.intel.bluetooth.BlueCoveImpl.detectStack(BlueCoveImpl.java:434)
   at com.intel.bluetooth.BlueCoveImpl.access$500(BlueCoveImpl.java:65)
   at com.intel.bluetooth.BlueCoveImpl$1.run(BlueCoveImpl.java:1020)
   at java.security.AccessController.doPrivileged(Native Method)
   at com.intel.bluetooth.BlueCoveImpl.detectStackPrivileged(BlueCoveImpl.java:1018)
   at com.intel.bluetooth.BlueCoveImpl.getBluetoothStack(BlueCoveImpl.java:1011)
   at javax.bluetooth.LocalDevice.getLocalDeviceInstance(LocalDevice.java:75)
   at javax.bluetooth.LocalDevice.getLocalDevice(LocalDevice.java:95)
   at wiiremotej.WiiRemoteJ.<clinit>(WiiRemoteJ.java:67)
   at org.uweschmidt.wiimote.whiteboard.WiimoteConnector.connect(WiimoteConnector.java:48)
   at org.uweschmidt.wiimote.whiteboard.WiimoteDataHandler.<init>(WiimoteDataHandler.java:84)
   at org.uweschmidt.wiimote.whiteboard.WiimoteWhiteboard.startup(WiimoteWhiteboard.java:99)
   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:633)
   at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:296)
   at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:211)
   at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:201)
   at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:196)
   at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:188)
   at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
JarClassLoader: Warning: Unable to load native library: java.lang.NullPointerException
15:12:15.735 error Library bluecove not loaded  java.lang.UnsatisfiedLinkError: no bluecove in java.library.path

     com.intel.bluetooth.NativeLibLoader.tryload(NativeLibLoader.java:221)
java.lang.UnsatisfiedLinkError: no bluecove in java.library.path
   at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1754)
   at java.lang.Runtime.loadLibrary0(Runtime.java:823)
   at java.lang.System.loadLibrary(System.java:1045)
   at com.intel.bluetooth.NativeLibLoader.tryload(NativeLibLoader.java:218)
   at com.intel.bluetooth.NativeLibLoader.isAvailable(NativeLibLoader.java:202)
   at com.intel.bluetooth.BlueCoveImpl.loadNativeLibraries(BlueCoveImpl.java:380)
   at com.intel.bluetooth.BlueCoveImpl.detectStack(BlueCoveImpl.java:434)
   at com.intel.bluetooth.BlueCoveImpl.access$500(BlueCoveImpl.java:65)
   at com.intel.bluetooth.BlueCoveImpl$1.run(BlueCoveImpl.java:1020)
   at java.security.AccessController.doPrivileged(Native Method)
   at com.intel.bluetooth.BlueCoveImpl.detectStackPrivileged(BlueCoveImpl.java:1018)
   at com.intel.bluetooth.BlueCoveImpl.getBluetoothStack(BlueCoveImpl.java:1011)
   at javax.bluetooth.LocalDevice.getLocalDeviceInstance(LocalDevice.java:75)
   at javax.bluetooth.LocalDevice.getLocalDevice(LocalDevice.java:95)
   at wiiremotej.WiiRemoteJ.<clinit>(WiiRemoteJ.java:67)
   at org.uweschmidt.wiimote.whiteboard.WiimoteConnector.connect(WiimoteConnector.java:48)
   at org.uweschmidt.wiimote.whiteboard.WiimoteDataHandler.<init>(WiimoteDataHandler.java:84)
   at org.uweschmidt.wiimote.whiteboard.WiimoteWhiteboard.startup(WiimoteWhiteboard.java:99)
   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:633)
   at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:296)
   at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:211)
   at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:201)
   at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:196)
   at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:188)
   at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
Native Library bluecove not available
15:12:15.738 java.library.path .:/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java

     com.intel.bluetooth.NativeLibLoader.isAvailable(NativeLibLoader.java:210)
java.lang.IllegalStateException: Bluetooth failed to initialize. There is probably a problem with your local Bluetooth stack or API.
   at wiiremotej.WiiRemoteJ.<clinit>(WiiRemoteJ.java:74)
   at org.uweschmidt.wiimote.whiteboard.WiimoteConnector.connect(WiimoteConnector.java:48)
   at org.uweschmidt.wiimote.whiteboard.WiimoteDataHandler.<init>(WiimoteDataHandler.java:84)
   at org.uweschmidt.wiimote.whiteboard.WiimoteWhiteboard.startup(WiimoteWhiteboard.java:99)
   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:633)
   at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:296)
   at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:211)
   at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:201)
   at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:196)
   at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:188)
   at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
Caused by: javax.bluetooth.BluetoothStateException: BlueCove library bluecove not available
   at com.intel.bluetooth.BlueCoveImpl.loadNativeLibraries(BlueCoveImpl.java:381)
   at com.intel.bluetooth.BlueCoveImpl.detectStack(BlueCoveImpl.java:434)
   at com.intel.bluetooth.BlueCoveImpl.access$500(BlueCoveImpl.java:65)
   at com.intel.bluetooth.BlueCoveImpl$1.run(BlueCoveImpl.java:1020)
   at java.security.AccessController.doPrivileged(Native Method)
   at com.intel.bluetooth.BlueCoveImpl.detectStackPrivileged(BlueCoveImpl.java:1018)
   at com.intel.bluetooth.BlueCoveImpl.getBluetoothStack(BlueCoveImpl.java:1011)
   at javax.bluetooth.LocalDevice.getLocalDeviceInstance(LocalDevice.java:75)
   at javax.bluetooth.LocalDevice.getLocalDevice(LocalDevice.java:95)
   at wiiremotej.WiiRemoteJ.<clinit>(WiiRemoteJ.java:67)
   ... 12 more

I know almost nothing about what is supposed to be going on, but this makes me wonder if the wrong version of bluecove is packaged in the software, or if our hardware/OS is incompatible with the bluecove version in WiimoteWhiteboard.  But if so, why does the .dmg version of WiimoteWhiteboard run at all?  Maybe there's a way to install bluecove libraries locally for the program to use?  I'll keep looking, but this is all I've got so far.
Logged
*
Karma: +0/-0
Posts: 9
Offline Offline
View Profile
« Reply #7 on: March 21, 2011, 02:10:21 AM »

Yeah, this is beyond my expertise (and I aint no expert).  I was hoping the real expertise would chime in any time now.  But its good to see someone dealing with the same thing.  If I come across anything I will let you know...but it looks like you are further along than I am. 
Logged
*
Karma: +0/-0
Posts: 8
Offline Offline
View Profile
« Reply #8 on: March 21, 2011, 05:03:21 AM »

Hey Jdubya,

Here's something new I just found.  This issue may have nothing to do with bluetooth communication at all.  We might have fake wiimotes.

There is an old thread on this site, last replied to in early 2010, that mentions fake wiimotes that work with Wii consoles but have substandard IR performance.  http://www.wiimoteproject.com/annoucements/fake-wimotes-be-warned/ .  The thread also links to another forum, http://forum.lowyat.net/topic/939583 , that has some more info. 

The wiimote I've got has a number of characteristics that match the alleged "fake" ones.  We got it off of amazon.com, a friend tried it with their Wii and it worked, and it has the Nintendo and Wii logos on it.  But since I never had a Wii or an actual Nintendo-manufactured remote, I had no way of knowing what's real and what isn't.  So I'm not 100% sure at this point, but I strongly suspect that I have an illegitimate remote.

Where did you get your wiimote?  Does yours look like one of the fake ones?  If so, that would explain why we have a problem that doesn't seem to have happened to anybody else (as far as my searching around has shown so far).
Logged
*
Karma: +0/-0
Posts: 9
Offline Offline
View Profile
« Reply #9 on: March 21, 2011, 11:08:30 AM »

Hey Tim


I had a sinking feeling about that too.  I bought mine here in HK in a local shop..it looks very much legit...but I borrowed a student's wii mote and I will try it tonite and report to you what happened, I hope to come back with good news.  Even if its fake, at least we would know what is the problem. 

I will report back.

Jason
Logged
*
Karma: +0/-0
Posts: 9
Offline Offline
View Profile
« Reply #10 on: March 21, 2011, 11:12:49 AM »

Okay Tim,

I just wiped out my student's wiimote and linked it to the mac pro...
It says 70% battery life..................so it looks like we have been cheated.  This really sucks but at least there is some conclusion...sigh...I am going to go home and try this remote and if I can calibrate then we have our problem solved. 
I was also on to this, just nice to get a little confirmation from you and then test it.

Stay tuned.

Jason
Logged
*
Karma: +0/-0
Posts: 9
Offline Offline
View Profile
« Reply #11 on: March 21, 2011, 04:47:13 PM »

Hey Tim


We got fake remotes.  
Logged
*
Karma: +0/-0
Posts: 9
Offline Offline
View Profile
« Reply #12 on: March 21, 2011, 06:53:38 PM »

Okay here is the conclusion: the Java App ujs wrote is fine.  If you have any of the symptoms described by Tim, 56% batter, LED 23 flashing, IR field flashing when you pop it up, not being able to calibrate...you got a fake Wiimote despite the fancy box, japanese writing on the remote etc etc. 

I just borrowed my students Wiimote and everything works perfect.  You should get the LEDs with the correct wave length since only the vistay 7400 worked on mine.

So Tim, thanks for your encouragement to try the Real remote, I had it in my classroom all day, and it wasn't until you brought it up again that I felt the urge to test it.  Hope you get the same results as I did. 
Logged
*
Karma: +0/-0
Posts: 9
Offline Offline
View Profile
« Reply #13 on: March 22, 2011, 02:03:36 AM »

Additional information (looks like this thread have attracted more readers by the day):

signs of a fake controller:
The A button, under the plastic, there is imperfection in the way it is manufactured.  The real WiiMote A button is crystal clear, fake, looks bubbly under the clear plastic.
The IR filter in the front, the fake has two sharp corners on the top corners, the real one is smooth on all for corners. 
The power button, the colour is slightly off and the print is a little off center.
The plastic on the WiiMote is slightly off...what do I mean?  The shiny white plastic on the top of the controller does not have the same white consistancy, it is not as smooth as the real one.  The bottom, is a more matte white, fake looks cheaper.

It is really really hard to tell if you only have one wii mote by itself.  But upon careful imspection, next to a real one, the fake will undoubtely show its true colour. 

Hope this helps everyone out there.
Logged
*
Karma: +0/-0
Posts: 8
Offline Offline
View Profile
« Reply #14 on: March 22, 2011, 02:42:53 AM »

Glad to finally know what the problem is.  Thanks Jason for letting me know that everything works for you with a real Wiimote.  I still have to go buy a real one myself, but I'm sure I'll have good results once I do.

I only have one wiimote, so I don't have anything to compare it with.  I never would have suspected anything but for the two forum threads I mentioned in an earlier post.  I've contacted Nintendo to see if they have any further info on recognizing counterfeit wiimotes, but I haven't heard anything useful yet.

Thanks for your help Jason.  I'll post back once I get a real wiimote.
Logged
Pages: [1] 2
Print
Jump to:  

Clicky Web Analytics