737 TQ - throttles mechanically stuck on Reverse

General
#1

I received the nice throttle assembly a few days ago. When I received it, the throttles moved freely. Yesterday I hooked the assembly to my PC and tried to run it with XP12 (an older version but also the newest version) and the ZIBO B737. I also downloaded the latest version of Bridge. At one time, there was a big clanking noise from the throttle assembly When trying flights from the ground, on a runway, the throttles are stuck in reverse mode. The throttles are mechanically locked on idle. The reverse levers move mechanically and XP12 correspondingly shows N1 moving from idle to some high-power value. The EICAS display shows REV in green letters but moving the reverse levers to idle does not get the system out of REV mode.

I tried starting a flight from a point ten miles away from the runway hoping that the system would get out of the reverse mode but during the approach the REV indication is still on, the throttle levers are still mechanically held on Idle but this time the reverse levers are unable to be moved (I suppose this is the way it should be in flight).

I tried getting out of the Reverse mode by interrupting power during operation but that did not help.

Even without power, the throttle levers are still mechanically locked on Idle.

Otherwise, the hardware looks and feels beautiful and the flaps, spoiler levers and switches are all working.

Is there something I am missing about getting the engines out of Reverse or is there a problem with the setup?

Thanks,

Guy

#2

Problem solved. When I saw the picture here on the forum I noticed that the reverser handles were pushed down much lower than I did. I was just afraid to push hard enough!
This throttle assembly is and works beautifully.
I develop software to analyze flight recordings and simulators help me understand the data better.
I must also warn others about another problem I experienced: after installing the latest bridge version, when I tried to execute it, Windows came back with a message saying that it could not access the file. The problem was caused by an anti-virus program.