A320 FMGS B38

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