Masayuki Akamatsu

http://www.iamas.ac.jp/~aka/max/#aka_wiiremote

I don't make a windows version because I have no experience on Windows.

But I published my source code at the same URL.

I updated aka.wiiremote.
- Connection/disconnection improved
- IR sensor support
- Status inquiry support
- Better help patch
http://www.iamas.ac.jp/~aka/max/#aka_wiiremote

Thanks comments to the previous version.
I don't make a windows version because I have no experience on Windows.
But I published my source code at the same URL.
I hope someone would port it to windows.

nintendo-wii-remote-object-updated

I'm just doing something quick with GlovePIE on windows at the moment but hopefully I'll get a chance to look at your code soon.

Wonderful. This was exactly what I was looking for this morning, after spending some time last night trying to understand Kimora Hiroaki's library (difficult, because I don't know obj-C).

The only odd behavior I did see is that the vibration output compared to Hiroaki's library is lower in intensity and has a modulation of 1-2Hz. I do not immediately see the reason for this behavior in your source code.

Wonderful.  This was exactly what I was looking for this morning, after spending some time last night trying to understand Kimora Hiroaki's library (difficult, because I don't know obj-C).  

The only odd behavior I did see is that the vibration output compared to Hiroaki's library is lower in intensity and has a modulation of 1-2Hz.  I do not immediately see the reason for this behavior in your source code.

> The only odd behavior I did see is that the vibration output 

> compared to Hiroaki's library is lower in intensity and has a 

> modulation of 1-2Hz. I do not immediately see the reason for this 

It's a bad side-effect of getting sensor data.

The vibration would be normal when you stop "metro".

I might be able to improve it in the next version.

> The only odd behavior I did see is that the vibration output  
> compared to Hiroaki's library is lower in intensity and has a  
> modulation of 1-2Hz.  I do not immediately see the reason for this  
> behavior in your source code.

It's a bad side-effect of getting sensor data.
The vibration would be normal when you stop "metro".
I might be able to improve it in the next version.

Do these only work when the remote is connected?? Or is it possible that they only load on Macintel? On my G5 it comes up as a bogus object but gives a different error then the usual can not fragload. My friend brought his wii over for the week and I would love to toy with this for a bit. Good work! I was actually thinking that it would make a great max/jitter controller after messing with the icubex gforce2d sensors.

Do these only work when the remote is connected?? Or is it possible that they only load on Macintel?  On my G5 it comes up as a bogus object but gives a different error then the usual can not fragload.  My friend brought his wii over for the week and I would love to toy with this for a bit.  Good work!  I was actually thinking that it would make a great max/jitter controller after messing with the icubex gforce2d sensors.


On 2006/12/16, at 17:46, Nicholas C. Raftis III wrote:

> Do these only work when the remote is connected?? Or is it possible 

> that they only load on Macintel? On my G5 it comes up as a bogus 

> object but gives a different error then the usual can not fragload.

I believe that it runs both on PowerPC-Mac and Intel-Mac.

I checked it on PowerBook G4 and MacBook Pro.

But it might need the latest Mac OS X(10.4.8) because of the 

> Do these only work when the remote is connected?? Or is it possible  
> that they only load on Macintel?  On my G5 it comes up as a bogus  
> object but gives a different error then the usual can not fragload.

I believe that it runs both on PowerPC-Mac and Intel-Mac.
I checked it on PowerBook G4 and MacBook Pro.
But it might need the latest Mac OS X(10.4.8) because of the  
difference of Bluetooth framework.
Please check it again.

Unfortunatey, on my Macbook 10.4.8 the new object won't connect at all. I reverted back to the previous object and it connected immediately. Not sure what's up with this, but I'm curious about the Security Update that came out a couple of days ago -- is it possible that this has killed the connect function?

also of note is that when I try to quit Max, after attempting to connect the wiiremote, Max hangs during quit and I need to log out and back in to relaunch Max.

