A320 FMGS B34

[OmniAtlas]

Hi,

@OmniAtlas: are you sure you actually do not have any windshear?

It is happening very frequently (nearly every other landing), might just be OPUS changing weather when I'm landing...I think I'm about to give up on OPUS and try a different weather program instead.

[SSO]

You do not get optimum performance with the engines, the aircraft will fail to climb and maintain its altitude/speed.

Because of a windsmooting parameter? That sounds VERY odd. The smoothing is made to give a more realistic movement from zone to zone or to WX updates.
Why does that affect the FMGS behaviour?

[SSO]

It is happening very frequently (nearly every other landing), might just be OPUS changing weather when I'm landing...I think I'm about to give up on OPUS and try a different weather program instead.

Im using Opus w P3Dv2.2. Works perfectly for me

[OmniAtlas]

Because of a windsmooting parameter? That sounds VERY odd. The smoothing is made to give a more realistic movement from zone to zone or to WX updates.
Why does that affect the FMGS behaviour?

Hi Stephen, Not too sure why it affects the aircraft dynamics -- you can try turning on the parameters in FSUIPC and see if it has the same detrimental effect.

[SSO]

Hi Stephen, Not too sure why it affects the aircraft dynamics -- you can try turning on the parameters in FSUIPC and see if it has the same detrimental effect.

Here is my FSUIPC.ini:

[General]UpdatedByVersion=4929
History=K55VG1EKKMMX8Q1LHVN8D
AxesWrongRange=No
TCASid=Flight
TCASrange=40
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
AxisIntercepts=No
DontResetAxes=No
InitDelay=0
GetNearestAirports=No
OOMcheck=Yes
WeatherReadFactor=2
WeatherRewriteSeconds=1
CustomWeatherModify=No
SimConnectStallTime=1
InitialStallTime=10
NormalStallTime=1
LuaRerunDelay=66
Console=No
InitDelayDevicesToo=No
UseSystemTime=No
UseMidMouseBtn=Yes
MouseWheelMove=No
MouseWheelTrim=No
MouseWheelTrimSpeed=1
JoystickTimeout=20
PollGFTQ6=Yes
BlankDisplays=No
FixControlAccel=No
FixMachSpeedBug=No
DeleteVehiclesForAES=Yes
AutoScanDevices=Yes
VisibilityOptions=No
OneCloudLayer=No
CloudTurbulence=No
CloudIcing=No
GenerateCirrus=No
SuppressCloudTurbulence=No
MaxIce=-4
MinIce=-4
UpperWindGusts=No
SuppressWindTurbulence=No
SuppressWindVariance=No
WindTurbulence=No
TurbulenceRate=1.0,5.0
TurbulenceDivisor=20,20,40,40
SuppressAllGusts=No
MaxSurfaceWind=0
WindLimitLevel=200
WindDiscardLevel=400
WindAjustAltitude=No
WindAjustAltitudeBy=2000
SmoothBySimTime=No
WindSmoothing=No
WindSmoothness=2
WindSmoothAirborneOnly=Yes
PressureSmoothness=0
TemperatureSmoothness=0
DisconnTrimForAP=No
ZeroElevForAPAlt=No
ThrottleSyncAll=No
WhiteMessages=No
ShowPMcontrols=No
SpoilerIncrement=512
MagicBattery=No
RudderSpikeRemoval=No
ElevatorSpikeRemoval=No
AileronSpikeRemoval=No
ReversedElevatorTrim=No
ClockSync=No
ClockSyncMins=5
ClearWeatherDynamics=No
OwnWeatherChanges=No
TimeForSelect=4
LoadFlightMenu=No
LoadPlanMenu=No
PauseAfterCrash=No
BrakeReleaseThreshold=75
SaveDataWithFlights=No
ZapSound=firework
ShortAircraftNameOk=Substring
UseProfiles=Yes
EnableMouseLook=No
NewInterceptTextMenu=No
DelayedMouseLookZoom=No
DebugLua=Yes
FSVersionUsed="Lockheed Martin® Prepar3D® v2",2.2.10437.0
SimConnectUsed=2.2.0.0


