Hi all:Just got my CH Products......yoke, throttle quad, pro pedals. Did the installation as should have. Used CM editor to map as saw on Hangar site...dummies III.On Dell portable, windows 7, 16 gig memory. one usb is v2 and two are v3.Using MS Flight Sim X deluxe edition which still works but does not recognize the CH stuff.Have yoke, throttle quad, pro pedals all plugged into portable.When I got into Control Manager v4.51 that I got with all the hardware, load my map file, then try calibrate in Control Manager, the yoke does not move the dot on the screen to show it is working. Have not tried the others yet.Saw on this site that should have usb ports set to NOT power down under power mgmt so did that, rebooted, unplugged all usb, then plugged in again. Tried calibrate again....same result.Have downloaded instructions from various places on net but nothing is directly related to Windows 7 and MS FSX.I'm all new to this stuff and am driving myself crazy trying different things....nothing works. Any suggestions....Ray

You can start by diagnosing your USB ports via USB Deview.Cheers,- jahman.

Hi Ray,With everything hooked up, click the Test/Calibrate button to get to the list of controllers in the Control Manager GUI. Probably there's nothing in the list, but down in the lower left corner there's a little button marked "Rescan". Click that and see if it will get the controllers for you.Couple of other notes. You mentioned a portable. Don't ever let it go to hibernate mode mode. That cuts the power to the USB devices and you've seen the comments on that. Sleep is okay as far as I know, but Hibernate will kill the hubs.Also, be sure to activate any map before you start FSX. When you activate, the names of the controllers change to "Control Manager Device xx". Those are the joysticks that FS will see. It causes FS to "Reset Defaults" on all of them and any custom settings you had get lost.Finally, if you're using Win7 64 or Vista 64, don't calibrate from within FS. It just calls the Windows standard calibration routines and those set flags and otherwise play with the data such that the CM can't do what it's supposed to. If you need to calibrate them, close FS and run the CM GUI, calibrate it from there. If you think you might have already done that, then you need to clear the Windows calibration data and get calibrate in the Control Manager.Best regards,- BobThe StickWorkshttp://www.stickwork.com

