Posts made by fxDreema

Maybe you ask for point format option in... click on the ? icon on the lower right corner.

http://charts.mql5.com/2/516/sp500u3-h4-mig-bank.png

Huh, when I do "Save As Picture" it uploads it on a link like this http://www.mql5.com/en/charts/763385/sp ... mig-bankSo

So, this is how it should be.

2013.09.14 13:31:17 2013.09.09 00:02 stoploss #SP500U3,H4: modify #1 buy 0.10 #SP500U3 at 1652.30 sl: 1648.06 tp: 0.00 ok
2013.09.14 13:31:16 2013.09.09 00:01 stoploss #SP500U3,H4: modify #1 buy 0.10 #SP500U3 at 1652.30 sl: 1648.04 tp: 0.00 ok
2013.09.14 13:31:16 2013.09.09 00:01 stoploss #SP500U3,H4: modify #1 buy 0.10 #SP500U3 at 1652.30 sl: 1648.02 tp: 0.00 ok
2013.09.14 13:31:16 2013.09.09 00:00 stoploss #SP500U3,H4: modify #1 buy 0.10 #SP500U3 at 1652.30 sl: 1647.99 tp: 0.00 ok
2013.09.14 13:31:15 2013.09.09 00:00 stoploss #SP500U3,H4: modify #1 buy 0.10 #SP500U3 at 1652.30 sl: 1647.97 tp: 0.00 ok
2013.09.14 13:31:15 2013.09.09 00:00 stoploss #SP500U3,H4: modify #1 buy 0.10 #SP500U3 at 1652.30 sl: 1647.95 tp: 0.00 ok
2013.09.14 13:31:15 2013.09.09 00:00 stoploss #SP500U3,H4: open #1 buy 0.10 #SP500U3 at 1652.30 ok

http://fxdreema.com/shared/qt1SxbDEd

On backtest this makes SL to move upwards only when MA goes up, otherwise SL stays untouched.

I don't understand something. This is Buy trade, SL should be below the open price, but it is above. It's true that sometimes I am dumb, but I think normal Buy trade should looks like this:

https://sphotos-b-ord.xx.fbcdn.net/hphotos-prn1/p480x480/12063_558492000849145_1588723552_n.jpg

And you want your SL to be on MA line, which is below that dotted green line, but now it is on the opposite side - above the green line. How is that possible?

Unfortunately markets are closed on my MT4, and I even don't have this instrument, but I backtested on SP500 and it seems to work.

If I don't have initial SL it works like this:
2013.09.14 01:27:45 2013.09.09 00:00 stoploss #SP500U3,H4: modify #1 buy 0.10 #SP500U3 at 1652.30 sl: 1647.79 tp: 0.00 ok
2013.09.14 01:27:45 2013.09.09 00:00 stoploss #SP500U3,H4: open #1 buy 0.10 #SP500U3 at 1652.30 ok

Otherwise, because 55 pips are something very small for this instrument (point format), it works like this:
2013.09.14 01:28:55 2013.09.09 00:00 stoploss #SP500U3,H4: open #1 buy 0.10 #SP500U3 at 1652.30 sl: 1651.75 ok

and there is no trailing stop, because the initial stop is above MA.

I don't understand why you have invalid SL/TP error, I think you have to receive something like "Order is too close to market". And this value 1669.11 is lower than 1688.50... very strange. Is the open price of this trade 1688.50 really? And why it looks that SL of this Buy is above it's open price

Just wondering why do you use such a strange, even wrong project to show something simple. If "Buy now" does not work, it's absolutely enough to have "Buy now" block, and "Just pass" only because it needs to be executed.

"Trailing stop" is not to be placed below "Start trades loop". If you have 20 trades and this makes "Start trades loop" to be executed 20 times in a tick, why do you need to execute "Trailing stop" 20 times in a tick? This blocks construction is not correct.

This works for me on live.

So you still receive error 4002? To be honest, I don't know where it comes, there are no arrays used in trading functions that I wrote, so I think it can be some MT4 fault. What if you restart it?

