jskibo Posted June 13, 2020 Report Share Posted June 13, 2020 I'm running a PFC Cirrus II Pro along with FSUIPC V6, Pfchid64 in P3Dv5 on Windows 10 Pro 64 Everything runs great until engaging autopilot with any form of ALT or VS hold and the electric trim kicks in. Any AP commanded trim movements are small and jerky freezing the sim between each small movement. After several of these choppy movements happen in a row the sim will finally freeze up completely. This happens no matter what plane I am flying. Tested with Carenado, Flysimware, A2A and Stock planes Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 13, 2020 Report Share Posted June 13, 2020 1 hour ago, jskibo said: Everything runs great until engaging autopilot with any form of ALT or VS hold and the electric trim kicks in. Any AP commanded trim movements are small and jerky freezing the sim between each small movement. After several of these choppy movements happen in a row the sim will finally freeze up completely. That sounds like it must be something on the USB channel being used for the device locking up Windows drivers.. Have you used the Cirrus before? is it a new purchase? If not, if you've been using it with no troubles before, what changed which might result in something so unpredictable? Enabling FSUIPC Event and Axis logging just before engaging a mode which will introduce electric trim activity might help show what is going on, though that could get pretty big depending how long you allow it. Please don't try sending us huge logs. Try looking at them yourself and perhaps quoting chunks t illustrate matters. Pete Link to comment Share on other sites More sharing options...
jskibo Posted June 13, 2020 Author Report Share Posted June 13, 2020 1 hour ago, Pete Dowson said: That sounds like it must be something on the USB channel being used for the device locking up Windows drivers.. Have you used the Cirrus before? is it a new purchase? If not, if you've been using it with no troubles before, what changed which might result in something so unpredictable? Enabling FSUIPC Event and Axis logging just before engaging a mode which will introduce electric trim activity might help show what is going on, though that could get pretty big depending how long you allow it. Please don't try sending us huge logs. Try looking at them yourself and perhaps quoting chunks t illustrate matters. Pete Pete, Thank you for the quick reply. The Cirrus II Pro is new to me. I enabled the logging and you're right, it seem to keep reconnecting the USB device as it repeats the "reconnecting" for another 10+ times before the sim finally locks up. 324281 Aircraft loaded: running normally now ... 324328 User Aircraft ID 2 supplied, now being used 324406 System time = 13/06/2020 12:51:31, Simulator time = 12:00:01 (16:00Z) 324406 Aircraft="Carenado PA34 SENECA V N95465" 330594 -------------------- Starting everything now ---------------------- 330594 Loaded PFChid64.dll okay! 330609 ASN active function link set 330609 Ready for ActiveSky WX radar with additional data 330734 Setting external joystick scanner link ... 330734 ... Okay! 331844 Advanced Weather Interface Enabled 821328 Sim stopped: average frame rate for last 497 secs = 29.8 fps 821328 Max AI traffic was 90 aircraft 821328 ------------------------------------------------------------------- 949469 Sim stopped: average frame rate for last 86 secs = 29.8 fps 949469 Max AI traffic was 91 aircraft 949469 ------------------------------------------------------------------- 959344 LogOptions changed, now 30000000 00000001 959531 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 959531 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 959672 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 959672 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 959969 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 959969 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 960000 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 960000 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 960172 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 960172 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 960344 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 960344 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 960516 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 960516 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 960672 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 960672 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 960844 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 960844 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 961016 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 961016 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 961172 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 961172 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 961344 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 961344 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 961516 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 961516 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 961688 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 961688 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 961844 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 961844 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 962016 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 962016 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 962188 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 962188 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 962344 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 962344 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 962516 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 962516 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 962688 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 962688 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 962859 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 962859 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 962891 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER 963016 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 963016 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 963188 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 963188 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 963219 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 409 (0x00000199) AXIS_ELEVATOR_SET 963359 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 963359 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 963453 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 532 (0x00000214) AXIS_ELEVATOR_SET 963516 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 963516 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 963688 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 963688 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 963859 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 963859 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 964031 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 964031 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 964188 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 964188 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 964359 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 964359 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 964531 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 964531 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 964703 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 964703 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 964734 *** EVENT: Cntrl= 65799 (0x00010107), Param= 0 (0x00000000) AP_PANEL_ALTITUDE_HOLD 964734 *** EVENT: Cntrl= 65729 (0x000100c1), Param= 0 (0x00000000) AP_NAV1_HOLD 965469 -------------------------------------------------------------------- 965469 ***** HID USB device reconnected: re-initialising FSUIPC connections 965469 HID: Vendor=0689, Product=C200 (Version 2.0) 965469 Manufacturer= Precision Flight Controls, Inc. 965469 Product= PFC Cirrus II Pro 965469 Serial Number= PFC Cirrus II Pro 965469 ---------------------- Joystick Device Scan ----------------------- 965469 Product= PFC Cirrus II Pro 965469 Manufacturer= Precision Flight Controls, Inc. 965469 Vendor=0689, Product=C200 (Version 2.0) 965469 Product= MFG Crosswind V2 965469 Manufacturer= MFG 965469 Serial Number= MFG500002 965469 Vendor=16D0, Product=0A38 (Version 33.1) 965469 GUIDs returned for product: VID_16D0&PID_0A38: 965469 GUID= {49EFA990-7FCC-11E9-8001-444553540000} 965469 Details: Btns=2, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R4096,U0,V0,X4096,Y4096,Z0 965484 ------------------------------------------------------------------- 965500 Device acquired for use: 965500 Joystick ID = 0 (Registry okay) 965500 0=PFC Cirrus II Pro 965500 0.GUID={8F3D9370-AB42-11EA-8001-444553540000} 965500 Device acquired for use: 965500 Joystick ID = 0 (Registry okay) 965500 0=MFG Crosswind V2 965500 0.GUID={8F3D9370-AB42-11EA-8001-444553540000} 965500 Device acquired for use (as alternative possibility): 965500 Joystick ID = 2 (Registry okay) 965500 2=MFG Crosswind V2 965500 2.GUID={49EFA990-7FCC-11E9-8001-444553540000} 965500 ------------------------------------------------------------------- Have you seen this before> Any thoughts as to what would be the issue? Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 13, 2020 Report Share Posted June 13, 2020 44 minutes ago, jskibo said: I enabled the logging and you're right, it seem to keep reconnecting the USB device as it repeats the "reconnecting" for another 10+ times before I don't see that in the log section you provided. This is repeated control is a concern in that part of the log: 45 minutes ago, jskibo said: 964359 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET This isn't a control I've ever used, nor is it programmed into any of my drivers. All my PFC radios only handle the usual frequency spacing in any case. At the time the PFDHid driver was made, control 68065 was beyond the highest numbered one known -- "ADF2 STBY SET" at 68039. I think it must be new for P3d5 because it isn'tin my P3D4.5 list. However, the question here is: why is is being sent and why so often? Looks like about 12 times per second. Is it something you've programmed? I don't suppose that's the reason for your problems, though it could well be related, but I don't really see anything else in that log segment. That device reconnection at the end of your log extract is presumably relevant, but that is actually 10 minutes after you started off. Do you have more, closer, later on? Could it be that with hands off the controls the USB devices are going to sleep? Have you turned off power management for every USB device you can find in Windows device manager? If not, try that -- Windows has a habit of turning off power for less used USB devices unless you stop it! Pete Link to comment Share on other sites More sharing options...
jskibo Posted June 13, 2020 Author Report Share Posted June 13, 2020 Pete, I had Power management off in the device settings and went to the Registry and killed it there too (and rebooted) for the latest run. I haven't programmed anything. I do have a set of Propwash radios but they aren't loaded for any of these tests. This test I pulled up the FSUIPC window and watched the radios scroll by constantly like you saw. Only thing I am now noticing is it doesn't take AP to trigger it. Anytime I touch the electric trim I get a pause in the sim for 2-4 sec then it continues. Log is 211k, from a 1-2 minute flight. Here's a small segment. I'm going to try removing anything USB except Cirrus II, Mouse, Keyboard and the Dongle for Fly Elise warping 265515 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -131 (0xffffff7d) AXIS_AILERONS_SET 265515 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -6012 (0xffffe884) AXIS_ELEVATOR_SET 265593 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 265593 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 265750 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 265750 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 265781 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -5461 (0xffffeaab) AXIS_ELEVATOR_SET 265828 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -4772 (0xffffed5c) AXIS_ELEVATOR_SET 265921 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -4313 (0xffffef27) AXIS_ELEVATOR_SET 265921 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 265921 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 266015 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -3763 (0xfffff14d) AXIS_ELEVATOR_SET 266093 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 266093 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 266156 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -3442 (0xfffff28e) AXIS_ELEVATOR_SET 266265 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 266265 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 266296 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -3212 (0xfffff374) AXIS_ELEVATOR_SET 266359 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -2661 (0xfffff59b) AXIS_ELEVATOR_SET 266437 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 266437 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 266500 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -2432 (0xfffff680) AXIS_ELEVATOR_SET 266593 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 266593 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 266765 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 266765 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 266765 *** AXIS: Cntrl= 65706 (0x000100aa), Param= 1293 (0x0000050d) ELEVATOR_TRIM_SET 266796 *** EVENT: Cntrl= 65814 (0x00010116), Param= 0 (0x00000000) AP_APR_HOLD_OFF 266796 *** EVENT: Cntrl= 65813 (0x00010115), Param= 0 (0x00000000) AP_LOC_HOLD_OFF 266859 *** AXIS: Cntrl= 65706 (0x000100aa), Param= 1439 (0x0000059f) ELEVATOR_TRIM_SET 267046 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET 267578 -------------------------------------------------------------------- 267578 ***** HID USB device reconnected: re-initialising FSUIPC connections 267578 HID: Vendor=0689, Product=C200 (Version 2.0) 267578 Manufacturer= Precision Flight Controls, Inc. 267578 Product= PFC Cirrus II Pro 267578 Serial Number= PFC Cirrus II Pro 267578 ---------------------- Joystick Device Scan ----------------------- 267578 Product= MFG Crosswind V2 267578 Manufacturer= MFG 267578 Serial Number= MFG500002 267578 Vendor=16D0, Product=0A38 (Version 33.1) 267578 GUIDs returned for product: VID_16D0&PID_0A38: 267578 GUID= {49EFA990-7FCC-11E9-8001-444553540000} 267578 Details: Btns=2, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R4096,U0,V0,X4096,Y4096,Z0 267578 Product= PFC Cirrus II Pro 267578 Manufacturer= Precision Flight Controls, Inc. 267578 Vendor=0689, Product=C200 (Version 2.0) 267578 ------------------------------------------------------------------- 267593 Device acquired for use: 267593 Joystick ID = 2 (Registry okay) 267593 2=MFG Crosswind V2 267593 2.GUID={49EFA990-7FCC-11E9-8001-444553540000} 267593 Device acquired for use: 267593 Joystick ID = 2 (Registry okay) 267593 2=PFC Cirrus II Pro 267593 2.GUID={49EFA990-7FCC-11E9-8001-444553540000} 267593 ------------------------------------------------------------------- 268046 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 268046 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 268062 *** AXIS: Cntrl= 65706 (0x000100aa), Param= -69 (0xffffffbb) ELEVATOR_TRIM_SET 268062 *** EVENT: Cntrl= 66416 (0x00010370), Param= -1 (0xffffffff) PAN_VIEW 268093 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -1698 (0xfffff95e) AXIS_ELEVATOR_SET 268093 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 1 (0x00000001) FUEL_SELECTOR_SET 268093 *** EVENT: Cntrl= 66523 (0x000103db), Param= 1 (0x00000001) FUEL_SELECTOR_2_SET 268093 *** EVENT: Cntrl= 66568 (0x00010408), Param= 1 (0x00000001) FUEL_SELECTOR_3_SET 268093 *** EVENT: Cntrl= 66576 (0x00010410), Param= 1 (0x00000001) FUEL_SELECTOR_4_SET 268109 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 268109 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 268109 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET 268109 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET Link to comment Share on other sites More sharing options...
jskibo Posted June 13, 2020 Author Report Share Posted June 13, 2020 New test. The " 268109 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET" only happens when running Alabeo or Carenado aircraft, I tried PA44, PA34 and PA32 and all cause that spamming. F1 KingAir (no cockpit in P3DV5) there was a momentary pause the first time I used trim, but none afterwards. Couldn't set autopilot as I had no cockpit Stock Mooney Bravo had the results pinned to this message (I edited out a few zoom and pan commands to make it fit). I watched in the FSUIPC window as the Cirrus repeatedly disconnected and reconnected. In fact the rudders did too but they are on a different hub. USB devices connected. MFG Rudders, Cirrus II Pro, Corsair Keyboard, Corsair Mouse, Fly Elise Warping dongle. Keyboard and mouse directly to computer, Cirrus II and MFG rudders each on separate powered hubs only device. Cirrus II power management off via device manager and registry entry New Text Document.txt Link to comment Share on other sites More sharing options...
jskibo Posted June 13, 2020 Author Report Share Posted June 13, 2020 Tried it in P3DV4.5 No radio spamming in any plane Many disconnects and reconnects when engaging autopilot Attached is a smaller edited to fit sample of what just repeats throughout the log. V4.5 did not lock up and crash like V5 did, it was just a lot of constant pauses and stuttering opps can't attach. Most of below is when autopilot engaged and Cirrus running electric trim. The first couple are me using electric trim without autopilot 544406 -------------------------------------------------------------------- 544406 ***** HID USB device reconnected: re-initialising FSUIPC connections 544406 HID: Vendor=0689, Product=C200 (Version 2.0) 544406 Manufacturer= Precision Flight Controls, Inc. 544406 Product= PFC Cirrus II Pro 544406 Serial Number= PFC Cirrus II Pro 544406 ---------------------- Joystick Device Scan ----------------------- 544422 Product= PFC Cirrus II Pro 544422 Manufacturer= Precision Flight Controls, Inc. 544422 Vendor=0689, Product=C200 (Version 2.0) 544422 GUIDs returned for product: VID_0689&PID_C200: 544422 GUID= {8F3D9370-AB42-11EA-8001-444553540000} 544422 Details: Btns=16, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U1023,V1023,X1023,Y1023,Z1023 544469 Joystick ID = 0 (Registry okay) 544469 0=PFC Cirrus II Pro 544469 0.GUID={8F3D9370-AB42-11EA-8001-444553540000} 549375 ***** HID USB device reconnected: re-initialising FSUIPC connections 549375 HID: Vendor=0689, Product=C200 (Version 2.0) 549375 Manufacturer= Precision Flight Controls, Inc. 549375 Product= PFC Cirrus II Pro 549375 Serial Number= PFC Cirrus II Pro 550484 ***** HID USB device reconnected: re-initialising FSUIPC connections 550484 HID: Vendor=0689, Product=C200 (Version 2.0) 550484 Manufacturer= Precision Flight Controls, Inc. 550484 Product= PFC Cirrus II Pro 550484 Serial Number= PFC Cirrus II Pro 551906 ***** HID USB device reconnected: re-initialising FSUIPC connections 551906 HID: Vendor=0689, Product=C200 (Version 2.0) 551906 Manufacturer= Precision Flight Controls, Inc. 551906 Product= PFC Cirrus II Pro 551906 Serial Number= PFC Cirrus II Pro 555187 ***** HID USB device reconnected: re-initialising FSUIPC connections 555187 HID: Vendor=0689, Product=C200 (Version 2.0) 555187 Manufacturer= Precision Flight Controls, Inc. 555187 Product= PFC Cirrus II Pro 555187 Serial Number= PFC Cirrus II Pro 556515 ***** HID USB device reconnected: re-initialising FSUIPC connections 556515 HID: Vendor=0689, Product=C200 (Version 2.0) 556515 Manufacturer= Precision Flight Controls, Inc. 556515 Product= PFC Cirrus II Pro 556515 Serial Number= PFC Cirrus II Pro 559750 ***** HID USB device reconnected: re-initialising FSUIPC connections 559750 HID: Vendor=0689, Product=C200 (Version 2.0) 559750 Manufacturer= Precision Flight Controls, Inc. 559750 Product= PFC Cirrus II Pro 559750 Serial Number= PFC Cirrus II Pro 561047 ***** HID USB device reconnected: re-initialising FSUIPC connections 561047 HID: Vendor=0689, Product=C200 (Version 2.0) 561047 Manufacturer= Precision Flight Controls, Inc. 561047 Product= PFC Cirrus II Pro 561062 Serial Number= PFC Cirrus II Pro 562390 ***** HID USB device reconnected: re-initialising FSUIPC connections 562390 HID: Vendor=0689, Product=C200 (Version 2.0) 562390 Manufacturer= Precision Flight Controls, Inc. 562390 Product= PFC Cirrus II Pro 562390 Serial Number= PFC Cirrus II Pro 563484 ***** HID USB device reconnected: re-initialising FSUIPC connections 563500 HID: Vendor=0689, Product=C200 (Version 2.0) 563500 Manufacturer= Precision Flight Controls, Inc. 563500 Product= PFC Cirrus II Pro 563500 Serial Number= PFC Cirrus II Pro 565000 -------------------------------------------------------------------- 565000 ***** HID USB device reconnected: re-initialising FSUIPC connections 565000 HID: Vendor=0689, Product=C200 (Version 2.0) 565015 Manufacturer= Precision Flight Controls, Inc. 565015 Product= PFC Cirrus II Pro 565015 Serial Number= PFC Cirrus II Pro 565015 ---------------------- Joystick Device Scan ----------------------- 568547 ***** HID USB device reconnected: re-initialising FSUIPC connections 568547 HID: Vendor=0689, Product=C200 (Version 2.0) 568547 Manufacturer= Precision Flight Controls, Inc. 568547 Product= PFC Cirrus II Pro 568547 Serial Number= PFC Cirrus II Pro 569562 ***** HID USB device reconnected: re-initialising FSUIPC connections 569562 HID: Vendor=0689, Product=C200 (Version 2.0) 569562 Manufacturer= Precision Flight Controls, Inc. 569562 Product= PFC Cirrus II Pro 569562 Serial Number= PFC Cirrus II Pro 571187 ***** HID USB device reconnected: re-initialising FSUIPC connections 571187 HID: Vendor=0689, Product=C200 (Version 2.0) 571187 Manufacturer= Precision Flight Controls, Inc. 571187 Product= PFC Cirrus II Pro 571187 Serial Number= PFC Cirrus II Pro 574094 ***** HID USB device reconnected: re-initialising FSUIPC connections 574094 HID: Vendor=0689, Product=C200 (Version 2.0) 574094 Manufacturer= Precision Flight Controls, Inc. 574094 Product= PFC Cirrus II Pro 574094 Serial Number= PFC Cirrus II Pro 575203 ***** HID USB device reconnected: re-initialising FSUIPC connections 575203 HID: Vendor=0689, Product=C200 (Version 2.0) 575203 Manufacturer= Precision Flight Controls, Inc. 575203 Product= PFC Cirrus II Pro 575203 Serial Number= PFC Cirrus II Pro 576234 ***** HID USB device reconnected: re-initialising FSUIPC connections 576234 HID: Vendor=0689, Product=C200 (Version 2.0) 576234 Manufacturer= Precision Flight Controls, Inc. 576234 Product= PFC Cirrus II Pro 576234 Serial Number= PFC Cirrus II Pro 579594 ***** HID USB device reconnected: re-initialising FSUIPC connections 579594 HID: Vendor=0689, Product=C200 (Version 2.0) 579594 Manufacturer= Precision Flight Controls, Inc. 579594 Product= PFC Cirrus II Pro 579594 Serial Number= PFC Cirrus II Pro 580656 ***** HID USB device reconnected: re-initialising FSUIPC connections 580656 HID: Vendor=0689, Product=C200 (Version 2.0) 580656 Manufacturer= Precision Flight Controls, Inc. 580656 Product= PFC Cirrus II Pro 580656 Serial Number= PFC Cirrus II Pro 581578 ***** HID USB device reconnected: re-initialising FSUIPC connections 581578 HID: Vendor=0689, Product=C200 (Version 2.0) 581578 Manufacturer= Precision Flight Controls, Inc. 581578 Product= PFC Cirrus II Pro 581578 Serial Number= PFC Cirrus II Pro 584828 ***** HID USB device reconnected: re-initialising FSUIPC connections 584828 HID: Vendor=0689, Product=C200 (Version 2.0) 584828 Manufacturer= Precision Flight Controls, Inc. 584828 Product= PFC Cirrus II Pro 584828 Serial Number= PFC Cirrus II Pro 585781 ***** HID USB device reconnected: re-initialising FSUIPC connections 585781 HID: Vendor=0689, Product=C200 (Version 2.0) 585781 Manufacturer= Precision Flight Controls, Inc. 585781 Product= PFC Cirrus II Pro 585781 Serial Number= PFC Cirrus II Pro 586984 ***** HID USB device reconnected: re-initialising FSUIPC connections 586984 HID: Vendor=0689, Product=C200 (Version 2.0) 586984 Manufacturer= Precision Flight Controls, Inc. 586984 Product= PFC Cirrus II Pro 586984 Serial Number= PFC Cirrus II Pro 590219 ***** HID USB device reconnected: re-initialising FSUIPC connections 590219 HID: Vendor=0689, Product=C200 (Version 2.0) 590219 Manufacturer= Precision Flight Controls, Inc. 590219 Product= PFC Cirrus II Pro 590219 Serial Number= PFC Cirrus II Pro 591281 ***** HID USB device reconnected: re-initialising FSUIPC connections 591281 HID: Vendor=0689, Product=C200 (Version 2.0) 591281 Manufacturer= Precision Flight Controls, Inc. 591281 Product= PFC Cirrus II Pro 591281 Serial Number= PFC Cirrus II Pro 594531 ***** HID USB device reconnected: re-initialising FSUIPC connections 594531 HID: Vendor=0689, Product=C200 (Version 2.0) 594531 Manufacturer= Precision Flight Controls, Inc. 594531 Product= PFC Cirrus II Pro 594531 Serial Number= PFC Cirrus II Pro 595562 ***** HID USB device reconnected: re-initialising FSUIPC connections 595562 HID: Vendor=0689, Product=C200 (Version 2.0) 595562 Manufacturer= Precision Flight Controls, Inc. 595562 Product= PFC Cirrus II Pro 595562 Serial Number= PFC Cirrus II Pro 596719 ***** HID USB device reconnected: re-initialising FSUIPC connections 596719 HID: Vendor=0689, Product=C200 (Version 2.0) 596719 Manufacturer= Precision Flight Controls, Inc. 596734 Product= PFC Cirrus II Pro 596734 Serial Number= PFC Cirrus II Pro Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 13, 2020 Report Share Posted June 13, 2020 2 hours ago, jskibo said: I had Power management off in the device settings and went to the Registry and killed it there too (and rebooted) for the latest run. Do you mean Device Manager, in Control Panel? You need to go through each of the lines under USB down near the end. i think it tends to be those labelled as "hubs" which have the Windows power management. 2 hours ago, jskibo said: I haven't programmed anything. I do have a set of Propwash radios but they aren't loaded for any of these tests. Well something is sending those 68065 controls. i realise they are probably nothing to do with your problem, but they don't make sense so make one suspicious. 2 hours ago, jskibo said: The " 268109 *** EVENT: Cntrl= 68065 (0x000109e1), Param= 1 (0x00000001) COM1_8333HZ_MODE_SET" only happens when running Alabeo or Carenado aircraft, Ah, so it's something internal to those. We'll forget those then. 2 hours ago, jskibo said: USB devices connected. MFG Rudders, Cirrus II Pro, Corsair Keyboard, Corsair Mouse, Fly Elise Warping dongle. Keyboard and mouse directly to computer, Cirrus II and MFG rudders each on separate powered hubs only device. And only the two hub devices keep powering off? Well, that's very suggestive of power problems for sure. Are you sure they have enough power? The electric trim operation will consume more power of course. 2 hours ago, jskibo said: Cirrus II power management off via device manager and registry entry No. The power management I'm talking of isn't against a specific device. Open Control Panel - Device Manager. Scroll right down to "System devices" then, within that, "Universal Serial Bus Controllers". Look in the right-click Properties of every single entry. Some, not all, will have a Power Management tab (mostly the ones labelled as Hubs - there are 13 such entries on this PC I'm using right now). Make sure the "Allow the computer to turn off ..." checkbox is unchecked in every case. 1 hour ago, jskibo said: The first couple are me using electric trim without autopilot That's suspicious. Sounds like there's not really enough power in any case. You might need to beef it up. But PFC are the folks you should ask about the needs of the Cirrus. I don't know. i have a full blown PFC cockpit and that needs almost 3000 watts worth, a cooling system, and an air conditioning plant!, and that's before i get to the computers! All your problems most certainly look related to power in one way or another. I can't think what else could do that, excepting stupid obvious thinks like bad connections or faulty interfaces. That would mainly be a matter of trying different USB sockets and different cables. Pete Link to comment Share on other sites More sharing options...
jskibo Posted June 13, 2020 Author Report Share Posted June 13, 2020 Thanks Pete. I have a note out to PFC support. Odd as they do have issues with their Atmel boards and Win 8 / 10, but the Cypress and Hardware Controller 3 boards are supposed to be compatible. I was more curious if you had seen this behavior before and I appreciate you having a look at it. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now