[JoyNames]
AutoAssignLetters=No
0=Joystick - HOTAS Warthog
0.GUID={4A90A5A0-5C66-11E3-8002-444553540000}
1=Throttle - HOTAS Warthog
1.GUID={4A90A5A0-5C66-11E3-8003-444553540000}
2=CH PRO PEDALS USB
2.GUID={4A9141E0-5C66-11E3-800A-444553540000}


[WideServer]
WideFSenabled=Yes


[Buttons]
ButtonRepeat=20,10
1=P0,1,C65580,0
2=P1,29,K113,8
4=U1,29,K112,8
5=P1,22,C65758,0
6=P1,21,C65759,0
7=P1,13,C66080,0
8=P1,12,C66079,0
9=P1,7,C1010,0
10=P1,6,C1011,0
11=P0,0,C65588,0


[AutoSave]
Next=9
Interval=60
Files=10
SaveOnGround=No
AutoSaveEnabled=Yes
AlsoSave=AutosaveFSUIPC
AlsoInterval=60
1=Sun 212117
2=Sun 212217
3=Sun 212316
4=Sun 212416
5=Sun 212515
6=Sun 212615
7=Sun 212714
8=Sun 212814
9=Sun 211918
10=Sun 212018


[GPSout]
GPSoutEnabled=No
Port=COM0
Speed=4800
Interval=2000
PosTo6Decimal=No
SimModeIndicator=No
Sentences=


[GPSout2]
GPSoutEnabled=No
Port=<none set>
Speed=4800
Interval=2000
PosTo6Decimal=No
SimModeIndicator=No
Sentences=


[Sounds]
Path=E:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Sound\
Device1=Primary Sound Driver
Device2=Speakers (Realtek High Definition Audio)
Device3=Realtek Digital Output (Realtek High Definition Audio)
Device4=BenQ PJ-1 (NVIDIA High Definition Audio)
Device5=Realtek Digital Output(Optical) (Realtek High Definition Audio)


[JoystickCalibration]
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=Yes
ExcludeMixtureSet=Yes
ExcludePropPitchSet=Yes
SepRevsJetsOnly=No
ApplyHeloTrim=No
UseAxisControlsForNRZ=No
FlapsSetControl=0
FlapDetents=No
ReverserControl=66292
Reverser1Control=66422
Reverser2Control=66425
Reverser3Control=66428
Reverser4Control=66431
MaxThrottleForReverser=256
AileronTrimControl=66731
RudderTrimControl=66732
CowlFlaps1Control=66162
CowlFlaps2Control=66163
CowlFlaps3Control=66164
CowlFlaps4Control=66165
SteeringTillerControl=0
MaxSteerSpeed=60


[Axes]
RangeRepeatRate=10
0=1Z,256,F,66423,0,0,0
1=1R,256,F,66420,0,0,0


[Profile.A320 FMGS - no joysticks]
1=a320 FMGS JH Project Airbus A320-214


[Axes.A320 FMGS - no joysticks]
RangeRepeatRate=10


[Buttons.A320 FMGS - no joysticks]
0=P0,0,C65588,0

[adonismartinez]

Good day Jeehell.




ECAMs has been great, I have been doing some test while swithcing off and on switches and it behaves well.


My latests tests has been focused in visual circuits, since ILS, RNAV, and non precision approaches works fine. The vertical deviation index is not always accurate.


** visual circuit performance unable to change **


Please follow this steps :


Init -> EGLL/EGLL
FL 50 any ISA Dev / Cost index
Alternate - > EGLL
complete INIT/B ZFW/ZFWCG


FPLAN - > L1 < DEPARTURE -> 27 R , press Right arrow key, Up arrow key until inserting NO SID


L6 > ARRIVAL -> 27R Up arrow key until inserting NO STAR


Fill MCDU upon completing


Preselect FCU altitude to 1500 ft and speed 210 for visual circuit.


Normal takeoff, engage AP1 , turn to downwind track.

The following configuration is required prior commencement of the downwind leg:
•Both AP and FDs will be selected off
•BIRD ON •A/THR confirmed active in speed mode, i.e. SPEED on the FMA. •Managed speed will be used to enable the "GS mini" function
•The downwind track will be selected on the FCU to assist in downwind tracking.
•The downwind track altitude will be set on FCU



Follow steps as described in image.


