As I try to get PSX setup for my system (day 3) I have the following issues. Before I start all my PFC Throttle Quadrant Console with the Two Engine Jet Enhanced Throttle Quadrant (PFC) work without any issues using P3d and the PMDG B744.
1. I was able to assign and calibrate FLAPS without any issues. When I went to assign the throttles I discovered the right throttle lever also moves the FLAPS assigned earlier (they are positions 5 & 6). Basically positions five and six on the PFC are assigned the same USB location. A link to my setup (https://flypfc.com/shop/throttle-quadrants/jet-throttle-quadrants/two-engine-jet-enhanced-spoiler-throttle-reverser-flap-ga-button/)
2. I way unable to find Reverser 1 & 2 and Reverser 3 & 4 in the USB drop down menu similar to those for the Throttles.
3. I was unable to locate an assignment for the Parking Brake in the USB drop down menu.
4. I was unable to get the Gear Cycle to work correctly with the Gear Lever on the PFC. Moving the PFC Gear Switch to the up position brings the Gear Handle from Down to OFF. I'm not sure that will raise the gear? I read earlier where one user had created a "work around" but never was able to figure out what that was.
I'm still struggling with the screens, but will start another thread if I am unable to get it resolved.
Bode
I went back into USB and made sure that position 5 and position 6 were not assigned any where else. In the USB page under line 140. PFC Throttle Quadrant Control - Slider there is a USB value shown. I can move position 5 and the value will change between 970 and -890. I can then move position 6 and the value will be between 960 and a -960. Again both USB values only show/move on Line 140. I need position 5 to be Throttle 3 &4 and position 6 to be Flaps.
Bode
I'm not sure what you mean by the word "position" ("position 5 and position 6") in the context of the word "line" (line 140). In your comment, do they have the same meaning -- "position" and "line"?
So do you have at least 140 USB items on the USB list?
Does it look like this?
...
Item #5 = Left throttle?
Item #6 = Right throttle?
...
etc.
...
Item #140 = Flap lever?
...
Or, by "position 5 and 6", do you mean flap lever positions? (Flaps 20 and 25?)
The flap calibration feature is only available for the slider which is assigned to "Flaps" on the axis pop-up menu.
The axis pop-up menu I mean is the one that provides these functions:
------------------
Off
Elevator
Aileron
etc.
etc.
Flaps
Throttles 1 & 2
Throttles 3 & 4
------------------
Are we on the same page?
An axis item is an item that provides a "Calibrate" button, followed by a USB signal indicator, followed by a pop-up menu. On this menu you may select "Flaps".
All other items are button items. Those have no "Calibrate" button.
|-|ardy
Bizarre.
You are not running more than one PSX instance at a time, are you? I mean, you're not running two or more networked PSX instances on the computer where your USB stuff is plugged in?
Could you please post the text stored in the following files?
Aerowinx/Developers/USB-Detect.txt
Aerowinx/Logs/errors.txt
Thank you.
|-|ardy
(The term "slider" is used for all axes that have no centering function. E.g. aileron, rudder, elevator are axes. Throttles, speedbrake, flaps, toe brakes are sliders.)
Another way to approach this is to unassign all the USB axes in PSX, to get to a point where the controller isn't doing anything. Then start assigning axes one-by-one to the hardware.
If no USB axes are assigned in PSX, then moving the levers on the throttle hardware should do nothing.
Do you still see the problem if you assign only one hardware axis to something in PSX?
Quote from: Hardy Heinlin on Thu, 23 Jun 2022 16:24
Bizarre.
You are not running more than one PSX instance at a time, are you? I mean, you're not running two or more networked PSX instances on the computer where your USB stuff is plugged in?
Could you please post the text stored in the following files?
Aerowinx/Developers/USB-Detect.txt
Aerowinx/Logs/errors.txt
Thank you.
|-|ardy
(The term "slider" is used for all axes that have no centering function. E.g. aileron, rudder, elevator are axes. Throttles, speedbrake, flaps, toe brakes are sliders.)
USB detection test:
USB Receiver | Unknown | 0 | Unknown | 0; Consumer Control;
USB Receiver | Unknown | 0 | Unknown | 1; Numeric Key Pad;
USB Receiver | Unknown | 0 | Unknown | 2; Button 2;
USB Receiver | Unknown | 0 | Unknown | 3; Button 3;
USB Receiver | Unknown | 0 | Unknown | 4; Button 4;
USB Receiver | Unknown | 0 | Unknown | 5; Button 5;
USB Receiver | Unknown | 0 | Unknown | 6; Button 6;
USB Receiver | Unknown | 0 | Unknown | 7; Button 7;
USB Receiver | Unknown | 0 | Unknown | 8; Button 8;
USB Receiver | Unknown | 0 | Unknown | 9; Button 9;
USB Receiver | Unknown | 0 | Unknown | 10; Button 10;
USB Receiver | Unknown | 0 | Unknown | 11; Button 11;
USB Receiver | Unknown | 0 | Unknown | 12; Button 12;
USB Receiver | Unknown | 0 | Unknown | 13; Button 13;
USB Receiver | Unknown | 0 | Unknown | 14; Button 14;
USB Receiver | Unknown | 0 | Unknown | 15; Button 15;
USB Receiver | Unknown | 0 | Unknown | 16; Button 16;
USB Receiver | Unknown | 0 | Unknown | 17; Button 17;
USB Receiver | Unknown | 0 | Unknown | 18; Button 18;
USB Receiver | Unknown | 0 | Unknown | 19; Button 19;
USB Receiver | Unknown | 0 | Unknown | 20; Button 20;
USB Receiver | Unknown | 0 | Unknown | 21; Button 21;
USB Receiver | Unknown | 0 | Unknown | 23; Button 22;
USB Receiver | Unknown | 0 | Unknown | 24; Button 23;
USB Receiver | Unknown | 0 | Unknown | 25; Button 24;
USB Receiver | Unknown | 0 | Unknown | 26; Button 25;
USB Receiver | Unknown | 0 | Unknown | 27; Button 26;
USB Receiver | Unknown | 0 | Unknown | 28; Button 27;
USB Receiver | Unknown | 0 | Unknown | 29; Button 28;
USB Receiver | Unknown | 0 | Unknown | 30; Button 29;
USB Receiver | Unknown | 0 | Unknown | 31; Button 30;
USB Receiver | Unknown | 0 | Unknown | 0; System Sleep;
USB Receiver | Unknown | 0 | Unknown | 1; System Power;
USB Receiver | Unknown | 0 | Unknown | 2; System Wake Up;
PFC Cirrus Yoke | Stick | 0 | Unknown | slider; Throttle; (analog)
PFC Cirrus Yoke | Stick | 0 | Unknown | y; Y Axis; (analog)
PFC Cirrus Yoke | Stick | 0 | Unknown | x; X Axis; (analog)
PFC Cirrus Yoke | Stick | 0 | Unknown | 0; Button 0;
PFC Cirrus Yoke | Stick | 0 | Unknown | 1; Button 1;
PFC Cirrus Yoke | Stick | 0 | Unknown | 2; Button 2;
PFC Cirrus Yoke | Stick | 0 | Unknown | 3; Button 3;
PFC Cirrus Yoke | Stick | 0 | Unknown | 4; Button 4;
PFC Cirrus Yoke | Stick | 0 | Unknown | 5; Button 5;
PFC Cirrus Yoke | Stick | 0 | Unknown | 6; Button 6;
PFC Cirrus Yoke | Stick | 0 | Unknown | 7; Button 7;
PFC Cirrus Yoke | Stick | 0 | Unknown | 8; Button 8;
PFC Cirrus Yoke | Stick | 0 | Unknown | 9; Button 9;
PFC Cirrus Yoke | Stick | 0 | Unknown | 10; Button 10;
PFC Cirrus Yoke | Stick | 0 | Unknown | 11; Button 11;
PFC Cirrus Yoke | Stick | 0 | Unknown | 12; Button 12;
PFC Cirrus Yoke | Stick | 0 | Unknown | 13; Button 13;
PFC Cirrus Yoke | Stick | 0 | Unknown | 14; Button 14;
PFC Cirrus Yoke | Stick | 0 | Unknown | 15; Button 15;
PFC Cirrus Yoke | Stick | 0 | Unknown | unknown; T; (analog)
PFC Cirrus Yoke | Stick | 0 | Unknown | unknown; S; (analog)
PFC Cirrus Yoke | Stick | 0 | Unknown | unknown; R; (analog)
PFC Cirrus Yoke | Stick | 0 | Unknown | unknown; Q; (analog)
PFC Cirrus Yoke | Stick | 0 | Unknown | unknown; P; (analog)
PFC Cirrus Yoke | Stick | 0 | Unknown | unknown; O; (analog)
PFC Cirrus Yoke | Stick | 0 | Unknown | unknown; N; (analog)
PFC Cirrus Yoke | Stick | 0 | Unknown | unknown; M; (analog)
PFC Cirrus Yoke | Stick | 0 | Unknown | unknown; L; (analog)
PFC Cirrus Yoke | Stick | 0 | Unknown | unknown; K; (analog)
PFC Cirrus Yoke | Stick | 0 | Unknown | unknown; J; (analog)
PFC Cirrus Yoke | Stick | 0 | Unknown | unknown; I; (analog)
PFC Cirrus Yoke | Stick | 0 | Unknown | unknown; H; (analog)
PFC Cirrus Yoke | Stick | 0 | Unknown | unknown; G; (analog)
PFC Cirrus Yoke | Stick | 0 | Unknown | unknown; F; (analog)
PFC Cirrus Yoke | Stick | 0 | Unknown | unknown; E; (analog)
PFC Cirrus Yoke | Stick | 0 | Unknown | unknown; D; (analog)
PFC Cirrus Yoke | Stick | 0 | Unknown | unknown; C; (analog)
PFC Cirrus Yoke | Stick | 0 | Unknown | unknown; B; (analog)
PFC Cirrus Yoke | Stick | 0 | Unknown | unknown; A; (analog)
G432 Gaming Headset | Unknown | 0 | Unknown | 0; Volume Decrement;
G432 Gaming Headset | Unknown | 0 | Unknown | 1; Volume Increment;
G432 Gaming Headset | Unknown | 0 | Unknown | 2; Mute;
G432 Gaming Headset | Unknown | 0 | Unknown | 3; Button 0;
G432 Gaming Headset | Unknown | 0 | Unknown | 4; Button 1;
G432 Gaming Headset | Unknown | 0 | Unknown | 5; Button 5;
G432 Gaming Headset | Unknown | 0 | Unknown | unknown; Axis 6; (analog)
G432 Gaming Headset | Unknown | 0 | Unknown | unknown; Axis 7; (analog)
Saitek X52 Flight Control System | Stick | 0 | Unknown | y; Y Axis; (analog)
Saitek X52 Flight Control System | Stick | 0 | Unknown | x; X Axis; (analog)
Saitek X52 Flight Control System | Stick | 0 | Unknown | rz; Z Rotation; (analog)
Saitek X52 Flight Control System | Stick | 0 | Unknown | slider; Slider; (analog)
Saitek X52 Flight Control System | Stick | 0 | Unknown | ry; Y Rotation; (analog)
Saitek X52 Flight Control System | Stick | 0 | Unknown | rx; X Rotation; (analog)
Saitek X52 Flight Control System | Stick | 0 | Unknown | z; Z Axis; (analog)
Saitek X52 Flight Control System | Stick | 0 | Unknown | 0; Button 0;
Saitek X52 Flight Control System | Stick | 0 | Unknown | 1; Button 1;
Saitek X52 Flight Control System | Stick | 0 | Unknown | 2; Button 2;
Saitek X52 Flight Control System | Stick | 0 | Unknown | 3; Button 3;
Saitek X52 Flight Control System | Stick | 0 | Unknown | 4; Button 4;
Saitek X52 Flight Control System | Stick | 0 | Unknown | 5; Button 5;
Saitek X52 Flight Control System | Stick | 0 | Unknown | 6; Button 6;
Saitek X52 Flight Control System | Stick | 0 | Unknown | 7; Button 7;
Saitek X52 Flight Control System | Stick | 0 | Unknown | 8; Button 8;
Saitek X52 Flight Control System | Stick | 0 | Unknown | 9; Button 9;
Saitek X52 Flight Control System | Stick | 0 | Unknown | 10; Button 10;
Saitek X52 Flight Control System | Stick | 0 | Unknown | 11; Button 11;
Saitek X52 Flight Control System | Stick | 0 | Unknown | 12; Button 12;
Saitek X52 Flight Control System | Stick | 0 | Unknown | 13; Button 13;
Saitek X52 Flight Control System | Stick | 0 | Unknown | 14; Button 14;
Saitek X52 Flight Control System | Stick | 0 | Unknown | 15; Button 15;
Saitek X52 Flight Control System | Stick | 0 | Unknown | 16; Button 16;
Saitek X52 Flight Control System | Stick | 0 | Unknown | 17; Button 17;
Saitek X52 Flight Control System | Stick | 0 | Unknown | 18; Button 18;
Saitek X52 Flight Control System | Stick | 0 | Unknown | 19; Button 19;
Saitek X52 Flight Control System | Stick | 0 | Unknown | 20; Button 20;
Saitek X52 Flight Control System | Stick | 0 | Unknown | 21; Button 21;
Saitek X52 Flight Control System | Stick | 0 | Unknown | 23; Button 22;
Saitek X52 Flight Control System | Stick | 0 | Unknown | 24; Button 23;
Saitek X52 Flight Control System | Stick | 0 | Unknown | 25; Button 24;
Saitek X52 Flight Control System | Stick | 0 | Unknown | 26; Button 25;
Saitek X52 Flight Control System | Stick | 0 | Unknown | 27; Button 26;
Saitek X52 Flight Control System | Stick | 0 | Unknown | 28; Button 27;
Saitek X52 Flight Control System | Stick | 0 | Unknown | 29; Button 28;
Saitek X52 Flight Control System | Stick | 0 | Unknown | 30; Button 29;
Saitek X52 Flight Control System | Stick | 0 | Unknown | 31; Button 30;
Saitek X52 Flight Control System | Stick | 0 | Unknown | pov; Hat Switch;
Saitek X52 Flight Control System | Stick | 0 | Unknown | unknown; Move Up/Down; (analog)
Saitek X52 Flight Control System | Stick | 0 | Unknown | unknown; Move Right/Left; (analog)
Gaming Keyboard G105 | Unknown | 0 | Unknown | 0; Mute;
Gaming Keyboard G105 | Unknown | 0 | Unknown | 1; Volume Decrement;
Gaming Keyboard G105 | Unknown | 0 | Unknown | 2; Volume Increment;
Gaming Keyboard G105 | Unknown | 0 | Unknown | 3; Play/Pause;
Gaming Keyboard G105 | Unknown | 0 | Unknown | 4; Stop;
Gaming Keyboard G105 | Unknown | 0 | Unknown | 5; Scan Previous Track;
Gaming Keyboard G105 | Unknown | 0 | Unknown | 6; Scan Next Track;
Saitek Pro Flight Combat Rudder Pedals | Stick | 0 | Unknown | y; Y Axis; (analog)
Saitek Pro Flight Combat Rudder Pedals | Stick | 0 | Unknown | x; X Axis; (analog)
Saitek Pro Flight Combat Rudder Pedals | Stick | 0 | Unknown | rz; Z Rotation; (analog)
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | slider; Dial; (analog)
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | slider; Slider; (analog)
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | rz; Z Rotation; (analog)
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | ry; Y Rotation; (analog)
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | rx; X Rotation; (analog)
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | z; Z Axis; (analog)
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | x; X Axis; (analog)
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | 0; Button 0;
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | 1; Button 1;
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | 2; Button 2;
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | 3; Button 3;
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | 4; Button 4;
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | 5; Button 5;
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | 6; Button 6;
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | 7; Button 7;
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | unknown; T; (analog)
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | unknown; S; (analog)
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | unknown; R; (analog)
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | unknown; Q; (analog)
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | unknown; P; (analog)
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | unknown; O; (analog)
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | unknown; N; (analog)
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | unknown; M; (analog)
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | unknown; L; (analog)
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | unknown; K; (analog)
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | unknown; J; (analog)
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | unknown; I; (analog)
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | unknown; H; (analog)
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | unknown; G; (analog)
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | unknown; F; (analog)
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | unknown; E; (analog)
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | unknown; D; (analog)
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | unknown; C; (analog)
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | unknown; B; (analog)
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | unknown; A; (analog)
[Aerowinx Precision Simulator - Exceptions]
There were no errors shown.
Bode
I had tried Will's method before I started this post. The only place where the Right Throttle Lever and the FLAP Lever show USB movement is Line 140.
The six axes for the Jet Enhanced package are from left to right -
1. Speed Brake
2. Left Throttle
3. Left Reverser
4. Right Reverser
5. Right Throttle
6. Flaps
The PFC Throttle Quadrant in P3dv5.3 is showing the following:
Spoiler - Z Axes
Left Throttle - X Rotation
Left Reverser - Y Rotation
Right Reverser - Z Rotation
Right Throttle - Dial
Flaps - Slider
If you look at your blue chart Line 141 should be available to Slider (Flaps). It is not. The USB value for Line 140 is 0.
If you look at your blue chart Line 140 should be available to Right Throttle which it is.
The problem is that Line 140 is also available to Flaps
From Line 140 to Line 146 there are USB values for each line except Line 141 which is 0. From Line 140 to Line 146 there are Calibration boxes for each line. For clarity Line 146 is the Rudder Trim rotary dial.
It appears to me that there is a coding error concerning Line 140 and Line 141. I do understand these type problems. So the question is how can this coding error be resolved.
I was going to send pictures of the USB page but I couldn't figure out how to post them.
Bode
The problem is that this erroneous flap lever signal is coming from a third-party Java interface which lies outside my coding scope. I might fix the problem if it were on the PSX assignment side of the system. But it's on the input signal side which I can't monitor nor analyse.
PSX obviously detects the "existence" of all hardware parts correctly; each part becomes an individual list item in the sim's detection text and on the sim's USB page. The only unusual effect being the flap lever's live signal coming in on an already occupied throttle channel.
Sherlock Holmes mode: I'm asking myself, what's so special in room #141 compared to the others? #141 is the only case where the function name and the part name are identical: They both read "slider". (Not, for example, "rz" and "Z Rotation", but "slider" and "Slider"; aside from the second name starting with a capital.)
If that could be a problem in the Java USB interface, let's see if there's a similar problem on your Saitek device. There you have another "slider" double name on the 4th Saitek part:
Saitek X52 Flight Control System | Stick | 0 | Unknown | y; Y Axis; (analog)
Saitek X52 Flight Control System | Stick | 0 | Unknown | x; X Axis; (analog)
Saitek X52 Flight Control System | Stick | 0 | Unknown | rz; Z Rotation; (analog)
Saitek X52 Flight Control System | Stick | 0 | Unknown | slider; Slider; (analog)
Just for a test: Have you assigned anything there and does it work correctly?
|-|ardy
Here are two ideas.
If it turns out that there is an error late in the USD assignments, then you may want to make sure that your throttle hardware is recognized first. To do this, you could physically unplug all the USB devices from your computer. Then plug in only the throttle hardware. That way, it would occupy USB positions 1-35 instead of 120-145 (or whatever). This could help isolate the error. If it works this way, then you could plug your other USB devices in to the computer sequentially to preserve the throttle hardware's principal spot.
The other idea has to do with the gear switch. The problem (if I understand correctly) is that your hardware switch has only two positions (UP and DOWN) while the real Boeing gear handle has three positions (UP, DOWN, and OFF). One way to make this work with a two position switch is to assign the hardware gear switch to the gear toggle command, but also assign a joystick button to the same thing.
That way, to raise the gear, you would move the lever up, and tap the button. To move the gear to off, tap the button again. Then to lower the gear, move the lever down.
GEAR UP: Move the lever up, tap the button
GEAR OFF: Tap the button
GEAR DOWN: Move the lever down
It's not "realistic," but might be more natural than just using the lever alone (where it could get out of synch, e.g. down when the gear is up, etc.).
Another option is to recognize that PSX was designed from the ground up for hardware cockpit support, but NOT for USB.
So the proper solution is to use an external program to listen to all USB events and then use this program to map the controls to PSX's network. Only code can solve this mapping challenge; trying to design a point and click interface powerful enough to support all present and future USB controls and all PSX controls is slightly out of scope of the product.
Of course this does not help you today.
And example would be the gear lever. An UP/DOWN lever will never properly simulate an UP/OFF/DOWN lever. But code can make it behave. When UP, the lever moves up, and when all proper conditions have been satisfied, it sends the OFF command underground. When DOWN, the code assures the lever of PSX is down no matter where it was. This kind of stuff is immensely difficult to pre-think for all possible combinations of USB controls out there.
Since all USB controls are designed with MSFS in mind, the problem exists uniquely for PSX and other less well known simulators, unfortunately.
Hoppie
Interestingly, if somebody would write the USB-to-PSX Bridge in Java using this same library, then the same problem should occur. Maybe it is useful to try this, if only as a device dumping one-shot program.
Hoppie
I'm always trying to be 100% sure that it's not a fault in my code. Just got another idea regarding "equal name" check within an iteration. But I found no such check in my code. What I mean is this:
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | slider; Dial; (analog)
PFC Throttle Quadrant Console | Unknown | 0 | Unknown | slider; Slider; (analog)
This time I don't mean the "slider; Slider;" thing within the same part. Now I mean the "slider" in the one part and the next slider in the next part. Maybe -- maybe -- the iteration puts the next slider's signal reference into the previous slider's reference because the previous type is also a "slider" (sort of "if equal do not iterate"). If this is really the cause, it should be reproducible in other cases where two sliders are listed one after the other. Does anyone have such a device? E.g. a 4-lever thrust quadrant? Are there 4 parts of the "slider" type?
|-|
1. If my idea works (see above), then a solution may be to add back the USB devices sequentially so that the problematic lines are occupied by buttons, or even better, by a button or axis that goes unused.
2. Hardy, I can test your "slider" question when I get home tonight. I use a throttle quadrant that has 4 throttles, 4 reversers, speedbrakes, and flaps. The quadrant itself is separated by the manufacturer into two USB devices of 5 axes each. I'll post USB-detect.txt later if that will help.
Aha ... that was in 1995 :-)
FS5 and Compuserve forums ...
I can well imagine that there were some talks about sidle-slip landings with V-tail aircraft :-)
Cheers!
|-|ardy
Here we go, here is my USB-Detect.txt. I don't know if it helps or is relevant. The only takeaways for me are (1) nothing is called "slider," and (2) I have a controller with 6 axes -- Throttletek 1 -- and all six work fine.
Here is it:
USB detection test:
MFG Crosswind V2 | Stick | 0 | Unknown | rz; Z Rotation; (analog)
MFG Crosswind V2 | Stick | 0 | Unknown | y; Y Axis; (analog)
MFG Crosswind V2 | Stick | 0 | Unknown | x; X Axis; (analog)
MFG Crosswind V2 | Stick | 0 | Unknown | 0; Button 0;
MFG Crosswind V2 | Stick | 0 | Unknown | 1; Button 1;
Joystick - HOTAS Warthog | Stick | 0 | Unknown | 0; Button 0;
Joystick - HOTAS Warthog | Stick | 0 | Unknown | 1; Button 1;
Joystick - HOTAS Warthog | Stick | 0 | Unknown | 2; Button 2;
Joystick - HOTAS Warthog | Stick | 0 | Unknown | 3; Button 3;
Joystick - HOTAS Warthog | Stick | 0 | Unknown | 4; Button 4;
Joystick - HOTAS Warthog | Stick | 0 | Unknown | 5; Button 5;
Joystick - HOTAS Warthog | Stick | 0 | Unknown | 6; Button 6;
Joystick - HOTAS Warthog | Stick | 0 | Unknown | 7; Button 7;
Joystick - HOTAS Warthog | Stick | 0 | Unknown | 8; Button 8;
Joystick - HOTAS Warthog | Stick | 0 | Unknown | 9; Button 9;
Joystick - HOTAS Warthog | Stick | 0 | Unknown | 10; Button 10;
Joystick - HOTAS Warthog | Stick | 0 | Unknown | 11; Button 11;
Joystick - HOTAS Warthog | Stick | 0 | Unknown | 12; Button 12;
Joystick - HOTAS Warthog | Stick | 0 | Unknown | 13; Button 13;
Joystick - HOTAS Warthog | Stick | 0 | Unknown | 14; Button 14;
Joystick - HOTAS Warthog | Stick | 0 | Unknown | 15; Button 15;
Joystick - HOTAS Warthog | Stick | 0 | Unknown | 16; Button 16;
Joystick - HOTAS Warthog | Stick | 0 | Unknown | 17; Button 17;
Joystick - HOTAS Warthog | Stick | 0 | Unknown | 18; Button 18;
Joystick - HOTAS Warthog | Stick | 0 | Unknown | pov; Hat Switch;
Joystick - HOTAS Warthog | Stick | 0 | Unknown | y; Y Axis; (analog)
Joystick - HOTAS Warthog | Stick | 0 | Unknown | x; X Axis; (analog)
throttleTek 2 | Stick | 0 | Unknown | rx; X Rotation; (analog)
throttleTek 2 | Stick | 0 | Unknown | z; Z Axis; (analog)
throttleTek 2 | Stick | 0 | Unknown | y; Y Axis; (analog)
throttleTek 2 | Stick | 0 | Unknown | x; X Axis; (analog)
throttleTek 2 | Stick | 0 | Unknown | 0; Button 0;
throttleTek 2 | Stick | 0 | Unknown | 1; Button 1;
throttleTek 2 | Stick | 0 | Unknown | 2; Button 2;
throttleTek 2 | Stick | 0 | Unknown | 3; Button 3;
throttleTek 2 | Stick | 0 | Unknown | 4; Button 4;
throttleTek 2 | Stick | 0 | Unknown | 5; Button 5;
throttleTek 2 | Stick | 0 | Unknown | 6; Button 6;
throttleTek 2 | Stick | 0 | Unknown | 7; Button 7;
throttleTek 2 | Stick | 0 | Unknown | 8; Button 8;
throttleTek 2 | Stick | 0 | Unknown | 9; Button 9;
throttleTek 2 | Stick | 0 | Unknown | 10; Button 10;
throttleTek 2 | Stick | 0 | Unknown | 11; Button 11;
throttleTek 2 | Stick | 0 | Unknown | 12; Button 12;
throttleTek 2 | Stick | 0 | Unknown | 13; Button 13;
throttleTek 2 | Stick | 0 | Unknown | 14; Button 14;
throttleTek 2 | Stick | 0 | Unknown | 15; Button 15;
throttleTek 2 | Stick | 0 | Unknown | 16; Button 16;
throttleTek 2 | Stick | 0 | Unknown | 17; Button 17;
throttleTek 2 | Stick | 0 | Unknown | 18; Button 18;
throttleTek 2 | Stick | 0 | Unknown | 19; Button 19;
throttleTek 2 | Stick | 0 | Unknown | 20; Button 20;
throttleTek 2 | Stick | 0 | Unknown | 21; Button 21;
throttleTek 2 | Stick | 0 | Unknown | 23; Button 22;
throttleTek 2 | Stick | 0 | Unknown | 24; Button 23;
throttleTek 2 | Stick | 0 | Unknown | 25; Button 24;
throttleTek 2 | Stick | 0 | Unknown | 26; Button 25;
throttleTek 2 | Stick | 0 | Unknown | 27; Button 26;
throttleTek 2 | Stick | 0 | Unknown | 28; Button 27;
throttleTek 2 | Stick | 0 | Unknown | 29; Button 28;
throttleTek 2 | Stick | 0 | Unknown | 30; Button 29;
throttleTek 2 | Stick | 0 | Unknown | 31; Button 30;
throttleTek 2 | Stick | 0 | Unknown | pov; Hat Switch;
Cat3Design A320 Tiller | Wheel | 0 | Unknown | 0; Button 0;
Cat3Design A320 Tiller | Wheel | 0 | Unknown | 1; Button 1;
Cat3Design A320 Tiller | Wheel | 0 | Unknown | 2; Button 2;
Cat3Design A320 Tiller | Wheel | 0 | Unknown | 3; Button 3;
Cat3Design A320 Tiller | Wheel | 0 | Unknown | 4; Button 4;
Cat3Design A320 Tiller | Wheel | 0 | Unknown | x; Steering; (analog)
throttleTek 1 | Stick | 0 | Unknown | rz; Z Rotation; (analog)
throttleTek 1 | Stick | 0 | Unknown | ry; Y Rotation; (analog)
throttleTek 1 | Stick | 0 | Unknown | rx; X Rotation; (analog)
throttleTek 1 | Stick | 0 | Unknown | z; Z Axis; (analog)
throttleTek 1 | Stick | 0 | Unknown | y; Y Axis; (analog)
throttleTek 1 | Stick | 0 | Unknown | x; X Axis; (analog)
throttleTek 1 | Stick | 0 | Unknown | 0; Button 0;
throttleTek 1 | Stick | 0 | Unknown | 1; Button 1;
throttleTek 1 | Stick | 0 | Unknown | 2; Button 2;
throttleTek 1 | Stick | 0 | Unknown | 3; Button 3;
throttleTek 1 | Stick | 0 | Unknown | 4; Button 4;
throttleTek 1 | Stick | 0 | Unknown | 5; Button 5;
throttleTek 1 | Stick | 0 | Unknown | 6; Button 6;
throttleTek 1 | Stick | 0 | Unknown | 7; Button 7;
throttleTek 1 | Stick | 0 | Unknown | 8; Button 8;
throttleTek 1 | Stick | 0 | Unknown | 9; Button 9;
throttleTek 1 | Stick | 0 | Unknown | 10; Button 10;
throttleTek 1 | Stick | 0 | Unknown | 11; Button 11;
throttleTek 1 | Stick | 0 | Unknown | 12; Button 12;
throttleTek 1 | Stick | 0 | Unknown | 13; Button 13;
throttleTek 1 | Stick | 0 | Unknown | 14; Button 14;
throttleTek 1 | Stick | 0 | Unknown | 15; Button 15;
throttleTek 1 | Stick | 0 | Unknown | 16; Button 16;
throttleTek 1 | Stick | 0 | Unknown | 17; Button 17;
throttleTek 1 | Stick | 0 | Unknown | 18; Button 18;
throttleTek 1 | Stick | 0 | Unknown | 19; Button 19;
throttleTek 1 | Stick | 0 | Unknown | 20; Button 20;
throttleTek 1 | Stick | 0 | Unknown | 21; Button 21;
throttleTek 1 | Stick | 0 | Unknown | 23; Button 22;
throttleTek 1 | Stick | 0 | Unknown | 24; Button 23;
throttleTek 1 | Stick | 0 | Unknown | 25; Button 24;
throttleTek 1 | Stick | 0 | Unknown | 26; Button 25;
throttleTek 1 | Stick | 0 | Unknown | 27; Button 26;
throttleTek 1 | Stick | 0 | Unknown | 28; Button 27;
throttleTek 1 | Stick | 0 | Unknown | 29; Button 28;
throttleTek 1 | Stick | 0 | Unknown | 30; Button 29;
throttleTek 1 | Stick | 0 | Unknown | 31; Button 30;
throttleTek 1 | Stick | 0 | Unknown | pov; Hat Switch;
Hardy, what version of Java are you using? Do you think that going back to that version would make any difference in my USB problem?
If this doesn't work I'm bringing in the heavy hitter to look at the problem. My grandson is an Aeronautical Engineer who' s about to finish up his Phd. He will be out to our place in a couple of weeks and told me he would fix the problem. He's really good with code. 😎
Bode
I'm using 1.8 and sometimes 12. I don't think that the version would make any difference. The code is in a third party interface and that hasn't changed in the past 7 years. Maybe using Linux or Mac instead of Windows could make a difference, but I don't think so.
|-|ardy