pots

I think that mini-tutorial is included with aircraft and after that are different YouTube channels and docs from smartcockpit.com (about Challenger 605 but good enough for this type also). I have understood that the whole documentation set for Challenger 650 is like 10 000+ pages and manufacturer likes to keep its eye it. So full tutorial would be like 1000+ pages and hard to use. Professional pilots have ground school where they study the aircraft for two weeks full-time, it is hard to have such commitment from flight simmer. So it is easier to learn aircraft step by step (starting with mini-tutorial).

Thanks a lot, seems interesting system!

Hi There is nice SUPP GND WING ANTI-ICE test in after start checklist. But then I started to think how does this system work? There is not much information about 650 pneumatics available, from Smartcockpit website good docs about Challenger 605 can be obtained. But 605 does not seems to have this panel. I tried to play with these switches and watched bleed simulation panel at the same time and found no direct connection. Just curios - for which purpose this this system is there and how it works?

I have been using X-Camera and it somehow is in conflict with Challenger. After disabling it from Plugins menu the Num keys for saved views are working fine.

Yes - seems that the issue was deicing. Loaded the state, reached on takeoff only to 80 kts, then stopped and ordered the deicing truck. After that aircraft accelerated nicely to v1 and further. Seems that during initial setup I tried once X-Plane real-world weather and aircraft managed collect enough invisible ice.

Yes - both problematic states were saved with aircraft on the ground, ready to takeoff. Good to know that I am not only one in world with this issue. Checked the X-Plane setup and seems that states are saved as state.bin files in X-Plane 11\Output\CL650\airframes\ folder. Files itself are binary. so it is hard to compare them.

Selected another airport and loaded saved state of Challenger, still similar problem, max velocity 90 kts. Then I created new aircraft from Airframe Manager in third airport and started everything from cold & dark and everything was working, managed to finally make planned short flight. So maybe the very first aircraft state was corrupted?

Thanks for information! Tested the controllers, no additional brakes axis were found. Put X-Plane brake data and frame rate output to screen, nothing suspicious. Maybe the state file of Airframe Manager got somehow corrupted during the updates and frequent changes? Will try to start from cold & dark and see what then happens...

Not a problem, today the maximum stablized speed seemed to be 71 kts:

Hi After some video watching, reading and checklist work managed to set up Challenger for short hop (~100 nm) and saved the state with Airfame Manager. Now I am finally trying to use this state for takeoff but for some reason the aircraft accelerates until 70 knots and nothing more, unable to reach V1 and futher, just keeps driving at runway. Now scratching head, conditions following: Weather X-Plane ISA (+15 °C, dry, no wind), total weight 13756 kg (according to X-Plane itself), FMS TO thrust limit 90.3, ATS display showing N1 TO, engines providing 90,3, parking brake off, flight spoilers retracted, left engine thrust 34.69 kN, right engine 34,9 kN (from Engine State Study menu), T/O CONFIG OK message on MFD, MFA modes |TO| |TO|, no failures in Failure Manager, X-Plane 11.52r2 running ~35 fps. Would it be better to create new state from cold & dark or am I missing some setting? Pots

Isnt there abnormal and emergency docs included in Documentation folder of aircraft? On the moment I could not check myself but I think they were there...

Maybe the manual would be too voluminous? For example Aerowinx PSX (Boeing 747-400) operations manual is 611 pages, 100 page of it is simulator handling and the rest about aircraft. Challenger 605 docs from SmartCockpit are 630 pages it total. I understood that learning this aircraft in real life training organisation takes few weeks of full working days. So for simulation the best way of learning seems to be from step to step (with different videos, SmartCockpit docs etc).

Like that? FI -flight idle LES - Leading Edge Simulation ?

Stupid question - how to open the cargo door in v 1.6.5? According to manual there should be some clickspots on door, but I have not found them. Clicked on door and around it for few minutes, nothing. Somehow I remember from some release notes of 1.6.* version that cargo door was not supposed to work and would be corrected in version 2.0? Or is it connected with selected livery? Not the most important feature of aircraft but still interesting.

After some testing the issue seems to be with only right side EFIS DRIVE XFR switch. On left side same switch moves nicely between three positions. As the feature itself is not modelled then it just small observation.

Thanks for information, always interesting to know such small details.

Yes - the main problem seemed to be somehow broken switch manipulator. It could be moved only once in one direction and thats all, Gizmo must be rebooted for moving switch back to central position.

Good to hear. I took short look of supposed A340A manual on a well-known text sharing site. In the beginning it looked like A340A AFM but after some pages it turned out to be A340B one, so some kind of strange mix. Thought that better spend time (and money) with something more authentic.

Testing here fresh 1.6.3 version on X-Plane 11.52r1. I had nerve to move switch DRIVE XFR in EFIS section of overhead. According to Saab 340B AOM this DRIVE XFR/NORM/XSIDE DATA switch is meant for switching DPU (Display Processor Unit) in case of failure. Everything is fine but switch animation seems to be broken somehow - switch can be moved only from NORM to DRIVE XFR and thats all - it could not be moved back to NORM or from NORM to XSIDE DATA. After rebooting Gizmo everything is good again. Am I only one experiencing this? Maybe not important switch (there are not many failures of DPU in sim) but still interesting with its one-way working.

Thanks for reply! Saab 340A AOM seems to be very rare but somehow I found Saab 340B AOM. According to it emergency power supply unit contains a 24 V 5 A·H lead-acid battery and battery heater (to warm the battery for best efficiency). Just curious - is similar solution in 340A?

This aircraft is great! It is not big nor very modern, it does not have complicated systems but it greates passion! This forum is filled with observations, ideas, suggestions, bug reports, busy life is going on. Was Saab released on year 2013, so almost 8 years ago? But it still creates emotions, so well done!

Due to version 1.6.2 release I started to reading again Saab 340A Systems Operation Manual. According to electrical system description on page 55 and schematics on page 65 there seems to be hidden emergency battery located somewhere. So it has no switch (always ON), no voltage display and it status is shown only by "EMER PWR" warning light?

Seems to be some issue with version 1.6. I managed to start engine 1, then manual start of engine 2 did not succeed. Then thought that auto-start should work fine, engine 1 is now working but auto-start itself is stuck for 5 minutes now.

Working fine here with v1.1! Thank you.

Just made observation about G5 in X-Plane 11.41. When pausing the simulation the G5 starts to increment the IAS value itself until the maximum (360 kts). When unpausing the correct value is swiftly restored. Maybe it not bug but just interesting behaviour. Pots