jdriskell

Just an update. I removed the old quad and plugged the new one in. I didn't have to edit the .ini file. FSUIPC recognized all the button assignments but I had to re-calibrate the throttle axes. The new values are equal and smooth so dealing with worn potentiometer values is a problem of the past. But I got 18 years service out of the old CH Throttle Quad. Jim Driskell

Hi John, Thanks for the quick reply. Your suggestions verify what I had thought so I'll give it a try. As usual, your support is par excellence. Jim Driskell

Hi John, The mid-value is read when the throttle lever is at the neutral detente on CH Quad before its either advanced or reversed. The third lever's values are inconsistent with the other lever's values. Some my sim aircraft use direct inputs so the inconsistencies can be a problem. Additionally, the reverse thrust position on the throttle levers doesn't always work because I think thee is some dead areas in resistance when I move the throttle lever to reverse. I could replace all the potentiometers but that's a lot of work. So, I bought a new CH Throttle Quad. Since my old and new quads are the same, can I simply unplug the old quad and plug the new one in. I would reboot my machine, then remove the old one, reboot again to clear the assignments, the shut down an plug in the new quad and reboot. Will FSUIPC recognize the new one and accept the existing axes and button assignments? I've always labeled my CH controllers alphabetically after they have been discovered so I'm hoping to save some work. Of course, I'll re calibrate those axes on the Quad to take advantage of the new potentiometer values. Thanks for the advice, Jim Driskell

I've been using the same CH throttle Quad and controlling it using FSUIPC for about 18 years. Both have served me faithfully thru the various versions of Microsoft Flight Simulator . But lately I think the potentiometer values in the Quad have changed enough that it's becoming difficult to calibrate. Currently I run MSFS2020 with FSUIPC controlling my CH Yoke, Pedals and Quad. Here are the values FSUIPC sees on the 6 throttle levers:             Max   Mid   Min Lever 1     14847 10663 -16384      Lever 2     14719 11313 -16254 Lever 3     15487  9232 -15604 Lever 4     14335 11313 -16384 Lever 5     14591 11053 -16254 Lever 6     14591 10272 -16384 With the exception of #3, the levers seem consistent. However, I would think the Max values would come closer to the Min values if the Pots weren't so worn. I can calibrate the various axes but the control between chosen levers isn't consistent. Should I expect more consistent values in a new quad? I'm thinking it's about time for a new one. Please advise. Jim Driskell

Again thanks for jumping on the stoppage problem. I noticed it but when I saw the mention of problem on the forum I got the fix. Good work, Jim Driskell

A brief note to thank your and Pete for your wonderful FSUIPC product. I've been using it for about 20 years and have found it superior for controlling my aged CH products. They are still working in spite of their aging POTS while FSUIPC irons out the bumps and jerks of the old systems. Keep up the good work! Jim Driskell

Hi John, Thanks for getting back to me. I re-scanned the throttles in the DC-6 Axes. They are now working. PMDG updated the DC-6 twice recently so I think the update disconnected the link between FSUIPC and the model. The reason you only found to poorly scanned throttles 1 & 2 is that I did this early on but now I generally scan and calibrate them within the various subsections specific to the particular airplane. The PMDG DC-6 accepts Throttle input direct, not calibrated. The DC-3 has the Duckworth enhancement that uses a preset Duckworth special connections. The PMDG 737 uses the standard scanned and calibrated throttle input. Apparently the standard is "no standard!" Thanks for your time and help. Your customer service is tops! Say "Hello" to your dad. As I mentioned, I've been using FSUIPC since the early days and think it's the superior method for controlling flight controls. I'm attaching my current .ini file for information is you have time to look at it. Jim Driskell FSUIPC7.ini

Hi John, I tried another flight with the PMDG DC-6 with the same results, the CH Quad loosing control for Throttle 1 & 2. The only way I could control them was with the mouse. 3 & 4 continue to work. I'm attaching my .ini file and the really big .log file. I included throttle 3 & 4 for comparison. Sorry for the extra data. Jim Driskell FSUIPC7.ini FSUIPC7.log

OK, I don't open FSUIPC very often if everything is working. Will be more observant. Jim

