Solo gli utenti che hanno acquistato o noleggiato il prodotto possono lasciare commenti
Alexandru Casian  
Rollover Scalper version 1.1 release notes
Release date: 3 May 2022
What's new:
  • "use_risk_per_trade" option added to dynamic lot size (as requested by customers).
    E.g. if you set the "risk per trade in %" parameter to "5" while having 1000$ on account and using "700" safety SL (~7$/0.01 lot), the lot size used will be 0.07 because by having a 49$ SL (7$*7) you indeed risk only 5% of your account.

  • "grid" option added (as requested by customers).
    All grid orders have the same SL and the same TP (which can be trailed).
    If you use the grid, the "Move the entry point with MA?" parameter is ignored and therefore the entry point will remain fixed.
    P.S. my subjective opinion is that, the EA is good as it was originally thought to be (without grid). Yet, it is useful to have the option to play around with the grid strategy on backtests. All sets I send do NOT use grid.

  • "Pause trading after a specific big loss?" option added.
    You can now minimize the drawdown caused by important news like pandemics or wars, news which affect the market for many days but can't be seen in an economic calendar. All you have to do is set the loss at which to pause trading, and the number of days to pause trading. Keep in mind that the loss is per trade is used to trigger the pause, not the drawdown per balance.
    Once the pause is triggered, you'll see it on the Info panel (if "Show info panel?" parameter is set to true).

  • StdDev (standard deviation indicator) parameters can now be seen and changed from EA’s settings.

  • The "Use every tick?" parameter was removed as it was no longer. Since build 1.1, the EA always does checks and calculations each tick during trading hours, and only each 5 minutes when idle (during non-trading hours). The goal is to improve the live trading results by minimizing the effects created by ping, network interrupts, too high CPU usage etc., and by making live trading results more similar to backtesting or other live accounts. In version 1.0 there was sometimes a big difference in trades taken on different live accounts (same set would behave differently). Now it's less likely to happen, and the only reasons for that to happen are not related to the EA (these reasons being slippage, ping, different servers etc.).

  • Fixed a bug in the MT5 version which wouldn’t close trades after the closing period time (4AM in default sets). The bug was present and could be seen in both live trading and backtesting results, and therefore the backtesting results were showing the real results.
You can find more details on that in the documentation for v.1.1 once I send it to you (in case you bought the EA).
Wan Suryolaksono  
Thank you for your new update. I'm very happy for your hard work and very careful development process so that I can use this EA without worry for a long time
Alexandru Casian  
Iwan Suryolaksono #:
Thank you for your new update. I'm very happy for your hard work and very careful development process so that I can use this EA without worry for a long time

Thank you for your feedback, it motivates me continue perfecting the EA.

UlrichG  

Hi Alexandru,

I am testing the RolloverScalper on MT5 VPS and get the following messages in the log:

2022.07.27 13:40:54.692    Rollover Scalper EA MT5 (GBPUSD,M5)    cannot load indicator 'Moving Average' [4302]
2022.07.27 13:40:54.692    Rollover Scalper EA MT5 (GBPUSD,M5)    cannot load indicator 'Standard Deviation' [4302]

On one server they come repeatedly every 10 sec, on another server this  stops and ther come the following messages:


2022.07.11 22:55:40.731    Rollover Scalper EA MT5 (GBPUSD,M5)    CTrade::OrderSend: buy limit 7.47 EURCHF at -1.00504 sl: -1.01204 tp: 1.00457 [invalid price]
2022.07.11 22:55:40.731    Rollover Scalper EA MT5 (GBPUSD,M5)    CTrade::OrderSend: buy limit 7.47 EURAUD at -1.00504 sl: -1.01204 tp: 1.00457 [invalid price]
2022.07.11 22:55:40.731    Rollover Scalper EA MT5 (GBPUSD,M5)    CTrade::OrderSend: buy limit 7.47 USDCHF at -1.00504 sl: -1.01204 tp: 1.00457 [invalid price]

There no such messages in the journal of the terminal befor synchronizing. The named indicators are installed on my terminal:


I limited the "max bars in chart" to 50000 in the settings.

What may go wrong?


Sincerely Ulrich


P.S.

I really appreceate your informative and clear hints on the telegram channel!

Alexandru Casian  
UlrichG #:

It seems that you haven't updated the EA to the latest version (1.2). This error was happening sometimes in the previous versions but I fixed it completely in the latest version.

UlrichG  
Alexandru Casian #:

It seems that you haven't updated the EA to the latest version (1.2). This error was happening sometimes in the previous versions but I fixed it completely in the latest version.


It is the actual version 1.2

Alexandru Casian  
UlrichG #:

It is the actual version 1.2

You're right, I just saw the date from your older error, my bad, I thought all the errors are from the same day.

The quick answer: ignore them all, the EA already solved the problem.

