Jump to content
The simFlight Network Forums

Tekworx Board on FSUIPC


scheffchoch

Recommended Posts

Hi guys

I have an A320 overhead panel with a USB Tekworx IO card (128 inputs, 256 outputs). I have installed the Tekworx InterfaceIT MCS software (https://www.tekworx.com/downloads.php) and the button operations and LED activation works from there. As I read on various forums and pages, these cards are also used in FDS (Flightdeck Solution) products. The card is visible in hidscanner.exe.

I plan on using the panel in MSFS with the Fenix A320. Therefore i planned to go over FSUIPC7, which i also licenced. When I try to assign a button in FSUIPC, it scans for button presses. However none of the buttons i press on the overhead panel are recognized in FSUIPC.

What steps do I have to take, to make the button presses over the Tekworx card recognized by FSUIPC?

Thank you for you help!

Cheers

Edited by scheffchoch
Link to comment
Share on other sites

53 minutes ago, scheffchoch said:

When I try to assign a button in FSUIPC, it scans for button presses. However none of the buttons i press on the overhead panel are recognized in FSUIPC.

What steps do I have to take, to make the button presses over the Tekworx card recognized by FSUIPC?

FSUIPC will only recognise buttons on HID joystick type devices. If this is a non-joystick type HID device, then you have to use the lua com library instead. There are various methods of doing this, but the easiest to start with would be to use the provided HidDemo.lua script, available in the Example Lua plugins.zip file which will be installed in your FSUIPC documents folder. This script converts HID button presses to virtual button presses, to which you can then assign in the Buttons & Switches assignment panel. You will need to edit the script to give the correct vendor and product ids for your device, and have the script auto-started from your FSUIPC ini file.

John

Link to comment
Share on other sites

Hi John

Thank you, it tried that with the following steps:

1. copied the HidDemo.lua into the main FSUIPC folder

2. looked at hidscanner, what the board properties are:

Device at "\\?\hid#vid_1fd1&pid_03ea&mi_00#8&25bbf48&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
  Vendor=1FD1, Product=03EA (Version 16.51)
  Manufacturer= TEKWorx Limited
  Product= Plain I/O
  Serial Number= 00000477
  Usage Page: 1
  Input Report Byte Length: 5
  Output Report Byte Length: 5
  Feature Report Byte Length: 0
  Number of Link Collection Nodes: 1
  Number of Input Button Caps: 1
  Number of InputValue Caps: 0
  Number of InputData Indices: 32
  Number of Output Button Caps: 1
  Number of Output Value Caps: 0
  Number of Output Data Indices: 1
  Number of Feature Button Caps: 0
  Number of Feature Value Caps: 0
  Number of Feature Data Indices: 0
  Buttons range 1 -> 32 at indices 0 -> 31

3. changed the vendor and product id in the hiddemo.lua and changed the logging to true

Vendor = 0x1FD1
Product = 0x03EA
Device = 0  -- Multiple devices of the same name need increasing Device numbers.

-- Logging on or off (to see when numbers you are getting)
Logging = true



4. FSUIPC added automatically inf FSUIPC.ini:
 

[LuaFiles]
1=HidDemo

5. enabled Lua logging in FSUIPC

 

As far as I understood the hiddemo.lua it should automatically identify the available buttons, right?

Nevertheless I cant see any sign of the board beeing recognized by FSUIPC... there is no log entry and no separate log for the hiddemo.lua. What am I doing wrong? Does the hiddemo.lua not autostart when there is said entry in FSUIPC.lua?

Thank you for you help!

Link to comment
Share on other sites

41 minutes ago, scheffchoch said:

4. FSUIPC added automatically inf FSUIPC.ini:
 

[LuaFiles]
1=HidDemo

5. enabled Lua logging in FSUIPC

 

As far as I understood the hiddemo.lua it should automatically identify the available buttons, right?

You also need to start the lua. You do this by adding it to the [Auto] section (which you can add if not already there), i.e.

Quote

[Auto]
1=Lua HidDemo

John   

Link to comment
Share on other sites

I added the [Auto] section and put the lua in there, still the Techworx board does not show up in the joystick scan and is not available for a button assignement.

 

Log:

********* FSUIPC7, Version 7.4.2 (2nd January 2024) by John Dowson *********
MS Store installation detected: Checking for FS path in 'C:\Users\XXXXXX\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt'
FS path found = G:\MSFS\
WebSocket server found: G:\MSFS\HomeCockpit\FSUIPC\\Utils\FSUIPCWebSocketServer.exe
Windows 10 Pro 64 Bit reported as Build 19045, Release ID: 2009 (OS 10.0)
Reading options from "G:\MSFS\HomeCockpit\FSUIPC\FSUIPC7.ini"
Checking the Registrations now ...
User Name="XXXXXX"
User Addr="XXXXXX"
FSUIPC7 Key is provided
WIDEFS7 not user registered, or expired
       47 System time = 11/01/2024 20:31:19
       47 FLT path = "C:\Users\XXXXXX\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\"
       47 Allowing calibration when not assigned with 'Send direct to FSUIPC Calibration'
       94 -------------------------------------------------------------------
      109 Preset file 'G:\MSFS\HomeCockpit\FSUIPC\myevents.txt' not found [info only]
      109 12465 Calculator Code presets have been loaded and are available for use
      156 Registered HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1)
      172 FS path = "G:\MSFS\"
      172 ---------------------- Joystick Device Scan -----------------------
      234 Product= T.A320 Pilot
      234    Manufacturer= Thrustmaster
      234    Serial Number= 1
      234    Vendor=044F, Product=0405 (Version 2.0)
      250    GUIDs returned for product: VID_044F&PID_0405:
      250       GUID= {2A3229B0-DF24-11EC-8002-444553540000}
      250       Details: Btns=17, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U0,V0,X16383,Y16383,Z255
      250 Product= CH Pro Pedals USB Rudder Pedals 
      250    Vendor=068E, Product=0501 (Version 1.8)
      250    GUIDs returned for product: VID_068E&PID_0501:
      250       GUID= {55612F00-0824-11EC-8001-444553540000}
      250       Details: Btns=1, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255
      250 -------------------------------------------------------------------
      266 Device acquired for use:
      266    Joystick ID = 2 (Registry okay)
      266    2=T.A320 Pilot
      266    2.GUID={2A3229B0-DF24-11EC-8002-444553540000}
      266 Device acquired for use:
      266    Joystick ID = 1 (Registry okay)
      266    1=CH Pro Pedals USB Rudder Pedals
      266    1.GUID={55612F00-0824-11EC-8001-444553540000}
      266 -------------------------------------------------------------------
      219 LogOptions=40000000 00000001
     8422 === Hot key unregistered
     8422 === Stop called ...
     8422 === Closing external processes we started ...
     8922 === About to kill any Lua plug-ins still running ...
     9844 === About to kill my timers ...
    10047 === Restoring window procs ...
    10047 === Unloading libraries ...
    10047 === stopping other threads ...
    10047 === ... Button scanning ...
    10047 === ... Axis scanning ...
    10047 === Releasing joystick devices ...
    10047 === Freeing macro memory
    10047 === Removing any offset overrides
    10047 === Clearing any displays left
    10047 === AI slots deleted!
    10047 === Freeing button memory ...
    10047 === Closing my Windows ...
    10047 === Freeing FS libraries ...
    11047 === Closing devices ...
    11047 === Closing the Log ... Bye Bye! ...
    11047 System time = 11/01/2024 20:44:30
    11047 *** FSUIPC log file being closed
