shorthauler

HI John, I think I get what you mean. I would also need to assign virtual buttons for each position, right? Yes, the switch rotates freely / indefinitely.

Hi John, thank you for looking into this and apologies for posting in the wrong forum. From the hardware side of things, both selectors are 8-position rotary switches. From the software side, both PMDG and FSLabs only have offsets / parameters to decrease or increase the position of the selector switch. There are no specific offsets / parameters for specific positions of the selector. I am attaching my Lua scripts (for both PMDG and FSLabs) and the FSUIPC.ini. The Lua scripts are triggered by way of Mobiflight. There is no slow / fast option as Mobiflight looks at an 8-position-rotary-switch as an assembly of eight buttons, not as an encoder. An encoder for Mobiflight is a switch that has three pins (A, B and ground). So I am trying to emulate a rotary encoder with a direction of turn by way of these scripts. Best regards, Holger Holgers scripts.zip

Dear all, I am using an 8-position-rotary switch for the mode / range function for various aircraft (FSLabs A320, PMDG). All these aircraft on increase or decrease of the knob, not a specific position. So I had to write a script that diagnoses in which direction the switch is being turned. This is what I did: Every position (e.g. "2") triggers a specific Lua script. The script first writes into a free custom FSUIPC offset specific to this position. It then checks whether the offset of the position to the left ("1") has been set. If yes, it assumes the switch has been turned to the right. It then clears the offset of the previous position and sends a parameter to increase range or mode. If no, it assumes the switch has been turned to the left and decreases. This works reasonably well, but if I turn the switch too much, I get jumps and mostly increases where there should be decreases. I am wondering why this is. Any ideas in this forum? I also have optical rotary encoders that send an enormous amount of parameters per unit of time and there is no problem. Software is Mobiflight, FSX, FSLABs A320, PMDG 744. I did a test in Mobiflight where I directly sent keyboard inputs to notepad - no skipping or reversing there. Best regards, Holger Script for the first position: ipc.writeUB(0x66CA,2) -- setting the offset of the current position to 2 btnstate = ipc.readUB(0x66C9) -- reading the offset of the position before (clockwise) if btnstate == 2 -- if the switch is turned in clockwise direction, the offset has been set to two at the previous detent then ipc.writeUB(0x66C9,1) -- resetting the offset of the previous detent ipc.control(70158,16384) -- command for increasing range else -- if btnstate is not 2 it means the switch has been turned counter clockwise ipc.control(70158,8192) -- command for decreasing range end Script for the second position: ipc.writeUB(0x66CB,2) btnstate = ipc.readUB(0x66CA) if btnstate == 2 then ipc.writeUB(0x66CA,1) ipc.control(70158,16384) -- command for increasing range else ipc.control(70158,8192) -- command for decreasing range end Etc.

I am using the EPIC card. Quite an old product but to my mind still more advanced as what is available today as values are generated within the card and then sent to FS rather then sending signals to FS which turn the knobs. However, not every add-on aircraft has Offesets, so I am now programming EPIC to send button pulses to FSUIPC. By way of a macro and LVARs they will then manipulate the aircraft's input (A2A C172 in this case). Now I notice if I turn a knob quickly, it sends three pulses from EPIC to the Windows Game Controller. But out of these three pulses, only one goes through to the aircraft. The other two get lost on the way. I think I have explained in a non-technical manner what some of you might have experienced - FSX seems to be rather slow accepting inputs, so if they are above FSX's tolerance, they get lost. Can anyone help with this? Best, Holger

Thanks a lot, this helped. No idea how this hotchpotch of *.ini came about, though. Best regards, Holger

