The difference is huge. Compare these aircraft cfg file...Quote:
Originally Posted by OmniAtlas
Just use my settings ... It'll be fine.
Printable View
The difference is huge. Compare these aircraft cfg file...Quote:
Originally Posted by OmniAtlas
Just use my settings ... It'll be fine.
@Henrik: thanks for your input. It happend again and I could get out of the situation with your procedure.Quote:
Originally Posted by Jerec
@Adonis: When it happend, all 'Off' indicator lights were off on the Overhead panel (hardware and software).
Adrian
Thanks, JL. The reason I'm not using jeeheell_IIT modul is because I cannot assign an action when going to 'on' and an action (same or different) when going to 'off'. May be I used the wrong switches in my Overhead panel. Because the korry switches stay 'on' when pressed and go to 'off' when pressed again. And for simple switches (e.g. Beacon on/off) I only use one input for 'on'. Or maybe I don't fully understand the jeeheell_IIT module configuration. Can you tell me how to configure correct? Thanks.Quote:
Originally Posted by jeehell
Adrian
Hi
@OmniAtlas: Totom is right I think, the PA aircraft "cheats" with the CG I think. So you need something meant for the PA.
@Adrian:
1) For toggle switches (i.e. like the beacon ON/OFF), you only need one input wired to the ON position. And you assign the ON action only (i.e. API_SW_BEACON_ON). I put the OFF action as well as the list is shared for all the hardware modules, and some hardware do not have ON/OFF detection on a single input.
2) Korry switches: the real ACFT uses both ON/OFF (not momentary) switches and MON/OFF ones (momentary).
-You can use yourself both types in your cockpit. In both case, you assign the action to the (M)ON position, and the software will (if necessary) detect the OFF position.
-For the ON/OFF switches of the real ACFT: if you chose to use MON/OFF, you need to select the "toggle action" option instead of the "separate press/release actions" option.
In any case, all korry and ON/OFF toggle switches only need one input on you I/O board.
Some of the 3 positions toggle need an extra input (like LDG lights). And the rotary switches need as many inputs as positions.
Regards,
JL
By the way Adrian, is your OVHD soft on a remote PC? And the EWD?
JL
Hi JLQuote:
Originally Posted by jeehell
Thanks for clarification of the type of switches. I'll check it out and will report the outcome.
Yes, the OVHD and EWD are on different remote PC's.
Adrian
Changing the configuration to 'Project Airbus' in TOPCAT works. No more bouncing aircrafts!Quote:
Originally Posted by ToTom
Yes, I think it works correctly now. At least I don't have an aircraft that lifts at 110 knots anymore and tailstrikes.Quote:
Originally Posted by jeehell
Hi JL,
just a quick question about Open Descent: When I am at CRZ LVL = FL300 and about to start the descent, I am pulling the altitude knob on FCU to trigger OP DES which is displayed in the FMA. I would normally expect the engines go into IDLE and the A/C trying to keep the speed by adjusting the pitch. When I do this at FL300, the engines are not going to IDLE, just slowing a bit down. During descent it is slowing a bit more down the engines, the more I descent the more slowing down the engine settings. Only at around FL240 the engines go into IDLE completely.
Is this how it is in real life? I actually don't know, so maybe it's all like it should be...
Thanks
Stefan
Quick query -- shouldn't your QNH be at the correct value (what you entered in the MCDU) when approaching? When I switch from STD -> QNH it is the same value when I departed.