Posts made by james

Hello again!

I think my previous explanation may have been poor, because I don't think you understood my query. In fact I'm beginning to think I need another block!

Anyway, I'll try to be clearer this time. I've amended and re-shared my example EA here: http://fxdreema.com/shared/MJUi8aI6

This is as far as I seem to be able to take my idea using fxDreema. What's happening is this:

The trade in Area #1 is opening properly, and subsequent trades are being placed when SL > Open Price.

Then the trade loop in Area #2 takes over and adds to the volume, but only for the first trade opened by Area #1. The subsequent trades opened by Area #1 are ignored by Area #2.
[/list:u:rpxj146r]

My question therefore, is this; how do I get the trades loop in Area #2 to work independently and correctly on all trades opened by Area #1?

I'm using local build 059.

As always, grateful thanks.

Hi again. I'm back! Sorry.

I've been struggling with this for many hours, and I wondered if you could advise.

I've made a small example of an EA here: http://fxdreema.com/shared/Wm5YJ3uGd.

My actual EA picks up on a few signals over quite extended periods, so I don't want to miss a signal if another one is still being processed in the trades loop.

I'm trying to do the following:
*
Allow the EA to pick up all new trade signals, without making multiple orders for each one.
Have the trades loop run and create additional trades (add to volume) for each buy without affecting the ability of the EA to pick up new trade signals.[/list:u:mdmfkztz]

Therefore the use of the "Less than "n" trades are running" block is counter-productive since it can stop the EA picking up new trade signals when the trades loop has added to volume (created new trades).

So in my shared example, I'm trying to place a buy on each and every signal, if either there are no trades running, or BuyPrice > SL. Then, in the trades loop, I'd like it to place one additional "add to volume" trade when the "Pips away from SL" blocks are satisfied. There would then be up to three trades running with the same trailing stop loss.

Please help!

Thank you

