Thanks.
Can you recommend any reputable coders who might be interested in helping with this project?
Can you recommend any reputable coders who might be interested in helping with this project?
Adjustable MA
- Thread starter Enivid
- Start date
- Watchers 19
Trading indices, for the most part, I would prefer the EA to avoid the Asian session ... Would it be possible to set the trading times ... As a starting point I am thinking of starting 16:30 (New York Open) to 23:00 (Lack of interest sets in) subject to optimisation
Preferably Start Hour - Start Minute - End Hour - End Minute
Talking of optimisation would it be possible to have the Time Frame in inputs
Thank you for your time
Preferably Start Hour - Start Minute - End Hour - End Minute
Talking of optimisation would it be possible to have the Time Frame in inputs
Thank you for your time
Last edited:
Be very careful hiring an MQL5 freelancer ... They like to think of themselves as Developers (name on the tab) BUT, in reality, are only coders looking for a fast buck and not prepared to think outside of the box ... Fine if you know EXACTLY what you want
The same applies to fiverr
Look at this thread I started ... https://www.mql5.com/en/forum/457686 ... after being so annoyed with the freelancer I had hired
There is no common tab on my version
As I understand it the facility has to be coded into the EA
Last edited:
//----
hey maverick..... it should be there...... even a blank ea should have the about, common and input sections..... no code on our part is required.......
you might try downloading it again......h
//-----
Close all either TP or SL end of EA trading day (23:00) ... Next day EA waits for a cross after the EA start
Start and End need optimising for optimum results ... Market generally (not always) changes direction when the session changes
Asia to Europe ... Europe to London ... London to New York ... New York to Asia
Easier and quicker to optimise with separate Hour and Minute
The option needs to be True / False for those who don't want to use it ... for whatever reason
Post automatically merged:
It can be coded in ... have had to ask MQL5 "Developers" to include it
Last edited:
Lets assume the EA is set to stop trading at 22:35 close (or 22:40 open) ... At that time all positions are closed either in profit or at a loss
Thanks, hayseed for the input
... Enivid set me straight (learn something new every day) ... ONLY there on MT4 platform
What I am thinking at the moment ... split the day into zones (when the market changes direction) ... each zone having its own TP level ... Friday was a once-in-a-month event (NFP) ... Zone 3 TP set at 15 for the rest of the month [all settings subject to optimisation]
Because I trade the US500 (indices) it's Points, not Pips ... I could never get the MQL5 "Developers" to understand there was a difference
For those readers who don't know ... A point in Forex is the last decimal place of the price ... A point in stocks, indices futures, or commodities is one whole number
The MACD is just to emphasise the change points for me (pity it can only be used with EMA) ... Now thinking of having an indicator made based on the MACD but with all the methods in inputs ... possibly line instead of histogram
Because I trade the US500 (indices) it's Points, not Pips ... I could never get the MQL5 "Developers" to understand there was a difference
For those readers who don't know ... A point in Forex is the last decimal place of the price ... A point in stocks, indices futures, or commodities is one whole number
The MACD is just to emphasise the change points for me (pity it can only be used with EMA) ... Now thinking of having an indicator made based on the MACD but with all the methods in inputs ... possibly line instead of histogram
Last edited:
//----
yeah me to..... bad habit of mine to assume everyone is talking about mq4.....
changes are seldom made without a practical reason..... now i'm curious as to why it was dropped in mt5......h
The backtest results are strange and it is opening positions WAY WAY after the MA's cross.
This is a screenshot of one of the trades opened on the EURUSD 15M chart.
It opens the trade 21 bars after the MA's ACTUALLY cross, which is a good 5+ hours later. Even so, with my TP at 200 it should have STILL closed the trade in profit, but instead didn't close it until it became a loss. Have tried this with even minimum distance at 1 and still the same thing happens.
using Period 1: 9 EMA and Period 2: 21 EMA. Even if I reverse the periods, the same thing happens.
Something is broken here.
This is a screenshot of one of the trades opened on the EURUSD 15M chart.
It opens the trade 21 bars after the MA's ACTUALLY cross, which is a good 5+ hours later. Even so, with my TP at 200 it should have STILL closed the trade in profit, but instead didn't close it until it became a loss. Have tried this with even minimum distance at 1 and still the same thing happens.
using Period 1: 9 EMA and Period 2: 21 EMA. Even if I reverse the periods, the same thing happens.
Something is broken here.
Last edited:
The EA was entering later in your backtest due to the MinDiff parameter. You can set to to zero if you want faster entries.The backtest results are strange and it is opening positions WAY WAY after the MA's cross.
This is a screenshot of one of the trades opened on the EURUSD 15M chart.
It opens the trade 21 bars after the MA's ACTUALLY cross, which is a good 5+ hours later. Even so, with my TP at 200 it should have STILL closed the trade in profit, but instead didn't close it until it became a loss. Have tried this with even minimum distance at 1 and still the same thing happens.
using Period 1: 9 EMA and Period 2: 21 EMA. Even if I reverse the periods, the same thing happens.
Something is broken here.
This trade was nowhere near 200 pips of profit for such a TP to trigger. This EA's parameters are in pips (which is explicitly stated on the EA's description page), not in points.
Even when I set it at 0, it was still entering trades late.
Ugh...that explains that on the pips/points thing...why would an EA be created in pips when points are so much more granular?
That's weird. Perhaps that was 1 bar "late" because it waits for the bars to finish forming before checking for the crossover?
I coded it at the time when people generally expected for all parameters to be in pips.
