I will code your EAs and Indicators for no charge

Fxid_trends.nrp

Hi, does anyone have an ATR channel indicator where you can change the reference days and the ATR value?
Thanks

Alternatives

https://www.forexfactory.com/showthr...1#post10956461
https://www.forexfactory.com/showthr...1#post12475181
https://www.forexfactory.com/showthr...1#post12464371

Hello I am looking for a simple EA Where I can set a time of day for the trade to start put in the direction buy or sell set a take profit in pips and a stop loss in pips do you have such an EA?

When a particular currency pair reaches 25% of its monthly ATR, I jump in, in that direction. Look at the image I attached below for a visual representation.

Can anyone code me a fibonacchi alert indicator for mt5 that send me a sound alert when the price (possibly in candles) bounces off a fib level?
It should ignore candles that close like 30% or 50% of their lenght beyond a fib level.

Thanks in advance.

This may be foolish or impossible but here goes...

I have an idea for scalping one or more candles after signal candle closes.

The idea consists of a script or indicator that takes a new candle and uses every tick (I guess) to count how many times a new high is made and how many times a new low is made (starting with the open price) for the duration of the candle and shows the result after close.

My idea is to trade in the direction with the most new highs/lows. The reasoning is if a candle is making more new highs than lows then we trade long on next candle. It may turn out that going in the opposite direction may be the better way.

We could have a situation where we get a bearish candle that has been making new highs all candle and then makes one new low and closes bearish and maybe going long would be the right move. This will need testing to figure out.

I find this intriguing.

This should be able to be tested on any TF.

Again this may be an idea that goes nowhere...but you know how it goes when you get an idea...you have to flesh it out and see where you end up.

If anyone is willing to help create this I would be grateful.

Thanks, Chris

I want the EA to open two trades simultaneously as it started. After every 50 pip movements, it opens one more Hedging trade of the 1.35 times the original lot size.
Total number of trades open like this goes only till level 6. That means if the market moved 300 (6 x 50 pips) pips in same direction, and now no more new trades are opened.

Regarding take profit. Lets say the market is going short, we open hedge order at 1.10, if the market goes to 1.09500 it will open one more hedge order here but will close the previous profit order.

Similarly, if it goes to 1.09, it will open one more hedge but close previous profit order opened at 1.095.

Once all 6 orders are open it will not open any more hedge orders. It will then wait for the market to retrace and will sell the buy order in this case at break even or 40% loss from the total profits taken in the process.

What parameters should be configurable? : Take loss at what percentage. In our example it is at 40%.

Lot size

New order after how many pips.

Hie i need an EA for MT5 made for me based on the stochastic oscillator it should include the following
TRADE EXECUTION
Buy and sell
Buy only option
Sell only option

TRADR ENTRY
Buy at stochastic... level option
Sell at stochastic.....level option
Close buy at stochastic ...... level
Close sell at stochastic ...... level
Stop loss..... pips /points
Take profit(if enabled it disables the close at stochastic.... level)
Adjustable lot size

TRADE FILTER OPTION
Trade uptrend only
Trade downtrend only
Trade ranging and uptrend
Trade ranging and downtrend

Hello,

Is anyone able to convert a prorealtime indicator to an MQL4 one?

This is an indicator to show the price point the next closing price will need to cross before the MACD Histogram changes directions.

The maths is here:

ma = 12
mb = 26
mc = 9
MM = Exponentialaverage[12]-Exponentialaverage[26]
MS = Exponentialaverage[9](MM)
f1 = ((mc+1)*MM-2*MS)/(rm-1)
f2 = Exponentialaverage[12]*(ma-1)/(ma+1)
f3 = Exponentialaverage[26]*(mb-1)/(mb+1)
f4 = 2/(ma+1) - 2/(mb+1)
dcv = (f1-f2+f3)/ f4

All help appreciated!

Thank you,

Q

Hi programmers:

I would like to add a feature to the EA.
I will try to explain my idea.

