A320 FMGS B31

[startrail]

Thanks a lot. Will advise FSCOCKPIT.

[romeow]

So do I! Make assurance double sure
René

[stefangr]

Hi,

When this happens, you can try to do the following:
- close FMGS Server and ND
- go to task manager-> services tab
- look for FMGSnavDB service and do right click->stop then right click ->start.
-Run server and NDs again.

Regards,
JL

Hi JL,

I am having the same problem as well, and your workaround helps. But I need to do that every time after the PC has started. Is there any chance to avoid this?

Thanks
Stefan

[Leonidas]

Hi,
@Leonidas: please download this one: http://www.jeehell.org/EHIDmodule.dll it should correct the ALL button issue.
As for the buttons LEDs, if I remember correctly we never had this one settled down. I'll contact you by mail.
Regards,
JL

Yes, the ALL button issue corrected, but the other buttons don't work yet.
I don't know if it has some relation with it, but the PFD at two clients don't close after I shut down the FMGS server. (Message: "Aceess violation at address...")
Regards

[jeehell]

Stefan, I'm still looking into it. I do not know why it won't correctly load on your system, I personnaly do not have any issues with it...
There should be a log file inside navdata folder, can you post it?

Leonidas: the issue you mention is not related to the ECAM issues.
JL

[startrail]

HI JL

AFTER INSTALLING B31.1 HAVE TRIED TO CALIBRATE SAITEK BRAKES BUT COULD NOT. ON PRESSING THE TOE IT JUST FREEZES ON THE FULL DOWN BUT NEVER RETURNS IN ORDER TO CALIBRATE FULL AFT. HAVE TESTED ON THE COMPUTER SYSTEM AND ARE OPERATING PERFECTLY.

ON THE OTHER HAND , I AM UNABLE TO SAVE THE ROUTES.


THANKS

[jeehell]

Hi,

Sometimes the calibration gauge "freezes" but the numeric value is still showing the correct value, please check that.
There are no other users reporting issues with these particular axes.

The CO/PIL RTE function was deactivated on purpose, I'll put it back in a future version.

Regards,
JL

[stefangr]

Hi JL,

I will send you a log file as soon as I make the next test.

Is it possible that the EFOB calculation on the FPLN page of MCDU is not correct? It is always very different to the one on FUEL-PRED page, sometimes 3 or 4 tons below, sometimes above. It looks the FUEL-PRED value is OK.

Besides that: thanks for the new version, very good!! What I like especially:
- Rudder trim calibration on FO side is working great now
- I have my triple click back again after disconnecting A/T or A/P
- Traffic display for FS9 on ND was fixed and I can use TA/RA mode again
- ND is running very smooth

Thanks!
Stefan

[jeehell]

Hi,

Yes the are issues with ful calculations, I'll work on them on future versions, it has always been very difficult to get accurate results in all conditions.

JL

[stefangr]

Hi JL,

thanks for your efforts. I am having once more question regarding the NavData and entering a route in MCDU. I am trying to enter the following route which was generated by PFPX:

EDDF TOBA8D TOBAK Z10 GISEM N850 PIROT UL126 ROBEG N850 NIE Z88 VERED VERE2P EDDW

This is what I do in MCDU on Flight Plan page (after setting up INIT page etc.):
- Enter waypoint TOBAK
- Select entered waypoint, choose AIRWAYS
- Enter 1st airway Z10
- Enter 2nd airway N850 -> MCDU responds with "GISEM" in column "TO" (which matches the above routing)
- Enter 3rd airway UL126 -> MCDU reponds with "MIC" in column "TO" (which should be PIROT according the above routing).

Is anybody else encountering the same problem? Is there anything I am doing wrong?

Thanks
Stefan