Jump to content
The simFlight Network Forums
Sign in to follow this  
amnz

Macro interfering with RIC knobs on PFC C2 Pro

Recommended Posts

No, it did not fix the problem. Baro not functionning and macros still being applied to other aircraft :(

 

Strange, because since I uploaded it I've managed to reconnect my console, and it works here! It correctly selects the right macro file and removes the previous ones when changing aircraft, and most particularly the "Alternator" macro isn't treated also as the "Alt" macro.

 

Please double check that you placed the replacement DLL into the correct Modules folder BEFORE loading FS. Please show me your FSUIPC4.LOG and PFCHID.LOG files. If those show things to be okay, particularly when changing aircraft, I'll need youto enable some additional logging.

 

Pete

Share this post


Link to post
Share on other sites

Followed your instructions and no baro, and NOW, NOTHING on the c2 pro works in fsx!

 

Its odd how it completely solves it on your end, and makes it worse on mine!

 

FSUIPC4.LOG:

 

********* FSUIPC4, Version 4.91 by Pete Dowson *********

Running inside FSX on Windows Vista
Module base=6E760000
User Name="Dean Michael"
User Addr="pilot4504@gmail.com"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
        0 System time = 14/08/2013 18:32:55
        0 FLT path = "C:\Users\Alex\Documents\Flight Simulator X Files\"
       31 Trying to connect to SimConnect Acc/SP2 Oct07 ...
       31 FS path = "D:\FSX\"
      390 LogOptions=00000000 00000001
      390 SIM1 Frictions access gained
      390 Wind smoothing fix is fully installed
      390 G3D.DLL fix attempt installed ok
      390 SimConnect_Open succeeded: waiting to check version okay
      390 Trying to use SimConnect Acc/SP2 Oct07
     1310 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)
     1310 Initialising SimConnect data requests now
     1310 FSUIPC Menu entry added
     1341 D:\FSX\FLIGHTS\OTHER\FLTSIM.FLT
     1341 D:\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR
     5553 D:\FSX\SimObjects\Airplanes\A2A_PiperJ3\PiperJ3.AIR
     5553 Weather Mode now = Theme
     5553 c:\users\alex\documents\flight simulator x files\Previous Flight.FLT
    19203 Aircraft="A2A Piper Cub"
    19203 System time = 14/08/2013 18:33:14, Simulator time = 13:19:17 (20:19Z)
    26691 Starting everything now ...
    26738 Setting external joystick scanner link ...
    26738   ... Okay!
    28017 Advanced Weather Interface Enabled
    51745 Sim stopped: average frame rate for last 29 secs = 51.1 fps
    54990 C:\Users\Alex\AppData\Roaming\Microsoft\FSX\Previous flight.FLT
    62119 System time = 14/08/2013 18:33:57, Simulator time = 13:19:47 (20:19Z)
    62119 *** FSUIPC log file being closed
Average frame rate for running time of 29 secs = 51.0 fps
G3D fix: Passes 9474, Null pointers 0, Bad pointers 0, Separate instances 0
Memory managed: 31 Allocs, 31 Freed
********* FSUIPC Log file closed ***********
 
 
PFCHID.LOG:
 
