Skavsta

Hello Pete! Good news after so many months. But corona allows to test,pimp and play the flightsim every day:-) And yesterday, I've solved the problem with my rotaries.lua-configuration: Instead of use the vendor-ID and the product-ID of my Leo Bodnar-card BU0836X I tried desperated a part of the name, in this case: Vendor = "odnar" Product= "0836" ..and voila: while turning the rotaries the UI reads correctly 2 virtual buttons clockwise and 2 virtual buttons ccw (68,0; 68,1; 68,2; 68,3) (had to change the offset in rotaries.lua from 3340 to 3350 because I need the virtual joystick 64 to get buttonscreen-commands from wideclient) Now I try to find out values for the "timer" and the poll rate. Not easy because the BU0386X-card also have a editable polling-rate. Don't know how to get them together... But I'm happy to get rotaries.lua on board - thank You so much!

Pete, how would be the simmers world without your support - many, many thanks! I will try these things during the next days. Not too much time to play with my sim due to work. But You will get response! Have a nice day!

The joysticks #3, #4 and #5 do not generate axes. I get no axis-assigment while clicking "rescan" in the FSUIPC-interface (axis-assignment) and then turning the rotaries. The field "ignore axis" remains grey/inactive. The #3, #4 and #5 are USB-boards with 32 pins for buttons (www.leobodnar.com). I will play and test this evening, f.e. flash new firmware. But I am sure that my configuration is buggy.

Have changed the entry DEVICE = 3 to DEVICE = 1. But I still read the normal joystick and button numbers in the fsuipc-interface while turning😯

ah...sorry. I assumed that I have to select the #3 in the joysticks-section of FSUIPC.cfg Will try it later and report - thanks a lot!

