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)
My connection dropped again today at 9:04:50. I really don't like attempting to trade with trepidation over the data feed. There has been great movement today in NQ.
I'm very patient, but this is getting old. I would rather have the issue resolved and move on with AMP, but I'm going to be looking around next week if this continues.
8:55pm EST and I have just been able to connect. Don't know if it was problematic any time earlier; I was logged in through to 5pm close. Was also having the disconnect issues regularly through the day, so we will see if the final fix went in successfully tonight, as of Sunday open.
I lost 10 POINTS on NQ on Wednesday morning after my AMP/CQG connection failed then reported incorrect position information to Ninjatrader. It was a lucky break that I even caught the error. AMP blamed Ninja first. Then Ninja correctly identified the problem was with AMP /CQG. The disconnection problem was supposed to be fixed Wednesday evening. Given that your post from Friday night tells me they didn't get it fixed when they said they did.
As for my losses AMP told me too bad. All the risk is on me even though my loss is caused by a problem that appears to have been known beforehand and they chose not to notify their customers of the potential for loss.
so this thread on futures.io (formerly BMT) would indicate that AMP already knew about the problem before I contacted them, yet they claimed ignorance of the problem and blamed Ninjatrader (AMP even dialed into my computer to verify I was using the latest Ninja version with a valid license string, which of course, I was). Ninja then looked into the problem and later in the day concluded it was in fact a problem with the AMP/CQG feed, which AMP already knew about given the reply from AMPTrading on 7/27/11 at 8:29 AM.
not gonna comment about whose butt they were looking out for on this deal.