Scotfleiger

Hi Pete Thank you for the feedback. Attached is a copy of the wxstationlist.bin as requested. Note: The wxstationlist.bin is in Prepar3d Folder under Weather\ and not located in the Appdata\Roaming\Prepar3d V4\ Andrew wxstationlist.bin

Hi Pete A LINDA user has reported an issue with Exception 25 ILLEGAL OPERATIONS that appears to be caused by loading the FSX Control values. Can you suggest what the cause could be? The errors are occurring before LINDA starts. Exception 25 - FSUIPC5.log

Hi Pete One of my LINDA users is experiencing repeated HID device disconnects (shown as Joystick Device Scans). He only has 3 devices connected (CH Fighterstick, CH pedals and ThrottleTek (Leo Bodnar card)). Can you suggest what may be happening? I can only think it is Windows. We have checked the auto power shutdown options (disabled). Strangely with the ThrottleTek physically disconnected (see FSUIPC4-ThrottleTek2.log), the first 2 Joystick Device Scan only has 2 devices listed but subsequent entries show 3 devices (only 2 connected). In the latter case both the ThrottleTek and Pedals have the ID 2 and the Pedals are listed twice. Any help would be appreciated. FSUIPC4-ThrottleTek.log FSUIPC4-ThrottleTek2.log

No problems. Thank you for looking.

I had great hopes for setting the 'damned' power management. However, no luck. I just have to remember to function the trim wheel before flight. Attached are the before and after joy files. FSUIPC5.JoyScanTrimMoved.csv FSUIPC5.JoyScanOnStart.csv

Pete I have recently acquired a Saitek Cessna Trim Wheel (VID 06A3, PID 0C2D) and assigned it to the Elevator Trim axis. FSUIPC5 logs it as but does not initially action any input. After the trim wheel has been operated the device reload and then FSUIPC recognises the trim input. The FSUIPC5.log shows the device reconnecting at this point. The attached load also includes LINDA logging. If this a known problem? FSUIPC5.log FSUIPC5.ini

Fine. I do not use ProSim and have never had the problem before. I switched back to 5.123d last night and the problem did not repeat. I will monitor.

Hi Pete Welcome back. I have installed your latest 5.123e but there appears to be a knock on adverse effect. After the FSUIPC is opened and closed, right-clicking on the virtual cockpit brings up the P3Dv4.2 View pop up but none of the side tabs appear (cockpit/spot) when the mouse is moved over the menu item. This makes it impossible to change views via this method. This was not happening with 5.122 or 5.123d. EDIT: I have the following Add-ons menu items: vPilot Squawk Mode C/Standy/Ident FSLabs & FSLabs Spotlights SODE 1.5.3 FSUIPC (of course) Active Weather Request (AS16) Couatl stings/live update GSX Add-on Manager (Virtuali)

I previously had no problems with 5.121 or 5.122 but you do not always need to open the FSUIPC dialog once you have your axes and any buttons set up. I have GSX and FSLabs in my add-on menu. I also use LINDA 3.0.5 as my primary interface through FSUIPC5. FSUIPC5 continues to work fine but you can not changes anything without the Add-on menu selected dialog.

I have hit the same problem with 5.123c. The FSUIPC add-on dialog randomly appears initially but once closed it can not be reopened unless P3D is restarted. I have also tried 5.121c and 5.122 with the same issue.

Hi Pete My user is still experiencing issues with connecting his VRi Combo Panel to FSUIPC4 and therefore LINDA. However, the VRi software can communicate with no issues. You mentioned above that FSUIPC tries to connect at 115200 bps which in this case be to high. Would it be possible to be able to vary this serial speed ideally as a .ini parameter?

You may like to look at LINDA which provides a easy way to integrate sophisticated actions using LUA. There are many available modules for specific aircraft. It free to use.

Hi Pete VRI issues 2 interface programs: VRISIM (which does a combination of what FSUIPC and LINDA do in a simplified way for a limited range of aircraft) and SerialFP2 (which I think you may be referring to). As my 2 VRI MCP Panels (Boeing and Airbus) work fine and they are the same firmware version (1.100) as my user, I don’t think there is anything more I can do. His panel is kaputt!!

