Jump to content
Sign in to follow this  
MarkDH

Bad HID on aircraft load + OFF actions peculiarity

Recommended Posts

I recently installed 2.8.3 and everything works fine except for two problems.

 

(1) First, every time I load an aircraft I get the following error (this example pops up when FSX loads with the default trike):

 

34d55e074aa41d109fd77a2844e4fafb.jpg

 

The HID it refers to is a Leo Bodnar BU0836X board, which is plugged in and working correctly. I have reproduced a portion of the config-hid.lua file below and all the button bindings work correctly. This doesn't seem to stop anything working, it's just a pain when it pops up (particularly if I'm in full-screen mode).

 

(2) My second problem is that for switches in the ON position when LINDA loads an aircraft profile, the OFF actions initially do not work. However, as soon as I click the 'joysticks' button (which shows the button bindings screen), the OFF actions now work! I don't know what to make of this. Again, it's not a show-stopper but it's another step I have to remember to do.

 

Here's my config-hid.lua for the FSX default aircraft (it's not the whole file, just down to the 'faulty' HID):

-- ##  HID Device ## (041701300) ## {NoSerNum} ############

JSTK["041701300"][1]="TrimTest"
JSTKrl["041701300"][1]="Do_nothing"
JSTKrl["041701300"][14]="FP_Hide_Fuel_Report"
JSTK["041701300"][27]="RXP_WX500_TILT_DEC"
JSTK["041701300"][28]="RXP_WX500_TILT_INC"
JSTK["041701300"][29]="RXP_WX500_GAIN_DEC"
JSTK["041701300"][30]="RXP_WX500_GAIN_INC"

-- ## CH Eclipse ## (068E00510) ## {NoSerNum} ############

JSTK["068E00510"][3]="Flaps_decr"
JSTK["068E00510"][4]="Flaps_incr"
JSTK["068E00510"][10]="CWS_ON"
JSTKrl["068E00510"][10]="CWS_OFF"

-- ## Quad 1 ## (06A30C2D0) ## {NoSerNum} ############

JSTK["06A30C2D0"][1]="FuelEmerg_R_on"
JSTK["06A30C2D0"][2]="FuelEmerg_R_off"
JSTK["06A30C2D0"][3]="FireTest_sw_on"
JSTK["06A30C2D0"][4]="FireTest_sw_off"
JSTK["06A30C2D0"][5]="FuelEmerg_L_on"
JSTK["06A30C2D0"][6]="FuelEmerg_L_off"
JSTK["06A30C2D0"][7]="Feather_Right_Prop"
JSTKrl["06A30C2D0"][7]="Unfeather_Right_Prop"
JSTK["06A30C2D0"][8]="Feather_Left_Prop"
JSTKrl["06A30C2D0"][8]="Unfeather_Left_Prop"

-- ## Quad 2 ## (06A30C2D1) ## {NoSerNum} ############

JSTK["06A30C2D1"][2]="Auto_Feather_Arm_Toggle"
JSTK["06A30C2D1"][3]="TestLvar"
JSTK["06A30C2D1"][6]="bAutopilotActive"

-- ## Saitek Radio ## (06A30D050) ## {NoSerNum} ############


-- ## Iris Yoke ## (16C001080) ## {NoSerNum} ############


-- ## Bodnar (analog) ## (1DD210010) ## {NoSerNum} ############

