Results 1 to 10 of 10
  1. #1
    75+ Posting Member Lezam's Avatar
    Join Date
    Dec 2007
    Location
    New York
    Posts
    92
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Boeing FMC interface

    Hey everyone,

    Was wondering if anyone knows how I can make the LDS 767 FMC software display on another monitor. For example. I want to build my own hard wired FMC, but I would like the actual LDS fmc program to show up on a monitor like this:


    I know project magenta is an option, but they want about $1000 for their boeing software, and I honestly dont want to spend that much. Any help would be appreciated!

  2. #2
    150+ Forum Groupie pdpo's Avatar
    Join Date
    Nov 2005
    Location
    belgium
    Posts
    280
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Hi,

    I know Niko Kaan from the netherlands has his FMC on a seperate TV (so should be the same on the OSone LCD) check his site :
    http://home.planet.nl/~nwkaan/

    Greetz Peter Depoortere

  3. #3
    500+ This must be a daytime job
    Join Date
    Nov 2005
    Location
    rotterdam, the Netherlands, Europe
    Posts
    898
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    i think its possible to undock the level-d fmc and drag it to another screen.

    With nico's program you can interface all keys of the fmc.

    If you want to build a Level-d 767 based sim, nico's software and website are a must. He is a wizzard and what he did with iocards and his software + the level-d 767 is amazing.

    He offers a perfect solution for those who want to build their fmc themselves and not want to use a plug and play cdu.

    Stef
    www.boeing737ng.com
    ___________________________
    The Dutch 737 Simulator Project

  4. #4
    1000+ Poster - Fantastic Contributor kiek's Avatar
    Join Date
    Jan 2007
    Location
    Netherlands
    Posts
    1,621
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Hi Guys,

    Stef is right (thank you for your kind words )

    But not only the 69 keys can be connected, also the two leds for MSG and EXEC lights.
    Note that with my solution you are digitally connected to the Level-D, so no key-generation, no key2mouse, but a real computer-computer protocol.

    The advantages are: it also works when you are in spot view, so you can still program the FMC while enjoying your 767 from outside; no KB switching before entering alfa numeric keys (and back), it's modeless, it's fast, reliable, and cheap.

    I'd recommend to buy 1 Opencockpits USB Expansion card, 1 Master Card, two break out boxes for inputs and 1 break out box for outputs (for easy wiring).

    Details about the switches I've used are at my site. There you will also find a modification of panel.cfg in order to get rid of the keyboard gauge in the Level-D panel (while that one is no longer needed).

    The programming in SIOC is very simple, this is all you need (if you are using my free LEKSEECON program):

    ///////////////////////////////////////////////////////////////////////////
    //
    // Level-D FMC
    //
    // SIOC 3.4 code for LEKSEECON v1.0+
    //
    // Version 1.0
    // July 25, 2007
    //
    // Nico Kaan
    // The Netherlands
    // www.nicokaan.nl
    // email: flightsim@nicokaan.nl
    //
    //
    // CHANGE LOG:
    //
    // 1.0 First Release
    //
    //
    // CONTENTS:
    // A full implementation of the FMC with 69 keys and two leds (EXEC and MSG)

    Var 0000, Value 0
    {
    &ColdAndDark = 0
    &ColdOrBattery = 0
    &TestPed = 0
    }


    //===============================================================
    // Chapter 8 CDU (FMC)
    Var 771 name FI_FmcFlags
    {
    CALL &OutFmcFlags
    }
    Var 6100 name InitFmcFlags Link SUBRUTINE
    {
    &O_FmcExec = &InitFmcFlags
    &O_FmcMsg = &InitFmcFlags
    }
    Var 6120 name OutFmcFlags Link SUBRUTINE
    {
    IF &ColdAndDark = 1
    {
    CALL &InitFmcFlags 0
    }
    ELSE
    {
    IF &TestPed = 1
    {
    CALL &InitFmcFlags 1
    }
    ELSE
    {
    IF &ColdOrBattery = 1
    {
    CALL &InitFmcFlags 0
    }
    ELSE
    {
    &O_FmcExec = TESTBIT &FI_FmcFlags 1
    &O_FmcMsg = TESTBIT &FI_FmcFlags 0
    }
    }
    }
    }
    Var 6180 name O_FmcExec Link IOCARD_OUT Device 1 Output 75
    Var 6181 name O_FmcMsg Link IOCARD_OUT Device 1 Output 76

    // 12 LSK keys:
    Var 387 name LSK_L1 Link IOCARD_SW Device 1 Input 134 Type P
    Var 388 name LSK_L2 Link IOCARD_SW Device 1 Input 133 Type P
    Var 389 name LSK_L3 Link IOCARD_SW Device 1 Input 132 Type P
    Var 390 name LSK_L4 Link IOCARD_SW Device 1 Input 131 Type P
    Var 391 name LSK_L5 Link IOCARD_SW Device 1 Input 130 Type P
    Var 392 name LSK_L6 Link IOCARD_SW Device 1 Input 129 Type P
    Var 393 name LSK_R1 Link IOCARD_SW Device 1 Input 140 Type P
    Var 394 name LSK_R2 Link IOCARD_SW Device 1 Input 139 Type P
    Var 395 name LSK_R3 Link IOCARD_SW Device 1 Input 138 Type P
    Var 396 name LSK_R4 Link IOCARD_SW Device 1 Input 137 Type P
    Var 397 name LSK_R5 Link IOCARD_SW Device 1 Input 136 Type P
    Var 398 name LSK_R6 Link IOCARD_SW Device 1 Input 135 Type P

    // 15 Function keys:

    Var 399 name INIT_REF Link IOCARD_SW Device 1 Input 107 Type P
    Var 400 name RTE Link IOCARD_SW Device 1 Input 106 Type P
    Var 401 name DEP_ARR Link IOCARD_SW Device 1 Input 125 Type P
    Var 402 name ATC Link IOCARD_SW Input 196 Type P
    Var 403 name VNAV Link IOCARD_SW Device 1 Input 123 Type P
    Var 404 name FIX Link IOCARD_SW Device 1 Input 105 Type P
    Var 405 name LEGS Link IOCARD_SW Device 1 Input 104 Type P
    Var 406 name HOLD Link IOCARD_SW Device 1 Input 118 Type P
    Var 407 name F_COMM Link IOCARD_SW Input 194 Type P
    Var 408 name PROG Link IOCARD_SW Device 1 Input 121 Type P
    Var 409 name EXEC Link IOCARD_SW Device 1 Input 120 Type P
    Var 410 name MENU Link IOCARD_SW Device 1 Input 103 Type P
    Var 411 name NAV_RAD Link IOCARD_SW Device 1 Input 102 Type P
    Var 412 name PREV_PAGE Link IOCARD_SW Device 1 Input 101 Type P
    Var 413 name NEXT_PAGE Link IOCARD_SW Device 1 Input 100 Type P

    // 26 letter keys:

    Var 414 name FMC_A Link IOCARD_SW Device 1 Input 97 Type P
    Var 415 name FMC_B Link IOCARD_SW Device 1 Input 98 Type P
    Var 416 name FMC_C Link IOCARD_SW Device 1 Input 116 Type P
    Var 417 name FMC_D Link IOCARD_SW Device 1 Input 115 Type P
    Var 418 name FMC_E Link IOCARD_SW Device 1 Input 114 Type P
    Var 419 name FMC_F Link IOCARD_SW Device 1 Input 95 Type P
    Var 420 name FMC_G Link IOCARD_SW Device 1 Input 96 Type P
    Var 421 name FMC_H Link IOCARD_SW Device 1 Input 113 Type P
    Var 422 name FMC_I Link IOCARD_SW Device 1 Input 112 Type P
    Var 423 name FMC_J Link IOCARD_SW Device 1 Input 111 Type P
    Var 424 name FMC_K Link IOCARD_SW Device 1 Input 93 Type P
    Var 425 name FMC_L Link IOCARD_SW Device 1 Input 94 Type P
    Var 426 name FMC_M Link IOCARD_SW Device 1 Input 110 Type P
    Var 427 name FMC_N Link IOCARD_SW Device 1 Input 109 Type P
    Var 428 name FMC_O Link IOCARD_SW Device 1 Input 108 Type P
    Var 429 name FMC_P Link IOCARD_SW Device 1 Input 126 Type P
    Var 430 name FMC_Q Link IOCARD_SW Device 1 Input 92 Type P
    Var 431 name FMC_R Link IOCARD_SW Device 1 Input 81 Type P
    Var 432 name FMC_S Link IOCARD_SW Device 1 Input 82 Type P
    Var 433 name FMC_T Link IOCARD_SW Device 1 Input 83 Type P
    Var 434 name FMC_U Link IOCARD_SW Device 1 Input 127 Type P
    Var 435 name FMC_V Link IOCARD_SW Device 1 Input 91 Type P
    Var 436 name FMC_W Link IOCARD_SW Device 1 Input 84 Type P
    Var 437 name FMC_X Link IOCARD_SW Device 1 Input 85 Type P
    Var 438 name FMC_Y Link IOCARD_SW Device 1 Input 86 Type P
    Var 439 name FMC_Z Link IOCARD_SW Device 1 Input 128 Type P

    // 4 special keys:

    Var 440 name FMC_BL Link IOCARD_SW Device 1 Input 90 Type P
    Var 441 name FMC_DEL Link IOCARD_SW Device 1 Input 87 Type P
    Var 442 name FMC_SL Link IOCARD_SW Device 1 Input 88 Type P
    Var 443 name FMC_CLR Link IOCARD_SW Device 1 Input 89 Type P

    // 12 numeric Input keys:

    Var 444 name FMC_1 Link IOCARD_SW Device 1 Input 99 Type P
    Var 445 name FMC_2 Link IOCARD_SW Device 1 Input 119 Type P
    Var 446 name FMC_3 Link IOCARD_SW Device 1 Input 117 Type P
    Var 447 name FMC_4 Link IOCARD_SW Device 1 Input 72 Type P
    Var 448 name FMC_5 Link IOCARD_SW Device 1 Input 73 Type P
    Var 449 name FMC_6 Link IOCARD_SW Device 1 Input 74 Type P
    Var 450 name FMC_7 Link IOCARD_SW Device 1 Input 75 Type P
    Var 451 name FMC_8 Link IOCARD_SW Device 1 Input 76 Type P
    Var 452 name FMC_9 Link IOCARD_SW Device 1 Input 77 Type P
    Var 453 name FMC_DOT Link IOCARD_SW Device 1 Input 78 Type P
    Var 454 name FMC_0 Link IOCARD_SW Device 1 Input 79 Type P
    Var 455 name FMC_PLMIN Link IOCARD_SW Device 1 Input 80 Type P


    //*****************************************************************
    // Panel info

    Var 782, name FI_Panel
    {
    &ColdAndDark = TESTBIT &FI_Panel 0
    &ColdOrBattery = TESTBIT &FI_Panel 1
    }
    Var 950, name ColdAndDark
    {
    CALL &Refresh
    }
    Var 951, name ColdOrBattery
    {
    CALL &Refresh
    }
    Var 955, name Refresh, Link SUBRUTINE
    {
    CALL &OutFmcFlags
    }

    //**********************************************************
    Var 962, name TestPed, Link IOCARD_SW, Input 103, Type I
    {
    CALL &Refresh
    }

    Have Fun!
    Nico
    Last edited by kiek; 12-10-2007 at 05:14 PM. Reason: typo

  5. #5
    75+ Posting Member Polmer's Avatar
    Join Date
    Dec 2006
    Location
    USA
    Posts
    141
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    (this is more of a Hardware Question, rather than Software)

    Nico,

    Regarding your FMC & SIOC Setup;

    Marius offers a PCB than can be used with the Hispanels FMC Panel.

    http://www.stormloader.com/users/marius/

    The PCB is wired to be directly connected to the Opencockpits USB Keys.1 card
    via a 40 pin IDE cable.

    This sounds like a good setup, but can this USB Key card interface be connected and controlled by SIOC, and work with the level-D?

    Or, should the switches& led's be connected to the Opencockpits I/O card for the FMC to work Correctly.

    Polmer

  6. #6
    1000+ Poster - Fantastic Contributor kiek's Avatar
    Join Date
    Jan 2007
    Location
    Netherlands
    Posts
    1,621
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Quote Originally Posted by Polmer View Post
    This sounds like a good setup, but can this USB Key card interface be connected and controlled by SIOC, and work with the level-D?
    Polmer
    No, no, no no, that is the old fashioned way using generated key-strokes (a technique from the previous century... ).

    If you want to build an FMC for the Level-D 767-300 (via my LEKSEECON program) you have to use an Opencockpits mastercard and connect your 69 buttons to its inputs.

    Regards,
    Nico

  7. #7
    75+ Posting Member Polmer's Avatar
    Join Date
    Dec 2006
    Location
    USA
    Posts
    141
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Ahh, thats too bad.

    The worst part of dealing with the I/O cards is the wiring mess and the FMC PCC/USB set-up seemed to be a nice way of keeping things organized.

    Thanks for the clarification.

    Polmer

  8. #8
    25+ Posting Member
    Join Date
    Jun 2007
    Location
    australia
    Posts
    38
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Quote Originally Posted by kiek View Post
    No, no, no no, that is the old fashioned way using generated key-strokes (a technique from the previous century... ).

    If you want to build an FMC for the Level-D 767-300 (via my LEKSEECON program) you have to use an Opencockpits mastercard and connect your 69 buttons to its inputs.

    Regards,
    Nico
    Isn't it as simple as changing the variable declaration to key inputs in the SIOC code so that the variables point to the relevant key codes?

  9. #9
    1000+ Poster - Fantastic Contributor kiek's Avatar
    Join Date
    Jan 2007
    Location
    Netherlands
    Posts
    1,621
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Quote Originally Posted by marius View Post
    Isn't it as simple as changing the variable declaration to key inputs in the SIOC code so that the variables point to the relevant key codes?
    Hi Marius,

    I have studied the USB Keys manual. I now see that there are two possible ways of working. You can either generate keys (from the SIOC source file, not by the card directly), or -interestingly!- you can set another SIOC variable, like can be done with the Project Magenta CDU linked to a a FSUIPC offset.

    The second approach could also be taken with Level-D and Lekseecon, then you have to set one of the Lekseecon variables representing the keys of the fmc keyboard upon receival of a 'key' (not really a key but an IOCP event via the USB keycard...) This approach does not fall under my 'previous century technology remark '

    Thank you for your valuable comment!

    However with the USB key card you miss the possibility to control the EXEC and MSG leds, you still need a Master card for that, so either use an MC or use both.

    Cheers,
    Nico

  10. #10
    25+ Posting Member
    Join Date
    Jun 2007
    Location
    australia
    Posts
    38
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Quote Originally Posted by kiek View Post
    Hi Marius,

    interestingly!- you can set another SIOC variable, like can be done with the Project Magenta CDU linked to a a FSUIPC offset.

    The second approach could also be taken with Level-D and Lekseecon, then you have to set one of the Lekseecon variables representing the keys of the fmc keyboard upon receival of a 'key' (not really a key but an IOCP event via the USB keycard...) This approach does not fall under my 'previous century technology remark '

    Thank you for your valuable comment!

    However with the USB key card you miss the possibility to control the EXEC and MSG leds, you still need a Master card for that, so either use aan MC or use both.

    Cheers,
    Nico
    Yes, that is what I was thinking but I was not 100% sure so I didn't want to go into too much detail.

    You are correct about the MSG and EXEC leds. That is the downside to only using the usbkeys card.

    Thanks for clarifying all this as your reply will be very usefull information for people visiting this thread in the future.

Similar Threads

  1. Should FBS create a lights interface for the PMDG Boeing 737NG for FS2004?
    By FBSInfo in forum Cockpit Software: Miscellaneous
    Replies: 11
    Last Post: 03-21-2011, 05:08 AM
  2. Boeing 777 Cockpit Parts for sale. MCP Overhead Interface, and More
    By vladsf in forum Off Site Articles For Sale
    Replies: 0
    Last Post: 10-04-2010, 08:00 PM
  3. PSS interface.
    By Jake 747 400 in forum General Builder Questions All Aircraft Types
    Replies: 8
    Last Post: 11-20-2009, 05:19 AM
  4. What Interface are you using or going to use?
    By Trevor Hale in forum MyCockpit Polls
    Replies: 33
    Last Post: 03-13-2007, 12:05 AM