Im looking for help in setting up all the above

Document Sample
Im looking for help in setting up all the above Powered By Docstoc
					Hi all
Here is a detailed method of setting up the CH USB devices in FS2004

Step by Step Guide to setting up the CH Yoke, TQ, and Pro Pedals in FS2004 using
CHCM ver4.0 (Mapped Mode) and FSUIPC (latest registered) version.
        1)    Very Important: Definitely use CH Control Manager 4.0 (nothing earlier). I
              would also use CMStart.exe and CMFS v1.2 and CMNOTE02.zip (the latter
              two items are available from Bob Church – www.stickworks.com).
        2)    Create a map using CHCM 4.0 and assign the appropriate throttle axes to the
              Throttle Quad – “TQ”. I use the map wizard to add each type of controller
              from the drop down box. You choose the controllers you require from a list,
              such as Yoke, TQ and ProPedals. [Note the order you enter the controllers
              with the wizard as it can help in identifying which device is which later. In
              mapped mode the first tab in CHCM will be shown in FS9 as CM Device 1,
              the second tab will be shown as CM Device 2, and so on. In the example
              above if you entered the Yoke first in CHCM (it would be displayed in FS9 as
              CM Device 1), the TQ second (CM Device 2), and Pro pedals third (CM
              Device 3)
        3)    In The Combining Controllers Window select “NO” when asked to combine
              the controllers.
        4)    In the next window, “Control Manager Scripting” choose “YES” to include
              “CMS scripting in this map”. You may never use CMS scripting but it does
              no harm to have it included.
        5)    On the last screen check “FINISH” to return to CHCM.
        6)    On the screen now there should be 5 settings: “Program Settings”; “FS Yoke”;
              “Throttle Quad”; “Pro Pedals” and “CMS Controls”.
        7)    We will look at setting up the TQ. Choose the TQ on the tab in CHCM and a
              picture of the TQ will appear showing all 6 levers and 6 buttons. The picture
              will also show 12 virtual buttons in 2 rows of 6 labelled Detent and minZone
              It will be named CM Device 2 if entered as I did above. Highlight the left
              most lever which will show a small yellow arrow above it. It is assumed that
              you need reverse thrust. On the right hand side of the box it will show: “DX
              Mode: Checked”; “DX Device: CM Device 2”; “DX Axis: X Axis”: “Min
              Val: 0”; “Max Val: 255”; “Detent Val: 255”; “Deadzone: 4”; “Invert:
              Unchecked”; “Comment: Empty”. For reverse thrust you must set the detent
              value at 240.
              Repeat this setting for other throttles choosing the appropriate lever on the
              picture before setting. You can also assign propeller and mixture settings as
              needed. I have assigned Axis 2: Throttle 2: Axis 3/4: Prop_Pitch_1_SET/
              Prop_Pitch_2_SET; Axis 5/6: Mixture1_Set/ Mixture2_Set.
              The buttons are assigned in a similar manner.
        8)    Buttons: I have assigned the far left button, button 1 (up) to the “BRAKES”
              and after highlighting the button the settings on the right would indicate: “DX
              Mode: Checked”; “DX Device: CM Device 2”; “Direct X Device: Button 1”:
              “Shifted Action: DirectX Device: None; DirectX Device: Control: None;”;
              “Comment: BRAKES”. My buttons are assigned as follows: Button 2 (down):
              Parking Brake: Button 3 (up): Autopilot off: Button 4 (Down): Autopilot on;
              Buttons 5/6 (Up/Down) Lights OFF/ON; Buttons 7/8: Beacon Off/ON:
              Buttons 9/10: Engine shut down/Engine Start; Buttons 11/12: Exit/Abort.
9)    I would assign (using Michael’s posted files as a guide), the other buttons and
      axes to the Pro Pedals and Yoke). When you have assigned all the buttons and
      axes that you need - Save the map!!
