How long does it freeze for each time and what does the NT trace file record at the point of freezing.
I had many months of intermittent chart and DOM freezing and I finally discovered it was all to do with my Broadband connection (nothing to do with NT 6.5 at all). But before I explain my situation I would like to know what messages are recorded in your NT Trace file to see if it is the same issue I had. Look for the words 'heartbeat' and/or 'lost connection'.
Do not be fooled, you can get 'lost connections' in the Trace file and still have the green connection light on Control Center the whole time.
The following user says Thank You to steve2222 for this post:
NT support already analyzed my trace file and instructed me to rid myself of one file that was in conflict, and could not find anything else that would be affecting NT's performance.
I also "detuned " my charts, eliminated non-essential 3rd party indicators, and followed all the performance tips that were suggested by NT and others, so it looks like a move to NT7 is the the next logical step.
Thanks to all, for your advice and suggestions.
This is arguably the best trading forum in the world!!!
The following 2 users say Thank You to tigertrader for this post:
Haha what is heartbeat? I have problems with freezing charts, but didnt have "heartbeats" up til now. Today I run the Zen Fire trial feed and get some heartbeats. Is there a problem with my connection? NT does know my trace file too, but I think I did not get heartveat issues with my erlier used Kinetick feed. Nevertheless it froze some time.
This is from Zen Fire SIM feed (today)
When I encountered 'heartbeat' issues I would often get several of them very close together - like every 50 seconds.
Initially I was convinced it was a NT/ZenFire issue as my internet would still work when my DOM locked. In fact I could still log on to ZenFire's web based interface and it was fine.
I tried everything ( re-install, try NT7, disable Skype/AntiVirus, wireless vs LAN connections, different computers etc) and yet intermittently I would still get the problem.
ZenFire were adamant it was not a fault at their end, they say they broadcast the data like a radio station and NT 'listens' out for it like a radio receiver. NT said the 'heartbeat' error meant NT could not detect a 'radio' signal - hence the DOM locking.
Anyway after poking around on the web I started to wonder if it was some technical aspect to the broadband delivery - and it was.
Here is the situation that existed for me in NZ: we use ADSL and ADSL2+ for the delivery of broadband over the standard copper wires for the phone line (there is hardly any cable services in NZ). I was on a data plan with my ISP that was uncapped ie no download data maximums - this plan has since been cancelled by the ISP. But what the ISP did to avoid bandwidth being hogged is reserved the right to data mange users connections. The way they did this was to slow down the download speed (and upload speed) for users accessing file download sites and peer to peer sites.
You were unaffected if you were just accessing a normal web page ie a www. site, hence why the ZenFire web interface still worked. Now what happened is ZenFire/NT got caught up in this data management as you don't' access a www site to get your trading data. In other words the ISP was treating ZenFire as a peer to peer arrangement and throttling back my download speeds in such a way ( I don't know the technology they use to do it) that NT was losing the 'radio' signal every now and then, hence the 'heartbeat' errors.
I also found that my two adult sons had inadvertently set one of their peer to peer download sites to allow sharing of files off their own computer (we all share the same router/internet connection) which significantly affected upload speeds which exasperated the problem.
So what I did to fix it is move to a new plan with the ISP that has a maximum data download limit (40Gb) for the month (but way more than enough to handle all my requirements) but has NO data management on that plan. I also made sure my sons do not allow sharing of files off their computer.
Since doing this I have had NO issues. Even when others on futures.io (formerly BMT) have complained about ZenFire issues, my connection has been fine.
So I suggest you look at the type of internet plan you are on and insure the ISP does not have any rights to manage the data download rates etc and that you have no programs running that allow others to access your files while trading - and that probably should include Skype.
The following 2 users say Thank You to steve2222 for this post:
I am having issues with my Dom price skewed from my chart and my charts are freezing up. To say I'm pissed is an understatement. This is only a problem with one instrument. I have contacted NT and their incapable support team cannot help. I have the newest version, but not beta and I did the db repair and removed and reinstalled the account connection. And still the problem persists, can someone help?
If you want any help, you need to give us more information:
-> which instrument is affected?
-> which NinjaTrader version are you running?
-> which datafeed do you use?
-> what assemblies do you have installed?
-> which custom indicators are you running?
-> are you running your indicators in CalculateOnBarClose mode set to "true" or " false"?
I have looked into this and one of my support team members said that he had requested a telephone number and a time that we could call you to provide remote assistance. Once we receive that information, we will work with you resolve your issue.
The following 3 users say Thank You to NinjaTrader for this post:
The problem has been determined to be a Trading Technology server issue with a specific FCM. From what we can tell, only demo (sim) connections are impacted but not live accounts. We are following up directly with the FCM to inform them of this problem so they can resolve it.