I've been running tests and I think the problem is in one of the USB hubs I have connected. One usb that I have connected to that hub sometimes turns on and off and maybe that's why I lose the SIOC/OC4BA connection.
I've ordered another hub and when I replace it I'll try it and tell you how it goes.
OC4BA_XP don´t work
Re: OC4BA_XP don´t work
It could be that the windows update enabled the USB power setting to Off. Try to disable so power is always On.
Re: OC4BA_XP don´t work
Yes, the Windows had activated the energy saving in all the usb. I turned them off.
I tried 1 CDUFMC only and it seems to work correctly. But the EXEC key doesn't work. I have started the IOCPconsole and every time I press the EXEC key it shows these values:
146=66 - CDU1
1999=2137 - k
146=0 - CDU1
1999=8 - k
Could it be that offset is wrong?
I tried 1 CDUFMC only and it seems to work correctly. But the EXEC key doesn't work. I have started the IOCPconsole and every time I press the EXEC key it shows these values:
146=66 - CDU1
1999=2137 - k
146=0 - CDU1
1999=8 - k
Could it be that offset is wrong?
Re: OC4BA_XP don´t work
2137 is the correct variable for the CDU_L_EXEC
I need to check this when I am back in my cockpit next week
I need to check this when I am back in my cockpit next week
Re: OC4BA_XP don´t work
Hi,
Did you get a chance to check why the EXEC button doesn't work?
Did you get a chance to check why the EXEC button doesn't work?
Re: OC4BA_XP don´t work
Sorry for letting this topic last this long before given an answer. It slipped to my checks.
If you still have this issue,
I now have an updated driver that corrects the Exec bug. Send request for an update to roarkrsp@gmail.com
The new latest driver should work with XPLANE11 v11.36 and Zibo 3.36.8
If you still have this issue,
I now have an updated driver that corrects the Exec bug. Send request for an update to roarkrsp@gmail.com
The new latest driver should work with XPLANE11 v11.36 and Zibo 3.36.8