Jump to content
The simFlight Network Forums

Recommended Posts

If I go to windows games devices calibration the throttle flaps and speed brake arm register as device Buo836a and can be calibrated. The park brake and fuel cutoff levers don’t. If this helps

Share this post


Link to post
Share on other sites

As I said, I need to see your joyscan.csv and log files, as well as your current ini - could you please attach all 3. If your devices are recognised by windows as joystick/HID devices then they should be recognised by FSUIPC.

Share this post


Link to post
Share on other sites

********* FSUIPC5, Version 5.151 (21st February 2019) by Pete Dowson *********
Running inside Prepar3D v4
Module base=7FED9920000
Windows 7 Home Premium 64 Bit with SP 1.0 reported as Build 7601 (OS 6.1)
Prepar3D.exe version = 4.5.12.30293
Reading options from "C:\Program Files\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.ini"
Checking the Registrations now ...
User Name="MARTYN DAVIS"
User Addr="marty.davis71@gmail.com"
FSUIPC5 Key is provided
WideFS7 Key is provided
        0 System time = 07/07/2019 20:43:10
        0 FLT UNC path = "C:\Users\sim\Documents\Prepar3D v4 Files\"
       16 Using DialogMode
       16 FS UNC path = "C:\Program Files\Lockheed Martin\Prepar3D v4\"
      156 ---------------------- Joystick Device Scan -----------------------
      156 Product= Saitek Pro Flight Rudder Pedals
      156    Manufacturer= Saitek
      156    Vendor=06A3, Product=0763 (Version 1.0)
      156    GUIDs returned for product: VID_06A3&PID_0763:
      156       GUID= {E98E5CA0-5C91-11E1-8006-444553540000}
      156       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0
      156       GUID= {E98E5CA0-5C91-11E1-8005-444553540000}
      156       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0
      172 Product= Saitek Pro Flight Rudder Pedals
      172    Manufacturer= Saitek
      172    Vendor=06A3, Product=0763 (Version 1.0)
      172 Product= BU0836A Interface
      172    Manufacturer= Leo Bodnar
      172    Serial Number= B31362
      172    Vendor=16C0, Product=05BA (Version 1.34)
      172    GUIDs returned for product: VID_16C0&PID_05BA:
      172       GUID= {8C6FD830-FE13-11E2-8001-444553540000}
      172       Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R3970,U3970,V3980,X0,Y0,Z3661
      172 Product= 737YOKE-LE by ACE
      172    Manufacturer= ACE
      172    Serial Number= A18593
      172    Vendor=16C0, Product=2786 (Version 1.35)
      172    GUIDs returned for product: VID_16C0&PID_2786:
      172       GUID= {6368B4F0-476D-11E2-8001-444553540000}
      172       Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X2822,Y2739,Z0
      172       GUID= {E98E5CA0-5C91-11E1-8009-444553540000}
      172       Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X2860,Y2950,Z0
      172 Product= 737YOKE-LE by ACE
      172    Manufacturer= ACE
      172    Serial Number= A23813
      172    Vendor=16C0, Product=2786 (Version 1.35)
      172 -------------------------------------------------------------------
      172 Device acquired for use:
      172    Joystick ID = 1 (Registry okay)
      172    1=Saitek Pro Flight Rudder Pedals
      172    1.GUID={E98E5CA0-5C91-11E1-8006-444553540000}
      172 Device acquired for use:
      172    Joystick ID = 4 (Registry okay)
      172    4=Saitek Pro Flight Rudder Pedals
      172    4.GUID={E98E5CA0-5C91-11E1-8005-444553540000}
      172 Device acquired for use:
      172    Joystick ID = 0 (Registry okay)
      172    0=BU0836A Interface
      172    0.GUID={8C6FD830-FE13-11E2-8001-444553540000}
      172 Device acquired for use:
      172    Joystick ID = 2 (Registry okay)
      172    2=737YOKE-LE by ACE
      172    2.GUID={6368B4F0-476D-11E2-8001-444553540000}
      172 Device acquired for use:
      172    Joystick ID = 3 (Registry okay)
      172    3=737YOKE-LE by ACE
      172    3.GUID={E98E5CA0-5C91-11E1-8009-444553540000}
      172 -------------------------------------------------------------------
      188 LogOptions=00000000 00000001
      188 -------------------------------------------------------------------
      188 SimConnect_Open succeeded: waiting to check version okay
      188 Opened separate AI Traffic client okay
      188 ### PDKmodeHelper callback registered
     2434 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.5.12.30293 (SimConnect: 4.5.0.0)
     2434 Initialising SimConnect data requests now
     2434 FSUIPC Menu entry added
     2434 ... Using Prepar3D with Professional License
     2450 C:\Users\sim\Documents\Prepar3D v4 Files\Prepar3D_Default.fxml
     2450 C:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Prosim 737-800 Regular\Prosim738.air
    32417 ### The user object is 'Prosim_737_800_Winglets_Prosim_Livery'
    32417 ### Mode is NORMAL
    33182 ### Mode: PAUSE on
    45677 Loading Complete ...
    45709 ### Mode is NORMAL
    48017 Aircraft loaded: running normally now ...
    48142 User Aircraft ID 2 supplied, now being used
    48298 System time = 07/07/2019 20:43:58, Simulator time = 14:02:28 (05:02Z)
    48298 Aircraft="Prosim_737_800_Winglets_Prosim_Livery"
    54445 -------------------- Starting everything now ----------------------
    54445 Starting WideServer now ...
    55958 Advanced Weather Interface Enabled
    69046 Sim stopped: average frame rate for last 20 secs = 4.5 fps
    69046    Max AI traffic was 0 aircraft
    69046 -------------------------------------------------------------------
    70357 === Closing session: waiting for DLLStop to be called ...
    78687 === DLLStop called ...
    78687 === Closing external processes we started ...
    79686 === About to kill any Lua plug-ins still running ...
    79842 === Closing global Lua thread
    80856 === About to kill my timers ...
    81058 === Restoring window procs ...
    81058 === Unloading libraries ...
    81058 === stopping other threads ...
    81058 === ... Button scanning ...
    81152 === ... Axis scanning ...
    81261 === Releasing joystick devices ...
    81261 === Freeing macro memory
    81261 === Removing any offset overrides
    81261 === Closing all WideFS threads
    81261 TransmitClientEvent failed!
    81261 TransmitClientEvent failed!
    81433 TransmitClientEvent failed!
    81433 TransmitClientEvent failed!
    81495 TransmitClientEvent failed!
    81495 TransmitClientEvent failed!
    81604 TransmitClientEvent failed!
    81604 TransmitClientEvent failed!
    81714 TransmitClientEvent failed!
    81714 TransmitClientEvent failed!
    81823 TransmitClientEvent failed!
    81823 TransmitClientEvent failed!
    81932 TransmitClientEvent failed!
    81932 TransmitClientEvent failed!
    82041 TransmitClientEvent failed!
    82041 TransmitClientEvent failed!
    82150 TransmitClientEvent failed!
    82150 TransmitClientEvent failed!
    82260 TransmitClientEvent failed!
    82260 TransmitClientEvent failed!
    82369 TransmitClientEvent failed!
    82369 TransmitClientEvent failed!
    82494 TransmitClientEvent failed!
    82494 TransmitClientEvent failed!
    82587 TransmitClientEvent failed!
    82587 TransmitClientEvent failed!
    82696 TransmitClientEvent failed!
    82696 TransmitClientEvent failed!
    82806 TransmitClientEvent failed!
    82806 TransmitClientEvent failed!
    82915 TransmitClientEvent failed!
    82915 TransmitClientEvent failed!
    83024 TransmitClientEvent failed!
    83024 TransmitClientEvent failed!
    83133 TransmitClientEvent failed!
    83133 TransmitClientEvent failed!
    83242 TransmitClientEvent failed!
    83242 TransmitClientEvent failed!
    83352 TransmitClientEvent failed!
    83352 TransmitClientEvent failed!

