TrendTrading EA

[falancak]

v1.23 and v1.24R on demo.

v1.23 has pyramiding disabled; v1.24R with scale-in enabled.

Khalid

Your EA looks impressive.Thanks much.But ı have some additional ideas.

1-Why you dont integrate css indicator strength values to filtrate more trendy pairs.

2-On someway hedge the orders partially on overbought and oversold levels with some indicators that you will estimate better

[falancak]

v1.23 and v1.24R on demo.

v1.23 has pyramiding disabled; v1.24R with scale-in enabled.

Khalid

Your EA looks impressive.Thanks much.But ı have some additional ideas.

1-Why you dont integrate css indicator strength values to filtrate more trendy pairs.

2-On someway hedge the orders partially on overbought and oversold levels with some indicators that you will estimate better

[falancak]

Khalid[/quote]

Your EA looks impressive.Thanks much.But ı have some additional ideas.

1-Why you dont integrate css indicator strength values to filtrate more trendy pairs.

2-On someway hedge the orders partially on overbought and oversold levels with some indicators that you will estimate better

[Radar]

Good evening folks,

We found a couple of bugs that you will have to squash...

If you are running v1.23...

1. Insert this line at line 118 (do not overwrite line 118).

Code: Select all

      if(Volume[0]>1)return; 

2. Copy this line from line 176, and insert at line 251(again, do not overwrite).

Code: Select all

      SLPips = Ask*StopPercent; 

3. Copy this line from line 210, and insert at line 260 (no overwrite).

Code: Select all

      SLPips = Bid*StopPercent; 

4. Edit lines 273 and 300 where they say...

Code: Select all

>= SLPips) 

...and change it to...

Code: Select all

>= SLPips * 2) 

That's it for v1.23.
=========================================================================

If you have v1.24...

1. Insert this line at line 127 (no overwrite).

Code: Select all

      if(Volume[0]>1)return; 

2. Copy this line from line 185, and insert it at line 277 (no overwrite).

Code: Select all

      SLPips = Ask*StopPercent; 

3. Copy this line from line 218 and insert it at line 286 (no overwrite).

Code: Select all

      SLPips = Bid*StopPercent; 

4. Edit lines 299 and 326 where they say...

Code: Select all

>= SLPips) 

...and change it to...

Code: Select all

>= SLPips * 2) 

That's it for v1.24.
==========================================================================

Don't worry, you won't break anything This is where I started... Following coders' instructions on how to make minor fixes.

Have fun!

Radar =8^)

[bazze]

Must say that things are happening very fast here,not much delay
Great people,that's what you are guys

[Radar]

Good evening, guys,

I have created an indicator based on RedZonLINE.mq4 by Khalid.

This one creates Enter/Exit lines at a user-defined distance (in percentage of the range) from the HH and LL.

Version 1.24R of the TrendTrading EA uses this method for entries and exits (along with VolOSC), though the indicator is embedded in the EA (the EA has an extra setting, MinimumRange, for use on M1 to around M30).

If you want to trade this method manually, or just see what the EA uses, throw this on a chart with VolOSC, using the same settings as the EA.

Have fun!

Radar =8^)

[spybreak]

Hi,

I'm up to + 600 pips actually in 8 opened orders

Two bad trades - 165 pips total .
http://www.myfxbook.com/members/cyberom ... ing/908608 (follow trades only since 6/2, close date)
lot 0.05 for all pairs, settings from author for different Length.

I've attached all presets for those who are interested (just change lots according to author or your choice )

I'm waiting now for good exits :
Thanks Khalaad and Radar for this promising EA

And sorry for my 'basic" english :hi:

[spybreak]

- 291 pips this week with my demo:

+ 400 pips in open trades, don't you think this ea needs seriously a Trailing stop ?
thanks

[spybreak]

- 291 pips this week with my demo:

+ 400 pips in open trades, don't you think this ea needs seriously a Trailing stop ?
thanks

Not, in my opinion, unless one pyramids; in which case the stop is moved progressively in the direction of the trade.

But, of course, every one trades differently. Therefore, please attach the DumpHistory script to your charts and PM me the CSV so that we may have the data to design evidence-based trailing stop.

Thank you.

Khalid

I executed the script on chart but after what is the csv you want , OrdersReport.csv ?
Thanks

[Radar]

Hi Stefan,

Could you post a copy of your Experts Log, as I need to see the sequence of events, and the timestamps on the orders and alerts are different, thanks.

Have fun!

Radar =8^)