The long answer:
So, you have 2 types of errors:
a. 3  [invalid price] errors from 2022.07.11 22:55:40.731. This were caused because you were using at that moment the older version of EA (the latest (1.2) version wasn't even published then). So we can ignore that error because it can't happen anymore.
b. 2 "cannot load indicator" errors from 2022.07.27 13:40:54.692. This error is shown when you load the EA on the chart and there is an error loading the indicator. This happens because the EA tries to load the indicator when it isn't yet ready. HOWEVER, the EA won't ignore it and instead will try again and again till the indicator is ready to be loaded. The fact that you got that error only once (once for each of the 2 indicators) means that it succeeded the 2nd try. If you'll read the logs you'll see there are new logs which show no error. Keep in mind that you wouldn't see them if the problem wouldn't have been solved. The EA won't proceed to the next steps if it didn't succeeded in loading all indicators for all symbols. The fact that you have new logs (with no errors) means that everything is ok. Even the fact that you have the Info Panel on the chart indicates that the EA was initialized successfully, otherwise you wouldn't see the Info Panel on the chart.
UlrichG  
Alexandru Casian #:
You're right, I just saw the date from your older error, my bad, I thought all the errors are from the same day.

The quick answer: ignore them all, the EA already solved the problem.

The long answer:
So, you have 2 types of errors:
a. 3  [invalid price] errors from 2022.07.11 22:55:40.731. This were caused because you were using at that moment the older version of EA (the latest (1.2) version wasn't even published then). So we can ignore that error because it can't happen anymore.
b. 2 "cannot load indicator" errors from 2022.07.27 13:40:54.692. This error is shown when you load the EA on the chart and there is an error loading the indicator. This happens because the EA tries to load the indicator when it isn't yet ready. HOWEVER, the EA won't ignore it and instead will try again and again till the indicator is ready to be loaded. The fact that you got that error only once (once for each of the 2 indicators) means that it succeeded the 2nd try. If you'll read the logs you'll see there are new logs which show no error. Keep in mind that you wouldn't see them if the problem wouldn't have been solved. The EA won't proceed to the next steps if it didn't succeeded in loading all indicators for all symbols. The fact that you have new logs (with no errors) means that everything is ok. Even the fact that you have the Info Panel on the chart indicates that the EA was initialized successfully, otherwise you wouldn't see the Info Panel on the chart.

Thanks for your quick and deligent answers, but the errors keep repeating every 10 sec on the VPS:

2022.07.27 15:28:30.227    Rollover Scalper EA MT5 (GBPUSD,M5)    cannot load indicator 'Moving Average' [4302]
2022.07.27 15:28:30.228    Rollover Scalper EA MT5 (GBPUSD,M5)    cannot load indicator 'Standard Deviation' [4302]
2022.07.27 15:28:30.228    Rollover Scalper EA MT5 (GBPUSD,M5)    [-] RolloverScalper: Error initializing the MA indicator for pair EURAUD... trying again in 10 seconds.
2022.07.27 15:28:40.228    Rollover Scalper EA MT5 (GBPUSD,M5)    cannot load indicator 'Moving Average' [4302]
2022.07.27 15:28:40.228    Rollover Scalper EA MT5 (GBPUSD,M5)    cannot load indicator 'Standard Deviation' [4302]
2022.07.27 15:28:40.228    Rollover Scalper EA MT5 (GBPUSD,M5)    [-] RolloverScalper: Error initializing the MA indicator for pair EURAUD... trying again in 10 seconds.

The screenshot was from my desktop, where everythig runs smooth (the backtests with HF3 are amazing!). The VPS from MQL5 has no screen ;-). The errors jus occur on the VPS, not on desktop.

 The CPU load of VPS shows 0%, memory used 144 MB, on disk 410 MB used. Other EAs run on that VPS, even in parallel with RolloverScalper. The errors occur also if RolloverScalper is the only one on the VPS. Please double check, I can send you logfiles etc as you need (shall we proceed as PM?)

And: Yes, you are right, the "Invalid Proce" errors came from the old version.

Alexandru Casian  
UlrichG #:

Thanks for your quick and deligent answers, but the errors keep repeating every 10 sec on the VPS:

2022.07.27 15:28:30.227    Rollover Scalper EA MT5 (GBPUSD,M5)    cannot load indicator 'Moving Average' [4302]
2022.07.27 15:28:30.228    Rollover Scalper EA MT5 (GBPUSD,M5)    cannot load indicator 'Standard Deviation' [4302]
2022.07.27 15:28:30.228    Rollover Scalper EA MT5 (GBPUSD,M5)    [-] RolloverScalper: Error initializing the MA indicator for pair EURAUD... trying again in 10 seconds.
2022.07.27 15:28:40.228    Rollover Scalper EA MT5 (GBPUSD,M5)    cannot load indicator 'Moving Average' [4302]
2022.07.27 15:28:40.228    Rollover Scalper EA MT5 (GBPUSD,M5)    cannot load indicator 'Standard Deviation' [4302]
2022.07.27 15:28:40.228    Rollover Scalper EA MT5 (GBPUSD,M5)    [-] RolloverScalper: Error initializing the MA indicator for pair EURAUD... trying again in 10 seconds.

The screenshot was from my desktop, where everythig runs smooth (the backtests with HF3 are amazing!). The VPS from MQL5 has no screen ;-). The errors jus occur on the VPS, not on desktop.

 The CPU load of VPS shows 0%, memory used 144 MB, on disk 410 MB used. Other EAs run on that VPS, even in parallel with RolloverScalper. The errors occur also if RolloverScalper is the only one on the VPS. Please double check, I can send you logfiles etc as you need (shall we proceed as PM?)