Minimum frame rate was 32768.0 fps, Maximum was 0.0 fps
Maximum AI traffic for session was 0 aircraft
Traffic deletions 0 aircraft
Memory managed: 6 Allocs, 5 Freed
********* FSUIPC Log file closed ***********

And I attached the JoyScan csv.

Somehow I am not seeing any sign of the hiddemo lua running and no sign of the Tekworx board being recognized.

What else might I be missing?

FSUIPC7.JoyScan.csv

Edited by scheffchoch
Link to comment
Share on other sites

Lua scripts are not started until you have an aircraft loaded and ready to fly. The log you pasted shows that FSUIPC was not even connected to MSFS, and ends after 11 seconds.

13 hours ago, scheffchoch said:

still the Techworx board does not show up in the joystick scan and is not available for a button assignement.

It will NOT show up there - that is a scan of HID joystick type devices ONLY.  When the script is running, it will map the buttons of your device to virtual buttons, which you should see when activated in the button assignments panel.

Link to comment
Share on other sites

Thank you I did not know that. So here is what I tried:

  1. Started MSFS over the FSUIPC Shortcut on the desktop
  2. Chose an Airplane and Location and launched a Flight
  3. Pressed ready to fly
  4. Opened the FSUIPC7 GUI and tried to make a button assignement with my overhead panel