Hi Bob:Thanks for your reply.....still can not get things to work so have removed all CH devices, uninstalled, and went through the process all over again. This time I wrote down everything that I did. Long post but wanted to show everything that was done.I sent CH Products tech support an email informing them of this problem and the suggestion was to use as direct without the control manager. Did that and in FSX assigned some of the buttons and all seemed to work ok. But, I don't want to do this for the Throttle quad and my point was "why can I not use the Control Manager" as it came with my products. The tech support suggested I phone them for assistance, but am trying here first as I am completely on the other side of the continent in Northern Canada. I requested updated instructions and got nothing. First of all, the instructions that came with the Yoke, Pedals, Throttle are outdated installation instructions and do NOT reference Windows 7 in any way. I don’t understand why they would advertise Win 7 and not ship with up-to-date instructions. Before starting the install, checked control panel, devices, and NO CH devices listed. Plug USB Throttle Quad, USB input device – software installed successfully. Control Panel, Devices, USB input device, right click game controller settings, CH Throttle Quad – ok, highlight Quad, properties, test – everything works....note...NOT calibrated here. Plug in Pro Pedals, USB input device - software installed successfully. Control Panel, Devices, USB input device, right click game controller settings, shows Throttle Quad-ok, shows CH Pro Pedals USB – ok, highlight pedals, properties, test, everything works. Note..NOT calibrated here. Plug in Yoke, USB input device – software installed successfully. Control Panel, Devices, USB input device, right click game controller settings, shows Quad-ok, Pedals-ok, Yoke-ok, highlight yok, properties, test, everything works. Note...NOT calibrated here. Insert CH Control Manager CD Click “Run install.exe”, click “install products”. This software also outdated as no option for Win 7, so chose to click “Windows vista”. Click “Control Manager”. See Welcome screen, click “Next”, click “agree”, click “Next”. Click “Install Program CH Control Manager Software”, click “Install”. 3 Verify screens and click “Install this driver software anyway” to all three.CH Control Manager Root Device – ready to use.CH Control Manager Aux 1 Device – ready to use.CH Control Manager Aux 2 Device – ready to use.CH Pro Pedals USB – ready to use.CH Throttle Quad – ready to use.CH Flight Sim Yoke USB – ready to use.Finish, Exit. Remove the CD and restart the computer. Start, all progs, CH Products, CH Control Manager – send to desktop as shortcut.Do same as above for CM Start. Control Panel, Device manager, CH Products, and have the following....CH Control Manager Aux 1 Device, Aux 2, Root, Flight Sim Yoke USB, Flight Sim Yoke Hardware,Pro Pedals USB (and Hardware), Quad USB (and Hardware). Windows Explorer to users, Ray, CH Control Manager, Maps file folder and copy MS FSX.cmd from my backup. This cmc file has definitions for the FS controls and corresponding keys to send....done as per instructions. Open CH Control Manager using icon. Click ‘Map Wizard’, click FS Yoke, Throttle Quad, Pro Pedals, okay, combine=no, cms=yes, click finish. Save in folder....Ray, CH Maps, MS FSX.map Program settings, command file=MS FSX which I had previously made up as noted above. FS Yoke, X-axis – uncheck DX Mode same for Y-axis and for all buttons.Click button 1, normal action, right click, insert command, dbl click “brakes_apply_release”Click button 12, normal action, insert command “engine(autostart)” Throttle Quad...uncheck DX mode for all levers and buttons.Same as above for the Pro Pedals. SaveTest/Calibrate, yoke, okay, “all ok”, done Test/Calibrate, pedals, okay, “all don’t work”. Calibrate and still don’t work.Same as above for Quad and “all don’t work”. Save Download, shows successful. FS Yoke panel, click “test/calibrate”, shows “Control Manager Device 1, okay....only POV works. Exit Control Manager. Dbl click CMStart icon. Shows on task bar and then disappears from task bar. Dbl click MS FSX. Missions, Intro to mountain flying, and click “fly”. Want to test the brakes and engine start. Button 1 on yoke (assigned to brakes)..this works.Button 12 on yoke (assigned to engine start) ...does not work. Looking at outside of plane, the rudder does not work and the ailerons don’t work. Now, I must be doing something wrong here with these few items and don’t want to continue to set up all buttons if a few don’t work. Can anyone set me on the correct path ?Ray

