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 am having an issue with charts stopping updating. I will post the link to Ninja Trader Support Forum were I posted the information. I am unable to duplicate this error as it happens at random. Has anyone else had this happen with NT7? If so, can you reproduce this problem? Unless I can provide a way to reproduce, I think it will get dropped by NT support like it did in January?
Any help on this or other things to try?
Note: I have had this happen on a single chart with no indicators, no moving averages, nothing just a blank default created chart.
I am responding because I use NinjaTrader with TWS. No, this has never happened to me so far.
The bid/ask shows that NinjaTrader was still correctly connected and registered the ticks. The chart shows that these ticks were not displayed on the chart.
The question is, what does prevent NinjaTrader from processing the ticks correctly, which it received from TWS, because bid and ask data is displayed on the chart trader.
In cannot be RAM limitations, because NT would simply shut down. So what comes to my mind is
-> a CPU limitation, if two many data is processed at the same time
Do you run any market analyzer or a complex indicator, which could interfere with the data processing?
Did you try to monitor CPU load during such an event via the Process Explorer or similar?
"'Do you run any market analyzer or a complex indicator, which could interfere with the data processing?
Did you try to monitor CPU load during such an event via the Process Explorer or similar?"
Hey Fat Tails:
I haven't used the performance monitor. I'll check and see if there is any processes running that might slow it down. I never have notice any slowness while in use. I use only standard Moving Averages, Stochastic, RSI, and your sessionpivots. I have had this issue with only 1 chart open and no indicators.
Do you have the Filter bad ticks option checked? The last 2 times this has happened was right when market news was released and the market made a sharp quick move? Just wondering if the Filter bad ticks option might be causing an issue?
Yes. It has happened to me several times this week. Most recently on Thursday, July 14th around 4:30pm CST. on the 6E. Bid/Ask was much moving higher & higher - much higher than the last bar displayed on my chart. I hit F5 several times - no change. Then I re-loaded historical data and ...... Same thing - Nothing changed. It looked just like it did before reloading historical data, then about 3 or 4 minutes later - bam, bam, bam, bam - more & more bars started appearing, in rapid succession - almost as though Ninja had frozen at 4:30 pm. Internet was fine, email was working fine. I have no explanation as to why this is happening. Maybe someone at Ninja can look into it. I'm stumped. Could be very costly to us, however !!
Let me know if you find any answers.
After all, it's what you learn AFTER you know it all, that counts!
This happened to me at the same date/time as it happened to you (CST) on the 6E. I also hit F5 several times and re-loaded "ALL" historical data - and NOTHING - Bid/Ask was moving (and had been moving the entire time the chart was frozen) on the "Chart Trader", but price bars and price marker where frozen. I wasn't in a trade, so, I disconnected and shutdown NT. I opened NT back up and re-connected. Again, chart still frozen, but Bid/Ask at least moving. So, fully shutdown the computer, re-booted, started NT and re-connected. This time everything working as it should - I guess. And, yes, I did check internet connection after the first shutdown of NT - pinging the Chicago test server at 28ms
Just to be clear, this is the first time that it has happened to me.
FYI: I use TT as a data feed. Probably has nothing to do with it though. I would be the wrong person to ask anyway.
I found a post on Ninja Support forum last night that describes an issue similar to mine. Bad tick filter is most likely the problem. I have disabled it and will monitor. Hopefully the fix is as simple as that. Being set to .01% depending on the instrument price could mean it would filter out what could be very small price movements.
