Hello
Since our passage under P3D (so PM autopilot) we notice an oscillation of the plane in Roll, only when descending on the glide.
We do not know how to solve this problem.
1) What kind of flying model could we try ?
Do you think it's possible to try PMDG 738 ?
We bought PMDG
2) In PM's aircraft config, there is this line:
Can you tell me how to use it?
What is it useful for?
roll_stability = 1.088 // 1.16 change it according to your hardware
Thank you for your help and your answers.
Patt.
Quote from: Patt737 on February 06, 2018, 09:53:08 AM
Since our passage under P3D (so PM autopilot) we notice an oscillation of the plane in Roll, only when descending on the glide.
I fixed this by turning the "PMautopilot=off" that was project magenta and MCP us the built in flightsim autopilot and it seems to be more stable. I have no oscillations.
Quote
1) What kind of flying model could we try ?
Hard to say, try different ones, but you will need to strip all the panels out remember as most will interfere with the PM software. Many years ago, when I had a 737 I used the PMDG, I don't know if you still can though.
Do you think it's possible to try PMDG 738 ?
We bought PMDG
Quote
2) In PM's aircraft config, there is this line:
Can you tell me how to use it?
What is it useful for?
roll_stability = 1.088 // 1.16 change it according to your hardware
Thank you for your help and your answers.
Patt.
See here.... CLICK (https://msdn.microsoft.com/en-us/library/cc526949.aspx)
Described as.... " Stability parameters The pitch, roll and yaw parameters are multipliers on the default stability (damping effect) about the corresponding axis of the airplane. For example, a value of 1.1 increases the damping by 10%. Likewise, a value of 0.9 decreases the damping by 10%. A negative number results in an unstable characteristic about the axis. A positive damping effect is simply a moment in the direction opposite of the rotational velocity. Omission of a parameter will result in the default value of 1.0."
roll_Stability = 1.0 would mean that its a stable aircraft 1.16 would be a 16% increase in stability .80 would be a 20% decrease in stability.
Trev
Super fast response. :) :)
Thank you .
I will study all this.
Patt
All airplanes have a tendency by design to revert to their original position when thrown in another one,
Start a 20 deg roll to the left, bring back the yoke to neutral and the airplane maintains a bank until you turn the yoke to the right to cancel the roll.
In reality the aircraft tends to slowly revert to a wing level position.
BUT in FS this is often exagerated and you constantly have to use yoke inputs to the left to maintain your 20 deg bank.
This is where Roll_stability= xx comes into play
The higher the number, the better the airplane will maintain a steady roll attitude. Too much is no good, you have to try and test to your liking.
Hello,
Thank you for your answers.
Ok for the PM autopilot on off.
I fixed this by turning the "PMautopilot=off" that was project magenta and MCP us the built in flightsim autopilot and it seems to be more stable. I have no oscillations.
But where can you find another autopilot ?
We are under p3d and no autopilot for the 738.
Can we install another autopilot for 738 if yes:
Or download it ?
Patt.
Ok.. That option is in the MCP.INI File It means use Project Magenta's (Internal MCP Logic) or use the Flightsim (Internal autopilot Logic) for autopilot functions.
The autopilot functions are built into Flightsim (prepared, etc)
Maybe I am confusing you. You will still run the Project Magenta MCP software, but rather than generating its own Autopilot logic, it will just use the logic inside Flightsim.
Trev
Ah!
Good news !
Do you know the exact name of the line in mcp ini?
When you say FLIHGTSIM it's also true for p3d?
Patt.
Quote from: Patt737 on February 07, 2018, 06:58:18 AM
Ah!
Good news !
Do you know the exact name of the line in mcp ini?
When you say FLIHGTSIM it's also true for p3d?
Patt.
Here is the line
[Autopilot]
APProjectMagenta=On
You can see mine is on. Trevor has this turned off.Either way you still run the PM MCP software.
Hello everyone.
This afternoon, I did a lot of tests, with APProjectMagenta = OFF
It's good for swinging in a roll, the plane is stable on loc and glide.
I find another problem, Autothrottle does not work anymore.
Why ?
Patt
Hi Patt,
Copy-paste your PM MCP.ini file (the text) and let me look at it...
John
Quote from: Patt737 on February 10, 2018, 06:45:25 AM
Hello everyone.
This afternoon, I did a lot of tests, with APProjectMagenta = OFF
It's good for swinging in a roll, the plane is stable on loc and glide.
I find another problem, Autothrottle does not work anymore.
Why ?
Patt
I ran into this issue once myself. I think the way I fixed it was a fresh reinstall of the PM software. There was something not changing cleanly when you switch. I am thinking about turning PM AP off as well. We will see how it goes. What version of the software are you running?
We use the mcp 518.
'' There was something changing when you switch ''
I do not understand This line?
Thank you
Between 514 and 516 there was an issue. Did you upgrade from an earlier version? Try a re install and see if that gets rid of the issue... Are you using the PM aircraft?
Yes we put PM regularly updated.
But we did not know where the problem of oscillations came from.
We use the model 738 pmp3d_v4.
But our version of p3d is p3dv3
Do you think we should try with the model pm738 fsx?
Quote from: Patt737 on February 10, 2018, 01:08:51 PM
Yes we put PM regularly updated.
But we did not know where the problem of oscillations came from.
We use the model 738 pmp3d_v4.
But our version of p3d is p3dv3
Do you think we should try with the model pm738 fsx?
Yes I think you should switch back as the new model was designed for P3D v4 not 3. There are a few differences in the model. See if that helps your issue.
Yes I can try again with pm 738 fsx.
But to try to fix the oscillation problem I had installed pm738 fsx
and I had not seen any difference.
Is P3d able to do an autothrottle alone?
Patt
Quote from: Patt737 on February 10, 2018, 02:05:22 PM
Yes I can try again with pm 738 fsx.
But to try to fix the oscillation problem I had installed pm738 fsx
and I had not seen any difference.
Is P3d able to do an autothrottle alone?
Patt
What happens if you use the stock 73 in P3D v3? Does your AT work?
Hello Bob,
What is this '' stock 73'' ?
Thanks
Quote from: Patt737 on February 10, 2018, 11:25:00 PM
Hello Bob,
What is this '' stock 73'' ?
Thanks
The 737 that comes with P3D v3..
It seems to me that there is no native 737 in p3dv3.
Patt
Correct - no native 737 for P3D
I thought it was just version 4 that did not come with a 73.. Sorry...
Hello everyone.
1) if I use APProjectMagenta = On, I have opscillations in roll on the glide
2) If I use APProjectMagenta = Off, the autothrottle does not work anymore but the roll oscillations disappear.
The problem of oscillations in roll seems known for several years.
Many post since years speak of this problem.
I really like PM and I would not buy anything else we use it since the year 2005.
How to use another autotrottle?
Thank you for your help.
Patt.
Patt,
It would be very helpful for you to copy/paste the text from your MCP.ini file. That is how I know all PM software...by looking at .ini files
John
OK, thanks. :) :)
Tonight I start the cockpit and I will make a copy of the ini file of the mcp.
Patt.
Are your oscillations up and down or left and right?
Hi Bob
Left and right,
Here is my mcp ini
[Project Magenta MCP]
Build#518
[Display]
Title=On
Menu=Off
WindowName=MCP/Enhanced Autopilot by Enrico Schiratti - Build 518
Topmost=Off
FSWindow=Off
Minimized=Off
/ Starts up minimized
NoMinimize=Off
/ Doesn't minimize MCP on double-click
[User]
Log=Off
SerialLog=Off
/ To log the serial communication
CycleMilliSeconds= 30
/ Speed of the MCP cycle, ideally
/ set to 50-70 ms
Top= 570
Left=-135
/ Top/Left coordinates of the MCP
/ program
Width737= 15375
Height737= 2430
Width747= 15390
Height747= 3180
Width777= 15390
Height777= 3210
/ Heigth and width of MCP for the
/ various types
MCPType=737
Intervent737=On
/ Enables SPD intervention buttons
/ for the 737
ClassicEFISSel=Off
/ When set to On, ND modes are selected
/ with the old method, when set to
/ Off, 8 modes are selectable...
/ APP/VOR/MAP/PLN ARC and CTR
DelayMouseClick=On
/ if mouse reaction is too fast,
/ you can delay it setting this flag
/ to On
Font=mcpfont
FontFactor= 1.27
[VNAV]
DescentSpeedControl=Off
/ when set to off, pilot controls
/ speed with the throttle
[Aircraft]
[PROJECT MAGENTA 737-800 P3D]
[\\DESKTOP-IPL7F3I\P3D\PREPAR3D V3\SIMOBJECTS\AIRPLANES\PROJECT MAGENTA 738P3D\PMX737-800.AIR]
MinIAS= 0
/ Minimum selectable airspeed
DefaultIAS= 110
DefaultAltitude= 10000
/ Default Speed and Altitude select
/ on startup
AutoHDG=On
AutoVS=Off
/ Will automatically select the current
/ HDG and V/S when mode is engaged
MachAltitude= 0
/ Will automatically switch to MACH/IAS
/ when this altitude is crossed (e.g.
/ 23450), 0 disables
AutoCRS=Off
/ When set to ON, VOR/LOC will *not*
/ go into intercept ARM mode first
AllowStabTrimOverride=Off
StabTrimDeflect= 6000
/ Disconnects A/P when Elevator or
/ Aileron is moved more than the
/ deflection value (default 6000)
/ This option needs to be enabled
/ via bit13 offset 0x50A - monitor
/ bit13 0x5528 for current setting
StabTrimOverrideActive=Off
/ This sets the option above to always
/ be active
Rollout=On
/ MCP will steer the aircraft during
/ the rollout phase after an autoland
DisableAdd20Kts=Off
/ Will not add 20 Kts to speed during
/ TOGA if set to On
AllowAPOnGround=Off
/ Allows engaging AP on the ground
NoModeAfterTOGA=Off
/ Doesn't automatically enable FLCH
/ after TOGA mode
UsePanel=Off
/ Set to On if the FS panel or remote
/ programs are used for MCP interaction
PushButton=Off
/ Enables the use of the pushbutton
/ for SPD, ALT and HDG
SpeedProtect=Off
/ Enables speed protection for A/P
/ modes
SELCurrentSpeed=On
/ MCP will take the current speed
/ when any speed mode is engaged
/ for the first time
TerrAlt=Off
/ Alternate Terrain Mode
Flare= 50
/ Altitude above ground at which
/ the flare is initiated during autoland
N1ref= 98.3
N1TOref= 98.3
N1GAref= 100
N1CLBref= 90.9
N1CRZref= 94.8
ThrRedAlt= 1500
/ Defaults used for reference thrust
/ and thrust reduction altitudes,
/ only if no CDU detected
MaxROC= 6000
MaxROD= 6000
/ Maximum rate of climb/descent
ClimbThrustLimiter=On
/ Limits the climb thrust increase
/ if the speed increases too much
/ during FLCH/LVLCHNG climbs
Climb2000Spd=Off
/ Climbs with SPD mode during FLCH/LVLCHNG
/ of less than 2400 ft
FlightIdle= 10
ApproachIdle= 15
/ Min Idle Value for Flight/Approach
/ (default 10% and 15%)
UsePMAutobrakes=Off
/ Enables the PM Auto Brake, do not
/ use the FS autobrake system at
/ the same time
DisableAutobrakes=Off
/ Switches Off Autobrakes below 30
/ Knots, both for PM and FS AutoBrake
/ System
DisableBrakes=Off
/ Disables the writing of any brake
/ valuesof the MCP for Rollout -
/ this is *not* the Aurobrake System,
/ if you use PM autobrake, then this
/ has to be off
BrakeFactor= 0
/ Brake factor in percent, default
/ 100%
BrkDiscPark=On
/ Brakes disconnect Parking Brake
ParkNeedsBrk=Off
/ Parking Brake Needs Brakes to be
/ Pressed to engage
TrimMin=-1
TrimCtr= 0
TrimMax= 10
/ 737 Trim Gauge Min/Ctr/Max
UsepmNavSounds=Off
/ Will not write Nav Sound flags
/ to FS Offsets but to Project Magenta
/ Offsets
StbySets1200=Off
/ Will set transponder to 1200 when
/ standby is selected
SwapCRS=Off
/ Swaps CRS 1 and CRS 2
[Input]
MouseWheel=On
MouseWheelInvert=On
/ Allows you to 'turn the knobs'
/ of the MCP using the mouse wheel,
/ you can also invert the direction
FSBusWriteBack=Off
/ Will write back Speed and V/S values
/ to offsets 0x5406 and 0x540C respectively
[Autopilot]
APProjectMagenta=Off
/ Enables the PM autopilot and overrides
/ the FS autopilot
APBankFactor= 75
APPitchFactor= 30
/ Autopilot pitch and bank factors,
/ the higher the value, the larger
/ the corrections
DynamicPitch=Off
/ Enables the PM autopilot and overrides
/ the FS autopilot
DynamicUseLoHi=Off
DynamicPitchLow= 5
DynamicPitchHigh= 19
/ Dynamic pitch will use low (close
/ to 100kts) and high (close to 350
/ kts) values
DynamicPitchTAS=Off
/ Currently Disabled
/ Project Magenta Autopilot for Pitch
/ and Bank modes
[Hardware Connections]
/ Enter Comm port the device is connected
/ to, please do not use this if you
/ do not have any hardware connected
/ e.g. enter = 2 for COM2:
/ Precision Flight Controls MCP hardware
/ www.flypfc.com (http://www.flypfc.com)
PFCComm= 0
PFC9600=Off
/ Important, the PFC9600 flag should
/ be set to OFF for normal use, currently
/ it is just for testing purposes
CautionThroughPass=Off
/ PFC Caution Button pressed are
/ not handled, but passed through
/ to 0x5534
/ For CPFlight 737 MCP hardware www.cpflight.com (http://www.cpflight.com)
ForceHardwareLight=Off
UseInstLight=Off
IgnoreBattery=Off
/ Ignores pmSystems battery and FS
/ Avionics (Battery)
IgnoreAvionics=Off
/ Ignores only FS Avionics (Battery)
DisableFSMessage=Off
/ Disables sending messages to FS
/ Window
NoMenu=Off
/ Removes Menu access and close button
PauseMetric=Off
/ First Officer Meters Pushbutton
/ sets Pause
CargoReset=Off
/ Cargo Buttons used for FS reset
/ via Instructor Station (CP Center
/ Console only)
CargoPause=On
/ Cargo Button used for FS Pause
/ (CP Center Console only)
CPFlightIP=
CPFlightPort= 0
/ CP Flight IP Address and IP Port
/ (default 4500)
CPFlightComm= 0
/ CP Flight Comm Port
CPFlightIO=On
/ Set CPFlightIO=Off to *disable*
/ digital and analog input/output
DisableMIP=Off
/ Set DisableMIP *disable* CPFlight
/ MIP handling (e.g 737 sixpack troubleshooting)
/ For FDS G1 Hardware Communication
FDS_G1_Comm= 0
/ Flight Deck Solutions FDS Glare
/ On/Off
FDSGlare=Off
/ For Daken IFS Hardware
DakenSkys_IFS_Comm= 0
/ FSC MIP Hardware
FSCMIPComm= 0
FSCMIPInvertGear=Off
/Inverts Gear Direction
FSCMIPInvertSixPack=Off
/Inverts both Sixpack Anunciation Lines
/ FSC Throttle Hardware Comm
/ http://www.flightsimulatorcenter.com (http://www.flightsimulatorcenter.com)
FSCThrottleQuadrantComm= 0
FSCNOTMotorized=Off
FSCTQMotorDisable=Off
/Disables the motorization of the throttle
FSCTQTrimMotorDisable=Off
/Disables the motorization of the trim
FSCTQTrimSpeed= 30
/Sets trim motor speed 0 min 255 max (default 30)
FSCTQInvertTrim=Off
/Inverts Trim Motor Direction
FSCTQInvertTrimWheel=Off
/Inverts Trim Wheel Direction (when stab trim disconnected
FSCTQTrimOffset0= 99
FSCTQTrimOffset10= 188
/Offsets Trim Indicator for Trim 0 and Trim 10
FSCTQInvertSpoiler=Off
/Inverts Spoiler Potentiometer Direction
FSCTQInvertSpoilerMotor=Off
/Inverts Spoiler Motor Direction
FSCTQCalib= 0
/UnCalibrated=0 - Calibrated=1 - Mixed=2 - Diff=3 - 2SameAs1=4 - useAdjust=5
FSCTQAdjust= 0
/Adjusts Throttle 2 position by X
FSCSplArmPos= 0
/Sets Spoiler Arm Position
FSCRevPct= 35
/Travel of reversers before they are activated, min 15%, default 35%
FSCThrottle1Min= 0
FSCThrottle1Mid= 0
FSCThrottle1Max= 0
FSCThrottle2Min= 0
FSCThrottle2Mid= 0
FSCThrottle2Max= 0
FSCReverser1Min= 0
FSCReverser1Max= 0
FSCReverser2Min= 0
FSCReverser2Max= 0
FSCSpoilerMax= 0
FSCSpoilerMin= 0
FSCSingleThrottle= 0
FSCSingleReverser= 0
FSCThrIntervent=Off
FSCTQMotBuffer= 13
/ Top and Bottom Buffer zone to switch
/ off Throttle Motors (default 13)
/ FSC Throttle Hardware Ver 0
/ Cockpitsonic EHID
/ http://www.cockpitsonic.com (http://www.cockpitsonic.com)
EHIDComm=Off
/ Can be set to 'On', 'Off', 'localhost'
/ or IP Address
/ ELAN MCP hardware
ElanComm= 0
ElanBaudRate=
/ Please leave ElanBaudrate empty
/ unless you know what you are doing(!)
/ Aerosoft 747 MCP hardware www.mcp747.com (http://www.mcp747.com)
AerosoftComm= 0
AerosoftFPV= 14
AerosoftDHRST= 0
/ Defines the action (offset 0x4F4)
/ of the Aerosoft FPV button or DH
/ Reset button, e.g. 14=FPV, 6=CTR
/EicasButton1=???
/ You can define the action (offset
/ 0x4F4) of each of the 10 EICAS
/ buttons by setting the corresponding
/ value here (e.g. EicasButton1=71,
/ EicasButton10=87)
[EPIC]
DisableRemoteMCP=Off
/ Set to on to disable input from
/ other programs using these offsets
/ via FSUIPC
/ Syntax: input type = joystick,
/ axis
[Extra]
NoFSCOptions=Off
ALWAYS BACKUP YOUR FILE BEFORE YOU MAKE CHANGES>>>>>
[VNAV]
DescentSpeedControl=Off
/ when set to off, pilot controls
/ speed with the throttle
Turn this on, unless you prefer to control the speed...
[Autopilot]
APProjectMagenta=On // Turn this back on so your Autothrottle works again
/ Enables the PM autopilot and overrides
/ the FS autopilot
APBankFactor= 30 // LOWER THIS 70 is way to big lots of corrections will make it look like osculations.
APPitchFactor= 30
/ Autopilot pitch and bank factors,
/ the higher the value, the larger
/ the corrections
DynamicPitch=ON // If you turn on the PM Autopilot above
/ Enables the PM autopilot and overrides
/ the FS autopilot
DynamicUseLoHi=Off
DynamicPitchLow= 5
DynamicPitchHigh= 19
/ Dynamic pitch will use low (close
/ to 100kts) and high (close to 350
/ kts) values
DynamicPitchTAS=Off
/ Currently Disabled
/ Project Magenta Autopilot for Pitch
/ and Bank modes
@ BOB --> DisableAutobrakes=Off
/ Switches Off Autobrakes below 30
/ Knots, both for PM and FS AutoBrake
/ System
Turn this one on to fix your issue LOL..
Hey Trevor, I was hitting the post button and you got in just before me because I was typing this long post...lol! The good thing is we're both saying the same thing here.
Patt,
Okay, I looked at your MCP.ini...first question, are you using some sort of MCP hardware, if so what is it? Next, you have PM Autopilot=off so it is not going to use PM Autopilot (you know this already), and you are now using the FSAutopilot mode from the simulator program. And, you have tried this already, but if you are using actual MCP hardware and/or a throttle with a TOGA button to engage autothrottle on the ground, you must make sure your offset(s) are also sending the info to the FSAutopilot.
Therefore, go to FSUIPC and check the TOGA Offset and see if the "send to FS is checked"? It might be your autothrottle is setup only using the PMOffsets and the FSUIPC offsets are not sending them to the FS program as well. This could be the same with your entire MCP hardware offsets for the FSAutopilot side...that is why I ask about the actual hardware.
Next, what type of Input/Output cards are you using...FDS or something else. So, whatever they are I would want too see the FSUIPC file that has your offset settings; it is an .ini file, but I cannot remember what the first part of the file name is, before the .ini side. Can you get that for me? If you want too go deeper?
Now, for you and Bob with using the PMAutopilot=on and for it too work better, you need to look at the PM MCP.ini, as there are sections you adjust to help fix the oscillations, and you must do the trial and error method. In other words, set the value, fly it, if it's fixed leave it alone, if not fixed, you must change the value, fly it and keep repeating this until it's the way you want. This is also known as dialing it in.
Here are the sections to look at, and they do affect both bank and pitch.
[Autopilot]
APProjectMagenta=Off
/ Enables the PM autopilot and overrides
/ the FS autopilot
APBankFactor= 75
APPitchFactor= 30
/ Autopilot pitch and bank factors,
/ the higher the value, the larger
/ the corrections
DynamicPitch=Off
/ Enables the PM autopilot and overrides
/ the FS autopilot
DynamicUseLoHi=Off
DynamicPitchLow= 5
For VNAV help, look at this:
[VNAV]
DescentSpeedControl=Off
/ when set to off, pilot controls
/ speed with the throttle
Now, look at this, it is a new feature. When you are on Descent/Approach and the AutoThrottle is controlling the throttles, and it is at idle while going down, these values will affect how it works by percentages, something like playing with Bank and Pitch that I mentioned above. In other words, another dialing in tool.
FlightIdle= 10
ApproachIdle= 15
/ Min Idle Value for Flight/Approach
/ (default 10% and 15%)
Finally, there are other factors that you could look at, but it's much deeper into the PM actual values of everything for speed and so on. They will not fix oscillations, but it'll change the reactions of the flight model, hard to explain in a post, so I will find the link to the area in the manuals for you later...in effect you would be editing the flight model itself.
Almost forgot, whenever you are on an Autolanding approach, make sure both Nav1 and Nav2 radios are set correctly. Sometimes, the Nav2 will not get set right with PM and this will cause the searching for the Glide Slope oscillations.
John
Note: Please use Trevor's recommended settings he high lighted in blue and not mine. I just pointed out the sections and did not change the values at all...
John
Did I mention I am using one finger to peck these replies from my cell phone? OMG LOL! It takes forever and I am slow like this...I need to get to my computer keyboard. :idiot:
John
Thank you a lot.
Your help is very precious.
Tomorrow I will try to change only the 3 parameters of Trevor (lines in blue).
For autobrake we use our own system.
Be careful not to damage your finger, because I will still need it ..... ;D ;D
Patt
Patt,
No guarantees, but this will get you started.. Please keep us posted with your progress.
Trev
Hello everyone,
I'm back.....
We have tests with the Trevor lines.
Nothing changes, the oscillations are weaker.
But the plane always lands next to and before the runway.
If we use: DynamicPitch = ON here is what happens:
https://www.youtube.com/watch?v=0WLspvUCA40 (https://www.youtube.com/watch?v=0WLspvUCA40)
Here is what we decided:
The plane works very well with APProjectMagenta = OFF, but without auto trhottle.
We are thinking of adding an A / T on the PM738fsx flight model.
We have tested the opensky project 737 and the A / T is working well, but no TOGA.
It must be possible to add an A / T on PM and maybe a toga..
Do you know how to do it ?
Thank you
Patt
In the aircraft.cfg file there is an autopilot section. Ensure the auto throttle is enabled. And all the throttle settings have values. See the attached under autopilot.
https://msdn.microsoft.com/en-us/library/cc526949.aspx#mozTocId942782 (https://msdn.microsoft.com/en-us/library/cc526949.aspx#mozTocId942782)
Thank you, Trevor.
I watch .
And I will make you a return
Patt
Have you tried putting the stock FSX 737 into P3d? Give that a try and see what happens.
Thank you Bob, it's a good idea.
Patt
Hello everyone.
We did new tests.
With the original 737 fsx, but that did not change anything.
On the other hand we modified these values in the cdu:
SPD% <11000FT // 110
SPD%> 11000FT // 110
LVLCHNG% // 120
And this one in the aircraft cfg:
max_throttle_rate = 0.05
And it's much better, we have almost no swing roll.
We also observed that path given by the cdu, to intercept
the loc should not be short between loc and glide.
Only when the plane is very stable on his loc can he intercept
the glide
If not, he will no longer be able to stop the oscillations.
We still have another problem touchdown is very violent 1300 ft / min!
whereas it should be 600 ft / min I think.
With what parameter can we set this in the cdu or the aircraft.cfg?
Thanks for your help.
And now a riddle:
What can we do in a 737 cockpit with these 2 objects?
(https://i62.servimg.com/u/f62/12/07/32/61/boule_10.jpg) (https://servimg.com/view/12073261/177)
See you soon
Patt
I would have to check but I'm the pm MCP I think it's flare altitude. You may need to up that a tad.
Quote from: Patt737 on March 10, 2018, 01:11:18 PM
...
We still have another problem touchdown is very violent 1300 ft / min!
whereas it should be 600 ft / min I think.
...
:o
Try around 300 ft/min.
600 ft/min is a typical threshold for a hard landing inspection.
Hello,
Thank you for your answers.
We did a flight this day and no oscillation it's great! :D :D :D
What value do I need to add to Flare for a soft landing ?
My value is 50 currently
Can you explain to me what is this?
Or tell me where I can find information, because I do not understand very well what these lines correspond to the mcp ini.
AutoCRS = Off
TerrAlt = Off
FlightIdle= 10
ApproachIdle= 15
For the answer to my question ..... :o
(https://i62.servimg.com/u/f62/12/07/32/61/img_1811.jpg) (https://servimg.com/view/12073261/179)
(https://i62.servimg.com/u/f62/12/07/32/61/img_1810.jpg) (https://servimg.com/view/12073261/178)
Thanks
Patt
Quote from: Patt737 on March 12, 2018, 03:05:27 PM
What value do I need to add to Flare for a soft landing ?
My value is 50 currently
Means start the flare at 50 feet off the ground. maybe set this to 100, and see what happens.. If you start the flare early, you will set down easier. If its worse, try lowering it because your flaring too soon.
Quote
AutoCRS = Off
Automatically sets the approach crs on the MCP rather than you setting it. This should stay off in case navdata is different then the rwy data.
Quote
TerrAlt = Off
Not 100% sure but I think this sets the terrain mode on the ND to an Altitudee (Topographical) rather than a 3d mode but could be wrong.
Quote
FlightIdle= 10
ApproachIdle= 15
These are Autothrottle controls
When in a decent (LEVEL Change) the engines will slow to 10% power to reduce the speed in the descent. When on approach and the engines slow to idle they will only drop to 15% power.
If you are having troubles slowing down on descent you can reduce this further, or if your having issues on approach with going to fast you can also reduce this.
Keep in mind though..... Dropping to a lower power setting takes a little longer for the engines to spool back up should it be required.
Trev
Hello,
Thank you very much Trevor.
I understand better now.
I'm going to test with FLARE.
I'll tell you if it's better.
Patt.
Hello everyone,
We still have problems with AT pm.
All is well, if he is not active.
If not, the plane is unstable and landings with autopilot impossible.
We will try to remake a complete installation of mcp and cdu.
We do not really believe it .......
Are there any people on this forum who use pm and and p3dv3, we would like to chat with them?
We do not have pmsystem do you think this can have an impact on the behavior of AT ?
We have tried many solutions:
Test aircraft of fs/fsx/p3d.
Change of value in air file (pm738 fsx).
Change of value in Ini mcp file.
Change of value in Flare .
We tried to use the p3d AT, but it is not compatible with
the MCP of pm, too bad it could have helped us.
But nothing helps.
Left right swing if speed less than 150 knots.
Aircraft plunging at 1600 ft/min while at 2000 ft ground approaching the glide ....
We asked PM, but no answer.
If you have other good ideas.....
Thank you.
Patt.
Okay, I am curious, are you setting both NAV radios and using the FO's FD to lock in the loc and G/S when intercepting?
Also, in the past it has worked for you, but not now? Are you changing things like upgrading the PM software with every new version? If so, stop and stick with a version that works. Only upgrade to the new version after everyone else has...gives time for the bugs too be worked out
Have you looked at ProSim 737? I have used PM for many years and yet, I purchased ProSim. I just like options.
John
Thank John you for your reply.
We created the cockpit in 2005 and bought PM.
We used fs9 and everything worked well.
We did not use pm autopilot.
Then we installed p3dv3 in 2017.
And we have to tick pm autopilot on the mcp.
To be able to use the pm auto throttle.
P3D AT does not work as fs9 does.
We do not know why?
And it is since we are under p3dv3 that nothing goes more.
We normally schedule our plane for a descent into ILS.
Since it works with p3d, but without autothrottle. (autopilot pm off)
Patt.
Quote from: Patt737 on April 17, 2018, 08:41:39 AM
Hello everyone,
We still have problems with AT pm.
All is well, if he is not active.
If not, the plane is unstable and landings with autopilot impossible.
We will try to remake a complete installation of mcp and cdu.
We do not really believe it .......
Are there any people on this forum who use pm and and p3dv3, we would like to chat with them?
We do not have pmsystem do you think this can have an impact on the behavior of AT ?
We have tried many solutions:
Test aircraft of fs/fsx/p3d.
Change of value in air file (pm738 fsx).
Change of value in Ini mcp file.
Change of value in Flare .
We tried to use the p3d AT, but it is not compatible with
the MCP of pm, too bad it could have helped us.
But nothing helps.
Left right swing if speed less than 150 knots.
Aircraft plunging at 1600 ft/min while at 2000 ft ground approaching the glide ....
We asked PM, but no answer.
If you have other good ideas.....
Thank you.
Patt.
See there is something else going on here. I use PM and I use the AT through all aspects of the flight. Until just recently I used the P3D AT and autopilot and just used PM to access that. I have recently switched back to using the PM AP. I have no AT issues in the sim. I have had lots of other issues but not the Auto Throttle....
Hello bob.
Thank you for the answer.
That I understand well.
You use the p3d AT and the p3d auto pilote with PM.
Are there any specific offset.
How are you doing ?
Patt
Bob, do you think PMSystems is causing this, in the past it never has because MCP didn't need it. Maybe, you could post all your PM.ini files.
Patt, you should post all of yours as well. Trevor found those other problem items for you this way, so maybe a comparison with Bob's would help.
The only other thing I would guess is your network speed along with the MCP's ms timing is conflicting and causing these oscillations. What is weird you had it working on March 18th, 2018, but it started going wrong between now and then? What changed since the 18th?
John
Quote from: blueskydriver on April 17, 2018, 02:02:36 PM
Bob, do you think PMSystems is causing this, in the past it never has because MCP didn't need it. Maybe, you could post all your PM.ini files.
Patt, you should post all of yours as well. Trevor found those other problem items for you this way, so maybe a comparison with Bob's would help.
The only other thing I would guess is your network speed along with the MCP's ms timing is conflicting and causing these oscillations. What is weird you had it working on March 18th, 2018, but it started going wrong between now and then? What changed since the 18th?
John
I do not think it is PMSystems. I will post my MCP.ini file and any other files that anyone wants to look at. I think it is in the settings for up down left right timing. I can not remember what it is called and I have shut the cave down for the night. I will post in the morning. I think what they believe is the AT causing issues is just the AT trying to keep up with the aircraft. As the aircraft swings left right or up down the worse the oscillations become as the autopilot tries to correct.
Good evening everyone.
It is very nice to have an exchange with you.
And besides it's fast.
We must thank those who take their time to help others.
For that I thank you.
To return to our sheep, as we say at home ......
'' I do not think it is PMSystems ''
I agree with you PMSystems has nothing to do with our problem, but I wanted your opinion.
""Patt, you should post all of yours as well. Trevor found those other problem items for you this way, so maybe a comparison with Bob's would help""
It's a good idea to publish our files, as I return to the cockpit.
I would take the files ini mcp / cdu.
'' The only other thing I would guess your network speed along with the MCP's timing is conflicting and cause these oscillations.
Actually it could be an interesting track.
But how can we fix the problem ?
The pc CDU is very old and we think to replace it at the end of the year, by a newer one.
But this one has only one task to control the cdu.
'' What is weird you had it working on March 18th, 2018, but it started going wrong between now and then? What changed since the 18th? ''
Yes indeed we had solved part of the problem.
There was no more left right swing.
But the plane landed before the runway.
But for all the tests to be the same we limit
the speed of approach to 150 knots.
But once the speed reaches below 150 the oscillations come back.
I do not understand why we can not use p3d's AT as we did with FS9 ?
Did you do special things to make it work ?
Do you use IOCP ?
See you soon.
Patt
Hmm I forgot to post my ini... After dinner. I did nothing special to make it work. The auto pilot in P3D is not aircraft specific. It is a system wide thing. As you have done I could get the oscillations to stop at higher speeds but when I would slow down they would come back. I am sure this is in the timing settings. Again I will post my MCP ini settings. I think..... :P
Ok, here it is the MCP ini file.
APBankFactor= 85
APPitchFactor= 30
These are the settings I have been slowly tinkering with to get my aircraft to fly as desired. APBankFactor= 85 is the one I have worked with the most. In my sim it works backwards to how I thought it worked. I set it to 30 and the aircraft was much worse. So then I took it to 75 and that was much better. I have slowly taken it up to 85. I am very happy with how it works now.
So here is the rest of the ini
[Project Magenta MCP]
Build#519
[Display]
Title=On
Menu=Off
WindowName=MCP (Active) Press Ctrl-L for Logger, Esc For Menu
Topmost=Off
FSWindow=Off
Minimized=On
/ Starts up minimized
NoMinimize=Off
/ Doesn't minimize MCP on double-click
[User]
Log=Off
SerialLog=Off
/ To log the serial communication
CycleMilliSeconds= 40
/ Speed of the MCP cycle, ideally
/ set to 50-70 ms
Top= 0
Left= 0
/ Top/Left coordinates of the MCP
/ program
Width737= 15495
Height737= 2490
Width747= 15390
Height747= 3120
Width777= 15390
Height777= 3150
/ Heigth and width of MCP for the
/ various types
MCPType=737
Intervent737=On
/ Enables SPD intervention buttons
/ for the 737
ClassicEFISSel=Off
/ When set to On, ND modes are selected
/ with the old method, when set to
/ Off, 8 modes are selectable...
/ APP/VOR/MAP/PLN ARC and CTR
DelayMouseClick=On
/ if mouse reaction is too fast,
/ you can delay it setting this flag
/ to On
Font=mcpfont
FontFactor= 1.27
[VNAV]
DescentSpeedControl=On
/ when set to off, pilot controls
/ speed with the throttle
[Aircraft]
[PM BOEING 737-800 ALASKA AIRLINES SPIRT OF SEATTLE1]
[\\FSX-PC\LOCKHEED MARTIN\PREPAR3D V4\SIMOBJECTS\AIRPLANES\PROJECT MAGENTA 738\PMX737-800.AIR]
MinIAS= 0
/ Minimum selectable airspeed
DefaultIAS= 110
DefaultAltitude= 10000
/ Default Speed and Altitude select
/ on startup
AutoHDG=On
AutoVS=On
/ Will automatically select the current
/ HDG and V/S when mode is engaged
MachAltitude= 0
/ Will automatically switch to MACH/IAS
/ when this altitude is crossed (e.g.
/ 23450), 0 disables
AutoCRS=Off
/ When set to ON, VOR/LOC will *not*
/ go into intercept ARM mode first
AllowStabTrimOverride=Off
StabTrimDeflect= 6000
/ Disconnects A/P when Elevator or
/ Aileron is moved more than the
/ deflection value (default 6000)
/ This option needs to be enabled
/ via bit13 offset 0x50A - monitor
/ bit13 0x5528 for current setting
StabTrimOverrideActive=Off
/ This sets the option above to always
/ be active
Rollout=On
/ MCP will steer the aircraft during
/ the rollout phase after an autoland
DisableAdd20Kts=On
/ Will not add 20 Kts to speed during
/ TOGA if set to On
AllowAPOnGround=On
/ Allows engaging AP on the ground
NoModeAfterTOGA=On
/ Doesn't automatically enable FLCH
/ after TOGA mode
UsePanel=Off
/ Set to On if the FS panel or remote
/ programs are used for MCP interaction
PushButton=Off
/ Enables the use of the pushbutton
/ for SPD, ALT and HDG
SpeedProtect=Off
/ Enables speed protection for A/P
/ modes
SELCurrentSpeed=On
/ MCP will take the current speed
/ when any speed mode is engaged
/ for the first time
TerrAlt=Off
/ Alternate Terrain Mode
Flare= 50
/ Altitude above ground at which
/ the flare is initiated during autoland
N1ref= 99.6
N1TOref= 99.6
N1GAref= 90
N1CLBref= 93
N1CRZref= 97.1
ThrRedAlt= 1500
/ Defaults used for reference thrust
/ and thrust reduction altitudes,
/ only if no CDU detected
MaxROC= 9000
MaxROD= 9000
/ Maximum rate of climb/descent
ClimbThrustLimiter=Off
/ Limits the climb thrust increase
/ if the speed increases too much
/ during FLCH/LVLCHNG climbs
Climb2000Spd=Off
/ Climbs with SPD mode during FLCH/LVLCHNG
/ of less than 2400 ft
FlightIdle= 10
ApproachIdle= 15
/ Min Idle Value for Flight/Approach
/ (default 10% and 15%)
UsePMAutobrakes=Off
/ Enables the PM Auto Brake, do not
/ use the FS autobrake system at
/ the same time
DisableAutobrakes=Off
/ Switches Off Autobrakes below 30
/ Knots, both for PM and FS AutoBrake
/ System
DisableBrakes=Off
/ Disables the writing of any brake
/ valuesof the MCP for Rollout -
/ this is *not* the Aurobrake System,
/ if you use PM autobrake, then this
/ has to be off
BrakeFactor= 100
/ Brake factor in percent, default
/ 100%
BrkDiscPark=On
/ Brakes disconnect Parking Brake
ParkNeedsBrk=Off
/ Parking Brake Needs Brakes to be
/ Pressed to engage
TrimMin=-1
TrimCtr= 0
TrimMax= 10
/ 737 Trim Gauge Min/Ctr/Max
UsepmNavSounds=On
/ Will not write Nav Sound flags
/ to FS Offsets but to Project Magenta
/ Offsets
StbySets1200=Off
/ Will set transponder to 1200 when
/ standby is selected
SwapCRS=Off
/ Swaps CRS 1 and CRS 2
[Input]
MouseWheel=On
MouseWheelInvert=On
/ Allows you to 'turn the knobs'
/ of the MCP using the mouse wheel,
/ you can also invert the direction
FSBusWriteBack=Off
/ Will write back Speed and V/S values
/ to offsets 0x5406 and 0x540C respectively
[Autopilot]
APProjectMagenta=On
/ Enables the PM autopilot and overrides
/ the FS autopilot
APBankFactor= 85
APPitchFactor= 30
/ Autopilot pitch and bank factors,
/ the higher the value, the larger
/ the corrections
DynamicPitch=On
/ Enables the PM autopilot and overrides
/ the FS autopilot
DynamicUseLoHi=Off
DynamicPitchLow= 5
DynamicPitchHigh= 19
/ Dynamic pitch will use low (close
/ to 100kts) and high (close to 350
/ kts) values
DynamicPitchTAS=Off
/ Currently Disabled
AltAcqDiv= 4
/ Altitude Divisor VS/this = capture
/ alt difference
/ Project Magenta Autopilot for Pitch
/ and Bank modes
[Hardware Connections]
/ Enter Comm port the device is connected
/ to, please do not use this if you
/ do not have any hardware connected
/ e.g. enter = 2 for COM2:
/ Precision Flight Controls MCP hardware
/ www.flypfc.com (http://www.flypfc.com)
PFCComm= 1
PFC9600=Off
/ Important, the PFC9600 flag should
/ be set to OFF for normal use, currently
/ it is just for testing purposes
CautionThroughPass=Off
/ PFC Caution Button pressed are
/ not handled, but passed through
/ to 0x5534
/ For CPFlight 737 MCP hardware www.cpflight.com (http://www.cpflight.com)
ForceHardwareLight=Off
UseInstLight=Off
IgnoreBattery=Off
/ Ignores pmSystems battery and FS
/ Avionics (Battery)
IgnoreAvionics=On
/ Ignores only FS Avionics (Battery)
DisableFSMessage=Off
/ Disables sending messages to FS
/ Window
NoMenu=Off
/ Removes Menu access and close button
PauseMetric=Off
/ First Officer Meters Pushbutton
/ sets Pause
CargoReset=Off
/ Cargo Buttons used for FS reset
/ via Instructor Station (CP Center
/ Console only)
CargoPause=On
/ Cargo Button used for FS Pause
/ (CP Center Console only)
CPFlightIP=
CPFlightPort= 0
/ CP Flight IP Address and IP Port
/ (default 4500)
CPFlightComm= 0
/ CP Flight Comm Port
CPFlightIO=On
/ Set CPFlightIO=Off to *disable*
/ digital and analog input/output
DisableMIP=Off
/ Set DisableMIP *disable* CPFlight
/ MIP handling (e.g 737 sixpack troubleshooting)
/ For FDS G1 Hardware Communication
FDS_G1_Comm= 0
/ Flight Deck Solutions FDS Glare
/ On/Off
FDSGlare=Off
/ For Daken IFS Hardware
DakenSkys_IFS_Comm= 0
/ FSC MIP Hardware
FSCMIPComm= 0
FSCMIPInvertGear=Off
/Inverts Gear Direction
FSCMIPInvertSixPack=Off
/Inverts both Sixpack Anunciation Lines
/ FSC Throttle Hardware Comm
/ http://www.flightsimulatorcenter.com (http://www.flightsimulatorcenter.com)
FSCThrottleQuadrantComm= 0
FSCNOTMotorized=On
FSCTQMotorDisable=Off
/Disables the motorization of the throttle
FSCTQTrimMotorDisable=Off
/Disables the motorization of the trim
FSCTQTrimSpeed= 30
/Sets trim motor speed 0 min 255 max (default 30)
FSCTQInvertTrim=On
/Inverts Trim Motor Direction
FSCTQInvertTrimWheel=Off
/Inverts Trim Wheel Direction (when stab trim disconnected
FSCTQTrimOffset0= 177
FSCTQTrimOffset10= 88
/Offsets Trim Indicator for Trim 0 and Trim 10
FSCTQInvertSpoiler=On
/Inverts Spoiler Potentiometer Direction
FSCTQInvertSpoilerMotor=Off
/Inverts Spoiler Motor Direction
FSCTQCalib= 0
/UnCalibrated=0 - Calibrated=1 - Mixed=2 - Diff=3 - 2SameAs1=4 - useAdjust=5
FSCTQAdjust= 0
/Adjusts Throttle 2 position by X
FSCSplArmPos= 212
/Sets Spoiler Arm Position
FSCRevPct= 15
/Travel of reversers before they are activated, min 15%, default 35%
FSCThrottle1Min= 19
FSCThrottle1Mid= 0
FSCThrottle1Max= 155
FSCThrottle2Min= 19
FSCThrottle2Mid= 0
FSCThrottle2Max= 148
FSCReverser1Min= 0
FSCReverser1Max= 82
FSCReverser2Min= 0
FSCReverser2Max= 84
FSCSpoilerMax= 199
FSCSpoilerMin= 15
FSCSingleThrottle= 0
FSCSingleReverser= 0
FSCThrIntervent=On
FSCTQMotBuffer= 13
/ Top and Bottom Buffer zone to switch
/ off Throttle Motors (default 13)
/ FSC Throttle Hardware Ver 0
/ Cockpitsonic EHID
/ http://www.cockpitsonic.com (http://www.cockpitsonic.com)
EHIDComm=Off
/ Can be set to 'On', 'Off', 'localhost'
/ or IP Address
/ ELAN MCP hardware
ElanComm= 0
ElanBaudRate=
/ Please leave ElanBaudrate empty
/ unless you know what you are doing(!)
/ Aerosoft 747 MCP hardware www.mcp747.com (http://www.mcp747.com)
AerosoftComm= 0
AerosoftFPV= 14
AerosoftDHRST= 0
/ Defines the action (offset 0x4F4)
/ of the Aerosoft FPV button or DH
/ Reset button, e.g. 14=FPV, 6=CTR
/EicasButton1=???
/ You can define the action (offset
/ 0x4F4) of each of the 10 EICAS
/ buttons by setting the corresponding
/ value here (e.g. EicasButton1=71,
/ EicasButton10=87)
[EPIC]
DisableRemoteMCP=Off
/ Set to on to disable input from
/ other programs using these offsets
/ via FSUIPC
/ Syntax: input type = joystick,
/ axis
[Extra]
NoFSCOptions=Off
Good evening bob.
Thank you for publishing the ini file.
I'm going to my cockpit at the end of the week and I'll give my ini files.
Just a few questions:
Which version of pm do you use (build 518?)
Can you publish the ini du cdu?
I would like to put them in my place to compare the behavior of the plane.
Do you think we need to start a complete installation again
of cdu and mcp because our programs have been installed for a long time?
Thank you.
Patt
Quote from: Patt737 on April 19, 2018, 12:39:00 PM
Good evening bob.
Thank you for publishing the ini file.
I'm going to my cockpit at the end of the week and I'll give my ini files.
Just a few questions:
Which version of pm do you use (build 518?)
Can you publish the ini du cdu?
I would like to put them in my place to compare the behavior of the plane.
Do you think we need to start a complete installation again
of cdu and mcp because our programs have been installed for a long time?
Thank you.
Patt
I just shut the airplane down, but later I will post the CDU ini. I do not think a reinstall is necessary. I am using 519 and 518. There are a couple parts of the software not available in 519 so that is why the difference.
Hello everyone and hello Bob.
I did not have time to try.
I had taken a few days of vacation.
I think we will resume testing this weekend.
Do you still agree to communicate me your CDU ini ?
If so, thank you very much.
See you soon for the results.
Patt
Quote from: Patt737 on May 01, 2018, 12:12:18 PM
Hello everyone and hello Bob.
I did not have time to try.
I had taken a few days of vacation.
I think we will resume testing this weekend.
Do you still agree to communicate me your CDU ini ?
If so, thank you very much.
See you soon for the results.
Patt
Yes I will post!
Good evening Bob and good evening to all.
Still no published file?
It does not matter because we have finally solved our problem.
1) In the file PMX7378 there is a pdf file installation.
It contained these lines:
'' Whether you use the MCP or CDU to set the AP factors (default):
PITCH FACTOR: 30 ROLL FACTOR: 75
N.B. Pitch and Roll factors are not relevant when using the default FS AP mode ''
That's what we had done ....
But it is also what caused the oscillations.
Today we use the basic data of the mcp and everything is working properly.
2) When we were doing updates we did not delete the ini file.
And when we compared with the bob file we realized we were missing lines.
So we redid all the updates to re-create an ini file for each install.
Now our plane is very stable and landed correctly.
We have two other questions:
1) Have you had problems with eicas with the latest update
windows 10?
2) Which command line (cdu or mcp) activates the request of the 2 autopilots for an automatic landing.
Thank you for your help.
Patt.
Hello,
I'm a little bit surprised.
Why is there no more answer here?
Patt.
Hi Patt,
Please don't get upset with the timeliness of members replying, it's that time of the year where a lot of people spend more time with their families and/or other outdoor activities...in other words, it's the slow period for flight simulator builders.
I am sure Bob will post his file soon enough. As for me, I cannot help much right now because my sim(s) are in total disarray; however, I will have some major changes coming in the next few weeks...HOORAY!
In the mean time, please hang in there as others will chime in soon. How about you making some YouTube videos of things that are happening and how you're fixing them...it would be a great help for others.
Kind Regards,
John
Hello,
I understand.
But the last message from bob is from May 01, 2018.
It is normal to enjoy family and holidays.
But can not anyone answer me on this question? :'(
2) Which command line (cdu or mcp) activates the request of the 2 autopilots for an automatic landing.
Yours sincerely.
Patt.
Quote from: Patt737 on June 09, 2018, 01:37:42 PM
Hello,
I understand.
But the last message from bob is from May 01, 2018.
It is normal to enjoy family and holidays.
But can not anyone answer me on this question? :'(
2) Which command line (cdu or mcp) activates the request of the 2 autopilots for an automatic landing.
Yours sincerely.
Patt.
Hi Patt. I do tend to layoff the sim in the summer time as it makes my house way too hot. I am slowly getting back into the game now. How is your sim doing and did you find an answer to this question?
Quote
1) Have you had problems with eicas with the latest update
windows 10?
2) Which command line (cdu or mcp) activates the request of the 2 autopilots for an automatic landing.
Thank you for your help.
Patt.
Hi Pat, I don't run Project Magenta on Windows 10 so therefore couldn't answer this question, but I will answer that I can't answer this.
#2. In order to couple the "2 Channel autoland" you need the following.
#1 Both NAV1 and Nav2 Must be tuned to the ILS. #2, Both Course Knobs set to the correct approach course. #3. LOC mode until Established and before you fly over (you must be underneath it) the G/S Press Approach mode and press the second channel CMD on the MCP. PFD May Display (NO AUTOLAND) But will change on approach to LAND2 If successful.
Trev
Hi Patt,
Unfortunately I´m running the EICAS on Win7, therefor can´t comment. However I noticed that the "throttle bug" N1 (green V) is missing. Even though THROTTLE BUG = ON is set in the pfd.ini.
No clue why :-[
May I anyway throw in my 2ct worth concerning Autoland with PM.
Concerning Autoland I found this:
Just in case you haven´t seen this, old but nevertheless still valid, on mycockpit.org:
http://www.mycockpit.org/forums/showthread.php?t=14382&highlight=autoland (http://www.mycockpit.org/forums/showthread.php?t=14382&highlight=autoland)
Another thing is that, depending on your aircraft.tx in the CDU Types Dir, you will see on the PFD FMA either CMD only when in autoland mode, provided Trevor´s hints are all set accordingly, or you may see "Land2" and later "Land3".
This depends on what´s been set in the a.m. aircraft.txt file (at the very end of file)
It´s obviously a Boeing option. Therefor you my change it according to your liking:
Aircraft.txt example from PM´s flight model B737-800 for P3Dv4:
Original setting showing CMD only:
ACMD1=CMD
ACMD2=FD
ACMD3=CMD
ACMD4=CMD
ACMD5=SINGLE CH
Mod this if required to:
ACMD3=LAND2
ACMD4=LAND3
Hope it helps you a bit further.
Best rgds and always 3 greens
Pete
What amazing Information. Thank you all!
Trev
Pete! Thanks for the post! Looks like good stuff I give it a look...