Dreamliners’ MPAS EAs, Indicators, etc | Page 12 | Forex Factory

Options

Go to
Permalinks
Print Thread

Similar Threads

Dreamliners’ MPAS (Mechanical Price Action Strategy) System 486 replies

MT4 doesn't save trendlines, indicators, etc 1 reply

Quantum leaps in tweaking MT4 (indicators, EAs, etc.) 0 replies

Merc's special Fibonacci trading,in combo w/QQE Gann etc.etc. 7 replies

indicators, etc... 12 replies

Attachments: Dreamliners’ MPAS EAs, Indicators, etc
Exit Attachments

Dreamliners’ MPAS EAs, Indicators, etc

  • #221
  • Jan 5, 2011 3:03am Jan 5, 2011 3:03am
Quoting Chris_B
Can you please explain if it was an opened trade or a pending trade?

The trades are closed with stop orders, not with market orders, so there is a stoploss and a takeprofit already inserted in the trade, when that price is hit the trade has to close...
I was under the impression that the EA would close an open order once a bar is closed and not rely solely on the TP to be hit.

Which it did eventually get hit but on the following bar.

I was assuming that the trade would be closed at the close of the bar using a market order.

Is this correct?
  • #222
  • Jan 5, 2011 3:03am Jan 5, 2011 3:03am
Quoting tommbstone
Ok the alert pop up and email functions work perfect.

so I guess my question now is... will the EA dump/cancel the trade on the new bar if it was never filled. Because I believe that is the way DL trades, each bar has to meet his parameters or no trade.

just wondering

I'm testing the range bar indy 1.4 and with 1.7

what i don't see is the waiting to trade on the side anymore when i changed from other RB script and from MpasEa1.5

anyone else notice that?

I need to just buy the commerical script
You are right....but I tried to eliminate that option in order to let you use Range_Bar_Indi, so at the moment the EA doesn't cancel trades when a new bar is opened because it doesn't check for new Volume anymore.

This was a compromise but I'm noticing it's not correct...

In the meantime I think I found another way to give that instruction to the EA...

The real problem is that RangeBar commercial script and Range Bar Indicator work in a different way...

I will update today
Market is like a puzzle, YOU have to fit the pieces!!
  • #223
  • Jan 5, 2011 3:08am Jan 5, 2011 3:08am
Quoting Musashi
I was under the impression that the EA would close an open order once a bar is closed and not rely solely on the TP to be hit.

Which it did eventually get hit but on the following bar.

I was assuming that the trade would be closed at the close of the bar using a market order.

Is this correct?
No...there is only TargetPrice with a stop order, no market orders are used here...because theoretically we know where the closing price of the bar is.
Anyway if you enable Consider Spread it can happen that when the trade is placed and when the bar is close...the spread is little different..this can cause the trade to not closing exactly at the close of the bar
Market is like a puzzle, YOU have to fit the pieces!!
  • #224
  • Jan 5, 2011 3:13am Jan 5, 2011 3:13am
Quoting Chris_B
No...there is only TargetPrice with a stop order, no market orders are used here...because theoretically we know where the closing price of the bar is.
Anyway if you enable Consider Spread it can happen that when the trade is placed and when the bar is close...the spread is little different..this can cause the trade to not closing exactly at the close of the bar
I think that is exactly what did happen the spread is what caused it not to get filled..
  • #225
  • Jan 5, 2011 3:17am Jan 5, 2011 3:17am
Quoting Chris_B
Here's the new version 1.7...

It's incredible how many details there are to adjust...

Anyway this version fixes all the Zero Divide errors (I hope) and it works even with the Range_Bar_Indi.mq4

I hope all works ok now...
I confirm with v1.7 the zero divide error was fixed and it works with Range_Bar_Indi.mq4.

Excellent programming, Chris!

gary
  • #226
  • Jan 5, 2011 3:23am Jan 5, 2011 3:23am
Quoting Musashi
I think that is exactly what did happen the spread is what caused it not to get filled..

It was a LONG trade or a SHORT trade?
Market is like a puzzle, YOU have to fit the pieces!!
  • #227
  • Jan 5, 2011 3:26am Jan 5, 2011 3:26am
Quoting gms
I confirm with v1.7 the zero divide error was fixed and it works with Range_Bar_Indi.mq4.

Excellent programming, Chris!

gary

As functionality double confirmed I suppose that I have to test with a platform of another broker. Minilots should not be an issue I guess...
  • #228
  • Jan 5, 2011 3:58am Jan 5, 2011 3:58am
Quoting peje
As functionality double confirmed I suppose that I have to test with a platform of another broker. Minilots should not be an issue I guess...
The issue is only on EURUSD?
Market is like a puzzle, YOU have to fit the pieces!!
  • #229
  • Edited 5:12am Jan 5, 2011 4:15am | Edited 5:12am
Quoting Chris_B
The issue is only on EURUSD?
I have been testing on EURUSD and GBPUSD with the same result - no signal, no open order. It is strange because Crodzilla's EA works but a problem is probably just on my site as only I complain now.
..any advices will be appreciated anyway.
  • #230
  • Jan 5, 2011 4:15am Jan 5, 2011 4:15am
