Guido

Hi Pete Again thank you very much for the professional and quick replay. I appreciate it very much. Your point: What CH driver is that, which writes to offsets? Most joystick drivers just allow you to assign the axes as you like. Feedback: It works with the CH throttle quadrant USB and it does also work with the integrated "throttle" in my Logitech stick. So I do not know what my new throttle is missing to write. The other points I need to study and will provide you feedback. Rgds Guido

Hi Pete Thank you for the quick replay. Maybe I am using the wrong wording but from Eric Marciano's help and feedback (bellow) - Anyway, what I can tell you is that my Airbus gauges read the standard FS variables that provide the throttle lever position. It is not a secret, my code read the KEY_AXIS_THROTTLE1_SET and KEY_AXIS_THROTTLE2_SET events to determine what to do when the throttle levers are moved. - I think that FSUIPC does read and write into variables (registers) to control FSX. My CH-Throttle driver did write in to the right locations to control the Airbus throttle levers but unfortunately my new one does it different (bellows feedback). Feedback from throttle supplier: The FeelThere Airbus probably uses out of standard ways to manage thrusts, as FSX itself doesn't have specific commands for this type of throttle. In our TQ throttle driver, we use only Microsoft's directives, as from Simconnect SDK, that is writing throttles values from -4096 to +16368 into throttle offsets, depending on lever positions on the TQ. Therefore I had the idea to correct this by reading 0x088C (what works) and then write into the missing location (location/variable/register). But unfortunately the writing into bellows location does not help. - 0x088C - 0x089A - 0x3AE8 Do you have an idea were to write the values read from "function 0x088C" that throttle levers and with this the "Airbus" moves? Thank you for your support. Rgds Guido

Hi Unfortunately my new throttle does not work with the Wilco Airbus SV1. With the CH-Throttle I had no problems. The Wilco Airbus does use the KEY_AXIS_THROTTLE1_SET and KEY_AXIS_THROTTLE2_SET registers to control throttles. I can read the HW throttle lever position via 0x088C but I can not make the graphic levers to move. I did test writes to different FSUIPC throttle entries like: - 0x088C - 0x089A - 0x3AE8 but nothing moves on the screen! Does someone know how to write into the KEY_AXIS_THROTTLE1_SET register set? Thank you very much for your help to let the levers move. Rgds Guido

Hi I did further study the TQ-Switch behavior when I assign LVD767 specific commands to the FSUIPC. As I did already write after take-off the switches do not trigger a key command any more. However in FSUIPC’s switch control window the assigned key-code is still displayed. Pls find the updated summary of my findings about the LVD767, Throttle Quadrant, and FSUIPC: - When I start FSX and then load the LVD 767 with 3D cockpit view after take-off the FSUIPC programmed switches on the TQ do not work anymore - With a standard aircraft like 747 I have no problems identified - When I use the LVD767 with 2D cockpit I discovered also no problems - When I check the switches first in the LVD767 2D cockpit view and then change to the 3D the switch assignment is only sometimes no problem - When I assign the TQ switches via LVD767’s customize commands menu everything works. It is quite erratic and I cannot see any correlation but it could well be that the source is a graphic or other driver problem. I hope AMD will soon fix some acknowledged issues with the video driver (eyefinity issues) for FSX. Therefore I decided to stay meanwhile with the LVD-Menu button assignment. Your question if the LVDS GPWS announcements issue was reported by others. I did read in the LVD forum that others have also problems. Some think it is linked to the Realtek sound driver, some say with Creative’s X-Fi it is no problem some say it is still a problem. Again thank you for your support. Rgds Guido

Hi I did install the latest FSUIPC version and as you did write no improvement. I did also log the switch codes. From the moment the Throttle Quadrant switches are not working there is also no further recording. Pls find the summary of my findings about the LVD767 Throttle Quadrant and FSUIPC issue: - When I start FSX and then load the LVD 767 with 3D cockpit view after take-off the FSUIPC programmed switches on the TQ do not work anymore - With the standard aircraft like 747 I have no problems identified - When I use the LVD767 with 2D cockpit I have also no problems - And now the trick: If I check the switches in the LVD767 2D cockpit view and then change to the 3D I have also no problems! (The used command to toggle the cockpit view is: A) This is similar to the LVD GPWS announcements. They work only when I test them in the 2D cockpit view first and then change to the 3D view. I think it could be a LVD issue and with the found work-a-round I can life for the moment. Again thank you very much for the professional and quick support. Rgds Guido

Hi Sorry I missed your latest mail and I will check your proposal. However this weekend I did follow your instructions and proposals. Below my findings: Q: Do you mean that there's no response from your devices that you can see in FSUIPC? [Guido]: Yes. However I did retest the key assignment in the FSUIPC. After selecting the check box aircraft specific the switches did display the assigned key values. Q: Also, please make sure you are using recent versions of FSUIPC -- not earlier than 4.60 -- as some earlier versions did time out responses from device [Guido]: I have version 4.60a. and as proposed I did switch off all USB-Hub power management functions. Q: By the way, why mention specifically the LVD 767? Are you implying that the same doesn't happen with default aircraft, or others added? If this is the case then the answer must lie in the LVD 767 code. [Guido]: I did test the throttle quadrant the LVD 767 and standard 747. With the 747 I had no issues but the LVD does lose the switch assignment after some time (normally after takeoff). I checked by changing windows, executing commands and menu calls if the assignment will be lost. I could not identify any dependency than after takeoff the switch assignments are gone. I appreciate if you could help as I like this functionality very much. Thanks Guido

Hi thank you for the quick replay. I will check the USB-Hub power management settings. I did not care it. Q: Do you mean that there's no response from your devices that you can see in FSUIPC? [Guido]: Yes, the FSUIPC switch monitor window shows no key codes when I press a switch after about 5..10min of use. Also, please make sure you are using recent versions of FSUIPC -- not earlier than 4.60 -- as some earlier versions did time out responses from device [Guido]: I did just download and register version 4.60a if I remember the number right. By the way, why mention specifically the LVD 767? Are you implying that the same doesn't happen with default aircraft, or others added? If this is the case then the answer must lie in the LVD 767 code. [Guido]: I am using the throttle quadrant only with the LVD 767 but I will check if it is OK with default aircrafts. I will check all when I am back home next Saturday and report you the outcome. Thanks Guido

Hi, I am using LVD 767 (3D Cockpit view) with FSX and W7-64. Connected to USB 2 HUB (external supply) are MCP Pro, yoke, and Throttle Quadrant. Right after start-up all throttle quadrant buttons/switches programmed in FSUIPC are working correctly. After some time only the lever “buttons” are working on the throttle quadrant and the switch buttons have lost the assigned functions. I did check it in FSUIPC and no functions are there any more. After FSX restart the same repeats. Can anybody help? What is going wrong? Thank you for your advices Rgds Guido