• If this is your first visit, you will have to register before you can post. To view messages, please scroll below and select the forum that you would like to visits. Questions? Be sure to check out the Forum FAQ.

Announcement

Collapse
No announcement yet.

Partner 728x90

Collapse

Setting up API M7

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

    Setting up API M7

    How to set up the SPI M7 future in the instrument manager? What need to be typed in each of the fields?

    Thanks~

    #2
    updated post with images~

    Problems also occured in HSI M7-HKF, here is the setting for HSI M7.

    The default settings of the instrument manager, is there anything I need to change?



    Thanks!
    Attached Files
    Last edited by vivienne; 05-06-2007, 10:36 PM. Reason: further explanation

    Comment


      #3
      Both instruments are already set up in the NT DB. There is nothing which you need to change.

      To make sure your setup is correct:
      - terminate NT
      - copy file <program files>/NinjaTrader6/db/instruments.txt to <my documents>/NinjaTrader.db
      - restart NT: instrument setup will be reset
      - Tools-> Instrument manager
      - select both instrument and add them to your default instrument list
      DierkNinjaTrader Customer Service

      Comment


        #4
        but, there is the error message in the LOG
        Attached Files

        Comment


          #5
          This is a limitation of the ATI functionality when driven from eSignal: NT can not handle the "-HKF" suffix.

          You would need to replace "getSymbol()" in your efs script (see e.g. NTCommand function) by e.g. "HSI M7" (without suffix).
          DierkNinjaTrader Customer Service

          Comment


            #6
            Thanks.

            So, now I try to use IB as the data feed, and the symbol APM7 is working fine.

            For the FDAX market, the esignal symbol is AX M7-DT, since it got the same suffix, so I use the IB one, which is FDAX JUN 07, and this IB symbol is not also got same error as the AP M7-SFE. Is it also because of the suffix "JUN 07" not supported?

            Thanks a lot!

            Comment


              #7
              Let's make sure we are not talking apples and oranges: The issue is related to the eSignal symbol name and not to the IB symbol name (where you place your orders).

              -> NT ATI does not accept any eSignal symbol with a suffix
              DierkNinjaTrader Customer Service

              Comment


                #8
                Yes. I am having problem on the esignal symbol on HSI, FDAX and SPI. So now, I try to use the symbol from IB.

                I am using esignal data feed in Multicharts and send the orders to IB through Ninja Trader. Seeing the problem with the SPI symbol of esignal, I switch to use IB data feed in Multicharts.

                For the SPI symbol in IB, it is APM7, so it is working fine, but for the FDAX, the IB symbol is FDAX JUN 07, it is having problem again.

                Comment


                  #9
                  Please see below: in eSignal you need put in e.g. "FDAX M7" and not (!) the IB symbol.
                  DierkNinjaTrader Customer Service

                  Comment


                    #10
                    In Esignal, I need to use the symbol "AX M7-DT" . Since you said the suffix is not yet supported. So I switch to IB, and the IB symbol is "FDAX JUN 07".

                    attached please see the error in the log
                    Attached Files

                    Comment


                      #11
                      a) We are going round in circles. Again: you can not (!) have a suffix on the symbol as you place an ATI command in eSignal. Please try hard coding "FDAX 06-07" in your eSignal EFS script.
                      b) The "unknown right" error in your log is related to a change IB made in TWS recently. This problem is not related to the above. next NT update will work around this TWS bug.
                      DierkNinjaTrader Customer Service

                      Comment


                        #12
                        So.. when is the next update??

                        Comment


                          #13
                          Not yet scheduled. Please see below: issue (b) is not related to your symbol mapping problem nor does it cause any other problem.
                          DierkNinjaTrader Customer Service

                          Comment

                          Latest Posts

                          Collapse

                          Topics Statistics Last Post
                          Started by BatBart, Today, 01:24 PM
                          1 response
                          21 views
                          0 likes
                          Last Post NinjaTrader_Melissa  
                          Started by ezrakoper, Today, 03:05 PM
                          1 response
                          7 views
                          0 likes
                          Last Post NinjaTrader_ChelseaB  
                          Started by asmmbillah, Today, 02:23 PM
                          1 response
                          17 views
                          0 likes
                          Last Post NinjaTrader_Jesse  
                          Started by steveg, Today, 02:44 PM
                          1 response
                          9 views
                          0 likes
                          Last Post NinjaTrader_Heath  
                          Started by lightsun47, Today, 12:33 PM
                          1 response
                          14 views
                          0 likes
                          Last Post NinjaTrader_Jim  
                          Working...
                          X