Hi! I have installed installed several HIDs. Some of them are connected to rotaries to adjust VOR OBI, ADF, altimeter etc. Now I want to use the rotaries.lua to get more rotation speed while turning the OBI or the altimeter. I tried different entries in rotation.lua and FSUIPC.INI, searched in this forum, but it does not work. When I turn the knob I get the normal assignments in FSUIPC-window. But turning fast it should be something like joystick 64 button 0, or not? All other HID-operations work fine, inkl. all button and offset assignments. The buttons I want to use for rotation.lua have no assignments, of course! My configs: WIN 10, P3D45, newest FSUIPC reg. FSUIPC.INI: [JoyNames] AutoAssignLetters=No 0=Saitek Pro Flight Rudder Pedals 0.GUID={157FB2C0-7637-11E9-8005-444553540000} R=Saitek Pro Flight Rudder Pedals R.GUID={157FB2C0-7637-11E9-8005-444553540000} 1=Saitek Pro Flight Yoke 1.GUID={15CE9610-7637-11E9-8006-444553540000} Y=Saitek Pro Flight Yoke Y.GUID={15CE9610-7637-11E9-8006-444553540000} 2=CH THROTTLE QUADRANT 2.GUID={1D3433B0-7637-11E9-8007-444553540000} Q=CH THROTTLE QUADRANT Q.GUID={1D3433B0-7637-11E9-8007-444553540000} 3=BU0836X Interface 3.GUID={F94574E0-A94F-11E9-8001-444553540000} A=BU0836X Interface A.GUID={F94574E0-A94F-11E9-8001-444553540000} 4=Button Box Interface 1 4.GUID={F94574E0-A94F-11E9-8002-444553540000} B=Button Box Interface 1 B.GUID={F94574E0-A94F-11E9-8002-444553540000} 5=Button Box Interface 2 5.GUID={F9459BF0-A94F-11E9-8003-444553540000} C=Button Box Interface 2 C.GUID={F9459BF0-A94F-11E9-8003-444553540000} FSUIPX.joyScan: Good?, flags, VID, PID, Name, INIid, REGid, RegEntry, INIguid, REGguid, HIDguid, ValsOK?, ReadsOk? ,,, HIDscanning completed N, x00, x1DD2, x1142, , -1, -1, 0, {NULL}, {NULL}, {F9459BF0-A94F-11E9-8003-444553540000}, Y, N N, x00, x1DD2, x1001, , -1, -1, 0, {NULL}, {NULL}, {F94574E0-A94F-11E9-8001-444553540000}, Y, N N, x00, x068E, x00FA, , -1, -1, 0, {NULL}, {NULL}, {1D3433B0-7637-11E9-8007-444553540000}, Y, N N, x00, x06A3, x0BAC, , -1, -1, 0, {NULL}, {NULL}, {15CE9610-7637-11E9-8006-444553540000}, Y, N N, x00, x1DD2, x1141, , -1, -1, 0, {NULL}, {NULL}, {F94574E0-A94F-11E9-8002-444553540000}, Y, N N, x00, x06A3, x0763, , -1, -1, 0, {NULL}, {NULL}, {157FB2C0-7637-11E9-8005-444553540000}, Y, N ,,, REGscanning completed N, x00, x1DD2, x1142, Button Box Interface 2, -1, 5, 0, {NULL}, {F9459BF0-A94F-11E9-8003-444553540000}, {F9459BF0-A94F-11E9-8003-444553540000}, Y, N N, x00, x1DD2, x1001, BU0836X Interface, -1, 3, 0, {NULL}, {F94574E0-A94F-11E9-8001-444553540000}, {F94574E0-A94F-11E9-8001-444553540000}, Y, Y N, x00, x068E, x00FA, CH THROTTLE QUADRANT, -1, 2, 0, {NULL}, {1D3433B0-7637-11E9-8007-444553540000}, {1D3433B0-7637-11E9-8007-444553540000}, Y, Y N, x00, x06A3, x0BAC, Saitek Pro Flight Yoke, -1, 1, 0, {NULL}, {15CE9610-7637-11E9-8006-444553540000}, {15CE9610-7637-11E9-8006-444553540000}, Y, Y N, x00, x1DD2, x1141, Button Box Interface 1, -1, 4, 0, {NULL}, {F94574E0-A94F-11E9-8002-444553540000}, {F94574E0-A94F-11E9-8002-444553540000}, Y, N N, x00, x06A3, x0763, Saitek Pro Flight Rudder Pedals, -1, 0, 0, {NULL}, {157FB2C0-7637-11E9-8005-444553540000}, {157FB2C0-7637-11E9-8005-444553540000}, Y, Y ,,, User settings imported N, x00, x1DD2, x1142, Button Box Interface 2, 5, 5, 0, {F9459BF0-A94F-11E9-8003-444553540000}, {F9459BF0-A94F-11E9-8003-444553540000}, {F9459BF0-A94F-11E9-8003-444553540000}, Y, N N, x00, x1DD2, x1001, BU0836X Interface, 3, 3, 0, {F94574E0-A94F-11E9-8001-444553540000}, {F94574E0-A94F-11E9-8001-444553540000}, {F94574E0-A94F-11E9-8001-444553540000}, Y, Y N, x00, x068E, x00FA, CH THROTTLE QUADRANT, 2, 2, 0, {1D3433B0-7637-11E9-8007-444553540000}, {1D3433B0-7637-11E9-8007-444553540000}, {1D3433B0-7637-11E9-8007-444553540000}, Y, Y N, x00, x06A3, x0BAC, Saitek Pro Flight Yoke, 1, 1, 0, {15CE9610-7637-11E9-8006-444553540000}, {15CE9610-7637-11E9-8006-444553540000}, {15CE9610-7637-11E9-8006-444553540000}, Y, Y N, x00, x1DD2, x1141, Button Box Interface 1, 4, 4, 0, {F94574E0-A94F-11E9-8002-444553540000}, {F94574E0-A94F-11E9-8002-444553540000}, {F94574E0-A94F-11E9-8002-444553540000}, Y, N N, x00, x06A3, x0763, Saitek Pro Flight Rudder Pedals, 0, 0, 0, {157FB2C0-7637-11E9-8005-444553540000}, {157FB2C0-7637-11E9-8005-444553540000}, {157FB2C0-7637-11E9-8005-444553540000}, Y, Y ,,, Values matched and decided (Y), x16, x1DD2, x1142, Button Box Interface 2, 5, 5, 0, {F9459BF0-A94F-11E9-8003-444553540000}, {F9459BF0-A94F-11E9-8003-444553540000}, {F9459BF0-A94F-11E9-8003-444553540000}, Y, N Y, x1E, x1DD2, x1001, BU0836X Interface, 3, 3, 0, {F94574E0-A94F-11E9-8001-444553540000}, {F94574E0-A94F-11E9-8001-444553540000}, {F94574E0-A94F-11E9-8001-444553540000}, Y, Y Y, x1E, x068E, x00FA, CH THROTTLE QUADRANT, 2, 2, 0, {1D3433B0-7637-11E9-8007-444553540000}, {1D3433B0-7637-11E9-8007-444553540000}, {1D3433B0-7637-11E9-8007-444553540000}, Y, Y Y, x1E, x06A3, x0BAC, Saitek Pro Flight Yoke, 1, 1, 0, {15CE9610-7637-11E9-8006-444553540000}, {15CE9610-7637-11E9-8006-444553540000}, {15CE9610-7637-11E9-8006-444553540000}, Y, Y (Y), x16, x1DD2, x1141, Button Box Interface 1, 4, 4, 0, {F94574E0-A94F-11E9-8002-444553540000}, {F94574E0-A94F-11E9-8002-444553540000}, {F94574E0-A94F-11E9-8002-444553540000}, Y, N Y, x1E, x06A3, x0763, Saitek Pro Flight Rudder Pedals, 0, 0, 0, {157FB2C0-7637-11E9-8005-444553540000}, {157FB2C0-7637-11E9-8005-444553540000}, {157FB2C0-7637-11E9-8005-444553540000}, Y, Y FSUIPC.log: Prepar3D.exe version = 4.5.12.30293 Reading options from "C:\Program Files\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.ini" Checking the Registrations now ... FSUIPC5 Key is provided WIDEFS7 not user registered, or expired 0 System time = 22/07/2019 09:13:47 0 FLT path = "C:\Users\Gunnar\Documents\Prepar3D v4 Files\" 0 Using DialogMode 31 FS path = "C:\Program Files\Lockheed Martin\Prepar3D v4\" 125 ---------------------- Joystick Device Scan ----------------------- 125 Product= Button Box Interface 2 125 Manufacturer= Leo Bodnar 125 Serial Number= B51344 125 Vendor=1DD2, Product=1142 (Version 1.4) 140 GUIDs returned for product: VID_1DD2&PID_1142: 140 GUID= {F9459BF0-A94F-11E9-8003-444553540000} 140 Details: Btns=128, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0 140 Product= BU0836X Interface 140 Manufacturer= Leo Bodnar 140 Serial Number= B39900 140 Vendor=1DD2, Product=1001 (Version 1.36) 140 GUIDs returned for product: VID_1DD2&PID_1001: 140 GUID= {F94574E0-A94F-11E9-8001-444553540000} 140 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R4095,U4095,V4095,X4095,Y4095,Z4095 140 Product= CH THROTTLE QUADRANT 140 Manufacturer= CH PRODUCTS 140 Vendor=068E, Product=00FA (Version 0.0) 140 GUIDs returned for product: VID_068E&PID_00FA: 140 GUID= {1D3433B0-7637-11E9-8007-444553540000} 140 Details: Btns=12, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U255,V255,X255,Y255,Z255 140 Product= Saitek Pro Flight Yoke 140 Manufacturer= Saitek 140 Vendor=06A3, Product=0BAC (Version 3.2) 140 GUIDs returned for product: VID_06A3&PID_0BAC: 140 GUID= {15CE9610-7637-11E9-8006-444553540000} 140 Details: Btns=23, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U255,V255,X1023,Y1023,Z255 140 Product= Button Box Interface 1 140 Manufacturer= Leo Bodnar 140 Serial Number= B51406 140 Vendor=1DD2, Product=1141 (Version 1.4) 140 GUIDs returned for product: VID_1DD2&PID_1141: 140 GUID= {F94574E0-A94F-11E9-8002-444553540000} 140 Details: Btns=128, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0 140 Product= Saitek Pro Flight Rudder Pedals 140 Manufacturer= Saitek 140 Vendor=06A3, Product=0763 (Version 1.0) 140 GUIDs returned for product: VID_06A3&PID_0763: 140 GUID= {157FB2C0-7637-11E9-8005-444553540000} 140 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0 140 ------------------------------------------------------------------- 156 Device acquired for use: 156 Joystick ID = 5 (Registry okay) 156 5=Button Box Interface 2 156 5.GUID={F9459BF0-A94F-11E9-8003-444553540000} 171 Device acquired for use: 171 Joystick ID = 3 (Registry okay) 171 3=BU0836X Interface 171 3.GUID={F94574E0-A94F-11E9-8001-444553540000} 171 Device acquired for use: 171 Joystick ID = 2 (Registry okay) 171 2=CH THROTTLE QUADRANT 171 2.GUID={1D3433B0-7637-11E9-8007-444553540000} 171 Device acquired for use: 171 Joystick ID = 1 (Registry okay) 171 1=Saitek Pro Flight Yoke 171 1.GUID={15CE9610-7637-11E9-8006-444553540000} 171 Device acquired for use: 171 Joystick ID = 4 (Registry okay) 171 4=Button Box Interface 1 171 4.GUID={F94574E0-A94F-11E9-8002-444553540000} 171 Device acquired for use: 171 Joystick ID = 0 (Registry okay) 171 0=Saitek Pro Flight Rudder Pedals 171 0.GUID={157FB2C0-7637-11E9-8005-444553540000} 171 ------------------------------------------------------------------- 390 LogOptions=00000000 00000001 390 ------------------------------------------------------------------- 390 SimConnect_Open succeeded: waiting to check version okay 390 Opened separate AI Traffic client okay 390 ### PDKmodeHelper callback registered 4765 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.5.12.30293 (SimConnect: 4.5.0.0) 4765 Initialising SimConnect data requests now 4765 FSUIPC Menu entry added 4781 ... Using Prepar3D with Academic License 4812 C:\Users\Gunnar\Documents\Prepar3D v4 Files\all9.fxml 4812 C:\Users\Gunnar\Documents\Prepar3D v4 Add-ons\A2A\SimObjects\Airplanes\A2A_C172\C172.air 9093 ### The user object is 'A2A C172R N7274H' 9093 ### Mode is NORMAL 12281 ### Mode: PAUSE on 40171 Loading Complete ... 40187 ### Mode is NORMAL 40968 User Aircraft ID 2 supplied, now being used 40968 Aircraft loaded: running normally now ... 41015 System time = 22/07/2019 09:14:28, Simulator time = 14:00:46 (21:00Z) 41171 Aircraft="A2A C172R N7274H" 48015 -------------------- Starting everything now ---------------------- 48062 LUA.0: beginning "C:\Program Files\Lockheed Martin\Prepar3D v4\Modules\rotaries.lua" 48062 LUA.0: ...les\Lockheed Martin\Prepar3D v4\Modules\rotaries.lua:1 48062 LUA.0: Global: ipcPARAM = 0 48062 LUA.0: ...les\Lockheed Martin\Prepar3D v4\Modules\rotaries.lua:2 48062 LUA.0: Global: Vendor = 1DD2 48078 LUA.0: ...les\Lockheed Martin\Prepar3D v4\Modules\rotaries.lua:3 48078 LUA.0: Global: Product = 1001 48078 LUA.0: ...les\Lockheed Martin\Prepar3D v4\Modules\rotaries.lua:10 48078 LUA.0: Global: Device = 3 48078 LUA.0: ...les\Lockheed Martin\Prepar3D v4\Modules\rotaries.lua:16 48078 LUA.0: Global: Rotaries = table: 000001C3DF2C5F10 48093 LUA.0: ...les\Lockheed Martin\Prepar3D v4\Modules\rotaries.lua:18 48093 LUA.0: Global: dev = 0 48109 LUA.0: ...les\Lockheed Martin\Prepar3D v4\Modules\rotaries.lua:19 48109 LUA.0: Could not open HID 48109 LUA.0: ...les\Lockheed Martin\Prepar3D v4\Modules\rotaries.lua:20 49203 Advanced Weather Interface Enabled rotaries.lua: Vendor = "1DD2" Product = "1001" Device = 3 -- Multiple devices of the same name need increasing Device numbers -- Use separate Lua plug-ins for separate cards! -- NOTE: this can handle up to 16 rotaries only, using the first 64 "virtual buttons" -- List the pairs here: Rotaries = {22, 23 } ... ... Thanks for help!

