Search the Community

Dear All, Hope you are well. I have a problem with my home cockpit. It incorporates two yokes, both with trim switches as per the real thing. They are connected to TSR Systems (both on prority 0) on a wideclient pc "instrument 2". Inputs are being read by FSUIPC on the FSX "server" pc and I can successfully trim up and down without issue on both yokes. The problem: I cannot make either yoke's input, repeat (even though it is selected in FSUIPC) like the real trim in the real aircraft allowing for smooth trim movements by holding down the yoke switch. For example to trim down by one push on the FOs yoke moves the trim down a step at the moment. I have studied and found that instead of using the FSUIPC dedicated options for trim dw/up you can use offsets. I have used offsets X0BCO and it increases the step size (16383 etc) but the step problem remains. To troubleshoot I thought that the sim could be experiencing conflicts. I removed all Trim selections from FSUIPC and I confirm no FSX controls are active in the FSX GUI. However the trim still moves. So this hypothesis seems to be correct. In the FSUIPC file attached I see buttons that have been configured. I cannot see them in the FSUIPC GUI. So I think they have been added outside the program. Linda? LUA? I don't know. Could you kindly look at the file and advise what the keys translate to? ie. the name? of most importance are the trim keys - I will delete them. If you can help identify more than even better. Just to add, I know by updating these would be annotated. But I am worried updating will loose any configs and or previous programming. If Mr. Thomas Richter is out there, I believe he did a lot of work on this sim in the past. It maybe that he in fact programmed this originally. If you could point me in the right direction as to how to make this work I would be very grateful. Thank you for a great program. KR Nick FSUIPC4.ini

Hi All. I don't know if anyone can shed any light on this. I've set up the following conditional button events to set and re set elevator, aileron and rudder trim. lines 23 to 29 work perfectly well, but lines 20, 21 and 23 are giving trouble. These resets events work once and once only. After that they do nothing until I restart FSX. 17=;***************************************** 18=; Throttle quadrant 19=;***************************************** 20=CP(+3,2)2,1,C65706,0 -{ELEVATOR_TRIM_SET}- 21=CP(+3,2)2,3,C66731,0 -{AILERON_TRIM_SET}- 22=CP(+3,2)2,4,C66721,0 -{GPWS_SWITCH_TOGGLE}- 23=CP(+3,2)2,5,C66732,0 -{RUDDER_TRIM_SET}- 24=CR(-3,2)2,0,C65607,0 -{ELEV_TRIM_DN}- 25=CR(-3,2)2,1,C65615,0 -{ELEV_TRIM_UP}- 26=CR(-3,2)2,2,C66277,0 -{AILERON_TRIM_RIGHT}- 27=CR(-3,2)2,3,C66276,0 -{AILERON_TRIM_LEFT}- 28=CR(-3,2)2,4,C66279,0 -{RUDDER_TRIM_RIGHT}- 29=CR(-3,2)2,5,C66278,0 -{RUDDER_TRIM_LEFT}- I've tried replacing CP with CR, but that seems to make no difference. I've also considered trying to use an offset to do the same thing, but there are several offsets that refer to trim and I'm not certain which one to use. So I would be pleased to hear from anyone who could help. My apologies if this duplicates any previous posts. I've looked but I can't find any. Regards. Pontius.

Hi Pete, this is about the problem of the misalignment of the Saitek trim wheel when disengaging the autopilot. As soon as you move the trim wheel the airplane bounces up or down related to the absolute position of the trim wheel. That is well known to all users of a trim wheel and really miserable. I found in a X-Plane forum an idea which leads imho to a really handy and reasonable workaround to avoid that problem: i wrote a lua to deal with the problem. what it does: in AP mode the trim wheel disconnect from the trim axis in non AP mode the trim wheel connects. in most cases the trim wheel will be physically in the wrong pos in relation to the ac trim axis, so if you move the wheel and he is out of sync, you get a display on the left side of your screen. red if out of sync, green when in sync. both values are visible so you can move the wheel to the correct ac setting. only then the wheel axis connects to the ac trim axis and you can use it. its possible you have to alter some settings due to different screen res. For me this would be a great solution to get rid of the trim wheel problem. Is it possible to realize that in FSX using a LUA? And at least a question to the community: is there anybody who is able to write that LUA and would like to do that? Thanks for your support, Juergen

