I wanted to see if anyone else had experienced similar issues after converting to CQG feed with NT7. I was using the static DOM and on a few occasions, I hit the 'C' or 'Close' button on the DOM and a trade was initiated. I have not been refunded by the broker, who should have advised me to switch back to my old feed after the first incident. Ninja Trader support has confirmed that this is an issue specific to CQG. I also think it may be specific to the static DOM, but can't confirm that.
Has anyone else experienced similar issues?
Thanks.
The following 2 users say Thank You to GoldTrader740 for this post:
I've had problems with CQG as well. Not with the DOM but on the charts with my orders appearing in various places where there were no bars on the chart. Couldn't wait to get back to Zenfire.
The following 2 users say Thank You to JohnnyAustin for this post:
Had many similar issues during my 12 month tour in the ninja and trust me you can look forward to more. I've posted on this subject previously, but my experiences include orders not transacting, orders doubling up, being flat and then ten minutes later out of the blue a position popping up on the screen showing that you are still in the trade, fills showing they transacted 20 ticks off the price, etc. Just consider it part of the initial excitement of using ninjatrader. As you mature as a ninjatrader user, however, you will eventually learn to handle yourself and no longer freak out when you get deep into the shiz. You will learn to calmly flatten all, contact your broker to make sure you really are flat, and then take the losses like an old pro. Eventually people will know you are a ninjatrader user simply by the stare.
To be fair I should add that my experiences all ocurred on 6.5 and the beta versions of NT7 through .18 as I recall, which did have fewer problems than 6.5. Also, per chance, I actually netted positive on all the errors, but just too many problems that I am certain shortened my life span, so I had to move on.
The following user says Thank You to vegasfoster for this post:
I am not 100% sure, but I believe this error is related to an issue by where CQG decremented their API version number (mistake that they ensured us will not occur in the future) and as a result, the MS Installer sometimes does not overwrite the CQG API DLL's. Please try uninstall NinjaTrader, then re-install, this forces the installer to install the latest DLL's.
If this does not resolve the issue, please report to my support team. Thanks.
The following user says Thank You to NinjaTrader for this post:
I trade a live account with AMP / NT / CQG and have not once experienced an issue with the data. My ISP is another issue. I saw some reports that yesterday there were some issues but I think they are connected to Sim accounts. My live account did not miss a beat.
Site Administrator Swing Trader Data Scientist & DevOps
Manta, Ecuador
Experience: Advanced
Platform: My own custom solution
Trading: Emini Futures
Posts: 49,740 since Jun 2009
Thanks: 32,288 given,
97,473
received
Consider this...
A lot of people complained about Zen Fire connections. Later it was discovered that different brokers use different connections or servers, so some users never experience problems with "Broker A" while other users experienced constant problems with "Broker B". All the while, users using Rithmic (the OEM of Zen Fire) also experienced no problems using "Broker C" and "Broker D".
The same may be true for CQG. I don't know. But you guys should post which broker you are using, or if you are going direct to CQG, to help narrow down the problem.
Also, as mentioned, sometimes it is just an internet problem. When the problem manifests itself, make sure you can still get to other websites like futures.io (formerly BMT), Google, CNN, etc and that it isn't just a general problem with your internet connection. It is also advisable to not use a WiFi connection, but instead a hard wired connection between your router and PC.
In a trade, I have an OCO bracket and I am close to one of the exits - target or stop, doesn't matter.
I am close to my stop or target and I close the trade - either I think my stops going to get hit anyway or I think we may reverse and I take profit early.
What appears to happen is I close the trade and this somehow manages to actually reverse the trade. It doesn't happen all the time and I can't reproduce it any time. I can't be 100% sure what exactly is happening. All I know is that I think I am out but I am really still in - this time in the opposite direction with no OCO.
please note, CQG does not "suck"... it is one of the better feeds out there... what sucks is AMP Infrastructure and NinjaTrader Implementation talking to CQG API... of course, you should always make sure your inet connectivity is good before making the statements below as well.
Thanks for your advice here Big Mike re: wifi vs hardwire. I'm still sim trading live using MIrus/NT and my wifi. I'm re-designing my office and was contemplating keeping the wifi connection but will take your advice and hardwire that connection even though I have to drill some holes.
NinjaTrader claims this is due to corrupt installation files on your side (not theirs), something I doubt seeing as very many are getting this exact error when installing newer versions. Anyways, a re-install usually solves the problem.
As for CQG having trouble, I have tested demo accounts via AMP with both CQG and ZenFire feed. Both feeds have had all kinds of weird issues, and I suspect that the problem lies with AMP rather than the feeds themselves.
I start having problem with CQG login since last week. Error msg ( Login Failed: Failed to receive login message response from SecBuf) anyone have the same issue?
Working fine and has been for ages here, with no changes, nor unsuccessfull connects. I connect via Amp's CQG infrastructure.
Any chance something software-wise has been introduced to your machine? Anti-virus programs can easily be culprits too, and turning them off (vs. uninstalling) doesn't always work.
If you have access to a 2nd PC, you can freely download NT via NT's site onto that machine and install, using the same license key - this would help you isolate if it is a issue with that specific PC.
The following user says Thank You to Beljevina for this post:
hi Peter, what you described above seems to be CQG's default behaviour when you have bracket orders enabled.
Say you enable a bracket OCO with a 5-tick stop and a 10-tick target. In CQG you then enable bracket orders, meaning the next market or limit order you place will be a bracket OCO one.
When the order is filled, the 5-tick stop and 10-tick target orders are automatically put in place. So far, so good.
What happens in CQG is, unless you now switch from "bracket order mode" to, let's call it "normal order" mode, if you close the trade manually(say at market), you are actually triggering a second bracket order, in the opposite direction of the prior one. You will have no positions on but you will have a stop and a limit on the opposite side that will be triggered if market reaches either of them.
What I do is trigger the first bracket order and then switch to normal mode if I want to close it manually.
Does it look like the scenario above might be what was happening?