Hi Ray,It sounds like it might be an old version of CH Control Manager on the disk that you have. You might want to try uninstalling it, and downloading the latest version from the CH website (http://www.chproducts.com/retail/downloads.html) and seeing if perhaps the download version is newer than the version on your disk, and if it resolves your issues. Personally, I have the yoke and pedals, and I just have them set up through FSX, without having the Control Manager software installed at all. Once I've got it all set up the way I want it in FSX, I then save a backup copy of my standard.xml file (in the Controls folder where your FSX.CFG is located) outside my FSX folders so I have it for future reference in case I have to reinstall.Good luck, I hope you get this resolved to your satisfaction.-George

Hi George:I have CH Control Manager v4.51 which is the latest I believe. I, too, can get the yoke and pedals running ok just using FSX with win7 but I want to use the control manager because I want to easily use the yoke, pedals, and the throttle quad. Besides, that is what I paid for. As I mentioned, the installation instructions for these 3 CH products is out of date as is the installation of the Control Manager as it does not reference Windows 7 either.I am so frustrated at receiving stuff that is incomplete or out-of-date that I am almost ready to send everything back and just forget it.Ray

Hi all: Been working more on my problems today and here is latest...... First I started FSX and on settings, I reset everything to the default and saved settings to file and load this file each time I start. In devices/printers I have Flight sim yoke usb, driver=chdrvr01.sys Pedals usb hardware, driver=chdrvr01.sys Quad usb hardware, driver=chdrvr01.sys 3 of these.....HID compliant game controller In test/calibrate shows device 1 screen shows movement of yoke and 3 levers In test/calibrate shows device 2 screen shows no movement of quad levers In test-calibrate shows device 3 screen shows no movement of pedalsNOTE....I DID NOT DO A CALIBRATE HERE. I then run cmstart program FSX settings calibrate screen shows device 1, 2, 3 DID NOT DO A CALIBRATE HERE Buttons/keys ....these are as FSX was received Control axes....these are as FSX was received Went to missions for the mountain mission to test things out....... On yoke....POV works ok, button 2 mapped to kneeboard and is ok Button 1 mapped to brakes and is ok, ailerons are ok, elevators are ok, Button 5, 6 mapped to flaps are ok, throttle lever is ok Button 12 mapped to engine(autostart) does a view movement to the left with each button press Button 3 mapped to rudder trim left does a kneeboard display Prop pitch lever does the rudder pedals Mixture lever does nothing that I can see Anybody have any ideas.... Ray

Anybody have any ideas....

See Post #2.Cheers,- jahman.

Anybody have any ideas....

See Post #2.Cheers,- jahman.

Jahman:I read these posts carefully and everything posted here has already been tried and done without success.....wouldn't have posted again without trying these.Ray

All I can say as I have for a long time is: "Dump CH Manager and use a registered version of FSUIPC". I have a CH TQ, Saitek yoke, 2 TQ's and pedals all assigned and working with FSUIPC. Just confirm that duplicate assignments don't exist in FS.Jim D.

Here is the latest in what I have found out........if the yoke is plugged into a USB 2.0 then it works both with and without the CH Control Manager. If the pedals are plugged into a USB 3.0 then they work without the CH Control Manager but WILL NOT work with the Control Manager.This would seem to be a software problem with the Control Manager......will I ever get a fix ??????Ray

Hi Ray,WRT to USB 3.0, you said the yoke is recognized in 2.0/CM, the pedals in 3.0/no CM. I haven't played with 3.0 yet, but my understanding is that the 3.0 plug is longer and that a USB 2.0 plug actually goes to a 2.0 bus. The 3.0 bus is seperate. I haven't seen one yet though. I'll have to look into it. Does the opposite hold, e.g. does the Yoke work into the 3.0 port and the Pedals into the 2.0 Port? Dont run FS, just have a look in the Game Controllers applet and see if they register (don't calibrate). If they don't show there, they're probably coming in as "Unknown" rather than their actual selves, the CM never sees them. Until they're "known", Windows can't look up the INFs and find the drivers, so the CM simply won't load (no driver would). It would have to be a problem somewhere between the controller and the port for that to happen.Your first "long" post took a bit of time to get through, but actually nothing really looks wrong. I wrote this reply sort of point-by-point, but really, it sounds more like some confusion and nothing really wrong. Have a read and see if it's any help. During that test were you using any 3.0 ports or just 2.0 ports?>> Thanks for your reply.....still can not get things to work so have removed all CH devices, uninstalled, and went through the process all over again. This time I wrote down everything that I did. Long post but wanted to show everything that was done.But, I don't want to do this for the Throttle quad and my point was "why can I not use the Control Manager" as it came with my products. The tech support suggested I phone them for assistance, but am trying here first as I am completely on the other side of the continent in Northern Canada. I requested updated instructions and got nothing. << There really aren't any. It can be confusing at first, but it hasn't really changed much since 2002 or so. >> First of all, the instructions that came with the Yoke, Pedals, Throttle are outdated installation instructions and do NOT reference Windows 7 in any way. I don’t understand why they would advertise Win 7 and not ship with up-to-date instructions. <<There's no real difference between that and Vista, and the installer should know what to do anyway. The only real options are to install so it only reconizes an MFP and Mouse, or doesn't install the programmability, just the drivers. MS made major changes in the installation process when Vista showed up, but since then it really hasn't changed. There were no changes to the Control Manager as a result of that. Arguably it might have been noted, but all it would have said is "Nothing Changed".>> Before starting the install, checked control panel, devices, and NO CH devices listed.Plug USB Throttle Quad, USB input device – software installed successfully.Control Panel, Devices, USB input device, right click game controller settings, CH Throttle Quad – ok, highlight Quad, properties, test – everything works....note...NOT calibrated here.Plug in Pro Pedals, USB input device - software installed successfully.Control Panel, Devices, USB input device, right click game controller settings, shows Throttle Quad-ok, shows CH Pro Pedals USB – ok, highlight pedals, properties, test, everything works. Note..NOT calibrated here.Plug in Yoke, USB input device – software installed successfully.Control Panel, Devices, USB input device, right click game controller settings, shows Quad-ok, Pedals-ok, Yoke-ok, highlight yok, properties, test, everything works. Note...NOT calibrated here. <<Okay. That's the Windows UID/USB drivers picking them up and it sounds like it went in just fine, really. The buttons should have lit up and the axes should have moved in the Windows Control Panel applet, but you were absolutely right not to calibrate there.>> Insert CH Control Manager CD <<v4.51 is the latest version, it should be on the GUI screen. It's probably what you've got. That's the version that came out with the Eclipse, which was the last time it was updated.>> Click “Run install.exe”, click “install products”.This software also outdated as no option for Win 7, so chose to click “Windows vista”. Click “Control Manager”. See Welcome screen, click “Next”, click “agree”, click “Next”.Click “Install Program CH Control Manager Software”, click “Install”.3 Verify screens and click “Install this driver software anyway” to all three.CH Control Manager Root Device – ready to use.CH Control Manager Aux 1 Device – ready to use.CH Control Manager Aux 2 Device – ready to use.CH Pro Pedals USB – ready to use.CH Throttle Quad – ready to use.CH Flight Sim Yoke USB – ready to use.Finish, Exit. <<That all sounds normal.>> Remove the CD and restart the computer. <<Okay. That sounds right. FWIW, it's really better to restart after you plug things in but before you run the installer. The first time Windows restarts, it almost invariably shuffles things around. That gives some or all of the Controllers back to the control of Windows the Windows. If it happens, the "rescan" button on the first page of the calibration dialog should get them back for you. You can tell, actually. Look at the first screen of the Windows Joystick applet where it lists the controllers it sees. If the CH names are in full upper-case (CH PRO PEDALS USB), then they're under Windows control. If they show up in mixed case (CH Pro Pedals USB) then they're under the Control Manager. Restarting before you actually install is usually easier because the reshuffling happens with Windows as well. Windows has in-box drivers, though, and so the whole thing goes quickly and smoothly. After the first restart, the ordering usually holds and it's not a problem, but hot-plugging things or moving them from one port to another will do that.>> Start, all progs, CH Products, CH Control Manager – send to desktop as shortcut.Do same as above for CM Start. <<That's fine.>> Control Panel, Device manager, CH Products, and have the following....CH Control Manager Aux 1 Device, Aux 2, Root, Flight Sim Yoke USB, Flight Sim Yoke Hardware,Pro Pedals USB (and Hardware), Quad USB (and Hardware). <<That sounds right. You should have two entries for everything except the Root device. One is actually the hardware device, the second is the HID device that represents it to DX. If you look, you'll see a HID keyboard and mouse have shown up, too. >> Windows Explorer to users, Ray, CH Control Manager, Maps file folder and copy MS FSX.cmd from my backup. This cmc file has definitions for the FS controls and corresponding keys to send....done as per instructions. <<That sounds right.>> Open CH Control Manager using icon. Click ‘Map Wizard’, click FS Yoke, Throttle Quad, Pro Pedals, okay, combine=no, cms=yes, click finish. <<Okay.>> Save in folder....Ray, CH Maps, MS FSX.map << >> Program settings, command file=MS FSX which I had previously made up as noted above. <<Okay.>> FS Yoke, X-axis – uncheck DX Mode same for Y-axis and for all buttons.Click button 1, normal action, right click, insert command, dbl click “brakes_apply_release” <<That wouldn't normally be what you'd want. When DX Mode is checked, the controller is going to send joystick axes and buttons. When it's unchecked, it's going to send characters. You might uncheck button for a character command, but unchecking X and Y, etc. doesn't sound like what you'd want to do. If you didn't then program them to send charactes, though, they wouldn't have done anything.>> Click button 12, normal action, insert command “engine(autostart)” <<So long "enging(autostart) was defined the CMC file it should be good., tthough I can't recall offhand it will allow the "(" and ")" in the macro name. You might try something like "EngingAutostart" and see if it helped.>> Throttle Quad...uncheck DX mode for all levers and buttons.Same as above for the Pro Pedals. >>Again, unless later programmed them to send characters, they would end up doing nothing at all.>> SaveTest/Calibrate, yoke, okay, “all ok”, done <<The map is inactive during calibration so the axes and buttons would come back as regular DX stuff.>> Test/Calibrate, pedals, okay, “all don’t work”. Calibrate and still don’t work. <<Was Auto-coordination disable?>> Same as above for Quad and “all don’t work”. <<I'd need to know about the character programming.....>> SaveDownload, shows successful. <<Okay.>> FS Yoke panel, click “test/calibrate”, shows “Control Manager Device 1, okay....only POV works. <<Probably. When you downoaded it, things switched to the Control Manager Device nomenclature, but you disconnected everything there when you unchecked the DX Mode boxes. Even with the characters, unless you were watching keytest or NotePad or something like that, you won't know.>> Exit Control Manager. <<Okay.>> Dbl click CMStart icon. Shows on task bar and then disappears from task bar. <<That's normal. CMStart only runs for about 5 seconds, long enough to send the command to the Control Manager to re-enable the map. It flashes so it looks "busy", in the end it just sends the command and closes.>> Dbl click MS FSX. >>Okay.>> Missions, Intro to mountain flying, and click “fly”. Want to test the brakes and engine start. <<>> Button 1 on yoke (assigned to brakes)..this works. <<Probably it was either left in DX mode and programmed in the FS Controls Assignments dialog or you put a character on it with DX Mode unchecked.>> Button 12 on yoke (assigned to engine start) ...does not work. <<I'd guess more assignment problems.>> Looking at outside of plane, the rudder does not work and the ailerons don’t work. <<No, probably not. Unchecking DX disconnected them.>> Now, I must be doing something wrong here with these few items and don’t want to continue to set up all buttons if a few don’t work.Can anyone set me on the correct path ? <<Go into the GUI, check that you're in Direct Mode and that if you go to the Test/Calibrate screen you see all three controllers listed there. Use the "Add" button on the tool bar and add the Yoke, Throttle, and Pedals. Download the map, the controllers will change names to Control Manager Device 1, 2, and 3 rather than the Yoke/Quad/Pedal. FS doesn't recognize those controllers and has no special defaults for those so it's going to give the same generic assignments to all three of you controls. For example, your yoke will control ailerons and elevators as expected, but so too will the first two throttle levers and the toe brakes. Those are all X/Y pairs and by default the'll end up tied to the same functions. You need to make a trip through the FS Controls Assignments dialog and at least make sure there are no duplicate assignments to the same axis. Initiall they'll alll have their first axs assigned to ailerons, you'll want to the first TQ lever to the throttle, something besides ailerons anyway.The left to brake will be your 3rd aileron axis, normally it's assigned toe brakes, and you'll need to check the "Reverse" box in the FS assignments dialog. It's a good idea to check the FS Sensitivity and Null Zone screen too. All the Null sliders should be fully left, all the Sensitivity sliders should be fully right. FS will normally set the 5th axis on the TQ ot 0% sensitivity, which is very confusing at first because FS wll assign it normally, but it has no effect on the control surface because of the zeroed sensitivity setting.I think you're biggest problem was with unchecking DX mode. If you're going to build the map with just characters, you would do that, but it seldom happens with axes. DX has a few other advantages. In any case, with things in DX mode the axis will have some effect and you know something's happening and get a hint as to what needs fixing.Anyway, maybe that will clear some of it up for you. My apologies for the delayed response, I haven't been online a lot the last week or so and didn't see this slip passed. I the Hangar (http://www.ch-hangar.com) is available, you can usually get a much quicker response over there, it's been down on server problems since the 8th though. Seems like it's working again okay now, though.Let me know about the 3.0 stuff. I'm working on the CM right now, if it's a problem I'll see if it can be fixed. If it's "Unknown" though, then you'll have to talk CH, it would have to be hardware if it has anything to do with the CH stuff at all.Best regards,- BobThe StickWorkshttp://www.stickworks.com