I am having a strange problems since updating to latest version of FSUIPC with the elevator trim on all my aircraft. As soon as I start my engines during pushback my elevator trim begins erratically moving up and down until I start to taxi and the plane reaches a few knots ground speed at which point the elevator trim corrects itself. Thou it is not a serious bug it was bothering me enough to uninstall FSX and reinstall my 60+ gigs of addons which unfortunately has not fixed anything. I have tried running FSX without my flight yoke. I've updated all addons and drivers. I've spent a few hours browsing support forums and still have not found a solution to my problem. Is there a way to disable auto trim when auto pilot is disconnected? Any suggestions would be greatly appreciated.

Hi Mr Pete Dowson Sir I'm a newbie to FSX and FSUIPC as well. So please bear with me if I have asked you a silly question and not googled hard for a similar question/solution already asked and answered. I have a requirement in which I wanted to read/write Pitch & Elevator Trim executed via lua scripting triggered by a button in a Joystick. I'm new to FSUIPC and hence started browsing example code from your collection of lua scripts ... and slightly modified "Display Vals". The offset document and code example( display vals, liar) is neat and clear when it comes to reading/writing Pitch/Altitude, etc but I could not find any example for reading/writing elevator trim...especially how to convert the value read from offset 0x2EA0. I have a gauge( XML in Panel) displaying ( digital readout ) of Elevator Trim( <String>T:%((A:Elevator Trim Position,degrees))%!2.2f!</String>) and I was trying to verify the data read from offset with the digital read out. My question a) what is the formula to convert value read from offset 0X2EA0 ( so that it would match my reading from gauge) b) if i write ( as per the example code in "Liar" example LUA plug-in for FSUIPC4/ESPIPC only, by Pete Dowson, January 2009) will it reflect really the changes in FS). The reason I'm asking is based on your comment "alter them all to values we want to fool other FSUIPC clients to believe" Need your guidance Thanks very much Regards Janakiraman Swaminathan display vals.txt

My first post: I have FSUIPC4 4.939 (registered) running in P3D 2.5; Saitek yoke, throttle, rudder, and trim fully controlled by FSUIPC (and thank you for that!). My problem exists with or without TRrackIr 5 or ASN add on programs running. When I start P3D for the first time after a PC boot everything works perfectly until I adjust the trim control; once the trim is used I lose all control inputs and FSUIPC not only quits working but is frozen to the point that the program cannot even be modified, nothing can be selected. However, if I exit P3D and restart, everything works perfectly again including the trim. The only difference in the FSUIPC4.log is the following entry in the first run: 1900890 ***** HID USB device reconnected: re-initializing FSUIPC connections The line is gone from the log on the next run. I have changed USB ports and tried resetting the trim settings (after the first run) and the problem persists. I look forward to any suggestions.

Hi Pete, First, thanks for your tremendous work, which allows us to build our home cockpits ! I have a question relative to building a motorized yoke for a Baron58 in a FSX/Win 7 sim. I want to get a "real" trim, i.e move the neutral position of the yoke when I use the trim whell (or when the AP moves it). I am using OpenCocpits SIOC language. I currently have a motorized trim wheel with a multi-turn potentiometer ; when piloting manually, to set the trim, I read the pot, and send its "value" to offset x0BC0. Under AP, I read the offset value, and move the motor so that the pot (and thus the wheel) match the trim value ordered by the AP. This works fine. Now, I would like to move the yoke accordingly. I plan to have 2 pots : 1 on the yoke which normally drives the elevator, and the second to drive the motor which determines the neutral (center) of the yoke in similar way as the wheel. The point is, when I will move this center point, the whole yoke will move, thus changing the yoke potentiometer (elevator) value. So I need, before sending the yoke pot value to the elevator, to substract the center pot value, so that at the new trimmed position, the elevator offset is 0. This way, when I trim the aircraft, I will release the effort on the yoke without moving it, it move the neutral position to match the current yoke position... Under AP, I will use the FS trim value to drive the motor and move the yoke (as I do with the whell), but still with a 0 elevator value)... Hope I am clear ! From my readings of your user documents : I understand that I can use joystick calibration in FSUIPC (currently the yoke works from a cannibalized CH yoke), then use the "Send to FSUIPC offset" option to read this value in a SIOC varaible, then substract the center pot value, and then send it to elevator control input at offset x0BB2. Questions : is that idea correct ? If so, in which offset shall I read the calibrated yoke value send by FSUIPC ? I could not find out... The other choice is to read directly both pots in SIOC, loosing calibration facilities. Would that be better/easier ? Do you see drawbacks on either method ? Or is it possible calibrate adding the two pots (to send the resulting value to to calibration), but inthat case data will not come from a joystick but from SIOC (possibly in a unused offset) ? Of course I plan to do something similar with the ailerons, to have the yoke follow the PA orders... Thanks for the time you will take answering me. Pierre, Saclay, France