Jump to content

Recommended Posts

Posted (edited)

current OB, do by-the-book startup, after CADC master reset couple seconds later "CADC" fault light is on, cannot manually sweep, only by lever.

Do I break the jet or bug?

EDIT: happens occasionally, not all the time.

Edited by bumblebomb
Posted

Nope. I got manual sweep fwd/aft on the front 4way on the WH throttle, that's it.

One thing I forgot: sporadically. Not always. Can't say if always on the same server, but after a re-spawn on the same server last time it worked a charm.

 

Posted

Reason I'm asking about the Emergency Wing Sweep handle is because the only condition that I can repeatedly cause the warning is a minor "bump" of the handle with the guard up right as I'm closing it, then tagging the Master Reset switch.  The minor out of sync of the sweep program versus the manual entry causes the system to properly show a fault.  Because of the way the implementation is right now (only restricting the axis when the cover is down, rather than requiring it per the actual hardware to have the handle lifted to engage the sweep control via the lever), it's really easy to catch with that little bump while in the process of closing and resetting- and it only takes one "step" (ie, one small bounce on the control) to do it.

To eliminate something being wrong with the nub 4-way, can you try putting the manual sweep controls on the mic 4-way switch instead, and then remap whatever you have on the mic switches to the nub on a temporary basis, to see if the "return" action of the nub when you let go is triggering the opposite "aft" control and stepping the sweep out of sync?

Posted

Let me see if I got this right: you suspect: when I release the 4way it overshoots into the opposite position, causing the in-game lever to come back a tiny bit? 

Does that matter when the lid is closed in-game and you issue CADC master reset?

I'll test your theory, though.

  • 3 weeks later...
Posted

Have you had any more issues with this? I've been smacking around various control configurations and such trying to make it occur again in testing builds during each startup, and still cannot cause the out-of-sync situation to occur (except from the method listed above).  

  • Recently Browsing   0 members

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