davidestevens
Member
hi,
I'm getting the following message from time to time -
Wiimote discovery error (code:189)
Once this pops up, I have to restart my macBook in order to get Osculator working again (just quitting & restarting the app doesn’t work).
This seems to happen when Osculator has been running for a long time, and I've allowed the wiimote to auto power down.
This is a wii-mote with MotionPlus.
OSX 10.5.8
Any comments? Is this a big or expectyed behaviour?
thanks
David
camille
oscltr cookr
Hi David,
This is definitely a bug from Mac OS X 10.5.8. It doesn't happen on 10.6.
I assume you are using oscltr 2.9-rc2 since you are reporting the error code (this wasn't possible before). I have tried to address the issue you are having in this version, with no luck.
Since you are able to reproduce the problem, it would be of interest to see wether the continuous discovery is the cause or not. I would suggest you go in the Preferences and turn off "Start discovery on launch", then restart the application (or stop the discovery). This way you will minimize the time and the number of occurrences where discovery is happening.
Have you done anything special to allow the wiimote to power down? I was not aware of this feature and it sounds interesting.
Best,
Cam
PS: FYI this user had the same problem: http://www.osculator.net/forum/topic/238#post-1182
davidestevens
Member
hi Camille,
OK, I've turned off auto discovery and will let you know if anything changes.
The power-down was actually the battery going flat :-))
Maybe it's time I updated this machine to 10.6 - I've been holding off because I haven't found definite confirmation that max/msp is ok with 10.6, and if 10.6 breaks anything with my existing patches I'd be in the doo-doo!
camille
oscltr cookr
ok then, this is the manual auto-shutdown mode, I know this one :-)
I think it is ok to upgrade to 10.6, but I would really recommend you to clone your hard drive before doing the big jump. Or better, install 10.6 on an external disk, and try your most important software on it.
Also, the compatibility headache comes often less than Max than it's extensions …
tuckwilliamson
Member
You don't have to restart your computer if you are okay with using the terminal. If you kill the bluetooth process it will be restarted and the error is resolved. Note that you may not want to do this if you have other bluetooth devices that are connected at the time as I don't know what would occur in that case.
If you would like you can use the following command in the terminal (under Applications/Utilities/Terminal):
sudo killall blued
camille
oscltr cookr
That is correct, however there is a possibility to corrupt blued's configuration files.
I guess that if you know how to use the Terminal, you also know what files are managed by blues and then remove them. But then, a restart would still be required.
You must log in to post.