Hello Pete! After many years of TCPIP-connection from notebook to my Flightsim-PC I want to install a connection via SPX-protocol. (OK - never change a running system, but this have non-FS-reasons!) But I'm getting desperate - reading the PDF-manual 1000 times did not help. On both PCs is WideFS 6.70 installed. FS9 WINXP ..and: I get a normal WIN-network-connection via SPX between both PCs and in both directions! This should exclude WIN-config-erros, or not? Here comes the newest log-file: ********* WideClient Log [version 6.70] Class=FS98MAIN ********* Date (dmy): 21/11/07, Time 17:18:56.716: Client name is NOTEBOOK 190 Attempting to connect now 190 Trying IPX/SPX on Port 8002, Node 0.0.1024.50958.40348 ... 6179 Error on client pre-Connection Select() [Error=10051] Network is unreachable 6189 Ready to try connection again 7210 Attempting to connect now 7210 Trying IPX/SPX on Port 8002, Node 0.0.1024.50958.40348 ... 14761 ****** End of session performance summary ****** 14761 Total time connected = 0 seconds 14761 Reception maximum: 0 frames/sec, 0 bytes/sec 14761 Transmission maximum: 0 frames/sec, 0 bytes/sec 14761 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0 14761 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) ********* wideclient.ini: [Config] Port=8002 ServerNode=0.0.1024.50958.40348 ServerName="FLIGHT" ;ServerIPAddr=67.12.64.13 Window=0,0,1024,738 Visible=Yes ButtonScanInterval=20 ;ClassInstance=0 NetworkTiming=5,1 PollInterval=2000 ResponseTime=18 ApplicationDelay=0 TCPcoalesce=No WaitForNewData=500 MaxSendQ=100 OnMaxSendQ=Log NewSendScanTime=50 Priority=3,1,2 ActionKeys=Yes PostKeys=no MailslotTiming=2000,1000 Port2=9002 Protocol=SPX ClassInstance=0 widerserver.ini: [Config] Port=8002 ServerName="FLIGHT" AutoRestart=0 AutoUpdateTime=13 MaximumBlock=4096 NoStoppedRestarts=Yes RestartTime=10 SendTimeout=15 ProtocolPreferred=SPX AdvertiseService=1 Port2=9002 TCPcoalesce=No ; ----------------------------------------------- [user] Log=Errors+ ; =============================================== [ClientNames] 1=NOTEBOOK Any hints? Thanks for Your answer! Gunnar Greetings from EDLW