This is a very interesting EA to use in certain market circumstances. It is one of Ilan's systems, which trades with the grid and martingale modality. Therefore it is very dangerous.
It has three independent strategies called: Violin, Cello and Piano.
The risk becomes worse, if all three strategies open trades in the same direction, since it triples the risk, making EA even more dangerous.

This is my idea:

Some restriction may be placed so that if two strategies are playing in one direction the third one opens only if it is in the opposite direction to those already open.

I explain.

Suppose Violin opened short, and Piano too. Put a restriction that if Cello wants later to open short too, EA does not do it because there are already two strategies in play in that direction and that allows EA to open if signal is long, or that allows EA to open short only if one of the previous two resolved with profit. Will that modification be possible? I hope I was clear. The idea is that you don't play all three strategies in the same direction at the same time, at most two

The idea is not to alter the EA to open in the opposite direction, only to avoid that if the three strategies try to operate in one direction they do not do it simultaneously. A maximum of two. This is because if the operation is complicated, do so only with two strategies and not with all three simultaneously

Thanks a lot

i also use the concept of precentange of ATR of W,M candle,i have few ideas and indicators that are helpful,pm me.

You just need to add the guitar .

Hello everybody,
I would like to use Trend Strength indicator attached for MT5 (quite good) but every time the MT5 refresh or connect/disconnect the indicator miss-calculate the trend. So everything became red or blue. Please I would like to ask you if it is possible to fix it. Please help.
Thanks.

I don't have any experience coding prorealtime. However, I could probably figure out what the code is achieving, except (just for starters) I have these problems:

Line 4: doesn't say what it is creating an ExponentialAverage of. By contrast, see the fragment from the prorealtime programmer's manual below. These are clearly 12 and 20 EAs of the Close. Same problem with lines 7 & 8.

Line 6: there is a variable rm, but there is nothing saying what this data item is, or how it is derived/calculated.

Can anybody help?

@Quass: do you have a prorealtime chart image showing the plotted output that your indicator produces?

Thanks for replying.
My bad about this. Prorealtime automatically uses the close price if no other price is specified, so the price would be the close in this case.

That would be totally my excitedness causing a typo. It should be mc. Really sorry.

Here's the fixed formula:
ma = 12
mb = 26
mc = 9
MM = Exponentialaverage[12]-Exponentialaverage[26]
MS = Exponentialaverage[9](MM)
f1 = ((mc+1)*MM-2*MS)/(mc-1)
f2 = Exponentialaverage[12]*(ma-1)/(ma+1)
f3 = Exponentialaverage[26]*(mb-1)/(mb+1)
f4 = 2/(ma+1) - 2/(mb+1)
dcv = (f1-f2+f3)/ f4

Thanks so much for looking into this!

The version you posted is of Igor and old enough,a lot has been changed till now regarding metaquotes language.
Try using Mladen's latest ver,it is on rsx when igor ver is using rsi - rsi and rsx are the same family indicators the difference simply rsx is a bit smoother (means removing false signals) comparing to rsi,users can adjust things by parameters according to his/her strategy and requirements
in picture the lowest sw - in middle sw your posted one
Always try posting your queries with illustrating picture/s for to avoid ignored and or over looked

Hi @hanover,

Thanks for looking into this.
I had previously replied your queries (the post is still pending approval, because newbie), prior to the asking for the PRT picture, so if the reply post shows up, please don't be surprised.

In case it doesn't show up, here are the responses (and my apologies for both):
1) Prices are for close prices - the PRT default is close if no price is specified.
2) I made a typo in the formula because I was too excited. The unknown variable should be mc.
For your convenience, the whole formula is listed here:
ma = 12
mb = 26
mc = 9
MM = Exponentialaverage[12]-Exponentialaverage[26]
MS = Exponentialaverage[9](MM)
f1 = ((mc+1)*MM-2*MS)/(mc-1)
f2 = Exponentialaverage[12]*(ma-1)/(ma+1)
f3 = Exponentialaverage[26]*(mb-1)/(mb+1)
f4 = 2/(ma+1) - 2/(mb+1)
dcv = (f1-f2+f3)/ f4

