Fmfx auto-trader. Another new toy by Steve Hopwood

[Fmfx]

First trade on a live acc, currently BE +5

[Fmfx]

Having the RSI Function enabled will help filter out bad signals, just like the picture below. RSI < 45

[gaheitman]

I don't think changing the "OnlyTradeCurrencyTwice" setting to true has helped. There was a good AUDUSD entry signal (see below) but no trade opened.

audusd.gif

Not sure if it matters, but you don't seem to be using the latest version. Your version still has the separate start time printing in the display.

George

I've checked against the EA in post 1 and you're right, the only difference is the start time is removed.

Just out of curiosity, did you get the AUDUSD trade I referred to above or aren't you running the EA currently?

Sorry, I am not running the ea.

George

[wynkins]

First trade on a live acc, currently BE +5

What settings did you settle on for live trading?

[Fmfx]

First trade on a live acc, currently BE +5

What settings did you settle on for live trading?

It is the last set file i posted, for audusd 1H, and also check that of nzdusd 1H. When we get the update version i will post set for other pairs.

Regards

[jjgengis]

Hi,

I noticed high instability of the EA at lotsize < 1 :

fmfx_error.jpg

JJ

[Fmfx]

Hi,

I noticed high instability of the EA at lotsize < 1 :

fmfx_error.jpg

JJ

Hello. Check if you have your MM set to true.

Regards

[jjgengis]

Hi,

I noticed high instability of the EA at lotsize < 1 :

fmfx_error.jpg

JJ

Hello. Check if you have your MM set to true.

Regards

only JSL.

Thank you for the quick reply.

fmfx_1.set

[Fmfx]

only JSL.

Thank you for the quick reply.

fmfx_1.set

The lot size of the set you provided is set to 1.0 (ten $), and also you have hedge on CBI set to true.

Regards

[SteveHopwood]

You guys should be aware that Empty4 appears to have an endless series of nasty tricks up its sleeve to defeat the efforts of ea coders to overcome them. I suspect more are added deliberately at every 'new' release of the bloody-horrendous software.

All my bots have an arsenal of anti-crap tests provided by Matt Kennel, a stunning programmer with epic experience of all this. The code that stops, or should stop multiple trade sends is monumental.

Despite this, the criminals responsible for coding Empty4 have a lovely trick up their sleeve. When you start a new platform, its candle history is incomplete. If the chart is being updated at the same time and ea is sending a trade, then the trade send can go into an endless loop that is nothing to do with the ea. Matt has posted a script to help overcome this, that you should run every time you start a fresh platform:
http://www.stevehopwoodforex.com/phpBB3 ... 7360#p7360

No guarantees of a permanent fix, mind.

I am sorry to say this yet again guys(actually, I am not in the least sorry; the truth of this is self-evident to all coders but I am being kind), but all traders should also be coders. You should all learn to code mql4. Only from this exercise will you gain the understanding that allows you to use EA's safely. Until you gain this understanding, you are like drivers in a world where there are cars, but nobody to fix them when they stop working.

So, learn how EA's work or stop using them.

It is no coincidence that someone like myself never suffers the kind of problem described by jjgengis. There is no substitute for understanding the nature of the beast you are trying to tame. Without this level of understanding, you are no better off than jjgengis, whose post basically says, "It dunt wurk" without giving a possible clue as to why not.

I hope this does not come across as being too critical. The fact is, I developed the EA on the same platform jjgengis is using for demo-trading, and had no problem with over-trading. Therefore, it is some combination of thingies at jj's end that is causing the problem, and there is nothing the rest of us can do about that.

Aint Empty4 fun?