OC4BAv5 MAX no longer working [SOLVED]

[radlad]

Software/version status

OC4BAv5 MAX 240221.jpg (255.01 KiB) Viewed 2284 times

Hi Roar,

I am currently using Opencockpits FMC v3, MCP v3 and EFIS v2 hardware and SIOC v7.03B2.

Having purchased OC4BAv5 MAX in November 2019, I initially had some minor issues which you dealt with and since then, everything has been working fine.

After a break of 6 weeks away from my PC/Simulator, I came back to fire up P3D this week only to find that none of my Opencockpits hardware were working correctly with my PMDG aircraft. With the 737 NGXu, nothing was working at all and with the 777/747 there was limited functionality. As the NGXu is my primary aircraft of choice, I decided to try uninstalling/re-installing SIOC and the OC4BAv5 MAX drivers/software which made no difference. In sim, the AP disengage button was continuously switching and every now and again, the LEDs would light on the MCP. There was no interaction with the EFIS/FMC.

The only changes to my PC were windows updates and PMDG updates.

Yesterday, I decided to completely uninstall P3D and all addons and start again with a fresh build. Having installed P3D, PMDG 737 NGXu and SIOC/OC4BAv5 MAX and remembering to update the OCP4NGXu driver and associated scripts that you sent out in November 2019, I am still experiencing the same as above.

All my Opencockpit devices are being recognised in SIOC and when I load the NGXu in P3D, both SIOC and the OCP4NGX_v5.1 script loads correctly.

Please find attached screenshots showing software versions/status.....

Many thanks,

Dave Dawson

[radlad]

I should have asked.......

Did I miss an update?

[mvr1918]

Did you make a new configuration file(PMDG B737.ini) with Oc4BAv5's Config?

If you since it was working OK, you have updated Windows OS, it could be that Windows OS screws up the USB numbering.

[radlad]

Hi Roar,

Thanks for sending over the latest drivers etc. in a separate email.

Unfortunately, I find myself in the same position.

As I reported in my initial thread, when re-installing SIOC/OC4BAv5 MAX (as admin), I did make a new config file. Please see below PMDG B737.ini:

[SIOC]
IOCP_port=8092
IOCP_timeout=4000
Minimized=Yes
toggle_delay=20
[IOCARDS MODULE]
IOCard_disable=No
IOCard_LPT=No
[FSUIPC MODULE]
FSUipcdisable=No
FSUipcRefresh=60
[IOCP CLIENTS MODULES]
IOCPini_delay=3000
IOCPclient0_disable=no
IOCPclient0_host=localhost
IOCPclient0_port=8099
IOCPclient1_disable=yes
IOCPclient1_host=localhost
IOCPclient1_port=8092
[SOUND MODULE]
Sound_disable=Yes
Volume=100
[*]
[PMDG B737]
CONFIG_FILE=C:\SIOC\OCP4NGX_v5.1.ssi
MASTER=7,7,1,47
MASTER=15,15,1,45
MASTER=13,13,1,9

As per my original screen shot, SIOC shows the correct USB numbers, i.e. MCP= 45, EFIS=47 and FMC=9 and the correct script for the 737, i.e. OCP4NGX_v5.1

Based on the updated drivers/software you sent over, I have again uninstalled/re-installed SIOC/OC4BAv5 MAX (as admin) and again I see the corresponding correct USB numbers and new script:

[SIOC]
IOCP_port=8092
IOCP_timeout=4000
Minimized=Yes
toggle_delay=20
[IOCARDS MODULE]
IOCard_disable=No
IOCard_LPT=No
[FSUIPC MODULE]
FSUipcdisable=No
FSUipcRefresh=60
[IOCP CLIENTS MODULES]
IOCPini_delay=3000
IOCPclient0_disable=no
IOCPclient0_host=localhost
IOCPclient0_port=8099
IOCPclient1_disable=yes
IOCPclient1_host=localhost
IOCPclient1_port=8092
[SOUND MODULE]
Sound_disable=Yes
Volume=100
[*]
[PMDG B737]
CONFIG_FILE=C:\SIOC\OCP4NGX_v5.5.ssi
MASTER=7,7,1,47
MASTER=15,15,1,45
MASTER=13,13,1,9

At the time of testing, all firewall/AV software had been disabled.

I can only think there is an issue with my windows 10 build, (currently running the latest version).

Unless you can suggest anything else, I think my only option is to re-build my PC and try again.

One other point, whilst running SIOC/OC4BAv5 MAX, I have even checked the relevant UDP port is listening on localhost via the 'netstat' command. However, I did notice that whilst in SIM, sometimes after a few minutes, the SIOC server showed the client had discconnected with no obvious reason why. I could run Wireshark to see if there is anything happening at the network/application level but I am clutching at straws at the moment.....

Many thanks,

Dave.

[mvr1918]