Share this post


Link to post
Share on other sites

********* FSUIPC5, Version 5.151 (21st February 2019) by Pete Dowson *********
Running inside Prepar3D v4
Module base=7FED9920000
Windows 7 Home Premium 64 Bit with SP 1.0 reported as Build 7601 (OS 6.1)
Prepar3D.exe version = 4.5.12.30293
Reading options from "C:\Program Files\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.ini"
Checking the Registrations now ...
User Name="MARTYN DAVIS"
User Addr="marty.davis71@gmail.com"
FSUIPC5 Key is provided
WideFS7 Key is provided
        0 System time = 07/07/2019 20:43:10
        0 FLT UNC path = "C:\Users\sim\Documents\Prepar3D v4 Files\"
       16 Using DialogMode
       16 FS UNC path = "C:\Program Files\Lockheed Martin\Prepar3D v4\"
      156 ---------------------- Joystick Device Scan -----------------------
      156 Product= Saitek Pro Flight Rudder Pedals
      156    Manufacturer= Saitek
      156    Vendor=06A3, Product=0763 (Version 1.0)
      156    GUIDs returned for product: VID_06A3&PID_0763:
      156       GUID= {E98E5CA0-5C91-11E1-8006-444553540000}
      156       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0
      156       GUID= {E98E5CA0-5C91-11E1-8005-444553540000}
      156       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0
      172 Product= Saitek Pro Flight Rudder Pedals
      172    Manufacturer= Saitek
      172    Vendor=06A3, Product=0763 (Version 1.0)
      172 Product= BU0836A Interface
      172    Manufacturer= Leo Bodnar
      172    Serial Number= B31362
      172    Vendor=16C0, Product=05BA (Version 1.34)
      172    GUIDs returned for product: VID_16C0&PID_05BA:
      172       GUID= {8C6FD830-FE13-11E2-8001-444553540000}
      172       Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R3970,U3970,V3980,X0,Y0,Z3661
      172 Product= 737YOKE-LE by ACE
      172    Manufacturer= ACE
      172    Serial Number= A18593
      172    Vendor=16C0, Product=2786 (Version 1.35)
      172    GUIDs returned for product: VID_16C0&PID_2786:
      172       GUID= {6368B4F0-476D-11E2-8001-444553540000}
      172       Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X2822,Y2739,Z0
      172       GUID= {E98E5CA0-5C91-11E1-8009-444553540000}
      172       Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X2860,Y2950,Z0
      172 Product= 737YOKE-LE by ACE
      172    Manufacturer= ACE
      172    Serial Number= A23813
      172    Vendor=16C0, Product=2786 (Version 1.35)
      172 -------------------------------------------------------------------
      172 Device acquired for use:
      172    Joystick ID = 1 (Registry okay)
      172    1=Saitek Pro Flight Rudder Pedals
      172    1.GUID={E98E5CA0-5C91-11E1-8006-444553540000}
      172 Device acquired for use:
      172    Joystick ID = 4 (Registry okay)
      172    4=Saitek Pro Flight Rudder Pedals
      172    4.GUID={E98E5CA0-5C91-11E1-8005-444553540000}
      172 Device acquired for use:
      172    Joystick ID = 0 (Registry okay)
      172    0=BU0836A Interface
      172    0.GUID={8C6FD830-FE13-11E2-8001-444553540000}
      172 Device acquired for use:
      172    Joystick ID = 2 (Registry okay)
      172    2=737YOKE-LE by ACE
      172    2.GUID={6368B4F0-476D-11E2-8001-444553540000}
      172 Device acquired for use:
      172    Joystick ID = 3 (Registry okay)
      172    3=737YOKE-LE by ACE
      172    3.GUID={E98E5CA0-5C91-11E1-8009-444553540000}
      172 -------------------------------------------------------------------
      188 LogOptions=00000000 00000001
      188 -------------------------------------------------------------------
      188 SimConnect_Open succeeded: waiting to check version okay
      188 Opened separate AI Traffic client okay
      188 ### PDKmodeHelper callback registered
     2434 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.5.12.30293 (SimConnect: 4.5.0.0)
     2434 Initialising SimConnect data requests now
     2434 FSUIPC Menu entry added
     2434 ... Using Prepar3D with Professional License
     2450 C:\Users\sim\Documents\Prepar3D v4 Files\Prepar3D_Default.fxml
     2450 C:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Prosim 737-800 Regular\Prosim738.air
    32417 ### The user object is 'Prosim_737_800_Winglets_Prosim_Livery'
    32417 ### Mode is NORMAL
    33182 ### Mode: PAUSE on
    45677 Loading Complete ...
    45709 ### Mode is NORMAL
    48017 Aircraft loaded: running normally now ...
    48142 User Aircraft ID 2 supplied, now being used
    48298 System time = 07/07/2019 20:43:58, Simulator time = 14:02:28 (05:02Z)
    48298 Aircraft="Prosim_737_800_Winglets_Prosim_Livery"
    54445 -------------------- Starting everything now ----------------------
    54445 Starting WideServer now ...
    55958 Advanced Weather Interface Enabled
    69046 Sim stopped: average frame rate for last 20 secs = 4.5 fps
    69046    Max AI traffic was 0 aircraft
    69046 -------------------------------------------------------------------
    70357 === Closing session: waiting for DLLStop to be called ...
    78687 === DLLStop called ...
    78687 === Closing external processes we started ...
    79686 === About to kill any Lua plug-ins still running ...
    79842 === Closing global Lua thread
    80856 === About to kill my timers ...
    81058 === Restoring window procs ...
    81058 === Unloading libraries ...
    81058 === stopping other threads ...
    81058 === ... Button scanning ...
    81152 === ... Axis scanning ...
    81261 === Releasing joystick devices ...
    81261 === Freeing macro memory
    81261 === Removing any offset overrides
    81261 === Closing all WideFS threads
    81261 TransmitClientEvent failed!
    81261 TransmitClientEvent failed!
    81433 TransmitClientEvent failed!
    81433 TransmitClientEvent failed!
    81495 TransmitClientEvent failed!
    81495 TransmitClientEvent failed!
    81604 TransmitClientEvent failed!
    81604 TransmitClientEvent failed!
    81714 TransmitClientEvent failed!
    81714 TransmitClientEvent failed!
    81823 TransmitClientEvent failed!
    81823 TransmitClientEvent failed!
    81932 TransmitClientEvent failed!
    81932 TransmitClientEvent failed!
    82041 TransmitClientEvent failed!
    82041 TransmitClientEvent failed!
    82150 TransmitClientEvent failed!
    82150 TransmitClientEvent failed!
    82260 TransmitClientEvent failed!
    82260 TransmitClientEvent failed!
    82369 TransmitClientEvent failed!
    82369 TransmitClientEvent failed!
    82494 TransmitClientEvent failed!
    82494 TransmitClientEvent failed!
    82587 TransmitClientEvent failed!
    82587 TransmitClientEvent failed!
    82696 TransmitClientEvent failed!
    82696 TransmitClientEvent failed!
    82806 TransmitClientEvent failed!
    82806 TransmitClientEvent failed!
    82915 TransmitClientEvent failed!
    82915 TransmitClientEvent failed!
    83024 TransmitClientEvent failed!
    83024 TransmitClientEvent failed!
    83133 TransmitClientEvent failed!
    83133 TransmitClientEvent failed!
    83242 TransmitClientEvent failed!
    83242 TransmitClientEvent failed!
    83352 TransmitClientEvent failed!
    83352 TransmitClientEvent failed!
    83461 TransmitClientEvent failed!
    83461 TransmitClientEvent failed!
    83586 TransmitClientEvent failed!
    83586 TransmitClientEvent failed!
    83679 TransmitClientEvent failed!
    83679 TransmitClientEvent failed!
    83788 TransmitClientEvent failed!
    83788 TransmitClientEvent failed!
    83898 TransmitClientEvent failed!
    83898 TransmitClientEvent failed!