What's unusual about this hang is that a force-quit doesn't work, and I can't "kill" it either, because it doesn't show up as a process in top or Activity Monitor. Yet, even though there appears to be no process, I also can't relaunch Max using the application icon, or from the dock. Never seen that before...

I looked up security updates for Intel, and this is the last one:

http://www.apple.com/support/downloads/securityupdate20060071048clientintel.html

So not "a few days ago" by any stretch of the imagination. I'm not sure how I got it so late, but I'm assuming most Intel-users will be running it by now.

Anyway, the new version looks great -- glad to see the new "tilt" sensor output -- so hopefully a fix will come soon.

also of note is that when I try to quit Max, after attempting to connect the wiiremote, Max hangs during quit and I need to log out and back in to relaunch Max. 

On 2006/12/17, at 10:44, jbmaxwell wrote:

> Unfortunatey, on my Macbook 10.4.8 the new object won't connect at 

> all. I reverted back to the previous object and it connected 

Could you try it again with Overdrive OFF ?

> Unfortunatey, on my Macbook 10.4.8 the new object won't connect at  
> all. I reverted back to the previous object and it connected  
> immediately.

Sorry for the delay -- working away and didn't notice your post. Yes, it connects fine with Overdrive disabled!

Sorry for the delay -- working away and didn't notice your post. Yes, it connects fine with Overdrive disabled!
Something to do with the sleeps?

It's also fine running with Overdrive on (naturally); it's just a matter of connecting.

I'm also just wondering what people are using for the IR sensors? I understand you need more than one point for the remote to triangulate. Any recommendations?

havent tried this (no wii i here yet) but take two-three tv remotes with a

stuck key and face the wiimote. this should work.

> It's also fine running with Overdrive on (naturally); it's just a matter

> I'm also just wondering what people are using for the IR sensors? I

> understand you need more than one point for the remote to triangulate. Any

havent tried this (no wii i here yet) but take two-three tv remotes with a
stuck key and face the wiimote. this should work.

On 12/17/06, jbmaxwell  wrote:
>
>
> It's also fine running with Overdrive on (naturally); it's just a matter
> of connecting.
>
> I'm also just wondering what people are using for the IR sensors? I
> understand you need more than one point for the remote to triangulate. Any
> recommendations?
>
> J.
>

On 2006/12/18, at 3:14, yair reshef wrote:

> havent tried this (no wii i here yet) but take two-three tv remotes 

> with a stuck key and face the wiimote. this should work.

Two candles works fine too. See my blog (text in Japanese).

http://max.iamas.ac.jp:16080/modules/xeblog/?

> havent tried this (no wii i here yet) but take two-three tv remotes  
> with a stuck key and face the wiimote. this should work.

Two candles works fine too. See my blog (text in Japanese).
http://max.iamas.ac.jp:16080/modules/xeblog/? 
action_xeblog_details=1&blog_id=53

Ok, I got it running on my laptop with 10.4.8 and max 4.6. Good work! I cant seem to activate the leds, rumble, or get the IR. Do you have to connect the wii to get the IR? I tried the remote trick, Ill try the candle trick tomorrow. I like the creative potential here. Have you tried 2 at once?

Ok, I got it running on my laptop with 10.4.8 and max 4.6.  Good work!  I cant seem to activate the leds, rumble, or get the IR.  Do you have to connect the wii to get the IR?  I tried the remote trick, Ill try the candle trick tomorrow.  I like the creative potential here.  Have you tried 2 at once?


On 2006/12/18, at 15:58, Nicholas C. Raftis III wrote:

> I cant seem to activate the leds, rumble, or get the IR.

I believe led and rumble activation will work if you can get motion- 

Let me know the details of your condition.

You can't get IR-sensor data if wiimote couldn't recognize the sensor 

> Do you have to connect the wii to get the IR

You need the sensor bar (or two IR transmitters or two candles).

No. It does not support multiple wiimotes at this time.

I believe led and rumble activation will work if you can get motion- 
sensor data.
Let me know the details of your condition.
You can't get IR-sensor data if wiimote couldn't recognize the sensor  
bar.

