• Project Magenta - High End Flight Simulation
  1. ND not handling ADF correctly (ADF1/2)

    May 14, 2011 by Enrico Schiratti

    Should you have strange effects when selecting the ADF1 or 2 in the ND via the EFIS selector, like needles missing or misdirecting, please check your FS aircraft.cfg file for these entries. It should show Adf.2 in order to operate correctly. Unfortunately this can’t be set remotely by the PM software.

    Edit your selected aircraft’s aircraft.cfg file:

    [Radios]
    // Radio Type = availiable, standby frequency, has glide slope
    Audio.1 = 1
    Com.1 = 1, 1
    Com.2 = 1, 1
    Nav.1 = 1, 1, 1
    Nav.2 = 1, 1, 0
    Adf.1 = 1
    Adf.2 = 1
    Transponder.1 = 1
    Marker.1 = 1

    Actions: Comments (1)
  2. Airbus Master Caution/Fire and Failures

    May 13, 2011 by Enrico Schiratti

    The Master Caution/Warning buttons on Captain and First Officer Side both access these offsets. They are controlled by the Glass Cockpit as a response to Instructor Station Failures and ECAM Warnings.

    INPUTS:
    0x56F8 .0 MasterCautionSwitch
    0x56F8 .2 MasterWarningSwitch

    OUTPUTS:
    0x56F7 .0 MasterCaution
    0x56F7 .2 MasterWarning

    Failures Input Variable
    0×5750 1 FailureCode

    Values written to that byte offset cause these failures:
    10 IAS/Pitot Fail
    50 APU Fail
    51 Engine 1 Fire
    52 Engine 2 Fire
    55 APU Fire
    61 fwd1pumpfault
    62 fwd2pumpfault
    63 ctr1pumpfault
    64 ctr2pumpfault
    65 aft1pumpfault
    66 aft2pumpfault
    91 AC BUS 1 Fault (91)
    92 AC BUS 2 Fault

    Actions: Comments (1)
  3. How to find Variable names in pmSystems

    by Enrico Schiratti

    To connect hardware via offsets if you are building your own overhead panel or for any other reason you need to see which variable does what and which offset it is connected to, you can do the following:

    Press [Esc] for the Menu
    Enable “Development Mode”
    Enable “Show Variable Names”
    Then press [Esc] to close the Menu again

    Move the mouse over the switch you want to check and you will see the variable name, the offset, the offset type and its value in a floating status bar.

    When you hover over a multiple switch, like for instance in the Airbus or the Boeing 747, it may show the upper value, the lower one as well as the input value (optional).

    If you click on the switch, you should see the value of that variable change.

    Actions: Comments (1)
  4. Project Magenta Registration Process

    May 11, 2011 by Enrico Schiratti

    [purchase]
    [website registration] – [status set to 'customer']
    [Download id not defined]
    [product request with computer ID generated by the software] – [response with registration keyvia e-mail]

    When you have purchased a Project Magenta Product, we will be notified by the vendor that the registration process can be started.

    You will receive an e-mail confirming your order and once you are registered on the website as a user, your status on the website will be set to Customer and you will be able to download the software update from there.  

    That process of setting your status is manual and it may take up to 24 hours to post, but it usually happens much sooner.

    In the Software Updates section you will then find links to the main Setup/Installation file, usually an executable, which you can download and install on the computer that you will be using it on.

    Once the installation is completed, you will get a request to enter your registration key. It usually shows a Computer ID generated by the software. This code needs to be sent to us and you will get your registration key code back via e-mail. If you have any type of question we can help you with, please Contact Us

    Actions: Comments (1)
  5. Using FSX or Third Party Aircraft with Project Magenta and FS

    by Enrico Schiratti

    FSX or third party aircraft & PM Autopilot and Systems

    General: At this time, to use our software with FSX you will have to disable the AP gauge in the FSX panel.cfg of the aircraft type you are using for flight with the PM / MCP software. Generally if not using a panel at all in MSFS, then the only section you need in the panel.cfg is the section referring to [VIEWS] everything else can be deleted. Please *always* keep a back-up of your original files in case you have to revert back. 

    If you want to use third party aircraft that has their own systems (APU/Electrical/Hydraulic etc) these need to be disabled as well. They are not going to work and interact with the Project Magenta Synoptics. Systems etc. These also have to be disabled by changing the panel.cfg file.

    • If you are using the default FSX Airbus, you must disable the FBW command in the aircraft.cfg file: fly_by_wire = 0
    • Use either the above method re the panel.cfg or copy a FS2004 737 panel.cfg for the Airbus, this is to ensure that the AP functions work.
    • Make sure FSUIPC and WideFS are fully up-to-date with current versions.

    All of the above are required for correct operation of the FCU in FSX. If using another add-on third party a/c model, make sure also that the above items are conformed to.

    Actions: Comments (1)
  6. Running MCDU or CDU full screen

    May 10, 2011 by Enrico Schiratti

    The Airbus Type MCDU and the Boeing Type CDU can both be run full screen without the bitmap for the keyboard and line selection keys (LSKs).

    Some basic commands are:

    [Ctrl-O] Toggles OpenGL and Normal Text Mode

    The normal text mode is just there for backward compatibility, and should be avoided. We recommend to use OpenGL. Most modern computers should be able to handle it and it is closer to the real thing. Please note that there is some FMC hardware which doesn’t require to set any such parameters, such as the CockpitSonic FMC products.

    Please Note: Any changes you make with the following commands need to be saved by exiting the program with the [Ctrl-Q] command. If you just switch off the computer, all settings will be lost.

    [Ctrl-Shift-O] Removes the bitmap and displays the FMC’s text in OpenGL Windowed mode. If you want to use the software this way, you can resize the window by grabbing the corners and moving them with the Mouse.

    [Alt-F] will force Full Screen Mode in OpenGL and toggle back if needed

    If you want to position the FMC’s screen on a secondary monitor, move the FMC to that screen, then press the corresponding command.

    [Ctrl-R] resets the size of the FMC to its default

    The positioning of the text in full screen mode can be done via the Keyboard commands Ctrl-Cursor Keys or Alt-Cursor Keys. There is also a special menu that allows you to adjust font size, scratchpad and title positoning.

    In the Airbus MCDU it can be accessed via MCDU MENU twice, then  DISPLAY, then FULL SCREEN (one page for text, frame and font)

    In the Boeing CDU you press MENU twice, then LSK  DISPLAY and choose FULL SCREEN (one page for text, frame and font)

     These things can also be set via the CDU.INI or MCDU.INI file:

    [OpenGL]
                                  / This section is for OpenGL settings
                                  / and OpenGL Full Screen Display
    UseOpenGL=On
                                  / Will use OpenGL rather than normal
                                  / windows text, 24 columns, 14 rows
    FontSmoothViaPolygons=Off
                                  / When set to on, font smoothing
                                  / for display is done via polygons,
                                  / if off, via blended outlines
    UseOpenGLFull=On
                                  / Bitmap-less full screen operation
    SetOpenGLFull=On
                                  / Will automatically Maximize screen
                                  / for full screen operation
    (followed by other parameters)

    
    Actions: Comments (1)
  7. What is a “Flight Simulator Offset”?

    by Enrico Schiratti

    To communicate with a Flight Simulator,  Project Magenta and other software uses the resources offered by FSUIPC (Peter Dowson) and XPUIPC (Torsten Spiering). For instance, to read the MSL altitude of the aircraft, a request is sent to the respective program and it would essentially ask for a location and the length of the value it is asking for.

    Depending on the size of the value, the precision needed or even texts , this request can be from one to hundreds of bytes long. In most cases there are just bytes (1 byte), words (2), long integers/dwords (4)  or double precision floats (8 bytes). Texts would be as long as the maximum expected string and are usually zero terminated. There is a special case for on/off bits where the value would have to be extracted from the smallest data unit that is requested, i.e. from a byte.

    Generally, you do not have to worry about these things… the software gets the data and writes the values it needs. But in some cases when you do your own interfacing of hardware or in some case even are programming your own features, you need to know what information can be found in which place. For this we have our own Project Magenta offset list as well as Peter Dowson’s SDK (Software Development Kit).

    With the advent of pmSystems, things changed a little, because values from and to the flight simulator were given names (variable names in this case) and could be used to make certain things happen depending on others. In pmSystems we have a file called SysVar.TXT and it contains a long list of variable names for FS data, for information handled by Project Magenta Software as well as switches you may have in your hardware.

    Here are some examples for the notation of these offsets, 0x merely indicates it is a hexadecimal address:

    Bit:
    561D .4 GenBus1
    Offset 0x561D, bit 4, PM Generator Bus 1

    Byte:
    55F0 1 CaptPFDDim
    Offset 0x55F0, 1 byte length, PM Captain Side PFD Display Dimmer

    Word:
    05DC 2 fsSlew
    Offset 0x5DC 2 bytes, FS Slew Control

    DWord:
    0808 4 fsYawDamper
    Offset 0×060, 4 bytes, the FS Yaw Damper

    Double:
    2834 8 fsBattVolt
    Offset 0×2834, 8 Bytes, FS Battery Volt indicator

    If you need to quickly check a value for an FS Offset while your simulator is running (for instance the yaw damper) you could look up the offset using pmFileCheck by entering the offset and its length. If you enter the offset, the length and a value, you can also set that offset within FS. If you are running pmSystems, you should see a dropdown box in the lower left corner with all Variables listed alphabetically.

    In pmSystems you can also use the variable display which shows you in real time the values of all the sysvar variables at any given moment.

    In the FMCs, if you go to the MAINT page, you can also check offsets by using the IPC menu.

    For PM Offsets please check: http://www.projectmagenta.com/pmoffsets/
    For FSUIPC offsets please check the FSUIPC SDK on http://www.schiratti.com/dowson.html

    Actions: Comments (1)
  8. About the Tutorial Section

    May 5, 2011 by Enrico Schiratti

    This section is for tutorials,  tips and tricks as well as FAQs as they pop up from support requests or customer comments.

    Registered users should be able to add comments and suggestions, so please do.

    Actions: Comments (1)