Share this post


Link to post
Share on other sites

General]
UpdatedByVersion=5151
History=ZHLS0H8HHGK4K0GRY3WHE
MouseWheelMove=No
MouseWheelTrim=No
MouseWheelTrimSpeed=1
JoystickTimeout=20
PollGFTQ6=Yes
BlankDisplays=No
FixMachSpeedBug=No
AutoScanDevices=Yes
VisibilityOptions=No
OneCloudLayer=No
CloudTurbulence=No
CloudIcing=No
GenerateCirrus=No
SuppressCloudTurbulence=No
MaxIce=-4
MinIce=-4
UpperWindGusts=No
SuppressWindTurbulence=No
SuppressWindVariance=No
WindTurbulence=No
TurbulenceRate=1.0,5.0
TurbulenceDivisor=20,20,40,40
SuppressAllGusts=No
MaxSurfaceWind=0
WindLimitLevel=200
WindDiscardLevel=400
WindAjustAltitude=No
WindAjustAltitudeBy=2000
SmoothBySimTime=No
WindSmoothing=No
WindSmoothness=2
WindSmoothAirborneOnly=Yes
PressureSmoothness=0
TemperatureSmoothness=0
DisconnTrimForAP=No
ZeroElevForAPAlt=No
ThrottleSyncAll=No
WhiteMessages=No
ShowPMcontrols=No
SpoilerIncrement=512
MagicBattery=No
RudderSpikeRemoval=No
ElevatorSpikeRemoval=No
AileronSpikeRemoval=No
ReversedElevatorTrim=No
ClockSync=No
ClockSyncMins=5
ClearWeatherDynamics=No
OwnWeatherChanges=No
TimeForSelect=4
LoadFlightMenu=No
LoadPlanMenu=No
PauseAfterCrash=No
BrakeReleaseThreshold=75
SaveDataWithFlights=No
ZapSound=firework
ShortAircraftNameOk=No
UseProfiles=Yes
EnableMouseLook=No
AxesWrongRange=No
TCASid=Flight
TCASrange=40
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
AxisIntercepts=No
DontResetAxes=No
InitDelay=0
GetNearestAirports=Yes
WeatherReadFactor=2
WeatherRewriteSeconds=1
LuaRerunDelay=66
Console=No
OOMcheck=Yes
InitDelayDevicesToo=No
PMDG737offsets=Auto
PMDG747offsets=Auto
PMDG777offsets=Auto
Annotate=Yes
UseSystemTime=No
UseMidMouseBtn=Yes
RestoreSimcWindows=No
DelayedMouseLookZoom=No
WideLuaGlobals=Yes
TextFileMaxRead=4095
TextFileNumbers=Yes
TextFilePhonetics=Yes
ThreadAffinityMask=x0
LuaAffinityMask=x0
LogOptionProtect=Yes
TimeForLuaClosing=2
TrafficStallTime=1
InitialStallTime=10
NormalStallTime=1
ComReadLoopTime=20
DebugLua=Yes
FSVersionUsed="Lockheed Martin® Prepar3D® v4",4.5.12.30293
SimConnectUsed=4.5.0.0
LogWeather=Yes
LogWrites=Yes
LogReads=Yes
LogEvents=Yes
LogLua=Yes
LogAxes=Yes
LogButtonsKeys=Yes
LogExtras=Yes

