Posts made by fxDreema

Yes. It's "Trade volume", because it's called like this in the documentation - https://www.mql5.com/en/docs/constants/ ... olume_enum

This error appears after request, I believe. It's not like error that the EA is giving before even trying to communicate with the broker. You can count your requests to the server. I only think that this error has nothing to do with the EA itself

I can check this. But you want to get the lowest/highest daily value, just get the Candle High or Candle Low value

Well, I think this error is self explanatory. I guess you are testing this on live demo account. At least I don't have US30 in my Tester, but I have it as a symbol for live. If the EA can't do something, it woud try again and again, which is probably not the best thing to do in case of such error. But what to do? Learn the limits of your broker and don't break them, this is what sounds to be the right answer.

If there are too many modifications, Trailing STEP can be raised to make them rare.

For the "group" TS, it depends what the initial stops are. If there are no stops they will be created. If they are shorter than STOP... it depends on the option I added lately. But try it. Even I have to try something to remember how it's working. I don't work with this particular block very often. I also tend to be confused about the Trailing Stop stuff even when I'm working with it actively

For pending orders there is OCO option. Try it with a single pending order block to see how it works.

I don't understand the takeprofit and stoploss thing

"Once per minutes" does not snap to :00, it starts counting from the moment it passed the first time. I think I'm gonna add such option. Unless I decide to not add it, because what happens when you want to snap to :00 for 9 minutes period. I mean, 60/9 is not a whole number.
But what solution can I suggest now.. I don't know really

"Indicator is visible", "Indicator appear", "Condition" (indicator > 0). It depends. When you use "Condition", if any of it's operands have value EMPTY_VALUE, the block does not pass and that's why Indicator vs Numeric works.

"Once per bar" can also help - https://fxdreema.com/demo/mt4-once-per-bar

Use "Trace" to check if the buffers are giving you values that can be used, something like this - https://fxdreema.com/demo/mt4-trace-psar

Most arrow indicators have nothing for the current candle, so try with Candle ID = 1 or bigger.

Only for "Indicators (My Indicators)" in "Condition" there are extra options available if you click "More options"

Spread is Ask - Bid. Also available somewhere in Condition - Market properties. In MQL4 you can also use the predefined variables Ask and Bid

Maybe this converter is old. In the past MQL4 was very different than MQL5, but now many things are the same. I often update the code of the blocks and I always try to keep it as same as possible in both, MQL4 and MQL5 versions

Sad. I remember these errors when I was playing with Core Liquidity back then (or whatever the name of the broker was). It looks that they still exists. Is it possible that the use of EA signals the broker to disable trading? I don't know actually. If you didn't had any problems before and now after you started using EAs the problems started, make me know

How stupid am I really... you are asking me for showing indicators, I'm showing you how to hide them. This function actually works at the end of the backtest.

I don't know how to show any indicator while the EA is working. Indicators are used, yes, but they don't appear. Yes, you can manually add any indicator, but I don't know if it's even possible to automatically add them

Look at my example again, block 11. You tend to prefer "If trade" blocks, but I used "No trade"

If you ask me such queston, it means that you don't understand something. I don't want people to copy stuff from here and there thinking that it might work as they expect. I prefer you to understand what is going on, so better ask me if you don't understand something.

"For each Trade" with value 1 set to "Not more than..." only loads the latest running trade, if such exists. Then in the next block I'm checking if the current price (Ask for Buys and Bid for Sells) is above or below the Open Price of that trade. Or I believe that it works that way :))
I used "Chart model", which means that the block will pass if the current price (Ask for Buys or Bid for Sells) is above the open-price (+ Pips away, which is 0 in this case) of the trade, no matter if the trade is Buy or Sell. In the default "Trading model" calculations are mirrored for Sells.

Look, I am a simple stupid guy, my mind is weak. I was answering to question from different people for the last few hours and I'm not finished. I don't remember what happened in my own life yesterday, I can't remember people's problems with details. And I remember that I explained everything about Trailing stops and Break even and I also told you multiple times to put 2-3 blocks in an empty project and try how something works. I'm lost in this topic already. I don't know what "cannot make it work" means at this point. My native language is also not english, so I often misunderstood what people are saying to me. What I can suggest is again, make a very very, I mean very simple EA that has 2-3 blocks and shows the problem, whatever it is. You can make screenshots (Lightshot is amazing program) and show me what exactly is not working. When I see the problem I will fix it in minutes, but if I have to dig into people's projects searching for something that is decribed as "cannot make it work"... I just can't, I surrender.

Block 67 have two MAs inside, it's the default Condition actually. I was thinking that maybe sometimes when you update a block, it doesn't really update. I think this is one of these moments, unfortunately

https://docs.mql4.com/customind/hidetestindicators

This function is used to hide indicators. It does not exists in a block. I was thinking to add it somewhere, but it doesn't exists in MT5 and I don't really want to make more things that work only in MT4 or MT5. At some point I guess I will decide to merge both, so I don't want too many differences

You know... people are often asking me something and then when I see what they are doing it turns out that the problem is something entirely different. Show me something that I can try and see the problem

When you got such an error, try if you can open a trade manually. It's possible that there is a problem with the broker itself and trading is really disabled. What can you do if trading is disabled and the broker refuses to accept even manual trades... nothing

Yes, but Zig-Zag repaints so much that I just don't understand how anyone can work with it. Semafor is similar. What can I say.

You have the options. If you don't understand something, you can ask me how it works. If you think that some option shoud do something, but instead it does something else, then there are 2 reasons for that - 1) You misunderstood the option (probably I used wrong words to describe it) or 2) There is a bug. But if you understand the option correctly and there is no bug, then what is the problem? Maybe the indicator does not work as you expect. Then you can use "Trace" in Visual Mode to see how things are working realtime. I did that, but again, I don't understand those zig-zag indicators.

I decided that it's better to put SL at TrailingStop distance from the average price when a new trade is created

Ok, I believe I fixed the reset.

So, how this block works. Virtual average price is calculated and it depends on the lot sizes. If you have 2 trades with the same lot size opened at levels 10 and 20 for example, then their average price is exactly in the middle - 15. But if one of the trades has bigger lot size, then the average price is closer to that bigger trade. SL is calculated from that price.

When a new trade is opened (or some trade is closed), the average price in the group changes... obviously... because there is new member in the group. If "Reset the stop on new trade" is set, then when a new trade is opened the SL is put at TrailingStop distance from the current price. Now I'm not sure that this is the best behaviour, because it looks that if you open new trades too often the SL line moves away from the current price and it's hard to reach it. But how it should be anyway