A320 FMGS B38

Quote:

---

Originally Posted by AirbusMike

Hi all,

JH thanks for the new version I've tried now but I still have no NDB, VOR APRT or WPT on the remote PC's
I've tried serveral WIN 7 64B pc's and all have the same issue. If I start the ND on the FSX computer where the
server is running I can see all the NDB, VOR APRT and WPT...

The actions I did:


removed the anti virus software
turned off the fire wall
disconnected the router

but no luck....

I'Ve tried the default port configuration and I saw a error on Port 8005

**12:3:42.720**port 8005:192.168.0.163 connected
**12:3:42.720** fmaps send timeout.
**12:3:55.125**port 8005:192.168.0.167 connected
**12:3:55.125** fmaps send timeout.

after this I've changed the ports to

9610, 9613, 9621 and 9622 because they should be free accoding to the internet steatments

I did start everything but still the same issue no NDB, VOR APRT or WPT.

Here my error logs:

*****WideFMGSserver started at:13:55:48.156
**14:1:35.802** port 9610:192.168.0.167 connected
**14:1:35.803** port 9613:192.168.0.167 connected
**14:1:35.803** port 9621:192.168.0.167 connected
**14:2:44.755** port 9610:192.168.0.163 connected
**14:2:44.755** fmaps send timeout.
**14:2:44.756** port 9613:192.168.0.163 connected
**14:2:44.756** port 9621:192.168.0.163 connected

First CLient PC

*****WideFMGS client started at:14:1:29.142
Create result:1
Host IP: 192.168.0.10
**14:1:30.534** Port 9622: connected
**14:1:33.576** Port 9621: connected
**14:1:33.576** Port 9610: connected
**14:1:33.576** Port 9613: connected

Second Client PC

*****WideFMGS client started at:14:4:3.338
Create result:1
Host IP: 192.168.0.10
**14:4:4.648** Port 9622: connected
**14:4:7.487** Port 9621: connected
**14:4:7.690** Port 9610: connected
**14:4:7.690** Port 9613: connected

ANd NAV Data Log




*13:55:49* Navdata module launched Server
*13:55:49*
*13:55:51*
*13:55:51* Navdata1:
*13:55:51* -ARPTliste:15372
*13:55:51* -NavaidListe:18180
*13:55:51* -FIXliste:186502
*13:55:51* -AWYsegments:97710
*13:55:51* -MarkerList:2505
*13:55:51*
*13:55:51* Navdata2:
*13:55:51* -ARPTliste:15372
*13:55:51* -NavaidListe:18180
*13:55:51* -FIXliste:186502
*13:55:51* -AWYsegments:97710
*13:55:51* -MarkerList:2505
*13:55:51*
*13:55:51* server started on port:9622
*14:01:32* Client connected: 192.168.0.167
*14:01:34* Client connected: 192.168.0.167
*14:02:41* Client connected: 192.168.0.163
*14:02:43* Client connected: 192.168.0.163
*14:02:43* Client connected: 192.168.0.163

Can someone help me with this? What do I wrong here?

Many thanks in advanced!

Mike

---

Hi Mike

did you start all apps with adminright's, that was what I found out, my account is local admin but I need to use right click on starter.exe and have to choose start as administrator, then it worked.

BR
Stefan

Hallo Mike,

did you following this installation steps?

Jl changed the Navdata since Version 38.3

Quote:

---

-Reworked navdata loading:

---

Quote:

---

*Navdata is computed from Aerosoft format to a direct format by the FMGS Server after each AIRAC cycle update
*This process creates .bin files in the Navdata folder (ARPT.bin,FIX.bin, etc)
*These files must be copied on your client computers in the same navdata folder
*If you change scenery or else, you need to delete the files on the server computer to re-generate them (then copy them again).
*If you update the airac cylce manually into navdata\navdata1 and navdata2 folders, you'll have to erase the bin files manually as well.

---

