frumpy

The dataref list ist not complete for all functions, but I think some will already work. It's on the list for later, so I guess we'll have to wait until the dust settles.

Using the matrix method you can connect 200+ pins per board: http://svglobe.com/arduino/input_kmx.html

Good page on the MCP, I did not know this one. The 7 segment displays can be driven by extra chips, or directly via the Atmel - however this would take a lot of time and pins. Thats more of a project if you have the time... As for the buttons - you're right, they are sold out. :-(

https://www.facebook.com/shitpilotssay/photos/a.254651147939619.60565.248576525213748/1071051796299546/?type=3

Hi Nils, are this the only datarefs? I'm not sure if I can drive the buttons and LEDs with the "_toggle" datarefs, but yes, it should work. Lack of time really, but I'll definitly check them out. 1achmed1, yes, handpainted with a white ink pen and a few layers of transparent color. The plate is 3mm acrylic, the holes are made with a Dremel and the buttons glued into it. Now if you have access to a 3D printer... I think next step could be hacking those: http://www.banggood.com/5Pcs-Yellow-LED-0_28-Inch-2_6V-30V-Mini-Digital-Voltmeter-Voltage-Tester-Meter-p-980045.html

Atmega 2560 board from China, about 50 pins. You guys can check Vlad's site for further details, very extensive site (incl. the plugin). Switches I have to check - got them from conrad.de for 3€ a piece.

From first sight: You seem to be a bit fast, but maybe you are high on weight. Also you are a bit high, the VASI are all white. Try to be at 50 ft at the threshold and look outside! During the final moments your scan should be "airspeed-touchdown markers". Your flare is a bit hard, flare slower. I try to fly the plane level at 2-5 ft, the decreasing airspeed will do the rest. And don't get fixed on reaching 5° pitch, raise the nose by about 2.5-3° depending on your pitch during approach. There is also a description on how to do it in the handbooks. And don't worry if you don't do a soft landing. Most important is, that it's in the touchdown zone, if you can't make it then do a go-around and try again! Last, but not least... do a dual-channel autopilot approach and watch how the AP does it. :-)

What tilt? The changing tilt of the knob? What datarefs are you using?

The Arduino I use has a native plugin, USB and more pins than the PRJC.

Hi guys, I made a simple MCP with an ATMEGA 2560 compatible board which is WIP. All buttons and LEDs work, next step is getting the right datarefs (which are currently not available, but I believe it's just a matter of time) and putting them in the code. I used the software interface from Vlad http://arduino.svglobe.com/ Even though this is low tech compared to other projects, it might inspire some people to do the same. No rocket science involved!

Yes, I've been to larger sims and programmed encoders myself with X-Plane. The thing is, you need to have a coarse and fine control with the encoder. Coarse moves 10kts/1000ft/10°, fine 1kts/100ft/1°. In order to distinguish between coarse and fine, you need to know the interval timing between signals when turning fast and slow. Turn as slow as you can while thinking "this should be fast" and as fast as you can thinking "this should be slow" and take the timing between the encoder clicks. To make a long story short, 30ms between intervalls distinguishes pretty good on encoders that I have seen. I'm not a programmer, but this algorithm worked for me with a Teensy board: flightsim.update (); if encoder moved timer_old=timer1; // save old value of timer timer1 = atmeltimer; // get the time from the chip time_between= timer1-timer_old; // calculate the time elapsed if time_between <30ms then {move encoder 4 steps}; if time_between >30 ms then {move encoder 1 step}; More can be found here: https://simelectronics.wordpress.com/2013/09/15/encoders-coarse-and-fine-control/

I believe in the scroll-wheel too. Setting up the MCP with the scrollwheel feels pretty natural. Zooming could be done with right click+scrollwheel, just like the right click moves the view around.

Vitabutch, thats lovely!

Replicating the EHSI with Air Manager won't be possible. However, I've got the strong hope that all datarefs will be published. E.g. if there is a dataref for each AP mode and speeds, the EADI could be fully replicated, along with all other instruments.

If you guys are into external instruments, you should check out https://www.siminnovations.com/software/air-manager/instruments First you draw the bitmaps and then overlay them using LUA. Can be well adapted to your needs, just takes some time and dedication. I think this can be utilized to draw very clean&usefull 2D panels.

Good question! I checked the handbook: "Immediate initiation of reverse thrust at main gear touchdown and full reverse thrust will allow the autobrake system to reduce brake pressure to the minimum level, thus minimizing brake and tire wear and keep brake temperatures in the normal range. The importance of establishing the desired reverse thrust level (approximately 80% N1) as soon as possible after touchdown to minimize brake temperatures and tire and brake wear and to reduce stopping distance on very slippery runways cannot be overemphasized. Since the autobrake system senses deceleration and modulates brake pressure accordingly, the proper application of reverse thrust will result in reduced braking for a large portion of the landing roll." In the 747 the brake pressure is a function of groundspeed and measured by the IRS and switching off the IRS disables the autobrake. Perhaps the same in 737, I don't know.

You will have to stick the key in the GPU fan while aligning the IRS.

If the thread is closed like you voted for, there is no room for discussion.

No need to. A simple mugshot will do!

I share your horror! Got mine in 2008 too and haven't flown since then. Uh well, one day...!

Google translator, olé! https://translate.google.de/translate?sl=auto&tl=en&js=y&prev=_t&hl=de&ie=UTF-8&u=http%3A%2F%2Fwww.tu.no%2Fartikler%2Fderfor-har-wideroe-flyene-sebra-propeller%2F275876&edit-text=&act=url

Good thread! L-39 in DCS. I knew I was low, still I wanted to push the limits and do a downwards half loop. I love them outside-in russian artificial horizons. No matter what position in space I have, getting the wings level for maximum lift is a no-brainer. Well, everything went fine, but altitude...

Wow! :-o

To me as a desktop driver, it's Airbus' design philosophy in general. While they were clever at some points, they tried to be very consequent in the fly-by-wire design and did some things that give some pilots headaches. I am thinking about the sidestick which isn't interconnected, the non-motorized thrustlevers that do not give you a valid feedback on thrust setting and other stuff (just think about the LH A320 that did a 4000ft dive because of frozen sensors - the pilots had to turn off a few systems to regain control) and other stuff. Proper reaction to errors which were not described in the manuals takes longer, as systems are more complex and more interconnected. Much more A320 pilots say they do not understand all systems/functions than any 737 (including NG)-pilot would do.

Hi guys, I've been to Riga Airport and saw a few classic 737s, some even with eyebrows! Not the best weather for shooting, but I thought you still might enjoy.