Jump to content
The simFlight Network Forums

Corruption of joystick names

paulnd
 Share

Recommended Posts

paulnd Newbie

paulnd

Posted
Posted

Hello Pete,

I seem to experience a regular problem where some of my joystick names, particularly the BU0836X controllers become corrupted in the ini file

[JoyNames]
AutoAssignLetters=Yes
0=Saitek Pro Flight Throttle Quadrant
1=Saitek Pro Flight Rudder Pedals
2=Saitek Pro Flight Yoke
3=Saitek Pro Flight Throttle Quadrant
A=Saitek Pro Flight Throttle Quadrant
B=Saitek Pro Flight Rudder Pedals
C=Saitek Pro Flight Yoke
D=Saitek Pro Flight Throttle Quadrant
E=xé
F=0ju±icuèÆ
G=0ju±icuèÆ
H=0ju±icuèÆ
J=0{u±ituèÆ	
K=ùHw˜ë

There is also a duplication of the Saitek joysticks above as I only have 1 Yoke, 1 Rudder Pedals and 2 Throttle Quadrants connected (and 3 BU0836X controllers, all with the same name unfortunately)

Some of the axis and button assignments then become muddled and I need to reassign them.

Any ideas on why this occurs and how I can resolve it?

regards

Paul

PS I'm using v3.912 on Windows 7 x64 build 7229

Link to comment
Share on other sites
Pete Dowson Rising Star

Pete Dowson

Posted
Posted

I seem to experience a regular problem where some of my joystick names, particularly the BU0836X controllers become corrupted in the ini file

Odd. not seen that before. Does it happen without you actually going into the options and changing things?

Could you show me a good copy, please? Also, I do really need to know what version of FSUIPC you are talking about. If it isn't the very latest (4.52 or 3.912), please try that first -- there have been quite a few changes which might affect this sort of thing.

Also, can check the file Properties of the INI file (right clcik - Properties) and tell me the exact size of the file, please.

There is also a duplication of the Saitek joysticks above as I only have 1 Yoke, 1 Rudder Pedals and 2 Throttle Quadrants connected

No, I don't see that there. It most certainly correctly lists 1 Yoke, 1 Rudder Pedals and 2 Throttle Quadrants. don't forget that the numerical lines are the ID numbers Windows is using, and the letters are the assignments made. That's how the letters are translated into numbers. If you read about this facility you'll understand. Here, look at the "good" part, which is perfect:

[JoyNames]
AutoAssignLetters=Yes
0=Saitek Pro Flight Throttle Quadrant
1=Saitek Pro Flight Rudder Pedals
2=Saitek Pro Flight Yoke
3=Saitek Pro Flight Throttle Quadrant

A=Saitek Pro Flight Throttle Quadrant
B=Saitek Pro Flight Rudder Pedals
C=Saitek Pro Flight Yoke
D=Saitek Pro Flight Throttle Quadrant

(and 3 BU0836X controllers, all with the same name unfortunately)

There are none of those listed. If they are not recognised by windows as joystick devices they won't be processed by FSUIPC in any case.

It looks like the lines from E= onwards are spurious rubbish. In fact they shouldn't do any harm at all as there are no numerical lines to correspond with them.

Some of the axis and button assignments then become muddled and I need to reassign them.

How muddled? They can only be assigned to A, B, C or D and those lines are fine. The E, F etc letters cannot be assigned as they have no numeric IDs.

PS I'm using v3.912 on Windows 7 x64 build 7229

Ah, that was the information I needed up front. Tell me the size of the file please, and explain what is getting muddled, as I don't see anything which could muddle anything.

BTW what is build 7229? I am using Win7 x64 RC, which says it is build 7100. Do you have something later than the RC available to all, and if so how do I get one?

Regards

Pete

Link to comment
Share on other sites
paulnd Newbie

paulnd

Posted
  • Author
Posted

Hello Pete,

Here is the full ini file

[JoyNames]
AutoAssignLetters=Yes
0=Saitek Pro Flight Throttle Quadrant
1=Saitek Pro Flight Rudder Pedals
2=Saitek Pro Flight Yoke
3=Saitek Pro Flight Throttle Quadrant
A=Saitek Pro Flight Throttle Quadrant
B=Saitek Pro Flight Rudder Pedals
C=Saitek Pro Flight Yoke
D=Saitek Pro Flight Throttle Quadrant
E=$1
F=0ju±icuèÆ
G=0ju±icuèÆ
H=0ju±icuèÆ
J=0{u±ituèÆ	
K=0þv±i÷vèÆ
L=ò



[General]
UpdatedByVersion=3912
WindSmoothing=No
AutoTaxiWind=No
PropTaxiWind=No
TimeSetMode=Partial
WhiteMessages=No
ThrottleSyncAll=No
GraduatedVisibility=No
LowerVisAltitude=0
UpperVisAltitude=25000
UpperVisibility=6000
GenerateCirrus=No
WindShearSharp=No
UpperWindGusts=Yes
ExtendMetarMaxVis=No
CorrectVSsign=Yes
MouseWheelTrim=No
MouseWheelTrimSpeed=1
AxisInterceptIfDirect=No
DisconnTrimForAP=No
ZeroElevForAPAlt=No
AutoClearWeather=Yes
ExtendTopWind=No
WindSmoothness=5
SmoothPressure=No
PressureSmoothness=5
SmoothVisibility=No
VisibilitySmoothness=2
MaxSurfaceWind=0
WindLimitLevel=200
WindDiscardLevel=400
WindAjustAltitude=No
WindAjustAltitudeBy=2000
MinimumVisibility=0
MaximumVisibilityFewClouds=0
MaximumVisibility=0
MaximumVisibilityOvercast=0
MaximumVisibilityRainy=0
OneCloudLayer=No
ThinClouds=No
ThinThunderClouds=No
CloudThinness=1000
ThunderCloudThinness=10000
CloudTurbulence=No
CloudIcing=No
WindTurbulence=No
SuppressAllGusts=No
ExternalOptionControl=Yes
AutoTuneADF=No
KeepFS98CloudCover=No
ShowPMcontrols=No
MagicBattery=No
RudderSpikeRemoval=No
ElevatorSpikeRemoval=No
AileronSpikeRemoval=No
ReversedElevatorTrim=No
StopAutoFuel=No
TrapUserInterrupt=Yes
NavFreq50KHz=No
ClockSync=No
SmoothIAS=Yes
SetVisUpperAlt=No
VisUpperAltLimit=6000
MaxIce=-4
MinIce=-4
WindSmoothingDelay=0
WindSmoothAirborneOnly=No
LimitWindVariance=No
VisSmoothingDelay=0
VisSmoothAirborneOnly=No
TrafficControlDirect=Yes
SuppressCloudTurbulence=No
SuppressWindTurbulence=No
SpoilerIncrement=512
ZapSound=firework
ShortAircraftNameOk=No
UseProfiles=No
TCASid=Flight
TCASrange=40
TrafficScanPerFrame=10
AxisCalibration=No
CentredDialogue=Yes
ShowMultilineWindow=Yes
SuppressSingleline=Yes
SuppressMultilineFS=No
ClearWeatherDynamics=Yes
OwnWeatherChanges=No
FixWindows=No
FixControlAccel=No
WeatherReadInterval=4
MoveBGLvariables=Yes
TimeForSelect=4
WeatherReadsFast=No
MainMenu=&Modules
SubMenu=&FSUIPC ...

[JoystickCalibration]
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=Yes
ExcludeMixtureSet=Yes
ExcludePropPitchSet=Yes
SepRevsJetsOnly=No
ApplyHeloTrim=No
FlapsSetControl=0
FlapDetents=No
ReverserControl=66292
Reverser1Control=66422
Reverser2Control=66425
Reverser3Control=66428
Reverser4Control=66431
MaxThrottleForReverser=256
AileronTrimControl=0
RudderTrimControl=0
CowlFlaps1Control=0
CowlFlaps2Control=0
CowlFlaps3Control=0
CowlFlaps4Control=0
MaxSteerSpeed=60
Aileron=-16383,-512,512,16352/8
Elevator=-16384,-512,512,16383/8
Rudder=-16380,-512,512,16380/8
Throttle1=-16383,-512,512,16256/40
Throttle2=-16383,-512,512,16256/40
Throttle3=-16380,-512,512,16256/40
Throttle4=-16380,-512,512,16256/40
Spoilers=-16128,16383/24
Reverser=-16252,16383/12
SteeringTiller=-11660,-352,960,10336/24
LeftBrake=-16380,16380/32

[MacroFiles]
1=747_PMDG_CONS
2=747_PMDG_OVH
3=747_PMDG_THR

[Buttons]
ButtonRepeat=20,10
1=PJ,0,K49,15
2=PJ,13,K50,15
3=PJ,15,K51,15
4=PJ,17,K52,15
5=PJ,7,K53,15
6=PJ,9,K113,15
7=PJ,8,K112,15
8=UJ,8,K114,15
9=PJ,1,K54,15
10=PJ,12,K55,15
11=PJ,14,K56,15
12=PJ,16,K57,15
13=PJ,6,K0,15
14=RC,3,C65615,0
15=RC,2,C65607,0
16=PE,25,CM2:44,0
17=PE,29,CM2:39,0
18=PE,27,CM2:38,0
19=PE,20,CM2:41,0
20=PE,21,CM2:40,0
21=PE,19,CM2:42,0
22=PE,18,CM2:43,0
23=PE,14,CM2:37,0
24=PE,12,CM2:36,0
25=PE,5,CM2:3,0
26=PE,4,CM2:4,0
27=PE,3,CM2:2,0
28=PE,2,CM2:1,0
29=PE,7,CM2:18,0
30=PE,9,CM2:19,0
31=PE,8,CM2:20,0
32=PE,6,CM2:13,0
33=PE,0,CM1:2,0
34=PE,1,CM1:1,0
35=RE,0,Cx61006DB1,x00080001
36=UE,0,CM1:2,0
37=RE,1,Cx51006DB1,x00080001
38=UE,1,CM1:1,0

[Axes]
0=KX,256,D,36,0,0,0
1=KY,256,D,9,0,0,0
2=KZ,256,D,10,0,0,0
3=BX,256
4=BX,BR,-16384,14592,x05006DB0,x01,x09006DB0,x01
5=BY,256
6=BY,BR,-16384,15872,x05006DB0,x02,x09006DB0,x02
7=BR,256,D,3,0,0,0
8=CX,256,D,1,0,0,0
9=CY,256,D,2,0,0,0
10=DX,256,D,11,0,0,0
11=DY,256,D,12,0,0,0
12=DZ,256,D,25,0,0,0
13=EX,256,D,36,0,0,0
14=LX,256,D,36,0,0,0

I have assigned a number of buttons and an axis to the three BU0836 controllers. An example of the 'muddling' of assignments : I had assigned the spoiler axis to the first axis of a Saitek Throttle Quadrant and the steering tiller to a BU0836. When I restarted to FS9, the steering tiller had replaced the spoiler axis but also remained assigned to the BU0836 axis. This sometimes also occurs with buttons. The size of this file is 4,518 bytes.

I deleted the ini file and this is the clean one that was created :

[JoyNames]
AutoAssignLetters=No
0=Saitek Pro Flight Throttle Quadrant
1=Saitek Pro Flight Rudder Pedals
2=Saitek Pro Flight Yoke
3=Saitek Pro Flight Throttle Quadrant

[General]
UpdatedByVersion=3912
WindSmoothing=No
AutoTaxiWind=No
PropTaxiWind=No
TimeSetMode=Partial
WhiteMessages=No
ThrottleSyncAll=No
GraduatedVisibility=No
LowerVisAltitude=0
UpperVisAltitude=25000
UpperVisibility=6000
GenerateCirrus=Yes
WindShearSharp=No
UpperWindGusts=No
ExtendMetarMaxVis=Yes
CorrectVSsign=Yes
MouseWheelTrim=No
MouseWheelTrimSpeed=1
AxisInterceptIfDirect=No
DisconnTrimForAP=No
ZeroElevForAPAlt=No
AutoClearWeather=Yes
ExtendTopWind=Yes
WindSmoothness=5
SmoothPressure=No
PressureSmoothness=5
SmoothVisibility=No
VisibilitySmoothness=2
MaxSurfaceWind=0
WindLimitLevel=200
WindDiscardLevel=400
WindAjustAltitude=No
WindAjustAltitudeBy=2000
MinimumVisibility=0
MaximumVisibilityFewClouds=0
MaximumVisibility=0
MaximumVisibilityOvercast=0
MaximumVisibilityRainy=0
OneCloudLayer=No
ThinClouds=No
ThinThunderClouds=No
CloudThinness=1000
ThunderCloudThinness=10000
CloudTurbulence=No
CloudIcing=No
WindTurbulence=No
SuppressAllGusts=No
ExternalOptionControl=Yes
AutoTuneADF=No
KeepFS98CloudCover=No
ShowPMcontrols=No
MagicBattery=No
RudderSpikeRemoval=No
ElevatorSpikeRemoval=No
AileronSpikeRemoval=No
ReversedElevatorTrim=No
StopAutoFuel=No
TrapUserInterrupt=Yes
NavFreq50KHz=No
ClockSync=No
SmoothIAS=Yes
SetVisUpperAlt=No
VisUpperAltLimit=6000
MaxIce=3
MinIce=-1
WindSmoothingDelay=0
WindSmoothAirborneOnly=No
LimitWindVariance=No
VisSmoothingDelay=0
VisSmoothAirborneOnly=No
TrafficControlDirect=Yes
SuppressCloudTurbulence=No
SuppressWindTurbulence=No
SpoilerIncrement=512
ZapSound=firework
ShortAircraftNameOk=No
UseProfiles=No
TCASid=Flight
TCASrange=40
TrafficScanPerFrame=10
AxisCalibration=No
CentredDialogue=Yes
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
ClearWeatherDynamics=Yes
OwnWeatherChanges=No
FixWindows=No
FixControlAccel=No
WeatherReadInterval=4
MoveBGLvariables=Yes
TimeForSelect=4
WeatherReadsFast=No
MainMenu=&Modules
SubMenu=&FSUIPC ...

[JoystickCalibration]
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=Yes
ExcludeMixtureSet=Yes
ExcludePropPitchSet=Yes
SepRevsJetsOnly=No
ApplyHeloTrim=No
FlapsSetControl=0
FlapDetents=No
ReverserControl=66292
Reverser1Control=66422
Reverser2Control=66425
Reverser3Control=66428
Reverser4Control=66431
MaxThrottleForReverser=256
AileronTrimControl=0
RudderTrimControl=0
CowlFlaps1Control=0
CowlFlaps2Control=0
CowlFlaps3Control=0
CowlFlaps4Control=0
MaxSteerSpeed=60

[MacroFiles]
1=747_PMDG_CONS
2=747_PMDG_OVH
3=747_PMDG_THR

[Buttons]
ButtonRepeat=20,10
1=P4,5,C65758,0

[Axes]
0=0X,256,F,66420,0,0,0
1=5X,256,D,36,0,0,0

Although the BU0836 controllers don't show in the joystick section they were recognised by FSUIPC and I was able to assign the steering tiller and a button to them.

regards

Paul

Link to comment
Share on other sites
Pete Dowson Rising Star

Pete Dowson

Posted
Posted

Here is the full ini file

Some of the assignments are made to devices in the E to L range, but since there are no Windows-assigned IDs for them, they cannot work. I need the IDs to operate them.

I have assigned a number of buttons and an axis to the three BU0836 controllers

But the "clean" INI file clearly shows that only the 4 Saitek devices are detected by FSUIPC. I am lost here. I cannot imagine how you can assign in FSUIPC if it cannot see them.

An example of the 'muddling' of assignments : I had assigned the spoiler axis to the first axis of a Saitek Throttle Quadrant and the steering tiller to a BU0836. When I restarted to FS9, the steering tiller had replaced the spoiler axis but also remained assigned to the BU0836 axis. This sometimes also occurs with buttons. The size of this file is 4,518 bytes.

The non-detection of the BUO836 devices cannot really impinge on the Saitek ones. Are you sure you don't have things being assigned in FS too?

I deleted the ini file and this is the clean one that was created :

Yes, with no sign of any devices other than the 4 Saitek ones.

Although the BU0836 controllers don't show in the joystick section they were recognised by FSUIPC and I was able to assign the steering tiller and a button to them.

That's what I don't understand.

Evidently the USB implementation of those devices is completely non-standard, and the process I use to access them and obtain their names is not working, despite it being drawn from standard Microsoft references. But how you can assign to them when they have no ID listed I don't know. what numbers do they come up with (if you omit changing to use letters)?

I don't have any of those devices so it is going to be a problem finding out how they are so non-standard as to mess normal microsoft-approved methods up. I'll think about what I can do and get back to you.

Pete

Link to comment
Share on other sites
Pete Dowson Rising Star

Pete Dowson

Posted
Posted

I'll think about what I can do and get back to you.

Here's a program called "HidScanner" which produces a log file containing all the data about Windows-recognised HID devices (Human interface Devices), which includes joysticks. Could you run this please and show me the resulting HidScanner.LOG file?

Thanks,

Pete

HidScanner.zip

Link to comment
Share on other sites
paulnd Newbie

paulnd

Posted
  • Author
Posted

HidScanner.log:

********* HidScanner, Version 1.00 by Pete Dowson *********

  Device at "\\?\hid#vid_046d&pid_c513&mi_00#7&1872237a&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
  Vendor=046D, Product=C513 (Version 50.0)
  Manufacturer= Logitech
  Product= USB Receiver
  Serial Number= 
  Device is a keyboard
  Usage Page: 1
  Input Report Byte Length: 9
  Output Report Byte Length: 2
  Feature Report Byte Length: 0
  Number of Link Collection Nodes: 1
  Number of Input Button Caps: 2
  Number of InputValue Caps: 0
  Number of InputData Indices: 173
  Number of Output Button Caps: 1
  Number of Output Value Caps: 0
  Number of Output Data Indices: 5
  Number of Feature Button Caps: 0
  Number of Feature Value Caps: 0
  Number of Feature Data Indices: 0
  **************************************************************************

  Device at "\\?\hid#vid_046d&pid_c513&mi_01&col01#7&2ba23fb8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
  Vendor=046D, Product=C513 (Version 50.0)
  Manufacturer= Logitech
  Product= USB Receiver
  Serial Number= 
  Device is a mouse
  Usage Page: 1
  Input Report Byte Length: 7
  Output Report Byte Length: 0
  Feature Report Byte Length: 0
  Number of Link Collection Nodes: 2
  Number of Input Button Caps: 1
  Number of InputValue Caps: 4
  Number of InputData Indices: 12
  Number of Output Button Caps: 0
  Number of Output Value Caps: 0
  Number of Output Data Indices: 0
  Number of Feature Button Caps: 0
  Number of Feature Value Caps: 0
  Number of Feature Data Indices: 0
  **************************************************************************

  Device at "\\?\hid#vid_046d&pid_c513&mi_01&col02#7&2ba23fb8&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}"
  Vendor=046D, Product=C513 (Version 50.0)
  Manufacturer= Logitech
  Product= USB Receiver
  Serial Number= 
  Usage Page: C
  Input Report Byte Length: 5
  Output Report Byte Length: 0
  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: 652
  Number of Output Button Caps: 0
  Number of Output Value Caps: 0
  Number of Output Data Indices: 0
  Number of Feature Button Caps: 0
  Number of Feature Value Caps: 0
  Number of Feature Data Indices: 0
  **************************************************************************

  Device at "\\?\hid#vid_046d&pid_c513&mi_01&col03#7&2ba23fb8&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}"
  Vendor=046D, Product=C513 (Version 50.0)
  Manufacturer= Logitech
  Product= USB Receiver
  Serial Number= 
  Usage Page: 1
  Input Report Byte Length: 2
  Output Report Byte Length: 0
  Feature Report Byte Length: 0
  Number of Link Collection Nodes: 1
  Number of Input Button Caps: 3
  Number of InputValue Caps: 0
  Number of InputData Indices: 3
  Number of Output Button Caps: 0
  Number of Output Value Caps: 0
  Number of Output Data Indices: 0
  Number of Feature Button Caps: 0
  Number of Feature Value Caps: 0
  Number of Feature Data Indices: 0
  **************************************************************************

  Device at "\\?\hid#vid_046d&pid_c513&mi_01&col04#7&2ba23fb8&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}"
  Vendor=046D, Product=C513 (Version 50.0)
  Manufacturer= Logitech
  Product= USB Receiver
  Serial Number= 
  Usage Page: FF00
  Input Report Byte Length: 7
  Output Report Byte Length: 7
  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: 1
  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
  **************************************************************************

  Device at "\\?\hid#vid_046d&pid_c513&mi_01&col05#7&2ba23fb8&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}"
  Vendor=046D, Product=C513 (Version 50.0)
  Manufacturer= Logitech
  Product= USB Receiver
  Serial Number= 
  Usage Page: FF00
  Input Report Byte Length: 20
  Output Report Byte Length: 20
  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: 1
  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
  **************************************************************************

  Device at "\\?\hid#vid_06a3&pid_0763#7&b19c85b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
  Vendor=06A3, Product=0763 (Version 1.0)
  Manufacturer= Saitek
  Product= Saitek Pro Flight Rudder Pedals
  Serial Number= 
  Usage Page: 1
  Input Report Byte Length: 4
  Output Report Byte Length: 0
  Feature Report Byte Length: 0
  Number of Link Collection Nodes: 2
  Number of Input Button Caps: 0
  Number of InputValue Caps: 3
  Number of InputData Indices: 3
  Number of Output Button Caps: 0
  Number of Output Value Caps: 0
  Number of Output Data Indices: 0
  Number of Feature Button Caps: 0
  Number of Feature Value Caps: 0
  Number of Feature Data Indices: 0
  **************************************************************************

  Device at "\\?\hid#vid_06a3&pid_0bac#8&18043f47&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
  Vendor=06A3, Product=0BAC (Version 2.1)
  Manufacturer= Saitek
  Product= Saitek Pro Flight Yoke
  Serial Number= 
  Usage Page: 1
  Input Report Byte Length: 10
  Output Report Byte Length: 0
  Feature Report Byte Length: 0
  Number of Link Collection Nodes: 2
  Number of Input Button Caps: 1
  Number of InputValue Caps: 6
  Number of InputData Indices: 29
  Number of Output Button Caps: 0
  Number of Output Value Caps: 0
  Number of Output Data Indices: 0
  Number of Feature Button Caps: 0
  Number of Feature Value Caps: 0
  Number of Feature Data Indices: 0
  **************************************************************************

  Device at "\\?\hid#vid_06a3&pid_0c2d#7&30aa7b2c&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
  Vendor=06A3, Product=0C2D (Version 2.0)
  Manufacturer= Saitek
  Product= Saitek Pro Flight Quadrant
  Serial Number= 
  Usage Page: 1
  Input Report Byte Length: 6
  Output Report Byte Length: 0
  Feature Report Byte Length: 0
  Number of Link Collection Nodes: 2
  Number of Input Button Caps: 1
  Number of InputValue Caps: 3
  Number of InputData Indices: 12
  Number of Output Button Caps: 0
  Number of Output Value Caps: 0
  Number of Output Data Indices: 0
  Number of Feature Button Caps: 0
  Number of Feature Value Caps: 0
  Number of Feature Data Indices: 0
  **************************************************************************

  Device at "\\?\hid#vid_06a3&pid_0c2d#7&7c961ca&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
  Vendor=06A3, Product=0C2D (Version 2.0)
  Manufacturer= Saitek
  Product= Saitek Pro Flight Quadrant
  Serial Number= 
  Usage Page: 1
  Input Report Byte Length: 6
  Output Report Byte Length: 0
  Feature Report Byte Length: 0
  Number of Link Collection Nodes: 2
  Number of Input Button Caps: 1
  Number of InputValue Caps: 3
  Number of InputData Indices: 12
  Number of Output Button Caps: 0
  Number of Output Value Caps: 0
  Number of Output Data Indices: 0
  Number of Feature Button Caps: 0
  Number of Feature Value Caps: 0
  Number of Feature Data Indices: 0
  **************************************************************************

  Device at "\\?\hid#vid_09f3&pid_0064#7&31779344&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
  Vendor=09F3, Product=0064 (Version 1.1)
  Manufacturer= GoFlight
  Product= MCP PRO
  Serial Number= 0012 66
  Usage Page: 14
  Input Report Byte Length: 8
  Output Report Byte Length: 0
  Feature Report Byte Length: 8
  Number of Link Collection Nodes: 15
  Number of Input Button Caps: 1
  Number of InputValue Caps: 1
  Number of InputData Indices: 33
  Number of Output Button Caps: 0
  Number of Output Value Caps: 0
  Number of Output Data Indices: 0
  Number of Feature Button Caps: 1
  Number of Feature Value Caps: 9
  Number of Feature Data Indices: 41
  **************************************************************************

  Device at "\\?\hid#vid_16c0&pid_05b5#7&17b654a2&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
  Vendor=16C0, Product=05B5 (Version 1.33)
  Manufacturer= Leo Bodnar
  Product= BU0836 Interface
  Serial Number= A04064
  Usage Page: 1
  Input Report Byte Length: 6
  Output Report Byte Length: 0
  Feature Report Byte Length: 18
  Number of Link Collection Nodes: 3
  Number of Input Button Caps: 1
  Number of InputValue Caps: 1
  Number of InputData Indices: 33
  Number of Output Button Caps: 0
  Number of Output Value Caps: 0
  Number of Output Data Indices: 0
  Number of Feature Button Caps: 0
  Number of Feature Value Caps: 1
  Number of Feature Data Indices: 1
  **************************************************************************

  Device at "\\?\hid#vid_16c0&pid_05b5#7&1a7dc7f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
  Vendor=16C0, Product=05B5 (Version 1.22)
  Manufacturer= Leo Bodnar
  Product= BU0836 Interface
  Serial Number= A01337
  Usage Page: 1
  Input Report Byte Length: 8
  Output Report Byte Length: 0
  Feature Report Byte Length: 18
  Number of Link Collection Nodes: 3
  Number of Input Button Caps: 1
  Number of InputValue Caps: 2
  Number of InputData Indices: 34
  Number of Output Button Caps: 0
  Number of Output Value Caps: 0
  Number of Output Data Indices: 0
  Number of Feature Button Caps: 0
  Number of Feature Value Caps: 1
  Number of Feature Data Indices: 1
  **************************************************************************

  Device at "\\?\hid#vid_16c0&pid_05b5#7&a920a23&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
  Vendor=16C0, Product=05B5 (Version 1.33)
  Manufacturer= Leo Bodnar
  Product= BU0836 Interface
  Serial Number= A04055
  Usage Page: 1
  Input Report Byte Length: 6
  Output Report Byte Length: 0
  Feature Report Byte Length: 18
  Number of Link Collection Nodes: 3
  Number of Input Button Caps: 1
  Number of InputValue Caps: 1
  Number of InputData Indices: 33
  Number of Output Button Caps: 0
  Number of Output Value Caps: 0
  Number of Output Data Indices: 0
  Number of Feature Button Caps: 0
  Number of Feature Value Caps: 1
  Number of Feature Data Indices: 1
  **************************************************************************

Paul

Link to comment
Share on other sites
Pete Dowson Rising Star

Pete Dowson

Posted
Posted
HidScanner.log:

Hmm. That looks okay.

One moreyou are using FSUIPC3, which doesn't use the HID interface to windows except to get the device names. I'd like to check the IDs. Can you run the attached program, JoyView, and write down which entry (0 to 15 I think, or it might be 1-16) corresponds with each of your devices? That will give me the IDs.

After that I can only think to add more code to FSUIPC3 to log what it is seeing.

Regards

Pete

joyview.zip

Link to comment
Share on other sites
Pete Dowson Rising Star

Pete Dowson

Posted
Posted

They are entries [05], [06] and [07]

Okay, thanks. That makes sense, looking at the HidScanner log.

I've no chance of reproducing this problem here, so I'm going to have to look at ways of getting information logged from FSUIPC itself about what is going on. I'll start on this tomorrow (Thursday). Meanwhile, so I can send you test versions to get the extra info, and you can send me the logs, which might be larger than usual, could you reply to this via email, please. Send to petedowson@btconnect.com.

Regards

Pete

Link to comment
Share on other sites
paulnd Newbie

paulnd

Posted
  • Author
Posted

Hello Pete,

log file as requested

********* FSUIPC, Version 3.913 by Pete Dowson *********
Running on Windows Version 5.1 Build 2600 Service Pack 2
Verifying Certificate for "E:\Microsoft Games\Flight Simulator 9\MODULES\FSUIPC.dll" now ...
   SUCCESS! Signature verifies okay!
Checking name of joystick #0:
at "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_0C2D\"
OK, registry entry found: looking for OEMName
OEMName="Saitek Pro Flight Throttle Quadrant"
Checking name of joystick #1:
at "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_0763\"
OK, registry entry found: looking for OEMName
OEMName="Saitek Pro Flight Rudder Pedals"
Checking name of joystick #2:
at "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_0BAC\"
OK, registry entry found: looking for OEMName
OEMName="Saitek Pro Flight Yoke"
Checking name of joystick #3:
at "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_0C2D\"
OK, registry entry found: looking for OEMName
OEMName="Saitek Pro Flight Throttle Quadrant"
Checking name of joystick #4:
at "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_16C0&PID_05B5\"
Checking name of joystick #5:
at "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_16C0&PID_05B5\"
Checking name of joystick #6:
at "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_16C0&PID_05B5\"
No joystick #7 detected
No joystick #8 detected
No joystick #9 detected
No joystick #10 detected
No joystick #11 detected
No joystick #12 detected
No joystick #13 detected
No joystick #14 detected
No joystick #15 detected
Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL)
User Name="***********"
User Addr="*******************"
FSUIPC Key is provided
WIDEFS not user registered, or expired
Module base=61000000
ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E
WeatherOptions(Orig)=40003605[40003605]
InitDelay: 0 seconds
WeatherReadInterval=4
LogOptions=00008001
LogExtras=2048
DebugStatus=15
   114162 System time = 17:55:23
   114162 E:\Microsoft Games\Flight Simulator 9\
   114162 System time = 17:55:23, FS2004 time = 12:00:00 (00:00Z)
   230913 FLIGHTS\OTHER\FLTSIM.flt
   230975 AIRCRAFT\c172\Cessna172SP.air
   231537 Aircraft="Cessna Skyhawk 172SP"
   262425 C:\Users\Paul\Documents\Flight Simulator Files\UI generated flight.flt
   262644 Clear All Weather requested: external weather discarded
   276294 Advanced Weather Interface Enabled
   327665 Traffic File #15 = "scenery\world\scenery\traffic27w&s88"
   327680 Traffic File #43 = "scenery\world\scenery\traffic_000_woa_air canada_su08_fs9"
   327790 Traffic File #363 = "scenery\world\scenery\traffic_000_woa_ultimate ga citation 550_su06"
   327946 Traffic File #212 = "scenery\world\scenery\traffic_000_woa_horizon air_su08"
   327961 Traffic File #507 = "scenery\world\scenery\traffic_225_woa_alaska airlines_wi07"
   328024 Traffic File #86 = "scenery\world\scenery\traffic_000_woa_american airlines_su08"
   328055 Traffic File #143 = "scenery\world\scenery\traffic_000_woa_continental air lines_su08"
   328055 Traffic File #432 = "scenery\world\scenery\traffic_115_woa_southwest airlines_su07"
   328148 Traffic File #478 = "scenery\world\scenery\traffic_191_woa_united airlines_su07"
   328164 Traffic File #153 = "scenery\world\scenery\traffic_000_woa_delta connection_su08"
   328258 Traffic File #436 = "scenery\world\scenery\traffic_120_woa_sun country airlines_su07"
   328289 Traffic File #255 = "scenery\world\scenery\traffic_000_woa_lufthansa_wi08"
   328507 Traffic File #506 = "scenery\world\scenery\traffic_224_woa_ultimate ga learjet 40_su06"
   328507 Traffic File #527 = "scenery\world\scenery\traffic_254_woa_ultimate ga cessna 402_su06"
   328850 Traffic File #234 = "scenery\world\scenery\traffic_000_woa_jetblue airways_su08"
   328975 Traffic File #284 = "scenery\world\scenery\traffic_000_woa_northwest airlines_su08"
   329116 Traffic File #372 = "scenery\world\scenery\traffic_000_woa_virgin america_su08"
   329162 Traffic File #449 = "scenery\world\scenery\traffic_13_woa_united parcel service_su07"
   329194 Traffic File #461 = "scenery\world\scenery\traffic_155_woa_scandinavian airlines_su07"
   329194 Traffic File #470 = "scenery\world\scenery\traffic_177_woa_ultimate ga gulfstream 4_su07"
   329521 Traffic File #498 = "scenery\world\scenery\traffic_213_woa_ultimate ga learjet 45_su06"
   339895 WeatherOptions set, now 40003605 (timer=0)
   340410 Traffic File #541 = "scenery\world\scenery\traffic_58_woa_british airways_wi07"
   340441 Traffic File #543 = "scenery\world\scenery\traffic_60_woa_fedex_su05"
   340473 Traffic File #575 = "scenery\world\scenery\trafficpp3"
   340488 Traffic File #576 = "scenery\world\scenery\trafficpp4"
   345402 System time = 17:59:14, FS2004 time = 17:57:41 (00:57Z)
   345402 *** FSUIPC log file being closed
Memory managed: 20 Allocs, 187 Freed
********* FSUIPC Log file closed ***********

The joystick section in the ini file has remained unchanged

[JoyNames]
AutoAssignLetters=No
0=Saitek Pro Flight Throttle Quadrant
1=Saitek Pro Flight Rudder Pedals
2=Saitek Pro Flight Yoke
3=Saitek Pro Flight Throttle Quadrant

If I change AutoAssignLetters=Yes then

[JoyNames]
AutoAssignLetters=Yes
0=Saitek Pro Flight Throttle Quadrant
1=Saitek Pro Flight Rudder Pedals
2=Saitek Pro Flight Yoke
3=Saitek Pro Flight Throttle Quadrant
A=Saitek Pro Flight Throttle Quadrant
B=Saitek Pro Flight Rudder Pedals
C=Saitek Pro Flight Yoke
D=Saitek Pro Flight Throttle Quadrant
E=Unknown Device #4
F=Unknown Device #5
G=Unknown Device #6

Paul

Link to comment
Share on other sites
Pete Dowson Rising Star

Pete Dowson

Posted
Posted

log file as requested

Okay. The interesting thing is not simply that there's no OEMName parameter in the Registry, but there's actually no entry at all in the Registry for the BU0836 devices!

Did you not receive any sort of installer for those devices? I don't understand why there can be numerical IDs assigned (4, 5, 6) yet there be no way of relating them to anything in the Registry.

Can Mr. Bodnar help at all with this, do you think?

The joystick section in the ini file has remained unchanged

Yes, it will do. I'll look at that, see if I can at least add the lines

4=Unknown Device #4

5=Unknown Device #5

6=Unknown Device #6

which might make it less confusing. But without registry information there's no full fix at all.

Regards

Pete

Link to comment
Share on other sites
Pete Dowson Rising Star

Pete Dowson

Posted
Posted

There are no installers required for the BU0836 controller and according to the website, this is a deliberate design feature.

The problem then is the omission of important information in the Registry. Registry data is probably the main reason for installers in any case. Even an .INF file whicvh you could execute yourself would be better than nothing.

All i can do is try to include them as Unknown Devices. Otherwise, you have to avoid using the Joystick Lettering facilities in FSUIPC.

Anyway, try 3.914. no need now for the logging, you can remove those extra lines.

http://fsuipc.simflight.com/beta/FSUIPC3914.zip

Let me know how you get on, please.

Regards

Pete

Link to comment
Share on other sites
paulnd Newbie

paulnd

Posted
  • Author
Posted

Pete,

According to the BU0836 website :

Unique serial number helps Windows remember each device

Ever unplugged a joystick and had Windows lose calibration settings?

This controller retains settings even if plugged in a different USB port.

Or if you use two and swap them over.

Is it not possible for FSUIPC to use the serial numbers to identify the controllers?

Paul

Link to comment
Share on other sites
Pete Dowson Rising Star

Pete Dowson

Posted
Posted

Is it not possible for FSUIPC to use the serial numbers to identify the controllers?

Two problems:

1. So far no other joystick manufacturer seems to make use of the serial number facility at all -- it is blank or a fixed value like 0. So this would be a one-off.

2. At present there is no HID-handling code in FSUIPC. I now know how to get this stuff as shown in that HidScanner program I provided. However it is a lot of code for very little useful return. It won't benefit the Saitek devices you have, for instance -- the two throttle quadrants are indistinguishable.

The only overall solution is for you to never swap the USB connections. Provided devices remain connected to the same USB sockets, the ID's will remain the same (unless you re-install windows!).

Regards

Pete

Link to comment
Share on other sites
paulnd Newbie

paulnd

Posted
  • Author
Posted

Thanks for your assistance Pete, I've no idea of the coding required but is it not possible to contruct an identifer from a combination of names and serial numbers so that if either one weren't used, the device could still be identified.

regards

Paul

Link to comment
Share on other sites
Pete Dowson Rising Star

Pete Dowson

Posted
Posted
Thanks for your assistance Pete, I've no idea of the coding required but is it not possible to contruct an identifer from a combination of names and serial numbers so that if either one weren't used, the device could still be identified.

You missed the point, I think, that (a) I can't read the serial number without adding a heluva lot of code which is not useful except, apparently for these BU0836 devices, and (b) It won't help at all with the two (or more) Saitek throttle quadrants, or most all other devices which do not provide a serial number in any case. Please re-read my last reply which you seem to have misunderstood.

Provided you don't keep unplugging things and moving them around i don't see there's a problem. The ID numbers assigned by Windows won't change if you leave them connected.

Pete

Link to comment
Share on other sites
  • 3 weeks later...

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
 Share
Go to topic listing
×
×
  • 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.