WiiServer stalls on connecting OSX Mavericks (10.9)

[GoogleCodeExporter]

What steps will reproduce the problem?
----
1. Launch WiiServer 0.99.5 in OSX 10.9
2. Press buttons 1 and 2 on WiiMote
3. Connecting message displays but gets no further

What is the expected output? What do you see instead?
----
Was getting a connected message and full functionality when running under OSX 
before upgrade (10.6.8)

What version of the product are you using? On what operating system?
----
WiiServer 0.99.5
OSX 10.9 Mavericks

Please provide any additional information below.
----
Initial report of issue at X-Plane.org forums here: 
http://forums.x-plane.org/index.php?showtopic=73468

Original issue reported on code.google.com by m...@headfirst.co.nz on 7 Jan 2014 at 10:32

[GoogleCodeExporter]

Hi,
I found out, that some basic info is being logged by the Wiimote server as it 
is now;
if you open a console (Applications/Utilities/Console) and search for Wii 
(search/filter field in the upper right corner), you should see some messages 
there - could you paste them to a file and attach it here? That would give me 
something to start from.

Kind regards,

Michal

Original comment by f.jo...@email.cz on 8 Jan 2014 at 3:38

[GoogleCodeExporter]

Hi,
after going through the sources, the only thing I can think of now, is a race 
between system and the wiimote server. I'm attaching a new build of the Wiimote 
server, that hints the system that the device should be ignored.

Please check, if it works for you and if not, please do as the previous post 
describe so I get some idea of what is going on.
Kind regards,

Michal

Original comment by f.jo...@email.cz on 8 Jan 2014 at 8:53

Attachments:

• WiiServer.zip

[GoogleCodeExporter]

Hi,

Bit confused at the moment. Tried the new WiiServer build with no change then 
quit and dropped the old one back in. This time it reconnected. Installed the 
new plugin via ltr_gui and ran X-Plane and all appears to work. Not sure what's 
going on here but reluctant to close the issue yet just in case. Have attached 
the log for the successful connection (using 99.5)

Original comment by m...@headfirst.co.nz on 9 Jan 2014 at 3:31

Attachments:

• wiimote-debug-090113.log

[GoogleCodeExporter]

Hi,
should you encounter the problem again, the console can be used to retrieve the 
log info afterwards... I'll keep it open at least until I'll be able to check 
it myself (looks like some kind of race condition to me).

Kind regards,

Michal

Original comment by f.jo...@email.cz on 9 Jan 2014 at 5:52

[GoogleCodeExporter]

Hi Matt,
I have a question - after installing the 10.9, did you run ltr_gui?

The thing is this: when you run Wiimote server before you ever run ltr_gui, it 
is not going to be initialized properly and it seems to exhibit the behavior 
you described (also the initial message is not disconnected in red, but black 
staus). 

The whole problem is solved by simply running ltr_gui and saving prefs, which 
you probably did when you reinstaled the XPlane plugin...
Kind regards,

Michal

Original comment by f.jo...@email.cz on 10 Jan 2014 at 3:31

[GoogleCodeExporter]

Hi Michal,

Sorry - just picked this up. That's possible - unfortunately I can't recall 
now. However I do still have issues connecting and staying connected. Two 
things I've noticed are:

1) When linuxtrack is running successfully in X-Plane and I toggle tracking off 
then on again, tracking does not resume until I change focus to another 
application and return back to X-Plane.

2) Occasionally the Wiimote disconnects during the flight (WiiServer status 
shows "Disconnected")

3) Today I woke my machine from sleep, connected then launched ltr_gui, enabled 
Preview which worked for a few seconds then WiiServer disconnected. Had to quit 
and restart WiiServer to get it to attempt another connection but it hangs at 
"Connecting" status, logging the following to console:

20/01/14 11:38:51.708 am WiiServer[12416]: Server communication initialized!
20/01/14 11:38:56.570 am WiiServer[12416]: Start requested!
20/01/14 11:38:56.607 am WiiServer[12416]: Discovery started!
20/01/14 11:39:15.914 am WiiServer[12416]: Opening control channel...

4) Quitting WiiServer and disabling/re-enabling Bluetooth in the OS then 
reconnecting worked but on launching ltr_gui tracking again resulted in a 
disconnect and no preview tracking displayed in ltr_gui. Console read:

20/01/14 11:47:04.115 am WiiServer[12498]: Server communication initialized!
20/01/14 11:47:06.660 am WiiServer[12498]: Start requested!
20/01/14 11:47:06.671 am WiiServer[12498]: Discovery started!
20/01/14 11:47:10.547 am WiiServer[12498]: Opening control channel...
20/01/14 11:47:10.947 am WiiServer[12498]: Control Channel Opened!
20/01/14 11:47:10.947 am WiiServer[12498]: Opening interrupt channel...
20/01/14 11:47:10.960 am WiiServer[12498]: Interrupt Channel Opened!
20/01/14 11:47:11.961 am WiiServer[12498]: Initializing Wiimote!
20/01/14 11:47:12.162 am WiiServer[12498]: Disabling IR Sensor
20/01/14 11:47:13.412 am WiiServer[12498]: We are connected to the wiimote!
20/01/14 11:47:13.412 am WiiServer[12498]: Disabling IR Sensor
20/01/14 11:47:14.414 am WiiServer[12498]: Buttons: 0000
20/01/14 11:47:14.414 am WiiServer[12498]: Battery: 49
20/01/14 11:47:14.415 am WiiServer[12498]: Flags: 01
20/01/14 11:48:17.518 am WiiServer[12498]: Enabling IR Sensor
20/01/14 11:48:35.813 am WiiServer[12498]: Disabling IR Sensor
20/01/14 11:48:41.286 am WiiServer[12498]: Write Error for command 0x13: 
0xE00002D7
20/01/14 11:48:41.347 am WiiServer[12498]: Write Error for command 0x1a: 
0x10000003
20/01/14 11:48:41.407 am WiiServer[12498]: Write Error for command 0x12: 
0x10000003
20/01/14 11:48:41.508 am WiiServer[12498]: Write Error for command 0x11: 
0x10000003
20/01/14 11:48:41.508 am WiiServer[12498]: Problem sending command! 0x1100
20/01/14 11:48:41.508 am WiiServer[12498]: Interrupt Channel closed!
20/01/14 11:48:41.508 am WiiServer[12498]: Still connected - trying to restore!
20/01/14 11:48:41.508 am WiiServer[12498]: Opening interrupt channel...
20/01/14 11:48:51.757 am WiiServer[12498]: Couldn't open interrupt L2CAP 
channel!
20/01/14 11:48:51.757 am WiiServer[12498]: Have DISCONNECT REQUEST in state 
CONNECTED!
20/01/14 11:48:51.758 am WiiServer[12498]: We are disconnected!
20/01/14 11:48:51.758 am WiiServer[12498]: Closing!!!
20/01/14 11:48:51.759 am WiiServer[12498]: Control Channel closed!
20/01/14 11:48:51.759 am WiiServer[12498]: Not connected anymore!
20/01/14 11:48:51.759 am WiiServer[12498]: Have DISCONNECT REQUEST in state 
DISCONNECTING!
20/01/14 11:48:51.759 am WiiServer[12498]: Closing!!!
20/01/14 11:48:51.760 am WiiServer[12498]: Closing baseconnection!

5) (Force) quit apps. Repeat Bluetooth disable/enable. Attempt connect with 
WiiServer. Hang at "Connecting". Console:

20/01/14 11:51:40.258 am WiiServer[12555]: Start requested!
20/01/14 11:51:40.268 am WiiServer[12555]: Discovery started!
20/01/14 11:51:59.575 am WiiServer[12555]: Opening control channel...

Any ideas?

Original comment by m...@headfirst.co.nz on 19 Jan 2014 at 10:53

[GoogleCodeExporter]

Hi Matt,
as for 1), I'll check that. 

Point 2) and the rest seem to indicate, that the connection between the Mac and 
Wiimote breaks completely (those write errors along with the channel close 
messages); however the fact, that in the 5) the connection doesn't occur might 
indicate something broken deeper than my app goes... You might try to force 
quit the blued and see if it helps (like 
http://www.isaackeyet.com/2011/how-to-restart-bluetooth-blued-on-a-mac/ )...

As for why does it happen - might be anything from bad driver to some 
interference (Wifi reportedly might clash with BT) or even a hardware problem; 
unfortunately with the informations I have, I can't really tell... I'd lean 
more to the side of the software problem on the MacOS X side - discovery 
apparently finds the device, but the connection doesn't succeed. I'll try to 
see if there are any more points of the failure that I can cover meaningfully.

Kind regards,

Michal

Original comment by f.jo...@email.cz on 20 Jan 2014 at 6:26

• Changed state: Accepted