Spug Posted February 12, 2019 Report Posted February 12, 2019 I have two model 2238-CONN USB boards(desktop aviators) connected to provide button/switch inputs to FSX using FSUIPC 4.968 in a Windows 10 system. FSUIPC only seems to allow one of the two boards at a time to connect and assigns the buttons specified in the INI file to that board. Is there a way to get both working with their individual ID's and button assignments? FSUIPC4.JoyScan.csv
Pete Dowson Posted February 12, 2019 Report Posted February 12, 2019 9 hours ago, Spug said: I have two model 2238-CONN USB boards(desktop aviators) connected to provide button/switch inputs to FSX using FSUIPC 4.968 in a Windows 10 system. FSUIPC only seems to allow one of the two boards at a time to connect and assigns the buttons specified in the INI file to that board. Is there a way to get both working with their individual ID's and button assignments? FSUIPC4.JoyScan.csv First, your FSUIPC4 is way out of date,, and changes have certainly been made in this area since 4.968. The currently supported version is 4.974. Update your copy then try again. If there is still a problem, as well as the fresh Joyscan file we need to see the FSUIPC4.INI and FSUIPC4.LOG, please. The JoyScan file does show some worrying indications, though. None of the 2235- devices (three of them: 2xCON, 1xDP) give returns when their data is read during the scan, nor in fact does the "DP3T Emulator". Three of those 4 devices are being accepted by FSUIPC "with reservations", whilst, as you found, one of the 2235-CON devices is not accepted at all. It is likely that if you only connect one of the two identical devices at a time, Windows is identifying both as the same device -- it can't tell any difference by reading their IDs. When we do get you sorted with both devices, they will need to remain connected all the time and to the same USB ports, else there will be a mix up with the assignments. Pete
Spug Posted February 12, 2019 Author Report Posted February 12, 2019 It appears to be working now. Your suggestion of upgrading to the latest version, 4.974 seems to have corrected the problem. Now, both boards are recognized. Thanks for your help Pete!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now