10)   There are lots of guides (including CMNOTE02.zip) on this forum on how to
      assign axes and buttons to the various CH controllers such as the Yoke, TQ
      and Pro Pedals. CMFS v1.2 is a great little tool that makes it quite easy to
      assign buttons and axes to each of the controllers, so I will not cover them all
      here (other than the examples above). In the GUI version I will cover this
      comprehensively showing a picture for each axis and button.] The map must
      be saved in the C:\Program Files\Control Manager\Maps. [Where C:\ is the
      drive you have installed CHCM v4.0 on].
11)   Calibrate all 3 with CHCM v4.0 (using “DIRECT” mode). After calibration,
      "Download" the map (“mapped mode” is automatically selected). Finally the
      map must be re-saved.
12)   Print out the assignments made in the map. CH Products has a piece of
      software that does this for you. Details: CMPrint.exe Version 1.00 - CH
      Control Manager Map Listing Utility
13)   Install and use CMStart.exe which loads every time Windows starts. This
      great little program ensures that the LAST map that you created, downloaded
      and/or mapped in CHCM, is used in “mapped” mode in FS2004.
14)   The first time that I use a new map, I rename the fs9.cfg file (Using note pad I
      print out all of the settings to be used as in Section 19 below) and when
      FS2004 next opens it will have to create a new fs9.cfg file, which
      unfortunately has to have all of your favourite settings such as Display, Sound,
      ATC, etc reset. (Reset these settings after carrying out #16/17/18/ see #19).
      [However, as Bob Church notes: If you are using CMFS, though, it does set
      the Sensitivities and Null Zones into devices.cfg. In fact, if you make the map
      and only use the CMFS method to assign axes and buttons, all of the
      assignments end up in devices.cfg and there are no joystick-related settings in
      FS9.CFG at all. For joystick settings, FS9.CFG only holds items that you've
      manually assigned using Flight Simulator that override settings in devices.cfg.
      Using the "Reset Defaults" button in FS9 essentially clears the FS9.CFG
      joystick settings and reverts to just using Devices.cfg for everything.)
15)   Open FS2004 and go to assignments and set the sensitivities for the TQ and
      the Yoke fully to the right for each axis i.e. most sensitive and set the null
      zone fully to the left i.e. minimum dead zone. (I have found that you can
      choose your own sensitivities/null zones for the Pro Pedals without upsetting
      anything in the TQ/Yoke.) (Note: If you use CMFS it will make these
      assignments for you. Although devices.cfg can set null zone and sensitivity,
      reverse the axes, set the repeat rate, etc. CMFS can also make the right default
      entries to do that.)
16)   In FS2004 assign (EXACTLY) the same buttons and axes that you have in
      your CH map created above, to the Yoke, TQ and Pro Pedals. This must be
      accurate. This is a “security step” as FS9 will not use any of the assignments
      from fs9.cfg, but if it does then they are exactly the same as in the devices.cfg
      and CHCM.
17)   In FS2004 under the Assignments Press the “Reset Defaults” button. This will
      assign all of your settings to the devices.cfg file (and probably will not use any
      controller settings in fs9.cfg.)
18)   Next, reset your General, Display, Scenery, ATC, etc settings wiped out when
      we changed the fs9.cfg
19)   Select a flight (DEFAULT) and open at default airfield (this is the simplest
      method but any flight will do).
20)   Using the “ALT” button, open “Modules” “FSUIPC”, and "FINE TUNE" your
      buttons and axes using PETE Dowson’s instruction manual or use the
      instructions found in Bob Church's CMNOTE02.zip obtainable from
      www.stickworks.com. Make sure that you assign the same buttons and axes
      in FSUIPC as in your CH map and in your FS2004 assignments. Close
      FSUIPC.