It could be an IOCP port conflict.

Try to change the IOCP port used from 8092 to 8094 or 8096 in the OC4BAv5.ini file.

Then delete the PMDG Bxxx.ini files and make new configuration files.

[radlad]

Hi Roar,

So I spent several hours yesterday testing......

I initially ran Wireshark prior to starting my P3D/SIOC etc. to establish if indeed UDP 8092 was being used by another application - it wasn't. In any case, I tried testing with different UDP port numbers as per your suggestion and this did not change anything. Even though I had said previously that I had observed some disconnects from the SIOC server, this did not happen at all yesterday. I have since changed the UDP port back to 8092.

With all my PMDG aircraft installed now and re-installing SIOC/OC4BAv5 MAX, the client connected each time to the SIOC server and stayed connected until I shut down P3D. I have found some very interesting results by trying each of my aircraft in turn:

737 NGXu
- No interaction from my MCP, EFIS & FMC and no led display on the MCP. Constant clicking of the AP disengage button in Sim and when turning off MCP/EFIS/FMC, I can interact with the Sim normally via keyboard/mouse etc.

747-400
- FMC working fine.
- MCP - all LEDs working and the IAS/Heading knobs interacting but the altitude knob did not. When switching either of the FD switches and AP Disengage switch, the Sim would respond but after a few seconds, the in Sim switches would revert to their previous/default position. The same can be said for some of the MCP buttons, like VNAV/LNAV and so on.
- EFIS - when pushing BARO/MINS knobs, initially, 'IN' will move to 'HPA' or 'RADIO' will move to 'BARO' in sim but again after a few seconds, will return to their default position. This also happens with the MAP and Range selector knobs. The 'FPV' & 'MTRS' button also follow this behaviour. The 'STA', 'WPT', 'CTR', 'ARPT', 'TFC', 'DATA' &'POS' buttons do nothing but in Sim, all buttons on both EFIS's are continually depressing/releasing with no input from myself. ( Please note that I have rotary selected in each aircraft)

777-200 - Exactly the same as the 747 but the only difference is that the altitude knob does work.

I am pretty convinced now that given everything was working in December and when I came back to my Sim 6 weeks later and installed windows and PMDG updates, I found the issues reported, it must be something to do with those updates. Given I have different levels of functionality in each aircraft, I am leaning towards the PMDG updates that have broken my set up. The only thing I haven't done is rebuild my PC and as I am sure you appreciate, I'm reluctant to do as it takes ages to add all your apps and settings etc.

Do you have a direct line into PMDG from a developer perspective and if so, can this be raised?

Many thanks,

Dave.

[mvr1918]

1. Do you have a Power Unit connected to your OC MCP?
2. Have you enabled the data transmission in the 737NGXu_Options.ini?
3. Have you the latest versions of the PMDG airplanes? Check in the PMDG Operational Center

[radlad]

Hi Roar,

1. Yes I do and as I have said, this is working with different levels of functionality in my PMDG aircraft. Also, please note that although I have several powered USB hubs to connect all my hardware, I have also tested by directly connecting my MCP, EFIS & FMC directly to USB2.0 ports on my PC and still the same outcome.

2. I have double checked that each of the aircraft have the below code in their corresponding options.ini file

[SDK]
EnableDataBroadcast=1

3. Again, when I returned after 6 weeks away from my Sim, this was the very first thing I did, update aircraft and all other add-ons. As I have since completed a new install of P3D, I have only added my PMDG/SIOC/OC4BAv5 MAX add-ons as their is no point installing anything else until I know everything is working and it helps from a troubleshooting perspective. Please see attached screenshot showing my PMDG aircraft status.

Many thanks,

Dave.

[mvr1918]

Hard to say what is the problem, but looking again at the first image, it looks like SIOC is not behaving as it should.

Do you still have the IOCP client #0 Connected running in the LOG window of SIOC?

If yes, you have some issues with SIOC. I would reinstall SIOC as it is not behaving correctly.

If you send me an ANYDESK ID I can take a remote look at your settings.

Send me an email, if you want that, roarkrsp@gmail.com

[radlad]

Hi Roar,

Apologies for the delay but I bit the bullet and decided to rebuild my PC. You'll be glad to hear that now having re-installed P3D and all add-ons, my OC hardware is now working correctly with every PMDG aircraft.

Thank you very much for your support and suggestions and for offering to take a remote look. I did try re-installing SIOC several times but still no joy, hence the re-build.

I am now very cautiously installing all my non-Sim apps and creating a restore point before each install. Like most people, I cannot dedicate my PC purely to flight sims and can only assume it was maybe one of these that was causing the issue. One thought was around virtualisation as I use VMware Workstation and possibly it was the networking elements that were causing SIOC to misbehave. If I find the culprit, I will report back on here for everyone else's benefit.

Many thanks,

Dave.