I have checked in FSX. The controllers are switched off, and I even deleted all axis in the controllers. This is my FSUIPC. Best, HOlger [General] UpdatedByVersion=4972 History=K5WTBRWEI4QTD1H2JE7ST AxesWrongRange=No TCASid=Flight TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No AxisIntercepts=No DontResetAxes=No InitDelay=0 GetNearestAirports=Yes OOMcheck=Yes OOMcheckInterval=10 WeatherReadFactor=2 WeatherRewriteSeconds=1 CustomWeatherModify=No SimConnectStallTime=20 LuaRerunDelay=66 Console=No InitDelayDevicesToo=No NewInterceptTextMenu=No UseSystemTime=No UseMidMouseBtn=Yes MouseWheelMove=No MouseWheelTrim=No MouseWheelTrimSpeed=1 JoystickTimeout=20 PollGFTQ6=Yes BlankDisplays=No FixControlAccel=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=Substring UseProfiles=Yes EnableMouseLook=No DelayedMouseLookZoom=No Annotate=Yes NewDeleteVehiclesForAES=No WideLuaGlobals=Yes LogOptionProtect=Yes TimeForLuaClosing=2 ThreadAffinityMask=x0 LuaAffinityMask=x0 ConsoleWindow=730,147,1407,554 FSVersionUsed="Microsoft Flight Simulator X",10.0.61472.0 SimConnectUsed=10.0.61259.0 [WideServer] WideFSenabled=Yes [JoyNames] AutoAssignLetters=No 2=BU0836X Interface 2.GUID={B2A96040-D917-11E8-8003-444553540000} 1=Logitech Attack 3 1.GUID={B2A96040-D917-11E8-8002-444553540000} [Axes] PollInterval=10 RangeRepeatRate=10 0=0X,256,D,1,0,0,0 -{ DIRECT: Aileron }- 1=0Z,256,D,4,0,0,0 -{ DIRECT: Throttle }- 2=1X,256,D,1,0,0,0 -{ DIRECT: Aileron }- 3=1Y,256,D,2,0,0,0 -{ DIRECT: Elevator }- 4=1Z,256,D,4,0,0,0 -{ DIRECT: Throttle }- 5=2X,256,D,1,0,0,0 -{ DIRECT: Aileron }- 6=2Y,256,D,2,0,0,0 -{ DIRECT: Elevator }- 7=2R,256,D,3,0,0,0 -{ DIRECT: Rudder }- [Buttons] PollInterval=25 ButtonRepeat=20,10 1=R2,30,C65721,0 -{BRAKES_RIGHT}- 2=R2,31,C65720,0 -{BRAKES_LEFT}- 3=P1,6,K113,8 -{Key press: F2}- 5=R2,28,C65607,0 -{ELEV_TRIM_DN}- 6=P2,27,K90,8 -{Key press: Z}- 7=R0,6,K113,8 -{Key press: F2}- 8=R2,29,C65615,0 -{ELEV_TRIM_UP}- [AutoSave] Next=4 Interval=60 Files=10 SaveOnGround=No AutoSaveEnabled=Yes 1=Wed 220318 2=Wed 220517 3=Wed 221608 4=Wed 000506 5=Wed 000606 6=Wed 000705 7=Wed 000805 8=Wed 000905 9=Wed 001004 10=Wed 001104 [GPSout] GPSoutEnabled=No Port=COM1 Speed=4800 Interval=2000 PosTo6Decimal=No SimModeIndicator=No Sentences= [GPSout2] GPSoutEnabled=No Port=<none set> Speed=4800 Interval=2000 PosTo6Decimal=No SimModeIndicator=No Sentences= [Sounds] Path=E:\FSX\Flight Simulator X\Sound\ Device1=Primärer Soundtreiber Device2=Lautsprecher (Realtek High Definition Audio) Device3=Realtek Digital Output (Realtek High Definition Audio) [Programs] Run1=HIDE,"E:\FSX\Flight Simulator X\Aero.bat" [JoystickCalibration] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No 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 Elevator=-15862,191,512,16283/16 Throttle=-13184,16253/16 Aileron=-8912,-1754,512,6064/8 Rudder=-15758,713,713,15496 [Profile.FSL A320] 1=FSLabs A320-X Gulf Air 2=FSLabs A320-X Airberlin 3=FSLabs A320-X Middle East Airlines 4=FSLabs A320-X Turkish Airlines 5=FSLabs A320-X Royal Jordanian 6=FSLabs A320X CFM Condor_D-AICK 7=FSLabs A320-X Lufthansa [Axes.FSL A320] RangeRepeatRate=10 0=0X,256,D,1,0,0,0 -{ DIRECT: Aileron }- 1=0Y,256,D,2,0,0,0 -{ DIRECT: Elevator }- 2=0Z,256,D,4,0,0,0 -{ DIRECT: Throttle }- 3=1Z,256,F,65697,0,0,0 -{ TO SIM: THROTTLE_SET }- 4=2R,256,F,65696,0,0,0 -{ TO SIM: RUDDER_SET }- [JoystickCalibration.FSL A320] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No 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 Elevator=-16383,58,512,16383 Rudder=-11267,-697,512,8720 Throttle=-16253,13952 Aileron=-16380,-512,512,16380 [Profile.C172R] 1=C172R default [Axes.C172R] RangeRepeatRate=10 0=0X,256,D,1,0,0,0 -{ DIRECT: Aileron }- 1=0Z,256,D,4,0,0,0 -{ DIRECT: Throttle }- 2=1Z,256,D,4,0,0,0 -{ DIRECT: Throttle }- 3=2X,256,D,1,0,0,0 -{ DIRECT: Aileron }- 4=2Y,256,D,2,0,0,0 -{ DIRECT: Elevator }- 5=2R,256,D,3,0,0,0 -{ DIRECT: Rudder }- [JoystickCalibration.C172R] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No 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 Aileron=-16173,-2052,-2052,16184 Elevator=-16111,-91,-91,15856/24 Rudder=-15762,-531,512,16280 Throttle=-16384,13952/16 [Buttons.C172R] 0=R2,31,C65720,0 -{BRAKES_LEFT}- 1=R2,30,C65721,0 -{BRAKES_RIGHT}- [Profile.FSL 320] 1=FSLabs A320-X Saudi Arabian Airlines [Axes.FSL 320] RangeRepeatRate=10 0=0X,256,D,1,0,0,0 1=0Y,256,D,2,0,0,0 2=1Z,256,D,4,0,0,0 3=2R,256,D,3,0,0,0 [JoystickCalibration.FSL 320] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No 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 Aileron=-16380,-512,512,16380 Elevator=-16383,58,512,16383 Rudder=-15758,713,713,15496 Throttle=-13208,16256/16 [Buttons.FSL A320] 0=R1,6,K113,8 -{Key press: F2}- 1=R2,30,C65721,0 -{BRAKES_RIGHT}- 2=R2,31,C65720,0 -{BRAKES_LEFT}- [Profile.B763] 1=Level D Simulations B767-300ER Winglet - DHL G-DHLF 2=Level D Simulations B767-300ER Winglet - Condor Flugdienst (circa 2014) D-ABUA 3=UPS 767-300ER - Winglet 4=Cessna310_DIRFT [Buttons.B763] 0=R1,6,K113,8 -{Key press: F2}- 1=R2,30,C65721,0 -{BRAKES_RIGHT}- 2=R2,31,C65720,0 -{BRAKES_LEFT}- [Axes.B763] RangeRepeatRate=10 0=0X,256,D,1,0,0,0 -{ DIRECT: Aileron }- 1=0Y,256,D,2,0,0,0 -{ DIRECT: Elevator }- 2=0Z,256,D,4,0,0,0 -{ DIRECT: Throttle }- 3=1X,256,F,65697,0,0,0 -{ TO SIM: THROTTLE_SET }- 4=1Z,256,D,4,0,0,0 -{ DIRECT: Throttle }- 5=2X,256,D,1,0,0,0 -{ DIRECT: Aileron }- 6=2Y,256,D,2,0,0,0 -{ DIRECT: Elevator }- 7=2R,256,D,3,0,0,0 -{ DIRECT: Rudder }- [JoystickCalibration.B763] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No 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 Aileron=-8176,-512,512,6344 Elevator=-11360,-512,512,14302/16 Rudder=-9945,-336,512,8392 //Throttle=-16384,13545/16 Throttle=-13568,16253/16 [Profile.B744] 1=PMDG 747-430 Lufthansa (D-ABVM | 2016) 2=PMDG 747-400ER SVA 3=PMDG 747-4P8ER BAHRAIN AIR A9C-HMK 4=PMDG 747-400 PMDG House (N744GE | 2017) [Buttons.B744] 0=R1,6,K113,8 -{Key press: F2}- 1=R2,30,C65721,0 -{BRAKES_RIGHT}- 2=R2,31,C65720,0 -{BRAKES_LEFT}- 3=P6,3,C70156,0 -{Custom control: <70156>}- 4=P6,4,C70156,1 -{Custom control: <70156>}- 5=P6,5,C70156,2 -{Custom control: <70156>}- 6=P6,6,C70156,3 -{Custom control: <70156>}- 7=P6,7,C70157,1 -{Custom control: <70157>}- 8=P6,8,C70158,0 -{Custom control: <70158>}- 9=P6,9,C70158,1 -{Custom control: <70158>}- 10=P6,16,C70158,2 -{Custom control: <70158>}- 11=P6,17,C70158,3 -{Custom control: <70158>}- 12=P6,18,C70158,4 -{Custom control: <70158>}- 13=P6,19,C70158,5 -{Custom control: <70158>}- 14=P6,20,C70158,6 -{Custom control: <70158>}- 15=P6,21,C70158,7 -{Custom control: <70158>}- [Axes.B744] RangeRepeatRate=10 0=0X,256,D,1,0,0,0 -{ DIRECT: Aileron }- 1=0Y,256,D,2,0,0,0 -{ DIRECT: Elevator }- 2=0Z,256,D,4,0,0,0 -{ DIRECT: Throttle }- 3=1Z,256,D,4,0,0,0 -{ DIRECT: Throttle }- 4=2X,256,D,1,0,0,0 -{ DIRECT: Aileron }- 5=2Y,256,D,2,0,0,0 -{ DIRECT: Elevator }- 6=2R,256,D,3,0,0,0 -{ DIRECT: Rudder }- [JoystickCalibration.B744] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No 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 Aileron=-7247,-1401,512,6080 Elevator=-14694,512,665,11656/16 Rudder=-15758,713,713,15496 Throttle=-13208,16256/16 [Profile.B737NGX] 1=Boeing 737-8KN NGX Fly Dubai Winglets V2 [Buttons.B737NGX] 0=R1,6,K113,8 -{Key press: F2}- 1=R2,30,C65721,0 -{BRAKES_RIGHT}- 2=R2,31,C65720,0 -{BRAKES_LEFT}- 3=P6,3,C69991,0 -{Custom control: <69991>}- 4=P6,4,C69991,1 -{Custom control: <69991>}- 5=P6,5,C69991,2 -{Custom control: <69991>}- 6=P6,6,C69991,3 -{Custom control: <69991>}- 7=P6,7,C69992,536870912 -{Custom control: <69992>}- 8=P6,8,C69993,0 -{Custom control: <69993>}- 9=P6,9,C69993,1 -{Custom control: <69993>}- 10=P6,16,C69993,2 -{Custom control: <69993>}- 11=P6,17,C69993,3 -{Custom control: <69993>}- 12=P6,18,C69993,4 -{Custom control: <69993>}- 13=P6,19,C69993,5 -{Custom control: <69993>}- 14=P6,20,C69993,6 -{Custom control: <69993>}- 15=P6,21,C69993,7 -{Custom control: <69993>}- 18=U6,7,C69992,131072 -{Custom control: <69992>}- 19=P6,24,C70008,2147483647 -{Custom control: <70008>}- 20=P6,25,C70008,536870912 -{Custom control: <70008>}- [Axes.B737NGX] RangeRepeatRate=10 0=0X,256,D,1,0,0,0 -{ DIRECT: Aileron }- 1=0Y,256,D,2,0,0,0 -{ DIRECT: Elevator }- 2=0Z,256,D,4,0,0,0 -{ DIRECT: Throttle }- 3=1Z,256,D,4,0,0,0 -{ DIRECT: Throttle }- 4=2X,256,D,1,0,0,0 -{ DIRECT: Aileron }- 5=2Y,256,D,2,0,0,0 -{ DIRECT: Elevator }- 6=2R,256,D,3,0,0,0 -{ DIRECT: Rudder }- [JoystickCalibration.B737NGX] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No 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 Aileron=-16380,-512,512,16380 Elevator=-16383,58,512,16383/16 Rudder=-15758,713,713,15496 Throttle=-13208,16256/16 [MacroFiles] 1=iFly737 2=leveld767 [LuaFiles] 1=ipcReady 2=linda 3=CAR_C90_CD [Traffic Limiter] TrafficLimit=0 AirportPreference=50 GroundPreference=50 NearerPreference=50 PlannedAirportsPreference=50 TargetFrameRate=0 [Profile.B200] 1=Carenado B200 King Air 3 [Keys.B200] 1=112,11,L3:R,0 -{ctl+shft+F1: Press=Lua CAR_C90_CD }- [Window.LUA display] Docked=7354, 2823, 3545, 2451 [Profile.C421] 1=Alabeo C421C N7864M 2=Alabeo C421C N421MN [JoystickCalibration.C421] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No 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 Aileron=-9033,-2530,512,7424 Elevator=-15862,191,512,16283/16 Rudder=-15758,713,713,15496 Throttle=-13184,16253/16 [Monitor] Monitor0=0,024C,4,0 [Profile.F70] 1=Fokker 70 KLM PH-KZO [JoystickCalibration.F70] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No 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 Aileron=-8632,-2322,512,6872 Elevator=-11400,496,512,14822/16 Rudder=-11147,-921,512,8600 Throttle=-13184,16253/16