The panel was running and I could see the switch movement in the in the InterfaceIT software from Tekworx but it was not recognized "Button&Switches Assignement" window when it said "PRESS BUTTON".

After that i closed the Sim back down.

I attached the log but hat to cut some repetitive parts out since it exceeded the maximum allowed file size of 18.59 kb.

Do you have any hints on what I am missing?

Thank you!

 

Edit: With Lua logging disabled I can see a data read, whenever i press a button on the overhead. But it is not recognized in the button assignement window.

308516 Lvars received: 2296 L:vars & 220 H:vars now available
   308516 Lvars/Hvars received - checking aircraft autos....
   308578 Requesting Input Events...
   308609 Aircraft="FenixA320_SWRHBIJS_4K"
   308953 -------------------- Starting everything now ----------------------
   310641 Lvars received: 2297 L:vars & 220 H:vars now available
   330000 LUA.1: Data Read= 1B 00 88 00 03 00 00 00
   330047 LUA.1: Data Read= 19 94 85 01 20 00 00 00
   330844 LUA.1: Data Read= 1A 83 80 00 00 00 00 00
   330891 LUA.1: Data Read= 19 94 85 01 20 00 00 00
   331500 LUA.1: Data Read= 1C 01 10 98 80 00 00 00
   331547 LUA.1: Data Read= 1A 83 80 00 00 00 00 00
   331594 LUA.1: Data Read= 19 94 85 01 20 00 00 00
   332250 LUA.1: Data Read= 1B 00 88 00 03 00 00 00
   332297 LUA.1: Data Read= 19 94 85 01 20 00 00 00
   363172 MSFS no longer running - exiting
   363187 === Hot key unregistered
   363187 === Stop called ...
   363187 === Closing external processes we started ...
   363703 === About to kill any Lua plug-ins still running ...
   363859 Lua threads being terminated:
   363859       1 = "G:\MSFS\HomeCockpit\FSUIPC\HidDemo.lua"
   364047 LUA: "G:\MSFS\HomeCockpit\FSUIPC\HidDemo.lua": killed

FSUIPC7.log.rar

Edited by scheffchoch
Link to comment
Share on other sites

20 minutes ago, scheffchoch said:

The panel was running and I could see the switch movement in the in the InterfaceIT software from Tekworx but it was not recognized "Button&Switches Assignement" window when it said "PRESS BUTTON".

This software may be interfering. Better to not run this, or use any specific drivers. First try without that software running, and also try uninstalling any specific drivers you have installed and and let windows install default drivers.

23 minutes ago, scheffchoch said:

I attached the log but hat to cut some repetitive parts out since it exceeded the maximum allowed file size of 18.59 kb.

You have activated logging for lua plugins - this is not needed (at the moment) and is adding a lot of noise to the logs so please disable. You have set logging in the lua script itself which is good and sufficient for the time being. This should be enough to determine what the lua script is seeing/doing, if anything, when you press a button on your panel. From what I see, it is not recognising any button presses at the moment, but this may be due to the additional software running.

Note that the script also handles axes/potentiometers. If you have no axes on your panel, best to remove these parts to simplify the script.

At least you now have the lua script running and it is detecting your device...

53 minutes ago, scheffchoch said:

Edit: With Lua logging disabled I can see a data read, whenever i press a button on the overhead. But it is not recognized in the button assignement window.

It is very strange that you only see this when you disable lua logging...not sure what that data logged is, but it doesn't seem to be related to button presses that the script recognises. This may be due to the software/drivers you are using.

John

 

 

Link to comment
Share on other sites

1 hour ago, John Dowson said:

This software may be interfering. Better to not run this, or use any specific drivers. First try without that software running, and also try uninstalling any specific drivers you have installed and and let windows install default drivers.

