Frequently Asked Questins

If your problem is not answered here feel free to ask us trough contact form

Brakes no longer work after adjusting footrests angle

This is normal if you use Manual Calibration or older firmware. You need to recalibrate brake axis ( X and Y) by using MFG Configurator software. Calibration procedure is explained in software manual inside software package. Recalibration is MANDATORY each time you change angle of the footrests !
Alternatively, user can activate Auto Calibration in MFG Configurator (firmware v5.09+)

Common Brake axis issues

1. Always verify working of brakes in MFG Configurator software. If this is working fine from 0 to 100% then read on other FAQ topic regarding windows calibration and in game settings
2. Check that brake axis cables are firmly plugged in. Try to unplugg them and then replugg them and check if problem is solved
3. If using Manual Calibration and you readjusted the angle of the footrests then it is mandatory to CALIBRATE brake axis INSIDE MFG CONFIGURATOR software
4. Sometimes, if you did not tighten footrests angle adjustment screws enough, angle of the pedals can change due to pressure of your heel, and therefore calibration will be wrong. If you experience that you need to recalibrate often this is usually the cause so tighten these screws better.
5. Faulty brake axis cable or FAQ for that
6. If you ever removed brake shaft for e.g. to replace brake springs and by mistake put left shaft in place of right brake shaft and vice versa ...brakes will not work or will work but very poorly/jittery. In that case it is necessary to swap brake shaft's and re-calibrate to make it work again

Faulty brake axis cable- test and replace

This happen very rarely so make sure you read all other brake axis FAQ topics first !

