Posts made by isp00rt

I did it as you suggested but it doesn't work properly yet. This the new structure now:

https://fxdreema.com/shared/oHOYeAtsc

Now all 'pink' things have a 'For Each Trade' above except on blocks 12 and 13. I don't know why but they already work correctly. The problem now is that blocks 48 and 49 are not catching the price levels they should. It is true that no more alien SL levels are taken from other charts. Now they are caught from the current chart, but incorrectly.

I show some examples. As you can see I added a comment block in which I show all relevant SL levels for the EA: the initial one, the one related to the MA and finally the one activated by the trail stop.

First example:

Here the trailing stop value is exactly the same as the MA one. As the trail stop conditions were not met at this point, it should be 0 but I took the wrong value.

Second example:

Similar situation, but in this case the value taken is the initial SL. As in the previous case, it should be 0.

Third example

In this case the trailing stop effectively moves as required (upper red line), but the value caught is still the one corresponding to the MA.

All blocks are functioning correctly except those planned to take the real value of the Trailing stop.

Let's imagine the following scenario:

1. I want to open open several trades in the same direction (let's say buy) one after another every 10 minutes. This I can do.
2. All of them wil have the same SL level price at a fixed pips distance from its open price. All the following ones will have that level or higher, never lower. This I can also do.
3. There will be a Trailing stop that will be common to all trades. This means that it will be activated from the first trade and then, as price moves up, will pull it up. This is what I want.

What I want to do is comparing both Stop levels for each new trade after the first one when opening it. I want to choose the shortest stop level comparing the current trailing stop with the fixed pips level for the new trade.

I know how the Trailing stop block works, but I have no idea how can I catch its price level now in order to do that comparison. Could someone please help?

Thank you in advance.

I don't understand what the blocks on 'On Chart' are suppoesed to do. Are you sure they work correctly on demo?

This EA I'm working with takes a random SL from one chart and then uses it for other charts.

https://fxdreema.com/shared/nievS41Hc

Look at this image:

The bottom trade was the first one to be opened with that stop level. As you can see its SL level was 'caught' I don't know why and then used in other two charts. However the EA worked well in all other charts. This is certainly a bug.

I found the origin of those weird numbers. They are the SL of another trade!!!

Look at this:

The bottom trade was the first one to be opened with that stop level. As you can see its SL level was 'caught' I don't know why and then used in other two charts. However the EA worked well in all other charts. This is certainly a bug. I will copy this message at that subforum too.

Could you please show the final form?

A new version including substantial changes is now available:

https://fxdreema.com/shared/nievS41Hc

Two important features have been added.

1. MA stop and trailing stop are now considered every time a new trade is open.
2. When a trade is opened the most favorable stoop is considered (i.e. the shortest one).

This new structure has solved apparently my previous problems, but new ones have raised up.

Let's see the most serious ones:

1. For reasons I don't understand, trades are not opened because weird numbers are taken for the initial SL after a first round of trades has been closed. Here you have an example of what I mean:

As you can see three different charts are requested to open the same weird SL level!! How can this happen if no terminal variables are used? I have no idea where they come from. This happens the more often the more trades have been opened for the day.

2. On the other hand, some trades are not opened because no indicator value has been available:

This happened repeatedly on a single chart. Why not in any other one?

Could someone please give me a hand on this weird behaviour?

I was wrong sorry. I think your structure should work. I don't know why it doesn't, sorry.

Your comment block is wrongly set. Look at the last example of this page to do it correctly.

https://fxdreema.com/examples#Tips-and Tricks

You are useing the same variable for two different price levels. You should use different variables.

Sorry but what does 'in the wizard' mean?

No suggestions?

Could you please show your current block structure?

I designed a new structure and followed your suggestions. This is the new draft:

https://fxdreema.com/shared/pbesCYnipb

One problem is solved but a new one appeared. Look at this image:

This is a series of 4 consecutive sell trades. The first one is the one whose open price and SL level are considered to condition all subsequent trades. Both levels are put into variables at blocks 26 and 27.

As you can see in the image, the second trade has incorrectly opened its SL level. That means block 34 has been ignored and block 29 has been activated instead of block 47. This situation didn't happen in my previous version. On the other hand, what was wrong in that previous version works correctly now. Apparently the problem simply swapped.

Any suggestion?

Interesting. Could you please share it here?

Just create a variable for it and assign it to each of your trades.

I tried the first way but there's a problem there. Pink blocks are designed to 'load' trade specific data, but not necessarily the one you want. This is specially annoying when opening many trades per chart.

I guess there must be a substantial difference between both blocks, but I can't see what.

I need to capture the opening price and stop loss levels from my trades. The only way I know in fxDreema is by using the (in loop) Trade/Order in loop option at the display. But recently I discovered it can also be taken by using the option (on trade) Event Data.

What's the difference between them?

It doesn't work. I'm afraid I will have to add some custom code to fix it.

Thank you for your help.

Interesting. I'll try it. Thanks a lot.