Hi Pete! Thank You very much for your help ! Ok, I'll do it by Your way: 2 TrafficLook, one for ground, the other for airborne. That should work fine. And last not least: I want to thank You for FSUIPC. This great tool expands the possibilities of FS and its hardware: Oh yes, after phases of testing and playing with compound-programming of joysticks it is so easy to get several views (cockpit, extern, all directions) with only 3 buttons! Regards, Gunnar

Hi Pete! Sorry for delay - here are my WideFs-Files: WIDECLIENT.INI ============= [Config] Port=8002 UseTCPIP=Yes ServerIPAddr=192.168.178.222 Window=32000,32000,160,34 Visible=Yes ButtonScanInterval=20 ClassInstance=0 NetworkTiming=5,1 PollInterval=2000 ResponseTime=18 ApplicationDelay=0 TCPcoalesce=No WaitForNewData=500 MaxSendQ=100 OnMaxSendQ=Log NewSendScanTime=50 Priority=3,1,2 ActionKeys=Yes PostKeys=no ; ----------------------------------------------- [user] Log=Errors+ RunReady1=X:\fs9\modules\trafficlook.exe RunReady2=X:\fs9\fsmeteo\fs_meteo.exe RunReady3=X:\fs9\modules\weatherset.exe ;RunReady4=D:\fstools\sb3\squawkbox.exe CloseReady1=Yes CloseReady2=Yes CloseReady3=Yes KeySend1=70,12,RunReady1 KeySend2=84,8,RunReady1 KeySend3=70,12,RunReady1 KeySend4=71,8,RunReady1 ShowRxFrameRate=yes WIDESERVER.INI ================ [Config] Port=8002 AutoRestart=0 AutoUpdateTime=13 MaximumBlock=4096 NoStoppedRestarts=Yes RestartTime=10 SendTimeout=15 TCPcoalesce=No AdvertiseService=Yes ; ----------------------------------------------- [user] Log=Errors+ [ClientNames] 1=NOTEBOOK 2=SHUTTLE Do You need more? Regards,Gunnar

