amnz

Yes It worked normally in each case. You mean to see which number in the fsx control pdf was triggering this issue? What test was it? I only see the 2 tests you told me to do. BTW can't I just set multiple "do nothing assignments" using the same number? (1126) Yes... As you mentioned : "Create a dummy PFC.mcro file for me"

Okay, With just [Macros] everything on the C2 console worked normally, which meant the ANTI ICE switch trigerred carb heat on and off in the A2A cub and in different aircraft. With: [Macros] 1=AntiIce=C1126 ANTI ICE switch does not turn carb heat on and off in the a2a cub and in different aircraft. BTW this is in the PFChid.ini [Config.A2A Piper Cub] MacroFilename=PFC TrimRange=256 ApBeepWave=sound\Caapdis AlertWave=sound\AltAlert

Yes, what is in bold is correct. I removed entries but 1=AntiIce=C65699... And Baro interestingly works again. Yes, sorry, I mean't unlisted' controls. I on purpose assigned them all to unlisted controls. However, I didn't know that those unlisted controls 'may actually do something'!!! If they were unlisted I thought that they would be doing nothing (an innocuous assignment)- which was what I needed. The reason why I need to do this is because I have a throttle quadrant which includes carb heat control. However, carb heat control is automatically activated by the ANTI ICE switch on the C2 pro. I wanted to configure carb heat control to the one in the throttle quadrant so I had to assign ANTIICE to an innocuous assignment in order to make it function properly on the throttle quadrant. I figured that this was an innocuous command because according to a pdf file called 'LIST of FSX controls' 65699 had no control assigned to it therefore it shouldn't conflict with another assignment. I did this for parking brake as well (cubs don't have parking brakes) as well as all the other assignments (because cubs don't have what I listed as well) sinceI thought they might cause a similar problem like the anti ice switch, so thought best to assign them to innocuous commands to prevent similar problems. Now then... What is this innocuous command called??? Where is it in the pdf document LIST of FSX CONTROLS? Also is it possible for you to fix the problem of the macros affecting other aircraft too?

What I am trying to get across is that the macro I created (CUB.mcro) was obviously made to work only with the A2A J3 Cub, yet the CUB.mcro also work for the default fsx planes. the macro file I posted was CUB.mcro, I have not made any other macro file. The act of having a macro file stops the BARO action. There is nothing within the macro file which should have anything to do with the BARO action. Actually every macro within CUB.mcro is assigned to an empty command (on purpose of course :) ) Hopefully this clears things up

As I said, the macros work in the a2a one, but it is also working for all other planes. Furthermore, all other planes don't have functioning kollsman windows as well that i can use via baro knob. I edited my post to show the macrofile, maybe you missed it.

Here is my PChid.ini --- [Options] FlashAPcapts=Yes FlashMarkers=Yes FlashTransponder=Yes FlashADFindicator=Yes DMEuseRMIselect=Yes [Debug] Console=No LogComms=No LogData=No LogDecode=No LogDevices=Yes LogDeviceChanges=Yes LogToDebugger=No LogIPCwrites=No LogMacroNames=No LogTxData=No LogReadCounts=No [Config] TrimRange=256 ApBeepWave=sound\Caapdis AlertWave=sound\AltAlert MacroFilename=PFC [Config.A2A Piper Cub] MacroFilename=CUB TrimRange=256 ApBeepWave=sound\Caapdis AlertWave=sound\AltAlert --- FYI, the macro is being applied to different airplanes as well such as the default 172. Here are the contents of the macro file: [Macros] 1=AntiIce=C65699 2=Battery=C66809 3=Alternator=C66801 4=LandingLight=C66802 5=TaxiLight=C66803 6=Strobe=C66804 7=PitotHeat=C66805 8=FuelBoost=C66808 9=TankSelect=C66809 10=CowlFlaps=C66810 11=Flaps=C66811 12=LandingGear=C66812 13=Nav=C66370 14=ParkingBrake=C65687

Hello again, I am using FSUIPC 4.9.1.0 with PFChid 1.3.30 on W7-64 bit Just did a fresh reinstall of Windows and got everything back up and running. I noticed that a macro I created for the J3 Cub does not allow me to use the BARO knob in the C2 Pro for the kollsman window in the plane. Without the macro it works fine, but that obviously means that I can't assign switches to different functions I need. I also take it that the macro file doesn't restrict the switch functions to those only in the macro file. For example I did not put Magneto in the Macro file, yet I can still use the magnetos normally. So really, my question is how can I still use the BARO whilst using the macro I made at the same time??

Well I think I found the golden solution for anyone who may have a similar problem! There are 2 holes on top of the casing that houses all the circuitry- just blast some air in them et voilà, problem solved!!! Who knew dust would be able to screw up some rudder pedals.

I have disabled controllers in FSX. So its a mechanical problem to do with the pedals in this case? NOTE: Is it normal for the max value in joystick calibration tab to have a value of over 4000??? Almost everything else, the max value is around 1683...