21)   The FSUIPC axes settings should range from approximately -16,256 to
      +16,256 values for minimum and maximum values if the sensitivities and null
      zone have been set correctly. For reverse thrust you should get a detent value
      which is different to the -16,256 minimum value (My values (for a single/twin
      engine with reverse thrust are: Throttle 1 =-16193, -14258, -14258, +16192;
      Throttle 2 = -16193, -14258, -14258, +16192. The values relating to these
      figures are: Minimum, Detent, Detent, Maximum, respectively. If you want
      absolute control over the detent then you can “wiggle” the TQ lever at the
      detent value and you will get 2 slightly different readings in the two detent
      boxes (this is the sort of “null zone” and makes sure that you do not select
      reverse thrust inadvertently at the detent value). Read Pete Dowson’s manual
      carefully as the order that you enter these values in FSUIPC is quite important.
      I usually use Maximum, Detent, Detent and Minimum, but this may vary from
      controller to controller. [Note from Bob Church: You only need this
      "wiggling" of the lever around the detent, if you're only using FSUIPC and
      NOT the CHCM. The CHCM will put a “dead-zone” around the détente
      automatically so it doesn't matter, but FSUIPC uses the two values to define
      the upper and lower limits of the “dead-zone”.]
22)   Begin the flight for a few brief seconds - end the flight and exit to "settings"
      screen.
23)   Check that FS2004 has not "changed" the sensitivity and null zone settings
      (for each separate axis). If FS2004 has changed the sensitivity and/or null
      zone you need to reset these values yet again, and then restart a new default
      flight as above and re-check until the sensitivities are full right and the null
      zones are full left. Repeat as necessary. [This is a peculiarity of FS9 in the
      way that it interfaces with external programs such as CHCM and in the way
      that it utilizes devices.cfg and other inbuilt default settings it uses to recognize
      any controllers attached to the PC.]
24)   [You can check in devices.cfg that the sensitivities and null zone are correct.
      For example for the TQ and throttle 1 you would look for the entry:
      AXIS_EVENT_00=THROTTLE1_SET: AXIS_SCALE_00=127:
      AXIS_NULL_00=1. The axis_scale = 127 means that the sensitivity is fully
      over to the right and axis_null = 1 means that the null zone is fully over to the
      left and is at a minimum. In another example, if the figures for axis_scale =
      64 and the axis_null = 36, this would mean that the sensitivity and null zone
      are not at their maximum or minimum respectively.]
25)   Exit Fs2004 and reboot the PC
26)   Check the fs9.cfg, the devices.cfg, and the CH CM Map so that they all have
      exactly the same assignments for each button and axis in their files. If you are
      using mapped mode in CHCM for the Yoke, Pro Pedals and TQ. In FS2004 in
               the devices.cfg file you should see entries for “CH Control manager Device 1,
               2, and/or 3” as appropriate. There may be settings for the “CH FLIGHT SIM
               YOKE USB” (Pro Pedals/TQ), but as I understand it if you use “mapped
               mode” in CH CM then FS2004 uses the “CH Control Manager Device”.
        27)    In fs9.cfg you will see an entry something like “JOYSTICK_MAIN
               {B77471A0-1E36-11DA-8005-444553540000}”. There will be 3 entries
               corresponding to the Yoke, TQ and Pro Pedals with the number I have made
               bold, underlined and italicised above being the value that changes [In my
               system the numbers allocated were 8004, 8005, and 8006]. Ensure that you
               choose the right entry when checking the values. [Note: Again this is attention
               to detail as the fs9.cfg is probably not used by FS9 for the controller
               assignments but it ensures that there are no conflicting assignments.]
        28)    If the settings are all exactly the same you are home free. If not, you need to
               edit the relevant “cfg” file that is different, using note pad. I also check the
               FSUIPC.ini file to ensure that it has recorded the values for each setting for
               each button and axis and that the assignments are exactly the same as in the
               above 3 files.
        29)    This may sound like overkill, but until I adopted this approach I had a lot of
               problems in controlling the aircraft. By using these methods, I get consistent
               results time after time.
        30)    I calibrate using CHCM 4.0 once a month and use FSUIPC to fine tune as
               needed.
        31)    I will have a go at setting all of this down as a GUI type document, so you it
               can be explained it step by step. It may take me some time as my other life
               intrudes.
