Page 1 of 4 1234 LastLast
Results 1 to 10 of 40
  1. #1
    500+ This must be a daytime job Boeing 747 Flyer's Avatar
    Join Date
    Nov 2009
    Location
    England
    Posts
    771
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Very weird transponder issue

    HI Nico,

    This issue is so strange I thought I'd post it here.

    I am using, for my main cockpit file, my Cockpit_Full.ssi file (in fact, it is untouched since you last modified it in the MCP thread), in addition to a few other group compiled files.

    Recently, I had to change the USB Port my Transponder was plugged in to, so I knew I had to change the SIOC.ini file to cater for this.

    My SIOC.ini file:

    Code:
    ; This sioc.ini was generated by ocm_configurator (version 2.0)
    ; ATC737 module detected
    ; FMC747 module detected
    ;
    [SIOC]
    IOCP_port=8092
    IOCP_timeout=4000
    Minimized=Yes
    toggle_delay=20
    CONFIG_FILE=Cockpit_Full.ssi
    [IOCARDS MODULE]
    IOCard_disable=No
    IOCard_LPT=No
    
    [USBKEYS]
    USBKeys=0,13
    
    [USBDCMOTORS]
    USBDCmotor=0,38
    
    [DCMOTORSAD]
    USBAnalogic=0,38
    
    [MASTERS]
    MASTER=3,11,1,70
    MASTER=2,5,1,50
    MASTER=0,4,1,12
    
    [USBKEYS]
    USBKeys=4,13
    
    [A/D USED MASTER]
    USB_AD=4
    
    [MULTIPLE]
    MUSB=Yes
    
    [USBSERVOS]
    USBSERVOS=0,4
    deviceUSB=2132
    
    [FSUIPC MODULE]
    FSUipcdisable=No
    FSUipcRefresh=50
    
    [IOCP CLIENTS MODULES]
    IOCPini_delay=3000
    IOCPclient0_disable=Yes
    IOCPclient0_host=localhost
    IOCPclient0_port=8090
    IOCPclient1_disable=Yes
    IOCPclient1_host=localhost
    IOCPclient1_port=8099
    
    [SOUND MODULE]
    Sound_disable=NO
    Volume=100
    My Transponder = Device 70

    USBExpansion = Device 12

    737 MCP = Device 50

    Correct?

    Secondly, the group compiler. This is my group compile file:

    Code:
    2
    Cockpit_Full.txt
    Jack_3.3_MCP.txt
    C:\lekseecon\cockpit767\6.1_ColdAndDark.txt
    C:\lekseecon\mcp767\3.3_MCP_IAS.txt
    C:\lekseecon\mcp767\3.3_MCP_HDG.txt
    C:\lekseecon\mcp767\3.3_MCP_VS.txt
    C:\lekseecon\mcp767\3.3_MCP_ALT.txt
    C:\lekseecon\mcp767\3.3_MCP_leds.txt
    C:\lekseecon\ocm\mcp\3.3_MCP737_generic.txt
    C:\lekseecon\ocm\mcp\6.2_TestLightsMIP_MCP737.txt
    C:\lekseecon\ocm\mcp\3.3_MCP737_VOR1Crs.txt
    C:\lekseecon\ocm\mcp\3.3_MCP737_VOR2Crs.txt
    This is, yet again, the same as the MCP thread. "Cockpit_Full" and "JackMCP" are the files you gave me; still unmodified.

    My Problem

    When I usually start Lekseecon, I load a flight in the B767 first. Usually instantaneously, the transponder digits alight with "1200".

    However, this time, I noticed I had to reload Lekseecon every time to get the digits to display.

    Secondly, the input rotaries do not seem to work. On either side of the transponder (you have grouped the transponder into two sides; two digits on each for each encoder), I cannot get higher than the number "18". To select a number, I have to turn backwards; turning forwards will stop at 18.

    Once I have dialled my code, I flick XPNDR switch from 1 -> 2. Nothing happens. I actually have to flick it BACK from 2 -> 1 for anything to happen. The switch is not broken, it tests okay in IOCPConsole. Not sure what's happeneing here.

    Also, once the code is finally accepted, it appears on the FS B767 display for about half a second. Then, it'll go to some random code like (5620, dialled) to (0002, random).

    Interestingly, when this happens, my XPNDR stills display the code I dialled, without the "d"; making it out of sync with FS.

    Also, occasionally, an "8" appears instead of a "d" at the front of the code.

    This is such a weird problem; I thought I'd ask you.

    If you want the files; they are indentical to the MCP thread, but I will repost here anyway. Sioc.ini and group compiler you have above.

    Cockpit_Full.ssi, the full file, consisting of the 11 group compiled files...

    http://www.mediafire.com/?ebvd6ewwkwf9zgt

    It is in .ssi format; I remembered you said never to export to txt.

    Since it is a big file, I will tell you that the Transponder bit starts at approximately line 1000, after the entry:

    Code:
    Var 0771, static
    {
      V0052 = TESTBIT V0771 ,1
      V0115 = TESTBIT V0771 ,0
    }
    Regards,

    Jack

  2. #2
    2000+ Poster - Never Leaves the Sim kiek's Avatar
    Join Date
    Jan 2007
    Location
    Netherlands
    Posts
    2,202
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Re: Very weird transponder issue

    Hi Jack,
    Cockpit_Full.ssi is for computers. I'd like to see your Cockpit_Fulll.txt, the one that is input to the group compiler.
    regards,
    Nico

  3. #3
    500+ This must be a daytime job Boeing 747 Flyer's Avatar
    Join Date
    Nov 2009
    Location
    England
    Posts
    771
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Re: Very weird transponder issue

    Hi Nico, it is the same one you gave me, but I shall post it anyway incase it got modified somehow:

    http://www.mediafire.com/?zwceykymk45kak1

    The "JackMCP" file is identical to the one you gave me.

    And, of course, the rest of the files are the untouched Lekseecon ones.

    Jack

  4. #4
    2000+ Poster - Never Leaves the Sim kiek's Avatar
    Join Date
    Jan 2007
    Location
    Netherlands
    Posts
    2,202
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Re: Very weird transponder issue

    Hi Jack,
    I have had a look at your Cockpit_Full.txt file and found that at three places in the XPDR code a piece of code was missing.
    For instance in Var RO_RIGHT
    Code:
      CALL &CalcXPDRFreqL
    must be
    Code:
      CALL &CalcXPDRFreqL L0
    The Cockpit_Full.txt file I had sent you around April 2nd already had this problem. So this transponder problem must be in your cockpit for quite some time.

    It looks like this problem is caused by the Save to .TXT facility of config_sioc.exe, or you must have removed these parts accidentally which I doubt while it occurred at 3 places. I'll test this later and if so I will send a bug report to Opencockpits.

    However, you would not have had this problem if you had not used Save to .TXT. So please, NEVER use this. Always keep control over YOUR .txt files and use the Group, Files feature of config.sioc to produce a.ssi file.

    Here is the updated Cockpit_Full.txt.

    regards,
    Nico
    Last edited by kiek; 04-21-2011 at 03:02 PM.

  5. #5
    500+ This must be a daytime job Boeing 747 Flyer's Avatar
    Join Date
    Nov 2009
    Location
    England
    Posts
    771
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Re: Very weird transponder issue

    Hi Nico,

    You are probably right. I haven't flown for months, constructing my HSI, sorting out TripleHead2Go, etc. Yesterday was the first flight.

    Thank you very, very much for your work. I shall download the file and see if it has fixed the issue.

    Jack

  6. #6
    500+ This must be a daytime job Boeing 747 Flyer's Avatar
    Join Date
    Nov 2009
    Location
    England
    Posts
    771
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Re: Very weird transponder issue

    Hi Nico,

    Good news. The Transponder now works perfectly! Thanks so much. I do, however, have a few other problems:

    - When dialling, I can only "confirm" a code by switching from 2 -> 1. For some reason, 1 -> 2 does not do anything.

    - My IRS LCD display is acting very, very strangely. The PPOS display seems to be random, and no matter what the position of my IRS display knob, it stays fixed on PPOS. This is the IRS section of the Cockpit_Full.txt file:

    Code:
    Var 0137, name LatHigh, Link FSUIPC_IN, Offset $0564, Length 4
    
    Var 0138, name LatLow, Link FSUIPC_IN, Offset $0560, Length 4
    {
      L1 = &LatHigh    
      L0 = &LatLow    
      IF L0 < 0     // convert to unsigned
      {
        L0 = L0 + 4294967296
      }
      L0 = L0 / 4294967296
      IF L1 > 0     // negative is South positive is North
      {
        L2 = L1 + L0
        &North = 1    
        &South = 0    
      }
      ELSE
      {
        L2 = L1 - L0
        &North = 0    
        &South = 1    
      }
      L2 = L2 * 90
      L2 = L2 / 10001750
      IF L2 < 0
      {
        L2 = L2 * -1
      }
      &Lat_Deg = TRUNC L2     // Convert to Degrees
      L2 = L2 - &Lat_Deg
      L2 = L2 * 10000
      L2 = L2 * 0.6     // 60/100 for mins.
      &Lat_Min = DIV L2 ,100     // Mins
      L0 = &Lat_Min * 100
      L2 = L2 - L0     // Secs
      L2 = L2 / 10
      &Lat_Sec = TRUNC L2
    }
    
    Var 0139, name North
    
    Var 0140, name South
    
    Var 0017, name Lat_Deg
    
    Var 0134, name Lat_Min
    
    Var 0135, name Lat_Sec
    {
      CALL &OutLatitude
    }
    
    Var 0136, name OutLatitude, Link SUBRUTINE
    {
      IF &Coldanddark = 1     // lekseecon state information variable
      {
        &O_North = 0    
        &O_South = 0    
        &O_DPLA1 = 0    
        &O_DPLA2 = 0    
        &D_Lat = -999999    
      }
      ELSE
      {
        &O_DPLA1 = 1    
        &O_DPLA2 = 1    
        IF &TestOvhd = 1     // lekseecon overhead lights test informati
        {
          &O_North = 1    
          &O_South = 1    
          &D_Lat = 888888    
        }
        ELSE
        {
          &O_North = &North    
          &O_South = &South    
          L0 = &Lat_Deg * 1000
          L1 = &Lat_Min * 10
          L2 = L0 + L1
          &D_Lat = L2 + &Lat_Sec
        }
      }
    }
    
    Var 0021, name LonHigh, Link FSUIPC_IN, Offset $056C, Length 4
    
    Var 0106, name LonLow, Link FSUIPC_IN, Offset $0568, Length 4
    {
      L1 = &LonHigh    
      L0 = &LonLow    
      IF L0 < 0     // convert to unsigned
      {
        L0 = L0 + 4294967296
      }
      L0 = L0 / 4294967296
      IF L1 > 0     // negative is West positive is East
      {
        L2 = L1 + L0
        &East = 1    
        &West = 0    
      }
      ELSE
      {
        L2 = L1 - L0
        &East = 0    
        &West = 1    
      }
      IF L2 < 0
      {
        L2 = L2 * -1
      }
      L2 = L2 * 360
      L2 = L2 / 4294967296
      &Lon_Deg = TRUNC L2     // Convert to Degrees
      L2 = L2 - &Lon_Deg
      L2 = L2 * 10000
      L2 = L2 * 0.6     // 60/100 for mins.
      &Lon_Min = DIV L2 ,100     // Mins
      L0 = &Lon_Min * 100
      L2 = L2 - L0     // Secs
      L2 = L2 / 10
      &Lon_Sec = TRUNC L2
    }
    
    Var 0107, name East
    
    Var 0108, name West
    
    Var 0109, name Lon_Deg
    
    Var 0026, name Lon_Min
    
    Var 0114, name Lon_Sec
    {
      CALL &OutLongitude
    }
    
    Var 0115, name OutLongitude, Link SUBRUTINE
    {
      IF &Coldanddark = 1
      {
        &O_East = 0    
        &O_West = 0    
        &O_DPLO1 = 0    
        &O_DPLO2 = 0    
        &D_Lon = -999999    
      }
      ELSE
      {
        &O_DPLO1 = 1    
        &O_DPLO2 = 1    
        IF &TestOvhd = 1
        {
          &O_East = 1    
          &O_West = 1    
          &D_Lon = 888888    
        }
        ELSE
        {
          &O_East = &East    
          &O_West = &West    
          L0 = &Lon_Deg * 1000
          L1 = &Lon_Min * 10
          L2 = L0 + L1
          &D_Lon = L2 + &Lon_Sec
        }
      }
    }
    
    Var 0116, name D_Lat
    
    Var 0117, name D_Lon
    
    Var 0031, name TKGS, Link FSUIPC_IN, Offset $02B8, Length 4
    {
      L0 = DIV &TKGS ,128
      &TKGSCALC = L0    
    }
    
    Var 0110, name TKGSCALC
    
    Var 0111, name WINDSP, Link FSUIPC_IN, Offset $0E90, Length 2
    
    Var 0112, name WINDDIR, Link FSUIPC_IN, Offset $0E92, Length 2
    {
      L0 = &WINDDIR * 0.0059493164063
      &WINDDIRCALC = ROUND L0
    }
    
    Var 0113, name WINDDIRCALC
    
    Var 0036, name HDG1, Link FSUIPC_IN, Offset $0580, Length 4     // true heading
    {
      L0 = &HDG1 * 8.3819E-008
      IF L0 < 0
      {
        L0 = L0 + 360
      }
      &D_HDG9 = ROUND L0
    }
    
    Var 0132, name D_HDG9
    {
      L0 = &D_HDG9    
      &D_HDG92 = L0    
    }
    
    Var 0133, name D_HDG92
    
    Var 0039, name HDGCALC
    
    Var 0040, name LCD, Link SUBRUTINE
    {
      IF &TKGSSW = 1
      {
        &LCD = 1    
      }
      ELSE
      {
        IF &WINDSW = 1
        {
          &LCD = 2    
        }
        ELSE
        {
          IF &PPOS = 1
          {
            &LCD = 0    
          }
          ELSE
          {
            &LCD = 3    
          }
        }
      }
    }
    
    Var 0130, name TKGSSW, Link IOCARD_SW, Input 67, Type I
    {
      CALL &LCD
    }
    
    Var 0131, name WINDSW, Link IOCARD_SW, Input 66, Type I
    {
      CALL &LCD
    }
    
    Var 0043, name PPOS, Link IOCARD_SW, Input 65, Type I
    {
      CALL &LCD
    }
    
    Var 0044, name O_North
    
    Var 0126, name O_South
    
    Var 0127, name O_East
    
    Var 0128, name O_West
    
    Var 0129, name O_DPLA1
    
    Var 0049, name O_DPLA2
    
    Var 0050, name O_DPLO1
    
    Var 0051, name O_DPLO2
    
    Var 0996, static     // lekseecon refresh variable
    {
      CALL &OutLatitude
      CALL &OutLongitude
    }
    All in all, it is just not working. Can you see any glaring errors that have arised from the exportation to .txt? (Please note, the script above is taken directly from the file you gave me; I have not run it through SIOC then re-exported to .txt).

    Also, when the cockpit is cold and dark, the digits do not display -9999999 like they should.

    Kind regards,

    Jack

  7. #7
    2000+ Poster - Never Leaves the Sim kiek's Avatar
    Join Date
    Jan 2007
    Location
    Netherlands
    Posts
    2,202
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Re: Very weird transponder issue

    Jack,
    wrt LCD:
    This script is the output of a SAVE to .txt operation while I see comma's in it. In my sources you will never see a comma (unless in comment parts) ...
    However, the script looks good to me, the only worry is about these:
    Code:
    Var 0116, name D_Lat
    Var 0117, name D_Lon
    Are you sure 116 and 117 are the variables used in your LCD definition file? Maybe you originally have taken different numbers. Variable numbers change if you work via Group, Run, unless you attach the keyword static.

    Note: if you do attach the keyword static, do not use the variable range 1 - 999 because these are in use by lekseecon.

    Nico

  8. #8
    500+ This must be a daytime job Boeing 747 Flyer's Avatar
    Join Date
    Nov 2009
    Location
    England
    Posts
    771
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Re: Very weird transponder issue

    Hi Nico,

    I think I have found the problem. Every single time I run the compiler in SIOC, ALL the variables (except for your Lekseecon ones) change numbers. All of them. This is probably why the LCD display isn't working.

    Regards,

    Jack

  9. #9
    2000+ Poster - Never Leaves the Sim kiek's Avatar
    Join Date
    Jan 2007
    Location
    Netherlands
    Posts
    2,202
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Re: Very weird transponder issue

    Hi Jack,

    Indeed, when you have a group of files defined in config_sioc.ini the compiler will solve number clashes (that's a feature!). It will start numbering from 1 beginning with the first file in config_sioc.ini. So each time you change the order in the group of file definitions, variable numbers may change (not "each single time I run the compiler"). This is not a problem as long as you do not depend on specific numbers. If you do, like lekseecon vars and your LCD vars you have to add the keyword Static. I recommend to define the LCD display variables starting from 9000 static and so on.

    About your 2-> 1 vs 1-> 2 transponder issue. It will only have effect if you dialled a new freq, indicated by 'd'. Whas that the case when you tried 2-> 1?
    The SIOC code looks fine.

    Nico

  10. #10
    500+ This must be a daytime job Boeing 747 Flyer's Avatar
    Join Date
    Nov 2009
    Location
    England
    Posts
    771
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Re: Very weird transponder issue

    Hi Nico,

    Firstly, fantastic news. I tried your Static idea and ALL of the LCD display worked! I was so worried I'd have to rescript the entire section of code.

    The Transponder issue is truly strange. Of course, I only ever flick the Transponder switch AFTER dialling my new squawk code.

    This is my exact procedure:

    1.) Receive code from ATC

    2.) Dial code into transponder. The "d" appears as always.

    3.) I confirm the code. I move the switch 1 -> 2

    RESULT: Nothing happens. The code stays "undialled" with the "d" infront of it

    New Procedure:

    1.) Receive code from ATC

    2.) Dial code into Transponder. "d" appears.

    3.) Confirm code. I move switch from 2 -> 1

    RESULT: Code is confirmed; "d" disappears and code registers on LDS add-on.

    Weird huh?

Page 1 of 4 1234 LastLast