Tried this also - no difference. I'll post the WideClient.ini and WideServer.ini on Monday, or do you need more? Good night, Gunnar

WideFs hangs, and sometimes also the whole system. The notebook has got a brandnew WinXP-installation (only 1 week old, after HDD-crash some weeks before), the WinXP-nstallation cannot be the reason. Entry in WideClient.ini: ... RunReady1=X:\trafficlook.exe ... KeySend1=70,12,RunReady1 KeySend2=84,8,RunReady1 ... KeySend3=70,12,RunReady1 KeySend4=71,8,RunReady1 ... Perhaps something wrong with the parameters behind the ASCII-codes? Regards, Gunnar

Yes- the menu opens. But after the second key (in this case G or T) the notebook hangs. KeySend1 ist set to ALT-F KeySend2 ist set to key G The ALT-F-combination doesn't exist on the notebook! Oh...good idea. I'll do this if i can't fix the problem. Regards, Gunnar

Hi Pete! I've tried almost everything to switch TrafficLook between "GroundTraffic only" and "Airborne only" by Joystick-button via WideFS (keySend) TrafficLook runs on notebook, but whilst using the ALT-F -Key on FS-Computer to get the TrafficLook-menu, the notebook always hangs up:-( Is there a way to switch between the 2 modes of TrafficLook WITHOUT using the dangerous ALT-Key? Any other hotkeys perhaps? Thanks, Gunnar

