Jump to content
The simFlight Network Forums

Search the Community

Showing results for tags 'Saitek'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Product Support Forums
    • FSUIPC Support Pete Dowson Modules
    • MyTraffic Support Forum
    • FeelThere Support Forums
    • FS Commander Support Forum
    • Flying W Simulation
    • AConstable Traffic Sounds Support Forum
    • Fabio Merlo Products Support Forum
    • Elite-Air Studio Support Forum
    • Nikola Jovanovic Support Forum
    • Intrasystems Support Forum
    • Taburet & DanVFR Support Forum
    • Environ Scenery
  • simFlight DE
  • simRussia


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







  1. Hi, I've found this topic about Saitek Switch Panel Leds : http://forum.simflight.com/topic/71786-programming-of-the-saitek-pro-flight-panels-with-fsuipc-and-lua/ Indeed, i'm looking for explanations or samples about this command : com.writefeature(dev, s, wrf) The goal of my request is to switch on (red or green) leds on Saitek Switch Panel. May someone help me ? Best regards, Oliver.
  2. Good evening Pete, I have just had to re-load Windows 7, and thus ALL my FSX Program, add-on aircraft and add-on scenery. Don't feel sorry for me - it was all my fault! :oops: However (there had to be a 'however'!) on flying the FSX Beech Baron I thought the pitch response was mighty sensitive, one might say fierce. I tried altering the response slope via the FSUIPC calibration page and it did not seem to make much difference. I then 'flew' the Carenado Beech Baron BE58, and lo and behold I had the same problem. On accessing the pitch calibration page I noticed an anomaly. When moving the yoke forwards the response varied according to the slope set, and reached the maximum set number of about 16,400 at full yoke movement. However, when pulling the yoke backwards the response was far more rapid, and reached the similar maximum set number of about 16,400 after only one third of the yoke movement from neutral to maximum. This reflected exactly what the pitch response was when 'flying' the simulated aircraft. I suspect this means there is a problem with the sensors inside my Saitek Pro yoke, but I would be grateful if you could give your opinion. If indeed this is the problem, do you know if there some way I could fix it by opening up the yoke black box and cleaning contacts/pitch pots or whtever may be causing the problem? :(
  3. All, I have purchased a few Saitek products with no issue. However I have an issue with my latest purchase, the yoke and throttle quadrant. The yoke seems to work fine, but the throttle quadrant (prop and mix also) goes from 0 to 16k with no range in between. I deleted all my joystick and axes assignments in FSX, but this issue remains. The calibration in Windows works perfectly with full range of motion. I'm really stumped on this one. Can anyone provide some input as to how I can fix this?
  4. Introduction This post explains how you can use a LUA routine to access the status of the buttons/switches/selectors/gear and flaps lever and trim wheel (herewith named collectively as Buttons) on 3 Saitek panels using FSUIPC and Linda. The first section presents a quick instruction to start gathering information based on lua program attached to this post. The second section gives a simple example of a Lua program that access the Saitek panel buttons status and select specific FSX/P3D actions accordingly. The third section goes more into the details about how this LUA programs was made. You need a registered version of FSUIPC for this to work. Section 1 – Quick Start Download and install the relevant LUA routines; Attached to this post are 3 Lua programs corresponding to the 3 Saitek panels. You just need to install the ones corresponding to the panel you own. The 3 Lua programs are: - HIDRadio.lua - HIDMulti.lua - HIDSwitch.lua Note; I have renamed the 3 programs with a .txt exension for upload as the system doesnt allow to upload .lua files. You will need to change the extension back to .lua before using them. To install them, just drop the ones corresponding to the panel you own into the “module” directory of FSX/P3D. Automatic start of the LUA programs The LUA programs selected above must run in permanence to scan the status of the buttons and map (copy) this information into specific address of the FSUIPC offsets. To inform FSUIPC that those programs must start and run continuously, it is necessary to add the following lines to the FSUIPC.ini files (located in the module directory of FSX/P3D). [Auto] 1=lua HIDRadio 2=lua HIDMulti 3=lua HIDSwitch On the next start-up of FSUIPC, the Lua program will start to scan the status of the buttons and selector on Saitek panels. Checking with FSUIPC logging facility that the Lua programs are in place and operating FSUIPC has a built in logging facility that can be useful to check the proper operation of the Lua programs and the correct mapping of switches to the offset address. Go to the FSUIPC Logging tab and on the right part of the screen, enter the following information: Offset Type of data Remark 3358 U32 Saitek Radio panel offset address 335C U32 Saitek Multi Panel offset address 3360 U32 Saitek Switches Panel offset address Then click on “FS window” and you should have a green message on the top left of your screen. Move some selectors or push buttons on each of your panels and see if the values on screen change according to the position of the buttons. An annex at the end of this post gives the value of each button. Note1 : The knob just send a short pulse so the number on screen will just change very rapidly and come back to the value prior to moving the knob when you stop moving it. Note 2: The buttons just change status while they are pressed, they doesn’t indicate the status of the corresponding function. Ex: the Autopilot button will just send a ON status when you press the button. So this is not intended to test if functions like the AP are engaged or not. It’s just to test the instantaneous position of the hardware buttons. Make sure you have version 4.934 as the previous one has a problem that killed lua programs on start-up and caused me a couple of evening of head scratching... 4.934 solved this as soon as I installed it. Accessing the information from within a LUA program in Linda Now everything is in place and you have the possibility to access the information on your panel switch. For simple assignation of a single button, you usually doesn’t need complex programming as FSX, Spad or Linda menu all allow you to directly select FSX/P3D commands. On the other hand, if you want to combine the status from different buttons to trigger a specific FSX/P3D action, then you need to use a Lua program (you can also use FSUIPC conditional button programming but Lua is more flexible). Using Linda, it is possible to assign user created Lua program to a button so the program is called when the button is push (or a switch is move to the “on” position or a selector is put in a specific position). The Lua program allows you to test the status of others buttons and makes your program act accordingly to send the proper FSX/P3D command. In Linda, you can create individual LUA program module (a module can contain several Lua program) for each aircraft. Linda includes also a text editor that makes creation of Lua program easy. Some functions in the Lua library allow reading specific address in FSUIPC offsets. Each address that will be assigned to the 3 Saitek panels covered here will contain between 18 to 20 bits of useful information (not considering the LED display) that correspond to all the buttons, switches, selectors and gear and flaps lever of the panel. The switches panel for instance contains 20 bits of information that you can test. The address to use in order to read each panel information are: 0x3358 = Radio panel 0x335C = Multi panel 0x3360 = Switch panel Note : You can assign other address if those one are already used for other purposed on your setup. You will need to modify the HIDxxx.lua program that correspond to the device you want to change. Note: The "0x" in the adress above just means that its written in hexadecimal notation. You will need to include the 0x within Lua program otherwise it will consider that the address provided is decimal. Please note that in the FSUIPC logging page, you don’t need to include the 0x as this page always consider that the value entered is hexadecimal. There are two main functions within Lua programs that can help you to read buttons status. First, the following Lua program line read all the bytes of information from the Saitek Radio panel and put it in a variable named “pos”. pos = ipc.readUB(0x3358) But the value returned is not quite useful by itself as it represents the cumulative sum of all the individual bits for switches that are in the “on” position resulting in a large number of possible values. You then need to isolate the value that you are specifically interested by using the following function (here represented in a separate line). pos = logic.And(pos,mask). Here mask correspond to the specific value (or sum of values) you are interested in. For instance, if you are interested to test if the position of the magneto switch is at the “right” position on the Saitek switch panel, then the value for the mask is 32768 (see annex for all possible values) and the Lua program line becomes Pos = logic.And(pos,32768) Section 2 : Example for the Duke piston or Douglas C-47 Magneto selector In the Duke Piston from Real air (and Douglas C-47 from Manfred Jahn), the magneto animation in the VC are reversed compared to the Saitek switch magneto button for the “left” and “right” position which create a weird jump in the VC while you move the magneto selector on your Saitek panel. - Duke Piston/Douglas C-47 VC magneto selector order: Off – Left – Right – Both – Start - Saitek Switch panel magneto selector order: Off – Right – Left – Both - Start So the objective is to program a function in a Linda module that will reverse the operation of the left and right magneto position between the Saitek panel and the VC. In addition, we want to test the position of the upper mode button for the Saitek radio panel to determine if we want to operate the motor 1 or 2. Spad has a built-in functionality that allows using several switches (ex: Aternator, fuel pump, cowl, de ice) to act on motor 1 or on motor 2 according to the position of the top selector on the Radio panel and we want to replicate this functionality here. First you need to create a module for your targeted aircraft if it’s not already existing. See Linda documentation to do this. Then you need to copy the following program (or use the Magneto.txt file provided) into the aircraft module using Linda editor screen. Again, refer to Linda documentation to see how to open the editor. The title between double hash characters is recognized by Linda as a heading separator for functions. It makes easier to identify function you have created. Comments (text preceded by --) in the program below provide detailed comments for each steps. -- ## Magneto ## Function MagLeftVC () -- This function handle the reversal of the magneto in the VC panel compared to the Saitek selector. -- It is activated when the selector on the Saitek switch panel will be put at the left position. -- It will result in positionning the VC magneto selector to the "right" position. -- The Saitek Radio top left selector at position COM1 means that the left engine is considered. If the selector is at the COM2 position, then the right engine will be treated. -- The information about the radio panel status is at offset 0x3358 -- reading the offset to get all Radio panel switches current status pos = ipc.readUB(0x3358) -- The next line of lua code will isolate the bits of information we are interested in -- mask = 1 would be usefull ot test if the top left selector at the COM1 position -- mask = 2 would be appropriate to test if the top left selector at the COM2 position -- Mask = 3 accept both COM1 and COM2 and will return either 1 or 2 as the selector -- can be only in one of the two positions at a given time. -- If the selector is not at COM1 or COM2, then the logic.And function will return zero and no action will be done. pos = logic.And(pos,3) -- the next group of lines will send the command to put the magneto for left or right motor in the right position in the VC. -- 66400 is the Magneto1_set command for FSX/P3D -- 66401 is the Magneto2_set command for FSX/P3D -- The parameter 2 is for the “right” position of the magneto if pos ==1 then ipc.control(66400,2) else if pos ==2 then ipc.control(66401,2) end end Function MagRightVC () -- same approach as for the left mag function, without comments here pos = ipc.readUB(0x3358) pos = logic.And(pos,3) if pos ==1 then ipc.control(66400,1) elseif pos ==2 then ipc.control(66401,1) end end Section 3 – Nut and Bolts. This section provides some additional explanation on how the HIDRadio.lua program was created from the HIDDemo.lua program provided by Peter. Step 1: Obtain HIDDemo.lua We need to have a Lua program running continuously to scan the Saitek panel switch status then map this information in FSUIPC offset. The offset can then be read from a Lua program in a Linda module for an aircraft. Peter Dowson provided an example of a Lua program that scan HID device like the Saitek panels and write the information on offset. We just want to use his demo and modify it a bit. The HidDemo.lua program is available in the complete install of FSUIPC4. Or you can download the latest HidDemo.lua example from : http://forum.simflight.com/topic/68257-latest-lua-package-for-fsuipc-and-wideclient/ Step 2: Create HIDRadio.lua Make a copy of HIDDemo.lua and name it HIDRadio.lua (we will give only one example herewith but the same approach works for the switch and the multi panel also). Step 3 – Adjust HID device identification At the beginning of the HIDDemo.lua program, there is two lines that identify the Saitek panel (HID device) you want to communicate with. You have to insert the hexadecimal code for the vendor and for the product. For instance the lines for the Saitek radio panel are: -- Saitek Radio panel Vendor = 0x06A3 Product = 0x0D05 If you dont know the HID device codes, there is a utility provided by Peter Dowson called HIDscanner.exe that gives a report about all devices connected to your PC and their vendor rand product codes. I already run this utility to find the relevant information of the 3 following Saitek Products. Radio Panel : Vendor = 0x06A3 Product = 0x0D05 Multi Panel : Vendor =0x06A3 Product = 0x0D06 Switch Panel : Vendor =0x06A3 Product = 0x0D67 The HIDScanner.exe utility is available at the same link provided above on Peter support page. Step 4 : Change the size and destination of information blocks In HIDDemo.exe, you will find a loop of instruction toward the end of the program that read the status of the buttons on your HID device and copy it to a specific offset. The loop is initially programmed for reading 8 blocks composed of 4 Bytes of information. For the Saitek panel switches, you only need to do it once as all information fit into a double world (32 bits of information). So I cleaned the iteration loop (from 1 to 8 and adjusted the HIDDemo.lua program to do a single read of a 32 bits of information that is sufficient for the Saitek panels. Next, you need to select the destination for the button information in the FSUIPC offset table. There is an ipc.writeUD instruction in the HIDDemo.lua program that was modified to correspond to an offset that was used for mapping. The possible offset for the 9 contiguous blocks of 4 bytes (32 bits of information) are: 0x3340, 0x3344, 0x3348, 0x334C, 0x3350, 0x3354, 0x3358, 0x335C, 0x3360. See the “FSUIPC4 Offset Status.pdf” document provided with FSUIPC documentation. The Saitek version of HIDDemo.lua use the 3 last virtual joystick addresses so Joystick 71,72 and 73 located at 0x3358, 0x335C and 0x3360 respectively. Step 5 : Install your newly created Lua program Just copy them it in the “module” directory of FSX or P3D. If you have started with the quick start portion of this document, you have already done this. Step 6 : Automatic startup of HIDRadio.lua To start automatically your Lua program add the following lines in FSUIPC.ini. If you have applied the quick start instruction, its already done. [Auto] 1=lua HidRadio Step 7 : Create custom lua program See the example provided for the Duke above. Annex: Saitek panels reference of “buttons” value Saitek Radio Panel (20 bit of information + 2 bit unused) Top left mode selector 1= Com1 2= Com2 4= Nav1 8= Nav2 16= Adf 32= Dme 64= Xpdr Bottom Left mode selector 128= Com1 256= Com2 512= Nav1 1024= Nav2 2048= Adf 4096= Dme 8192= Xpdr 16384 = Top right ACT/STB button 32768 = Bottom right ACT/STB button 65536 = Clockwise turn of the top knob 131072 (2E17)=Counter-clockwise turn of the top knob 1048576 (2E20) = Clockwise turn of the bottom knob 2097152 (2E21) = Counter-clockwise turn of the bottom knob Saitek Multi Panel (20 bit of information) Selector button 1= Alt 2= VS 4= IAS 8=HDG 16=CRS 32= Clockwise rotation of knob 64= Counter clockwise rotation of knob 128= AP button 256= HDG button 512= NAV button 1024= IAS button 2048= ALT button 4096= VS button 8192= APR button 16384= REV button 32768= Auto Throttle switch ON 65536= Flaps up (2^16) 131072= Flaps down (2^17) 262144= Elevator Trim Pitch up (2^18) 524288= Elevator Trim Pitch Down (2^19) Saitek Switch panel (20 bit of information) Note: The minimum value returned corresponds to the position of the landing gear handle plus the position of the magneto knob. 262144 is returned if the gear lever is UP and 524288 if the gear lever is DOWN. 1= Battery 2= Alternator 4= Avionic 8= Pump 16= De Ice 32= Pitot heat 64= Cowl 128= Panel 256= Beacon 512= Nav 1024= Strobe 2048= Taxi 4096= Landing Magneto selector 8192= Off magneto 16384= Left Magneto 32768= Right Magneto 65536= Both Magneto 131072= Start Magneto Landing gear lever 262144= Landing gear Up 524288 (2E19)= Landing Gear Down Magneto.txt HidMulti.txt HidRadio.txt HidSwitch.txt
  5. I need help! recently purchased FSUIPC. can anyone explain in easy steps on how to program. using FSUIPC, I have watched video's but I still do not understand, what I must do. I also have read the manual which is provided with the software.. still no wiser :oops: I use a saitek pro yoke and rudder pedals, The pedals are working fine. If I can just program the yoke so I can turn/bank left and right, that would be good I tried to use the Axis settings, when I apply the configuration and return FSX, no nothing happens, when I turn the yoke to the left or right in the simulator. If I enable the controller in FSX .the control yoke in the simulator moves by itself hard over to the left, it then begins to shake and then moves hard right,.and then randomly back to the left and then right and drives me crazy, I have not touched anything the yoke is in the normal horizontal position. Has anyone experienced this before, and how did you fix it.
  6. I have no doubt that this is not an FSUIPC4 v 4.927a problem but maybe you could point me in the right direction. I have been attempting to load FSX/wAcc in my new 8.1 build for days now. I have sorted thru everything, I thought, until this problem popped up. I am using 23 Saitek devices and all but the Flight Information Panels (FIP's) were finally up and running today without problems, believe me this was a challenge. If I load the FIP panels which calls this section of the exe.xml file, and will not run without it, <Launch.Addon> <Name>Saitek DirectOutput RadioStack</Name> <Disabled>False</Disabled> <Path>C:\Program Files (x86)\Saitek\DirectOutput\SaiFlightSimX.exe</Path> <CommandLine>-run</CommandLine> </Launch.Addon> the panels load and run just fine until there is any little hiccup in the system. By that I mean if one of the FIP's needs to reload for some reason it locks up FSUIPC and my controls. If I open FSUIPC it will not find any devices. And, when I exit FSX I find that the Enable Joysticks, which had been showing JOYSTICKS=0 in the FSX.cfg is now missing and FSX loads with it enabled? As I said, it ran fine unitil I started trying to install the FIP's which calls the Saitek program. As long as the FIP's are loaded prior to selecting a flight , they work perfectly; if loaded after the flight is loaded, I have the described problem. Here is my INI and Log files: FSUIPC4.ini [General] UpdatedByVersion=4927a History=OFT90BO8YW4BZE3PLZRCC InitDelayDevicesToo=No InterceptTextMenu=Yes UseSystemTime=No UseMidMouseBtn=Yes MouseWheelMove=No MouseWheelTrim=No MouseWheelTrimSpeed=1 JoystickTimeout=20 PollGFTQ6=Yes BlankDisplays=No FixControlAccel=No FixMachSpeedBug=No DeleteVehiclesForAES=Yes 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 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 WeatherReadFactor=2 WeatherRewriteSeconds=1 CustomWeatherModify=No SimConnectStallTime=1 LuaRerunDelay=66 Console=No FSVersionUsed="Microsoft Flight Simulator X",10.0.61637.0 SimConnectUsed=10.0.61259.0 [JoyNames] AutoAssignLetters=No 1=Saitek Pro Flight Rudder Pedals 1.GUID={51FE9810-6C06-11E3-8004-444553540000} 2=Saitek Pro Flight Yoke 2.GUID={7D242AE0-6C07-11E3-8008-444553540000} 3=Saitek Pro Flight Throttle Quadrant 3.GUID={48BF94A0-6C08-11E3-8009-444553540000} 0=Saitek Pro Flight Cessna Trim Wheel 0.GUID={51F82F70-6C06-11E3-8002-444553540000} [buttons] ButtonRepeat=20,10 [AutoSave] Next=1 Interval=60 Files=10 SaveOnGround=No AutoSaveEnabled=No [GPSout] GPSoutEnabled=No [GPSout2] GPSoutEnabled=No [WideServer] WideFSenabled=Yes AdvertiseService=1 Port=8002 Port2=9002 [sounds] Path=D:\FSX\Sound\ Device1=Primary Sound Driver Device2=Speakers (2- High Definition Audio Device) Device3=Digital Audio (S/PDIF) (2- High Definition Audio Device) Device4=Digital Audio (S/PDIF) (2- High Definition Audio Device) [Axes] RangeRepeatRate=10 0=0X,256,D,21,0,0,0 1=1X,256,D,7,0,0,0 2=1Y,256,D,8,0,0,0 3=1R,256,D,3,0,0,0 4=2X,256,D,1,0,0,0 5=2Y,256,D,2,0,0,0 6=2Z,1,D,4,0,0,0 7=2U,256,D,5,0,0,0 8=2V,256,D,6,0,0,0 [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 Aileron=-16380,-512,512,16380 LeftBrake=-16380,16380/16 RightBrake=0,16380/16 ElevatorTrim=-16380,128,128,16380/16 Throttle=-16380,16380/8 Elevator=-16380,-512,512,16380 Rudder=-16380,-512,512,16380 PropPitch=-16380,16380 Mixture=-16380,16380 [Programs] RunIf1=Ready,D:\spad\spad.exe FSUIPC4.log ********* FSUIPC4, Version 4.927a by Pete Dowson ********* Running inside FSX on Windows 8 Module base=6F610000 User Name="Rick Sheehan" User Addr="ricks@datacruz.com" FSUIPC4 Key is provided WideFS7 Key is provided 15 System time = 10/01/2014 13:52:39 31 FLT UNC path = "\\RICKS4600\Users\Rick S\Documents\Flight Simulator X Files\" 531 Trying to connect to SimConnect Acc/SP2 Oct07 ... 531 FS UNC path = "D:\FSX\" 796 LogOptions=00000000 00000001 796 SIM1 Frictions access gained 796 Wind smoothing fix is fully installed 796 G3D.DLL fix attempt installed ok 796 SimConnect intercept for texts and menus installed ok 796 SimConnect_Open succeeded: waiting to check version okay 796 Trying to use SimConnect Acc/SP2 Oct07 3218 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 3218 Initialising SimConnect data requests now 3218 FSUIPC Menu entry added 3265 \\RICKS4600\Users\Rick S\Documents\Flight Simulator X Files\172spG100.FLT 3265 D:\FSX\SimObjects\Airplanes\C172\Cessna172SP.AIR 16937 ***** HID USB device reconnected: re-initialising FSUIPC connections 16953 ***** HID USB device reconnected: re-initialising FSUIPC connections 17093 ***** HID USB device reconnected: re-initialising FSUIPC connections 17265 ***** HID USB device reconnected: re-initialising FSUIPC connections 17421 ***** HID USB device reconnected: re-initialising FSUIPC connections 17593 ***** HID USB device reconnected: re-initialising FSUIPC connections 21453 ***** HID USB device reconnected: re-initialising FSUIPC connections 21609 ***** HID USB device reconnected: re-initialising FSUIPC connections 21781 ***** HID USB device reconnected: re-initialising FSUIPC connections 21921 ***** HID USB device reconnected: re-initialising FSUIPC connections 22093 ***** HID USB device reconnected: re-initialising FSUIPC connections 22234 ***** HID USB device reconnected: re-initialising FSUIPC connections 94984 Aircraft="Cessna Skyhawk 172SP G1000" 94984 System time = 10/01/2014 13:54:14, Simulator time = 13:52:42 (21:52Z) 104421 Starting everything now ... 104468 Run: "D:\spad\spad.exe" 105625 Advanced Weather Interface Enabled 150093 Sim stopped: average frame rate for last 50 secs = 29.3 fps 655562 ***** HID USB device reconnected: re-initialising FSUIPC connections 655562 ***** HID USB device reconnected: re-initialising FSUIPC connections 655687 ***** HID USB device reconnected: re-initialising FSUIPC connections 655875 ***** HID USB device reconnected: re-initialising FSUIPC connections 656031 ***** HID USB device reconnected: re-initialising FSUIPC connections 656218 ***** HID USB device reconnected: re-initialising FSUIPC connections 706859 ***** HID USB device reconnected: re-initialising FSUIPC connections 706859 ***** HID USB device reconnected: re-initialising FSUIPC connections 707046 ***** HID USB device reconnected: re-initialising FSUIPC connections 707203 ***** HID USB device reconnected: re-initialising FSUIPC connections 707343 ***** HID USB device reconnected: re-initialising FSUIPC connections 707531 ***** HID USB device reconnected: re-initialising FSUIPC connections 710421 ***** HID USB device reconnected: re-initialising FSUIPC connections 710562 ***** HID USB device reconnected: re-initialising FSUIPC connections 710734 ***** HID USB device reconnected: re-initialising FSUIPC connections 710875 ***** HID USB device reconnected: re-initialising FSUIPC connections 711046 ***** HID USB device reconnected: re-initialising FSUIPC connections 711203 ***** HID USB device reconnected: re-initialising FSUIPC connections 730984 Sim stopped: average frame rate for last 578 secs = 27.5 fps 734812 Weather Mode now = Theme 734812 \\RICKS4600\Users\Rick S\AppData\Roaming\Microsoft\FSX\Previous flight.FLT 755546 System time = 10/01/2014 14:05:15, Simulator time = 14:03:10 (22:03Z) 755546 *** FSUIPC log file being closed Average frame rate for running time of 628 secs = 27.6 fps G3D fix: Passes 26041, Null pointers 0, Bad pointers 0, Separate instances 0 Memory managed: 293 Allocs, 293 Freed ********* FSUIPC Log file closed *********** Could you please point me in a direction? Thanks Rick S.
  7. Mr Dowson. I have a cockpit at home and bought SAITEK products. One of the products is the Throttle Quadrant. I bought two, so I have to use 6 thrust levers. The problem is not that I'm able to calibrate the thrust levers. When I set the Axis Assignment levers show the range -16384 to 0 and then jump unexpectedly to 16383. This happens with four thrust levers, two of the a Throttle Quadrant and two with each other. Thus thrust levers do not work propely. If you prefer, I made two short videos (19s) to demonstrate what is happening. The links are: I appreciate your help and patience. Gallo
  8. I am experiencing a slightly strange situation and I'm not sure what has caused it. I have a simple cockpit setup including a yoke, pedals, multi-panel, radio panel, switch panel and an additional USB throttle quadrant (All of the Saitek Pro-Flight variety). I am also running FS9 with the latest compatible version of FSUIPC (registered) on a Win-7 64-bit machine. I have had to disconnect my USB throttle quadrant because it somehow triggers the "Pan view up" control continuously. I have run the calibration on all the peripherals and all axes/buttons seem to be responding properly (albeit with some spikes) but none of them are "stuck". I have also cleared all the button and axis assignments in both FSUIPC and FS9 and reassigned them. The only thing I have been able to narrow down is that the problem only occurs if the throttle quadrant is plugged in, regardless of where it is plugged in (USB hub, directly to the PC or to the USB plugs on the yoke). Could you give me some troubleshooting ideas to narrow down what is triggering the control input or another way to address it? I am completely at a loss here. I wish I had another throttle quadrant to plug in so I can rule out bad hardware, but unfortunately I don't. Any help will be greatly appreciated!
  9. Hi all, I am looking to enlist the aid from anyone who can help. I am seeing strange things with my rudder pedals. When I run FSX after a while (and sometimes on inital startup) the rudder starts acting crazy going back and forth rapidly. Originally I had CH pedals installed and saw the issue. Figuring my pedals were old and wanting a reason to upgrade I bought the new Saitek Cessna pedals. Unfortunatly I still have the same issue. I am currently running FSUIPC Ver 4.92 and have setup my pedals thru there (yes I ensured I disabled all joysticks in FSX). Went thru the setup and cal for all my stuff including the pedals yet I still have the issue. Whats really strange is the issue also shows up in FSUIPC itself . I see the rudder pedals changing rapidly on the numbers in both directions(-16000 to + 16000). I try to rescan but cant. My only fix right now is to reboot the PC when this happens and then I am good for a while. Any suggestions would be very helpful. Also if you need additional info to help me troubleshoot let me know. Thanks. Mike
  10. Hello, :razz: I am having problems with my Saitek throttle quadrants ; the throttle levers are not synchronised at the same positions. For Example, I could have them In the exact same position (physically) on the quadrant, but on the simulator I get different output, It may only be 3-4% of a difference in throttle but asymmetrical thrust Is actually quite a problem in the simulator. The two throttle levers that aren't synchronised are both on the same quadrant which makes it even more strange :???: . I have FSUIPC installed and I have tried mapping the throttle controls into there to see if It makes a difference, but it remains the same. If someone has a workaround for this in FSUIPC to calibrate the throttle positions to be the same I would be very appreciative if you could help me, Thanks in advance! Kriss
  11. I have installed FSUIPC 4.852 into my FSX installation, which includes several bits of hardware including a Saitek Pro Flight Multi Panel. Unfortunately all is not well with this installation. In essence, without FSUIPC installed (e.g. rename .DLL to .DLX) the system works perfectly as expected. However with the system installed, the Multi Panel does not behave as expected. For example if I press the AP button to engage the autopilot, some random action occurs such as the Vertical Speed autopilot being selected. If I then press AP again, some other lights will come on. Basically it makes the entire Multi Panel unusable. If I click on the graphics of the autopilot on the screen however, the correct commands occur i.e. click on AP and the autopilot engages. (Interestingly the Saitek mirrors this OK.) However if I then press the now lit AP button on the Multi Panel, some new random thing will happen such as the IAS will set to some random value. So as things are at the moment, if I wish to fly using an autopilot, I have to disconnect FSUIPC. Does anyone have a fix for this? What additional information can I provide? Thanks!
  12. The Saitek Pro Flight Switch, Radio and Multi Panels can be accessed directly from FSUIPC and with the lua com library. Start with the HidDemo.lua and open the HID interface to the panels just as with a joystick. Vendor and product names can be retrieved with HIDScanner. Note that the switch panel has "HOLTEK" as Vendor/Manufacturer. Switch Panel For the Switch panel one 32-bit word is retrieved by com.read containing all the switches (incl. the rotary starter button). Adressing the LEDs works by sending a two-by string by com.writefeature(dev, s, wrf). The first byte must be char(0), the second byte contains a char which represents binary numerical representation of the LED-states: 0 b X X R1 R2 R3 G1 G2 G3 X stands for "ignored", R1 is the top, R2 bottom left, R3 bottom right LED, all in red, G1-3 the same in green. I.e. if you want turn on all LEDs in green then the character code is 0b00000111 or 7d (decimal). You can also turn on green and red at the same time by sending 0b00111111 (or 63d) to the feature data. Multi Panel It works similar for the Multi-Panel. Again, com.read retrieves all the button states. It has to be noticed that the trim wheel and the rotary button generates only short pulses in two individual bits each, indicating the turn direction. Not to miss relevant events by the proposed polling routine in HidDemo and also not to overload the lua-engine, I recommend to use at the begin of the polling routine this: while com.test(dev) >= 10*rd do CurrentData, n = com.read(dev, rd) End CurrentData, n = com.read(dev, rd) ... [/CODE] This discards effectively all but the last 10 button events and thus will provide enough rotary events to adjust trim and autopilot effectively, without having to much momentum effect after turning the knobs. Setting the display of the Multi-Panel works similar as with the Switch panel. Now the data string to the panel contains 13 bytes, which might be created like this: string.char(0, a1,a2,a3,a4,a5,b1,b2,b3,b4,b5,x) Again the first character must be a zero, then five characters follow for the first display line, and another five characters for the second display line. The last byte seems to be ingored. The displayed digit is the same as the character code. Character codes from 10-13 result in a blank position. In the second line character code 14 results in a "-". If all positions are filled with character code 15, the display is turned off. The display labels are not programmable, instead depend on the position of the mode selector switch (which is also mapped as a set of buttons). Also, when displaying courses, only the last three digits of the first line are shown. However the format of the writ string remains the same (i.e. only a3-a5 are shown on the panel). [b]Radio Panel[/b] As with the previous, the rotary, mode selector, and ACT/STBY buttons are mapped to buttons in the HID input section. Addressing the digital displays works similar as with the Multi-Panel by writing a string to the feature data. In this case the string contains 23 characters. As before, the first character code must be 0, then 20 characters follow containing the 5 digits each of the four displays. The last two characters seem to be ignored again: string.char(0,a1,a2,a3,a4,a5,b1,b2,b3,b4,b5,c1,c2,c3,c4,c5,d1,d2,d3,d4,d5,X,X) Again the first character code has to be zero, the next five codes show the upper left display, then upper right and so forth. Character codes are converted to the display as follows: [CODE]Code Display 0-9 0-9 10-15 <blank> This repeats in modulo 16 until a character code of 207. 208-217 0.-9. (decimal dot set) 218-223 . 224-239 - 240-248 0-9 250-255 <blank> [/CODE] [b]Annunciator Panel[/b] I don't have it, so I can't test it, but I'd expect it works the same way. [b]Finally[/b] Forgive me not to provide all the individual button mappings, I simply verified that it works this way and used the rotaries to dial through all possible codes at the digit positions, for finding out what they do. However, up to now I have now idea, what the effect is in writing other codes than "0" in the first byte (other than that the panel does not seem to accept anything), or in the ignored positions at the end of the string. Furthermore, the Multi-Panel has altogether two features caps, and I have no idea what the "second" means. Anyway, I know there a number of people interested in programming the Saitek Panels directly and this may help.
  13. After long time reseaching why my FSX freeze (sound still play but screen freeze) i know that lates FSUIPC not compactible with SPAD driver. If fly with default aircraft, SPAD working in default FSUIPC mode no problem. When using SPAD as virtual Joystick, it make random Freeze and i need to kill FSX manual. Turnoff all Saitek Panels (radio, switch ..etc..) remove SPAD, all fine work. I fly with PMDG 737, iFly, LEVELD ... all the same result. Still no solution to solve problem. Any one can help. ================================== My System: PC1: HP z-400 Q.Core W3530 2.8Ghz ATI HD Radeon 6970 x 2 (Crossfire Enabled) 16Gb ECC RAM (HP Original RAM for HPZ400) 3x 32 inches LED LCD Vrinsight MCP Combo II + Linda lates vertion Saitek: Yoke + Quadriant + FIP+ Radio Panel+Switch Panel+AP panels+rudder Windows 7 x64 Ultimate Main FSX running with GEX, FS Global 2010 some airports scenary. PC2: HP-Touchsmart 610 Core i7 2600 3.4Ghz 8Gb RAM Touch screen 23 inches. + USB to VGA Adapter Windows 7 x64 Home Running WideClient + FS Commande 9 + GA Panels
  • 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.