[JoyNames]
AutoAssignLetters=No
T=G-Throttles << MISSING JOYSTICK >>
T.GUID={048B2C90-D690-11E1-8001-444553540000}
B=BU0836X Interface << MISSING JOYSTICK >>
B.GUID={8C6FD830-FE13-11E2-8001-444553540000}
R=Saitek Pro Flight Rudder Pedals
R.GUID={E98E5CA0-5C91-11E1-8006-444553540000}
S=Saitek Pro Flight Rudder Pedals
S.GUID={E98E5CA0-5C91-11E1-8005-444553540000}
Z=737YOKE-LE by ACE
Z.GUID={6368B4F0-476D-11E2-8001-444553540000}
Y=737YOKE-LE by ACE
Y.GUID={E98E5CA0-5C91-11E1-8009-444553540000}
1=Saitek Pro Flight Rudder Pedals
1.GUID={E98E5CA0-5C91-11E1-8006-444553540000}
2=737YOKE-LE by ACE
2.GUID={6368B4F0-476D-11E2-8001-444553540000}
3=737YOKE-LE by ACE
3.GUID={E98E5CA0-5C91-11E1-8009-444553540000}
4=Saitek Pro Flight Rudder Pedals
4.GUID={E98E5CA0-5C91-11E1-8005-444553540000}
0=BU0836A Interface
0.GUID={8C6FD830-FE13-11E2-8001-444553540000}
A=BU0836A Interface
A.GUID={8C6FD830-FE13-11E2-8001-444553540000}

[Buttons]
ButtonRepeat=20,10
13=P64,0,C66072,0  -{PITOT_HEAT_ON}-
14=U64,0,C66073,0  -{PITOT_HEAT_OFF}-
15=P64,1,C65591,0  -{SITUATION_RESET}-
16=P64,24,C65733,0  -{ABORT}-
17=P64,25,Cx02003320,xABCD  -{offset word set, offset 3320}-
21=PT,0,Cx02000BC8,x0007
22=UT,0,Cx02000BC8,x0000
23=RT,3,C65602,0
24=UT,3,C65697,0
25=PB,0,Cx02000BC8,x0007
26=UB,0,Cx02000BC8,x0000
27=PB,1,C66079,0
28=PB,2,C66080,0
29=RB,3,C65607,0
30=RB,4,C65615,0
31=PB,5,Cx02007370,x003C
32=RY,1,C65607,0  -{ELEV_TRIM_DN}-
33=RY,0,C65615,0  -{ELEV_TRIM_UP}-
34=RZ,1,C65607,0  -{ELEV_TRIM_DN}-
35=RZ,0,C65615,0  -{ELEV_TRIM_UP}-
36=PZ,4,C65561,0  -{PAUSE_TOGGLE}-
PollInterval=25

[AutoSave]
Next=1
Interval=60
Files=10
SaveOnGround=No
AutoSaveEnabled=No

[GPSout]
GPSoutEnabled=No

[GPSout2]
GPSoutEnabled=No

[WideServer]
WideFSenabled=Yes
AdvertiseService=No
Port=8002
Port2=9002
ProtocolPreferred=UDP
AllowShutdown=Yes


[Sounds]
Path=D:\fsx\Sound\
Device1=Primary Sound Driver
Device2=Speakers (Realtek High Definition Audio)
Device3=Realtek Digital Output (Realtek High Definition Audio)
Device4=MX613ST-4 (NVIDIA High Definition Audio)
Device5=MX613ST-0 (NVIDIA High Definition Audio)
Device6=MX613ST-C (NVIDIA High Definition Audio)

[Axes]
0=TX,256,D,9,0,0,0
1=TY,256,D,10,0,0,0
2=TZ,256,D,23,0,0,0
3=TU,256,D,22,0,0,0
PollInterval=10
RangeRepeatRate=10
4=RX,256,D,7,0,0,0 -{ DIRECT: LeftBrake }-
5=RY,256,D,8,0,0,0 -{ DIRECT: RightBrake }-
6=RR,256,D,3,0,0,0 -{ DIRECT: Rudder }-
7=ZX,256,D,1,0,0,0 -{ DIRECT: Aileron }-
8=ZY,256,D,2,0,0,0 -{ DIRECT: Elevator }-
9=YX,256,D,1,0,0,0 -{ DIRECT: Aileron }-
10=YY,256,D,2,0,0,0 -{ DIRECT: Elevator }-
11=SX,256,D,7,0,0,0 -{ DIRECT: LeftBrake }-
12=SY,256,D,8,0,0,0 -{ DIRECT: RightBrake }-
13=SR,256,D,3,0,0,0 -{ DIRECT: Rudder }-

[ClientNames]
1=SLAVE12
2=SLAVE13
3=SLAVE14

[JoystickCalibration]
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=Yes
ExcludeMixtureSet=Yes
ExcludePropPitchSet=Yes
SepRevsJetsOnly=No
ApplyHeloTrim=No
UseAxisControlsForNRZ=No
FlapsSetControl=0
FlapDetents=Yes
ReverserControl=66292
Reverser1Control=66422
Reverser2Control=66425
Reverser3Control=66428
Reverser4Control=66431
MaxThrottleForReverser=256
AileronTrimControl=66731
RudderTrimControl=66732
CowlFlaps1Control=66162
CowlFlaps2Control=66163
CowlFlaps3Control=66164
CowlFlaps4Control=66165
SteeringTillerControl=0
MaxSteerSpeed=60
LeftBrake=-16380,16380/16
RightBrake=-16380,16380/16
FlapStarts=-16384,-13765,-9239,-6209,-2020,336,6755,10375,11868
Flaps=-16384,16380
FlapEnds=-14027,-10025,-7032,-3553,75,4292,10226,11607,13137
RudderBlendLowest=1
Throttle1=-16380,-512,512,16380
Throttle=-16380,16380

[Traffic Limiter]
AirportPreference=50
PlannedAirportsPreference=50
GroundPreference=50
NearerPreference=50
TargetFrameRate=0
TrafficLimit=0

