View Full Version : Number of stop orders not correct
BradB
01-25-2007, 04:19 AM
I have been testing a few strategies for the last 3 days. They enter the market as designed, but when the orders are filled (10), the corresponding stop orders do not match. Once this morning I got a 1+8, and once I got a 1+2. Any ideas???
I have attached a print of my order screen.
NinjaTrader_Ray
01-25-2007, 04:23 AM
BradB,
I can't say without seeing your code. Assuming it is coded correctly, then for sure one would expect the 10 lot to be protected. Could you send me the strategy code and a screen shot of the strategy dialogue window when applied to a chart so I can set it up using your exact settings?
ray at ninjatrader dot com
BradB
01-25-2007, 04:34 AM
Strategy screen as requested...
Strategy code to follow
BradB
01-25-2007, 04:37 AM
Code as requested...
NinjaTrader_Ray
01-25-2007, 04:39 AM
What time frame and market?
BradB
01-25-2007, 04:42 AM
ER2 03-07 10 Minute
NinjaTrader_Ray
01-25-2007, 04:56 AM
Can you send us an email via Help > Mail to Support, in subject include "For Dierk"
Thanks.
NinjaTrader_Dierk
01-25-2007, 05:01 AM
Also: please send me traces and logs plus order id and timestamp of order in question.
Thanks
BradB
01-25-2007, 05:57 AM
I cannot get the 'mail to support' function to work. I believe there is a problem with our Exchange box at the office here. I manually emailed what I hope was the files you are looking for. Let me know if you need more...
NinjaTrader_Ray
01-25-2007, 07:36 AM
Where did you send it to?
NinjaTrader_Ray
01-25-2007, 07:36 AM
Where did you send it to?
BradB
01-31-2007, 04:00 AM
subscriber-support@ninjatrader.com (mailto:subscriber-support@ninjatrader.com)
You didn't get it?
BradB
01-31-2007, 04:01 AM
Today I had 9 of 10 stops filled, and one simply cancelled.
BradB
01-31-2007, 04:33 AM
We had SMTP blocked at our firewall. We changed it and I was able to successfully send via the "mail to support" function today. I also attached today's order info...
NinjaTrader_Ryan
01-31-2007, 04:41 AM
Hi Brad:
What email address did you use to send this to us? We can keep an eye out for it in our support queue.
Thanks,
Ryan
BradB
01-31-2007, 04:42 AM
bekowies@macomb.edu (mailto:bekowies@macomb.edu)
NinjaTrader_Ryan
01-31-2007, 04:46 AM
Thanks Brad.
We received it and forwarded to development.
NinjaTrader_Dierk
01-31-2007, 05:15 AM
I noticed you are still on NT6B5. This beta is outdated.
Please update to latest NT6B6 and try again. I even would suggest waiting a few days more when next beta NT6B7 with most recent bug fixes comes out (a few days from now).
BradB
01-31-2007, 05:33 AM
No problem. Do you send out a notification when the new beta is available?
NinjaTrader_Dierk
01-31-2007, 05:35 AM
Notification on NT6B6 was sent out 2 week ago.
Notification on NT6B7 is not yet sent out.
BradB
02-05-2007, 01:24 AM
Do you do this by email? Is there a way I can tell from the web site what the current beta/realease level is? Thanks.
NinjaTrader_Dierk
02-05-2007, 01:33 AM
Start NT -> Help->Download site will tell you which is the latest release/beta.
Note: Right now NT crashes if you haven't "*.htm" file extension associated to a browser. This will be fixed the next beta.
BradB
02-05-2007, 07:41 AM
I thought I would try to download 6.0.0.6 to see if it resolved some of my problems, but I get the attached error...
NinjaTrader_Dierk
02-05-2007, 07:50 AM
Please clear your browser cache and download the installation file again. If still not working, try a different browser of even one of those free downlod tools.
BradB
02-06-2007, 02:07 AM
Just an fyi....installing 6.0.0.6 didn't eliminate the problem... Will wait for b7.
NinjaTrader_Dierk
02-06-2007, 02:10 AM
Great. Next beta will hold some changes related to high-requency order handling. This could make a difference.
There is a logic error in the code attachment. However, its probably not the error that BradB was looking for.
The following lines are found twice in the strategy....
if (Bars.DayBreak)
orderPlaced = false;
...and the second time is right after the orderPlaced flag might have been set to "true" after an EnterLong() was done.
I'm sure this is not the intended result.
KBJ