********* PFChid, Version 1.34 by Pete Dowson *********
       16: Error 6 [00000006] returned on HidD_GetAttributes:  (\\?\hid#vid_046d&pid_c52e&mi_00#7&b26e42b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030})
       16: Error 6 [00000006] returned on HidD_GetAttributes:  (\\?\hid#vid_046d&pid_c52e&mi_01&col01#7&2efe21ed&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030})
  
  Manufacturer= Precision Flight Controls, Inc.
  Product= PFC MFD Rudder Pedals
  Vendor=0689, Product=D010
  Serial Number= 
       32: ... Ok, added as device #1
     2543: Device #1 Write: Class 07, Cmd 0010, Indx 0, Data { 00 }**** FAILED: buffer full!
     2871: Device #1 Write: Class 06, Cmd 0020, Indx 1, Data { 00 }**** FAILED: buffer full!
     3214: Device #1 Write: Class 06, Cmd 001E, Indx 1, Data { 00 }**** FAILED: buffer full!
     3557: Device #1 Write: Class 09, Cmd 000F, Indx 0, Data { 00 }**** FAILED: buffer full!
     3900: Device #1 Write: Class 06, Cmd 0022, Indx 0, Data { 00 }**** FAILED: buffer full!
     4244: Device #1 Write: Class 09, Cmd 000F, Indx 0, Data { 00 }**** FAILED: buffer full!
     4587: Device #1 Write: Class 06, Cmd 001E, Indx 0, Data { 00 }**** FAILED: buffer full!
     4930: Device #1 Write: Class 06, Cmd 0021, Indx 0, Data { 00 }**** FAILED: buffer full!
     5273: Device #1 Write: Class 06, Cmd 001E, Indx 0, Data { 00 }**** FAILED: buffer full!
     5616: Device #1 Write: Class 06, Cmd 0021, Indx 1, Data { 00 }**** FAILED: buffer full!
     5960: Device #1 Write: Class 06, Cmd 001E, Indx 1, Data { 00 }**** FAILED: buffer full!
     6303: Device #1 Write: Class 09, Cmd 000F, Indx 0, Data { 00 }**** FAILED: buffer full!
     6646: Device #1 Write: Class 06, Cmd 0022, Indx 0, Data { 00 }**** FAILED: buffer full!
     6974: Device #1 Write: Class 09, Cmd 000F, Indx 0, Data { 00 }**** FAILED: buffer full!
     7332: Device #1 Write: Class 06, Cmd 0022, Indx 0, Data { 00 }**** FAILED: buffer full!
     7691: Device #1 Write: Class 07, Cmd 000E, Indx 0, Data { 00 }**** FAILED: buffer full!
     8019: Device #1 Write: Class 06, Cmd 001F, Indx 1, Data { 00 }**** FAILED: buffer full!
     8378: Device #1 Write: Class 07, Cmd 0010, Indx 0, Data { 00 }**** FAILED: buffer full!
     8705: Device #1 Write: Class 06, Cmd 0021, Indx 0, Data { 00 }**** FAILED: buffer full!
     9064: Device #1 Write: Class 06, Cmd 0022, Indx 0, Data { 00 }**** FAILED: buffer full!
     9407: Device #1 Write: Class 07, Cmd 000D, Indx 0, Data { 00 }**** FAILED: buffer full!
     9750: Device #1 Write: Class 06, Cmd 001F, Indx 1, Data { 00 }**** FAILED: buffer full!
    10094: Device #1 Write: Class 07, Cmd 0010, Indx 0, Data { 00 }**** FAILED: buffer full!
    10421: Device #1 Write: Class 06, Cmd 0020, Indx 0, Data { 00 }**** FAILED: buffer full!
    10780: Device #1 Write: Class 06, Cmd 001E, Indx 0, Data { 00 }**** FAILED: buffer full!
    11108: Device #1 Write: Class 06, Cmd 0021, Indx 1, Data { 00 }**** FAILED: buffer full!
    11466: Device #1 Write: Class 06, Cmd 001E, Indx 1, Data { 00 }**** FAILED: buffer full!
    11794: Device #1 Write: Class 06, Cmd 0021, Indx 1, Data { 00 }**** FAILED: buffer full!
    12153: Device #1 Write: Class 06, Cmd 0022, Indx 0, Data { 00 }**** FAILED: buffer full!
    12480: Device #1 Write: Class 09, Cmd 000F, Indx 0, Data { 00 }**** FAILED: buffer full!
    12839: Device #1 Write: Class 06, Cmd 0022, Indx 1, Data { 00 }**** FAILED: buffer full!
    13198: Device #1 Write: Class 07, Cmd 000E, Indx 0, Data { 00 }**** FAILED: buffer full!
    13526: Device #1 Write: Class 06, Cmd 001F, Indx 1, Data { 00 }**** FAILED: buffer full!
    13884: Device #1 Write: Class 06, Cmd 001E, Indx 0, Data { 00 }**** FAILED: buffer full!
    14212: Device #1 Write: Class 06, Cmd 0021, Indx 0, Data { 00 }**** FAILED: buffer full!
    14571: Device #1 Write: Class 06, Cmd 001E, Indx 0, Data { 00 }**** FAILED: buffer full!
    14898: Device #1 Write: Class 06, Cmd 0021, Indx 1, Data { 00 }**** FAILED: buffer full!
    15242: Device #1 Write: Class 06, Cmd 001E, Indx 1, Data { 00 }**** FAILED: buffer full!
    15585: Device #1 Write: Class 06, Cmd 0021, Indx 1, Data { 00 }**** FAILED: buffer full!
    15928: Device #1 Write: Class 06, Cmd 001E, Indx 1, Data { 00 }**** FAILED: buffer full!
    16271: Device #1 Write: Class 09, Cmd 000F, Indx 0, Data { 00 }**** FAILED: buffer full!
    16614: Device #1 Write: Class 06, Cmd 0022, Indx 0, Data { 00 }**** FAILED: buffer full!
    16942: Device #1 Write: Class 09, Cmd 000F, Indx 0, Data { 00 }**** FAILED: buffer full!
    17301: Device #1 Write: Class 06, Cmd 0022, Indx 0, Data { 00 }**** FAILED: buffer full!
    17644: Device #1 Write: Class 07, Cmd 000D, Indx 0, Data { 00 }**** FAILED: buffer full!
    17987: Device #1 Write: Class 06, Cmd 001F, Indx 1, Data { 00 }**** FAILED: buffer full!
    18330: Device #1 Write: Class 07, Cmd 0011, Indx 0, Data { 00 }**** FAILED: buffer full!
    18658: Device #1 Write: Class 06, Cmd 0020, Indx 1, Data { 00 }**** FAILED: buffer full!
    19017: Device #1 Write: Class 06, Cmd 001E, Indx 1, Data { 00 }**** FAILED: buffer full!
    19344: Device #1 Write: Class 06, Cmd 0021, Indx 1, Data { 00 }**** FAILED: buffer full!
    19703: Device #1 Write: Class 06, Cmd 001E, Indx 1, Data { 00 }**** FAILED: buffer full!
    20031: Device #1 Write: Class 09, Cmd 000F, Indx 0, Data { 00 }**** FAILED: buffer full!
    20390: Device #1 Write: Class 06, Cmd 001E, Indx 1, Data { 00 }**** FAILED: buffer full!
    20717: Device #1 Write: Class 06, Cmd 0021, Indx 1, Data { 00 }**** FAILED: buffer full!
    21060: Device #1 Write: Class 06, Cmd 001E, Indx 1, Data { 00 }**** FAILED: buffer full!
    21404: Device #1 Write: Class 09, Cmd 000F, Indx 0, Data { 00 }**** FAILED: buffer full!
    21747: Device #1 Write: Class 06, Cmd 0022, Indx 0, Data { 00 }**** FAILED: buffer full!
    22090: Device #1 Write: Class 09, Cmd 000F, Indx 0, Data { 00 }**** FAILED: buffer full!
    22433: Device #1 Write: Class 06, Cmd 0022, Indx 0, Data { 00 }**** FAILED: buffer full!
    22761: Device #1 Write: Class 09, Cmd 000F, Indx 0, Data { 00 }**** FAILED: buffer full!
    23120: Device #1 Write: Class 06, Cmd 0022, Indx 0, Data { 00 }**** FAILED: buffer full!
    23463: Device #1 Write: Class 07, Cmd 000D, Indx 0, Data { 00 }**** FAILED: buffer full!
    23790: Device #1 Write: Class 06, Cmd 001F, Indx 0, Data { 00 }**** FAILED: buffer full!
    24149: Device #1 Write: Class 07, Cmd 0011, Indx 0, Data { 00 }**** FAILED: buffer full!
    24477: Device #1 Write: Class 06, Cmd 0020, Indx 1, Data { 00 }**** FAILED: buffer full!
********* PFChid Log file closed *********
 

Share this post


Link to post
Share on other sites

Followed your instructions and no baro, and NOW, NOTHING on the c2 pro works in fsx!

Its odd how it completely solves it on your end, and makes it worse on mine!

 

The PFCHID log shows a problem with the PFC rudder pedals, and no connection at all to the console itself. This is a USB interface problem -- nothing in any of that area is any different whatsoever in the DLL. You need to reset the thing, power it down, unplug it, plug it back in and power it back up.

 

The DLL is most certainly not worse in any area. All it is doing differently is comparing the macro name properly (i.e. "Alt" with "Alternator" instead of Alt with a truncatesd Alt from Alternator), and is reads the aircraft name more often. No other changes from 1.33 whatsoever.

 

Let me know when you get the device connected properly again.

 

Pete

Share this post


Link to post
Share on other sites

I followed your instructions. I loaded up PFC Test GUI (which is a PFC application to see if functions on your PFC hardware are indeed working) and everything checked out fine.

 

However, as soon as I load up a plane in flightsim absolutely nothing works! I have never experienced this problem before.

Share this post


Link to post
Share on other sites

I followed your instructions. I loaded up PFC Test GUI (which is a PFC application to see if functions on your PFC hardware are indeed working) and everything checked out fine.

 

However, as soon as I load up a plane in flightsim absolutely nothing works! I have never experienced this problem before.

 

 

By "absolutely nothing works" do you mean FS freezes or crashes, or only that no devices do anything?  If so, it sounds like something is screwing up the USB device interface. Try unplugging all USB devices, check it then works, then replace them one at a time.

 

If you want to prove it isn't related to PFCHID 1.34 you could always try 1.33 again.

 

Pete

Share this post


Link to post
Share on other sites

By "absolutely nothing works" do you mean FS freezes or crashes, or only that no devices do anything?  If so, it sounds like something is screwing up the USB device interface. Try unplugging all USB devices, check it then works, then replace them one at a time.

 

No devices working

 

It isn't to do with PFCHID 1.33.

 

Windows is giving me an error: "one of the usb devices attached to this computer has malfunctioned, and Windows does not recognize it"

 

I really don't know what to do now... Its like its one problem after another.

Share this post


Link to post
Share on other sites
Windows is giving me an error: "one of the usb devices attached to this computer has malfunctioned, and Windows does not recognize it"

I really don't know what to do now... Its like its one problem after another.

 

I assume you've eliminated an in-memory USB driver corruption by rebooting the PC? If not, that's certainly the first step.

 

You'll need to unplug the devices, check things are then okay, and add them back one at at time. Don't forget any hubs you might be using -- they can play up too.

 

I'm afraid I'm going to be busy this evening, but I'm around tomorrow again. I'll try to get my PFC console more accessible -- currently it is difficult for me to connect to it with a decent PC. At least if I have it connected to my development system I'll be able to advise better about exactly what to look at and so on. I don't have any pedals I can connect to it though. Mostly my PFC involvement is with the full 737NG cockpit (which they don't do any more).

 

Regards

Pete

Share this post


Link to post
Share on other sites

Well here's a quick but probably insignificant update:

 

I did manage to eventually get windows to recognize the PFC devices. PFC test GUI confirmed this. Then loaded FSX- and the C2 actually worked! One second later, it stopped functioning  :mrgreen: Its just odd how FSX is deciding to refuse to notice the PFC hardware. After quitting FSX, if I try to unplug and then replug the C2 back into the computer, Windows doesn't recognize it! This way over my head now.

 

BTW in device manager I turned off 'Allow to turn off this USB device to save power' on all USB devices and still nothing works.

 

Could this somehow be a registry problem. Do you think an entire FSX reinstall would fix it?

Share this post


Link to post
Share on other sites
I did manage to eventually get windows to recognize the PFC devices. PFC test GUI confirmed this. Then loaded FSX- and the C2 actually worked! One second later, it stopped functioning  :mrgreen: Its just odd how FSX is deciding to refuse to notice the PFC hardware. After quitting FSX, if I try to unplug and then replug the C2 back into the computer, Windows doesn't recognize it! This way over my head now.

 

Mine too I'm afraid.

 

BTW in device manager I turned off 'Allow to turn off this USB device to save power' on all USB devices and still nothing works.

 

That probably has no effect on a device like this in any case as when connected iand switched on it is always active, and it doesn't draw power from the USB connection in any case unlike joysticks etc.

 

Could this somehow be a registry problem. Do you think an entire FSX reinstall would fix it?

 

I think that's rather drastic, and i don't think there's any permanent Registry stuff specific to these devices which matters.  You could see if you could actually uninstall the devices in the Device Manager, so that they get freshly "installed" next time they connect, but that may need them to be recognised again first.

 

Is the problem the same for both the rudder pedals and the console? Are they recognised as separate? Do the pedals pluf into the console or are they a USB device in their own right?

 

I assume you've tried different USB sockets on the PC? Different USB cables? Do you have access to any other PC you coud check things out on, maybe with the PFC Test GUI program (to save installing FS).

 

Try also checking all HID devices using my HidScanner program -- you'll find it with the Lua library stuff in Download Links subforum. That identifies all HID devices connected according to the Registry, and enumeates ther main properties.

 

Failing all this I would tend to suspect an intermittently failing hardware component, maybe in the device or on the PC motherboard. Maybe PFC tech support can help narrow it down.

 

Pete

Share this post


Link to post
Share on other sites

Failing all this I would tend to suspect an intermittently failing hardware component, maybe in the device or on the PC motherboard. Maybe PFC tech support can help narrow it down.

 

Pete

 

[sARCASM ON] Well I talked to PFC and very conveniently the controller chip on the C2 decided to die , oh joy! :razz: [sARCASM OFF]

 

Well thanks for all of your time and effort Pete anyway, and as always for your top-notch support.

 

AlexM

Share this post


Link to post
Share on other sites

[sARCASM ON] Well I talked to PFC and very conveniently the controller chip on the C2 decided to die , oh joy! :razz: [sARCASM OFF]

 

Is the 'sarcasm' bit the "very conveniently", and the C2 is really bust? If so can PFC send you a replacement part, or has the whole thing got to go back? Are you in the US?

 

Regards

Pete

Share this post


Link to post
Share on other sites

Please replace PFCHid.DLL version 1.34 with 1.35: PFChid135.zip. I just found a silly typo in the code which can, in certain circumstances, slow FS down, even possibly to a crawl!

 

Hope you are making progress with the C2 Pro. If it responds now to the PFCTest GUI, please try now with this updated DLL.

 

Regards

Pete

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.