1) in case of an inmediate return due to a RED ECAM for example, inmediate diversion is required or in the standard procedure for visual circuit it is necesary to select the approach phase. Since plane never reached the CRZ LEVEL, you never get the app phase ready to select, which is incorect because you should activate app phase and plane will decelerate to S speed prior to order "Flaps one ". PERF page remains frozen.


2) while flying the downwind leg, before turning to base leg, in order to sequence flight plan and get the correct vdi, you can use two methods:


from PPoS, leave a discontinuity, then next point is center fix.
Or
Directo to radial-in to Rwy and set rwy track as inbound radial


For some reason, sometimes the vdi appears correctly and sometimes not.


3) upon landing and below 40 knots, an early activation of the preflight phase occurs which leads to CRC warning for incorrect flap setting,


4) ATHR Caution Landing light turns when retarding levers at landing, not happens in real landing.


5) In a Touch and go, after lift off, PERF page remains frozen in Go Around phase.


6) Pitch angle indicator box background is black when it should be transparent, and flight directors bars should be visible.


7) Entry out of range validation not applied for MDA value. You can enter any value at minimus value at APP page.


I'll keep testing and let you know.


Thanks as always for the great software.


Regards
Adonis


image.jpgi

[jeehell]

Hi Adonis,


Are you sure you use the very latest version (B34 with auto updates) ?
Some of the points you mention should be corrected already??



1)

in case of an inmediate return due to a RED ECAM for example, inmediate diversion is required or in the standard procedure for visual circuit it is necesary to select the approach phase. Since plane never reached the CRZ LEVEL, you never get the app phase ready to select, which is incorect because you should activate app phase and plane will decelerate to S speed prior to order "Flaps one ". PERF page remains frozen.

I always have the ACTIVATE APPR PHASE prompt when in the PERF pages?



2)

while flying the downwind leg, before turning to base leg, in order to sequence flight plan and get the correct vdi, you can use two methods:


from PPoS, leave a discontinuity, then next point is center fix.
Or
Directo to radial-in to Rwy and set rwy track as inbound radial


For some reason, sometimes the vdi appears correctly and sometimes not.

What do you mean by "vdi"? V/DEV indicator?


3)

upon landing and below 40 knots, an early activation of the preflight phase occurs which leads to CRC warning for incorrect flap setting,

I thought this was corrected, I'll check again.


4) ATHR Caution Landing light turns when retarding levers at landing, not happens in real landing.
This should not happen in B34??


5)

In a Touch and go, after lift off, PERF page remains frozen in Go Around phase.

As said in my previous post, the APPR phase will become available only when the GA AROUND activation are no longer in effect, so you will need to put the THR LVR to CL detent to activate the APPR.
Maybe on the Honeywell FMGS (on which you fly I think?) it is a bit different, but on the Thales FMGS the manuals are very clear on that:

The FMGS is designed to switch automatically from APPROACH to GO-AROUND phase when all the following conditions are met:
- A/C in flight,
- slats extended,
- Thrust levers set to TOGA detent

And right after lift off on a touch and go, all these conditions are active...


6)

Pitch angle indicator box background is black when it should be transparent, and flight directors bars should be visible.

From all the pictures I could find, the background is black, but indeed the FD bars are shown in front of the background, which should be simulated in B34?

7)

Entry out of range validation not applied for MDA value. You can enter any value at minimus value at APP page.

I'll correct that ASAP, not very difficult




Thanks for the feedback, always appreciated from real pilots!

Jean Luc

[adonismartinez]

Hi Jeehell.

You are welcome! In fact, Im always happy to contribute with this beatiful software.

Im sure it might be, you know sometimes some modules shows "B 3X" but it content might be newer

Attached please find image for PITCH indication box, you can see those small four points inside .

yes, VDi = V / DEV , sorry for wrong acronym.

Let me make a complete new instalation, keep you in the loop.

Best regards

Adonis

[adonismartinez]

Image attached.

[Jerec]

Hello all,

i´ve got an issue, that WPTs are not displayed an ND, all other EFIS-items are displayed at once, but WPTs dont appear, even when another ND is started on Main PC to be sure, its not a network issue. (1Gbit)
Anyone else has the same issue or could tell me a solution. Navdata is newest from Aerosoft and installed in both Navdata-folders on Main and remote-PCs.

Regards Henrik