New wiiremote object for testing (based on aka.wiiremote)

    Nov 04 2009 | 12:15 pm
    The below is a duplicate of a post I put up yesterday in reply to another thread, but I'm reposting because the original subject might not attract everyone to whom this might be relevant.
    Hello all,
    I did some work on aka.wiiremote this summer (to make ajh.wiiremote I guess):
    There were several things I was working on:
    1 - Much enhanced stability - and more verbose description (so you can tell whether things are working or not).
    I totally revamped the connection process and how it's dealt with, and found the tedious dropped connection issue, which I have worked around, so as far as the end user is concerned it doesn't exist - I'd hate to say 100% reliable connection here (because I know I'll be proved wrong), but pretty damn close.
    The main problem with the old version is that when things don't connect it can leave the wiiremote in a state where it is partially connected, and you have to use the red button inside the case to reset it. But you don't KNOW that, because you can't really tell what's going on.
    2 - No decoding outside the object (the data is internally decoded for buttons etc.)
    3 - WiiMotionPlus Support
    4 - full 10bit accelerometer values (rather than the 8 bit values)
    So. I need it testing - but I'm also not totally done with it yet. I was going to wait till I had more time to get it ready. However, seeing as this has come up. I'm happy for people to test it, as long as they understand it's as is, and other than simple bug fixes I'm not able to work on it right now. I can't remember exactly how I left it, but I think all the aka.wiiremote features still work, but some stuff works a bit differently.
    Also, I'm on Tiger here, so I can't address Leopard specific issues easily, but I have a feeling that what I've done so far my eliminate a lot of issues - then again, it might not...
    There's not a help patch yet, but I think I have an example patch which is easy to figure out.
    Also, - should say - Mac only (sorry to any PC users)
    If you're interested contact me offlist - you can get my address here:

    • Jan 31 2010 | 12:57 pm
      the [ajh.wiiremote] from Alex is truly working and I've made few patches with it.
      But I've got a stupid trouble when I want to adapt a patch who use [aka.wiiremote] because now I can't compare the difference in between these two object… I can't connect my wiiremote with [aka.wiiremote] anymore !
      the sub-patch (motion) has learn me a lot but I still do not know how to scale the adaptation with accelerators !
      Is there anybody who's find the right algo ?
    • Jan 31 2010 | 3:29 pm
      Jerome - if the below doesn't clear things up you can email me with your patches I'll try to help.
      I'm now outputting the motion calibrated in g-s , but also output-ing 10bit values after that (uncalibrated). If these are for some reason more useful to you then the calibrated values, you'll find that the raw values are roughly 4 times bigger than those from aka.wiiremote (0-1023 rather than 0-255). There is no direct way to translate between gs and the old values because of the calibration - but calibrating in gs mean that the same physical force produces the same results on different remotes.
    • Mar 01 2010 | 12:27 am
      hi AlexHarker, sounds like a wonderful job your doing!! I'm performing a lot with wii's, can't wait to use the wiimote plus... Anyway, my question is. Are you planning to make a windows version as well?
    • Mar 01 2010 | 12:33 am
      Unfortunately I cannot offer windows support as I have no expertise in that area, no windows install, and no particular personal need for this. The time input would just be too great. When the object and source are public anyone is welcome to port the code and sort out the bluetooth stuff on windows (unfortunately the bluetooth and wiimote stuff are fairly intermingled) - if someone is really desperate to do this and knows how they can contact me offlist.
    • Mar 01 2010 | 1:28 pm
      I understand, well, more reason to switch to mac...:)
    • Mar 28 2010 | 9:06 am
      sorry for that profane question, but where can I download the extension?
    • Aug 19 2010 | 4:39 pm
      I am also looking to download this updated version....does anyone have it?
    • Oct 08 2012 | 11:52 am
      Me too bump
    • Jan 31 2013 | 12:16 pm
      Hi Alex
      Firstly, thanks for fixing the aka.wiiremote.
      ajh.wiiremote works well with Max 5 running 10.6.8, but its not working on MAX6 running Mountain Lion (10.8.2).
      Is there any chance ajh.wiiremote will be updated for Mountain Lion and Max 6? i suspect the issue is with Mountain Lion, not Max.
      FYI this link documents the 10.8 fix for DarwiinRemote:
      A link to the new DarwiinRemote is available there too.
    • Feb 03 2013 | 11:03 am
      Hi Damien,
      Thanks. I am aware of the issue and the solution requires porting the code to Objective C and using newer OS routines. darwiinRemote has already done this, but there would still be a need to do significant work to report this code.
      I am not on Mountain Lion and I have no time/personal reason for doing this anytime soon. However, anyone who wants to try is welcome to the source, and whatever support I have time for in attempting to do this work. This has been my answer to all similar enquiries. So far one person has replied with a maybe, which may result in a new version, but otherwise it is still an open offer.
      Sorry not to be able to help more...
    • Feb 06 2013 | 10:41 am
      To update - A couple of nice people are kindly looking at this. I hope to bring more concrete news soon to the community.
    • Feb 06 2013 | 10:48 am
      hi Alex
      I was just going to try to get in touch with you about a similar (same ?) problem : So far I was using wiiMotes (on a mac, 10.6.8) without any problem, now I just bought some more wiis for an upcoming project, those are Wii Motion plus inside, and those do not work. I found out that those are now called "wii mote TR" as their "address" (as seen by the mac) finishes by TR. Just recently Osculator posted a new version which recognises them (see the thread on ) - so I could go osculator->max but would of course prefer to use your object Do you think an update is possible, so the new ones work??
      on a similar note, does anyone tested the "generic" wii-motes? do they have a chance to work, or rather not?
      many thanks - all the best
    • Feb 06 2013 | 11:05 am
      Hmm - there are various issues with the all in one devices - does it not connect at all, or is it the extension stuff/MP that is broken?
      It's always technically possible to fix this stuff - it's just the time to do it, and access to one of the relevant devices - looks like this fix to OSCulator took a little while. As with other issues I can provide source happily, and collate fixes between other devs, but it is unlikely I can offer time to fix these devices anytime soon. In the longer term anyone with time/money to send me a device and fund some work on this would be welcome to do so, but right now I sadly don't have the same time as I did before to work on things freely......
    • Feb 06 2013 | 11:12 am
      for me the problem is that the new (TR, or "wii motion plus inside") wii motes do not connect at all. They were not connecting on the previous osculator I had....
      since I use only a minimal amount of the infos from the wii (basically just the xyz from the accelerometer) - as they are attached to a structure, I basically just need to be able to connect them....
      i am afraid that receiving the source code will not help me at all, however!!! I currently am looking in second-hand shops for previous versions of the wiimote!!!
      thank you for your answers
    • Feb 06 2013 | 11:21 am
      Hi Kasper,
      OK - what happens if you try with the attached version? I've just included what I expect the name to be in the search criteria. I expect this to connect, but that you will possibly have limited functionality. Please update me as to exactly what works with this version.
    • Feb 06 2013 | 11:52 am
      hi again
      so, with the new object there is no improvement but things are slightly different
      1/ in Max 5 (in which i am currently building my patch, but I could make it in max 6) _with bluetooth on, using the help patcher with the new object the wait on connecting is very long, after a while it says it is connected but nothing happens (no acc. data), and the patch is not working (kliking on a toggle has no effect), then max freezes max window says
      Starting Search.... DO READ 1 1e Found wiimote.... Connection Successful!! print: connected wiiremote initiated disconnection Failed to write to wiiremote.... print: disconnected
      2/ in max 6, more or less the same except that when the 4 leds on the wii stop flashing, it does not write (in max window) connected - but the spinning wheel spins forever kliking on a toggle makes max or freeze
      max window said
      ajh.wiiremote 1.0 by Alex Harker (based on aka.wiiremote by Masayuki Akamatsu) Starting Search.... DO READ 1 1e wiiremote initiated disconnection Failed to write to wiiremote.... Found wiimote.... Connection Successful!! Search Finished.... wiiremote not found Found wiimote.... Connection Failed Search Finished.... wiiremote not found print: disconnected
      on the project I am working now I attach a few Wiis to a (real) web on which a dancer/trapezist is... doing this in Reims which is the (French) capital of Champagne - would be happy to send you a bottle of champagne if it works !!! ;-)
    • Feb 06 2013 | 12:59 pm
      I'm afraid that this appears to mean that the device has a different connection process to a normal wiiremote. I doubt I could fix this without a similar device and an amount of time that unfortunately I don't have right now.
      SOrry about that - not sure I can be any more helpful....
    • Feb 06 2013 | 1:11 pm
      will try to buy a "generic" wii mote (not nintendo) and see what is possible with the osculator-> max
      many many thanks
    • Feb 06 2013 | 4:11 pm
      one more note : a "generic" Wiimote (here an "undercontrol" brand) seems to work OK (is a little PITA to connect but then seems stable)
      if it helps
    • Jul 28 2013 | 9:19 pm
      I was wondering if there are any news on this? Would like to avoid using Osculator, though it seems like an awesome tool.
      aka and harkers have been working great and it would be so good to have them back.
      Hope all is well
    • Aug 02 2013 | 9:05 pm
      no doubt, osculator works, but like you I hope a max object in ...a near futur ?
      and, yes all is well ;-)
    • Oct 22 2013 | 9:50 pm
      Just letting everyone know, I am working on this problem right now, I am trying to tackle two birds with one stone and make either objects or at least OSC bridging utilities for both WiiMote and Sony PS Move (using PS Move API).
      I will post updates when I have the chance.
    • Jan 16 2014 | 4:21 pm
      Excellent news that work is still ongoing to keep the a**.wiiremote object alive. is there any recent progress?
    • Nov 06 2014 | 5:05 pm
      Hello I am a senior in high School and I am doing my senior capstone project on making dubstep music from the way I move my body. I have decided to use the aka.wiiremote program using the Theremin from this program. Unfortunately i have found that the does not work for me. I am using a 2012 Macbook pro that is running OSX Mountain Lion. I have managed to connect to Darwin Wii remote which is one of the programs that the help program uses. However the actual help program will not open. If you know what i'm doing wrong i would appreciate your help. Thank you.