Problems with NTConnected

[muthaf]

Guys,

I am trying to write my ATI and can seemingly place an order but I am not getting the right returns from functions such as NTOrders etc. When looking at NTConnected I keep getting that my EFS is not connected to NT5.

Also the order I place does not seem to have the OrderID I supplied to it. Are all these issues related to the same thing? Can someone send me a sample EFS that truly works?

TIA
MuthaF

[NinjaTrader_Ray]

See the sample NT EFS in the Help Guide (also installed on your PC) that does work.

[muthaf]

Thanks for the reply. If I modify that script to represent the NTConnected status in the formula output window I get "false".

[NinjaTrader_Ray]

Is Automated Trading Enabled via the File menu in the Control Center window?

[muthaf]

Hi,

Yes the Automated Trading is enabled, the ATI at the bottom right is green and the log says that NT has established a connection to the eSignal Data Manager.

Since I posted last I have downloaded the very latest version and still have the same problem.

Regards,
MuthaF

[NinjaTrader_Ray]

For clarification, when you call this function, it returns a value of "-1" ?

[muthaf]

Yes

[NinjaTrader_Ray]

Will get back to you Monday morning, have escalated this.

[muthaf]

Many thanks

[NinjaTrader_Ray]

Please try the the sample script unaltered. Does this work as intended?

[muthaf]

It loads but does not buy any contracts which is why I started to look into the reasons why and the state of NTConnected

[NinjaTrader_Ray]

On what instrument?

[muthaf]

FDAX instrument. I've retried the NTSample.efs script and this time it seems to be trying to reinstall NinjaTrader. It's trying to install (very slowly) but will let you know what happens. It seems to be a DLL registration issue which would make sense except I was able to run NT by itself and it's only he ATI interface that seems to be the issue.

[NinjaTrader_Ray]

FDAX is not supported out of the box since the instrument mapping will not work since eSignal has a "-d" at the end of the instrument. You have to create a new wrapper function for NTCommand() that passes in the correct instrument name for FDAX which is "FDAX 06-06". Trythat. If you use the script on another instrument like ES you will that it works as designed.

[muthaf]

I've found that out and changed my code for NTCommand. What is still the issue is NTConnected. For NTCommand I've got an EFS object that is loading all the stuff I need into that structure.

[muthaf]

The attempt by NT to install something from the MSI gave the clues. I've had to reinstall the package twice but after doing that it seems to work! Onwards and upwards, going to restart the machine and try again to make sure.

Thanks for the support, it seems to have been an install issue.

UPDATE: After reboot it still seems to work... :D

[NinjaTrader_Ray]

Thanks for lettting me know.

Ray