Solo gli utenti che hanno acquistato o noleggiato il prodotto possono lasciare commenti
Catalin Zachiu  

mqsato #:

Added possibility to cancel the pending orders if the price moves too much in a short period of time .
New parameters :
UseDistanceToCancel : true/false
ApproachDistance : distance from the pending order to current price in points which enables the closing of the pending order
JumpDistance : distance between the pending order price and the reference price (high or low of the 1 minute candle /candles defined in the next parameter)
JumpTimeMinutes : defines the number of the passed 1 minute candles from which the JumpDistance is calculated (takes into account the High (for SellStop/BuyLimit orders) or Low (for BuyStop/SellLimit orders) of the candle)

The last parameter is preset to 2 (editable), so it will take into consideration the High or Low of the second candle , counting backwards from the current candle(current candle count is zero) on the M1 timeframe (not neccessary to open the M1 chart) .
mqsato  
Catalin Zachiu #:

Added possibility to cancel the pending orders if the price moves too much in a short period of time .
New parameters :
UseDistanceToCancel : true/false
ApproachDistance : distance from the pending order to current price in points which enables the closing of the pending order
JumpDistance : distance between the pending order price and the reference price (high or low of the 1 minute candle /candles defined in the next parameter)
JumpTimeMinutes : defines the number of the passed 1 minute candles from which the JumpDistance is calculated (takes into account the High (for SellStop/BuyLimit orders) or Low (for BuyStop/SellLimit orders) of the candle)

The last parameter is preset to 2 (editable), so it will take into consideration the High or Low of the second candle , counting backwards from the current candle(current candle count is zero) on the M1 timeframe (not neccessary to open the M1 chart) .
Thank you for your prompt response!
Thank you very much!

I have three questions,
① If JumpTimeMinutes is set to 0, will it be canceled when the condition is reached in less than a minute?
②In that case, is it impossible to verify with a back test and only real trade can be reproduced?
(Even in all tickback tests, JumpTimeMinutes = 0 cannot be reproduced, and is it necessary to set JumpTimeMinutes = 1 or more?)
③Once an order is canceled, how long is the timeframe interval for a new order to be placed?
Catalin Zachiu  
mqsato #:
Thank you for your prompt response!
Thank you very much!

I have three questions,
① If JumpTimeMinutes is set to 0, will it be canceled when the condition is reached in less than a minute?
②In that case, is it impossible to verify with a back test and only real trade can be reproduced?
(Even in all tickback tests, JumpTimeMinutes = 0 cannot be reproduced, and is it necessary to set JumpTimeMinutes = 1 or more?)
③Once an order is canceled, how long is the timeframe interval for a new order to be placed?
Jump time minutes set to zero will take as a base of refference the High or Low of the current M1 candle (developing candle , not yet closed) , the current  M1 candle should be higher than 300 points , if you use 300 as Jump Distance .
Testing on Every Tick shows that the cancelation of orders takes place even if the Jump Time Minutes is set to zero . Control points mode may skip some .
A blue or a red dot will appear on chart , where the order was canceled .
Another order will be placed when stochastic passes through the 50 value on the chart(timeframe) you placed the EA to work on .
mqsato  
Catalin Zachiu #:
Jump time minutes set to zero will take as a base of refference the High or Low of the current M1 candle (developing candle , not yet closed) , the current  M1 candle should be higher than 300 points , if you use 300 as Jump Distance .
Testing on Every Tick shows that the cancelation of orders takes place even if the Jump Time Minutes is set to zero . Control points mode may skip some .
A blue or a red dot will appear on chart , where the order was canceled .
Another order will be placed when stochastic passes through the 50 value on the chart(timeframe) you placed the EA to work on .
thank you for your reply.

I made a loss cut at eurusd15:30 in real trade on 2/16.
It was the moment when the economic index moved 30 pips within a minute.
However, this trade could not be reproduced in backtesting.
① Therefore, I can't confirm the effect of "UseDistanceToCancel" in the backtest, but do you think you could have avoided it in real trade?
②Assuming that transactions with sudden price movements are not reproduced in the backtest, do you think that using "UseDistanceToCancel" for real trades will give results closer to the backtest?
Catalin Zachiu  
mqsato #:
thank you for your reply.