[Monitor]
Display=15

Share this post


Link to post
Share on other sites
3 hours ago, John Dowson said:

As I said, I need to see your joyscan.csv and log files, as well as your current ini - could you please attach all 3. If your devices are recognised by windows as joystick/HID devices then they should be recognised by FSUIPC.

where would i find joyscan.csv

Share this post


Link to post
Share on other sites

********* WideServer.DLL Log [version 7.076] *********
Blocksize guide = 8192 (double allowed)
Date (dmy): 07/07/19, Time 21:17:29.187: Server name is MASTER11
    15085 Initialising TCP/IP server
    15085 Initialising UDP/IP server
    17082 Connected to computer "SLAVE14" running WideClient version 6.860 (IP=192.168.15.120) UDP
   726028 Auto send for 0 stopped before sending all data (0 of 47 sent), Error=10013 (IP=255.255.255.255) UDP
   732549 Close signalled to clients
   733657 Closing down now ...
Memory managed:  Offset records: 244 alloc, 242 free
Read buffer usage:  6932 alloc, 6932 free, max in session: 1
Write buffer usage: 31690 alloc, 31690 free, max in session: 1
Throughput maximum achieved:  20 frames/sec, 789 bytes/sec
Throughput average achieved for complete session:  4 frames/sec, 137 bytes/sec
Average receive rate from "SLAVE14":  9 frames/sec, 552 bytes/sec
********* Log file closed *********

Share this post


Link to post
Share on other sites

********* WideServer.DLL Log [version 7.076] *********
Blocksize guide = 8192 (double allowed)
Date (dmy): 07/07/19, Time 20:44:04.710: Server name is MASTER11
    15662 Initialising TCP/IP server
    15662 Initialising UDP/IP server
    26816 Auto send for 0 stopped before sending all data (0 of 47 sent), Error=10013 (IP=255.255.255.255) UDP
    33540 Close signalled to clients
 

Share this post


Link to post
Share on other sites

oh if i move throttles in prosim they show as as the interface card as well with heap of numbers

Share this post


Link to post
Share on other sites
22 hours ago, Marty said:

where would i find joyscan.csv

The same folder as your log an ini files - a file called FSUIPC5.Joyscan.csv.

Which PC is your throttle connected to? Both your ini and log files don't show this device connected.

It looks like you do have issues with WideFS. Error 10013 indicates that there is a socket connection error, most probably caused by a firewall or antivirus software. You need either to stop the firewall/anti0virus software or configure to allow access form your client to server PCs and vica-versa.

I am not familiar with ProSim. Pete should be back tomorrow and will be able to advise further with this.

Do you see anything in the axis assignment tab when you move your throttle? I am slightly confused...if the BU0836A Interface card IS your throttle, but just renamed, then the update I previously posted will restore your previous assignments, i.e. change these lines

T=G-Throttles << MISSING JOYSTICK >>
T.GUID={048B2C90-D690-11E1-8001-444553540000}

to

T=BU0836A Interface
T.GUID={8C6FD830-FE13-11E2-8001-444553540000}

and now also remove this:

A=BU0836A Interface
A.GUID={8C6FD830-FE13-11E2-8001-444553540000}

 

John

Edited by John Dowson
Further info added

Share this post


Link to post
Share on other sites

The joyscan.csv file is not in that folder I have looked around but can’t locate it. I dont recall it ever being there. I will make your changes the throttle quad is connected to the server pc via USB (pc prepar is located) there is a wire connection to the Bodnar interface card I have looked at this and it is I presume the park brake LED light. There is an SIOC script for park brake light I’m assuming when it is on the light goes on the Bodnar card is connected to the slave pc where SIOC server is located. I’m assuming Prosim and fsuicpv5 communicate via widefs but having trouble with connection. The firewall is turned off on all pc and just to be sure I made sure the wide client 9Now the slave had firewall permission

i can’t see how the throttle is connected to the Bodnar card and it was running via fsuicp before the changes

Share this post


Link to post
Share on other sites
21 hours ago, Marty said:

The joyscan.csv file is not in that folder I have looked around but can’t locate it.

FSUIPC5 always created the FSUIPC5.Joyscan.csv file. It will certainly be there, in the same folder as your FSUIPC5.INI and FSUIPC5.Log files.

21 hours ago, Marty said:

I will make your changes the throttle quad is connected to the server pc via USB (pc prepar is located) there is a wire connection to the Bodnar interface card I have looked at this and it is I presume the park brake LED light. There is an SIOC script for park brake light I’m assuming when it is on the light goes on the Bodnar card is connected to the slave pc where SIOC server is located. I’m assuming Prosim and fsuicpv5 communicate via widefs but having trouble with connection.

 I'm finding this a bit confusing. If the Bodnar board is connected to the same PC as your P3D Installation, then that's where the throttle axes will be seen, and directly, not via WideFS.

If your throttles are connected to a Bodnar board on a different PC, then WideClient does not send the axis inputs through to FSUIPC, only buttons -- these will be seen as connecting to joysticks with numbers with a client PC number first. Client numbers are listed in your FSUIPC5.INI file, here:

[ClientNames]
1=SLAVE12
2=SLAVE13
3=SLAVE14

I don't know what troubles you are having with connection, or which WideFS client your Bodnar board is connected to (if it is), but the WideServer.LOG you posted showed a healthy connection with "SLAVE14":

********* WideServer.DLL Log [version 7.076] *********
Blocksize guide = 8192 (double allowed)
Date (dmy): 07/07/19, Time 21:17:29.187: Server name is MASTER11
    15085 Initialising TCP/IP server
    15085 Initialising UDP/IP server
    17082 Connected to computer "SLAVE14" running WideClient version 6.860 (IP=192.168.15.120) UDP
   726028 Auto send for 0 stopped before sending all data (0 of 47 sent), Error=10013 (IP=255.255.255.255) UDP
   732549 Close signalled to clients
   733657 Closing down now ...
Memory managed:  Offset records: 244 alloc, 242 free
Read buffer usage:  6932 alloc, 6932 free, max in session: 1
Write buffer usage: 31690 alloc, 31690 free, max in session: 1
Throughput maximum achieved:  20 frames/sec, 789 bytes/sec
Throughput average achieved for complete session:  4 frames/sec, 137 bytes/sec
Average receive rate from "SLAVE14":  9 frames/sec, 552 bytes/sec