Bob:I have been working very hard on this item and have slowly been eliminating the possibilities of what could be wrong. Here is what I have determined....1. Plugging a unit into the usb 3, going to the control manager, using as a new map and adding just that one unit, the unit appears there, go into test/cal and unit shows up there, but totally unresponsive there. This happens regardless of the unit plugged in.2. All units will show up in the games controller.Now, I have one usb 2 port and two usb 3 ports. Neither of the usb 3 ports will work with this software. No problem with the usb 2 port.I purchased a splitter unit which I plugged into the usb 2 port and it gives me 4 ports to plug in to. Using this, I can load my original map, and see all units on the test/cal screen and all are now responsive.I can then run the CMstart, run FSX, and all is ok.This deduction tells me that the software will not work with the usb 3 ports. Now, if I plug a memory stick into the usb 3 ports, it works and that tells me that the usb 3 ports are working satisfactorily.You say you have not worked with usb 3 ports.........almost all machines today being sold are using usb 2 and usb 3 ports and so the software should be compliant with these usb 3 ports.Even though I now have everything working with this splitter, I would prefer to have the software work with the usb 3 ports so that I do not have to use this splitter as it is a pain.If you are currently working on the CM as you say, I suggest you test out with a unit plugged into a usb 3 and you will verify what I have detailed above.Ray