On my PC taxiing at big hubs is like a slideshow, because there are many objects near my aircraft (buildings, vehicles, signs etc). All these things are not shown during approaches, so the framerate is ok. But on the apron and near the terminal-buildings it goes down. So I need there EACH fps - and the trick (turbolence/gust decreases fps while using much AI) saves some fps (found it somewhere on simflight.com a few months ago). OK, that sounds complicated - but I'm dreaming of a hotkey (like taxiwind-hotkey) to turn off/on the turbolence when ever the framerate goes up/down... Gunnar

Hi Pete! I'm using the newest FSUIPC, FS9.1 and external weather (FSMETEO) To save framerate I have to deactivate all turbolences and/or gusts. The reason: I'm using 100% AI-Traffic, and at big hubs like EDDF, EHAM etc. my framerate decreases to a slideshow, especially while taxiing!!! OK, I should get a new PC:-) But there is a cheaper way: Switching off all turbolences/gusts increases the framerate by 4-7fps, if You are using much AI-traffic. But flying without turbolences is not very realistic, and I'm missing these bumpy approaches.... That means: - I want turbolences while I'm flying. - I do not want them while taxiing. Now my question: Is there any possibility to manage this problem with FSUIPC? ("Supress all turbolences if not airborne" ?!) Greetings from EDLW Gunnar