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.

Basics

Trying to set this up with 2.0.300.0
Long time user with the PDMG interface, hardly ever touch the mouse now. Thanks Steve.

Starting with the Basic Microsoft C172 (little steps to start with) Battery master switch, I can toggle it on and off and have the led on the GF-T8 come up.
By flicking the switch twice. I read a previous post that said you should use the detective to set up for the T8.

This is were I get lost !!  I can get it to show Master battery switch Toggle but no on off function.
Someone care to explain in a easy step how to do this, if I can get my old head around this I can then progress.

Pls don't use terms "if" "and" "next" "else" etc, way over my head..

Cheers
Trevor

Comments

  • edited February 2013

    Hi Trevor,

    The Detective will show you what the developer of the aircraft has used to initiate an action. In this case its a toggle event. Most of the time there are alternative events you can send such as autopilot on and autopilot off as well as autopilot toggle.

    If I didn't want to use a toggle, I would search the simconnect event list here: http://msdn.microsoft.com/en-us/library/cc526980.aspx

    to find alternatives.

    Always use simconnect events first. If the aircraft is complex and uses its own events and lvars thats when you really need to start using the detective and building your own bespoke events.

    Best wishes

    Steve

  • edited November -1

    Hi Trevor,

    I have had some time this evening to look into detail about your particular request. Sadly the master battery switch is one of those events without an on or off function. It can be set via a simconnect variable, but GIT doesn't support that yet.

    Your best bet is to send the toggle event for both on and off button actions and it should work ok as long as the switch is set to the same position as in the aircraft when first loaded.

    Alternatively use a button instead of a switch as toggle suits buttons very well.

    Best wishes

    Steve

  • edited November -1
    Thanks Steve, I were pulling my hair out in vain after all, I thought I would start with a basic common Microsoft aircraft and basic switch to start with.  May have to reorganise setup for button instead of switch.

    Cheers
    Trevor
  • edited November -1
    Hi Steve, now using 2.0327.0 in FSX, had another play tonight. PDMG 737 working great with it.
    Back to MS Cessna 172 set up. Doing the straight MCP unit with FSX defaults set.
    Everything works except for the Alt button.
    input = on,      AP_ALT_HOLD
    Nothing
    Light display= AUTOPILOT_ATTITUDE_HOLD
    Light Display = ON       Value = 1

    Problem, Button light does not illuminate,  light in vc unit does.
                  Set the Altitude and VS rate (before I need it) When I activate the Alt hold button
    both the Alt window reading and the VS window revert back to Zero.
    Happens everytime, even just the Alt set soon as I push the button the reading zero's back again.
    Not the way it normally behaves with old fashion GoFlight system. <G>

    Regards
    Trevor


  • edited November -1

    Hi Trevor,

    The new code for the GF166 has caused an updating problem and the default settings for altitude hold were wrong (it was set to atitude hold instead of altitude lock). Both have been corrected in version 2.0.329.0 that I have just uploaded. You will need to reset the FS defaults on the MCPPRO tab or manually change the Altitude Hold Light Data.

    Best wishes

    Steve

  • edited November -1
    G'Day Steve,
    2.0.329.0 loaded and LED on Alt hold button now ok but still have problem with the displays.
    When I activate the Alt hold button the Alt window reading drops now to 300 and the VS window reverts back to Zero.

  • edited November -1

    Hi Trevor,

    When I tested this yesterday, clicking the ALT HOLD button in the virtual cockpit did exactly the same thing so its behaving as it should.

    Best wishes

    Steve

  • edited November -1
    Hi Steve,
    My setup, if I click on the hold button in the vc it has never altered the pre entered data in any of my aircraft using the GF -MCP. I would normally load say 2500 ft fly then de-activate hold, climb over saddle or go down and investigated a town, push the hold and resume at previous setting 2500 ft

    I'll go back to old GF set up and check today to confirm.

    Cheers
    Trevor
  • edited November -1
    OK, let me know.
  • edited March 2013
    I must not swear, I must not swear, I must not swear, I must not swear
    Thought I would try it out on my old FSX an old machine no GoFlight stuff on it -------FSX Drive kaput !!!!!
    Plan B
    Fired up flying machine and reloaded old GoFlight Cessna files
    GF-MCP advanced works perfect Alt hold button pushed many times and never set the numbers back to zero. Just the way it's worked for many years.

    Reload GF-MCP config as per manual = all set to Project Magenta  with both boxes clear for arm/disarm autothrottle.

    Loaded new 2.0.330.0 with "only" the MCP activated and FSX with prepar3D unticked.
    Manually entered AP command, turned autopilot on and off. No led indication on the GF-MCP, had entered that correctly.
    Entered the Alt Hold and tried that, soon as button pushed - digits reset in the VC.
    Don't reset when pushed in the VC.

    Set the MCP tab to FSX defaults just in case I had mucked up.

    Config file shows 27KB.
    Now I end up with complete failure.
    No LED's on buttons light, no displays are active. AP CMD will activate as it did when I manually entered it which when pushed the second time deactivated the AP, now to deactivated I have to use the Disconnect bar.
    Everything works in the vc ie: rotaries alter the VC readings.

    Going back a couple of versions all the digits worked ok along with the LED's.

    Sorry Steve if its not helping you. Love to see this working but I'm only on step 1 basic plane.......
    God help you when I try the PMDG JS4100 <G>

    Regards
    Trevor
     
  • edited November -1

    Hi Trevor,

    I'll double check the code this evening.

    Best wishes

    Steve

  • edited November -1

    Hi Trevor,

    Just a note to say I haven't forgot about your issue, I just haven't had a chance to look at it in any detail. Hopefully tomorrow I'll find a chunk of time.

    Best wishes

    Steve

  • edited November -1

    Hi Trevor,

    I have changed the default events for the autopilot on/off and altitude hold so it behaves how you expect it. I would like you to test this and then let me know if the displays still play up.

    Download link: https://www.dropbox.com/s/zvm73i7mpqanlq1/Goflight%20PMDG%20Interface%202-0-332-0.zip

    Best wishes

    Steve

  • edited November -1
    Hi Steve,
    Brilliant, skipped your 332 and went straight to 345. Everything as predicted

    Technically,  when the Avionics Master is turned off the digits should go out.
    What happens is that they go out after the Master Battery is turned off.
    One little hiccup is when the master battery is turned on again the GF-MCP is working before the Avionics is on but the digits do not show until each rotary is turned.

    Not worried by this at all, just a finding.
    Re using the toggle for switch actions, as you said above works ie: use on and a off for the T8
    Found any toggle action used will be loaded as on, even if aircraft is saved with it off.
    Any switch action as a on/off will be in the position saved with the flight.

    Now back to program some more actions. <G>

    Regards
    Trevor
  • edited November -1
    Quickie Steve I forgot to add.
    My GF-TQ6 is greyed out, I understood this had been added recently.

    Cheers
    Trevor
  • edited November -1

    Hi Trevor,

    I'll add that requirement to the development plan.

    In relation to the TQ6, is it enabled when in the VC and does the TQ6 count on the status page equal 1 or more?

    Best wishes

    Steve

  • edited November -1
    Steve,
    TQ6 shows as 1 on the status page.
    All entries in Goflight TQ6 are disabled
    FSUIPC knows it is in the system and can programme it, it's clear at the moment nothing is programmed .

    I don't actually use the throttles but use the 4 buttons of the TQ6, the throttle and mixture are used with FSUIPC using CH throttles.
    If I crawl under the panels with a torch I could still operate the throttles but wouldn't be able to see the screens <G>

    Cheers
    Trevor
  • edited March 2013

    Hi Trevor,

    Is it enabled when in the Virtual Cockpit? Also check the TQ6 ADV thread as someone had the same issue.

    Best wishes

    Steve

  • edited March 2013
    G'Day Steve,

    Checked the other thread, no help.
    I am using the GF-TQ6  basic unit.
    Are in the virtual cockpit, both GoFlight and FSUIPC will control the levers/buttons ok.

    Still greyed out with no access in the interface.

    Log read everything down to the lines
    simconnect: event duplicate (about 4 of them)      next line read
    simconnect: exception received: name_unrecognized       next and last line
    Synchronising switches and selectors complete


  • edited November -1

    Hi Trever,

    The levers are not supported as yet - I started writing the code for axis support yesterday.

    However, you can assign the buttons if the aircraft is not the NGX. Can you attach a screen dump of the TQ6 tab for me to look at.

    Thanks

    Steve

  • edited November -1
    No worry Steve,
    I don't use the levers just the buttons.

    Think is what you wanted.

    Cheers
    Trevor
    image
  • edited November -1

    Thanks. Prepar3d or FSX?

  • edited November -1
    FSX Steve and DX10 on win7 64 bit.

    Cheers
    Trevor
  • edited March 2013

    Hi Trevor,

    I have identified and fixed this bug. Wait for the next release.

    Best wishes

    Steve

  • edited November -1

    Hi Trevor,

    This issue is now fixed in 2.0.351.0

    Best wishes

    Steve

Sign In or Register to comment.