Hi Ray,>> This deduction tells me that the software will not work with the usb 3 ports. Now, if I plug a memory stick into the usb 3 ports, it works and that tells me that the usb 3 ports are working satisfactorily. <<Yes, I'd agree with you on all points. It can't actually be an incompatibility with the ports though, the CM doesn't interact with them at all. Only hub chip manufacturers and MS can play around down there. You've probably noticed that USB devices always show up as two entries. One is the output of the USB stack, and that's protected system stuff. The other is the output of the HID stack, the "Hid-compliant game controller" that the sim sees. That's what the CM puts up. It gets it's data from the USB driver stack, it doesn't really talk to the USB device or port at the hardware level at all. That's really a hardware transaction between the controller and the chipset, the chipset collects the data and makes it available at the top of the USB stack. That's where the CM collects it. Anyway, I'll need to see what they've changed and figure the workaround.>> Even though I now have everything working with this splitter, I would prefer to have the software work with the usb 3 ports so that I do not have to use this splitter as it is a pain. <<If you want to get rid of the external hub, the best thing to use is one of those PCI -> USB 2.0 cards. They come with 4 or 5 2.0 hubs which are fine for scanners, etc. The power is right off the motherboard, too. External hubs just divvy up the bandwidth that one motherboard hub offers. The cards give you the equivalent of 4 or 5 more motherboard hubs, and it would leave the 3.0 ports available for devices that moved lots of data.USB 3.0 is capable of something like 5 gigabits/second as I recall. The joystick moves around 4 kilobits/second maximimum, normally considerably less. I expect that as time goes along the 3.0 stuff will see utilization for external mass storage, things that need lots of data. Joystick hardly need that bandwidth but the way things seem to go, in year or two 3.0 will probably be the only thing they supply at all. It has to be fixed, but I don't think that will be any real problem. I won't know for sure until I've got one in front of me, though.>> If you are currently working on the CM as you say, I suggest you test out with a unit plugged into a usb 3 and you will verify what I have detailed above. <<Oh, I don't doubt it at all, Ray. It's just the first report I've had of a problem there. I can't find anywhere you mention whether you're using Win7 32-bit or 64-bit. If it's 32-bit, it may be possible to just replace the driver, with 64-bit it will probably need to be a complete installation because of the signing. A 32-bit fix might be quicker, I haven't tried yet to find out whether Win 7 will let you replace one driver manually, Vista was a little picky about it sometimes. Anyway, 32-bit and I could do the one driver first, otherwise it'll have to wait for the installer to be complete.If you want to, drop me and email at:stickworks (at) verizon (dot) netand I can feed you the betas and keep you in the loop. Otherwise, probably the first place it will get announced is on the CH page and over at the CH Hangar (http://www.ch-hangar.com). I'll need to get the card first, that'll take a few days, but if I'm right about where the problem lies it could get fixed pretty quickly, at least for 32-bit.Best regards,- BobThe StickWorkshttp://www.stickworks.com