I had no specific drivers installed besides the software. With the InterfaceIT software not running, there are no presses even recognized bei FSUIPC. The software itself has the availability to configure FSUIPC offsets which apparently seem to work. But I would rather work with the MSFS events over FSUIPC than with the offsets. Screenshot of the software (not from me, but shows the options, source: https://www.tekworx.com/products.php?section=interface-mcs).

2interfaceIT_MCS_InputSelect.JPG

 

 

 

 

 

 

 

 

1 hour ago, John Dowson said:

At least you now have the lua script running and it is detecting your device...

It seems to only detect anything when the InterfaceIT software is running for now.

1 hour ago, John Dowson said:

It is very strange that you only see this when you disable lua logging...not sure what that data logged is, but it doesn't seem to be related to button presses that the script recognises. This may be due to the software/drivers you are using.

The data read seems to come from the test configuration of the software and maybe not from the Lua script detecting virtual buttons. But then again I would not now how a proper button press recognition should look like.

One way or another I am not able to make a button asignement because no button press is recognized....

Link to comment
Share on other sites

13 hours ago, scheffchoch said:

I had no specific drivers installed besides the software. With the InterfaceIT software not running, there are no presses even recognized bei FSUIPC. The software itself has the availability to configure FSUIPC offsets which apparently seem to work.

Ok, then it sounds like you need  to use this software. If designed to use FSUIPC offsets, then it may be easier to go down this route... Otherwise, maybe ask the panel/software providers if it is possible to detect button presses directly using the lua com library. If the HidDemo script isn't seeing these button presses, it is not behaving as a standard Hid joystick type device.

One thing you could try is to change the Report number - try changing this to 1 on line 26 of the HidDemo.lua script.

Other than that, I don't think I can helpfurther with this and you should try the support for your panel.

14 hours ago, scheffchoch said:

The data read seems to come from the test configuration of the software and maybe not from the Lua script detecting virtual buttons.

The lua script is receiving this data and logging it in the code in lines 93-102. I do not know what this data is, but it doesn't seem to be related to button presses  or axes movements.

14 hours ago, scheffchoch said:

But then again I would not now how a proper button press recognition should look like.

Button presses/state changes would be logged at line 185, starting "Buttons=...."

Sorry I can't be of more help with this.

John

Link to comment
Share on other sites

22 hours ago, John Dowson said:

Ok, then it sounds like you need  to use this software. If designed to use FSUIPC offsets, then it may be easier to go down this route... Otherwise, maybe ask the panel/software providers if it is possible to detect button presses directly using the lua com library. If the HidDemo script isn't seeing these button presses, it is not behaving as a standard Hid joystick type device.

I contacted the board provider if he has an idea.

The approach over the offsets would theoretically work I guess. Other option would be to rewire the whole overhead to an Arduiono or Leobodnar hardware...

To go the FSUIPC offset approach: How do I get all the offsets for the Fenix A320? For example I noticed an offset for the landing lights but not individual offsets for landing lights left and right and no offsets for on/off/retract as they are used in the airbus. Will it be possible to get all the offsets for a complete working OVHD panel?

Link to comment
Share on other sites

2 hours ago, scheffchoch said:

To go the FSUIPC offset approach: How do I get all the offsets for the Fenix A320? For example I noticed an offset for the landing lights but not individual offsets for landing lights left and right and no offsets for on/off/retract as they are used in the airbus. Will it be possible to get all the offsets for a complete working OVHD panel?

I don't have the Fenix so do not know which offsets will work for this aircraft. However, to control things such as the landing lights, the HubHob site shows the preset for these use the lvars S_OH_EXT_LT_LANDING_L and S_OH_EXT_LT_LANDING_R, using values 
    0 = Retract
    1 = Off
    2 = On~
So you should add these lvars to spare FSUIPC offsets and then you can write to those offsets to control the lvar values and thus the landing lights.
You can also send presets to the FS by writing the preset name to offset 0x7C50. You can also directly update lvars using that offset without the need of adding them to a spare offsets if you don't need the ability to also read the value of an lvar.

 

Link to comment
Share on other sites

10 hours ago, John Dowson said:

So you should add these lvars to spare FSUIPC offsets and then you can write to those offsets to control the lvar values and thus the landing lights.

Thank you John, that seems to me like a feasonable approach. I have read in another post, that 66C0 - 66FF and 4200-42FF (if ESOUND is not used) would be available as spare.

Can you point me in to the direction, where I can find, how I assign lvars to these offsets? I only found something for axis but with the same concept on page 34 in the User Guide.

Other option would be to stay with offsets whenever possible. Is there a similar document like for the PMDG 737 in the Documents folder but for the Fenix A320?

Link to comment
Share on other sites

11 hours ago, scheffchoch said:

I have read in another post, that 66C0 - 66FF and 4200-42FF (if ESOUND is not used) would be available as spare.

Please see the Offset status guide for offsets free for general use:

Quote
0x2544 184 Free for general use
0x2644 184 Free for general use
0x2744 216 Free for general use
0x2ABC 68 Free for general use
0x6174 28 Free for general use
0x66C0 64 Free for general use, for example in button or keys programming
0xA000 512 Free for general use, for example in button or keys programming

 

11 hours ago, scheffchoch said:

Can you point me in to the direction, where I can find, how I assign lvars to these offsets?

See section Adding Lvars to Offsets on page 46 of the Advanced User guide.

11 hours ago, scheffchoch said:

Is there a similar document like for the PMDG 737 in the Documents folder but for the Fenix A320?

No - that document is for specific additional offsets provided for PMDG aircraft only, populated via the PMDG SDK. There is no such data for the Fenix A320.

John

Link to comment
Share on other sites

  • 4 weeks later...

Hi again!

 

I mounted the overhead panel in the meantime and tried various different approaches, unfortunatley none of them worked until now.

The board software does somehow not support sending strings to FSUIPC, so sending the preset names to 0x7C50 does not work...

Then i tried the approach to use the custom offsets. In FSUIPC7.ini I added the following three test offsets at the end:

[LvarOffsets]
1=L:S_OH_ELEC_EXT_PWR=UB0xA000
2=L:S_OH_ELEC_BAT1=UB0xA008
3=L:S_OH_EXT_LT_WING=UB0xA010

I always save and reload the config over Addons->WASM -> Reload

These LVARs can be observed in the MSFS behaviour debug changing, then the corresponding switch in the virtual cockpit is manipulated. (EXT_PWR has a weird pattern that with every time it is switched on, it adds +2 to the LVAR.)

Now I see in the board software the value triggered by the hardware switch is getting sent to the offsets. I also see them change when I monitor said offsets in FSUIPC. But none of the three functions work in MSFS. Not the virtual cockpit switch nor the LVAR value in the behaviour debug list...

I tried to follow the part with custom offsets as good as possible (Advanced User Guide, page 46ff), but up until now I did not get it working.

What am I missing?

Thank you for your help!

Link to comment
Share on other sites

18 hours ago, scheffchoch said:

The board software does somehow not support sending strings to FSUIPC, so sending the preset names to 0x7C50 does not work...

That is a bit of a pain, but you can also use the control numbers to execute presets via offset 0x3110, but it can be troublesome as the control number is based upon the position in the file. To prevent this changing, you need to use the myevents.txt file and not install the events.txt file. There are some details on this approach in the manuals.

18 hours ago, scheffchoch said:

I always save and reload the config over Addons->WASM -> Reload

No point in doing that as this will not reload the lvar offsets. I think these may be read when the WASM/WAPI connection is established, but it maybe before. Best to restart FSUIPC7 to pick up changes to this section.

18 hours ago, scheffchoch said:

These LVARs can be observed in the MSFS behaviour debug changing, then the corresponding switch in the virtual cockpit is manipulated. (EXT_PWR has a weird pattern that with every time it is switched on, it adds +2 to the LVAR.)

Yes - the preset just increments by one each time it is called, so even numbers are off, odd numbers on. Strange! I would still try using 0/1 (i.e. toggle) rather than incrementing on each press, at least to see if that is valid.

18 hours ago, scheffchoch said:

Now I see in the board software the value triggered by the hardware switch is getting sent to the offsets. I also see them change when I monitor said offsets in FSUIPC. But none of the three functions work in MSFS. Not the virtual cockpit switch nor the LVAR value in the behaviour debug list...

I tried to follow the part with custom offsets as good as possible (Advanced User Guide, page 46ff), but up until now I did not get it working.

What am I missing?

I am not sure. How/where are you assigning? Please attach your FSUIPC7.ini and FSUIPC7.log files, the latter with logging for Events and Buttons & Keys activated, as well as offset monitoring on the offsets you are using, Also try listing the lvars after you have updated them, to confirm they are actually being updated. 

Also, there are some connection issues in the latest few releases. Hopefully these are now resolved in the latest beta, so please update to this version, available here: 

 

 

John

Link to comment
Share on other sites

On 2/9/2024 at 4:26 PM, John Dowson said:

That is a bit of a pain, but you can also use the control numbers to execute presets via offset 0x3110, but it can be troublesome as the control number is based upon the position in the file. To prevent this changing, you need to use the myevents.txt file and not install the events.txt file. There are some details on this approach in the manuals.

Thank you John, this works relatively convenient with a myevents.txt! And i can use the free offsets for the lights.

Only issue i have is, when I switch a (lock in) korry on, everything works. But when I switch it back off, nothing arrives in the simulator even tough I see the correct control number being sent to 0x3110. Then I have to switch it back on and off again, then the corresponding off control gets executed correctly (in the offset monitor I then see once again the correct commands for on and off). I have seperate controls and according presets for switch on and off.

In order to see whats getting sent to MSFS I tried to get the log options to display the LVAR commands and changes, but did not succeed. Which options could help me to Identify?

And with the event option on, my log is getting spammed with the same 3 events continiously. Might that be contributing to my korry events not getting executed?

With the correct log options I can then submit a log file.

Link to comment
Share on other sites

17 minutes ago, scheffchoch said:

In order to see whats getting sent to MSFS I tried to get the log options to display the LVAR commands and changes, but did not succeed. Which options could help me to Identify?

Set logging for Buttons & Keys and Events. You cannot log lvar values directly, but you have two options:
1. Add the lvars to offsets, and use the offset monitoring facilities to log the lvar value changes
2. Manually list the lvars (and values) using the Add-ons->WASM->List Lvars option before and after you press the assigned button. This will log all lvars and their values both to the FSUIPC7.log file and the FSUIPC7 main window.

20 minutes ago, scheffchoch said:

And with the event option on, my log is getting spammed with the same 3 events continiously. Might that be contributing to my korry events not getting executed?

Many MSFS aircraft, especially add-ons, continually emit certain events, and these events are different for each aircraft. These are not an issue and won't prevent any other events from getting executed, but they are just noise in the log file. You can prevent such events from being logged using the DontLogThese ini parameter, best used in your [Profile.xxx] section (as they are aircraft and so profile specific). 

Also, please turn off logging options not needed (e.g. IPC Read/Writes), as these will just fill the log with info not relevant to your issue.
Please also attach your FSUIPC7.ini file when attaching FSUIPC7.log file - I need to see them both to understand what is happening.

John

Link to comment
Share on other sites

Hi John.

I did some further testing but with the same results. For this example I used the ENG1 anti ice button:

FNX320_Icing_Engine_1_Button_Press#(L:S_OH_PNEUMATIC_ENG1_ANTI_ICE) ! (>L:S_OH_PNEUMATIC_ENG1_ANTI_ICE)
FNX320_Icing_Engine_1_Button_Release#(L:S_OH_PNEUMATIC_ENG1_ANTI_ICE) 0 == if{ 0 (>L:S_OH_PNEUMATIC_ENG1_ANTI_ICE_Anim) } (L:S_OH_PNEUMATIC_ENG1_ANTI_ICE) 1 == if{ 2 (>L:S_OH_PNEUMATIC_ENG1_ANTI_ICE_Anim) }

Offset A000 is listeing for the ON led on the korry which correspons to the korry in MSFS being on and off in normal ops. I also monitored offset 3110 and the commands correspond to the line in the myevents.txt file.

What is weird is, that the korry in MSFS goes off after I push it in for the second time and then stays off when I push it back out, as you can see in the log.

I attached the FSUIPC.ini and the log.

Cheers!

scheffchoch

FSUIPC7.log FSUIPC7.ini

Link to comment
Share on other sites

First, you are using an old and unsupported version of FSUIPC7 (7.4.2). Please update to the latest released version (7.4.5) or the latest beta, available here:

 

 

Why are you adding lvars I_OH_PNEUMATIC_ENG1_ANTI_ICE_L and I_OH_PNEUMATIC_WING_ANTI_ICE_L to offsets and monitoring those if the presets you are using are using the lvar L:S_OH_PNEUMATIC_ENG1_ANTI_ICE? Monitor the lvars that you are using to determine what is happening...

You are also monitoring offset 0x3110 as U8, so are getting rubbish. This offset is 8 bytes, or, to be more precise, is 2x 4-byte integers. Monitor 0x3110 as U32, and 0x3114 as either U32 or S32. But you don't need these offsets logged if you add logging for Events.

1 hour ago, scheffchoch said:

For this example I used the ENG1 anti ice button:

FNX320_Icing_Engine_1_Button_Press#(L:S_OH_PNEUMATIC_ENG1_ANTI_ICE) ! (>L:S_OH_PNEUMATIC_ENG1_ANTI_ICE)
FNX320_Icing_Engine_1_Button_Release#(L:S_OH_PNEUMATIC_ENG1_ANTI_ICE) 0 == if{ 0 (>L:S_OH_PNEUMATIC_ENG
1 hour ago, scheffchoch said:

What is weird is, that the korry in MSFS goes off after I push it in for the second time and then stays off when I push it back out, as you can see in the log.

Do you understand what those presets are doing? The first one is toggling the lvar S_OH_PNEUMATIC_ENG1_ANTI_ICE (between 0 and 1), and the second is controlling the switch animation based upon the value of that lvar, using the lvar L:S_OH_PNEUMATIC_ENG1_ANTI_ICE_Anim. So it looks like those presets are designed for a momentary button, that sends a press and release, and each time you press/release it toggles the function and switch. If you are using an actual switch, you will not want to use those. For a switch, try:

    FNX320_Icing_Engine_1_Button_On# 1 (>L:S_OH_PNEUMATIC_ENG1_ANTI_ICE) 2 (>L:S_OH_PNEUMATIC_ENG1_ANTI_ICE_Anim)
    FNX320_Icing_Engine_1_Button_Off# 0 (>L:S_OH_PNEUMATIC_ENG1_ANTI_ICE) 0 (>L:S_OH_PNEUMATIC_ENG1_ANTI_ICE_Anim)

Link to comment
Share on other sites

On 2/11/2024 at 6:37 PM, John Dowson said:

Do you understand what those presets are doing? The first one is toggling the lvar S_OH_PNEUMATIC_ENG1_ANTI_ICE (between 0 and 1), and the second is controlling the switch animation based upon the value of that lvar, using the lvar L:S_OH_PNEUMATIC_ENG1_ANTI_ICE_Anim. So it looks like those presets are designed for a momentary button, that sends a press and release, and each time you press/release it toggles the function and switch. If you are using an actual switch, you will not want to use those. For a switch, try:

    FNX320_Icing_Engine_1_Button_On# 1 (>L:S_OH_PNEUMATIC_ENG1_ANTI_ICE) 2 (>L:S_OH_PNEUMATIC_ENG1_ANTI_ICE_Anim)
    FNX320_Icing_Engine_1_Button_Off# 0 (>L:S_OH_PNEUMATIC_ENG1_ANTI_ICE) 0 (>L:S_OH_PNEUMATIC_ENG1_ANTI_ICE_Anim)

You were right as always. I did not yet look deeper in to the presets. So i went through the whole myevents.txt and adjusted all the ones that were lock-in but worked as momentary. First tests looked promising.

Further on to adress the LEDs I could not think of an other way than to write these in to the free offsets and configure the board software to listen and display the LED values according to the defined custom offsets. Only downside is, that it took 137 U8 offset slots of a total of 157 i managed to find according the offset status document. But then again, as long as it works 🙂

Thank you so much for you expertise, John! Helpful as always.

 

PS: I also updated the version but was confused at first because i renamed my events.txt and the update created a new one, nothing worked at first. After some hairs lost, I found the new events.txt file 😉 

Link to comment
Share on other sites

10 minutes ago, scheffchoch said:

PS: I also updated the version but was confused at first because i renamed my events.txt and the update created a new one, nothing worked at first. After some hairs lost, I found the new events.txt file

Not exactly sure on what you  are saying. but please understand the difference between the events.txt file and the myevents.txt file...every time you update, the events.txt file will be updated/installed to the version included in the installer.

Please read the Advanced User guide for details.

John  

Link to comment
Share on other sites

9 hours ago, John Dowson said:

Not exactly sure on what you  are saying. but please understand the difference between the events.txt file and the myevents.txt file...every time you update, the events.txt file will be updated/installed to the version included in the installer.

 

No worries. I configured all my presets in the myevents.txt and renamed the events.txt to events.txt.bak. But in the in stalling process, FSUIPC (of course) noticed that the events.txt is missing and added it again. And because the events.txt gets scanned first, the control numbers did not work any more. Just took me a few worried seconds to find the problem and now that I know it, I will remeber it next update 🙂 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.