You don't need the wii (console) itself.
You need the sensor bar (or two IR transmitters or two candles).

No.  It does not support multiple wiimotes at this time.
I'll try it later.

Im running osx10.4.8 and newest max/msp/jitter. I click the sync on the remote and it flashes and I click connect and everything does as it should. Its just that if I check those boxes (for IR,Rumble,LEDS), nothing occurs. Im also not sure how to get the IR bar to work with this since it seems to be connected to wii by a proprietary connection. I tried with the wii on so that it might power the IR but it crashes with wii on. It also seems to be rather touchy in general, crashing sometimes when connnecting, and then it will work the next time with no real difference in method. Im curious if it may be more stable on intel? Lastly it seems to update rather slowly, even if I put the metro high up. I tried triggering drum samples with the keys and its a bit too slow to make a serious rhythm. All in all though I think this has a ton of potential, just trying to "bug report" if it helps.

Im running osx10.4.8 and newest max/msp/jitter.  I click the sync on the remote and it flashes and I click connect and everything does as it should.  Its just that if I check those boxes (for IR,Rumble,LEDS), nothing occurs.  Im also not sure how to get the IR bar to work with this since it seems to be connected to wii by a proprietary connection.  I tried with the wii on so that it might power the IR but it crashes with wii on.  It also seems to be rather touchy in general, crashing sometimes when connnecting, and then it will work the next time with no real difference in method.  Im curious if it may be more stable on intel?  Lastly it seems to update rather slowly, even if I put the metro high up.  I tried triggering drum samples with the keys and its a bit too slow to make a serious rhythm.  All in all though I think this has a ton of potential, just trying to "bug report" if it helps.

On 2006/12/19, at 11:55, Nicholas C. Raftis III wrote:

> Im running osx10.4.8 and newest max/msp/jitter. I click the sync 

> on the remote and it flashes and I click connect and everything 

> does as it should. Its just that if I check those boxes (for 

I have nothing to say at this time but I'll check my object again.

> Im also not sure how to get the IR bar to work with this since it 

> seems to be connected to wii by a proprietary connection. I tried 

> with the wii on so that it might power the IR but it crashes with 

The Sensor Bar (IR Bar) get the power from Wii Console. And you might 

not be able to connect Wii Remote to the computer if you turn the 

power of Wii Console on because Wii Console have a connection to Wii 

Remote. I can't say the detail because I don't have Wii Console ;-)

Thus I think you should provide the power to the Sensor Bar by 

> It also seems to be rather touchy in general, crashing sometimes 

> when connnecting, and then it will work the next time with no real 

> difference in method. Im curious if it may be more stable on intel?

It might due to the processing power. Please check it without 

graphical things. (ex. remove the patch cords from outlets of 

aka.wiiremote and connect to print object.)

> Lastly it seems to update rather slowly, even if I put the metro 

> high up. I tried triggering drum samples with the keys and its a 

It might due to the bad implementation in 1.0B2.

I'll release the next version as soon as possible.

> All in all though I think this has a ton of potential, just trying 

> Im running osx10.4.8 and newest max/msp/jitter.  I click the sync  
> on the remote and it flashes and I click connect and everything  
> does as it should.  Its just that if I check those boxes (for  
> IR,Rumble,LEDS), nothing occurs.

Thank you for reporting.
I have nothing to say at this time but I'll check my object again.

> Im also not sure how to get the IR bar to work with this since it  
> seems to be connected to wii by a proprietary connection.  I tried  
> with the wii on so that it might power the IR but it crashes with  
> wii on.

The Sensor Bar (IR Bar) get the power from Wii Console. And you might  
not be able to connect Wii Remote to the computer if you turn the  
power of Wii Console on because Wii Console have a connection to Wii  
Remote. I can't say the detail because I don't have Wii Console ;-)

Thus I think you should provide the power to the Sensor Bar by  
yourself (or use two candles).

> It also seems to be rather touchy in general, crashing sometimes  
> when connnecting, and then it will work the next time with no real  
> difference in method.  Im curious if it may be more stable on intel?

