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.

Flight Factor 777 EFIS + MCPPro profile (X-Plane)

This profile is for the Flight Factor 777(1.83 but old versions should work fine too).

 Please see the readme, if you have any questions or find a problem please ask and I'll help if I can.


Steve McNitt
«1

Comments

  • New version after Wayne found a few glitches, please update to GIT 1.3 before trying to use , see readme for changes.



    Steve McNitt
  • Thank you, MCP PRO VOR LOC and APP button lights now come on. Still trying to find out why my minimums rotary DH knob and Baro knob will not work properly. Since it works at your end it must be something related to my setup.

    Thanks again!

    Wayne

  • edited May 2016
    Have you tried clearing out all the bespoke events in detective(big red button lower right corner) and then re import the bespoke events then the profiles for the hardware? I've seen it before on a few occasions where the bespoke events don't get fully imported then stuff breaks. usually starting fresh works.
    Steve McNitt
  • Yes I did this a couple of times with same result. Everything works but the EFIS DH and Baro rotary knobs. Haven't noticed anything else. Its a real mystery to me. I even re-downloaded your profile for the 777 and started fresh from there.

    If anybody comes up with a solution please let me know.

    Thanks

    Wayne


  • Hi Wayne,

    Have you checked the hardware is working correctly?

    Best wishes

    Steve

  • Hi Steve

    Yes, it works fine with your GIT for FSX on the T7, 737NX and the Majestic Q400. Only have this problem with X-PLANE GIT.

    Best Regards

    Wayne

  • Need a third person to see if it works or something is lost when I export.
    Steve McNitt
  • I can try it later on and debug at the same time.

    Best wishes

    Steve

  • edited May 2016

    Wiped all my devices and Detective. Loaded in Bespoke Events, loaded in MCP PRO config and then loaded in EFIS config and everything works great.

    Wayne, can you check Bespoke Events have been assigned against the EFIS rotaries.

    Also make sure you have nothing else installed that can manage Goflight gear that could be affecting it.

    Best wishes

    Steve

    PS: Check the log tab and also are you in DRE Mimic Mode?

  • Hi Steve

    Yes I am in DRE Mimic Mode. Don't know if this will help but I EXPORTED your EFIS.xml file that I loaded in the GIT and included it as part of this email and the two other files that are presently in the GIT are also included below. So everything appeared to load OK for the EFIS Module. I can't see anything interfering or affecting the GIT but I will keep looking, It's still possible that's the case. The problem has to be at my end.

    Having said all this I hope these files download OK. I will try and include them but not sure if they downloaded properly.

    Thank you for your time Steve

    Wayne 

  • Hi Wayne

    Your EFIS config is correct compared to mine. The only thing I can think, is that something else is configured to use the EFIS.

    Can you go into Detective and test the following Bespoke Events:

    T7_EFIS_MINS_CW

    T7_EFIS_MINS_CCW

    T7_EFIS_BARO_CW

    T7_EFIS_BARO_CCW

    and watch the EFIS in the VC and see if the rotaries move.

    Best wishes

    Steve

  • Hi Steve

    Thank you very much for suggesting I do this. As soon as I did these tests everything started working.

    Don't know why but it now works fine.

    Thank you so much Steve! Fantastic support.

    All the best!

    Wayne


  • Very strange indeed
    Steve McNitt
  • I'm trying to finish up 1 last  update for this profile.  Learning a few new tricks along the way and want to improve this.

    Made the CTR, TFC, MINS switch and BARO switch  functions a lot better for the EFIS , now the function above it will not trigger if you press and hold

    I need a 777 expert to tell me under which conditions that the IAS display is blanked? I know when FMS is controlling speed but exactly what "mode" is that called?
    Steve McNitt
  • Just saw this post. Don't know if I'm answering your question right or not. If I misunderstood your question I apologize. Let me try and explain how the IAS display works on my T7 with the goflight interface disconnected and then connected.

    I am not an expert on the 777 but I will tell you what I observed, first - with the goflight interface disconnected. Using the control panel in the Sim this how my T7 functions.

    When the auto pilot is engaged after take off and the LNAV and VNAV buttons are in the activated position (both LNAV and VNAV  button lights on) the IAS display will go blank and the speed is controlled by the FMC. If you want to manually control the speed you just push the IAS button "in" and the speed indication reappears in the display and you can then control the speed manually. If you want the FMC to take over the speed again you just push the IAS button "in" once again and the display goes blank.

    With my Xplane goflight interface connected the IAS display stays on at all times but you can switch from manual speed control to FMC speed control by pressing the SPD INTV (speed intervention) on my Goflight MCP PRO panel. So it works the same except the IAS display stays on.

    Best I can come up with for what mode this is as follows: I could stand to be corrected on this.

    FLC (Flight Level Change) mode maintains airspeed during a climb or descent, while VS mode maintains a specific vertical speed.

    I hope this helps in some way!

    Wayne






  • New version - Improved handling of the TFC CTR MINS and BARO switching, It will not trigger the function above anymore when you push and hold.
    Steve McNitt
  • Steve I downloaded New Version. 777_GFMCPPRO.XML imported OK to Interface but 777_GFEFIS.XML did not. I get message "Failed to Load Config Data for Device GFDEVHWTYPE_GFEFIS"

    I get these messages when I try to import 777.xml file in "Detective"

    T7EFIS_CTR Button has Errored

    T7EFIS_TFC Button has Errored

    T7EFIS_FPV Button has Errored

    T7EFIS+MTRS Button has Errored

    Wayne

  • edited May 2016
    Wayne, thanks for checking out the new profile.

    Did you delete all the old bespoke events in detective first?

    Those are the modified bespoke events, so you have the new EFIS config loaded but the events don't match up so it throws an error. (educated guess) 

    I've found I get that error if that's the case. 

    Restarting GIT and X-plane, then clearing the events , then finally importing the device configs fixes it for me when this happens.


    Steve McNitt
  • Hi Steve

    That is the process I followed. Anyway I just did it again. I deleted the bespoke events in detective and re-imported 777.xml file. It will not import all events from new version 777.xml file into detective. Same problem with same errors.

    So I deleted the 777.xml file again in Detective and went back to your previous old file. That one imports all events OK into detective. EFIS then works OK with your old file. Won't work with your new file, unless I'm doing something wrong but I'm following same procedure.

    Wayne



  • It could be worth checking you are using the same version of the 777.

    Best wishes

    Steve

  • Same version Steve. Might be worthwhile waiting to see if somebody else runs into same problem.

    Wayne

  • When I get home I will do another export of all the files and see if that helps.
    Steve McNitt
  • edited May 2016
    Wayne what driver version of goflight software are you using. I saw the older version do this exact problem on another system, the latest driver fixed it for him. This would also prove theres a bug in there.
    Steve McNitt
  • I'm using 2.25.2 - which ones should I be using?

    Thanks

    Wayne

  • OK Steve I downloaded 2.26.1 drivers and it does import the 777.xml file properly into detective and when I import the other files into my GIT they also import OK but I end up with the same problem I originally had with the DH rotary knob not working and the Baro knob not working. Just those two functions not working on the EFIS.

    When I test those functions in detective this time it does not work there. Remember I said (although very strange, I agree) when I did that on a previous posts it started working but that was with your older version GIT file.It seems my system will only work with the 2.25.2 drivers and your old version file. Very odd. Certainly confuses me.

    Unless you want me to do further tests I'm quite happy with the way your older version works on my system with the older drivers. Having said that perhaps that will mean I can no longer update future versions of the GIT.

    Wayne


  • edited May 2016
    It certainly appears to be a bug in the way the driver is communicating with the software.

    If memory serves there are a couple of versions of the EFIS firmware too and I wonder if this has to do with that. How old is your EFIS?

    Ive done all I can at this point Steve will have to take another look at this.
    Steve McNitt
  • Ok Thanks. I got my EFIS December 2013

    Wayne

  • Hi Wayne,

    I'll pick this up with you later in the week. Something odd going on here. I've just done 3.5 days coding straight, so need a few hours to myself before I start work in the morning.

    Best wishes

    Steve

  • Absolutely, thanks for your replies, no rush on this at all.

    Wayne

  • Hi Wayne,

    With the drivers that cause the issue can you monitor the status tab when you turn the dials on the EFIS and tell me if the GoFlight LED flash.

    Thx

    Steve

Sign In or Register to comment.