Posts made by fxDreema

Once per bar passes one time per bar. Start trades loop self-executes as many times as many trades there are. Once per bar, sonnected after Start trades loop limits it to the last trade only.

If I'm not missing something, I think this will work:

Condition - Once a day - Start trades loop - (in loop) Modify

This is modifying stops once a day when some condition occurs.

Done... but in web version (local version later)

This works on live only, but not in backtest. At least this is the behaviour of the native MQL4 "Sleep()" function, otherwise .dll function can be used to create real delay, and this can be useful... I will check what I can do about this now.

Pips away from SL - this means the difference between the current price and SL.
For buy -> Ask-SL, for sell -> SL-bid.
For % of SL option, SL size is calculated as the difference between SL and Open Price.
55% of SL, if OP-SL is 100 pips, this is 55 pips. But initially the trade is 100% pips away from SL, so this block will pass every time if Ask is 55 pips above SL, and it does that and the EA produces 3 trades in one shot.

My idea for this block was to be able to build custom trailing stop with it, because in trailing stop the difference between the current price (Ask or Bid, depending on trade type) and SL. But I think you should use Pips away from open price or at least use value bigger than 100% for that option (% of SL).

By the way, this Once per bar (block 7) limits the loop to work with only the newest trade once per bar. But in the loop block it can be also told to work with the newest trade only, all the time (setting the last option to 1)

The last problem was that .ex4 file cannot be read... for whatever reasons. Try to compile this indicator from .mq4 file with MetaEditor that belongs to the installed MetaTrader.

Well, you can always check the number of trades before opening new one. Find "Check trades count". The basic structure of every EA is that on every tick it checks some conditions and depending on them it take some actions. Checking trades count is also a condition (or filter).

I see things like:
KL 2 20:13:28 Tester program file Indicators\Heiken_Ashi.ex5 read error

HH 2 20:13:42 Custom Indicator loading of Heiken_Ashi EURUSD,M1 failed

And it works for me... but too many positions.

Moving average is trend indicator, stochastic is oscillator. Moving average has values that depends on the price and on the market, stochastic is in between 0 and 100. Both indicators are from different nature, they have very different values, these cannot be crossed.

Well, meanwhile I fixed some things, now it uploads this indicator with 5 buffers. Buffer #4 (last one) is the one that is used for color.

The number of digits is something different than minimum lot. Every bloker has minimum lot that you can send, and in your case it's probably 0.1. You can actually try to send 0.01 lot manually... it should be impossible, I think.

"pips" uses the point format defined in options, so it depends.
search for "double toPips", I can tell where exactly it is located because what functions to be used inside the project depends on the project itself - only the ones needed are places in the code.

Yes, twice. But it will take effect on all places where timeframe is defauld - Current.

I can see what you are trying.

You don't need to use "AND" block at all, this block is to make parallel blocks to behave as serial, but it's much better to just connect them one after another.

Then, under "on Tick" blocks are executed on every tick, and every block does what it has to do once. "Sell now" creates a new trade, and goes to the next blocks... but next blocks are executed only once, after the sell trade is created.

There are many ways to do this, but this can do the trick: http://fxdreema.com/shared/P2Wh31uac

EAs are to be used from "/experts" folder, indicators are read from "experts/indicators", scripts (one-shot EAs) from "experts/scripts". For MT5 is similar, but these folders are in "/MQL5".

Yes, and if you choose buffer #4 you will see 0 and 1 around candles

It's also true that I have to update custom indicators system. I tried this Heiken ashi and it's not imported very well in fxDreema, but I will tell you how to do it. When you upload it, write 5 for number of buffers (it shows 1). Then, name buffers something like this:

Open
High
Low
Close
Color (0=Blue, 1=Red)

The last buffer (4) describes the color, and use Condition to check what is the color. ==0 for blue and ==1 for red candle. Other buffers (0,1,2 and 3) are for all the candle parts, obviously.

In this situation my responce is to try "Levels tester" block, because this block shows you how values are changing in time, it's something like indicator for indicators. I made it as a tool to check custom indicator buffers, because sometimes they behave weird or not working at all... it depends how the indicator is programmed. Then, when you know what your custom indicator gives to the EA, you will be able to work with it.

You can check these indicators with "Levels tester" and if both of them are showing lines then they can be crossed. Otherwise... bad luck

There is a block named "Indicator is visible" who probably can detect whether some indicator "is red" or "is blue". Red and Blue are just colors, but EAs and indicators works with digits, so you should find the buffer that represents this red color and the one that represents the blue one.

This block is to check if the indicator is above/below some limits for more than one candle. To check the current indicator value or it's value for older candle, use Condition. Blocks does not return something, they just pass if what they are supposed to do is true. By "pass" I mean that the orange output is active and next block(s) is executed right after this one, which in MQL language means that the function of one block calls the function of the next block

I think this is related to MetaTrader, because MetaTrader tells the EAs what to do, but you can also check logs if there is error message from any of these EAs?