jetblst

Well done!!

I finally figured it out. What I need(ed) is a three way switch. It dawned on me that with my new Saitek Yoke I have a spare HAT switch since the X52 HAT is being used to PAN view. So I assigned my FSUIPC Mouse Macro ( LT WS HT ON) to one button in the HAT switch and LT WS HT OFF to another. Wonderful!! It works. Now, the Pro Flight Yoke also came with a MODE switch so I will now assign these new Mouse Macros to keypresses that way Mode 1 will be the Left side on and off and Mode 2 will be the Right side on and off. (Button 32 and button 34). So how I do this is to assign the delete key to LT WS HT ON. Then assign Cntl Del to RT WS HT ON. Then the Insert key for LT WS HT OFF and Cntl Insert for RT WS HT OFF. Then I use the Saitek Profile software to program Del and Insert in mode 1 and Cntl Del and Insert in mode 2 to the same buttons 32 and button 34 respectively. Now I can use the same controller switch to operate two different Panel (three way) switches simply by switching modes on the Proflight Yoke. (I just picked Del and Insert keys randomly, and deactivated all instances of it in the FSX controls area). In the future I'll try to refrain from asking a question when tired :razz: Sorry for the confusion Pete!

Sorry Pete for being unclear. With the Saitek X52, the three position rotary mode switch allows different programming for the same buttons. To accomplish this however, ALL your assignments must be in the form of a keyboard command. If one does not wish to go to that length then simply assign controls to buttons or switches. and your good to go. f you take advantage of asigning controls to keypresses you can get a lot more asigned to your controller. This is why I use keypresses, then asign those keypresses to the X52. (F1 = Nav Lights, Cntl F1 = AOA Heat, Shft F1= Boost Pumps on) They are all on the T-1 button on my X52 just in different modes. So with the Mouse Macros I made a macro for Windshield Heat ON and another for Windshield Heat OFF. So as a button, one push would go from LO to OFF then another push would go from OFF to HI. IF I push the button again, nothing happends and the WS Heat is stuck in HI. So I created an OFF Macro which does the reverse. My question: Is this the only procedure I can do via Mouse Macros to get a three way switch to work? I hope this was more clear. Again sorry be sending you out to sea. I like that expression! LOL

Hi Pete, As I have said, I have had a lot of success with the Mouse Macros. I've run into a little hitch. I have a three way switch. Windshield Heat. I have HIGH OFF LO choices. Now if I want, I can simply make a Macro to turn it on, from LO to OFF to HIGH as much as I would like. Visa Versa of course. This however will take up 4 buttons or levers, and there are other ways around it. So what I want to do is simply use these as Key Presses then asign that to my controller. The following you are explaing to us how to set up a spring loaded switch which is fantastic. My three way switch is not. Here is a clip from the instructions Before we start experimenting, prepare the file for multiple-line macros, as follows: [Macros] Module="XXXXXXXX.GAU" 1=APU Start=RX70280*X8bcc 2=APU Normal= 2.1=RX70280*X8bcc 3=APU Off=RX70310*X8bcc 4=L Eng Start 4.1=RX4a470*X8bcc 5=R eng Start 5.1=RX4a4f0*X8bcc 6=XTIE 6.1=RX66560*X8bcc All I’ve done here is changed the lines we know don’t work by leaving the name on its own line, and inserting the extra .1 lines with the mouse action assigned. The file is actually identical in its effect to the original, but now we can add more actions. With the “APU Normal” switch, we want it to return to the normal position on button “leave” or “release” from either “Start” or “Off”. So the first thing to do is extend its part with the Off code as well, so it does both: 2=APU Normal= 2.1=RX70280*X8bcc 2.2=RX70310*X8bcc By experimentation, the solution for this is the “leave” code, 11:... Here is my Macro [Macros] Module="xesbj400antiice.GAU" 1=R WSHLD HT LO 1.1=R7 2=R WSHLD HT OFF 2.1=R6 3=R WSHLD HT HIGH 3.1=R6 I got to the part where we are using 11 or 17 to return the switch. I don't want to have FSUIPC return the switch I want to leave it where I set it. QUESTION. Will I simply need to use 4 keys? One to turn the switch on another to turn it off, then another switch for the other side of the windshield? I could always use say F6 (on) then Cntl F6 (off), and F7 Cntrl F7.etc? What do you suggest?