And: Yes, you are right, the "Invalid Proce" errors came from the old version.

You have the EURAUD pair disabled in the Market Watch. I mentioned a few weeks ago this error on the telegram channel and showed screenshots how to fix it.
The MT5 installer comes from some brokers with most symbols disabled. The EA won't be able to trade them and you have to enable them.In fact, the EA can't even load the indicator (in this case for EURAUD) because it's disabled, that's why the error keeps appearing.

I PMed you the link to the solution.
UlrichG  
Alexandru Casian #:
You have the EURAUD pair disabled in the Market Watch. I mentioned a few weeks ago this error on the telegram channel and showed screenshots how to fix it.
The MT5 installer comes from some brokers with most symbols disabled. The EA won't be able to trade them and you have to enable them.In fact, the EA can't even load the indicator (in this case for EURAUD) because it's disabled, that's why the error keeps appearing.

I PMed you the link to the solution.

I Got news on this issue:

At first I want to thank Alexandru for is quick and intensive dialog with me.

Second: It was not a configuration problem caused by me, all symbols and the config if MT5 and RolloverScalper were OK.

But there is an issue with MT5: These messages [4302] can occur although you have the named symbol in your market watch, if you never loaded a chart with it to your terminal!

So there is a workaround, if you have the complained symbol on your market watch and the message [4302] appears in the log of your MQL5 VPS (and not on the desktop!), just load a chart with the complained symbol to your terminal and then press "migrate" to synchronize the VPS with your desktop. you can even close the chart and migrate again, it still works.

Uff, this was heavy stuff, I go to bed now.

Alexandru Casian  
UlrichG #:

I Got news on this issue:

At first I want to thank Alexandru for is quick and intensive dialog with me.

Second: It was not a configuration problem caused by me, all symbols and the config if MT5 and RolloverScalper were OK.

But there is an issue with MT5: These messages [4302] can occur although you have the named symbol in your market watch, if you never loaded a chart with it to your terminal!

So there is a workaround, if you have the complained symbol on your market watch and the message [4302] appears in the log of your MQL5 VPS (and not on the desktop!), just load a chart with the complained symbol to your terminal and then press "migrate" to synchronize the VPS with your desktop. you can even close the chart and migrate again, it still works.

Uff, this was heavy stuff, I go to bed now.

That's indeed more complicated stuff. It seems to be a MQL5 VPS only related issue, because on locally installed MT5 terminals (or on non-MQL5 VPS) you don't have to load all charts.
Anyways, I'm glad you managed to solve the problem and thank you for sharing the solution!
rvcarnei  
Hi, may I have MF set file? 
Alexandru Casian  
rvcarnei #:
Hi, may I have MF set file? 
Hi! I answered you in private
UlrichG  
UlrichG #:

I Got news on this issue:

At first I want to thank Alexandru for is quick and intensive dialog with me.

Second: It was not a configuration problem caused by me, all symbols and the config if MT5 and RolloverScalper were OK.

But there is an issue with MT5: These messages [4302] can occur although you have the named symbol in your market watch, if you never loaded a chart with it to your terminal!

So there is a workaround, if you have the complained symbol on your market watch and the message [4302] appears in the log of your MQL5 VPS (and not on the desktop!), just load a chart with the complained symbol to your terminal and then press "migrate" to synchronize the VPS with your desktop. you can even close the chart and migrate again, it still works.

Uff, this was heavy stuff, I go to bed now.

Correction: You have to place any EA on the chart to make the MQL5 VPS load it once. So you have to do the following if you are using MQL5 VPS together with Rollover Scalper (and some other Multicurrency EAs I expect):

1. Open one chart for every pair that you have in the "Pairs to trade" list

2. place any EA on every chart (with e.g. 0.01 lot size or a dummy EA that does not really trade) to make MQL5 VPS load the chart

3. Press "Migrate" on the VPS tab of MT5 Desktop terminal

4. Close the additional charts again (leaving just the one chart GBPUSD M5 chart with Rollover Scalper)

5. press "migrate" again

This lets MQL5 VPS "know" the needed pairs so the messgae [4302] will not come anymore. I know this sounds weird, bit it helps relyably in those casesu
Alexandru Casian  
UlrichG #:

Thanks a lot Ulrich! Your previous message (from 29th July) already helped some people and this one will be helpful too.

1718465  
Alexandru Casian #:
The set #1 (for 6 best pairs, GBPUSD,EURUSD,EURCHF,EURAUD,USDCHF,AUDUSD), for MT5.
Hello, don't know where to talk to you. Just rent the ea for the month to try. Can you give me details for telegram and ea please! Thabk you
1718465  
Hello, just rent the ea for a month to test it.

Can i have details for the ea and telegram please.

Thank you
Alexandru Casian  
1718465 #:
Hello, don't know where to talk to you.

Hi! Just PM me on MQL5, that's how everyone else is doing.
I sent you the link to the telegram channel in PM.

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