Lastly, the requested pictures:


As can be seen from the picture, the indicator (Histxover) is represented as dots on the chart.
It is read by looking at the close price of the NEXT candle.

In the picture, Wed 22 Jan's is marked on the cursor. The HistXover value is 1.1085.
The next close (Thurs 23 Jan) is below 1.1085, so correspondingly in the histogram (below), the histogram goes down from 22 to 23Jan.

Here's another case to look at, one day before:
Wed 22 Jan's close is above the Xover of 21 Jan..
This means that the MACD Histogram will go upwards from 21 Jan to 22 Jan.

One last case study with the two most recent prices on this chart:
Looking at the most recent two candles, because the most recent candle closed above the XOver value of the 2nd candle from the right, the MACD Histogram goes up.

(The MACD and corresponding HistXOver uses the standard Appel formula, and not the MT4 one).

Hope this clarifies! Really appreciate your looking into this!

I assume you want a timeseries plotted? Also you didn't say whether you wanted the plot in the main chart or in a separate window. I have no idea what the output should look like. Perhaps an image from your prorealtime would have been helpful.

Anyway that's my best shot, and if it's not what you're seeking, I'll let somebody else have a try.
____________________________________

Sorry, I had already done the work before I saw your post. Comparing the respective plots, it looks like something is amiss (the yellow line strays much further away from the candles than the dots in your prorealtime plot), but I can't see anything obvious in my code. To reduce the possibility of a transcription error, I copy/pasted your formulae and modified them for MQL4.

I created the DivZero(x,y) function to simply return 0 on a divide by zero error for x/y; MT4 used to freeze when it encountered such an error.

You might be able to see the error in my code and fix it yourself. The debug commands (if you uncomment them) allow you to check the calculation step by step for each datapoint; data is output to .../MQL4/Files/debug.txt by default. I can't run a side-by-side comparison with prorealtime. Alternatively, if you see anything obviously wrong, let me know what it is, and I'll attempt to correct it for you. Unfortunately I have no experience with prorealtime so what I've attempted amounts to guesswork.

[EDIT] I just noticed your comment "It is read by looking at the close price of the NEXT candle." Given that there's a dot plotted under the rightmost candle on your chart, then in order to plot this dot, how does it know what the close of the next candle will be? Anyway, perhaps that's part of the problem with my code, as I'm using the close of the current candle.

It's almost 1am in my part of the world and I'm going to bed now.
____________________________________

My last attempt. I've uploaded a xls with a step-by-step calculation of the values for EURUSD,Daily, as calculated by my MT4 indicator.

Perhaps you can make PRT perform a similar dump, and then compare the values in each column, to see at what point the respective calculations differ. Of course the close prices will likely be different, especially if midnight in the respective datafeeds differs.

Maybe MT4 and PRT calculate EMAs differently. If I recall correctly, because the EMA calc involves the EMA of the prior datapoint, and none exists for the leftmost value, SMA is used to calculate the leftmost value (confirmed here). Also it means that any rounding issue gets propagated as we move rightward. Moreover, any discrepancy would be exacerbated because the required calc involves taking the EMA of an EMA (MS is an EMA of MM, which itself is the difference of 2 EMAs).

I checked the calculations of f1, f2, f3, f4, dcv -- the attached xls shows that they are all correct except for minor rounding considerations. Hence the discrepancy is somehow being caused by the respective calculations of the EMAs. Or because I'm using the close of the current candle rather than the next candle.

I attempted to calc the values both left-to-right and right-to-left, but there was no apparent difference in the result.

Anyway, I've spent almost 2 hours on this, it's time for me to do something more productive.

Hi,

Does anyone have a London Breakout Strategy EA or coder they could refer me too. Your help would be immensely appreciated.

Kindest Regards,

Pipfish