I made a loss cut at eurusd15:30 in real trade on 2/16.
It was the moment when the economic index moved 30 pips within a minute.
However, this trade could not be reproduced in backtesting.
① Therefore, I can't confirm the effect of "UseDistanceToCancel" in the backtest, but do you think you could have avoided it in real trade?
②Assuming that transactions with sudden price movements are not reproduced in the backtest, do you think that using "UseDistanceToCancel" for real trades will give results closer to the backtest?
If you set JumpTimeMinutes to zero and the 30 pip move is made in at least 5 seconds or more , then it should work on real account as well . But ,we also have to consider the widened spread on such moves , maybe ten times the size of the normal spread and so , the distance measured will be shorter and the rest is the spread . 
I had another user some time ago who requested pending order cancelation just by using spread . If spread widened too much , the orders were deleted . Do you want me to implement that condition also in the official product version ?
mqsato  
Catalin Zachiu #:
If you set JumpTimeMinutes to zero and the 30 pip move is made in at least 5 seconds or more , then it should work on real account as well . But ,we also have to consider the widened spread on such moves , maybe ten times the size of the normal spread and so , the distance measured will be shorter and the rest is the spread . 
I had another user some time ago who requested pending order cancelation just by using spread . If spread widened too much , the orders were deleted . Do you want me to implement that condition also in the official product version ?
thank you for your reply.

I would like you to add a function that cancels the order when the spread widens.
Also, if canceled by "JumpTimeMinutes", I would like to have a function that can cancel both "buy" and "sell" and set the interval time until restart.
Catalin Zachiu  
mqsato #:
thank you for your reply.

I would like you to add a function that cancels the order when the spread widens.
Also, if canceled by "JumpTimeMinutes", I would like to have a function that can cancel both "buy" and "sell" and set the interval time until restart.
Added option for canceling both pending orders if UseDistance to Cancel is true and resuming operation timer that can be set in seconds .
Added option for canceling pending orders if spread is higher than the preset value . Operation will resume normally if the spread goes lower than the preset value .
mqsato  
Catalin Zachiu #:
Added option for canceling both pending orders if UseDistance to Cancel is true and resuming operation timer that can be set in seconds .
Added option for canceling pending orders if spread is higher than the preset value . Operation will resume normally if the spread goes lower than the preset value .
Thank you for your prompt response.

However, when I backtested with the "UseDistanceToCancel" option set to true, it did not trade.
Setting "ResumeAfterSecond" to 0 was useless.
By the way, it seemed that there was no problem at the time of version 4.1.
Catalin Zachiu  
mqsato #:
Thank you for your prompt response.

However, when I backtested with the "UseDistanceToCancel" option set to true, it did not trade.
Setting "ResumeAfterSecond" to 0 was useless.
By the way, it seemed that there was no problem at the time of version 4.1.
It does not work on Tester , because the OnTimer function is disabled in Strategy Tester and the timer is programmed into the OnTimer function . It can be tested on a demo account .
sebastian0815  

Hello Catalin, I have a problem with the : Decreses on Win Setting is on Decrease on loses : 0.0 Decrease on win : 2.0 it should start at 0.1, for example, then 0.05 and finally 0.01 until a loss occurs. it works perfectly on the MT4 tester. I have now tested it on DEMO and LIVE accounts for 3 weeks plus on virtual server. he always makes the same mistakes. sometimes the EA does 2 times 100% trades then 2 times 50% trades then sometimes again 100% - 50% - 50% - 0.01 - 50% - 0.01 - 50%.....so it's relatively random. what I also noticed is that the one shown in the chart TOTAL PROFIT / LOSS and DAILY PROFIT / LOSS are displayed incorrectly. maybe it has something to do with that. The MAGIC numbers are all different, that's not the problem. can you help me with that. and as already mentioned, everything runs wonderfully on the MT4 tester, but not in live/demo mode Thanks & Greetings

Catalin Zachiu  
sebastian0815 #:

The formulas for the smart lot are as following : for wins :

if(wins>0)   lot = lot-lot*wins/DecreaseOnWins    // wins are reset if we get one loss

for losses :

if(losses>0)  lot = lot/DecreaseOnLosses  // losses are reset if we get one win

The apparently random results are there because if you get win on a BuyStop , the lot size of the SellStop is not changed , so it remains the same as before .

If you would use "Virtual Orders" the lot size will be changed gradually after the input parameters , but using "Virtual Orders" might give some delays in order execution .

The Daily Profit might not be correct if the EA is relaunched . Daily profit is reset every time the EA is set on a chart or some parameters are changed , because if you change some parameters while running , some internal variables are reset .

If you want me to change the formulas for the smart lot let me know  , or if you want me to add a function for lot size correction for the pending orders .

Another solution would be to use pending buy on one chart and pending sell on another chart , but that will not be so practical .

Until now , nobody said anything about the smart lot function , aparently nobody used it or made any research about it .

I think youu want something like this : (only buystop test , smart lot active , decrease on wins set to 10 , manual lot size set to 0.10 ) 

TS Simulation

sebastian0815  
Catalin Zachiu #:

Die Formeln für das intelligente Los lauten wie folgt: für Gewinne:

if(wins>0) lot = lot-lot*wins/DecreaseOnWins // Gewinne werden zurückgesetzt, wenn wir einen Verlust bekommen

für Verluste:

if(losses>0) lot = lot/DecreaseOnLosses // Verluste werden zurückgesetzt, wenn wir einen Gewinn erzielen

Die scheinbar zufälligen Ergebnisse sind da, denn wenn Sie bei einem BuyStop gewinnen, ändert sich die Losgröße des SellStop nicht, sie bleibt also gleich wie zuvor.

Wenn Sie "Virtuelle Aufträge" verwenden würden, wird die Lotgröße nach den Eingabeparametern schrittweise geändert, aber die Verwendung von "Virtuellen Aufträgen" kann zu Verzögerungen bei der Auftragsausführung führen.

Der Tagesgewinn ist möglicherweise nicht korrekt, wenn der EA neu gestartet wird. Der Tagesgewinn wird jedes Mal zurückgesetzt, wenn der EA auf ein Diagramm gesetzt oder einige Parameter geändert werden, denn wenn Sie einige Parameter während des Laufens ändern, werden einige interne Variablen zurückgesetzt.

Wenn Sie möchten , dass ich die Formeln für das Smart Lot ändere , lassen Sie es mich wissen , oder wenn Sie möchten , dass ich eine Funktion zur Losgrößenkorrektur für die Pending Orders hinzufüge .

Eine andere Lösung wäre, Pending Buy auf einem Chart und Pending Sell auf einem anderen Chart zu verwenden, aber das wird nicht so praktisch sein.

Bisher hat noch niemand etwas über die Smart-Lot-Funktion gesagt, anscheinend hat sie niemand genutzt oder darüber recherchiert.

Ich denke, Sie wollen so etwas: (nur Buystop-Test, Smart-Lot aktiv, Abnahme der Gewinne auf 10 gesetzt, manuelle Losgröße auf 0,10 gesetzt)


Thank you for your quick response. not that we're talking past each other. in the tester it works exactly like you did in your example. I only use virtual orders, I've noticed that buy stop or sell stop doesn't work. if I set DECREASES ON win e.g. to 5 and lot to 0.10 it should proceed as in the tester 0.10 win - next 0.08 win- next 0.06 win - next 0.04 loose - next 0.10 win - next 0.08...etc... right? he does that in the MT4 tester perfect. but not in live mode with me? Please let the setting DECREASES on win with set 2 with virtual order run on your demo for 1 week and see if it works for you. and let me know again. maybe it's because of my server or something. thanks greetings

Catalin Zachiu  
sebastian0815 #:

Thank you for your quick response. not that we're talking past each other. in the tester it works exactly like you did in your example. I only use virtual orders, I've noticed that buy stop or sell stop doesn't work. if I set DECREASES ON win e.g. to 5 and lot to 0.10 it should proceed as in the tester 0.10 win - next 0.08 win- next 0.06 win - next 0.04 loose - next 0.10 win - next 0.08...etc... right? he does that in the MT4 tester perfect. but not in live mode with me? Please let the setting DECREASES on win with set 2 with virtual order run on your demo for 1 week and see if it works for you. and let me know again. maybe it's because of my server or something. thanks greetings

It made the same thing on tester if the StopLoss was higher than the distance between the orders . Two orders were activated and the lot size modified as they were closed , first in loss and second on win or viceversa , so the lot size was modified randomly , depending on which order closed first . 

I added option for opening only one order at a time for both pending and virtual orders . For pending orders , if one order is activated , the other one is canceled , if using virtual pending orders , if one order is active , the other one will not be opened if the options are set to "true" .

Corrected the "Daily Profit" function .

For the total profit function you can go to the "Account History" tab , right click on any order , then select "All History" . If it's not selected , then the total profit will show only the profit calculated from the period selected in the  "Account History" tab .

sebastian0815  
Catalin Zachiu #:

Dasselbe machte es beim Tester, wenn der StopLoss höher war als der Abstand zwischen den Orders. Zwei Orders wurden aktiviert und die Losgröße beim Schließen geändert , zuerst bei Verlust und dann bei Gewinn oder umgekehrt , also wurde die Losgröße zufällig geändert , je nachdem , welche Order zuerst geschlossen wurde .

Ich habe die Option zum Öffnen von jeweils nur einer Bestellung für ausstehende und virtuelle Bestellungen hinzugefügt. Bei Pending Orders wird, wenn eine Order aktiviert ist, die andere storniert, bei Verwendung virtueller Pending Orders, wenn eine Order aktiv ist, wird die andere nicht geöffnet, wenn die Optionen auf „true“ gesetzt sind.

Die Funktion „Tagesgewinn“ wurde korrigiert.

Für die Gesamtgewinnfunktion können Sie zur Registerkarte "Kontoverlauf" gehen, mit der rechten Maustaste auf eine beliebige Bestellung klicken und dann "Gesamter Verlauf" auswählen. Wenn es nicht ausgewählt ist, zeigt der Gesamtgewinn nur den Gewinn an, der aus dem auf der Registerkarte "Kontoverlauf" ausgewählten Zeitraum berechnet wurde.

I tested it this week and it works very well. thank you very very much. thank you for taking such good care of it. I still have a small question. have you ever thought about adding a trend filter like SMA / EMA ? E.g. the SMA points up then only long would be allowed, the SMA only shows sideways no trades allowed, and points down only short allowed.

might be an idea for future updates
Thank you. greeting

Catalin Zachiu  
sebastian0815 #:

I tested it this week and it works very well. thank you very very much. thank you for taking such good care of it. I still have a small question. have you ever thought about adding a trend filter like SMA / EMA ? E.g. the SMA points up then only long would be allowed, the SMA only shows sideways no trades allowed, and points down only short allowed.

Thank you. greeting

I'll give it a try and see how it goes . Thanks for your suggestion !
mqsato  
Hello,
Will you not develop the MT5 version of Tops Scalper?
I would love to use it.
Catalin Zachiu  
mqsato #:
Hello,
Will you not develop the MT5 version of Tops Scalper?
I would love to use it.
I will try to do it and let you know when it's done . It might take a while , mt5 is more complex than mt4 .
mqsato  
Catalin Zachiu #:
I will try to do it and let you know when it's done . It might take a while , mt5 is more complex than mt4 .
thank you! We are looking forward to the completion!
mqsato  
Hello,

I'm sorry, but let me ask you one more question.
MT4 CPU usage increases outside the trading hours set in "PauseHour" and on weekends.
I'm using it with multiple brokers, but with some brokers, MT4's CPU usage rises abnormally to nearly 100%.
It will return to normal during trading hours, but I would like to reduce the burden on my PC whenever possible.
Are there any countermeasures?
Solo gli utenti che hanno acquistato o noleggiato il prodotto possono lasciare commenti