Send an FSUPC Offset

Answers

• admin_pps

  September 2013 edited November -1

  Hi Kevin,

  Simple answer, no.

  Last time I looked though, the offsets were just fsuipc's link to simconnect variables. FSX\modules\FSUIPC Documents\FSUIPC4 Offsets Status.pdf should help guide you.

  Best wishes

  Steve 
• Kconlon

  September 2013 edited November -1

  To me, it appears that sending 69817 , <value> can change the efis mode.

  function PMDG_EFIS_Mode_show ()
      ipc.sleep(10)
       CEfisMode = ipc.readLvar('switch_185_a')
       if CEfisMode == 0 then CEfisModeTxt = "APP"
       elseif CEfisMode == 10 then CEfisModeTxt = "VOR"
       elseif CEfisMode == 20 then CEfisModeTxt = "MAP"
       elseif CEfisMode == 30 then CEfisModeTxt = "PLAN"
       end
       DspShow ("Mode", CEfisModeTxt)
  end

  function PMDG_EFIS_Mode_inc ()
      ipc.control(69817, 256)
      PMDG_EFIS_Mode_show ()
  end

  function PMDG_EFIS_Mode_dec ()
      ipc.control(69817, 128)
      PMDG_EFIS_Mode_show ()
  end

  function PMDG_EFIS_Mode_ctr ()
      ipc.control(69818, 1)
      DspShow ("Mode", "Ctr")
  end

  function PMDG_EFIS_Mode_inc ()
      ipc.control(69817, 256)
      PMDG_EFIS_Mode_show ()
  end

  function PMDG_EFIS_Mode_dec ()
      ipc.control(69817, 128)
      PMDG_EFIS_Mode_show ()
  end

  function PMDG_EFIS_Mode_ctr ()
      ipc.control(69818, 1)
      DspShow ("Mode", "Ctr")
  end

  Is there a way to assign this to a bespoke variable then assign that bespoke value to an action of the GFEFIS?

  
  Thanks

  Kevin

   
• admin_pps

  September 2013 edited November -1

  Hi Kevin,

  ipc.control values are simply simconnect events and the associated data. You can configure these directly onto controls or create Bespoke events.

  ipc.readLvar are reading lavr values that you can do in detective and create a Bespoke event.

  Best wishes

  Steve
• admin_pps

  September 2013 edited September 2013

  P.S.

  The ipc.control value can be found in Detective. Just browse or search the events list in Detective to find the full name. E.g. 66100 is AP_VS_ON. 69817 and 69818 are custom events and should show up in detected events when the EFIS is used. If they don't let me know.

  Best wishes

  Steve