Ok, thanks Pete. While getting to know how to use the logging features and creating the Mouse Macros, I saw those assignments so I am eager to try this out. Thanks again!

Where can I read more on the L:vars? Is that in the programmers instructions?

Hi Defcon, Here is what you need to do. First you will need to assign your Axis Correctly. Go into FSUIPC interface - Assign Axis - and you will want to move your throttle to ensure it works. Now select under Type of Action, Send direct to FSUIPC Calibration. Then you will want to assign Throttle 1 and Throttle 2. in two of the 4 choices you have. Now go to Joystick Calibration. (Tab to the right of Axis Assignment). Go to page 3, there you will notice the movement of your throttle. Now move your throttle full forward then full aft. You should have a friction detent about 2/3rds from full forward back. Move your throttle to be just forward of the friction point. Do not move your throttle at all. Simply click on the Idle tabs (twice for each throttle) 1 and 2. Now move your throttle full aft. Come forward about an half inch. Click on the Reverse tabs twice for each throttle. The idea is you want to have precisely the same values for both throttles in idle and in the reverse boxes. If not, start over and do this until you do. Try it out in your jet of choice. You can vary the reverse points now that you are using those thottle settings good luck.

After reading, logging, reading, watching Fox News, then reading some more it dawned on me. I wasn't quite understanding the Mouse Macros. So I went back and re read it once more. Key word. Mouse Traps, and success I got the levers to work. That's not all. While reading Appendix: Axis assignment in FSUIPC4 – 10x2 Commandments, I thought why stop at AXIS. Why not delete all the function key asignments from F1 - F8? ( I like the F9 - F12 functions. LOL I also deleted the Cntrl Function assignments as well as the Shift Function assignments. The idea is that first to make the Macros of all of my overhead switches. There are quite a few of them on the Hawker 400 XP. So I did. I then got the idea to asign the macros to key presses, THEN asign my buttons to key presses. Here is the cool part. I finally was able to get my MODE switch to work on my X52!! Something I had been trying to do for a long time. What I needed was the correct driver WITH the correct programming software. If they are mismatched the X52 MODE switch will not work in FSX. Well it does now. So instead of only 6 T-switches I now have 18. Add that to the 6 T-Switches on the Proflight Yoke I now have 36 T-switches between the two. They gave us a handy USB outlet on on the Saitek yoke that allows us to hook up the X52 and the Yoke to work together. :) Instead of the POV hat switches I can simply use the joystick from the X52 to look around with. Now I have to figure out what to do with the two hat switches. A good place to be!! So I now can manipulate EVERY switch on my overhead panel with my controllers instead of having to use the mouse! Not as fancy as your cockpit Pete but that's ok! Thanks for the ideas and the help!!

GREAT!! Thanks for taking the time on this Pete. I get back to the forum when I get it working. I do have a request to the originator, about the assignable key press, however it is an older model and I understand that particular programmer has moved on. Ugh. LOL. I see what I can do.

I read most of the instructional documentation (advanced users, lua, etc) and I have read through the FAQ's and I appologize as I think this is going to be simple. I just need a push in the right direction. The Hawker 400 XP landing lights DO NOT operate via the L key or the Cntrl-L keyboard functions. The only way I can turn them on is in flight with my mouse. I have not found the keyboard command to make that happen. 1. Is there a way to find out from addon model to addon model how a system (landing lights in this case) is actuated? How the author may have assigned it to operate? The main FSX Cntl-L does turn on most of the lights in the 400XP but does not turn on the tail flood, recog, or landing lights. So if I knew how to find out what was assigned in this model maybe it would make it easier to assign this to a button or axis on my controller? I have the Saitek X52 as well as now the Saitek Proflight Yoke and Thottles. 2. IF there is no way to find that out. THEN what is my BEST approach to make them work with my controller? Offset, Lua, something else? I'll go read up on what is the best way I am just lost as to what that method is. Thanks