It might due to the processing power. Please check it without  
graphical things. (ex. remove the patch cords from outlets of  
aka.wiiremote and connect to print object.)

> Lastly it seems to update rather slowly, even if I put the metro  
> high up.  I tried triggering drum samples with the keys and its a  
> bit too slow to make a serious rhythm.

It might due to the bad implementation in 1.0B2.
I'll release the next version as soon as possible.

> All in all though I think this has a ton of potential, just trying  
> to "bug report" if it helps.

I am experiencing the same problems as Nicholas. Acceleration and 

buttons work, but I am not able able to change LEDs or get it to 

vibrate, and IR sensor returns "nan nan nan 1".

I have been fiddling with the code, recompiling and testing to see if I 

could track down the problem. Adding post messages to myDataListener() 

in wiiremote.c, I see that when first connecting to the wiiremote I 

receive one message with dp[1] = 0x30, and from there on I only receive 

I have tried adding post messages to sendCommand() and 

wiremote_irsensor(), and sending messages to the wiiremote appears to 

work as supposed to, but I believe that the problem is that these 

messages either do not reach the remote device, or are 

ignored/misinterpreted so that it do not respond to them.

I have also discovered that disconnecting do not work, wiiremote keeps 

sending messages. So it seems that the problem has to do with 

communication from the mac to the wii while communication from wii to 

Below are my specs in case they can point to something obvious that I am 

Apple Bluetooth Software Version: 1.7.8f2

http://www.billionton.com.tw/english/product/USBBT02-X.htm

It doesn't have Mac drivers, but it do still seem to work. In System 

profiler, this info comes up the device as USB:

>> Im running osx10.4.8 and newest max/msp/jitter. I click the sync on 

>> the remote and it flashes and I click connect and everything does as 

>> it should. Its just that if I check those boxes (for 

> I have nothing to say at this time but I'll check my object again.

>> Im also not sure how to get the IR bar to work with this since it 

>> seems to be connected to wii by a proprietary connection. I tried 

>> with the wii on so that it might power the IR but it crashes with wii 

> The Sensor Bar (IR Bar) get the power from Wii Console. And you might 

> not be able to connect Wii Remote to the computer if you turn the 

> power of Wii Console on because Wii Console have a connection to Wii 

> Remote. I can't say the detail because I don't have Wii Console ;-)

> Thus I think you should provide the power to the Sensor Bar by 

I am experiencing the same problems as Nicholas. Acceleration and 
buttons work, but I am not able able to change LEDs or get it to 
vibrate, and IR sensor returns "nan nan nan 1".

I have been fiddling with the code, recompiling and testing to see if I 
could track down the problem. Adding post messages to myDataListener() 
in wiiremote.c, I see that when first connecting to the wiiremote I 
receive one message with dp[1] = 0x30, and from there on I only receive 
messages with dp[1] = 0x31.

I have tried adding post messages to  sendCommand() and 
wiremote_irsensor(), and sending messages to the wiiremote appears to 
work as supposed to, but I believe that the problem is that these 
messages either do not reach the remote device, or are 
ignored/misinterpreted so that it do not respond to them.

I have also discovered that disconnecting do not work, wiiremote keeps 
sending messages. So it seems that the problem has to do with 
communication from the mac to the wii while communication from wii to 
the laptop works.

Below are my specs in case they can point to something obvious that I am 
missing out on.

TiBook (1GHz G4, PPC)
Mac OSX 10.4.8 (8L127)
Max 4.6.2
aka.wiiremote-b3
Apple Bluetooth Software Version:    1.7.8f2

This USB bluetooth device:
http://www.billionton.com.tw/english/product/USBBT02-X.htm

It doesn't have Mac drivers, but it do still seem to work.  In System 
profiler, this info comes up the device as USB:

  Version:    19.58
  Bus Power (mA):    500
  Speed:    Up to 12 Mb/sec
  Product ID:    0x0001
  Vendor ID:    0x0a12