John, Will do. MSFS starts FSUIPC and I don't usually read the splash screen but will do in the future. Jim Driskell

Flying PMDG DC-6 in MSFS that requires direct throttle input via FSUIPC 7 ver 7.3.24. Engine runup and take off is fine. Reducing power to 30" for cruise is works. But further reducing power for descent below 30" only works on engine 3 & 4. Can manually reduce throttles 1 & 2. input from my very old CH Throttle Quad has no effect on 1 & 2. I can increase power on 1 & 2 above 30" Checking FSUIPC values: Throttle 1 2 3 4 14719 15615 14335 14719 -16254 -15604 - 16384 - 16234 Lots of variation here but the quad has been working until just now. any ideas why half of the system would quit? I'm attaching the last log file for what it's worth. Maybe it's time for a new Quad. Thanks, Jim Driskell FSUIPC7.log

Hi John, I had 7.3.20 installed but upgraded today to 7.3.24. Make lots of difference and easier to use with the pesky lvars. I corrected the spelling of $Param on added your suggestion for parking brake controls and now everything works as advertised. Thanks again for your prompt help. As I mentioned before, I'm a long time user of FSUIPC and plan to continue. There is so much power built into the system but I've only scratched the surface. My complements to the Dowsons. Jim Driskell

Hi John, I'm still struggling with the lvar concept. I'm using an old CH Throttle Quad what shows its age. Max and Min Values for the Throttles and Mixture levers are: T1 - 15615, -15604 = 31219 T2 - 14335, -16384 = 30729 M1 - 14591, -16254 = 30773 M2 - 14591, -16384 = 30975 Myevents.txt file contains the following: DuckWorks_DC3_Throttle1#$Parm 31219.0 / 0.5 + (>L:DUCKWORKS_THROTTLE1_SET) DuckWorks_DC3_Throttle2#$Parm 30729.0 / 0.5 + (>L:DUCKWORKS_THROTTLE2_SET) DuckWorks_DC3_Mixture1#$Parm 30773.0 / 0.5 + (>L:DUCKWORKS_MIXTURE1_SET) DuckWorks_DC3_Mixture2#$Parm 30975.0 / 0.5 + (>L:DUCKWORKS_MIXTURE2_SET) I got this format from a previous entry in forum dated 6/23/2023 with a conversaton with Andre92. I bound these lvars to the throttle and mixture axes, checked select for Preset and Send to FS as normal axis but they have no effect on the throttles within the Duckworks Enanced DC-3 aircraft within the sim. What an I missing? Probably my numeric parms. In addition, the Duckworks Enhancement also uses the lvar "DUCKWORKS_PARKING_BRAKE_SET." I sent the lvar to 0 but am unsure how to define the lvar within the myevents.txt file. Suggestions? Your documentation refers to a subset within the .ini file titled "[LvarOffsets]. Is this necessary when the system already has lvars listed and available? Thanks in advance for your help. I've been using FSUIPC ever since your father and I were young enough to learn new tricks. But I beginning to think that learning new ways of attaching flight controls to actions within the simulation is leaving me in the lurch. As they say, "if it ain't broke, don't fix it." Jim Driskell

Apparently the Duckworks enhancement for the MSFS DC-3 has it's own throttle and mixture labels for controlling these axes. They are called; DUCKWORKS _THROTTLE1_SET DUCKWORKS _THROTTLE2_SET DUCKWORKS _MIXTURE1_SET DUCKWORKS _MIXTURE2_SET Can FSUIPC control these axes and if so, how? Thanks, Jim Driskell

Hi John, Another weekend, but has Micamber said, "Things are looking up." I think I understand why I was having so much trouble with the missing Throttle Quad in the scan and the pesky xBox controllers impinging on my FSUIPC install. After getting a clean scan for FSUIPC and MSFS described above, I decided to re-install the Steam version of FSX since I have a lot of time and money invested in that old system. Bad idea! The registry conflict reappeared as evidenced by the missing Throttle Quad when I installed FSUIPC 4.997 into FSX - Steam. So I uninstalled FSX and Steam and the problem is gone. I get a clean scan with MSFS and FSUIPC7 so something within the Steam version is the problem. I'll stick with MSFS. Jim