XPJavelin

The version 2.15 is now available on x-pilot.com and on my website. Per user request, Flaps 30 can be selected instead of Flaps 40 for landing. How to do that is documented in the PDF documentation. The version 2.15 has been tested on a typical flight profile with CRZ above FL100 and no sign of malfunctions was spotted throughout the different phases of flight but feel free to report any here. Happy flights !

I din't want the FO to arm speed brake because I am focussing on Pilot Monitoring on right hand seat. In the FCOM, landing procedure (NP 21.49), it is the Pilot Flying who "Set the speed brake lever to ARM"... I found it great the Captain PM to be in charge of it so I didn't try to add it.. Anyway, you can decide differently with your own SOP... That would be great, at the moment, I don't now how to store a data displayed in the CDU into a Lua variable. It is not an IXEG dataref... Instead I would be inclined to find a trigger that allow FLAPS 40 or FLAPS 30. The best way is to tell the copilot with a workaround like pushing a specific button below 6000 feet, he understands it will be one of the configurations instead of the other and then does : if planned_flaps == 40 then FLAPS = 1 end --flaps 40* if planned_flaps == 30 then FLAPS = 0.xx end --flaps 30* I have updated it to allow Flaps 30 on landing, it is ready and will be uploaded in v2.1 I have updated the documentation. But still have to test the new version 2.1 before uploading. Speedy Copilot_2.pdf

Hi,yes the chronometer is left apart in my version 2.0. But the engine start swithes is solved, and the flap retraction altitude is a good idea... Did you use the version 2.0 as a basis? Because it is greatly improved in regard to previous versions 1.x... In theversion 2, my the FO handles the GRD/FLT switch without problem. The solution is to use the Lua function "set" instead of the "dataref" function (see fly_with_Lua documentation). For flaps 30, I didn't do that at that time.It is very easy to change FLAPS 40 for FLAPS 30,but it requires more code to create a situation for FLAPS 30 OR FLAPS 40. I am glad you like my work ! And try to improve it !! Just,be sure your work is based on 2.0...

Speedy Copilot for IXEG 737 Classic View File Description Speedy Copilot for IXEG 737 makes for you the steps normally done by the first officer and pilot monitoring, when you are pilot flying and captain of a Boeing 737. This plugin is intended for the IXEG 737 (version 1.21). It was tested and works with X-plane 11.26. Please install at least FLW 2.7.11 NG. The Flight Crew Operating Manual makes a clear separation between actions from left and right seats. So we'd like to have the right hand actions (first officer and pilot monitoring) done for us in reaction to the phase of flight and to left seat actions (captain and pilot flying). Remember that the Copilot is not calling the checklist. The copilot is doing the procedure. We suggest that you run on your own the checklist at the end of each procedure. Additional features You can listen to the cabin PA and boarding music if PA receiver is activated on the left hand side Radio Management Panel. Cabin crew is handled by Speedy Copilot without pilot intervention according to phase of flight. In addition, the first officer pressure altimeter setting is linked to the captain's one. If you change the barometric settings, the F/O will synchronize his one. Context Several virtual copilot options might have existed previously but they seamed challenging to install and maintain, or required payware software. The intent in this Speedy Copilot for IXEG 737 project was to provide a very simple solution yet realistic and efficient. We made a transcript from the FCOM into a Lua script for the IXEG 737. The first version of Speedy Copilot for IXEG 737 was released in June 2018. In August 2018, we published Speedy Copilot 320 for FF/STS A320 Ultimate. Based on the success of Speedy Copilot 320, many users reports and five months of updates and evolution, we transferred-back some exciting features to Speedy Copilot for IXEG 737, which led to version 4. Installation See PDF manual. Forum You can discuss this file in the IXEG forum if you wish : http://forums.x-pilot.com/forums/topic/14433-speedy-copilot/ Screenshots Speedy Copilot series Speedy Copilot for IXEG 737 Classic Speedy Copilot 320 Speedy Copilot Twinjet Submitter XPJavelin Submitted 06/17/2018 Category Plugins and Utilities  