JSTK["1DD210010"][1]="TW_AP_Pitch_thumbknob_dn"
JSTKrp["1DD210010"][1]="TW_AP_Pitch_thumbknob_dn"
JSTK["1DD210010"][2]="TW_AP_Bank_thumbknob_left"
JSTKrp["1DD210010"][2]="TW_AP_Bank_thumbknob_left"
JSTK["1DD210010"][3]="TW_AP_Yaw_toggle"
JSTKrl["1DD210010"][3]="TW_AP_Yaw_toggle"
JSTK["1DD210010"][4]="RXP_Nav_Device_Toggle"
JSTKrl["1DD210010"][4]="RXP_Nav_Device_Toggle"
JSTK["1DD210010"][5]="Parking_Brake_ON"
JSTKrl["1DD210010"][5]="Parking_Brake_OFF"
JSTK["1DD210010"][6]="TW_AP_Bank_thumbknob_right"
JSTKrp["1DD210010"][6]="TW_AP_Bank_thumbknob_right"
JSTK["1DD210010"][7]="Flight_Data_Recorder_ON"
JSTKrl["1DD210010"][7]="Flight_Data_Recorder_OFF"
JSTK["1DD210010"][8]="Aileron_Trim_Left"
JSTKrp["1DD210010"][8]="Aileron_Trim_Left"
JSTK["1DD210010"][9]="TW_DC_Source_sw_Ext"
JSTKrl["1DD210010"][9]="TW_DC_Source_sw_Off"
JSTK["1DD210010"][11]="Lights_LANDING_on"
JSTKrl["1DD210010"][11]="Lights_LANDING_off"
JSTK["1DD210010"][12]="Ign_Mode_Sw_manual"
JSTKrl["1DD210010"][12]="Ign_Mode_Sw_normal"
JSTK["1DD210010"][13]="Lights_LANDING_on"
JSTKrl["1DD210010"][13]="Lights_LANDING_off"
JSTKrl["1DD210010"][14]="Do_nothing"
JSTK["1DD210010"][15]="Starter_Sw_left"
JSTKrl["1DD210010"][15]="Starter_Sw_off"
JSTK["1DD210010"][16]="SYNC_Aircraft_To_Switch_Settings"
JSTK["1DD210010"][17]="Ign_Eng1_Sw_1"
JSTKrl["1DD210010"][17]="Ign_Eng1_Sw_both"
JSTK["1DD210010"][18]="Ign_Eng2_Sw_1"
JSTKrl["1DD210010"][18]="Ign_Eng2_Sw_both"
JSTK["1DD210010"][19]="Mod_ADF_Power_on"
JSTKrl["1DD210010"][19]="Mod_ADF_Power_off"
JSTK["1DD210010"][20]="GNS530_MENU"
JSTK["1DD210010"][21]="GNS530_Power_ON"
JSTKrl["1DD210010"][21]="GNS530_Power_OFF"
JSTK["1DD210010"][22]="ADF_SET_RST_Down"
JSTKrl["1DD210010"][22]="ADF_SET_RST_Up"
JSTK["1DD210010"][23]="DME_Mode_RMT"
JSTKrl["1DD210010"][23]="DME_Mode_FREQ"
JSTK["1DD210010"][24]="GNS530_Decrease_Range"
JSTK["1DD210010"][25]="GNS530_Increase_Range"
JSTK["1DD210010"][26]="SPK_COM1_ON"
JSTKrl["1DD210010"][26]="SPK_COM_OFF"
JSTK["1DD210010"][27]="ADF_FRQ"
JSTK["1DD210010"][28]="ADF_FLT_ET"
JSTK["1DD210010"][29]="GNS530_Direct_To"
JSTK["1DD210010"][30]="TW_AP_Pitch_thumbknob_up"
JSTKrp["1DD210010"][30]="TW_AP_Pitch_thumbknob_up"
JSTK["1DD210010"][31]="GNS530_Panel_Drives_RXP"
JSTKrl["1DD210010"][31]="GNS530_Panel_Drives_Default"
JSTK["1DD210010"][32]="Flight_Data_Recorder_Test_DOWN"
JSTKrl["1DD210010"][32]="Flight_Data_Recorder_Test_UP"

-- ## Bodnar 1 ## (1DD211400) ## {NoSerNum} ############

JSTK["1DD211400"][1]="GNS530_Radio_Outer_Knob_Right"
JSTK["1DD211400"][2]="GNS530_Radio_Outer_Knob_Left"
JSTK["1DD211400"][3]="GNS530_GPS_Outer_Knob_Left"
JSTK["1DD211400"][4]="GNS530_GPS_Outer_Knob_Right"
JSTK["1DD211400"][5]="GNS530_Radio_Inner_Knob_Left"

MarkH

gGzCVFp.jpg
Core i7-7700K / 32Gb DDR4 / Gigabyte GTX1070 / 1080p x 3 x weird / Win7 64 Pro

Share this post


Link to post
Share on other sites

 

 


I recently installed 2.8.3 and everything works fine except for two problems.
 
(1) First, every time I load an aircraft I get the following error (this example pops up when FSX loads with the default trike):
 