Hi Pete Just to conclude. My user and I have carried out tests without LINDA and they prove that his VRi MCP Combo 2 (Airbus) is faulty - see relevant portions of the logs below. It fails to respond to the 5 CMDCON requests sent by FSUIPC4. I have advised him to contact his supplier. Thank you again for your help. His Test (using faulty MCP2a Airbus Panel) 500 SimConnect_Open succeeded: waiting to check version okay 500 Trying to use SimConnect Acc/SP2 Oct07 500 Opened separate AI Traffic client okay 516 VRI port 1 "com3" opened 532 VRI com3 <--- CMDRST [from FSUIPC init] 1610 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N 2438 VRI com3 <--- CMDCON [from FSUIPC init] 2516 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 2516 Initialising SimConnect data requests now 2516 FSUIPC Menu entry added 2547 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y 2547 C:\Users\Erwin\Documents\Flight Simulator X-Dateien\standard.FLT 2547 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\C172\Cessna172SP.AIR 2547 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=N 2563 Memory in use: 612Mb, Avail=3484Mb, MaxFreeBlock=2043Mb 3703 VRI com3 <--- CMDCON [from FSUIPC init] 3844 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y 4969 VRI com3 <--- CMDCON [from FSUIPC init] 6203 VRI com3 <--- CMDCON [from FSUIPC init] 7422 VRI com3 <--- CMDCON [from FSUIPC init] 62641 Memory in use: 1122Mb, Avail=2974Mb, MaxFreeBlock=2043Mb 91172 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N 91203 Aircraft loaded: running normally now ... 91203 User Aircraft ID 1 supplied, now being used 91594 System time = 20/12/2017 08:04:15, Simulator time = 08:02:45 (07:02Z) 91594 Aircraft="Cessna Skyhawk 172SP Paint1" 94532 Starting everything now ... My Test (using serviceable MCP2 Boeing Panel) 187 SimConnect_Open succeeded: waiting to check version okay 187 Trying to use SimConnect Steam 187 Opened separate AI Traffic client okay 218 VRI port 1 "com4" opened 234 VRI com4 <--- CMDRST [from FSUIPC init] 1265 Running in "Microsoft Flight Simulator X", Version: 10.0.62615.0 (SimConnect: 10.0.62615.0) 1265 Initialising SimConnect data requests now 1265 FSUIPC Menu entry added 1281 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y 1281 C:\Users\andre\Documents\Flight Simulator X Files\C172 EGPH.FLT 1281 C:\Program Files (x86)\Steam\steamapps\common\FSX\SimObjects\Airplanes\C172\Cessna172SP.air 1281 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=N 1375 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y 1453 VRI com4 <--- CMDCON [from FSUIPC init] 1500 COMread: 8 bytes: 43 4D 44 43 4F 4E 00 42 1515 VRI com4 <--- CMDFUN [from FSUIPC init] 1687 Memory in use: 727Mb, Avail=3369Mb, MaxFreeBlock=2043Mb 1906 COMread: 8 bytes: 43 4D 44 4D 43 50 32 42 1921 VRI com4 <--- CMDVER [from FSUIPC init] 1921 VRI MCP2B ("MCP2 Boeing") detected on port com4 1968 COMread: 8 bytes: 43 4D 44 31 2E 31 30 30 1984 VRI com4 <--- CMDFR [from FSUIPC init] 4250 Weather Mode now = Theme 10781 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=Y 10781 Aircraft loaded: running normally now ...

Thanks Pete I have received the attached log with the COM logging on. I have yet to sit down and work out what the HEX means. I will do this this evening. FSUIPC4.log

Thank you Pete. That gives me some ideas. LINDA too sends the CMDRST and CMDCON in its initialisation. If FSUIPC is not getting a response then LINDA won’t. I will try the additional debug settings. Many thanks.

Hi Pete I have changed my comport to a high number (7) but I am not seeing the same problem - both my Combo Boeing and Airbus work. I will try a slower connection speed. The point behind sending you the log is that FSUIPC is reporting the VRI port 1 "com7" opened (line 500) in the FSUIPC only section (before LINDA starts). On my system FSUIPC then reports VRI MCP2a detected on the port com7. My user does not get this message. Can you confirm what FSUIPC is checking to detect the VRi panel? Is there a non-detected message or action? Any help would be gratefully received as I have exhausted all the possible fault diagnosis routes.

Hi Pete One of my users has a problem connecting to his VRi Combo panel. I have tried all I know but have not solved the problem. Perhaps you can help. He has the correct FDTI USB Serial drivers installed. FSUIPC4.ini has the correct [VRInsight] block with the correct comport com7 set. The FSUIPC4.log reports that: VRI port 1 "com7" opened (line 500) but it not showing VRI MCP2A ("MCP2a Airbus") detected on port com7 as I am getting. LINDA can use com.open(com7, 115200, 0) to obtain a device number but the panel fails to respond to com.write commands to reset and initialise. The panel is working with VRi's software (VriSim.exe) so it is working. What would cause FSUIPC4 not to detect the panel? FSUIPC4.ini FSUIPC4-com7.log

FUSIPC5 is a new product for 64-bit P3Dv4. You will need to purchase a new licence to register it.

You could also try LINDA which provides a full set of modules for PMDG aircraft with easy to use functions to operate most switches and knobs.

Davide, take a look at the LINDA Support forum for information on LINDA. We have a fully functional module that should meet your needs. This provides specific functions for most controls, buttons and knobs provided your cockpit emulates button pushes. Under the download sub-forum you will find links for LINDA 3.0.4 and the specific module for the PMDG737NGX.

Thank you Pete.

Hi Pete Can you confirm whether ipc.macro is available in FSUIPC5? It is not something I have ever used but one of my users has asked the question. The lua document still lists it as available but I read from other threads that mouse macros (similar?) are not implemented.

The FSX Controls Gear_up and Gear_down (66079 and 66080) work fine. These can be set via FSUIPC dialog or using LINDA.