Here we discussed very similar EA, see the example at the top: topic/2287

Ah! Its the project expiration date! Sorry! The terminology, "The trial version has been expired!" had me confused and thinking it was something internal to fxDreema. Acutally the project expiration date is something I haven't as yet used anyway.

Thanks for the help - as always!

🙂

Last days I updated the documentation about indicators.
Here: http://fxdreema.com/documentation/getti ... indicators
and here: http://fxdreema.com/documentation/proje ... indicators

Everything starts with the tick, an EA basically works on every tick, on every tick it checks something, it does somethig. No ticks - no actions at all. And when you place blocks under "on Tick", they will be exexuted and they will work. So what blocks to place there?

How to know when EMA5 is below EMA10? There is a "Condition" block for this. Do you need to check this on every tick - then connect other blocks below this one, so there will be nothing above it that will stop it for working on every tick. Do you need to check this condition sometimes, for example on every new bar - then place "Once per bar" above it.

Now that you know when EMA5 is below EMA10... you want to close all trades? There is a block called "Close trades". Just place it below that "Condition". And again, how often do you need that block to be executed? Place conditions or filters above it to make it work only when you want to.

There are very few basics when creating an EA. The first one is what I mentioned - there is an TICK event and the main code is executed on every tick. Because there is no need to do it more often or not so often, market changes because of ticks so ticks rule everything. Then... the EA contains conditions, filters and actions. Filters are basically conditions, so everything is conditions followed by actions, and those conditions are run on every tick.

Tick -> Condition (and filters) -> Actions

Yes, I added this new functionality, but it is for the web version at the moment. I will make new local build when bugs from the last update disappear 😕 They are almost gone.

MetaEditor is much more flexible and you can find support from other programmers in mql4.com and mql5.com 😉

Yes, the limited one can be enough, it is possible even to export whole EA by making it as shared copy. I'm too lazy to check if someone is subscribed or not 😄 I don't know, I don't feel good if I miss someone 🙂

MA3 x< MA5 checks two conditions inside, one of which is MA3 < MA5. If you want to check if one of your block conditions are true and continue, then that crossover condition is not needed there, at least in the example on the right. In this example you can have moments when 1708 will be executed twice per tick because both conditions are true at the same time.

The example on the left.. this separates crossover moments from the general condition (MA3 < MA5) that is true in both conditions. But as you connect outputs to the same block, it is the same as you use only MA3 < MA5.

Here see more about crossovers: viewtopic.php?f=2&t=2290

Yes, use the backtester to see what is going on! That's why they created it.

And in any case, to check if your custom indicator works as expected, check it with "Indicators tester" first. This block should be connected under "on Tick" with some "Pass" block. And it shows the values out of one of the buffers of the selected custom indicator. If it shows normal values (depending on the indicator), it can be used and you will know that it works fine. This is because there are some custom indicators that have buffers, but they have the same value all the time, so the EA can't really use them.

Noooo, with using pink blocks it can be more optimized, if one loop is used for many purposes. The problem is that the number of blocks becomes bigger.
There are loops everywhere - in every blue block, in every brown block, and this is because in MT we can work with multiple trades at once and in order to control them we must select those that we want to work with.

SL and TP are levels in fact, price levels, like 1.3456. There are options to get SL and TP as pips, but sometimes this is not a good idea. If SL as pips is the difference between OpenPrice and StopLoss, then what is SL as pips if after trailing we have our StopLoss on the opposite side of OpenPrice?
But to just check if there is a SL or TP, it is enough to check if they are > 0.

This block resets counter by ID number - see in the properties of this block and also in the counter block that you use. So the reset block is not connected with the counter block directly, it can be placed anywhere around connected with other blocks, it only gives command to clear the counter with given ID. It's like you have a variable that you increment somewhere and you modify it to 0.

I don't remember exactly, but I think that each counter block should have unique ID, but I might be wrong and they probably work as groups - for example to reset more than one counters at once 😕

This is normally for applied price for indicators:
http://docs.mql4.com/constants/prices

Thank you for "Hours filter" update. Now it's easier to set a schedule for each day of the robot 🙂

The idea is to have 2 block chains under "on Tick" like this:

No buys => Check condition to open new Buy => Close all trades (or only sells, but there are no buys anyway) => Create new Buy
No sells => Check condition to open new Sell => Close all trades (or only buys, but there are no sells anyway) => Create new Sell

Depending on the condition "Once per bar" can be used somewhere to speed up the backtesting (actually not checking conditions when there is no need to) or to limit the number of trades in one bar in case you got both conditions within a very short period of time.

Thank you for the chatting but the problems exits further on. I wrote you an e-mail with the following contents:

We have chate together. I have improved and simplified the ea for the optimizing in the tester. The problem that this very simple ea takes a long long time for the optimation prozess exits further on. I have this problem with a lot ea´s that was created with the latest version local version.

After optimationstep 3 the tester has displayed 2:66 hours optimationtime but stops to count higher.

I have canceled the running optimation after 6 minutes and 12 seconds. The optimationtime 180 hours was displayed by the tester:

If I keep running the tester for 60 minutes the optimationtime 1850 hours was displayed by the tester.

Can you please check of errors with the code. I have no answers what it is? I am not a programmer.
😞 😞 😞
I attached the 2 files.

I recommend to use the same group of blocks instead of copy-paste them. I know it feels natural for beginner-programmer to copy-paste things, but this is not a good idea actually. Well, fxDreema is not exactly programming tool and it's not that flexible as the plain code, but the best is if any part of the program exists in one place and if needed it is used multiple times. Using Variables can help with this in general, not in every situation, but if it is possible use the same group of blocks with different parameters 🙂 Even better is to program custom code with all the specific stuff, but this is for someone who knows how to do it 🙂

I can't see partial close here, but otherwise yes - there is some order in blocks execution after all, it depends on block numbers.

Pass block does nothing actually, and that message has nothing to do with blocks. When EA is started it says "Starting" and when the first tick comes it is changed to "Working". In MQL4 language "Starting" shows with init() and "Working" shows with the first execution of start().

Blocks placed under "on Tick" are executed on every tick - again and again and again, maybe few times per second. At least first ones above others. A block, when executed, does what it has to do and it can pass or not depending on what it does (see it's description for information about that).

Some blocks are conditions, others are filters (like "No trade is running")... and filters are conditions on steroids.
Other blocks are actions, like "Buy now", "Sell now", "Close trades" and all the others that do changes somewhere. "Draw arrow" can be also called action block, but it is more for debugging (seeing what is going on).

Connect blocks like this: Conditions, Filters => Actions

If you don't know what some block does, there is an information about it. Hold your mouse over the block in the list, or if you have it as a block - right click and hit "Information".

And what did you tried? What is the actual step that you can't understand?