After a ‘forever’ pre-order I finally received my Winctrl NWS 32. (Tiller) Unfortunately I can not get it to work with the FBW A32NX. I also own the MCDU, EFIS and FCU. When the Tiller is connected, it knocks out the MCDU, EFIS and FCU. When I disconnect the Tiller, all 3 come back online again.
When I say knock out I mean the screens go dark,and no response from sim or vice versa.
In simappPro all the devices are there. I tried different USB cables and ports including plugging them straight in the motherboard. I am surprised I couldn’t find anything by others about my problem, it makes me think I’m the only one. I suspect it might need a software update as everything seems to work normal in calibration and tests. Anyone else have this problem?
Being new to the Winctrl scene, I just dealt with a similar issue. Do you use a powered USB hub for your other Winctrl gear? If yes, try plugging the tiller directly to your motherboard and leaving everything else on the USB hub. Also, very important but easy to forget, go into your Device Manager under Universal Serial Bus Controllers and make sure each of your Winctrl devices and your USB hub are not allowed to be turned off to save power (untick “Allow the computer to turn off this device to save power” in the Power Management tab in Properties of each device). If that doesn’t solve it, ask Winctrl support.
Yes I tried and did all what you suggested already. And my USB hub is a very good quality powered one anyway. But thanks for your reply.
Update, I tried a default Airbus, (inibuild?) and there the Tiller will play together with the EFIS and FCU, only the MCDU is not working, to me that suggests it’s a software issue. Winctrl support is … well, I went many hrs already going through their scripted “support”…
This is quite a complex issue, and since I am new to hardware in general and Winctrl in particular, this is out of my league. I hope you solve it quickly.
I’ve had similar issues with the FCU when it came out and I was a early owner. After a while a software update fixed the issue. I might be patient and wait for that , instead of getting a new motherboard… Yes that’s what Winctrl support recommended yesterday…