There is even more - something called "Freeze level", where you can't modify. Here is more about these limits: http://book.mql4.com/appendix/limits . Scalping is not easy

The first project you posted is wrong, because BuySL holds price value and you are using this value as a pips size, so at the end Buy now thinks you want to place SL at 1.314... pips, or whatever the MA value is.

Build 054 is uploaded. Now I'm changing things a bit. Before, if SL/TP are too close or on the opposite side it will give you error 13 and it will stop there.

Now before opening a new trade it checks if SL/TP are too close, and it places them on the minimum available level. For Buy the minimum SL level is Ask-StopsLevel, where StopsLevel depends on the broker and in my broker it is 0, it is measured in points).
If we have SL (or TP) at this minimum price it will go to buy/sell... but I found that sometimes it gives error 130 again. This is probably because of the time delay between SL/TP calculation and the moment when the order is received in the server.

Unfortunately SL/TP levels are send as levels, not as points relative to the open price, so I can't help much about that. We calculate the minimum levels at time X, we send them to the server with delay, and it receives them at time Y, but in this time price can be changed. So what we can do - try again.

I even tested things in Market Execution manner (ECN broker). This is when you send the trade without stops and then you send another command to modify them. Why this is correct in theory? Because when you have Market Execution the trade is opened on the nearest available price, not on Ask/Bid, so at the end the open price can be different than Ask/Bid - and knowing that price you can calculate SL/TP in relation to it. But I tested that and things are the same - there are errors again because of the time delay.

In theory Market Execution is different than Instant Execution (where you must send Ask/Bid price and max Slippage, and it will decide if it's possible to create the trade), but it looks that there is no difference. At least it's good that OrderSend() can now work with stops bigger than 0

I rewrote the trading functions, so now 053 is old... but I got another type ot strange errors that seems to come from the server
Do you have errors when using that EA from the web version?

No, but I will :))

RiseCandles in Indicator Fall block :))) Fixed.

Now Turn ON/OFF blocks are not edited when you change block ID, I know I have to make it happen. By the way block ID's can be text, not only numbers, so you can give unique IDs to be controlled from Turn ON/OFF, but use latin letters only, numbers and "_".

Why don't you just backup the old build by copy it somewhere. All the projects are stored in Data subfolder, and their data size is relatively small. I think it's always better to copy the database itself.

Try this:

"//=== Fractals Setting",true,"//=== Buy/Sell Signal Alert Settings",true,true,true,true,false,"//=== Alert Settings",true,true,true,true,false

That's true for all blocks actually, and I always skip this part with the excuse that I am not native english

I know about this problem, but I was not able to find what causes it, because I never had it on my projects. I can see it on other people's projects, but when you see it it's too late to understand how it started.
I think all the numbers are there, they are just hidden. Can you tell me when this problem started for this project? And how old is this project?
Looking at the code everything seems ok, but I'm probably missing something and I don't know how to replicate this.

That idea of blocks re-numbering is very cool, I'm gonna add it to my to-do list.

I think that these options does not work when virtual stops are used, I have to fix that.

"Manually / Automatic" means that the trade is closed, but not with SL and not with TP, it's just closed manually or with come of the "Close" blocks (OrderClose() function in MQL)
"Undefined" includes all ways of closing - SL, TP, OrderClose() or manually.

This is known as Martingale, and there is a special block for this, you can scroll down and you will find it. All these blocks are like Buy now and Sell now with additions.
In the future I want to add all these money managements inside Buy now and Sell now, but now they are in independent blocks.
I just found that Labouchere blocks don't work, but I will fix that tomorrow

For sure, it's always best if you can simulate something as fast (and accurate) as possible. In my opinion, the main weakness of MT4/MT5 is that it's slow when backtesting and it's pretty hard to find some problem.

By the way currently I'm rewriting most of the trading functions (MQL4/MQL5) and I think I found some possible problem when working with multiple currencies, so if you can do all with a single currency - do it.

I think you need "Check last closed trade profit", as it gets information from the last filtered trade only.
"Check consecutive losses" counts the number of losses happened in a row (looking at the filtered trades, skipping all the others), and it compares them to the desired value.