View Full Version : Mapping Problem
bushey12
02-12-2007, 01:00 AM
I am having problems getting trades signal from Esignal for the FTSE futures Index tradedusing Interactive Brokers feed.
The symbo; on esignal is 'Z H7-EEI'. NT rejects the order returning a 'holds unknown instrument error message'. I have tried to map this, using the Instrument Manager, by typing: Z H7-EEI for the Esignal fieldunder the Misc tab. It hasn't worked. Can you please tell me the steps to take in order to get this working.
NinjaTrader_Dierk
02-12-2007, 01:07 AM
The "-<exchange code>" logic is not supported by NT right now. I'll look into it.
bushey12
02-12-2007, 02:11 AM
I'm sure some of your clients will be trading FDAX and Z(FTSE Futures). what kind of setting do they use please?
NinjaTrader_Dierk
02-12-2007, 03:32 AM
Sorry, I don't know
bushey12
02-12-2007, 03:46 AM
Dierch, are you saying that NT cannot be used for automated trading of FTSE and DAX futures if your platforms are Esignal and IB TWS. I find this unbelievable. I would really appreciate it, if you can find outfor me howmapping between Esignal and IB can be achieved in NT.
I have spent so much time and effort trying to do this myself. I have already paid my subscription for 3 months with the hope that I can use NT automate trading of my favourite instruments; NQ, DAX and FTSE
thanks
NinjaTrader_Dierk
02-12-2007, 03:51 AM
Please see below: I'll look into it.
bushey12
02-12-2007, 05:15 AM
I figured out a way to do the mapping. I'm posting it for the benefit of those who might have similar problems in future.
The trick is to write a routine within the Esignal efs that converts Esignal symbol to the Instrument symbol recognized by NT. So for FTSE futures, since getSymbol() returns Z H7-EEI (which NT rejects), I pass hardcoded string 'Z 03-07' to NT's dll calls within the efs.
Hope this helps someone infuture.
NinjaTrader_Dierk
02-12-2007, 06:32 AM
Thanks for letting us know. I'm in touch with eSignal support to reoslve this issue.
NinjaTrader_Dierk
02-12-2007, 10:25 AM
I forgot: There already is support for that.
Just add "|EEI" to your instrument mapping for this particular instrument on eSignal instrument manager.