kaha

Ok, that's at least something. Thx, Karl

Great news! No mouse macros is a significant drawback, however. Karl

I want to share my lua script for trimming. It works as follows: https://www.dropbox.com/s/2ceuy2jj8hfftib/Surface_Trim.lua?dl=0 To a button assign the control "Lua Surface Trim" after you have copied the file into your FSUIPC folder. The Parameter entry consists of 100000 for Elevator trim 200000 for Aileron trim 300000 for Rudder trim To this add the amount you want to trim: 1 for very small trim a maximum of 16383 for full trim add this to the base: 100000 + 300 = 100300 that would be a moderate trim up

Just to mention this: I had a bug in a lua script. This caused FSUIPC to crash. The tray icon was still there but did not respond. Restarting MSFS told me that FSUIPC is already running. In TaskManager FSUIPC 7 is not visible. I had to reboot. I attached the .log file (which just says that my lua script had to be terminated). So, no worries, this is just to let you know, John. Karl Windows 10 20H2 Build 19042.867 FSUIPC 7.0.8 FSUIPC7.log

My question aimed at finding a possiblity within lua to clearly identify the Arduinos I have connected to my rig, they are not HIDs. I use Teensy 3.2, 3.5, 2.6, 4.0 and 4.1. Anyway, I stick to what I have. I wanted to be able to identify the Arduinos automatically regardless on which port they connect. The main criteria I use for recognition is the baudrate of 115200 that I use for all my connected Teensys. Anyone wants to share how he handles this? Here is my code (Identify_Arduinos.lua), but it's surely far from being an ideal solution. I'm more a C/C++ coder, not a lua coder. A

Thank you Pete. Karl

Quick question: With the possibilities of FSUIPC and lua only, how could I get a list of devices that have an active com port? It basically would be the list delivered by HidScanner.exe with the addition of a com port number for devices where it is available. Thank you, Karl

Yes, had 7.0.6 installed somehow. It works now. Sorry, Karl

I can read but not write 0x0354 transponder code Karl

Ok. Karl

I think I'm all set now. It was quite a challenge. The log file told me that joystick id 0 is registered twice in the registry, so I had to clean that out. I switched to Letters, adjusted the button and axis actions and now everything works. https://www.dropbox.com/s/w30ipn5rlfng034/FSUIPC6.ini?dl=0 https://www.dropbox.com/s/ysd8q262pa45lun/FSUIPC6.log?dl=0 I still have to take a look to FSUIPC 7 in MSFS now. Thx, Karl

Thx for letting me know. I'm sure I will read your post again several times. Karl

Thank you Pete, I'll work on it and report back then. Karl

Thank you John, this is a very generous offer. However, I want to try to sort it out by myself. If I will not succeed, I would be very glad if I then could get back to you and ask for your help. Thx, Karl

Thank you Pete. Button presses and axis movements on the Hotas Throttle do not arrive in FSUIPC. They arrive in P3D, though. Here is the .ini file form before my hardware change, I made a backup before I started to change hardware. https://www.dropbox.com/s/ikzjoawn2ariiif/FSUIPC6_original.ini.txt?dl=0 At that time I had connected: - Logitech G920 Racing Wheel - Logitech Extreme 3D Joystick - Thrustmaster T.Flight Stick X - Thrustmaster Hotas Warthog Throttle And here is the new .ini file https://www.dropbox.com/s/