Most of the commonly reported issues and questions are answered in the Frequently Asked Questions (FAQ) option under the Support menu of this website.
*** PLEASE NOTE ***
Your forum account is not the same as the account used in the shop. They are completely separate accounts.
1st December: A new version of the GoFlight Interface Tool for MSFS is now available.
12th November: A new version of the GoFlight Interface Tool for X-Plane is now available.
6th June: A new version of Virtual Flight Sim Hardware is now available (huge update)
21st November: A new version of the GoFlight Interface Tool for FSX/FSXSE/P3D is now available.

rotary knobs

morpheousmorpheous
in GoFlight Interface Tool - Technical Support
Can someone give an example of how to program a rotary knob? I can get the on off switches to work after I use detective to determine the event name but have no clue how to program an event that required a rotary knob.
Thanks
Jim

Comments

  • admin_ppsadmin_pps

    Hi Jim,

    What aircraft are you using? I'm asking because the NGX and 77X handle it differently.

    Best wishes

    Steve

  • morpheousmorpheous
    I'm trying to program for the q400. I know there are challenges with that aircraft until the pro version comes out.
    Jim
  • admin_ppsadmin_pps

    You need to use CLOCKWISE/ANTICLOCKWISE Input Events with a different event for each and the Input Action ROTATE.

    E.g. for an autopilot's VOR course:

    CLOCKWISE, VOR1_OBI_INC, ROTATE

    ANTOCLOCKWISE, VOR1_OBI_DEC, ROTATE

    Best wishes

    Steve


  • morpheousmorpheous
    I'm afraid that doesn't have any effect. I have the Mcpro with default fs options working so The course knobs are working. The one I'm trying to program is the barometric pressure dial. Using detective I see the event is MAIN_INDEX1_QNH_KNOB_ANGLE. lvar Data : 39
    Obviously lvar increasing and decreasing is the event I'm looking for but I can't seem to get this to work. Any ideas? I'm trying to program the rotators knob on the rp 48
    Jim
  • admin_ppsadmin_pps

    That looks like the angle of the knob to do with displaying its image in the VC. Have you tried the simconnect barometric events?

    Best wishes

    Steve

  • morpheousmorpheous
    Yes, there doesn't seem to be any effect using the barometric event.
    Jim
  • admin_ppsadmin_pps

    I have found the following on a forum which should sort everything out for you (note the XML variables show up as Lvars):

    Abstract
    This document is a specification for the FSX XML vars based External Interface included in the MJC Platform

    Applicability
    Applies to every edition of the MJC8Q400 version 1.008

    Description
    The XML based access to MJC8Q400 systems can be used to read and write most of the numerical variables within the MJC8Q400

    Access is performed in a request/response sequences via 4 dedicated XML variables:

    MJC_VAR_READ_CODE
    MJC_VAR_READ_VALUE
    MJC_VAR_WRITE_CODE
    MJC_VAR_WRITE_VALUE

    Interface contains 2 special return codes, which are returned in the MJC_VAR_READ_CODE/MJC_VAR_WRITE_CODE:
    9991999 // Acknowledge success
    9992999 // Acknowledge variable not found


    READING THE VARIABLES

    To read a variable from MJC, a requestor would perform the following steps:

    Design time
    1. Identify the variable name in the varlist.xlsx located under \SimObjects\Airplanes\mjc8q400\doc\scripts
    2. Derive the 32 bit var name hash using the IntVarCRCGen.exe utility

    Run time
    3. Write the var name hash into MJC_VAR_READ_CODE
    4. Wait for MJC_VAR_READ_CODE to indicate one of the Acknowledge codes (success, or var not found)
    5. If Ack is success, the variable value is in the MJC_VAR_READ_VALUE

    WRITING THE VARIABLES

    To write a variable to MJC, the following steps are performed

    Design time
    1. Identify the variable name in the varlist.xlsx located under \SimObjects\Airplanes\mjc8q400\doc\scripts
    2. Derive the 32 bit var name hash using the IntVarCRCGen.exe utility

    Run time
    3. Write the desired variable value into MJC_VAR_WRITE_VALUE
    4. Write the var name hash into MJC_VAR_WRITE_CODE
    5. Wait for MJC_VAR_WRITE_CODE to indicate one of the Acknowledge codes (success, or var not found)
    6. If Ack is success, the variable was written

    Considerations:
    + Only the numerical variables can be accessed by the XML interface
    + A Read and a Write operation can be executed concurrently
    + The response time of the interface equals to a single FSX visual frame. Due to this fact, the interface might be blocked during aircraft repositions or while the blocking FSX dialogs, such as select flight, or weather setting are shown


    Copyright (c) 2013 Majestic Software


    Forum link here: http://www.molitor-home.de/fs/forum/viewtopic.php?t=1729&p=7123

    Best wishes

    Steve

  • morpheousmorpheous
    Wow sounds promising, I wish I was smart enough to figure out how to do this.

    Can someone post an example of using this..
    Jim

  • admin_ppsadmin_pps

    Hi Jim,

    I've just written a little guide for you and others. Its here: http://www.pollypotsoftware.org.uk/support/forum.html#/discussion/230/how-to-guide-build-bespoke-events-for-the-majestic-dash-q400

    Best wishes

    Steve


  • morpheousmorpheous
    Brilliant! It works great.. thanks for that Steve.

    Jim
  • admin_ppsadmin_pps

    Hi Jim,

    Just added a guide for the lights: http://www.pollypotsoftware.org.uk/support/forum.html#/discussion/231/how-to-guide-settings-lights-for-the-majestic-dash-q400

    Best wishes

    Steve

  • morpheousmorpheous
    This is all really great stuff. Do you think it would be possible to get an updated MCPRO profile for the Q400?

    Also, I'm having difficultly with the "EFISdata_->EFCP_controls1.range_selector" What value needs to into the "MJC_VAR_WRITE_VALUE" ? If I use 1 the knob snaps back to the 20mile range but I can't get it to move from there. I can see from detective that the knob moves in increments of 5 I think.

    Jim


  • admin_ppsadmin_pps

    Hi Jim,

    If you have Goflight hardware selectors, you will need a Bespoke Event for each position on the selector. Each of the Bespoke Events will send a different MJC_VAR_WRITE_VALUE (I assume starting from 0, then 1, then 2, then 3 etc.). You can then assign the relevant  Bespoke Event to a Goflight Selector position.

    If you are trying to use the Bespoke Events on a rotary, you would need 2 Bespoke Events (clockwise and anticlockwise). They would need to read the current value (i.e. the current position) as described in the how to lights guide mentioned in a previous post, then add (Set +) or subtract (Set -) 1 from the bespoke variable assigned the position data and then use Set = to set the MJC_VAR_WRITE_VALUE to the updated bespoke variable. Also include an If check to limit the max and minimum values of the bespoke variable so you cannot go over the allowed position values.

    Best wishes

    Steve

  • morpheousmorpheous
    Hi again,

    I'm trying to program the IAS button on the autopilot to work with the speed button on the MCpro.

    I'm using
    MJC_VAR_WRITE_VALUE = 1
    MJC_VAR_WRITE_CODE=42203 

    but am having no luck, it should be the AP_indicated_airspeed_mode  button.

    Can anyone help? Steve?

    Jim

  • admin_ppsadmin_pps

    Hi Jim,

    I get 33470 for the write code. Remember to remove any spaces in the variable name.

    Best wishes

    Steve

  • morpheousmorpheous
    Steve does it not go in like this?

    AFCS_->FGM[1].ias_to_maintain
    =42203

    perhaps i'm using the wrong line item
    Jim
  • admin_ppsadmin_pps
    edited July 2015

    Its AFCS_->inputs.mode_button.

    You use a value of 0 to 13 as follows

    NONE 0, IAS 1,
    VS 2, VNAV 3, ALT 4, ALTSEL 5, HDG
    6, NAV 7, APPR 8, BC  9, STBY 10, AP  11, YD 
    12, HSISEL 13

    Best wishes

    Steve

  • morpheousmorpheous
    Thanks Steve, I missed that one, works great now.

    I'm having an issue assigning a few engine commands, perhaps they are not programmable.

    I'm looking to assign the following to push buttons on my GF-P8

    MCL (Maximum Climb power)
    MCR (Maximun Criuse power)
    MTOP (Maximum take off power)

    I can't find them on the XML file.

    Can anyone help with this?
    Jim

  • admin_ppsadmin_pps

    Hi Jim,

    Use a write code of 198197 and the following write values:

    1 - MTOP, 3 RDC TOP RESET, 4 - RDC TOP DEC, 5 - MCL, 6 - MCR, 7 - RDC NP

    Best wishes

    Steve

  • morpheousmorpheous
    Wow that was quick, thank you so much, I forgot to add Autofeather as well.

    Cheers,

    Jim
  • admin_ppsadmin_pps

    Engine 1: 68825, 0 - OFF, 1 - ON

    Engine 2: 119566, 0 - OFF, 1 - ON

    Best wishes

    Steve

  • morpheousmorpheous
    Thanks Steve but the MJC model shows only one button for Autofeather?
    Jim

  • admin_ppsadmin_pps

    My mistake, its just 68825 with 1 or 0.

    Best wishes

    Steve


  • morpheousmorpheous
    Thank you Steve
    Jim

  • twgintwgin
    Awaking this old thread, has anyone done some work on programming knobs in X-Plane ?  I am using GIT with GA type planes and having trouble attacking the problem of getting RP-48 knobs to be used for adjusting altimeter, moving the bug around, and so on.  I can't seem to find any examples around...

    Thanks,

    Terry

  • admin_ppsadmin_pps

    Hi Terry,

    Its very straight forward. Open up the file <xplane directory>\Resources\plugins\Commands.txt in a decent editor (I recommend Notepad++). Search for what you want to change e.g. heading or alt. You will then locate suitable commands that can be sent to XPlane. All you need to do is assign these commands to the CLOCKWISE and ANTICLOCKWISE inputs via the dropdown list boxes for the rotary concerned. Use the Input Action of ROTATE.

    E.g for autopilot altitude:

    CLOCKWISE: sim/autopilot/altitude_up

    ANTICLOCKWISE: sim/autopilot/altitude_down

    Input Action: ROTATE.

    Remember to enable the device if you haven't already.

    Best wishes

    Steve

  • twgintwgin
    thanks ! I'll give it a try...

Sign In or Register to comment.

© Vanilla Keystone Theme 2025