Thanks for your quick reply. You are right, this happens with any aircraft. I am using two joysticks, one of them has been converted into a throttle quadrant. The problem happens when I move the throttle quadrant. It has never happend before. I have deactivated the controllers in FSX, so it should all be FSUIPC. I have even deleted the axis from the FSX controller menu. And in FSUPIC, the joysticks are of course assigned to different axis each. Best regards, Holger

Dear Peter, I am running FSX with FSUIPC 4.9.7.2. I am experiencing the following: When I start a saved flight with the PMDG 744 QOTSII, as soon as I move the throttles, the aileron moves to a full right deflection and freezes. If I then load another plane, everything is normal. I have deactivated the FSX axis and am only using FSUIPC. Can you help? Best regards, Holger

Do you think it is worthwhile trying LINDA? I installed it yesterday, but I got stock here "LINDA:: ---> ERROR:: Main system config not found! Run GUI and check configs!" I might attempt to solve this, but if LINDA is only a graphical interface for FSUIPC I can probably save myself this trouble? Best, Holger

Interesting comment on the mouse wheel. It makes for fast changes when you use it manually. When you "roll" the mousewheel via flag commands and virtual buttons, it is as slow as the clicks. As if there is a buffer in PMDG which, when filled, only sends one increment while the other input is disregarded - until the buffer is empty again. So Lua goes via FSUIPC? I guess I will have to read up on Lua, then. Somebody must have found a way to send quick value changes to PMDG, however. I guess that otherwise it would be difficult to sell the expensive plug & play MCPs. The whole point of this hardware is to get as real as possible, and that's not the case when you keep your eyes glued at the MCP watching the values change at glacial speed ... I will also write to some manufacturers, let's see what I come back with. Best, Holger