(I hope I've explained this clearly! My apologies in advance if its confusing.)

I have a query with the "Set 'Current Timeframe' for next blocks" block. Is my understanding correct that if I have it set to, say, current timeframe M1, and repeat and set at M5, that this block and all blocks it is attached to will run twice on the two timeframes?

Sorry for the silly question, but I'm having difficulty confirming it for myself.

Thanks.

Got it now! Thanks again.

OK. Tried that... twice! Still can't see "Just pass" block.

When I try to launch "Create custom blocks" in local 058 I get this:

__Warning: copy(C:/fxDreema_058/Data/FXDB/start_files/MQL4/blocks.list): failed to open stream: No such file or directory in C:\fxDreema_058\Data\generator\studio.php on line 37 Warning: copy(C:/fxDreema_058/Data/FXDB/start_files/MQL4/functions.list): failed to open stream: No such file or directory in C:\fxDreema_058\Data\generator\studio.php on line 41 Warning: copy(C:/fxDreema_058/Data/FXDB/start_files/MQL4/predefined.data): failed to open stream: No such file or directory in C:\fxDreema_058\Data\generator\studio.php on line 44 Failure to create blocks list[/quote:56d1q8ip]

Is it just me, or is the "just pass" block missing in local build 058?

Maybe I need new glasses! 0-0¬

Er... sorry, me again!

I'm getting a compilation error ('MagicStart' - variable not defined). Again I've narrowed it down to just the attached fragment of an EA to help you. The error doesn't show up in build 055.

Does this happen with you?

......
local build 056 magic compile error.mq4

That's great! Glad to know that the fault is on your to do list. I'll work around it for now. And thank you also for the extra bonus! Most generous, and much appreciated by me!

I've narrowed it down to a fault with the blocks on the attached project. It seems to be centred around block No123 in the "on timer" section. If you do a copy -> paste of block 1 in the "on tick" section it will (or it does with me!) do a copy -> cut -> paste instead. Without No123 present, cut -> paste of block 1 seems to work OK.

This was the first indication I saw of the bug, which was then followed by the fault seen in my picture Clipboard01.jpg posted earlier (Sat Sep 28, 2013 11:26 pm).

The history of this project is very long, with a huge number of edits. It is also one where the earlier ID numbering fault appeared, and the ID's became huge numbers. I edited the ID of No123 from some other huge number, and then ran the new "Normalize IDs" function.

Hope this helps you!

......
Copy paste test.mq4

OK. However, when it was in the "on tick" section block 1 in the picture had only one connection. I see local 056 is available. I'll try that.

Yes. This picture shows the strange behaviour I'm talking about.

Block 76 was copied from the "on tick" section to the "on timer" section where it became block number 1 with all sorts of strange connections. On this copy -> paste occasion, block 76 remained in the "on tick" section.

Very strange.

......
Clipboard01.jpg

Hello again!

I'm experiencing some strange behaviour in local version 055. Right click -> copy -> paste does a cut -> paste instead. Do you have the same result?

Thanks again.

Ah. Yes. You did mention this before, and I'm sorry I forgot! However, I still think it would be useful for other users to be reminded that if a numerical system is used with controlling blocks that the numbers will need changed. And probably the best way is to have a small pop-up with a reminder and a "continue" or "cancel" button.

Thanks again.

Hey! Thanks for "Normalize IDs". Much appreciated as some of my numbering was becoming stratospheric!

One small issue arises, though. It messes up "Turn off block" (and presumably other block controlling blocks). Might be worth having a small pop-up asking the user if they wish to continue the action before it is finally executed, as they'll have to manually edit these control blocks afterwards.

Thanks again.

Sounds like you might be going to have a well-earned holiday! Hope its restful!

Yes. I've resolved the short stops. It was the result of the conflict between two EAs running on the same market using the same magic number start. I've decided that I'll use the "Group" option in fxDreema and give all EAs that run on the same market a different group number in the buy/sell, etc., blocks. In this way I'll avoid the problem, and I assume won't even run the risk of a random magic number conflict.

Many thanks again.

Good morning!

I've been running your EA called "stoploss" (from here: http://fxdreema.com/shared/qt1SxbDEd), on the live feed of M1 on US500 (SP500, S&P500), and here are some results:

Experts tab says:
__2013.09.16 11:09:40 stoploss US500.Z,M1: Warning: Too short SL requested (1700.43 or 132 points), minimum will be taken (1700.00 or 175 points)
2013.09.16 11:09:40 stoploss US500.Z,M1: Warning: Too short SL requested (1700.44 or 106 points), minimum will be taken (1700.00 or 150 points)
2013.09.16 11:09:40 stoploss US500.Z,M1: Modify error: Invalid Sl or TP (130). Waiting for a new tick to retry..
2013.09.16 11:09:39 stoploss US500.Z,M1: Warning: Too short SL requested (1700.44 or 131 points), minimum will be taken (1700.25 or 150 points)
2013.09.16 11:09:39 stoploss US500.Z,M1: Warning: Too short SL requested (1700.43 or 132 points), minimum will be taken (1700.00 or 175 points)
2013.09.16 11:07:56 stoploss US500.Z,M1: Operation details: Speed 671 ms
2013.09.16 11:07:56 stoploss US500.Z,M1: modify #33174436 buy 0.10 US500.Z at 1701.50 sl: 1700.00 tp: 0.00 ok
2013.09.16 11:07:55 stoploss US500.Z,M1: Warning: Too short SL requested (1700.42 or 133 points), minimum will be taken (1700.00 or 175 points)
2013.09.16 11:07:51 stoploss US500.Z,M1: Operation details: Speed 703 ms
2013.09.16 11:07:51 stoploss US500.Z,M1: modify #33174436 buy 0.10 US500.Z at 1701.50 sl: 1700.25 tp: 0.00 ok
2013.09.16 11:07:50 stoploss US500.Z,M1: Warning: Too short SL requested (1700.43 or 132 points), minimum will be taken (1700.25 or 150 points)
2013.09.16 11:07:49 stoploss US500.Z,M1: Operation details: Speed 484 ms
2013.09.16 11:07:49 stoploss US500.Z,M1: modify #33174436 buy 0.10 US500.Z at 1701.50 sl: 1700.00 tp: 0.00 ok
2013.09.16 11:07:49 stoploss US500.Z,M1: Warning: Too short SL requested (1700.42 or 133 points), minimum will be taken (1700.00 or 175 points)
2013.09.16 11:07:44 stoploss US500.Z,M1: Operation details: Speed 672 ms
2013.09.16 11:07:44 stoploss US500.Z,M1: modify #33174436 buy 0.10 US500.Z at 1701.50 sl: 1700.25 tp: 0.00 ok
2013.09.16 11:07:43 stoploss US500.Z,M1: Warning: Too short SL requested (1700.43 or 132 points), minimum will be taken (1700.25 or 150 points)
2013.09.16 11:07:39 stoploss US500.Z,M1: Warning: Too short SL requested (1700.42 or 133 points), minimum will be taken (1700.00 or 175 points)
2013.09.16 11:07:39 stoploss US500.Z,M1: Warning: Too short SL requested (1700.42 or 133 points), minimum will be taken (1700.00 or 175 points)
2013.09.16 11:07:21 stoploss US500.Z,M1: Operation details: Speed 390 ms
2013.09.16 11:07:21 stoploss US500.Z,M1: modify #33174436 buy 0.10 US500.Z at 1701.50 sl: 1700.00 tp: 0.00 ok
2013.09.16 11:07:20 stoploss US500.Z,M1: Warning: Too short SL requested (1700.42 or 133 points), minimum will be taken (1700.00 or 175 points)
2013.09.16 11:07:04 stoploss US500.Z,M1: Operation details: Speed 937 ms
2013.09.16 11:07:04 stoploss US500.Z,M1: modify #33174436 buy 0.10 US500.Z at 1701.50 sl: 1700.25 tp: 0.00 ok
2013.09.16 11:07:03 stoploss US500.Z,M1: Warning: Too short SL requested (1700.43 or 157 points), minimum will be taken (1700.25 or 175 points)
2013.09.16 11:07:03 stoploss US500.Z,M1: Modify error: Invalid Sl or TP (130). Waiting for a new tick to retry..
2013.09.16 11:06:40 stoploss US500.Z,M1: Operation details: Speed 1343 ms | Slippage 0.0 pips
2013.09.16 11:06:40 stoploss US500.Z,M1: open #33174436 buy 0.10 US500.Z at 1701.50 ok
[/quote:1rqczxe9]
Journal says:
__2013.09.16 11:09:40 '58032744': modification of order #33174436 buy 0.10 US500.Z at 1701.50 sl: 1700.00 tp: 0.00 -> sl: 1700.25 tp: 0.00 failed [Invalid S/L or T/P]
2013.09.16 11:09:40 '58032744': modify order #33174436 buy 0.10 US500.Z at 1701.50 sl: 1700.00 tp: 0.00 -> sl: 1700.25 tp: 0.00
2013.09.16 11:07:56 '58032744': order #33174436 buy 0.10 US500.Z at 1701.50 was modified -> sl: 1700.00 tp: 0.00
2013.09.16 11:07:55 '58032744': request in process
2013.09.16 11:07:55 '58032744': request was accepted by server
2013.09.16 11:07:55 '58032744': modify order #33174436 buy 0.10 US500.Z at 1701.50 sl: 1700.25 tp: 0.00 -> sl: 1700.00 tp: 0.00
2013.09.16 11:07:51 '58032744': order #33174436 buy 0.10 US500.Z at 1701.50 was modified -> sl: 1700.25 tp: 0.00
2013.09.16 11:07:50 '58032744': request in process
2013.09.16 11:07:50 '58032744': request was accepted by server
2013.09.16 11:07:50 '58032744': modify order #33174436 buy 0.10 US500.Z at 1701.50 sl: 1700.00 tp: 0.00 -> sl: 1700.25 tp: 0.00
2013.09.16 11:07:49 '58032744': order #33174436 buy 0.10 US500.Z at 1701.50 was modified -> sl: 1700.00 tp: 0.00
2013.09.16 11:07:49 '58032744': request in process
2013.09.16 11:07:49 '58032744': request was accepted by server
2013.09.16 11:07:49 '58032744': modify order #33174436 buy 0.10 US500.Z at 1701.50 sl: 1700.25 tp: 0.00 -> sl: 1700.00 tp: 0.00
2013.09.16 11:07:44 '58032744': order #33174436 buy 0.10 US500.Z at 1701.50 was modified -> sl: 1700.25 tp: 0.00
2013.09.16 11:07:44 '58032744': request in process
2013.09.16 11:07:43 '58032744': request was accepted by server
2013.09.16 11:07:43 '58032744': modify order #33174436 buy 0.10 US500.Z at 1701.50 sl: 1700.00 tp: 0.00 -> sl: 1700.25 tp: 0.00
2013.09.16 11:07:21 '58032744': order #33174436 buy 0.10 US500.Z at 1701.50 was modified -> sl: 1700.00 tp: 0.00
2013.09.16 11:07:21 '58032744': request in process
2013.09.16 11:07:21 '58032744': request was accepted by server
2013.09.16 11:07:21 '58032744': modify order #33174436 buy 0.10 US500.Z at 1701.50 sl: 1700.25 tp: 0.00 -> sl: 1700.00 tp: 0.00
2013.09.16 11:07:04 '58032744': order #33174436 buy 0.10 US500.Z at 1701.50 was modified -> sl: 1700.25 tp: 0.00
2013.09.16 11:07:04 '58032744': request in process
2013.09.16 11:07:04 '58032744': request was accepted by server
2013.09.16 11:07:03 '58032744': modify order #33174436 buy 0.10 US500.Z at 1701.50 sl: 0.00 tp: 0.00 -> sl: 1700.25 tp: 0.00
2013.09.16 11:07:03 '58032744': modification of order #33174436 buy 0.10 US500.Z at 1701.50 sl: 0.00 tp: 0.00 -> sl: 1700.43 tp: 0.00 failed [Invalid S/L or T/P]
2013.09.16 11:07:03 '58032744': modify order #33174436 buy 0.10 US500.Z at 1701.50 sl: 0.00 tp: 0.00 -> sl: 1700.43 tp: 0.00
2013.09.16 11:06:40 '58032744': order was opened : #33174436 buy 0.10 US500.Z at 1701.50 sl: 0.00 tp: 0.00
2013.09.16 11:06:40 '58032744': request in process
2013.09.16 11:06:40 '58032744': request was accepted by server
2013.09.16 11:06:40 '58032744': instant order buy 0.10 US500.Z at 1701.50 sl: 0.00 tp: 0.00
[/quote:1rqczxe9]
My observations:
*the trailing SL seems to go up and down (why?);
the modify errors are to expected on an SL based on a MA, and in normal trading wouldn't occur due to other price filters.[/list:u:1rqczxe9]

In addition:
__2013.09.16 11:03:52 stoploss US500.Z,H1 inputs: inpstd="-= System =-"; MagicStart=2007; ECNbroker=false;
[/quote:1rqczxe9]
*I don't seem to have an input "ECNbroker" in my EA generated on local build 054;
MagicStart - see next paragraph![/list:u:1rqczxe9]

Phew! I'm going through a STEEP learning curve! After thinking about the errors I was seeing, and doing some more hunting around the web I found some information about running multiple EAs on the same index. I now understand that the Magic Start Number should be different for each EA, otherwise there will be conflict. This would explain my misleading picture in my post of Sat Sep 14, 2013 12:02 am where the buy SL appears to be above the price! Sorry! I was running two EAs on US500, and they both had the same Magic Start Number.

This leads me on to the next two queries, which I wasn't able to absolutely confirm on the web:
*do you know, when running two EAs on the same index/currency pair/whatever, if it is sufficient to have the magic start number of the first set at say 1234, and the second at say 1235, i.e. just one above?
do you think that, even with very different magic start numbers, it would be safer to build both EAs into one, and use the Group function of fxDreema instead?[/list:u:1rqczxe9]

So, just to summarise the above:
*why does the trailing SL seem to go up and down?
I don't seem to have an input "ECNbroker" in my EA generated on local build 054;
any tips on how best to use magic start numbers?[/list:u:1rqczxe9]

I'm so sorry to have wasted your time. Please accept my apologies.

Thanks again for the quick reply.

I'm not using the File/Save As option in MT4 to get a picture. I'm screen copying into IrfanView, and saving this file onto this forum. And no, you are not dumb! I promise! If either of us is, its me! My picture in my post Sat Sep 14, 2013 12:02 am is misleading. Sorry.

Anyway, it doesn't matter as I think there may be some progress.

I've back tested your EA from http://fxdreema.com/shared/qt1SxbDEd (date range 2013.05.06 to 2013.05.08 on the SP500) and it runs fine, just the way I expected. I then checked mine again, made a couple of edits and made a new link: http://fxdreema.com/shared/0G2DBNfbd. It also back tests perfectly over this time.

So now I think we are both on the same track!

Therefore, when the markets open, I'd be very grateful if you would put both yours and mine onto a live feed to see if the stop losses get set correctly at the 55 day EMA. I'll do the same here.

Many thanks, again.

Hi again, and thanks for the reply.

I agree that back testing on SP500 (S&P500, US500 are all the same index) works fine. Its running on the live feed that is the issue. From what I can work out, the broker, Alpari, allows anything down to a 2 pip stop loss on this.

Actually, if you look carefully at the picture of my chart, the price is just above the SL on it. As I said, the EA managed to move the SL twice during many attempts, and the SL got very close to the current price. The SL isn't above the current price. This is what it managed just before I stopped the EA:
__2013.09.13 21:35:38 US500 TrendFollow 2PointFormat type 1 v2 US500.U,M1: modify #33169429 buy 10.37 US500.U at 1688.50 sl: 1688.75 tp: 0.00 ok
[/quote:kazcf2bp]
As you see, a very close stop, way above the 55 day EMA, and just below the current price of 1689.25.

So, just to re-cap, on the live feed...
*the "Buy now" block with a 55 pip SL seems OK, but not if a dynamic price is used;
the "Trailing stop" set to "Dynamic value" with a price loaded into variable BuySL seems not to work;
but "Dynamic value" for both blocks work fine on the back tester.[/list:u:kazcf2bp]

Do you think these two blocks set to "Dynamic value" should work in this way, or not? If not, how to I set a stop loss and trailing SL at the 55 day EMA?

I'm afraid it still isn't working for me, and I am using local build 054.

Take a look at http://fxdreema.com/shared/M7Rosd5rb. Its the same EA as before, edited.

Block 8 updates the variable BuySL with the price of the 55 day EMA, and block 7 is the trailing stop block which uses a "Dynamic level" to set a stop loss at the price held in BuySL.

Now take a look at the picture of MT4 on a live feed:

The solid red line at the bottom is the 55 day EMA, well below the current price. The dotted red line is one of only two successful attempts over many attempted placings of the SL, and is as close to the price as possible, but not where I want it!

Experts tab says:
__2013.09.13 21:59:15 US500 TrendFollow 2PointFormat type 2 v1 US500.U,H4: Modify error: Invalid Sl or TP (130). Waiting for a new tick to retry..
[/quote:3n862o2e]
Journal tab says:
__2013.09.13 21:59:15 '58032744': modification of order #33169429 buy 10.37 US500.U at 1688.50 sl: 1688.75 tp: 0.00 -> sl: 1669.11 tp: 0.00 failed [Invalid S/L or T/P]
[/quote:3n862o2e]
It seems to me that even if the "Dynamic level" in the trailing stop block was setting a pips stop loss and not a price stop loss, the figure in this case would be a 1669.83 pips stop loss. So where its getting its stop loss from I just don't know.

You'll notice that the "Buy now" on the EA uses a fixed pip SL of 55. Therefore the errors are related to what's happening in the trade loop. It seems to me that the "Dynamic level" bit isn't working correctly. Somehow the broker's server doesn't get the correct instruction.

Have I done something wrong? This should work, shouldn't it?

If I do have it wrong, how do I place a stop and then run a trailing stop, both at the 55 day EMA price?

......
Clipboard02.jpg