Search the Community
Showing results for tags 'Data Collection'.
Found 1 result
I'm using Win 8.1 Pro x64, FSX w/Accel Pack, the PMDG 737-800NGX, a registered copy of FSUIPC 4.929, and the Saitek Pro Flight Yoke/Throttle quadrant properly set up in FSUIPC to use the Flaps Axis and calibrated accordingly. All axis settings inside the FSX control settings have been deleted. FSUIPC controls all yoke, throttle quadrant, and rudder pedal axis. We ran across a problem using our virtual airlines ACARS in that the ACARS was reporting that I was using Flaps 40 on takeoff when I actually was using Flaps 1. Just to see what I am sending out, I installed Monitor FSUIPC Data and took a look at the flaps data as I cycled through the flaps positions. Even though flaps movement and indicators in-game were perfectly normal, there were situations where FSUIPC jumped up to Flaps 40 and Flaps Handle Index 8 out of sequence. (There are 9 handle index positions on the 737NGX: 0 through 8). The most common flaps settings where the disconnect occurs are flaps 10 and flaps 30. So starting with flaps up, I will usually see a flaps handle index progression of 0, 1, 2, 3, 8, 5, 6, 8, 8. Other combinations have been encountered (including the "Flaps 40 when I'm at Flaps 1" indication), but the progression above is the most common. Keep in mind that throughout all of this, the flaps on the plane have been setting correctly and the cockpit indicators have ben positioning correctly using the Saitek throttle quadrant. It's only the information reported by FSUIPC that appears out of synch with what's actually happening. I can provide screen shots of what Monitor FSUIPC Data is reporting for each flaps position if you need them.