Pete - thanks for your reply. Some findings that might also be of interest for you: - As long as you use the correct number for the custom control and the right parameter within this, it does not matter where your mouse pointer is. A button command will do what it is told. - Holding the mouse button (actually doing this, not by a button command) yields an increase which is much too slow to be practical for sim operations. Using the wheel will get you closer to reality. - I was posting here since I expect that in a PMDG forum everyone will tell me to go the Lua way and to forget about FSUIPC. But FSUIPC for me is still the way to go. I will now post in other fora and come back with what I learn Best, Holger P.S.: Can you positively confirm that values cannot be written directly with PMDG aircraft? Doesn't this make all those expensive plug-&-play MCPs useless?

OK, coming out of the test lab: With generic FSX aircraft, a value would be generated inside EPIC and sent via an offset to FSX. If I understand correctly, PMDG only has readable offsets but no offsets one could write to. I adapted my script - instead of generating values it now sends virtual button pulses. These buttons show up inside FSUIPC. For example, turning the course selector knob to the left will generate a pulse by a virtual button. The button is assigned via FSUIPC to the course selector (custom control 7008), with a respective mouse flag as parameter (I tried clicks and whell up / down - does not seem to make a difference). This works for increments in steps of one. However, my script recognizes the speed a t which a button is turned. With a script that sends values to offsets, these values will increase or decrease exponentially (i.e. first turn notch on the heading knob = +-/1, second = +/-2, third = +/-4 etc.). Eventually, this will stop at +/-30 (the 12th part of a circle). While the button is still turned quickly, every knotch wil generate an increase or decrease of 30 degrees of heading. Once the button is turned slower, the increments will decrease. If you leave it still for the fracion of a second, it will revert to +/-1. I adapted my script so that instead of increasingly higher values it sends multiple pulses. However, it seems that PMDG cannot digest a "fusilade" of button pulses (i.e. a high number of pulses within a unit of time). I had to put a delay of 0.2 seconds between the pulses, so they would be recognized by PMDG. With a smaller spacing than 0.2 s, they would be counted as one pulse, maximum as two. Whether I used the flag for clicks or the wheel did not make a difference. Plus, with a spacing of 0.2 seconds, PMDG would actually receive all pulses but bank them and change the value in the course selector much slower (about 3 increments of 1 within one second). This came as a surprise, as by turning the mouse wheel, you can increase or decrease the values pretty quickly. By mouseclick, you actually cannot. Even if you keep the mouse button pressed, the changes are slow. Unfortunately, this makes it unfeasable to use buttons for selectors such as Heading, Altitude, Speed, Course selectors, VS ... that need high changes in short time. So it seems I am back to my quest of how to send values to PMDG without there being writeable offsets ... If anyone has any advice, please let me know (change of hardware does not count as advice ;-)) I know that Peter is not using PMDG, but maybe someone else has been confronted with the same conundrum. Best, Holger

