Announcement

Collapse
No announcement yet.

Esignal/IB Order entry Stop Orders???

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

  • Esignal/IB Order entry Stop Orders???

    I attempted to place a SELL/SHORT Stop order via the Esignal Order entry tool with IB.

    Price was at $1.10

    Esignal Order confirmation came up saying...

    SYMBOL SELL STOP @ $1.00..i went yes...nothing went thru to IB/TWS

    I get an error message saying auxprice not entered, when clearly I have...

    Does the Sell/short tool work with IB in esignal, can any of you confirm this, do I have to turn something on.

    Any ideas..

  • #2
    IB Issue

    Digs,

    We have seen this error before. To correct this, please make sure you have the latest versions of eSignal, TWS, and the IB Plug-in for eSignal.

    eSignal Download Site

    TWS Download Site

    If the issue continues or if I can be of further assistance, please let me know.

    Regards,
    Jay F.
    Community Support Specialist
    eSignal
    Regards,
    Jay F.
    Product Manager
    _____________________________________
    Have a suggestion to improve our products?
    Click Support --> Request a Feature in eSignal 11

    Comment


    • #3
      I have all the correct versions

      IB/TWS version 786.8 2003/01/30 14:30

      Java SunMicrosystems 1.4

      Esignal 7.2 Build 544 1/27/2003
      - With IB plug in of the ame date.[and I installed plug in after Esignal]

      Any ideas

      Comment


      • #4
        I just re installed TWS/IB and Esignal IB Plug in..

        Just did a STOP Order on INTU

        Price at 45.50

        I went BUY STOP AT 46.00

        It failed, saying Aux prices incorrect...same as before, no transfer to IB/TWS software, nothing in pending

        Then I tested a STOP LIMIT order...

        I went BUY STOP LIMIT AT 46.00, 46.10..

        This worked fine, Order showed up in TWS correctly, entry in pending ok...

        So It must be esignal code problem..

        please check

        Comment


        • #5
          IB has done something in the laqtest version that make my Bracket Trader STOP orders into STOP LIMIT orders. It has something to do with the gact that Globex does not accept straight stops, only STOP LIMITS and previously IB held the stops onits servers and if the Globex/IB connection went down, your stop was not executed.

          Tom

          Comment


          • #6
            Hi Digs,

            I use IB myself. I have eSignal 7.2, JavaScript 1.4.1, but the TWS API is 6.0. In 7.1, the stop order interface didn't work. Like you say below, I would get an auxprice error msg. That was an error in our code. We corrected that in 7.2. When I upgraded to 7.2, at that time I had TWS API 6.1. I entered a stop order and it worked. Then I downloaded Bracket Trader and in order to get that to work, I had to downgrade the TWS API to 6.0. So I have been using Bracket Trader for several weeks now with no problem. This morning, upon reading this thread & working with Jay, I went into the IB demo account and then thru eSignal / IB order Entry interface, I entered a limit order then immediately enterd a stop order and all was transfered over to the TWS system with no problems.

            I'm not sure where to go with you next on this as it is working for me. I realize that you have a problem and this is not to say that there is not a problem, but just that it's not a problem here. Are you on TWS API 6.1? If so, try downgrading to API 6.0 and see if that corrects your problem. You can get the link to TWS API 6.0 downgrade here.

            Let us know if there's anything else we can do for you.

            Regards,
            Andy S.
            eSignal Support

            Comment


            • #7
              My latest test...

              TWS/IB version 787.2 as of 02/25/03...Windows Standalone

              Java 1.40.03

              Esignal/IB Plug in the same as 7.2 buil 544.

              I uploaded IB API 6.01 ...

              Did the stop order ...it failed

              I uploaded IB API 6.00..stop order still failed.

              Stop order fail was AUXprice error

              My system is Win Xp, SP1, Intel 2.4 GHZ, 512 RAM.

              Ok who has stop orders working, please advise me on your exact system setup with version details please ( ie of Esignal, IB Plug IN, IB API, IB/TWS, Java).

              Question : How do you find Esignal IB Plugin to check version details?

              thx

              Comment


              • #8
                Hi Digs,

                Here's my set-up for which the stop orders work;

                TWS/IB version 786.8 Windows Standalone

                Java 1.4.1

                eSignal 7.2 build 544

                IB API 6.0

                Here's the potential catch - Latest IB plugin

                On the IB plugin, there currently is no good way to determine what the version is (latest or not). I have addressed this situation with Product Management and hopefully in the future they'll add a version number. If you are not sure that you grabbed the latest IB plugin, which was posted to our site on Feb. 3rd, 2003 then I recommend that you go and download that again. Can't hurt. If you do, please be sure that when you download it that eSignal is NOT running. The link to get the plug-in is here.

                Let me know if this helps.

                Regards,
                Andy S.
                eSignal Support

                Comment


                • #9
                  yes fixed it...

                  I re installed IB Plug in on my setup below....

                  If the Esignal Plug in is responsible for the Esignal Order Entry screen for IB, then that was at fault.

                  When it was not working , after I selected Order type STOP, the box to put the stop price in was the "LIMIT PRICE". When it worked this box was turned off, and the STOP LIMIT PRICE was turned on...so the wrong box was turned on when STOP order type was selected.

                  Developers get a version number on the IB PLUG please, as issues are bound to arise again, as they do as part of the code evolution process.

                  Thx

                  Comment

                  Working...
                  X