You can inspect brake axis by turning off (untick) autocalibration ON/OFF feature on X and Y axis (called "service mode since v.2.17) and click apply. This is basically sensor inspection mode. In this mode you will have a working signal regardless of angle adjusted and calibration, troughout the range...but it will not be full from 0 to 100%. In fact, it should NEVER reach 0 or 100% signal on axis. This provide us with few handy tests :

1. Swap left and right brake cable connection to main electronics. In essence your left brake will now become Y axis, and right brake will be X axis. IF problem is in the cable it will follow cable now and change axis...but if electronics have issue the problem WILL STAY on same axis regardless of cable being swapped. In this step you determine what is to blame - cable or electronics.

In any case...blow off your contacts and test again ...and use contact spreay if you have one.

2. Shake / wooble faulty brake axis cable near the connector and watch the signal while doing so ( DIVIEW software is more handy to watch signal). If you see the signal suddenly spike to 0% or 100% than its likely that you have faulty cable and need to replace it. Of course, if your signal is already at 0 or 100% and it spikes BACK to normal when you wooble the cable it's also a faulty cable.
Sometimes it's just a poor contact between cable and electronics so it is important to make a proper conclusion before you jump on replacement cable, as replacement take a bit of time and patience.

Cable can be bought in our shop at accesorries section, but take care to buy correct one for your pedals (V1 or V2). Replacement instructions are described ( and in video) on cable product page !

Note : Sometimes, if brake cable is not firmly plugged in or if a signal wire on a cable is cut off, a "ghosting" effect can be seen - meaning that signal from good cable can ghost itself on faulty brake since there is open contact. Pay attention to this possibility to draw correct conclusion !!!

NOTE : If you ever removed brake shaft for e.g. to replace brake springs and by mistake put left shaft in place of right brake shaft and vice versa ...brakes will not work or will work but very poorly/jittery. In that case it is necessary to swap brake shaft's and re-calibrate to make it work again

Brake axis often loose calibration and need to be recalibrated

Most probable cause is if a customer readjusted the angle of the footrests, but while doing so, did not tighten the angle adjustment screws strong enough. In such case, while flying, pressure of the user's heel on the pedal cause the angle of the footrests to be moved from the adjusted angle.
Usually when this happen, user will experience a large deadzone ( non responding zone) at start of pressing brake, and inability to press brake fully to 100%...and therefore re-calibration is required.

Tighten the angle adjustment screws more firmly and recalibrate and pedals will no longer "loose" calibration.

Another thing that customers sometimes wrongly interpret as loose of calibration is actually jitter or loss of signal on brake axis. Therefore check if any of above mentioned brake axis troubles concern you !

Brake axis jump to 50% and then operate smoothly 50-100%

That is because you configured your pedals brake axis with "have center" option turned ON (ticked), but in reality brakes dont have center detent which causes wrong signal interpretation.
Fix this by unticking "have center" option on X and Y axis and click apply. If you are unsure you can also click on "show defaults"  button and software will fix it by reverting all settings to factory defaults.

Alternatively, if such issue is only in the sim and NOT in MFG Configurator -> reset windows calibration for MFG Crosswind to default trough joystick control panel  !

Applying Left and right brake is uneven/ asymetrical

Are you measuring this in DIVIEW on RAW axis readings ? You should ! Also reset windows calibration to default as per FAQ.  Windows Calibration sees brake X and Y axis as something that has defined centar position which you clearly don't have on MFG Crosswind brakes. By letting Windows to calibrate these axis it will record a center position somewhere which will induce non-linearity on axis !

In-game Calibration actually equals windows calibration for many Simulators ( Microsoft, Prepar3d, Xplane...) so tthe above also apply !

If it is still uneven reaction after above fix - > you can tamper with reducing/increasind deadzone start value in MFG Configurator for both X and Y (=20 by default) and deadzone end (default =6) to make both brakes react evenly across full range

I recalibrated on START/STOP button but calibration is not accurate (Firmware 5.09+)

It is most likely that you have "Auto Calibration" turned ON on axis which is fine, but in order for device to train itself new calibration values in this mode (e.g. after changing footrests angle) device need to be restarted (either by replugging or clicking Bootloader button).

Rudder axis (rZ) need to be recalibrated often / cannot calibrate properly

If Rudder axis need to be re-calibrated often than it is most likely That magnet rotated on axis. Actually magnet is glued to the nut at bottom side of big M8x50 screw so it is not a magnet itself that got rotated but the MM8x50 screw holding it !

This issue is known that can happen on MFG Croswind serial numbers < S/N 1964 . Newer pedals (> S/N 1964) have additional M8 nut installed to prevent this from happening but there is always a possibility that nut got loose a little leaving up screw to spin easily.

To determine if this is the cause of your issue turn OFF Autocalibration on/off feature on rZ (rudder) axis (inside MFG Configurator software...since v2.17 called "service mode") and OBSERVE RAW AXIS READING while rudder axis is at rest. We FACTORY SET UP RUDDER CENTER at 25% or 50% (+-1%) which represent magnet rotary orientation ! If your rudder is not at 25% or 50% in this uncalibrated mode than YOU HAVE THIS ISSUE !. Following wideo will explain how to fix it :
NOTE ! Read video description !
NOTE 2 ! MFG Crosswind V1 pedals must be set to = 50% (+- 0,5%) for axis linear behaviour !

Axis issues outside MFG Configurator ( Windows calibration , Game specific setups)

When you have a problem like this it need to be addressed from root hardware to the sim to determine the cause !

1. Check that axis respond from 0 to 100% in MFG Configurator...if not then FOLLOW OTHER FAQ and calibrate axis inside MFG Configurator...this must be addressed first !

2. Check how axis respond in windows control panel/game controllers or better so in DIVIEW software. If they dont respond OK then RESET WINDOWS CALIBRATION TO DEFAULTS !!!

3. Check inside your game/ simulator...By now if steps 1 and 2 are fine you are 100% sure that your simulator recieve 100% good signal on axis and that, if it is not OK, cause of your issue is inside SIMULATOR ITSELF. There are too many simulators out there and therefore it is beyond the scope of our support . We can only provide most common general guidelines :

  • check that axis mappings are OK and that some other perhapial is not also bind to axis used by MFG crosswind
  • some simulators require brakes to be "inverted" in axis settings
  • check and adjust DEADZONE and SENSITIVITY settings on axis
  • some simulators can have specific plane axis assignments. Therefore conduct your tests on basic airplane in the sim e.g. C172 !
  • 3rd party addons to your sim like FSUIPC can also tamper axis settings. Try to disable those addons to determine if they are causing issues or not.
  • lastly , google about similar issues for that specific simulator. Sometimes controllers settings inside game might get corrupt. Check that too and google how to reset.

Squeek sound when brake axis pressed

Brake springs are torsion ones and they do squeek when pressed due to friction in it.

We oil them in factory in order to reduce friction, and therefore provide quiet operation. However, over time, they get dry again and need a bit of oil to get silent again.

You can use teflon spray or any oil, even kitchen cooking oil will do fine. Just pour a little oil onto the brake axis spring and work out brake axis few times, then wipe out excess oil on it.

I updated firmware and pedals keep restarting ( plug/unplugg sound all the time)

You loaded wrong firmware for your pedals version ! Electronics for V1 and V2 are different and have safety feature built in to protect electronics from such event. To determine which version of the pedals you have take a look at the following picture

However, no reason to panic. You can revive your pedals with correct firmware. All you have to do is open Mikrobootloader application directly from software package/firmware upgrade... and click connect untill you see pedals connected. Then proceed to upgrade firmware ( with correct file, you have firmware changelog and explanation in software package).
V4.xx firmware is for V1 pedals
V5.xx is for V2 pedals
V7.xx is for universal joystick firmware, all settings unlocked. We don't provide support for this firmware and it is intended only for advanced users and cockpit builders !

Microsoft Flight Simulator 2020 - set up MFG Crosswind

Read our blog article blog article

Credit Card processor (WS Pay) refuse to accept my valid Credit card

Despite having a valid card with funds available customers can still experience payment issues due to following reasons :
1.Our card processor temporary not working - try later

2. PSD2 Compliance of your Card issuing Bank. Since 2021 new regulation in EU made it mandatory that, beside entering credit card info, payment must be validated by something you are ( biometric fingerprint) or you have (net banking phone app or similar). After entering credit card info and processing payment this means that you should see a pop up window from your bank asking you additional confirmation of some sort

3.Limits on your card. Your bank can impose limits that you can lift trough your banking app or by calling your Bank. It can be that card is disabled or limited to certain ammount for internet purchases altogether or international purchases only...

4. Unsupported Card ... we support VISA, Maestro, Mastercard & Diners only

For security reasons we decided to use outside card processing company (WSPay/Monri). Due to that fact we dont have insights in your card info or reason for failure in payment processing. We only see that you tried to pay and if it was sucess or not.