Thanks so much. This explains a lot. It also provides a workaround for the lack of writeable offsets for all those who are using EPIC. I need some time to experiment with my scripts and then will come back with a description of the workaround. Best, Holger

I just found out something that I cannot explain. But maybe someone here can: I looked at a Lua script (I am not familiar with Lua, I am using EPIC), and I noticed something called "endfunction". So I took the parameters from the Lua script and an On/Off combination for the buttons, and now I have "69992" for the customs control and "536870912" as a parameter when the button is pressed and "131072" when it is released. This works but I have no idea why. For the PMDG 744 I only used a pulse for the button and one parameter ("1"). Can anyone explain to me what I just did? Best, Holger

Hi folks, Who else has trouble with the event "EVT_EFIS_CPT_MODE_CTR" from the 737 NGX SDK? I am sending a joystick pulse to FSUIPC, custom control 69992, parameter 1. This pushes the button, but it remains pushed. I also tried On/Off instead of Pulse, to send the parameter 0 when the button is released, but this will yield two no pushes instead of none. Anyone had the same problem and solved it? Best, Holger

I will check whether it is possible to interface LUA between EPIC and FSX, i.e. EPIC would be talking to LUA like it is to Leeksicon for the LVD763, and LUA would then talk to FSX directly. With my current setup, EPIC talks to EPICINFO5 and EPICINFO5 talks to FSX. Does this make sense to you? Best, Holger

