A320 FMGS B45

[tuomasho]

The issue with ILS and RWYs is due to mis alignment between the navdata from Aerosoft/navigraph and the facilities inside FS/P3D.
To counter that, when compiling the navdata bin files, my soft reads directly the FS/P3D BGL files to correct the navdata with ILS/RWY lat,lon,course.
With P3D V3, now everythign has to be put outside P3D folder, this could be the issue, particularly if your problem is only with addon sceneries.
The problem is also present with Runways which changed QFU, or which were later added, so the original runway naming changed to for example R/L or C.

JL

Thank you for your quick answer! This could be the case... So, what should I do to get it work? Put something out from FSX Steam folder or what?

-=Tuomas=-

[SSO]

Hi JL, in MCDU I can not select between Squawk mode Standby or Mode C.
at startup it blue up both standby and mode C.
I select Mode C however my VATSIM software vPilot not turn to Mode C as previous version of FMGS.
Thanks.

Thanks for a huge update.

I am having the same problem with vPilot and FMGS.
Previously i could control the squawk mode in the MCDU, but now it forces it back to SBY even if I select mode C in vPilot.


Further my view hat does not work anymore despite it being assignedin P3Dv3.2...

[asessa]

Hi JL, last version installed...
All Cockpitsonic devices dont't work...

This is the hw log

*Date of file:23/03/2016
*22:17:59*:HardwareConnect Launched
*22:18:02*:G:\A320FMGS\Hardware Modules\EHIDmodule.dll loaded
*22:18:02*:G:\A320FMGS\Hardware Modules\FSUIPCmodule.dll loaded
*22:18:02*:G:\A320FMGS\Hardware Modules\SkalarkiIO.dll loaded
*22:18:03* Skalarki JL:client connected
*22:18:07* EHID:Connected version 15 127.0.0.1
*22:18:09* EHID: DisConnected
*22:18:09* EHID:Socket error
*22:18:13* EHID : DisConnected
*22:18:13* EHID:Socket error
*22:18:18* EHID: DisConnected
*22:18:18* EHID:Socket error
*22:18:23* EHID: DisConnected
*22:18:23* EHID:Socket error
*22:18:28* EHID: DisConnected
*22:18:28* EHID:Socket error
*22:18:33* EHID: DisConnected
*22:18:33* EHID:Socket error
*22:18:38* EHID: DisConnected
*22:18:38* EHID:Socket error
*22:18:43* EHID: DisConnected

Any idea?

[jeehell]

Hi JL, last version installed...
All Cockpitsonic devices dont't work...

This is the hw log



Any idea?

The EHID applciation from uweSchneider is runnning on the same computer?
If yes did you try to restart it?

[asessa]

The EHID applciation from uweSchneider is runnning on the same computer?
If yes did you try to restart it?

Hi JL, yes it run on this pc (FGMS server)

In anycase, I restarted my server and i can see the A320_EHID process run.

Now i read this hw log:

*22:47:45*:HardwareConnect Launched
*22:47:48*:G:\A320FMGS\Hardware Modules\EHIDmodule.dll loaded
*22:47:48*:G:\A320FMGS\Hardware Modules\FSUIPCmodule.dll loaded
*22:47:48*:G:\A320FMGS\Hardware Modules\SkalarkiIO.dll loaded
*22:47:53* EHID:Connected version 15 127.0.0.1

But all devices dont's work in anyway...

The FCU has all digits setted to 0 (QNH=00, SPD=00, HDG=000, ALT="000 2", V/S=nothing)
The RMP has only a dot at left of each displays
The ECAM panel doesn't work

I also tried your EHID_Module.dll you send me few days ago but nothing to do.
I also tried to delete ehid_module.dll into fgms\hw folder and reinstall the suite...nothing to do.

[jeehell]

And if you use previous version it works correctly? There is no reason it would not work anymore...

[asessa]

I tried the v44 e v45.3 and don't work.... i don't know what i have to check...

Now i'll try to reinstall A320_EHID service...

[jeehell]

check you have all the xml A320 IDs installed, as well as the licence from uweschneider in the ehid.ini file...

[asessa]

Now works....
I disinstalled b44 e b45.3 , and reinstalled 45.4.
Restarted the A320_Ehid service

I don't know why but now it works... :/

[SSO]

Hi JL, last version installed...
All Cockpitsonic devices dont't work...

This is the hw log



Any idea?

works fine for me - both HW and SW Clients.
when installing Win10 i had to reinstall EHID.
But no change with the latest FMGS update.
the EHID allows for various levelss of log file details. Look in there for clues.