Absolutely, thanks again. I posted a 'how to' over at the Radar Contact page of AVSIM. I've seen quite a few questions about this, and I would have never put TCAS commands and how that effects Radar Contact phraseology. Ever. That is why I missed this to begin with. So, thanks again Pete I appreciate it! http://forum.avsim.net/topic/404648-airline-callsigns-fsuipc-can-help-radar-contact-recognize-them/

There it is. Ok, Thanks Pete. I don't deal with these settings and programming everyday, so when I did read the advanced user's guide, I missed this entirely. I really appreciate your efforts in answering this!

Ah, ok. Thanks for clearing that up.

I appologize Pete as I wasn't as clear as I should have been! I am a proud registered user and have been for years now. Can you detail how to do this in the ini? I just could not remember the terminology of the flight vs. type. I would appreciate it. Thanks. Sorry for the confusion. Mark

EXACTLY!! That was it. I read somewhere, that you can change the ini file, (must be another file) so that "flight" would render Callsigns instead of N numbers.Thanks so much Kihew. Well at least I was reminded that I didn't read it here. http://forum.avsim.net/topic/382793-call-signs-in-fsx-with-ultimate-traffic/ I HAD gone to the RC site first looking for this answer but JD had only mentioned reference to his manua, and that had other topics to do with FSUIPC, not what I was looking for. So I figured Pete might know about it, or point me in the right direction. Ooops. If I find it and get it to work I post something.

Sorry if I was unclear. This is how I have my FSUIPC.INI set up for buttons of course. [buttons] Buttonrepeat=5,0 //20,10 DEFAULT 1=P0,6,C65752,0 2=P0,21,K49,8 3=P0,20,K55,8 4=P0,22,K50,8 5=P0,19,K191,11 6=P0,2,C65759,0 7=P0,3,C65758,0 8=P0,1,C65861,0 9=P0,4,C65570,0 14=P0,0,C66654,0 16=P0,14,C65567,0 17=P0,5,K65,8 18=R0,17,C65615,0 19=R0,15,C65607,0 Is there a way to have the left/right buttons on my mouse have the same setting? (IE 5,0 instead of 20,10)? I understood the part about the delay, and it being a good thing. I simply liked the manner of the faster response of my heading bug. Almost instantly. So I thought there might be a way to do this with my mouse buttons.

Hi Pete, Just for the benefit of people new to FSUIPC, in the Advanced Users Guide there is some very useful information such as Button Repeat, where the User can program the rate at which their button repeats the command. If found this useful in programming my X-52 upper HAT switch. I used the Left and Right portion to set my heading bug. I grew tired of the small delay built in for the heading bug to move. Using the Button Delay programming, I was able to move the heading bug instantaneously instead of that half second delay or so. You can increase the delay or get rid of it all together. Page 15. Ok so, is there a way I can have this same feature when I click on a control with my mouse? Now that the modelers are getting sophistacated with the switchology in the VCcockpits, it would be useful to get rid of that pesky delay when I point at say, the heading dial in my CJ1+. Also, can this be done if I want to use a key on my keyboard say F1 for example? As always thanks in advance for your advice and help! Hope you're doing well!

Hi Pete! I may have my wires crossed here but I thought there was some sort of command, or entry to the FSUIPC.INI file, something, that allows the controllers with Radar Contact to use strictly Real World nomenclature for the Airlines. Forgive me if this has been asked a lot. I can't seem to remember. -OR- Was this something to do with World of AI Aircraft? I recently installed Radar Contact as well as My Traffic -Lite- and I wanted to get rid of the Orbits etc. Thanks Pete!

Hey thanks Pete. I sort of thought that would be the case, but you know way more than I of course so I thought Id ask.

Just a quick question. Is there any way we could use FSUIPC to adjust the scenery or other performance sliders while IN FLIGHT with FSUIPC?