I am still on EPIC, so I would need to modify my EPICINFO5.cfg and maybe also the FSUIPC.ini I know that you are not working on EPICINFO5 anymore, but since it was also working with FSX, I thought I would find some information. Best, Holger

Apologies for not being sufficiently precise. Instead of "issues", I should have written "topic". With "controls" I meant "controls" as in "events" (the five digit numbers). I searched the User Guide and the guide for advanced users. I was hoping to find some examples for how to script. Best regards, Holger

Peter, could you tell me in which document I should be reading up on these issues and what would be a good keyword to look for? I went through the User Guide and the guide for advanced users, looking for anything on "controls", but no success, or I missed it. Best, Holger

Thanks for confirming that I was indeed on the wrong track. I remember events like sending pulses, but can they also send values? I am mainly thinking about the course selector. Best, Holger P.S.: What I like about EPIC is that the values are first generated within EPIC and only then sent to FSX. For example, I have mechanical encoders with only 9 detents, but I "taught" EPIC to read how fast they are turned, and when they are turned quickly, they generate a high value quicker. This is generated within EPIC and only then sent to FSX via EPICINFO5. Very practical. Also, FSX is not overwhelmed by a large number of inputs within a short period of time.

Gents, Is it possible that I am mixing offsets and controls? I have a file called EPICINFO5.CFG that lists all the offsets (four digits) that my hardware us writing to. I have replaced them with the five digit values provided by PMDG. But this is probably a mistake, isn't it? I am also using the Level D 767 where the only thing I had to do to continue using my hardware was to replace the "native" offsets with those that are specific to the 767 and Leeksicon. I imagined this to be the same with the PMDG values. Best, Holger

Thank you, this works. What are you using for ADF1, if I may ask? And for course? Do you send the five digit event value to FSX? I am wondering if FSUIPC and EPIC only accept four digits. Best, Holger

Thanks, I have opened a thread there: http://www.avsim.com/topic/499158-pmdg-ngx-sdkh-and-fsuipc-offsets/ Thanks also for the detail about the radios. The NGX radios are a bit peculiar insofar as it is always the same interface, but you have to chose which radio is being set: http://www.b737.org.uk/communications.htm This is why I suspected that with the offsets you can only turn the knob but not set a specific frequency directly, but let's see about the answers. Best, Holger

Dear Community, I am trying to rewrite an EPIC script that works for the standard FSX planes, sending offsets to control various values. My script is sending the values itself. It does not simply send increments ("turning the knobs"). Looking at the PMDG_NGX_SDK.h, my impression is that the events only "turn knobs", but I have not found events to send values. Only the offsets in the section "MCP direct control seem to send direct values. Is this correct? I am looking for a way to send NAV and COMM radio frequencies to the NGX. Best, Holger

Good to hear, but did you also click on the link? This is what I get: Not Found The requested URL /beta/EPICINFO5_version_4941.zip was not found on this server. Apache/2.4.10 (Debian) Server at fsuipc.simflight.com Port 80