********* Log file closed *********

The error 10013 is only the disconnection when you closed the P3D session. It was obviously quite happily exchanging data for nearly 12 minutes before this.

However, WideFs is not involved in your throttle axis problems.

22 hours ago, Marty said:

i can’t see how the throttle is connected to the Bodnar card and it was running via fsuicp before the changes

If the only change was from P3D3 to P3D4 and so FSUIPC4 to FSUIPC5, and no changes were made to the hardware at all, then everything would have worked exactly as before. That's always been one of the whole points of the FSUIPC interface -- continuity right through FS versions since FS98.

Changes to the USB connections would mean the assignments have to be re-matched, for which I see John has helped sort out for you. Also, re-installs of Windows changes things too because it will generate new "GUIDs" -- the unique identity assigned by Windows to everything (all devices, all objects, even all internal textures and so on).

Incidentally, I assume you are using the old version of ProSim (v1)? The latest versions of Prosim v2 do require you to assign and calibrate all flight controls in ProSim. But i have been doing this for my throttles successfully now since first using ProSim, which was then an early version 1. I've only just recently moved my flight controls (yoke, rudder, till0 to ProSim.

Pete

 

Share this post


Link to post
Share on other sites
1 hour ago, Pete Dowson said:

FSUIPC5 always created the FSUIPC5.Joyscan.csv file. It will certainly be there, in the same folder as your FSUIPC5.INI and FSUIPC5.Log files.

 I'm finding this a bit confusing. If the Bodnar board is connected to the same PC as your P3D Installation, then that's where the throttle axes will be seen, and directly, not via WideFS.

If your throttles are connected to a Bodnar board on a different PC, then WideClient does not send the axis inputs through to FSUIPC, only buttons -- these will be seen as connecting to joysticks with numbers with a client PC number first. Client numbers are listed in your FSUIPC5.INI file, here:

[ClientNames]
1=SLAVE12
2=SLAVE13
3=SLAVE14

I don't know what troubles you are having with connection, or which WideFS client your Bodnar board is connected to (if it is), but the WideServer.LOG you posted showed a healthy connection with "SLAVE14":

********* WideServer.DLL Log [version 7.076] *********
Blocksize guide = 8192 (double allowed)
Date (dmy): 07/07/19, Time 21:17:29.187: Server name is MASTER11
    15085 Initialising TCP/IP server
    15085 Initialising UDP/IP server
    17082 Connected to computer "SLAVE14" running WideClient version 6.860 (IP=192.168.15.120) UDP
   726028 Auto send for 0 stopped before sending all data (0 of 47 sent), Error=10013 (IP=255.255.255.255) UDP
   732549 Close signalled to clients
   733657 Closing down now ...
Memory managed:  Offset records: 244 alloc, 242 free
Read buffer usage:  6932 alloc, 6932 free, max in session: 1
Write buffer usage: 31690 alloc, 31690 free, max in session: 1
Throughput maximum achieved:  20 frames/sec, 789 bytes/sec
Throughput average achieved for complete session:  4 frames/sec, 137 bytes/sec
Average receive rate from "SLAVE14":  9 frames/sec, 552 bytes/sec

********* Log file closed *********

The error 10013 is only the disconnection when you closed the P3D session. It was obviously quite happily exchanging data for nearly 12 minutes before this.

However, WideFs is not involved in your throttle axis problems.

If the only change was from P3D3 to P3D4 and so FSUIPC4 to FSUIPC5, and no changes were made to the hardware at all, then everything would have worked exactly as before. That's always been one of the whole points of the FSUIPC interface -- continuity right through FS versions since FS98.

Changes to the USB connections would mean the assignments have to be re-matched, for which I see John has helped sort out for you. Also, re-installs of Windows changes things too because it will generate new "GUIDs" -- the unique identity assigned by Windows to everything (all devices, all objects, even all internal textures and so on).

Incidentally, I assume you are using the old version of ProSim (v1)? The latest versions of Prosim v2 do require you to assign and calibrate all flight controls in ProSim. But i have been doing this for my throttles successfully now since first using ProSim, which was then an early version 1. I've only just recently moved my flight controls (yoke, rudder, till0 to ProSim.

Pete

 

The throttles are connected via USB to the server pc the park brake lever led light to the slave pc via a bodner board. The USB connection has not been changed on the server pc for the throttle I will look again tomorrow for the joystick file. It was not in the module folder but I will check again to be absolutely sure. Prosim is v1.45 I was going to upgrade that but after this I think I’ll give it a miss.

The bodner card is connected to the slave pc only and not the server. The only change other than the prepar upgrade was fsuicpv5 and the accidental upgrade to windows on the slave pc the bodner card is connected to. I disconnected the firewall and just to be sure made sure the wide client was in the firewall accepted programmes. I will implement johns changes tomorrow and c how things go. Thank you for the support thus far

Share this post


Link to post
Share on other sites
1 hour ago, Marty said:

The throttles are connected via USB to the server pc

and

1 hour ago, Marty said:

The bodner card is connected to the slave pc only and not the server.

So the throttle unit is a normal Windows-recognised throttle, or does it have specific drivers? What make is it?

Check Windows "Game Controllers". Is it seen there, as throttle, and will it show its actions there? If not then that's what FSUIPC doesn't see it.

1 hour ago, Marty said:

The only change other than the prepar upgrade was fsuicpv5 and the accidental upgrade to windows on the slave pc the bodner card is connected to.

Well the slave PC change would have no effect at all on the main PC so that's not the main problem. And it really isn't possible for things to get messed up by only a change from P3D3 to 4 and FSUIPC4 to 5. They are completely interchangeable as far as FSUIPC is concerned -- well, except for isolated facilities like "mouse macros" which won't apply to ProSim aircraft in any case.

So i'm sure something else must have changed in your changeover process. It would be useful to know what, but never mind. Let's move on.

2 hours ago, Marty said:

I disconnected the firewall and just to be sure made sure the wide client was in the firewall accepted programmes.

I don't think there's much to worry about on the 'slave'. I think we're now only trying to work out why the throttles aren't seen.