Peter H
January 2006

My sincere thanks to Bob Church for all of his input, advice and help in preparing this guide.
QUICK Step by Step Guide to setting up the CH Yoke, TQ, and Pro Pedals in FS2004
using CHCM ver4.0 (Mapped Mode) and FSUIPC (latest registered) version in FS2004
(FS9).
          1) Use CH Control Manager 4.0, CMStart.exe and CMFS v1.2 and
        CMNOTE02.zip and FSUIPC ver 3.53 or latest.
          2) Create a map using CHCM 4.0 and the map wizard. In mapped mode if you
        entered the Yoke first in CHCM (it would be displayed in FS2004 as CM Device
        1), the TQ second (CM Device 2), and Pro pedals third (CM Device 3)
          3) In the Combining Controllers Window select “NO” when asked to combine
        the controllers.
          4) In the next window, “Control Manager Scripting” choose “YES” to include
        “CMS scripting in this map”. (Not needed but useful).
          5) On the last screen check “FINISH” to return to CHCM.
          6) On the screen now there should be 5 settings: “Program Settings”; “FS Yoke”;
        “Throttle Quad”; “Pro Pedals” and “CMS Controls”.
          7) Using CHCM and CMFS assign all axes to each controller, ie Yoke, TQ and
        Pro-Pedals.
          8) Using CHCM and CMFS assign all buttons on each controller, as needed.
          9) When you have assigned all the buttons and axes that you need - Save the
        map!!
          10) The map must be saved in the C:\Program Files\Control Manager\Maps.
        [Where C:\ is the drive you have installed CHCM v4.0 on].
          11) Calibrate all 3 with CHCM v4.0 (using “DIRECT” mode). After calibration,
        "Download" the map (“mapped mode” is automatically selected).
          12) Finally re-save the map, and if required, print out the assignments made in the
        map.
          13) Install and use CMStart.exe which loads every time Windows starts and
        ensures FS2004 uses your last “downloaded” map.
          14) Rename fs9.cfg file and let FS2004 create a new fs9.cfg next time it opens.
          15) Open FS2004 and go to assignments and set the sensitivities for the TQ and
        the Yoke fully to the right for each axis i.e. most sensitive and set the null zone
        fully to the left i.e. minimum dead zone.
          16) In FS2004 under “assignments” assign (EXACTLY) the same buttons and
        axes that you have in your CH map created above, to the Yoke, TQ and Pro Pedals.
          17) In FS2004 under the Assignments Press the “Reset Defaults” button.
          18) Next, re-enter your General, Display, Scenery, ATC, etc settings wiped out
        when we renamed the fs9.cfg
          19) Select a flight (DEFAULT) and open at default airfield.
          20) Using the “ALT” button, open “Modules” “FSUIPC”, and "FINE TUNE" your
        buttons and axes
          21) The FSUIPC axes settings should range from approximately -16,256 to
        +16,256 values for min and max values with approximately 14,000+ at the detent
        values.
          22) Begin the flight for a few brief seconds - end the flight and exit to "settings"
        screen.
          23) Check that FS2004 has not "changed" the sensitivity and null zone settings
        (for each separate axis).
          24) Check in devices.cfg that the sensitivities and null zone are correct.
          25) Exit FS2004 and reboot the PC
            26) Check the fs9.cfg, the devices.cfg, and the CH CM Map so that they all have
           exactly the same assignments for each button and axis in their files.
            27) See the comprehensive guide for a full explanation of the above steps.

Peter H
January 2006
My sincere thanks to Bob Church for all of his input, advice and help in preparing this guide. (and Revvin &
Ghost).

				
DOCUMENT INFO
Shared By:
Categories:
Stats:
views:16
posted:3/30/2011
language:English
pages:6