Guido

Hi Pete Maybe I don’t understand the access or numbering method. Reading the description for offset 2910: Byte 0 (bits 0-7): Joystick number (0-15) + 128. In other words 128 for Joystick 0, 129 for joystick 1, etc. Byte 1 (bits 8-15): Button number (0-39) The FSUIPCs Joystick assignment window shows joy# 158 and the button window 11, 12, 13 when pushing the MCP-Pro buttons. If the "joystick" number is already > 128 (like # 158) then the sum is out of range for Byte 0. What I don't understand is how to calculate the right "joystick" number for byte 0 of offset 2910. What I want to do is to assign Wilco A320 specific commands to 3 push buttons on my MCP-Pro. Thank you for your help. Rgds Guido

Hi Pete After my difficulties controlling throttle I wanted to do something easy! I wanted to read keys from MCP-Pro and assign a new function (for Airbus use). The tests with my Joystick was no problem. FSUIPC button asignment window shows Joy# 0 and button 2. The button is detected at (32FF) and which one selected via (2910). But the MCP-Pro shows in FSUIPC Joy# 158 buttons 11,12,13. The joystick number is out of range! How should I handle this correctly? Any idea? Sorry for bother you again but this is the “last” thing I wanted to do for now. Rgds

Hi Pete I am sorry to bother you again! After several attempts to make my throttle HW working with WA320 I realized that it is “not possible” to do this via FSUIPC. As written the WA320 uses throttle information compatible to DirectX and uses the AXIS_THROTTLE1(+2)_SET. The Serial USB TQ737 joystick driver does not support DirectX. Therefore I wanted to: Read 88C Engine1AxisValue Write to 3114 Engine1AxisValue and 3110 (66420) to AXIS_THROTTLE1_SET Write to 88C Engine1AxisValue The last write to 88C is to overwrite the FSX throttle increase from the write to 3310. If the engines are off levers move more or less on the 2D/3D display. But as soon as the engines are on the thing gets unstable and wild. I think by writing back to the 88C register, to remove the unwanted additional throttle increase, interferes with the FSX throttle loop. I did the same exercise using F1..F4 keys. The behavior is the same. Every F3 key write to (3200) increases the value at 88C and is then different to AXIS_THROTTLE1_SET. The attempt to overwrite the changed value at 88C makes the system unstable (levers jump up and down if engines are on)! So I think it is not possible to do make my joystick work with the WA320 via FSUIPC L. Rgds Guido

Hi Pete Yes, I have a solution for now. But I also think it is a bit complicated for the little I wanted to do. In deed I need to study what the Lua plug-in can do. About your lever movement question: I referred to the WA320 levers displayed at the monitor. Again thank you for your support and patient Guido

You are trying to use an axis control from a Client PC, not on the FS PC? A: The throttle axis is on the FS PC. At this very moment I use the wide client as "programming station" and for further developments or better further challengesJ. Er, sorry. Now I am really confused. Where is this USB connection< then? Surely not on the WideClient PC? How does it get its value into FS? A: Yes the Serial-USB-HW is connected to the FS PC. The client only reads and writes the values from/to the FS PC. These levers, are they motor controlled by any chance? If so, the software used with them might be READING the value from 088C, moving the lever according, which is then giving you a new position which you are feeding back -- result positive feedback, completely unwanted. A: I had the option with or without motor. For “time” reasons and for Airbus simulation compatibility I decided to skip the motor option. Writes to 089A are either ignored (except for a copy placed at 3330) if the thorttles are currently disconnected for AutoThrottle control, or result in a write to 088C, so I'm not at all surprised. 089A is realy simply a disconnectable 088C intended for autothrottle motor control applications where the feed through has to stop when A/T is engaged. A: OK, now I understand why the lever position did not change when I copied the position value to 089A only (I hoped to simulate a direct x axis input to FSX). I guess the unwanted move from the commanded lever position to full throttle could come from the motor option of my throttle. This seems to stop when “closing” the feedback loop from “KEY_AXIS_THROTTLE1_SET via 0x3110” to 089A (read 088C, write 089A and 03110). Sorry, you'll need to explain what you mean there. Since copying to 089A shouldn't do anything, isn't this the same as doing "copy the read value from 0x88C “calibrated” to 0x3114 addressing KEY_AXIS_THROTTLE1_SET via 0x3110", which would certainly make more sense. What exactly do you mean by "calibrated" in this context? A Calibration: The values delivered at 088C are from 0 to +16k. To move the throttles over the full range on the displayed WA320 I have to send -16k to +16k. Sorry, what do you mean? I wish I knew a bit more about this weird throttle device of yours. Did you build it yourself? Why is it so unorthodox? 1. A: Maybe this helps: B737 TQ from Poland Videos zu B737 TQ poland Throttle maker feedback: 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. My problem is that no direct x commands are used and my guess is that the Wilco Bus does not handle the Simconnect SDK inputs. Regards Pete Thank you for the smart feedback. Rgds Guido

Hi Pete Over the weekend I did quite an exercise in the attempt to make my TQ throttle work with Wilco’s A320 “misusing” FSUIPC (actually Wide Client). My steps: A: Read lever position in FSUIPC: The serial USB driver throttle input is available at “offset” 0x88C. B: The next thing was to copy the 0x88C value as proposed to 0x3114 addressing KEY_AXIS_THROTTLE1_SET via 0x3110 and wow the levers did move but move and move to max without any further lever movement. C: Next was to check what will happen when I copy the 0x88C value simply to 0x89A. No lever movement. D: When I copy the read value from 0x88C to 0x89A and “calibrated” to 0x3114 addressing KEY_AXIS_THROTTLE1_SET via 0x3110 did make it. But I am not sure if this is a clever implementation. I think my Logitech and CH-Throttle use the standard USB driver/gaming interface. FSX reads it from there and stores the values at the "right" locations that the Airbus can use it. I wonder if this can be emulated by using FSUIPC easier or if the current implementation is reasonable. By the way which document gives a good insight about the FSX and FSUIPC for me? Rgds 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