Version 2.0 from 2018-06-16 Change log * v 2.0 : Engine start switches CONTINUOUS (after start and before landing) is now handled by the copilot, with the use of a different Lua function not conflicting with IXEG software * v 2.0 : Autobrake switch is now fully handled by the copilot, with the use of a different Lua function not conflicting with IXEG software * v 2.0 : Press. FLT - GRD switch is now handled by the F/O. * v 2.0 : Guarded switches (flt_control_A_guard, flt_control_B_guard, spoiler_A_guard, spoiler_B_guard, alt_flaps_guard, att_pwr_guard, stby_pwr_guard and bus_xfr_guard) now checked guarded by the F/O during preflight. * v 2.0 : The F/O sets his CDU to LEGS page as part of the before start flow, per FCOM. Speedy Copilot_2.pdf

Hi, I know a lot of simmers use Simbrief or PFPX butI don't. I do my route preparation on my own website for free. I like to do it this way. I did update today the OFP generated for the Boeing 737 (both classic and NG). I have kept at the moment the legacy OFP for classics and NG, but added the Boeing B737_CL_and_NG OFP. When you export in PDF or print the OFP selection from Open Office Calc, you have the result attached below (ofp.pdf). If you wish, you can download the ofp.ots (Open Document Template, made with Open Office) below, or generate it dynamically using my web site YART  ¡ Yet Another Route Tool !© in Advanced mode. The principle is to follow the worklow suggested in the first tab of the spreedsheat and then export the OFP located in the last tab of the Calc document. Click on the signature standing on the OFP to add the handwritten notes to the OFP. Best regards. ofp.pdf ofp.ots ofp-notes.pdf

Version 1.3 from 2018-06-12 2130z Change log * v 1.2 : Sound set totally reworked for more clarity, including PA annoucement (only with PA receiver tuned) and copilot. [Done at work when the boss was not noticing ] * v 1.2 : When you set an altimeter setting, you hear the pilot telling you that he synchronized his baroaltimeter shortly after yours with "altimeter updated" * v 1.2 : Engine start switches bug which crashed the aircraft is now repaired (However, at that time, you'll have to do it yourself, I'm sorry) * v 1.2 : Autobrake switch differently handled, code speaking. (However, at that time, you'll have to do it yourself, I'm sorry) * v 1.2 : Code tweaking * v 1.2 : Reworked the logic for FL100 - it is no more mandatory to fly above FL100 in cruize to trigger subsequent flows. It remains mandatory to perform all the steps and procedures from the FCOM in the right order. The copilot cannot skip procedures, otherwise next procedures wont be triggered. * v 1.3 : Repaired the logic to trigger approach mode (was broken in version 1.2) It was tested in XP 11.20 and IXEG Classic 1.21, Better Pushback and JAR GroundHandling.

Hi you should wait :). I am heading to my office for the day at the moment

Hi ! Thank you for your time. And your interest. Yes it is mandatory to perform all the steps. The copilot cannot skip procedures, otherwise next procedures wont be triggered. I had also the space shooting and deactivated the engine start switches from the copilot tasks because manipulating them had that bad side effect on engine start, nevertheless prestart procedures are done or not. . I did not uploaded the corrected script at that time but it's identified and fixed in the next version. I have also removed the sound of the copilot stretching his muscles when entering the chu abin in the next version (was not very happy with it) but kept intentionnaly the other environnemental sounds. I recognize it was a quick recording and some sounds should be improved. When you set an altimeter setting, you hear the pilot telling you that he synchronized his baroaltimeter. for sure the quick and dirty" sync baro" should be replaced by a more appropriate sentence.