Incidentally, have you considered assigning and calibrating the throttles in Prosim instead, in any case. I'm sure it suits it better -- as i say, i've been using this method through all ProSim 1 and 2 versions.

2 hours ago, Marty said:

Prosim is v1.45 I was going to upgrade that but after this I think I’ll give it a miss.

Why? Prosim is becoming more and more capable. What other cockpit software would you consider?

Pete

 

Share this post


Link to post
Share on other sites

Good?, flags, VID, PID, Name, INIid, REGid, RegEntry, INIguid, REGguid, HIDguid, ValsOK?, ReadsOk?

,,, HIDscanning completed

N, x00, x06A3, x0763, , -1, -1, 0, {NULL}, {NULL}, {E98E5CA0-5C91-11E1-8006-444553540000}, Y, N

N, x00, x06A3, x0763, , -1, -1, 0, {NULL}, {NULL}, {E98E5CA0-5C91-11E1-8005-444553540000}, Y, N

N, x00, x16C0, x05BA, , -1, -1, 0, {NULL}, {NULL}, {8C6FD830-FE13-11E2-8001-444553540000}, Y, N

N, x00, x16C0, x2786, , -1, -1, 0, {NULL}, {NULL}, {6368B4F0-476D-11E2-8001-444553540000}, Y, N

N, x00, x16C0, x2786, , -1, -1, 0, {NULL}, {NULL}, {E98E5CA0-5C91-11E1-8009-444553540000}, Y, N

,,, REGscanning completed

N, x00, x06A3, x0763, Saitek Pro Flight Rudder Pedals, -1, 1, 1, {NULL}, {E98E5CA0-5C91-11E1-8006-444553540000}, {E98E5CA0-5C91-11E1-8006-444553540000}, Y, Y

N, x00, x06A3, x0763, Saitek Pro Flight Rudder Pedals, -1, 4, 0, {NULL}, {E98E5CA0-5C91-11E1-8005-444553540000}, {E98E5CA0-5C91-11E1-8005-444553540000}, Y, Y

N, x00, x16C0, x05BA, BU0836A Interface, -1, 0, 0, {NULL}, {8C6FD830-FE13-11E2-8001-444553540000}, {8C6FD830-FE13-11E2-8001-444553540000}, Y, Y

N, x00, x16C0, x2786, 737YOKE-LE by ACE, -1, 2, 1, {NULL}, {6368B4F0-476D-11E2-8001-444553540000}, {6368B4F0-476D-11E2-8001-444553540000}, Y, Y

N, x00, x16C0, x2786, 737YOKE-LE by ACE, -1, 3, 0, {NULL}, {E98E5CA0-5C91-11E1-8009-444553540000}, {E98E5CA0-5C91-11E1-8009-444553540000}, Y, Y

,,, User settings imported

N, x00, x06A3, x0763, Saitek Pro Flight Rudder Pedals, 1, 1, 1, {E98E5CA0-5C91-11E1-8006-444553540000}, {E98E5CA0-5C91-11E1-8006-444553540000}, {E98E5CA0-5C91-11E1-8006-444553540000}, Y, Y

N, x00, x06A3, x0763, Saitek Pro Flight Rudder Pedals, 4, 4, 0, {E98E5CA0-5C91-11E1-8005-444553540000}, {E98E5CA0-5C91-11E1-8005-444553540000}, {E98E5CA0-5C91-11E1-8005-444553540000}, Y, Y

N, x00, x16C0, x05BA, BU0836A Interface, 0, 0, 0, {8C6FD830-FE13-11E2-8001-444553540000}, {8C6FD830-FE13-11E2-8001-444553540000}, {8C6FD830-FE13-11E2-8001-444553540000}, Y, Y

N, x00, x16C0, x2786, 737YOKE-LE by ACE, 2, 2, 1, {6368B4F0-476D-11E2-8001-444553540000}, {6368B4F0-476D-11E2-8001-444553540000}, {6368B4F0-476D-11E2-8001-444553540000}, Y, Y

N, x00, x16C0, x2786, 737YOKE-LE by ACE, 3, 3, 0, {E98E5CA0-5C91-11E1-8009-444553540000}, {E98E5CA0-5C91-11E1-8009-444553540000}, {E98E5CA0-5C91-11E1-8009-444553540000}, Y, Y

,,, Values matched and decided

Y, x1E, x06A3, x0763, Saitek Pro Flight Rudder Pedals, 1, 1, 1, {E98E5CA0-5C91-11E1-8006-444553540000}, {E98E5CA0-5C91-11E1-8006-444553540000}, {E98E5CA0-5C91-11E1-8006-444553540000}, Y, Y

Y, x1E, x06A3, x0763, Saitek Pro Flight Rudder Pedals, 4, 4, 0, {E98E5CA0-5C91-11E1-8005-444553540000}, {E98E5CA0-5C91-11E1-8005-444553540000}, {E98E5CA0-5C91-11E1-8005-444553540000}, Y, Y

Y, x1E, x16C0, x05BA, BU0836A Interface, 0, 0, 0, {8C6FD830-FE13-11E2-8001-444553540000}, {8C6FD830-FE13-11E2-8001-444553540000}, {8C6FD830-FE13-11E2-8001-444553540000}, Y, Y

Y, x1E, x16C0, x2786, 737YOKE-LE by ACE, 2, 2, 1, {6368B4F0-476D-11E2-8001-444553540000}, {6368B4F0-476D-11E2-8001-444553540000}, {6368B4F0-476D-11E2-8001-444553540000}, Y, Y

Y, x1E, x16C0, x2786, 737YOKE-LE by ACE, 3, 3, 0, {E98E5CA0-5C91-11E1-8009-444553540000}, {E98E5CA0-5C91-11E1-8009-444553540000}, {E98E5CA0-5C91-11E1-8009-444553540000}, Y, Y

Share this post


Link to post
Share on other sites

i found the joyscan.csv file attached i will wait for a response before making johns changes. Im thinking I might use prosim for the throttles as u do i never gave it much thought looks like iam going to have to re config the whole throttle anyway so start afresh.

With the sim i want to keep it as close to real 737 800 as i can to mimic real world cockpit. Im still looking at software but for now orbx for scenery mainly airport scenery in australia and AI ATC like vox i will use vatsim and IVAO but i dont want to bod down the sim to much with software.

Share this post


Link to post
Share on other sites

