Announcement

Collapse
No announcement yet.

eSignal crashes after EFSAT_SAMPLE.efs sends order to IB and will not come back up!

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Avery,

    The efs you have is the same strategy I renamed it after removing a bunch of comments, the page you are seeing the missing efs was the page loaded with the previously named efs so you have the code that was failing on my end.

    That's great news so it's not the efs and apparently something got corrupted on my end. I will follow the procedure in the link you posted.

    I have the latest version R14 installed, the procedure is about removing R12 which I do not have installed so I don't know how to proceed?

    thank you.
    Last edited by demarcog; 05-22-2020, 08:23 AM.
    Glen Demarco
    glendemarco@gmail.com

    Comment


    • #17
      Avery,

      Haven't seen a response to my last post on this last Friday.

      The link you included is a procedure to upgrade from R12 to R14 which I do not understand as I am already R14 as mentioned.

      The crash apparently has nothing to do with my EFS which I did provide as mentioned.

      The EFSAT_SAMPLE.efs that eSignal provided crashes immediately when I execute an order with EFSAT_SAMPLE.efs , so it's clearly nothing on my end.

      BTW whoever put a default order size in EFSAT_SAMPLE.efs of 100 should consider that if someone has a Commodity Futures symbol loaded up they will buy or sell 100 contracts. I'm aware of it but the next person may not be and 100 contracts on a futures contract with a $10 spread is a $2000 loss and that's the absolute minimum loss as a 100 contract market order in a thin market could push the price such that the loss could be many times that.

      Can you please provide some guidance on how to resolve this apparent bug in eSignal. I'm running the latest version of eSignal, TWS, EFSAT_SAMPLE.efs and Windows 10 and have no problems with dozens of other applications. Also no problem executing orders on IB's TWS as this version of TWS is stable.

      So it appears that this is a eSignal-IB interface bug which I need your help in resolving?


      Thank you
      Last edited by demarcog; Yesterday, 06:45 AM.
      Glen Demarco
      glendemarco@gmail.com

      Comment


      • #18
        Glen

        The link you included is a procedure to upgrade from R12 to R14 which I do not understand as I AM ALREADY RUNNING R14 as I mentioned several times.
        The article Avery directed you to is not "a procedure to upgrade from R12 to R14" as you state. It is the procedure to clean uninstall eSignal 12 which is the version of eSignal you are running. The numbering is related to the version i.e. 12 and not the sub-version (12.11, 12.12, etc). Perhaps you may want to read more attentively next time.

        The EFSAT_SAMPLE.efs that eSignal provided crashes immediately when I execute an order with EFSAT_SAMPLE.efs , so it's clearly nothing on my end.
        Actually it does look like it is something on your end because I tried EFSAT example with eSignal 12.14 (albeit not with your page – and do not intend to) and IB's latest TWS version and have no issues at all on two computers. Furthermore Avery has also told you he used your page with EFSAT example and latest IB TWS and he too had no issues
        As Avery suggested you should do a clean uninstall and reinstall

        BTW whoever put a default order size in EFSAT_SAMPLE.efs of 100 should consider that if someone has a Commodity Futures symbol loaded up they will buy or sell 100 contracts. I'm aware of it but the next person may not be and 100 contracts on a futures contract with a $10 spread is a $2000 loss in an out.
        As clearly stated in this sticky post at the top of this forum (and for that matter the name of this specific foum itself) , EFS Automated Trading is in BETA and one uses it at their own risk.
        Alex



        Originally posted by demarcog View Post
        Avery,

        Haven't seen a response to my last post on this last Friday.

        The link you included is a procedure to upgrade from R12 to R14 which I do not understand as I am already R14 as mentioned.

        The crash apparently has nothing to do with my EFS which I did provide as mentioned.

        The EFSAT_SAMPLE.efs that eSignal provided crashes immediately when I execute an order with EFSAT_SAMPLE.efs , so it's clearly nothing on my end.

        BTW whoever put a default order size in EFSAT_SAMPLE.efs of 100 should consider that if someone has a Commodity Futures symbol loaded up they will buy or sell 100 contracts. I'm aware of it but the next person may not be and 100 contracts on a futures contract with a $10 spread is a $2000 loss and that's the absolute minimum loss as a 100 contract market order in a thin market could push the price such that the loss could be many times that.

        Can you please provide some guidance on how to resolve this apparent bug in eSignal. I'm running the latest version of eSignal, TWS, EFSAT_SAMPLE.efs and Windows 10 and have no problems with dozens of other applications. Also no problem executing orders on IB's TWS as this version of TWS is stable.

        So it appears that this is a eSignal-IB interface bug which I need your help in resolving?


        Thank you

        Comment


        • #19
          Alexis,

          Thank you for the clarification.

          The post only stated "eSignal 12" how is one to know if that is Version 12 or Release 12 without the customary Vxx.Rxx or xx.xx?

          I did not realize that EFS Automated Trading is still in Beta...after 7 years.

          As always I very much appreciate you assistance as now I have a probable resolution to my problem.

          Thank you,

          glen
          Last edited by demarcog; Yesterday, 09:19 AM.
          Glen Demarco
          glendemarco@gmail.com

          Comment


          • #20
            I uninstalled and reinstalled R14 and trades are going to IB successfully again.


            Thank you Avery and Alexis for the help.

            Glen Demarco
            glendemarco@gmail.com

            Comment

            Working...
            X