A320 FMGS beta 30

[jeehell]

@Umberto: Why can't you use SIOC Creator?? Anyway, I'll try to add the fire buttons in FSUIPC module for next version.

@Stefan: should be corrected in next version (if it's what I'm thinking).

JL

[stefangr]

Hi,

I am trying to plan a flight from EDDH to LEIB using this route:
EDDH IDEKO Y900 TIMEN UL126 WRB UN850 POS LEIB

This is what the MCDU shows afterwards:
mcdu_alt.PNG

At TIMEN it shows an altitude of 2000 which is continued all the way until the destination. I have inserted a cruize level of FL340. How does this happen?

Thanks
Stefan

[jeehell]

Hi,

The VNAV is not perfect, and sometimes there can be errors. I tried your route though, and it worked correctly on my computer. I do not where the error lies. What did you enter in the MCDU (INIT A/B and PERF)?
JL

[stefangr]

Hi,

The VNAV is not perfect, and sometimes there can be errors. I tried your route though, and it worked correctly on my computer. I do not where the error lies. What did you enter in the MCDU (INIT A/B and PERF)?
JL

I tried once more, getting the same effect. This is what I entered:

INIT:
Attachment 7677 Attachment 7678
PERF:
Attachment 7679Attachment 7680
F-PLN:
Attachment 7681Attachment 7682Attachment 7683Attachment 7684
SID:
Attachment 7685
STAR:
Attachment 7686

Maybe I am doing anything wrong? Thanks for your help.
Stefan

[jeehell]

Did you leave any FPLN Discontinuity? those must be removed.

JL

[stefangr]

Did you leave any FPLN Discontinuity? those must be removed.

JL

No, discontinuities were all removed.

Stefan

[stefangr]

Maybe it has anything to do with SID or STAR? I am currently on crz level from LEBB to EDDS, FL330, but MCDU shows me 4000 feet altitude for all upcoming waypoints. 4000 is the constraint of the first STAR waypoint.

Stefan

[Arbizzano]

@Umberto: Why can't you use SIOC Creator?? Anyway, I'll try to add the fire buttons in FSUIPC module for next version.

@Stefan: should be corrected in next version (if it's what I'm thinking).

JL

Hi JL,
I can use your SIOC Creator, but I must add my SIOC code because the new Opencockpits IOCards outs has been designed to expand the IOCard Master outputs with 32 outputs more for each additional IOCard Outs connected.The card is connected directly to IOCard Master's port J1 through a 40-wire ribbon cable IDC type, just like the IOCard Displays II and to turn-on an output you must indicate the number of the display and not the output number.
In your SiOC the panel is already provided but may indicate only outputs.
So I thought of using the variables of the fire protection panel to turn on the lights by writing the appropriate code.

Bye

Umberto

[jeehell]

@Stefan: yes maybe there is an issue with your AIRAC, which date is it? try deleting the ALT CSTR.

@Umberto: Ok I see, I wasnt aware of that. I'll see if I can do anything, though it might be a lot of work to add that feature. I need to get some info on these new boards.
I confirm next will have the fire sw/leds in the FSUIPC module.

Cheers,
JL

[stefangr]

@Stefan: yes maybe there is an issue with your AIRAC, which date is it? try deleting the ALT CSTR.

I will install the new AIRAC Cycle at the weekend, will check then once more.

Thanks
Stefan