Your joyscan.csv file shows the device BU0836A Interface is recognised and matches you log and ini, so this must be your throttle device - please go ahead and make the suggested changes. I'm not sure if this will work though, as you cannot see the axis value change (in the axis assignment tab) when this is unassigned, which is strange.

You could also try downloading the HiDScanner utility  - from 

Run this and move the throttle to see if any axis values are changed (and post the log).

 

Share this post


Link to post
Share on other sites
1 hour ago, John Dowson said:

Your joyscan.csv file shows the device BU0836A Interface is recognised and matches you log and ini, so this must be your throttle device - please go ahead and make the suggested changes. I'm not sure if this will work though, as you cannot see the axis value change (in the axis assignment tab) when this is unassigned, which is strange.

You could also try downloading the HiDScanner utility  - from 

Run this and move the throttle to see if any axis values are changed (and post the log).

 

What does FSUICP SDK do? I’m trying to learn about offsets does this have something to do with that?

Share this post


Link to post
Share on other sites

I made johns changes to the ini file and fsuicp is now seeing the throttles speed brake and flaps is there any way to load the old assignments or will I have to re calibrate from scratch. 

Share this post


Link to post
Share on other sites

I tried calibrating throttles in Prosim but the MCP module is running on the slave Prosim recommends running on flight sim pc. I tried calibrating on MCP module on flight sim pc but did not recognise will have to do more research I think I will calibrate in fsuicp as originally was

Share this post


Link to post
Share on other sites
22 hours ago, Marty said:

What does FSUICP SDK do? I’m trying to learn about offsets does this have something to do with that?

The SDK is the 'Software Development Kit', which allows you to write programs (in various languages) that communicate with FSUIPC (i.e. read/write offsets).

22 hours ago, Marty said:

I made johns changes to the ini file and fsuicp is now seeing the throttles speed brake and flaps

The changes did not allow you to see the throttles! They only put back your previous assignments/calibration to that device. If that worked, then you must have been  able to see this before, they just weren't assigned.

23 hours ago, Marty said:

is there any way to load the old assignments or will I have to re calibrate from scratch

Well, what you have now is all your old assignments back from your old ini, or thats what I thought! Looking at your ini, it looks like you have your flaps and toe brakes calibrated:

    LeftBrake=-16380,16380/16
    RightBrake=-16380,16380/16
    FlapStarts=-16384,-13765,-9239,-6209,-2020,336,6755,10375,11868
    Flaps=-16384,16380
    FlapEnds=-14027,-10025,-7032,-3553,75,4292,10226,11607,13137

But no calibration for your ailerons, elevator, throttle, etc, so you will need to calibrate them (especially if you are sending to FSUIPC for calibration).

Then again, if you are going to upgrade ProSim, you will probably be better off assigning and calibrating there, as Pete suggested.

23 hours ago, Marty said:

I tried calibrating throttles in Prosim but the MCP module is running on the slave Prosim recommends running on flight sim pc

It is recommended to run on the flight sim pc to avoid delays caused by network latency, although it should still work running on the slave.

 

Share this post


Link to post
Share on other sites
12 hours ago, John Dowson said:

The SDK is the 'Software Development Kit', which allows you to write programs (in various languages) that communicate with FSUIPC (i.e. read/write offsets).

The changes did not allow you to see the throttles! They only put back your previous assignments/calibration to that device. If that worked, then you must have been  able to see this before, they just weren't assigned.

Well, what you have now is all your old assignments back from your old ini, or thats what I thought! Looking at your ini, it looks like you have your flaps and toe brakes calibrated:

    LeftBrake=-16380,16380/16
    RightBrake=-16380,16380/16
    FlapStarts=-16384,-13765,-9239,-6209,-2020,336,6755,10375,11868
    Flaps=-16384,16380
    FlapEnds=-14027,-10025,-7032,-3553,75,4292,10226,11607,13137

But no calibration for your ailerons, elevator, throttle, etc, so you will need to calibrate them (especially if you are sending to FSUIPC for calibration).

Then again, if you are going to upgrade ProSim, you will probably be better off assigning and calibrating there, as Pete suggested.

It is recommended to run on the flight sim pc to avoid delays caused by network latency, although it should still work running on the slave.

 

Before your suggested changes there was no recognition of the throttles flaps and speed brake in fsuicp now the movements are seen in axis assignments.

Share this post


Link to post
Share on other sites
12 hours ago, John Dowson said:

The SDK is the 'Software Development Kit', which allows you to write programs (in various languages) that communicate with FSUIPC (i.e. read/write offsets).

The changes did not allow you to see the throttles! They only put back your previous assignments/calibration to that device. If that worked, then you must have been  able to see this before, they just weren't assigned.

Well, what you have now is all your old assignments back from your old ini, or thats what I thought! Looking at your ini, it looks like you have your flaps and toe brakes calibrated:

    LeftBrake=-16380,16380/16
    RightBrake=-16380,16380/16
    FlapStarts=-16384,-13765,-9239,-6209,-2020,336,6755,10375,11868
    Flaps=-16384,16380
    FlapEnds=-14027,-10025,-7032,-3553,75,4292,10226,11607,13137

But no calibration for your ailerons, elevator, throttle, etc, so you will need to calibrate them (especially if you are sending to FSUIPC for calibration).

Then again, if you are going to upgrade ProSim, you will probably be better off assigning and calibrating there, as Pete suggested.

It is recommended to run on the flight sim pc to avoid delays caused by network latency, although it should still work running on the slave.

 

I’m not real keen at this time to upgrade Prosim a little weary after this upgrade I will look into it.  But I would have to install across 4 pc etc with mcp EFIS and displays running I would hate to upset those. At this time Prosim detects the throttle but I can’t calibrate or assign I really haven’t spent any time on Prosim I wanted to upgrade software before making switch and gauge assignments. 

I think the sdk is a little out of depth for the moment I understand the principle but I don’t intend on writing programmes I’m still trying to work out SIOC scripting. 

I will re calibrate the throttles, speed brake and ailerons. The ailerons appear easy but throttles a little different as well as speed brake have looked at some videos and the user manual but appreciate any advice here.

Share this post


Link to post
Share on other sites

We provide (or at least try to...) all the information that you should need in the manuals, so please use them. If you have any issues/problems, then post and we can help (but check FAQ and previous posts first).

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

×

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.