Dimmer is already supported for all EIS.
ECAM swtiching will come later, it's not trivial at all.
Regards,
JL
Printable View
Dimmer is already supported for all EIS.
ECAM swtiching will come later, it's not trivial at all.
Regards,
JL
I would like to request that feature if possible -- was it very buggy and had to be removed?Quote:
Originally Posted by jeehell
Thank you JL -- I have officially switched and sold most of my Boeing hardware; and your software was a large part of that decision.
Hi,
just a quick question about baros on CP + FO side and their connection to AP 1 and 2. Let's say both baros are setup to different values and the A/C has leveled off. I would think that if AP1 is engaged, the A/C would try to establish the altitude based on CP's baro, and if AP2 is engaged the A/C would try to establish the altitude based on FO's baro and FO's current altitude as shown on FO's PFD.
Am I wrong? It looks like the A/C always follows the current altitude on CP side, even if AP2 is engaged only.
Thanks
Stefan
HI,
You are probably right, but this is not a priority item for now. Also, I need to be sure exactly how each FMGC and FD gets its air data.
Regards,
JL
JL i'm using skalarki hardware...the PFD and ND dimmers act strange.
ND dimmer: turning counterclockwise it dims to black but reaching the extreme position gives full bright again.
PFD dimmer: turning counterclockwise dims to black but reaching extreme position it switch the PFD/ND xfer switching the displays.
axis correctly calibrated in profiler...reported to marcin as well but he said everything looks correct on his side.
HI
the auto PFD XFR to ND is normal when you turn the PFD OFF.
I'll have a look at the ND dimmer when at 0.
JL
thx JL...
airbus features keep amazing me :-)
btw...after today's update at fmgs startup the HC does not connect to skalarki (on its window it says NOT RESPONDING) if manually shutting it and restarting everything is fine.
regards
fil
nevermind jl...re running fmgs HC is running as it should and comnecting correctly to profiler...don't ask me why :-)
regards
fil
i was wrong jl!
hardwareconnect keeps hanging at startup...it says waiting for client in its window...the log does not contain anything particular more than saying SKALARKIIO.dll client connected....then disconnected....then connected...many times ending in WAITING FOR CLIENT
last update...after rebooting the pc HC works...i'll report again should it fail...sorry for this!
filippo