Masayuki Akamatsu wrote:
>> Im running osx10.4.8 and newest max/msp/jitter.  I click the sync on 
>> the remote and it flashes and I click connect and everything does as 
>> it should.  Its just that if I check those boxes (for 
>> IR,Rumble,LEDS), nothing occurs.
>
> Thank you for reporting.
> I have nothing to say at this time but I'll check my object again.
>
>> Im also not sure how to get the IR bar to work with this since it 
>> seems to be connected to wii by a proprietary connection.  I tried 
>> with the wii on so that it might power the IR but it crashes with wii 
>> on.
>
> The Sensor Bar (IR Bar) get the power from Wii Console. And you might 
> not be able to connect Wii Remote to the computer if you turn the 
> power of Wii Console on because Wii Console have a connection to Wii 
> Remote. I can't say the detail because I don't have Wii Console ;-)
>
> Thus I think you should provide the power to the Sensor Bar by 
> yourself (or use two candles).
>


I should mention that, although I haven't checked for all the issues Trond reported, I have noticed that the disconnect doesn't work on my system either.

Macbook 1.83 GHz
2 GB RAM
OS X 10.4.8
MaxMSP 4.6.2


I always thought the Tibooks have built-in Bluetooth...

Trond Lossius wrote:
> This USB bluetooth device:
> http://www.billionton.com.tw/english/product/USBBT02-X.htm

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com


> I always thought the Tibooks have built-in Bluetooth... 

Stefan Tiedje wrote: 
>> This USB bluetooth device:
>> http://www.billionton.com.tw/english/product/USBBT02-X.htm
>
> I always thought the Tibooks have built-in Bluetooth... 


I have been doing further testing to narrow down the problem. The 

problem seems to be occur when connecting.

First of all sendCommand() in wiiremote.c do not return any indications 

if it fails to send the command as can be seen by adding a few 

Boolean sendCommand(unsigned char *data, size_t length)

ret = IOBluetoothL2CAPChannelWriteSync(gWiiRemote.cchan, buf, 

Recompiling with these changes I see that sendCommand() manage to send 

four commands successfully when connecting, but from there on, it 

consequently fails whenever I try to change LED, trigger vibration or 

Next step I have done has been to change arguments for the function 

calls at the end of wiiremote_connect(void). It turns out that I am able 

to get LEDs lighting, vibration and IR sensing using arguments such as:

However I am not able to change them again once the connection is done.

Doing this change in wiiremote_connect(void) I start receiving IR data. 

Using candles for IR I get somewhat meaningless data from the second 

outlet of the external: "-100 -100 NAN 0", but that's another story to 

be looked into once I have managed to have communication to and from the 

I have noticed one more thing: When connecting, I get the following 

error message in system.log as viewed in Console:

Dec 22 10:32:17 Trond-Lossius-Computer kernel[0]: 

[IOBluetoothHIDDriver][handleStart] staticPrepControlChannelAction 

[IOBluetoothHIDDriver][handleStart] Failed.

I am not sure what this error message indicates and how to solve it, but 

I believe I've found the crime scene. ;-)

If you have the time to help me out here or give me some cues about 

further steps, Masayuki, it would be appreciated a lot.

> I am experiencing the same problems as Nicholas. Acceleration and 

> buttons work, but I am not able able to change LEDs or get it to 

> vibrate, and IR sensor returns "nan nan nan 1".

> I have been fiddling with the code, recompiling and testing to see if 

> I could track down the problem. Adding post messages to 

> myDataListener() in wiiremote.c, I see that when first connecting to 

> the wiiremote I receive one message with dp[1] = 0x30, and from there 

> on I only receive messages with dp[1] = 0x31.

> I have tried adding post messages to sendCommand() and 

> wiremote_irsensor(), and sending messages to the wiiremote appears to 

> work as supposed to, but I believe that the problem is that these 

> messages either do not reach the remote device, or are 

> ignored/misinterpreted so that it do not respond to them.

Nintendo Wii Remote Object Updated