[sevensa]

Originally Posted by rcossey73 »

I don't use e-signal so not sure how it works. I do use NT with Zen-Fire data feed and there is not another application or two others as you state. I use NT to place orders with my broker...

You failed to read my first post then, I stated that I did use IB and with NT and do not use them any longer. If this issue no longer exist than that is fine, I only pointed out that it was an issue.

Ok, so how you do code your automated strategy to detect that Zen-Fire lost connection and is no longer feeding data?

[Tams]

Originally Posted by rcossey73 »

If there is then I can't find it, and if so then that means there are 3 apps required for NT to work with IB then.

Open your Task Manger...

look under the Processes or the Services tab...

all your resident programs are there.

[diablo272]

I use Ninja with Zenfire, and when I start Ninja, only one executable is added to the processes list. When I connect to Zenfire, no executables are added, so I'm not sure if there is something between Zen and NT in this case. That's just what I can see--I don't know much about this kind of technical stuff, though I'd like to learn more--so there could be something I'm missing.

I think if you really wanted to know for this particular case, you could just go to the Ninja forums and ask one of the CS reps there.

[Tams]

Originally Posted by diablo272 »

I use Ninja with Zenfire, and when I start Ninja, only one executable is added to the processes list. When I connect to Zenfire, no executables are added, so I'm not sure if there is something between Zen and NT in this case.

To be exact, he is concerned the broker connection.

The zen connection can be in a dll.

[rcossey73]

Originally Posted by Tams »

Open your Task Manger...

look under the Processes or the Services tab...

all your resident programs are there.

Nope, only one new program when NT is started and connected.

[diablo272]

Originally Posted by Tams »

To be exact, he is concerned the broker connection.

The zen connection can be in a dll.

I suspected that what you were talking about had something to do with dlls or something like that. I sort of know what the purpose of dlls are, but not enough to be useful, so I think I'll just stop talking now.

[rcossey73]

Originally Posted by sevensa »

Ok, so how you do code your automated strategy to detect that Zen-Fire lost connection and is no longer feeding data?

There is nothing to code, as NT can already detect this failure with Zen-fire and many other feeds/connections.

The thing to determine (possibly code) based on your strategy is what you need to happen once it detects the failed connection. The whole point is making sure NT does detect the failure so you can act upon it. The more applications in the middle the harder this may be.

Although you state this is no longer an issue with NT, it was at one point so it is important to make sure you are using the recommended versions of each application.

[Tams]

Originally Posted by rcossey73 »

There is nothing to code, as NT can already detect this failure with Zen-fire and many other feeds/connections.

The thing to determine (possibly code) based on your strategy is what you need to happen once it detects the failed connection. The whole point is making sure NT does detect the failure so you can act upon it. The more applications in the middle the harder this may be.

Although you state this is no longer an issue with NT, it was at one point so it is important to make sure you are using the recommended versions of each application.

I don't know of any keywords or commands you can use to "program" your strategy in the event of signal failure/absence.
and I really don't know, realistically or practically, anything NT can do.


Let me explain,
NT is an event driven program. (which is how 99.9% of the charting software works)

Event-driven means your program is sitting idle ALL the time.
It is not updating your chart,
it is not re-calculating your indicators,
it is not doing anything... just sit there... waiting... for the "event" to happen.

The "event" being a new tick.

When a new tick comes in, the software will spring to life...
it will re-calculate the indicators,
it will update the chart,
it will take whatever actions directed by your strategy.

In the absence of a new tick... the indicator/strategy is just sitting idle... not doing anything.


Hope you see a better picture...