The HID it refers to is a Leo Bodnar BU0836X board, which is plugged in and working correctly. I have reproduced a portion of the config-hid.lua file below and all the button bindings work correctly. This doesn't seem to stop anything working, it's just a pain when it pops up (particularly if I'm in full-screen mode).
 
(2) My second problem is that for switches in the ON position when LINDA loads an aircraft profile, the OFF actions initially do not work. However, as soon as I click the 'joysticks' button (which shows the button bindings screen), the OFF actions now work! I don't know what to make of this. Again, it's not a show-stopper but it's another step I have to remember to do.

 

The aircraft config-hid.lua file should include the Leo Bodnar device serial number. You can fix this by edited the file and replace the corresponding NoSerNum with the reported serial number.

 

The initial position of switches is not reported to LINDA. You do need to operate at least one button on the device for the position to be recognised.


Andrew Gransden

Scotland, UK

LINDA Support/Developer - VATSIM and BAVirtual - Airbus Flyer

i7 1TB SSD GTX980 - FSX/P3D - Aerosoft Airbus A318/A319/A320/A321 - FS2Crew

Share this post


Link to post
Share on other sites

The aircraft config-hid.lua file should include the Leo Bodnar device serial number. You can fix this by edited the file and replace the corresponding NoSerNum with the reported serial number.

 

Sorry for the confusion but I posted the wrong config-hid.lua file (I don't know where I copied that from). The one below is the actual config-hid.lua for the 'FSX Default' aircraft. As you see, it has the serial numbers in but I still get the error. Maybe there is some difference between the BU0836X board and the BBI-32 boards?

-- ##  HID Device ## (041701300) ## {NoSerNum} ############


-- ## CH Eclipse ## (068E00510) ## {NoSerNum} ############

JSTK["068E00510"][22]="Trim_ELEVATOR_center"

-- ## Quad 1 ## (06A30C2D0) ## {NoSerNum} ############


-- ## Quad 2 ## (06A30C2D1) ## {NoSerNum} ############


-- ## Saitek Radio ## (06A30D050) ## {NoSerNum} ############


-- ## Iris Yoke ## (16C001080) ## {NoSerNum} ############


-- ## Bodnar (analog) ## (1DD210010) ## {B36466} ############

JSTK["1DD210010"][1]="AAL_AP_DN_Attitude_Hold_Decrease_Pitch"
JSTKrp["1DD210010"][1]="AAL_AP_DN_Attitude_Hold_Decrease_Pitch"
JSTK["1DD210010"][5]="Parking_Brake_ON"
JSTKrl["1DD210010"][5]="Parking_Brake_OFF"
JSTK["1DD210010"][9]="Control:_66702:1"
JSTKrl["1DD210010"][9]="Control:_66702:0"
JSTK["1DD210010"][11]="Lights_LANDING_on"
JSTKrl["1DD210010"][11]="Lights_LANDING_off"
JSTK["1DD210010"][13]="Lights_LANDING_on"
JSTKrl["1DD210010"][13]="Lights_LANDING_off"
JSTK["1DD210010"][15]="ENG1_start"
JSTK["1DD210010"][16]="SYNC_Aircraft_To_Switch_Settings"
JSTK["1DD210010"][20]="RXP_530_MNU"
JSTK["1DD210010"][21]="RXP_530_POW"
JSTK["1DD210010"][24]="RXP_530_RANGE_DEC"
JSTK["1DD210010"][25]="RXP_530_RANGE_INC"
JSTK["1DD210010"][29]="RXP_530_DTO"
JSTK["1DD210010"][30]="AAL_AP_UP_Attitude_Hold_Increase_Pitch"
JSTKrp["1DD210010"][30]="AAL_AP_UP_Attitude_Hold_Increase_Pitch"

-- ## Bodnar 1 ## (1DD211400) ## {B39327} ############

JSTK["1DD211400"][1]="RXP_530_LKNOBO_R"
JSTK["1DD211400"][2]="RXP_530_LKNOBO_L"
JSTK["1DD211400"][3]="RXP_530_RKNOBO_L"
JSTK["1DD211400"][4]="RXP_530_RKNOBO_R"
JSTK["1DD211400"][5]="RXP_530_LKNOBI_L"
JSTK["1DD211400"][6]="RXP_530_LKNOBI_R"
JSTK["1DD211400"][7]="RXP_530_RKNOBI_L"
JSTK["1DD211400"][8]="RXP_530_RKNOBI_R"
JSTK["1DD211400"][9]="RXP_530_FPL"
JSTK["1DD211400"][10]="RXP_530_MSG"
JSTK["1DD211400"][11]="RXP_530_NAVFLIP"
JSTK["1DD211400"][12]="RXP_530_LKNOBPUSH"
JSTK["1DD211400"][13]="RXP_530_ENT"
JSTK["1DD211400"][14]="RXP_530_OBS"
JSTK["1DD211400"][15]="RXP_530_RKNOBPUSH"
JSTK["1DD211400"][20]="RXP_530_CLR"
JSTKrp["1DD211400"][20]="RXP_530_CLR"
JSTK["1DD211400"][22]="RXP_530_PROC"
JSTK["1DD211400"][24]="RXP_530_NAV"
JSTK["1DD211400"][26]="RXP_530_CDI"
JSTK["1DD211400"][27]="RXP_530_COMFLIP"

-- ## Bodnar 2 ## (1DD211401) ## {B41851} ############


MarkH

gGzCVFp.jpg
Core i7-7700K / 32Gb DDR4 / Gigabyte GTX1070 / 1080p x 3 x weird / Win7 64 Pro

Share this post


Link to post
Share on other sites

I suggest you remove the brackets around the description (analog). As you will see the device is enclosed in round brackets and this is used to determine the right sections of the description.


Andrew Gransden

Scotland, UK

LINDA Support/Developer - VATSIM and BAVirtual - Airbus Flyer

i7 1TB SSD GTX980 - FSX/P3D - Aerosoft Airbus A318/A319/A320/A321 - FS2Crew

Share this post


Link to post
Share on other sites

I suggest you remove the brackets around the description (analog). As you will see the device is enclosed in round brackets and this is used to determine the right sections of the description.

 

Okay, I did that. I then ran 'setup joysticks' and saved. It still gave the error but now the error said 'BodId=analog, SerNo="NoSerNum". After quitting LINDA restarting FSX it now runs without the error. However, some of my devices are scrambled and all the entries in config-hid.lua show {NoSerNum}. I can probably repair the programming but why doesn't it pick up the serial numbers? LINDA seems to behave inconsistently here - sometimes config-hid.lua has all the serial numbers, sometimes it doesn't. All the serial numbers are shown correctly in the LINDA 'setup joysticks' page.

 

Regarding the '()' in my original 'Bodnar (analog)' device name, I notice that in the error message I posted at the start of this thread has the 'BodId' as 'analog', as if it has stripped the brackets.


MarkH

gGzCVFp.jpg
Core i7-7700K / 32Gb DDR4 / Gigabyte GTX1070 / 1080p x 3 x weird / Win7 64 Pro

Share this post


Link to post
Share on other sites

The reason that "analog" was displayed in the original error message was LINDA had assumed it was the device ID because proud are used brackets. It was looking and should have displayed 1DD210010.

 

You can either manually edit your current files or go back to the dated backup before you named the card "Bodnar (analog)" . You need to ensure that the system config-hid.lua.lua (in linda-cfg\system\) has the correct device ID and corresponding serial number. After edit save file. The next time you change the Joystick for Default aircraft it should correctly formatted.

 

I will add code next time to stop users pulling key characters into the device description.


Andrew Gransden

Scotland, UK

LINDA Support/Developer - VATSIM and BAVirtual - Airbus Flyer

i7 1TB SSD GTX980 - FSX/P3D - Aerosoft Airbus A318/A319/A320/A321 - FS2Crew

Share this post


Link to post
Share on other sites

go back to the dated backup before you named the card "Bodnar (analog)"

 

Okay, did that and now my mappings are correct. I still have all 'NoSerNum' in the config-hid.lua file, though.

 

The next time you change the Joystick for Default aircraft it should correctly formatted

I don't know what you meant by this bit.


MarkH

gGzCVFp.jpg
Core i7-7700K / 32Gb DDR4 / Gigabyte GTX1070 / 1080p x 3 x weird / Win7 64 Pro

Share this post


Link to post
Share on other sites

There are 2 config-hid.lua files (system and aircraft). Which one is showing NoSerNum?

 

I was trying to say. You need edit your current default aircraft Joystick assignments and save. This should correct any errors in the aircraft file. The correct serial numbers should be recorded.


Andrew Gransden

Scotland, UK

LINDA Support/Developer - VATSIM and BAVirtual - Airbus Flyer

i7 1TB SSD GTX980 - FSX/P3D - Aerosoft Airbus A318/A319/A320/A321 - FS2Crew

Share this post


Link to post
Share on other sites

There are 2 config-hid.lua files (system and aircraft). Which one is showing NoSerNum?

 

I was trying to say. You need edit your current default aircraft Joystick assignments and save. This should correct any errors in the aircraft file. The correct serial numbers should be recorded.

 

The aircraft file is showing NoSerNum for all devices, just like in the first extract I posted at the top of the thread. By 'edit your current joystick assignments' I am assuming you mean in the 'setup joysticks' page so I went into this page. The only way I can get it to save is to untick one of the boxes, then tick it again. The file saves but it does not record the serial numbers.


MarkH

gGzCVFp.jpg
Core i7-7700K / 32Gb DDR4 / Gigabyte GTX1070 / 1080p x 3 x weird / Win7 64 Pro

Share this post


Link to post
Share on other sites

I then suggest you manually added the correct serial numbers. I can't solve individual problems remotely. I have other work I need to get on with.


Andrew Gransden

Scotland, UK

LINDA Support/Developer - VATSIM and BAVirtual - Airbus Flyer

i7 1TB SSD GTX980 - FSX/P3D - Aerosoft Airbus A318/A319/A320/A321 - FS2Crew

Share this post


Link to post
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
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...