This problem has been seen frequently when using an eSignal data feed with NT6 during fast market conditions. Falling behind is understandable, but failing to recover to show the data in real-time is not. Maybe the problem is specific to the NT6 to eSignal interface.
Disconnecting and reconnecting to eSignal results in the data being displayed in real-time. The result is similar to that in a previous post
which received the response:
"When you disconnect, you clear up an buffer on the MBT server side that may be building which could have caused delay. Then when you reconnect, all is back to normal. Any delay is on the data feed side not NT."
It appears there is a buffer in the interface that retains the data, it's not clear who wrote it or who is responsible for fixing it. Since winros was not shut down, it doesn't seem it's an eSignal problem.
The problem has not been noticed with NT5 connected to a Patsystems data feed, so NT5 is used for trading. Maybe NT6 wouldn't have the problem with the Patsystems data feed, but there is some doubt about that.
Today just for kicks, when swing highs or swing lows were noticed to have occurred with the eSignal "real-time" data, simulated orders were placed with NT6 - which was using it's "delayed" eSignal data. This made it pretty easy to make money. Would using data that's not caught up to real-time, make it more difficult to make money?
Comment