[Axes] 0=1R,256,D,3,0,0,0 1=1U,1,D,7,0,0,0 2=1V,1,D,8,0,0,0 3=17X,1 4=17X,B,13545,16383,66030,0 5=17X,B,-14578,-11998,66029,0 6=17Y,256,D,10,0,0,0 7=17Z,1,D,4,0,0,0 8=17R,256,D,18,0,0,0 9=17U,1,D,26,0,0,0 10=17V,256,D,14,0,0,0 [MacroFiles] 1=PFCCUB [Profile.cub] 1=A2A Piper Cub [JoystickCalibration.cub] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=66731 RudderTrimControl=66732 CowlFlaps1Control=66162 CowlFlaps2Control=66163 CowlFlaps3Control=66164 CowlFlaps4Control=66165 SteeringTillerControl=0 MaxSteerSpeed=60 Throttle=-16384,16383 LeftBrake=-16384,15609 SlopeLeftBrake=-5 RightBrake=-16384,15222 SlopeRightBrake=-5 Aileron=-16384,0,0,16383 Elevator=-16384,0,0,16383 Rudder=-2024,1248,1280,2144 [JoystickCalibration] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=66731 RudderTrimControl=66732 CowlFlaps1Control=66162 CowlFlaps2Control=66163 CowlFlaps3Control=66164 CowlFlaps4Control=66165 SteeringTillerControl=0 MaxSteerSpeed=60 Rudder=-1960,2304,2496,3904 [Keys] 1=32,8,66734,0

Dear Pete, I have to keep on re-calibrating my PFC Cirrus GA pedals every 3 minutes to get them to function normally. Even when I am not touching the pedals, the rudder will automatically jar to one side in the sim and then re-centre (but it doesn't re-centre all the time) This obviously is a very frustrating problem. In FSUIPC (4.907 with PFCHID 1.32) I have set my delta value in the axis assignment tab up to 256 and I still get the same issue. Furthermore, in the joystick calibration section the 'in' and 'out' values constantly fluctuate. I really hope it isn't the potentiometer on the pedals that is wearing out- i've barely had time to use them! Please help if you can :)

It is from A2A simulations so I am pretty sure it isn't a cosmetic switch! I can definitely live without it, but I find it strange how it worked succesfully for the carb heat and not for the fuel shutoff valve. I will probably ask the guys at A2A if they can help out.

Hi, checked logging. Weirdly enough, I only got a recurrence of this: 52229 *** EVENT: Cntrl= 66507 (0x000103cb), Param= 100 (0x00000064) PANEL_ID_OPEN 52291 *** EVENT: Cntrl= 66029 (0x000101ed), Param= 1 (0x00000001) ANTI_ICE_ON 52291 *** EVENT: Cntrl= 66507 (0x000103cb), Param= 100 (0x00000064) PANEL_ID_OPEN 52354 *** EVENT: Cntrl= 66029 (0x000101ed), Param= 1 (0x00000001) ANTI_ICE_ON 52354 *** EVENT: Cntrl= 66507 (0x000103cb), Param= 100 (0x00000064) PANEL_ID_OPEN 52401 *** EVENT: Cntrl= 66029 (0x000101ed), Param= 1 (0x00000001) ANTI_ICE_ON In this case, i couldn't identify what FSX would define as the fuel shutoff control

Hi Pete, The aircraft is a piper cub, it simply has 2 options "on" and "off" - I take it this is called the fuel shutoff control.

I spoke too soon. I am having trouble assigning the alt air control on the console to act as the fuel cut off valve. I went through the list of fsx control documents and tried (TOGGLE_FUEL_VALVE_ALL) (C66493) but that didn't work. I don't know what else the fuel cut off valve could be in that document. FYI, The AltAir macro is supported according to the .csv file

It is what I needed- although its good that you pointed that out because I wanted to configure some other things on the console to different things

Hi Pete, Thanks for your help, I managed to get everything working. All I did was [Macros] 1=AntiIce=66810 [/CODE] AntiIce, I got from the [i]PFCmacroIndex.csv [/i](so the program could read what switch I want to modify) 66810, I got from [i]List of FSX controls.pdf [/i](so I could find the function I wanted that switch to do, in this case it was nothing so that there was no conflict with the carb heat axis I wanted to use instead of the anti ice switch on the console for carb heat) Once again, thank you for quick support Pete and enjoy flying!

Achso! Lets see if I can use my own brain now and the documentation to make progress with my original goal.

One must have lots of patience with me when I try to deal with problems :) I have read this page- where I am stuck is on the first sentence... My question was how do I create a file type .mcro in the first place? Sorry if I wasn't clear on my part. I cannot seem to find anywhere in the manual which details how to do this, but rather find that it only details how to handle these macro files.

Alrighty, I have read the user guide, but I can't' find where it explains how to actually create these non mouse macro files.

Okay, I will have a read of the advanced user guide to see how I will create the necessary macros and report back. Thanks for your help so far

Alright... If I am understanding this correctly (probably not :) ) ..All I need to do is to assign the carb heat to a keypress, and somehow connect this keypress to the console???

Hi, I am confused how I can link the macro to the PFC console? I have attempted to create a macro by starting macro, press the carb heat to 'on' but I don't get the green message which allows me to test it or name it... The carb heat is already linked with the anti ice switch, so perhaps there is some sort of conflict? How can I unlink the switch from the carb heat? Yours in confusion,

Thanks for your response Pete, I will check it out.

Dear Pete, I am using FSUIPC 4.86 with PFCHID 1.30 to use my Cirrus C2 Pro USB console in FSX. (W7 64-bit) I was wondering if there was a way to change the assignments of the different switches on the console. This is because the 'ANTI ICE' switch is controlling the carb heat, which is a problem since my PFC throttle quadrant has a carb heat lever- so even when I configure the carb heat lever axis to control carb heat, it will initially control the action, but then it will change back according to the position of the anti ice switch. (FYI, here is the image of the throttle quadrant: Carb-Heat-Throttle-and-Mix.jpg) Hopefully a simple solution exists? Kindest Regards,