Made two short test flights yesterday and all (without the displayed disconnection but working clients) works very fine and nice!
BIG THANK YOU FOR YOUR HARD WORK AGAIN!
Looking forward to your next steps, like maybe a weather radar? . ;):p

Cheers Florian

Thanks Stefan, I run it under admin rights..

Hi Florian,

this was the missing link, I didn't copy those files to the remote pc's... done and now it work very well :p

You guys so cool thanks for your help!

Mike

Hi JH and Guys,
have anybody a idea because of my crashing P3D when i start the Jeehell Server? Or how i can finde out what goes wrong?
Slowly it makes me crazy. :(and i´m really frustrated. Sometimes it works without any problems, sometimes i try more as a half hour to start the server without a crash and suddenly it works again. Firewall, Antivir all are off.
Got now also the newest P3D Version... all Windows and Graphic-Updates.... newest JH Ware...

Help me Obi-Wan, your are my last hope! :/

Florian

Using the latest P3D 2.5 with the hotfix? Have you updated FSUIPC?

Hi Omni,
Yes with the hotfix and fsuipc is also up to date.

cheers
Florian

Hi all

Is it ok to run the Starter.exe respectively the StarterFSX.exe with admin privs or does every single .exe need to have admin privs?

And how do you run an .exe with admin privs as an autorun at Windows start (eg. out of the Startup folder)?

Cheers
Greg

Quote:

---

Originally Posted by Gregor

Hi all

Is it ok to run the Starter.exe respectively the StarterFSX.exe with admin privs or does every single .exe need to have admin privs?
Greg

---

I believe only StarterFSX is enough.

Quote:

---

Originally Posted by Gregor

And how do you run an .exe with admin privs as an autorun at Windows start (eg. out of the Startup folder)?

Cheers
Greg

---

See here:
http://www.tekrevue.com/tip/always-r...administrator/

Thanks for your advices.

The "Run this program as an administrator" checkbox however only helps if you start the application manually but not if you want to have it started automatically at windows startup (at least I have not found a solution therefore).

Cheers
Greg

Oh Oh Oh OH Guys.... :roll:

Big Big fu...... misstake from me. This is so embarrassing that i have told you so annoyed all the time. Really stupid from me!!! :(

I find out my problem....
Long time ago i changed the default ports because got some other issues....
In the last hour i made an complete fresh and clean installation of Jeeheel and saw that the default Ports are usually other!
Changed all to default... all works without any crash and clients displayed as connected. :-|

I`ll thump me with the hammer to the head! BIG BIG SORRY FOR THIS GUYS!!!

But i find a small issue with the SIOC Creator...
It doesn´t saves the "Use SWTCHG/RUDDER TRIM" when i enabled it.

AGAIN: A BIG SORRY FOR THIS AND THX FOR YOUR PATIENCE!

Cheers
Florian

Hello everybody,

I'v got a problem with the MCDU modul. When I press the PROG or PERF key the following error message is displayed

MCDU DIPLAY PROBLEM PLEASE REPORT ISSUE


All other keys (and modules) work fine.



Version B38.3 is installed but I face the same issue with older versions. The MCDU is running on a touch screen monitor (10 inch) but with a normal TFT I get the same error message. And there is no difference using the mouse or my fingers to press the button.
As I'm still testing A320FMGS is running on a single PC.

Regards

Mario

Quote:

---

Originally Posted by emani

Hello everybody,

I'v got a problem with the MCDU modul. When I press the PROG or PERF key the following error message is displayed

MCDU DIPLAY PROBLEM PLEASE REPORT ISSUE


All other keys (and modules) work fine.



Version B38.3 is installed but I face the same issue with older versions. The MCDU is running on a touch screen monitor (10 inch) but with a normal TFT I get the same error message. And there is no difference using the mouse or my fingers to press the button.
As I'm still testing A320FMGS is running on a single PC.

Regards

Mario

---

Hi Mario,

I had the same with 38.3 but with 38.4 the problem is gone

BR Mike

Hi Folks,

I've a small question concerning the FSUIPC pipe &H78EE (OVHD input) as soon as I write a command the input
from the graphical OVHD does stop working but the lights are working.. Is there an option to have both inputs?
(I'll try to wirte my own driver for my cockpit hardware and sometimes it's good to have both running for testing :p)

BR Mike

@AirbusMike: I see no reasons for the OVHD UI to stop working, can you elaborate a bit more?

regards,
JL

Quote:

---

Originally Posted by jeehell

@AirbusMike: I see no reasons for the OVHD UI to stop working, can you elaborate a bit more?

regards,
JL

---

Hi JL

I had the OVHD UI running and did turn on the couple of things with the mouse (like EXT PWR etc..) and it worked find
The UI was stil running and I did send one byte to 78EE (value 47 for Pack 1) and the PACK1 light on the UI turned on and
off as expected but after this all mouse inputs on the UI didn't work anymore..
I did close and restart the UI but no change... but the FSUIPC input did still work and the light on UI did respond
That looks to me that the FSUIPC inputs were processed.

There is one more question from my side is it possible to have not only toggle commands for the Korry switches
a few in the ovhd are also alternating switches (solid ON or OFF position like fuel pumps flt controls packs etc)

like
78EE value 47 (Pack 1 TOGGLE)
78EE value XXX (Pack 1 ON)
78EE value YYY (Pack 1 OFF)

That would be really nice :D

best regards
Mike

Hi all
since the last update my system crashes without an error message. all systems are no longer usable after take off. using all Skalarki HW. Is there a error log file which tells me why all systems (FCU, MCDU, RMP etc.) are not responding anymore?

Regards
Stefan

@Mario and Stefan: did you upgrade to 38.4 by first using the full installer ( http://www.jeehell.org/A320FMGS_B38.4.exe ) then doing the auto updates?

@Airbus Mike: I tried the FSUIPC module alongside the OVHD UI and I do not have any issues. It is not possible to add the full ON/OFF logic for all korries in FSUIPC module. You'll have to do some sort of synchronization yourself (it's not too hard to do since the OVHD panel always starts in the same SW state).


JL

Hi JL,

yes I did, and before all systems are inop I see the message on the MCDU Display problem... like emani wrotes. That is real strange because all went fine so far.... all freezes and no knob is functioning. No error message, so I can't tell what is the problem. I may need to install again a fresh installation on all systems. Will check during thze weekend and report out come.

BR
Stefan

Strange, did a clean install but Navigation does not create .bin files. Do I need to start a special exe?
regards
stefan

After last autoupdate, which required the B38.5 installation, my EHID MCDU is blank.
I already tried to restart EHID service (sometimes it helps) but it's still all blank.

The MCDU is indeed initialized since the bootup logo goes away but then remain blank and do no react to any keypress.

Any advice?

Thanks

Stefano

Quote:

---

Originally Posted by Miatanet

Strange, did a clean install but Navigation does not create .bin files. Do I need to start a special exe?
regards
stefan

---

Not sure exactly what you did?
The process for the navdata files:
*Navdata is computed from Aerosoft format to a direct format by the FMGS Server after each AIRAC cycle update
*This process creates .bin files in the Navdata folder (ARPT.bin,FIX.bin, etc)
*These files must be copied on your client computers in the same navdata folder
*If you change scenery or else, you need to delete the files on the server computer to re-generate them (then copy them again).
*If you update the airac cylce manually into navdata\navdata1 and navdata2 folders, you'll have to erase the bin files manually as well.

Quote:

---

Originally Posted by krosa

After last autoupdate, which required the B38.5 installation, my EHID MCDU is blank.
I already tried to restart EHID service (sometimes it helps) but it's still all blank.

The MCDU is indeed initialized since the bootup logo goes away but then remain blank and do no react to any keypress.

Any advice?

Thanks

Stefano

---

Did you try running the software MCDU to see if that one works?

JL

Hi Jl,
today i made the last update. Alle works fine for me! ;)
But the only small thing with the SIOC_CREATOR still be there. When i start the SIOC-CREATOR and load a before saved config file where are the F/O MCDU assigned with the IDX2 and enabled Switchingpanel, this two things are every time lost. So i must assigned the F/O MCDU with IDX 2 and enabled the Switchingpanel again before i apply this configuration.

Cheers
Florian

Quote:

---

Originally Posted by jeehell

Not sure exactly what you did?
The process for the navdata files:
*Navdata is computed from Aerosoft format to a direct format by the FMGS Server after each AIRAC cycle update
*This process creates .bin files in the Navdata folder (ARPT.bin,FIX.bin, etc)
*These files must be copied on your client computers in the same navdata folder
*If you change scenery or else, you need to delete the files on the server computer to re-generate them (then copy them again).
*If you update the airac cylce manually into navdata\navdata1 and navdata2 folders, you'll have to erase the bin files manually as well.

---

Sorry JL,
did not know that after update from 38.4 to 38.5 I need to re-install Aerosoft NavData again, just checked and the Nav1 and 2 were empty....

Now it works, and MCDU is up to date :-). Now I am testing the rest and hope my problems are history ...

BR
Stefan

Quote:

---

Originally Posted by jeehell

Did you try running the software MCDU to see if that one works?

JL

---

Hi JL,

yes I tried...the software MCDU is working correctly but the hardware MCDU is always blank.
I looked into the HClog but it seems all ok

Code:

---

*13:52:39*:HardwareConnect Launched
*13:52:42*:CPFlightmodule.dll loaded
*13:52:42*:EHIDmodule.dll loaded
*13:52:42*:FSUIPCmodule.dll loaded
*13:52:42* JeeHell_IIT:Get Log Proc
*13:52:42* JeeHell_IIT:End of Start procedure
*13:52:42* JeeHell_IIT:Get SW Proc
*13:52:42* JeeHell_IIT:Get Analog Proc
*13:52:42*:JeeHell_IIT.dll loaded
*13:52:42* JeeHell_IIT:7seg except
*13:52:42* JeeHell_IIT:7seg except
*13:52:47* EHID:Connected version 10 127.0.0.1
*13:55:27*:HardwareConnect closed

---

Please let me know if there's anything I can do to help in debug.

Thanks

Stefano

Quote:

---

Originally Posted by krosa

Hi JL,

yes I tried...the software MCDU is working correctly but the hardware MCDU is always blank.
I looked into the HClog but it seems all ok

Code:

---

*13:52:39*:HardwareConnect Launched
*13:52:42*:CPFlightmodule.dll loaded
*13:52:42*:EHIDmodule.dll loaded
*13:52:42*:FSUIPCmodule.dll loaded
*13:52:42* JeeHell_IIT:Get Log Proc
*13:52:42* JeeHell_IIT:End of Start procedure
*13:52:42* JeeHell_IIT:Get SW Proc
*13:52:42* JeeHell_IIT:Get Analog Proc
*13:52:42*:JeeHell_IIT.dll loaded
*13:52:42* JeeHell_IIT:7seg except
*13:52:42* JeeHell_IIT:7seg except
*13:52:47* EHID:Connected version 10 127.0.0.1
*13:55:27*:HardwareConnect closed

---

Please let me know if there's anything I can do to help in debug.

Thanks

Stefano

---

Quick update: I just noticed that the key pressed on the hardware MCDU are correctly handled by the software MCDU so I suspect that the problem may regard just the output/rendering part.

Thanks

Stefano

Hi JL

So, tested all system and flew from EDDM to EDDl without any problems. All fine so far :-).

Regards
Stefan

Quote:

---

Originally Posted by krosa

Quick update: I just noticed that the key pressed on the hardware MCDU are correctly handled by the software MCDU so I suspect that the problem may regard just the output/rendering part.

Thanks

Stefano

---

Hi

it should be solved with current auto-update.

regards,
JL

Hi everybody, hi JL, I a truly great fun for the new update B38.5, everything seems to be working great, except for the terrain on ND. I have only tried the CPT side, but when I turn it on, I get an access violation which freezes the ND, until I clear the access violation and reset the ND. Anybody getting this? Do I need to reinstall the terrain data? My setup is the CPT and FO PFD and ND are on one remote computer, and two other computers work the FSX and the rest of the sim.

Jose

jose if u check the bug tracking there's a long report about this...some users are having the access violation and others not.
it looked like nvidia drivers related but actually seems not
regards
fil

Thanks fil, I guess I do remember reading that before, sorry for posting about it again.

Jose

Hi JL,

I've a small question concerning the TERR ON ND

If I send "WriteToFSX 1, &H78ED, 43" (thats my FSUIPC function in VB) the TERR is displayed on the CPT ND. If I now send the same command nothing happens. The TERR is still displayed on the ND.
I thought it's toggle but maybe it's different. I can only turn the TERR ON ND off if I use the
MCDU function. What do I wrong here or did I simply oversaw something? And do you have an FSUIPC offset for the
TERR ON ND light CPT & F/O.

Many thanks!

Best regards
Mike

BTW the OVHD UI and my own hardware working in paralell, I'm not sure what I did wrong last time :)

Quote:

---

Originally Posted by AirbusMike

Hi JL,

I've a small question concerning the TERR ON ND

If I send "WriteToFSX 1, &H78ED, 43" (thats my FSUIPC function in VB) the TERR is displayed on the CPT ND. If I now send the same command nothing happens. The TERR is still displayed on the ND.
I thought it's toggle but maybe it's different. I can only turn the TERR ON ND off if I use the
MCDU function. What do I wrong here or did I simply oversaw something? And do you have an FSUIPC offset for the
TERR ON ND light CPT & F/O.

Many thanks!

Best regards
Mike

BTW the OVHD UI and my own hardware working in paralell, I'm not sure what I did wrong last time :)

---

Hi,

@All : I'm aware some have this bug with ND/EGPWS. I cannot reproduce it, it seems it is hardware/driver related.

@Mike: I corrected the switches actions. I also added the LEDs to the offset 0x73AB bits 3 & 4 (the offset lists in the sticky HELP thread is up to date).

Regards
JL

Quote:

---

Originally Posted by jeehell

Hi

it should be solved with current auto-update.

regards,
JL

---

Hi JL,

just to confirm that the MCDU is working correctly after the last autoupdate.

Thank you again for your super quick fix.

Regards,

Stefano

Quote:

---

Originally Posted by turbovela

Thanks fil, I guess I do remember reading that before, sorry for posting about it again.

Jose

---

Solved with the latest eis.exe! http://www.jeehell.org/EIS.exe

Quote:

---

Originally Posted by jeehell

Hi,

@All : I'm aware some have this bug with ND/EGPWS. I cannot reproduce it, it seems it is hardware/driver related.

@Mike: I corrected the switches actions. I also added the LEDs to the offset 0x73AB bits 3 & 4 (the offset lists in the sticky HELP thread is up to date).

Regards
JL

---

Dear JL,

works perfect many thanks for your incredible work :)
and thanks for the hint with the sticky HELP thread!

Best regards
Mike

hi jl,
from version 38 onward experienced two fmgs server crashes i never experienced in the past.
first time right after takeoff...yesterday right after touchdown.
no windows error message for it but it crashed and server could only be hardly killed from task manager.
is there any log/report i can provide u to understand where it came from?
cheers
fil

Hi Fil,

the FMGSserverLog.txt may be useful.

JL

Hi,
just updated from B37 to B38.8, seems I´m pretty late with it. But now both MCDUs (Software, on other PC) remain black even when APU is running, while PFD, ND and ECAM (on Server PC) come alive. Back to B37 the CDUs work as usual. Does anyone have the same problem?
The Server required a full new install, while the Client was updated by the updater. Did I make something wrong? THX for any help!
Regards Rainer