Quoting Chris_B
It was a LONG trade or a SHORT trade?
Short trade on GU
  • #231
  • Jan 5, 2011 4:54am Jan 5, 2011 4:54am
Same here, dozens of plotted instantly cancelled orders ????

I delete the volume thing of code, and since i wait

A postive one, it works with my renko/constant ea posted
  • #232
  • Jan 5, 2011 6:32am Jan 5, 2011 6:32am
Chris, I apologize if I'm out of line because I have not looked at your code... but I would recommend using Time[0] to see if there is a new bar instead of volume.

Time[0] is the opening time of the current bar... so if the bar is new... the first tick of the new bar will be a different open time than the previous bar.

This works on the commercial version of the CRB, but don't know about the indicator version.

Pseudo-code:

Inserted Code
init:
old_time = Time[0]

start:
current_time = Time[0]
if (current_time != old_time) {
    a new bar has started.
    old_time = current_time }
  • #233
  • Jan 5, 2011 6:47am Jan 5, 2011 6:47am
Quoting crodzilla
Chris, I apologize if I'm out of line because I have not looked at your code... but I would recommend using Time[0] to see if there is a new bar instead of volume.

Time[0] is the opening time of the current bar... so if the bar is new... the first tick of the new bar will be a different open time than the previous bar.

This works on the commercial version of the CRB, but don't know about the indicator version.

Pseudo-code:

[code]init:
old_time = Time[0]

start:
current_time = Time[0]
if (current_time != old_time) {...

Thank you for your suggestion..I found another solution...if it will not work I will try with your code...

Version 1.8 coming...
Market is like a puzzle, YOU have to fit the pieces!!
  • #234
  • Jan 5, 2011 6:57am Jan 5, 2011 6:57am
New version for all...1.8

I found another solution for cancel pending trades if a new bar opens...hope it works....

Here is a video that demonstrates that the EA works even with Range_Bar_Indi.mq4

Inserted Video
Attached File(s)
File Type: ex4 Mpas_EA_v1.8.ex4   21 KB | 276 downloads
File Type: mq4 Mpas_EA_v1.8.mq4   18 KB | 331 downloads
Market is like a puzzle, YOU have to fit the pieces!!
  • #235
  • Jan 5, 2011 7:55am Jan 5, 2011 7:55am
Thanks thanks for work Chris !

Guys i just wonder if i'm the only one with problem of history after i restart my metatrader with the range indi :


2011.01.05 14:54:04HistoryBase: 227 errors in 'GBPUSD2'
2011.01.05 14:54:02HistoryBase: 227 errors in 'GBPUSD2'
2011.01.05 14:54:01HistoryBase: 227 errors in 'GBPUSD2'


I go to the 1 minute chart and refresh the indi, and the warning stops ?

Strange again
  • #236
  • Jan 5, 2011 8:14am Jan 5, 2011 8:14am
Just got a buy gu @ 1.5511.

So it worksssssssss ! And with my renko expert too, BEAUTIFULL ! Now we have 2 free solutions for constant
  • #237
  • Jan 5, 2011 8:14am Jan 5, 2011 8:14am
Quoting crashout
Thanks thanks for work Chris !

Guys i just wonder if i'm the only one with problem of history after i restart my metatrader with the range indi :


2011.01.05 14:54:04 HistoryBase: 227 errors in 'GBPUSD2'
2011.01.05 14:54:02 HistoryBase: 227 errors in 'GBPUSD2'
2011.01.05 14:54:01 HistoryBase: 227 errors in 'GBPUSD2'


I go to the 1 minute chart and refresh the indi, and the warning stops ?

Strange again
Are you using the correct version of the Range indy?

You have to use the file called Range_Bar_Indi.mq4 (Not Range_Bar.mq4)
Market is like a puzzle, YOU have to fit the pieces!!
  • #238
  • Jan 5, 2011 8:27am Jan 5, 2011 8:27am
Quoting Chris_B
Are you using the correct version of the Range indy?

You have to use the file called Range_Bar_Indi.mq4 (Not Range_Bar.mq4)
Yes Range Bar Indi !
  • #239
  • Jan 5, 2011 8:32am Jan 5, 2011 8:32am
Quoting Chris_B
New version for all...1.8

I found another solution for cancel pending trades if a new bar opens...hope it works....

Here is a video that demonstrates that the EA works even with Range_Bar_Indi.mq4

http://www.youtube.com/watch?v=BOdoI...er_profilepage
thank you for sharing of the video. I have noticed that in my enviroment the EA is added into the graph by dragging immediately without possibilty to see the options as on the picture. What should I do? I am so sorry for lack of experience with the platform..
Attached Image
  • #240
  • Jan 5, 2011 8:49am Jan 5, 2011 8:49am
Quoting peje
thank you for sharing of the video. I have noticed that in my enviroment the EA is added into the graph by dragging immediately without possibilty to see the options as on the picture. What should I do? I am so sorry for lack of experience with the platform..
Double click on ea, don't drag.
0 traders viewing now