EUREKA!! I found it!!! You may not find it here because the line containing the problem was delted. The reason I thought I still had it was because I merely reloaded the aircraft. Instead of re running FSUIPC.ini which you have to completely log out of FSUIPC. It dawned on me that I needed reload FSX AND FSUIPC to see the effects of the delted line take place. Sure enough that was the cure. I now have a clear button again! Thanks guys. Time for me to hit the rack LOL!!!

Ok, I read these posts. I tried my best at it but I cannot see what the problem is, mainly because Im not used to looking at the button codes. So I have the same message and I understand that in the dialog I assigned a push on a button and a key press for a release. It worked great when I needed it but I have been after it for a month trying to get it. The Button is Button 08 (x52) Saitek. I thought I had the line where this was taking place, and deleted it to no avail. LOL help? Here is my .ini file as well thanks a lot guys. !1=1[General] UpdatedByVersion=4703 History=LL7CF6Z507OEK1WKPRL6Z MouseWheelTrim=Yes MouseWheelTrimSpeed=1 JoystickTimeout=20 PollGFTQ6=Yes BlankDisplays=No FixControlAccel=No FixMachSpeedBug=No VisibilityOptions=No OneCloudLayer=No CloudTurbulence=No CloudIcing=No GenerateCirrus=Yes SuppressCloudTurbulence=No MaxIce=-4 MinIce=-4 UpperWindGusts=No SuppressWindTurbulence=No SuppressWindVariance=No WindTurbulence=No TurbulenceRate=1.0,5.0 TurbulenceDivisor=20,20,40,40 SuppressAllGusts=No MaxSurfaceWind=5 WindLimitLevel=200 WindDiscardLevel=400 WindAjustAltitude=No WindAjustAltitudeBy=2000 SmoothBySimTime=No WindSmoothing=Yes WindSmoothness=2 WindSmoothAirborneOnly=No PressureSmoothness=0 TemperatureSmoothness=0 DisconnTrimForAP=No ZeroElevForAPAlt=No ThrottleSyncAll=No WhiteMessages=Yes ShowPMcontrols=No SpoilerIncrement=512 MagicBattery=15 RudderSpikeRemoval=Yes ElevatorSpikeRemoval=Yes AileronSpikeRemoval=Yes ReversedElevatorTrim=No ClockSync=No ClockSyncMins=5 ClearWeatherDynamics=No OwnWeatherChanges=No TimeForSelect=4 LoadFlightMenu=Yes LoadPlanMenu=No PauseAfterCrash=No BrakeReleaseThreshold=75 SaveDataWithFlights=No ZapSound=firework ShortAircraftNameOk=No UseProfiles=No TCASid=Type TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No AxisIntercepts=No DontResetAxes=No GetNearestAirports=No WeatherReadFactor=30 WeatherRewriteSeconds=1 CustomWeatherModify=No SimConnectStallTime=1 LuaRerunDelay=66 Console=No [JoyNames] AutoAssignLetters=No 0=Saitek X52 Flight Controller 0.GUID={169927E0-5B42-11E0-8005-444553540000} [buttons] Buttonrepeat=20,10 18=P0,4,C65570,0 54=P0,2,C65759,0 55=P0,3,C65758,0 66=P0,0,C66653,0 67=P0,14,C66654,0 69=R0,5,C66854,0 70=U0,5,C66653,0 81=U0,8,C65752,0 85=P0,1,C65580,0 86=U0,1,C65793,0 93=P0,12,C65774,0 94=P0,13,C65778,0 100=P0,26,C66530,0 101=R0,15,Cx42000BC0,xC0010040 102=R0,17,Cx32000BC0,x3FFF0040 103=R0,21,K187,8 104=P0,20,K65,8 105=R0,19,K189,8 106=P0,22,K83,9 107=P0,18,C66288,0 108=P0,16,C66289,0 111=P0,28,K49,8 112=P0,27,K55,8 [AutoSave] AutoSaveEnabled=No [GPSout] GPSoutEnabled=No Port=COM1 Speed=4800 Interval=2000 PosTo6Decimal=No Sentences= [GPSout2] GPSoutEnabled=No Port=<none set> Speed=4800 Interval=2000 PosTo6Decimal=No Sentences= [WideServer] WideFSenabled=Yes [sounds] Path=C:\Flight Simulator X\Sound\ Device1=Primary Sound Driver Device2=Speakers (2- C-Media USB Headphone Set ) Device3=Digital Audio (S/PDIF) (High Definition Audio Device) Device4=Digital Audio (S/PDIF) (High Definition Audio Device) [Keys] 2=82,8,66512,0 15=40,8,66525,0 17=38,8,66524,0 19=32,8,66530,0 20=118,8,66379,0,66239,0 21=39,8,66526,0 22=37,8,66527,0 24=186,8,66525,0 26=33,8,66524,0 27=115,8,65910,0 [Axes] 0=0X,256,D,1,0,0,0 1=0Y,256,D,2,0,0,0 2=0Z,256,D,4,0,0,0 3=0R,256,D,3,0,0,0 4=0U,256 5=0U,BR,-16384,-5934,x42000BC0,xC0010020 6=0U,BR,4644,16383,x31000BC0,x3FFF0020 7=0V,256 8=0V,B,14448,16383,65752,0 9=0V,B,-16384,-14061,66066,0,66065,0 10=0S,256,D,8,7,0,0 [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 Aileron=-16287,-401,464,16383/8 Elevator=-16383,-255,256,16383/8 Rudder=-15228,-223,289,16383/8 Throttle=-16384,16383 LeftBrake=-16383,16380/24 RightBrake=-16380,16380/24 ElevatorTrim=-16380,-5031,2193,16380/24 Spoilers=-16383,16383/8 PanHeading=-16383,-902,387,16383/8 PanPitch=-16384,-903,645,16383/24 SlopeRudder=15 [window.Radar Contact] Docked=12790, 445, 3536, 2449 Undocked=0, 0, 8, 8 [Keys.Raytheon Premier1 N3216P] 2=112,8,65907,0,1126,0 6=115,8,65910,0,1126,0 7=114,8,65909,0,1126,0 14=113,8,65908,0,1126,0 22=120,8,66657,0 23=38,8,66528,0 24=40,8,66529,0 25=37,8,66527,0 26=39,8,66526,0 27=186,8,66525,0 28=33,8,66524,0 34=119,8,65560,0 35=117,8,66239,0,66379,0 38=118,8,66240,0,66378,0 39=116,8,66389,0 [buttons.Raytheon Premier1 N3216P] 13=P0,0,C66653,0 14=P0,14,C66654,0 26=U0,28,C66524,0 [General] UpdatedByVersion=4703 History=LL5AI703Y8KEJTSINPJ42 MouseWheelTrim=Yes MouseWheelTrimSpeed=1 JoystickTimeout=20 PollGFTQ6=Yes BlankDisplays=No FixControlAccel=No FixMachSpeedBug=No VisibilityOptions=No OneCloudLayer=No CloudTurbulence=No CloudIcing=No GenerateCirrus=Yes SuppressCloudTurbulence=No MaxIce=-4 MinIce=-4 UpperWindGusts=No SuppressWindTurbulence=No SuppressWindVariance=No WindTurbulence=No TurbulenceRate=1.0,5.0 TurbulenceDivisor=20,20,40,40 SuppressAllGusts=No MaxSurfaceWind=5 WindLimitLevel=200 WindDiscardLevel=400 WindAjustAltitude=No WindAjustAltitudeBy=2000 SmoothBySimTime=No WindSmoothing=Yes WindSmoothness=2 WindSmoothAirborneOnly=No PressureSmoothness=0 TemperatureSmoothness=0 DisconnTrimForAP=No ZeroElevForAPAlt=No ThrottleSyncAll=No WhiteMessages=Yes ShowPMcontrols=No SpoilerIncrement=512 MagicBattery=15 RudderSpikeRemoval=Yes ElevatorSpikeRemoval=Yes AileronSpikeRemoval=Yes ReversedElevatorTrim=No ClockSync=No ClockSyncMins=5 ClearWeatherDynamics=No OwnWeatherChanges=No TimeForSelect=4 LoadFlightMenu=Yes LoadPlanMenu=No PauseAfterCrash=No BrakeReleaseThreshold=75 SaveDataWithFlights=No ZapSound=firework ShortAircraftNameOk=No UseProfiles=No TCASid=Type TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No AxisIntercepts=No DontResetAxes=No GetNearestAirports=No WeatherReadFactor=30 WeatherRewriteSeconds=1 CustomWeatherModify=No SimConnectStallTime=1 LuaRerunDelay=66 Console=No [Axes.Raytheon Premier1 N3216P] 0=0X,256,D,1,0,0,0 1=0Y,256,D,2,0,0,0 2=0Z,256,D,4,0,0,0 3=0R,256,D,3,0,0,0 4=0V,256 5=0V,B,-516,16383,66064,0,66065,0 6=0V,B,-16384,-11352,65752,0,65752,0 7=0S,256,D,7,8,0,0 [Axes.T210 CENTURION BLUE CLASSIC] 0=0X,256,D,1,0,0,0 1=0Y,256,D,2,0,0,0 2=0Z,256,D,4,0,0,0 3=0R,256,D,3,0,0,0 4=0U,256,D,5,0,0,0 5=0V,256 6=0V,B,14448,16383,65752,0 7=0V,B,-16384,-14061,66066,0,66065,0 8=0S,256,D,8,7,0,0 [JoystickCalibration.T210 CENTURION BLUE CLASSIC] 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 Aileron=-16383,-401,464,16383/8 Elevator=-16383,-255,256,16383/8 Rudder=-15228,-223,289,16383/8 SlopeRudder=15 Throttle=-16384,16383 LeftBrake=-16383,16380/24 RightBrake=-16380,16380/24 ElevatorTrim=-16380,-5031,2193,16380/24 Spoilers=-16383,16383/8 PanHeading=-16383,-902,387,16383/8 PanPitch=-16384,-903,645,16383/24 PropPitch=-16380,16380/16 SlopeElevator=14 [Keys.T210 CENTURION BLUE CLASSIC] 1=116,8,66374,0,1126,0 [buttons.T210 CENTURION BLUE CLASSIC] 0=R0,15,Cx42000BC0,xC0010020 1=R0,17,Cx32000BC0,x3FFF0020 2=P0,8,C65751,0 3=P0,9,C66240,0 4=P0,10,C66379,0 5=P0,11,C66239,0 6=P0,12,C65560,0 7=P0,13,C66579,0

The Lua sounds interesting. I just havent worked with them yet. Still fiddling with Offsets LOL! Love them! Ive read the material for the Lua's and Ill have to do a very easy one or two on something simple then I can go from there. If I have the right Idea, does the Lua make something happen, that you'd like to happen when your controls do (x) action, that is not programmed into the aircraft? A work around sort of thing?

Actually Both the 2D and the VC have the button here are some screen shots. Does the Lua plug in allow me to establish a throttle range and or both hopefully a silence means like this button area does? Thanks Pete.

Hi Pete! I hope you enjoyed your time off. Eaglesoft Premier 1a Saitek X52 FSUIPC4 FSX Acceleration 1st. Id like to map my gear warning button on the panel to my X52, for starters. 2nd. Id like to try to determine when the warning horn comes on to adjust that lower. At the moment the warning horn comes on in the 40% n1 range. I can reach the gear horn button in 2d without effort, the problem is in the 3d cockpit and my eyepoint, makes it difficult to get to it. The warning comes on when I practice the stall series and Id like to mute it via FSUIPC or some button. I have scanned the List of Controls.pdf and did not find any obvious control for this nor did I see it in FSX controls. I looked through the sound and aircraft.cfg and did not see a clear definition. I searched the net for it and was unlucky. Before I get too far into this, I was wondering if I can even manipulate it. If so Id, appreciate some advice on where to go in the manuals to get that accomplished. THANKS!