Hi everybody.
About my previous post "Consecutive signals" for Phoenix, I've found a "small" bug in my changes to a code
if (CurTime()-s_time>900) {ss=ss+1; bs=0;}
if (ss>=signal_count) {
res=OrderSend(...SELL....);
ss=0; s_time=CurTime();}
it's counting "ticks" during signal is "ON", means not counting signals 1 per 15min bar, instead counting ticks during active signal. That's why such amounts of consecutive signals (100,200, etc.) are working.
The code should be :
...if (CurTime()-s_time>900) {ss=ss+1; bs=0; s_time=CurTime();}...
Then even 2 or 3 as signal_count reduces number of trades significantly.
On the other hand, this buggy "tick counter" instead of "signal counter" works too, at least at tester. Now testing it live, let's see...
About my previous post "Consecutive signals" for Phoenix, I've found a "small" bug in my changes to a code
if (CurTime()-s_time>900) {ss=ss+1; bs=0;}
if (ss>=signal_count) {
res=OrderSend(...SELL....);
ss=0; s_time=CurTime();}
it's counting "ticks" during signal is "ON", means not counting signals 1 per 15min bar, instead counting ticks during active signal. That's why such amounts of consecutive signals (100,200, etc.) are working.
The code should be :
...if (CurTime()-s_time>900) {ss=ss+1; bs=0; s_time=CurTime();}...
Then even 2 or 3 as signal_count reduces number of trades significantly.
On the other hand, this buggy "tick counter" instead of "signal counter" works too, at least at tester. Now testing it live, let's see...