Thank you very much of your interest. Of course I can listen to the comments and bug reports. I have made some minor bug removal,not uploaded to the server at this time. The main thing is I had trouble with some datarefs. I would have prefered sending custom commands, instead, sometimes, monitoring dataref in "writable" mode had some negative effects (the switch was not responding normally anymore, etc...). So far I have reached a state were I am happy with it, with the exception of engine start switches I has to remove from F/O responsability (e.g. moving them to readonly mode).... and some other switches less critical. I am doing currently the flight from the majestic scenery of Kerkira LGKR to LFMT, and it seems to be fine. Thank you again !

I have corrected a few bugs. For instance this critical one : dataref("ENG1STARTER", "ixeg/733/engine/eng1_start_act", "readonly") dataref("ENG2STARTER", "ixeg/733/engine/eng2_start_act", "readonly") is now,on my computer version, readonly instead of writable because it is suspected to cause troubles at engine start (actuator not being able to move to the OFF position automatically). Therefore, engine start switches are now in the responsability of the captain with speedy copilot. I will upload at a later date the correction. In the mean time, if you encounter problems at startup (false behavior of switch or aircraft crash), I suggest you do the correction above..

Hello captains ! This is the livrery I have done this morning. And I would like to share it with you greek pilot ! This livrery MINOAN AIRLINES is a fictionnal variant of the MINOAN LINES ferry-boat compagny founded in Crete, Greece. It is named after the famous palace of the antiquity at Knossos, in Crete, an Island where my family was involved for archeological studies and where I spent some of time. This is a tribute to them and to greek people ;-)

IXEG 737 Classic MINOAN AIRLINES 'Palace of Knossos' (fictionnal) View File MINOAN AIRLINES - a fictionnal livrery for the IXEG Classic MINOAN AIRLINES Minoan Lines is a greek ferry boat compagny which was created in Crete, Greece in 1972. With this livrery, we adapted the design of the maritime compagny and apply them to a fictionnal subsidiary in air transportation, namely « Minoan Airlines ». (We have no link with Grimaldi Group nor Minoan Lines. We changed « Minoan Lines » to « Minoan Airlines », a fictionnal title not representative of any real compagny). You can also find the same livrery for the flight factor A320 Ultimate : ff-a320-minoan-airlines-palace-of-kato-zakros-fictionnal/ Submitter XPJavelin Submitted 06/10/2018 Category IXEG 737 Classic Livery For http://www.x-aviation.com/catalog/product_info.php/take-command-ixeg-737-classic-p-122 X-Plane Version(s) X-Plane 10 & 11  

I have updated the script with vocal remarks made by the first officer and also the activation of the PA emitter when the PA button is triggered. It is in the process to be uploaded, expect it for 0600Z 2018-9-6.

Hello captains, I wanted to present you my Lua Script used as copilot in the 737. I wanted a very robust and simple solution, and so far the Lua script has proven to be reliable. While there is some limitations stated in the PDF manual I have written for you, it's a great help not to fly alone and have a very simple but efficient first officer ! All the best, and please let me speak about Speedy Copilot ! What it Speedy Copilot ? Speedy Copilot makes for you the steps normally done by the first officer and pilot monitoring, when you are pilot flying and captain of a Boeing 737. Speedy copilot is intended for the IXEG 737 (version 1.21 and above). It was tested and works with X-plane 11.20 and IXEG 1.21. It is not very realistic to do all the steps required in the procedures on your own. The Flight Crew Operating Manual makes a clear separation between actions from the left hand seat and the right hand seat. So we'd like to have the right hand actions (F/O, PM) done for us in reaction to the phase of flight and to left seat actions (CPT, PF). Several options exist to have a virtual copilot flying with you In X-Plane. But they might be technically complex, challenging to maintain, or require payware softwares. The intent was to provide a simple solution! We have made a transcript from the FCOM into a Lua script for the IXEG 737. We have made the transcription of the following procedures : Preflight procedure (triggered by the left hand side oxygen mask test) Before start (triggered by the beacon to ON) Before taxi (trigger by both engine generators to ON) Runway Entry procedure (including TCAS control, triggered by left outboard landing light) Take off run : gear and flaps retraction schedule (automatic trigger per rate and speed) Flight 100 and climbing items (automatic trigger per captain altitude) Flight 100 and descending items (automatic trigger per captain altitude) Approach, flaps extension schedule (automatic trigger per altitude and speed) Go around (reversion to Take Off procedure above) (automatic trigger at positive rate) After landing procedure (triggered by speedbrake down on ground) Apron entry (lights and doors) (triggered by runway turnoff lights OFF) Shutdown procedure until turn around state (beacon to OFF) The procedures are either manually triggered or automatically called. The Copilot is not calling the checklist. The copilot is doing the procedure. DOWNLOAD

