Jump to content

How to rule out software problem in a malfunctioning USB device


SimWare

Recommended Posts

  • Aerosoft

Please login to display this image.



How to rule out software problem in a malfunctioning USB device ?
 

A common support case we have is for strangely behaving axes in a yoke, rudder, throttle, etc.

Symptoms are :

 

  • Non or partially-moving axis
  • Some/all buttons/switches not detected
  • Some/all buttons/switches acting randomly or intermittently
  • Device not recognized at all
  • Random disconnection
  • Vibrating axis
  • Axes interfering with other ones (X moves Y for instance)
  • Dead zones
  • Non linearity
  • Axes acting like ON/OFF contacts

 

These can of course be the result of an electrical malfunction like :

 

  • Broken internal wire or USB cable
  • Shorted potentiometer
  • Mechanically loose potentiometer
  • Damaged USB board
  • Etc.

 

But the unit may be perfectly functioning and still appears as malfunctioning in the simulator because of external reasons :

 

  • Axis isn’t assigned properly (Wrong function or function type)
  • Axis sensitivity isn’t properly set up in the simulator
  • Device isn’t calibrated in Windows
  • Computer USB power supply is to weak or overloaded
  • Device driver or computer USB driver has problem
  • The unit is hooked to a USB hub causing problem

 

The method to locate the problem is to start from the bottom level, NOT from the simulator.
You must make sure Windows receives correct and consistant signals from the device
and correctly sends them to the simulator or any third-party software (FSUIPC, Spad.Next, etc.)

Otherwise, no matter what you do, the result in the last link of the chain, the aircraft, will be wrong.
 

So, once again, don’t start from the top. Start from the bottom.

Follow ALL these steps :

 

  • Find another computer (No simulator, nor driver required. ANY Win 10 PC will do)
  • Again : DO NOT install any driver !
  • If possible and applicable, use another USB cable -> Very important !
  • Connect the device to the computer directly - DO NOT use any USB hub.
  • Start the standard Windows Joystick utility
  • Go in calibration mode and check "Display Raw Data)
  • Move each axis one by one and check the Raw Data value is responding on the full course
    without any interference with other axes.
  • Perform a full calibration of EACH axis and apply it.
  • Check response, linearity and stability of EACH axis.
  • Check all the buttons one by one and see if they illuminate on the utility interface.
    NOTE #1 Honeycomb systems have more than 32 buttons, so you ill need to check buttons above #32 in MSFS configuration panel)
    NOTE #2 : Often in the case of throttle quadrant, the levers have a detent on the low-end of the course or a smaller lever both for  
                      the reverse functions. These detents or small levers often trigger an input too.
                      In the case of reversers malfunction, make sure you test them too.
  • Disconnect the device, restart the computer, reconnect the device and check that the calibration is still correct.

 

See here how to access the calibration utility in Windows.

For symmetrical axes, make sure you follow this procedure.
NOT FOLLOWING IT MAY RESULT IN AXES “JUMPING” ON 50% OF THE COURSE.

 

For buttons or contacts above #32, make sure you follow this procedure.


These are very basic and down to earth common sense steps.

They insure the unit is working well and sends correct information to the computer.

Only then it makes sense to investigate on the software side.

 

 

Link to comment
Share on other sites

  • SimWare changed the title to How to rule out software problem in a malfunctioning USB device
  • 3 weeks later...
  • Aerosoft
52 minutes ago, policarmelo said:

Hello, I have the throttle axis of Motor No.1 moving at 50%, I

Please login to display this image.

sent you a screenshot

Dear Sir,

 

It is most likely a calibration and/or sensitivity cureve issue.
Please check those two tutorials : 
 

Calibration : 

Sensitivity : 

 

 


You also got an answer int the support ticket (#145064) you opened for the same question.


Best regards.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use