Hi Rob,
Yes in manual flight, the flare law commands a small pitch down action. This is intended to force the pilot to have a pitch up command on the stick just as he would on a conventional aircraft.
Regards
JL
Printable View
Hi Rob,
Yes in manual flight, the flare law commands a small pitch down action. This is intended to force the pilot to have a pitch up command on the stick just as he would on a conventional aircraft.
Regards
JL
Hi JL,
thanks for you answer. It is indeed the real thing but I could imagine that this pitch down action is introduced more gentle/smooth so the pilot can really counteract by smoothly pulling the stick back.
As far as I know the flare mode the real ACFT remembers the pitch attitude at 50ft RA as a sort of reference attitude. So instead of g-load demand you command a delta pitch which returns to this reference pitch state if you have zero pitch stick input.
Do you agree?
Now, when passing 30ft the real ACFT smoothly goes down to -2 deg pitch att. This pitch down to -2deg happens over 8!!! seconds in the real aircraft. I did not take a stop watch but I have the impression that your FBW introduces the pitch down more rapidly or to a more negative alpha.
So all I want to say is that I have the feeling that your pitch down during flare seems a bit to quick/hard What do you think?
Rob
Hi All,Quote:
Originally Posted by AirFan
I have to same issue too. When I started to flare, the aircraft sets the Pitch Trim to maximum down in about 2 to 3 seconds. After that it's no more possible for me to land the aircraft even with the maximum deviation of the sidestick. This issue occured first as I updated to B30. Did I something do wrong with my config?
All in all it's a great A320 FMGS and it works without any problem except the mentioned issue.
Thanks for all the great work and support Jeehell!
Best wishes,
Sascha
Hi
The pitch down is probably a bit too quick and too hard, but I never experienced a full down pitch trim?
I'll look at that later, I really am busy on the navdata right now...
JL
@ I didnt experience a full pitchj down either... but as I said: I got the feeling that the aircraft derotates too quick. I just wanted to know your opinion about it and if you implemented the described behaviour :) Looking forward for the new nav system.Quote:
Originally Posted by jeehell
Thanks
Robert
Hi JL, i'm trying to program a route, from LIRN to LIME (Naples to Bergamo) and i've this message after i insert this data -> Airway: UM726 , TO VERUN , if i push on the LSK about VERUN point : "MCDU DISPLAY PROBLEM , PLEASE REPORT ISSUE". Could be a problem after i installed the new airac cycle?
Update : if i confirm FPLN (pushing on TMPY INSERT) i don't have the problem.
I don't think so. Probably an FMGS bug.
JL
In anycase, this was the first time i've that message.Quote:
Originally Posted by jeehell
Hi Jl,
since the update to v30 I have always problems to fill in the V2 in the MCDU on INIT B page. It always says "not allowed" when entering 139 for example, it does not accept anything.....
Do you have a clue?
Best regards
Stefan
Hi Stefan
There were no changes regarding V2 in B30 version?
Usually this message appears when you enter a V2 which is too low (below V1 or below minimum V2 for current weight).
Regards,
JL
Hello JL,
After testing a long time I have found the text message "not for commerciale use " caused strong stutter. Is there a possibility to fix this?
Regards,
Micha
Hi
I never noticed that. This is strange. I cannot do much, the message itself is produced by FS directly...
JL
Hello JL,
Thanks for the reply, I have to search in fsx to look for the problem.
Regards,
Micha
Quote:
Originally Posted by jeehell
Hi, i also have this problem...Quote:
Originally Posted by Airmichel
Hi JL
you were right, wrong speeds :-( grrrrr
Best regards
Stefan
Quote:
Originally Posted by jeehell
hi guys,
experienced yesterday and today a strange issue:
short flight LIEE-LIEO.
after filling the f-pln when performing lat revision for the arrival at LIEO, the arrival page did not show up any approach name; scrolling down showed the ils freq on the right hand side, but the left hand side reported NO app names and identifiers. line selecting any approach line caused an error in fmgs server (access violation).
replicated today in the same way.
i don't have the latest navigraph airacs but just the last month's ones...don't know if this issue is related to the nav database thing.
anyone else ecperienced this? (maybe antonio?)
or jl can u replicate it if u find any spare time?
all the best
filippo
Hi Filippo, i can try this weekend, i have last navdata on board.Quote:
Originally Posted by filippoporcari
Hi Filippo, i'm trying to program from LIRN to LIEO and i've same problem but i solved choosing 24 in arrival page, then FMGS show stars and it works fine.
yes antonio,
but if u choose just 24 u select just a rwy and not an approach.
there is something wrong there
regards
fil
Hi Filippo , after i choose 24 the fmc show me all stars for that rwy. Try ;)Quote:
Originally Posted by filippoporcari
Hi,
I think it will be solved in next version.
Regards,
JL
antonio....i'm not talking about seeing the list of the STARS i wanted the list of the ILS APPROACHES to choose from...if u don't select an ils approach from the ils list it's hard to fly the procedure on an airbus :-)
@JL: thanks a lot as usual!
cheers
fil
Hi Filippo, i understand it....but when i choosed 24 -> SUKUN1A the ILS was set in NAV/RAD Page correctly and i landed with autoland with no problems.Quote:
Originally Posted by filippoporcari
However i think is a navdata problem , because it is only with LIEO approach procedures.
@JL , thanks
yes antonio, definitely a navdata issue as jl explained.
what i meant about your workaround choosing just rwy 24 is that u cannot choose the approach: at lieo and at many airports there are many...and u choose them from the letter identifier.
agree with me that having the ils freq and course autotuned in the nav rad page is not enough to fly an approach?
did u have all the fixes in the fplan page after your workaround? ...don't think so...
how can u choose for example if landing on rwy 05 the straight in ils...or the procedure turn ils?
can't wait to test the next release with own airacs from aerosoft.
regards
fil
After i selected 24 then SUKUN1A (if i remember well) i had all points (but they were incorrect in comparison to the charts) .Quote:
Originally Posted by filippoporcari
In any case, this was the first time i had this problem and only at LIEO.
I reported you how i done only for a test, i know is not a correct action (but keep in mind the approach with an Airbus is different than Boeing, you can't fly [for example] an arc in standard mode like you do it with a boeing , you don't have the ability to fly radials in standard mode and so on ;))
Regards
antonio: i definitely know the differences between boeing and airbus...i'm actually studying the 4 volumes of airbus FCOM and the FCTM volume...knowing the differences i wrote that u NEED to select the correct approach with the correct identifier from the mcdu before flying that precise approach.
anyway we're going offtopic now :-)
cheers
filippo
Hi Jeehell
pair of questions:
1) in beta 28 I loaded the sid stars procedures modify tool but it doesnt work, have you changed something there?
2) I made some tests in the software and I went amazed when tried the emergency electrical configuration, so, how many ECAMs are implemented by now? do you have a list of them to contribute with some test with FCOM at hand?
3) the overspeed warning for flaps is not working , intentionally I exceeded the 230 kt limitation for F1 and I didnt get the CRC, any idea?
Keep up the good work as usual ,and thanks in advance.
Adonis
Hi,
1) no but I havent looked at that for ages, and will disappear in next version anyway...
2) I do not have a list, it is for you all to find out ;)
3) Not all warnings are implemented yet
Best regards,
JL
Hi JeehellQuote:
Originally Posted by jeehell
well time to start doing weird things to the plane to find ecams, and of course crosscheck on the plane and ley you know
;)
So if the sid stars tool will bit be working in the future
do you know any tool to add ir edit sids for example to add an engine out sid?
Regards
Adonis
Hmmm EOSID are not implemented, and I'm not sure I will add them.
Reason is as you know EOSID are company tailored. And no FS navdata providers give any EOSID.
Also, I don't think there will be any way to modify/add procedures in the database, at least in the near future.
Regards,
JL
+1 JL...
there are no glass cockpit suites on the market (both boeing & airbus style) which implement EOSIDs for the reason well explained by JL: company custom tailored.
cheers
fil
Hi jeehell
as always thanks for your great support
Working on version 30 I have noticed some lags over the network specially with pfd nd and ewd, I have cleaned up firewalls, antivirus updaters and everything, even i went back to fs9 to check if things speeeeds up, but some intermitency remains.
Any suggestions about a preferend port for the network or any trick to improve network lags?
Also is beta 30 the latest version or is there an upgrade im not aware of?
Best regards
adonis
Hi,
B30 is the latest version, there were no upgrades for some weeks now.
So far you're the first I think who experienced more lag with B30 than the previous version? if others have feedback on that...
There is no particular trick, a good port is a port which does work.
Best regards,
JL
Quote:
Originally Posted by filippoporcari
Hi,
In B30 I have lost the Runway ILS in many airports. Example ILS 16 is now nav rad 16.
HI JL,
A few days ago I started planning the first phase of an instructor station.
The first part is reserved for fault management.
I found some things that could help me to clarify.
for the engine failure I used the standard FSUIPC offsets, but indications on ECAM are not always equal.
For example, the management does not display some of the levers and start idle valve, and does not continue with the list on the display card.
is a problem of offset, or you have reserved a particular offset list?
The project provides a first part for fault management, and thereafter the weather and ground control.
If you have a list of offsets dedicated to this type of work, where can I find it?
Regards
Daniele
Hi JL,
one thing about the barometric switch on FO side: When this is set to Hg mode and is then pulled, it goes to standard which is fine. If it is pushed later, it's displaying somthing around zero. It then takes minutes to turn back to the right pressure again. In hPa mode this is working fine, and on CP side it's working fine in both modes.
Thanks for looking into this.
Stefan
hi JL,
i was guessing if the APP NAV approach mode is fully implemented in your suite: i've flown a couple of vor approaches but when pressing the app button on the fcu i get the APP NAV annunciated on the fma but no way to have the FINAL annunciated and of course engaged. moreover i have the amber ILS flashing on the pfd. am i missing something or the vertical FINAL mode is just not yet implemented?
thanks a lot
filippo
Hi,
@Startrail:everything concerning navdata is changing in next version, until then we'll all have to wait.
@Daniele: the ECAM messages available are only those which results of wrong actions under normal conditions (i.e. no failures: a switcvh off when it should be on...). There is no way to trigger any failure otherwise.
@Stefan:I'll try to have a look...
@Filippo: as you noticed, the APP NAV and FINAL mode are not yet fully implemented. I am working on that for next version.
Best regards,
JL
thanks for your quick reply!
imagined that u were working on it...just wanted to be sure i was not doing something wrong on my side.
thanks a lot for your work!!!
all the best
fil