I usually send command and read dataref to do things like : if pressurization selector is not on GRD position, put it to GRD selection. I retrieve the dataref throughSPAD.Next and send them via Voice Attack, that way I have the copilot doing it's flows per FCOM on its own. With the last updates (x-plane or ixeg 1.21), sending commands or reading some dataref makes X-plane crash. Thefirst actionsofcockpit preparation flows are usually fine (reads and execute stall test, flight recorder, airspeed warning test,checking fuel quantities) then at some point (reading window heater status and applying correction if required, but not exclusively at that point of the flow), X-plane crashes. Anyone else ?

still in 1.2. Just not to forgot, waiting for this for another update. ;-) Best regards

How does the F/O choose between Left and right Igniter ? And can we ask the FO to read the checklist on top of doing the procedural flows ? I don't see that in the video ? -> edited and created myself I also would have liked to have a "cycle flight director" command. -> edited and created myself

Hey, I am back, I will try this...

Hi, It has been said somewhere here that a dedicated freighter version might come.

Nice ! Please keep us aware of availability for the 737.

Et voilà, the third version of my guide is out (my current understanding of the systems and my current observations in the simulation) !

I am not convincced by the answer " but when you switch off the battery on the classic, everything goes off ". Let me revise here my previous statement that everyhing goes off, because a more thorough trial tells me that indeed, I keep some systems (STALL WARNING SYSTEM 1 fori nstance, and CAPT displays) even if those systems are clearly different than in my NG simulation. Then why would the CL FCOM says that DC and AC STANDBY BUS are not deenergised when a normal power source is still available? BAT SWITCH OFF : removes power from battery bus and switched hot battery bus when operating with normal power source available / removes power from battery bus, switched hot battery bus, DC STANDBY BUS, static invertor and AC STANDBY BUS when operating with normal power source available / BAT SWITCH ON : (guarded position) –> provides power to switched hot battery bus –> energizes relays to provide automatic switching of standby electrical system to battery power with loss of normal power [in flight for B737-300] In the mean time STDBY POWER SWITCH has to be put on BAT (on ground iand n the CL only because relays are not energized to provide automatic switching when BAT SWITCH is OFF). Also when I restore to ON the battery after having switch to OFF, I have to reconnect the GPU generator in the CL, and not in the NGX. I can conceptually agree that if the gen relays are battery feed (can't find source), loosing the battery will lead to a complete electricity loss as it has happened on real life [IN FLIGHT]. Because APU dies. But here I am on ground with GPU, so definitively something seems wrong here, in contrast to my other 737 simulation. I should not lost AC connection on ground from GPU in the IXEG simulation without touching the BUS PWR CONTROL UNIT switches. But I do. I agree and I see that ground power contactor without battery power cannot have effect (verified both in the NG and inthe classic). That does not mean that the GPU connection behind and already established should die. (Which is perfectly modeled in my NG simulaiton). So after much hours working on it, I am not conviced by how the GPU source and BUS PWR CONTROL UNIT are modeled in the IXEG or I need more explanations and sources (obviously would love to have an enginner manual, a pilot operating book seems not enough). Because it is my NG simulation that may be wrong. ;-)