Jump to content

XPJavelin

Members
  • Posts

    165
  • Joined

  • Last visited

  • Days Won

    15

Posts posted by XPJavelin

  1. I have uploaded the stable version 3.15 !

    I had time to test it tonight, find & repair some bugs, both severe and minors.

    I am confident I have reached a stable state (without severe bug) with nice features now. Therefore, from now on, I will reduce the updates rate ! From version 1 to version 3, I have implemented various ideas thanks to feedback from users (Jean Joubert , Carl) . With this fully operational version 3.15, it's time to freeze the features1.

    Hope you'll like it.

    1Of course, if any user finds a bug, I can certainly publish code revisions as I am fully open to comments.

    • Like 1
  2. I have uploaded the version 3.1 !

    I had time to test it tonight, find & repair some bugs, both severe and minors.

    I am confident I have reached a stable state (without severe bug) with nice features now. Therefore, from now on, I will reduce the updates rate ! From version 1 to version 3, I have implemented various idea from users. With this fully operational version 3.1, it's time to freeze the features1.

    1Of course, if any user finds a bug, I can certainly publish code revisions as I am fully open to comments.

  3. I wanted to trigger the various procedures with logical actions. Just pursue your actions of captain and pilot flying exactly as described in the FCOM.. :-) that should trigger the first officer ! 

    Or check the documentation. :)

    Also during last week end, the download has been corrected and updated to version 3. I suggest you do a full download again for v3.0. (I might upload version 3.1 soon with bug fixes  as I have more tests to do, and then you will only have to download the small lua script update) . 

     

    Thank you for your interest

    Speedy Copilot_3.pdf

  4. During last week end, the download has been corrected and updated to version 3. I suggest you do a full download again for v3.0. (I might upload version 3.1 soon with bug fixes  as I have more tests to do, and then you will only have to download the small lua script update) . 

    Options2.png.9bb179a5c15fd79a0620243f7aa7a84c.png

    Now it is possible to set copilot options like flaps settings for landing. 

    It is now possible to set them in the xplane menu. 

    Also, we have now slowed down the copilot for various procedures at some steps, using os.clock without totally removing simplicity in the mean time... :-) 

    Change log
    * v 3 : Copilot works in a more realistic way, with delays between actions.
    * v 3 : Options are now changed in X-Plane menu → Fly with Lua entry, instead of cockpit knobs.
    * v 3 : New option : user can deactivate flaps and gear by F/O.

    Speedy Copilot_3.pdf

  5. I am looking for something simple in my code.

    It was very convenient to read the FCOM and just translate in a few command lines, in a very straighforward way. I am not sure I am ready to sacrifice simplicity for human delay of actions.

    12 hours ago, jfjoubert said:

    if os.clock() > r_trigger_start_time +1 then if w_acft_flap ~= 0.5 then w_acft_flap = 0.5 end end

    I like that way of doing however.

    I will think about it.

    In the mean time, I was thinking of implementing a GUI menu to set options (F30 of F40, with or without APU...)

  6. thanks @jfjoubert,I will investigate your work, in the mean time, I was working on a revision of my script to include after landing flow with and without APU.

    I also added altitude constraint for flaps retraction, compatible with the go around triggers,  and runway Entry procedure is triggered by left inboard landing light instead of left outboard.

    Both as suggested by @blocks_off

  7. 1 hour ago, jfjoubert said:

    The problem with the above code is that you cannot have it in a function which is only executed once... you will never get to most of the steps.

    The current code has a conditional check for PREFLIGHT to see that preflightproc_trigger == 0 and beforestartproc_trigger == 0 and OXYTEST == 1

    Now this means that the actual code inside the function will only execute once. On the second pass all the above variables will not meet the condition again. So you will never get to os.clock() > r_trigger_start_time + 4 and further.

    So one possible solution is to change the conditional check to make sure that the code inside the function is repeated until all steps have been completed. This is what is adding to the clutter because now you have to make sure that you don't repeat a previously executed step and and that all steps are still done in the right order.

    Anyhow, I will upload my lua file (once done) with my modified code for the PREFLIGHT procedure and you guys can then have a look to see if it's not too much clutter in the code.

     

    Mmm :huh: Well said.

  8. 6 hours ago, jfjoubert said:

    I am still trying to see if I can optimise my code (clutter wise and not speed wise).

    I have absolutely no lags or stutters whatsoever. I will upload as soon as I feel it is worthy of sharing.

     

    So we have a winner here :)

  9. Hi

    Quote

    PS: I think you should also rename your script to "Not so speedy Copilot" once the random delays have been added.

    ahah !;D ;)

    I like the randomness idea too.

    I found a way to pausing a LUA script but it was pausing the whole simulator (simulator freeze, waiting for the Lua  with os.clock function to be finished) , therefore, not interesting at all. We cannot pause the whole aircraft while flying,it would looks like a giant stutter !

    Quote

    os.clock()

    When you use this function, are your sure,that you don't produce that giant stutter ? (I rejected that method).

    My attempt used a function calling sleep(1) for a pause of 1second :

    function sleep(n)
    
     local t = os.clock()
    
     while os.clock() - t <= n do
    
      -- nothing
    
    end
    
    end
    
    -- function sleep is dissused because it pauses the whole simulator !

    I have investigated the Internet and found the function pause was not available in Lua (except maybe with the last version of it).

    Quote

    It does however clutter the code

    Not sure it should clutter the code extremely : if you write the code into a function and call it - like sleep(1) - , it is a one-liner !

    If you find an elegant solution, you are very welcome to share it here.

    (And just as a reminder the current version is still 2.15, change log attached.)

    Speedy Copilot_2.pdf

  10. 2 hours ago, SkyFly said:

    after landing procedure trigger

    The after landing trigger was SPOILERS DOWN and, per FCOM, I prefer the F/O to handle the strobe switch on his side. However, it is perfectly understandable that you want to change your triggers to your liking and your own logic. You are very welcome to do that.

    2 hours ago, SkyFly said:

    I´d change the takoff items trigger to one of the inboard landing lights

    Nice idea !

    2 hours ago, SkyFly said:

    engine start switches and FLT/GRD switch doesn´t work for me

    With Speedy Copilot 2.15, engine start switches are manually activated by you, for the start procedure. Then ,during after start flows (and in approach,later), tjeF/O switches them to CONTINUOUS. I just tested that,and it worked perfectly on my computer. Did you erase the previous versions of the script before copying the last version ? Also, close and restart X-Plane for and after the installation to erase any global variable values.

    2 hours ago, SkyFly said:

    for flap retraction i simply added:

    if speed >= 140 and radioaltitude >= 1000 and step == 1 then

    I did not change the trigger in version 2.15 following your suggestion, because I made several tests with the current state of triggers for the after takeoff flow to ensure they are robust as is. The triggers are sensitive, because it has to work both for take off and go around. I remember fine tuning those takeoff triggers and it is not clear to me (without doing a series of tests) if the after takeoff sequence would keep safe and operationnal with your modification, but I hope so. So I reserve this modification for later so far. In the mean time, you are very welcome to modify the script on your computer of course.

     

    2 hours ago, SkyFly said:

    I have so many ideas for this script : P  I can write them down and send them to you if you like : )

    I welcome your ideas and suggestions.

    Thank you for your interest. :)

    • Like 1
  11. 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 !

    • Like 1
  12. 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...
     

    Quote

    I´wonder if it would be possible to link takeoff and landing config to the FMC data.

     

    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

    • Like 1
  13. 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...

     

    • Like 1
  14. 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

    Speedy737_4-6.thumb.jpg.b1ea6da18500640abaa36cdae0144b29.jpg

     

    Speedy737_4.jpg

    Speedy737_4-1.jpg

    Speedy737_4-2.jpg

    Speedy737_4-3.jpg

    Speedy737_4-4.jpg

    Speedy737_4-5.jpg

    Speedy737_4-7.thumb.jpg.659391adebb14b3509150440a3bbc95e.jpg

    Speedy Copilot series

    Speedy Copilot for IXEG 737 Classic

    Speedy Copilot 320

    Speedy Copilot Twinjet


     

  15. 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

     

     

    • Like 1
  16. 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 &nbsp;¡ 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

    • Like 1
  17. 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.

×
×
  • Create New...