Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
I see that SodyTexas set up a CL native spread in NT7 as CLES1. I have a CQG data feed and NT8 and am trying to set up to trade native spreads too.
No luck so far, and I think I have copied what SodyTexas did in my NT8 setup, see my screen shots. But when I try to add a CLES1 06-17 instrument so I can put it on a chart, it says "Invalid instrument name". Has anyone successfully set up and charted an exchange traded spread like this in NT8? I have tried different combinations of symbols, like CLES1 06-17, CLES1 07-17, CLES1, CLES1N7, CLES1N17, CNES1N 06-17, CLEAS1 N17, CLES1-N17.... none work. I believe the actual CL Calendar Spread symbol for the Jun-Jul 2017 spread would be CLES1N7, correct? Why can't I enter this in NT8 if the CQG data feed supports it?
I called the CQG Chicago office and asked their support if they could help set up the spread in NT8, but they didn't know how. She said that what I'm trying to trade on their system would be CLESM-CLESN, but that doesn't work in NT8 either.
Thanks!
Bryan
Can you help answer these questions from other members on NexusFi?
Yes, "officially" from NinjaTrader that is true. However, I have seen some posts from on futures.io about people who got it to work in NT7. SodyTexas was one of them.
I don't know what @SodyTexas did but the idea is to create a symbol with the right mapping, see screenshot as an example.
The exchange has to be "defaut" and not the right one (at least from what I found).
No success to map a symbol from IB (it should be TSLA 180817C00350000 in my example) yet.
