Jump to content

MFG Crosswinds not detected in CH-47F


Go to solution Solved by flyingscotsman,

Recommended Posts

Posted

I have found in the past that some modules recognise the brake pedals, some don't

They ALL recognise the Rudder axis

So, I have A-10C ii, & AH-64D, brake pedals are recongnised in the axis command

But nothing happens in the CH-47F. 

Brakes working with other sims, i.e. PMDG 777 etc in MSFS2020

Any ideas?

Thanks in advance

Posted

And mine

  • Like 1

Windows 11 Home ¦ Z790 AORUS Elite AX motherboard ¦ i7-13700K ¦ 64GB Corsair Vengeance DDR5 memory @ 5600MHz ¦ Samsung 990 Pro 1TB SSD for OS, Samsung 980 Pro 2TB SSD for DCS ¦ MSI GeForce RTX 4090 Gaming X Trio 24GB ¦ Virpil WarBRD base with VFX grip, Thrustmaster A10c and F/A-18 grips ¦ VKB Gunfighter Mk4 and MCG Pro ¦ Thrustmaster Warthog Throttle ¦ VKB STECS Throttle ¦ Virpil TCS rotor base with Shark and AH-64D  grips ¦ MFG Crosswinds ¦ Total Controls Multi-Function Button Box ¦ Pimax Crystal

Posted (edited)

I think you might have had the same problem I did a while ago. On my MFGs I changed the angle of the pedals and did not do one side up tight enough. Couldn't feel a difference but that side had intermittent issues. 

I fixed it by resetting the position. Doing them up properly and the recalibrate all axis in the software. Never had an issue since. 

Currently my MFGs are flawless in all modules and work in the CH47 too. 

Edited by Hoirtel
  • Like 1
Posted

Hello All,

               Thanks for replying, I've not touched my pedals since getting them in about 2018. I can see the values look odd, X is 4500 and Y is 7600 (say) but they work on some DCS aircraft and not others. Have the same problem with MSFS, seems wierd. I'll get them out from under the sim and check the tightness of everything and re-calibrate as you advised.

That'll not be until later today. Thank you

 

  • Solution
Posted

Horitel, You were the closest, I found another post on a differnet forum about MFG's and they suggested, "Unplug the brake cables and hoover out any dust."

worth a Try. So at this point, neither pedal is seen in the CH-47F, but both working on the AH-64 and others....grrrr.

I also removed all MODS, No change

Did a DCS Repair and Cleanup, no change

Unplugged/replugged the MFG's and did a manual calibration. Noticed that the RAW numbers fluctuated even when no feet on pedals, so something is stopping full equilibrium.

Unplugged brake cables, they pull out by hand. Hoovered the compartment and firmly inserted the connecters.

Automatic calibration, still had some numbers flickering, but MUCH less.

Manual Calibration, set them to ZERO and the LEFT brake was working in the CH-47F, so bind that to both brakes....SORTED

Thanks to all who responded.

Milan, to his credit now has cables that can be replaced, without soldering, So when that other one packs in, I'll be sending for it. But this solution works for me

Happy flying everyone

  • Like 2
Posted (edited)
On 8/11/2024 at 6:49 PM, flyingscotsman said:

Horitel, You were the closest, I found another post on a differnet forum about MFG's and they suggested, "Unplug the brake cables and hoover out any dust."

worth a Try. So at this point, neither pedal is seen in the CH-47F, but both working on the AH-64 and others....grrrr.

I also removed all MODS, No change

Did a DCS Repair and Cleanup, no change

Unplugged/replugged the MFG's and did a manual calibration. Noticed that the RAW numbers fluctuated even when no feet on pedals, so something is stopping full equilibrium.

Unplugged brake cables, they pull out by hand. Hoovered the compartment and firmly inserted the connecters.

Automatic calibration, still had some numbers flickering, but MUCH less.

Manual Calibration, set them to ZERO and the LEFT brake was working in the CH-47F, so bind that to both brakes....SORTED

Thanks to all who responded.

Milan, to his credit now has cables that can be replaced, without soldering, So when that other one packs in, I'll be sending for it. But this solution works for me

Happy flying everyone

Glad you got it sorted. On a similar but unrelated note I have also experienced modules responding differently to peripherals. I had a button box that worked in Apache but not/partially in many other modules. Probably just have differences in the way they are coded.

I fixed the box with a firmware update. 

Edited by Hoirtel
  • Like 1
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...