I will code your EAs and Indicators for no charge

Thank you for pointing out my question.
I may have used some inappropriate terms.
I am not using renko but range bar charts, which are started and calculated on the main M1 chart and opened on standalone charts labeled M61 and M62.
Bbands is given as an example because it can be calculated on the basis of another open autonomous chart. And when changing the size of the range bara (for example, for M62 we set 100 instead of 50), it performs the calculation based on these changes on the M61 chart.
That's why I thought I could get such a function from HA_sub.
I have another HA_MTF, but it is not displayed the way I would like it to be.
In the image it is now based on the M62 chart, but I would like it to look like the M62 chart on the M61 chart.
Maybe it's impossible.

Thank you so much. Actually I was hoping for a Sound Alert when the line changed direction. Which will now be the first red or green dot. At least I will know if I have missed a large move by the time I check. That was my concern. If I can get in when the ZigZag line first appears, or has not moved too much before I realize the change, maybe I can catch a wave.

Have a fun Halloween

It doesn't matter if it's Renko or Range Bar.
Renko is a fixed brick (the open to close is fixed).
Range Bar is a fixed bar from low to close or from high to close.
Both concepts are not time based!
So, everything I said for Renko also stands for Range Bars.

Well, I get your idea, but you need to remember that it doesn't always work that way.
Your idea is pretty good, and it can be profitable, but you would need a few extra elements to properly judge what's likely to happen next.
Because, otherwise, if you take every first signal, you may be losing too much.

BTW, the alert is there, too, if you look at the inputs!
The only thing is that the alert will trigger on every dot, so once per candle with dot.

Also, look at my chart:

There are two very important aspects:
1. Ask yourself if there may be reasons not to act on the specific signal.
2. Ask yourself what is the better price to enter if the opposite signal doesn't appear?
Hope you understand what I'm saying!

Not impossible, but that would be a very specific custom project which would require to code specific custom indicators.
And I don't think that anybody would be willing to do this for free.
Plus, there really is no sense in applying HA to Range Bars or Renko.

I don't know how to explain it.
Maybe my eyes are already very used to the main graphic. But. In the other (lower) window I can better and more clearly define support and resistance lines.
This is gold on RB5.

I didn't invent this method.
Author
https://www.forexfactory.com/thread/...-of-range-bars

Hello BestTraderEV and other Coders in the house, can you please make the following amendment to this indicator:
1 Make it work on ALL time frame from M1 to H1
2 Make it work on all major currency pairs
I dont know why it is not workin on lower TF and some currency pairs and others.
Thankung you in advancxe for your time.

I also include the original code from FS
GBP not stable and dissappearing

I don't see any significant difference for recognising SR.
However, the HA candles are not actual prices, so that is already a minus.
And, the other difference is that your candle colors on RB are different, because you have the Bar Up and Bar Down colors in different colors than Bull candle and Bear candle colors. If you change the Bar colors to the same colors as Candle colors, you may see it better...
Just a hint.

Mate, he's gone so far down that rabbit hole there is no saving him...

You need this RangeBar indicator

1. RangeBar - For creating your offline charts M61 set 2pips (20points) and M62 ser 5pips (50points)

1. Then apply your indicator(s) for each chart M61 and M62

1. After adding your indicator

I have attached OmniaAutoRange that will help you to get the size of range bar in pips based on timeframe. Eg M1 or M15.

Example: If your are using two different range bar size, equivalent to two different time frame, on normal chart like m5 for entries to the direction of m30 as your trend, For XAUUSD range bar size is 15pips (equivalent to M5 chart), and 37pips (equivalent to m30 chart)


NB: Most indicators we use not designed for offline chart, so to get better view of your indicator create offline charts using hourly charts like H2, H3, Note range bar size is not affected by offline charts you are using.
I hope this input will help you.

If you're using Renko or RB from ovo.cz, first you need a license, or you will only get only two weeks trial.
Otherwise, there is no such thing as "RB generated from H1 charts", at least not from ovo.cz
They are all generated from M1 data, no matter on which Tf the generator is running.

Here is the pine script version...
//@version=5
//

strategy(title='OPEN STRATEGY', shorttitle='OPEN STRATEGY', overlay=true, pyramiding=0, default_qty_type=strategy.percent_of_equity, default_qty_value=10, calc_on_every_tick=false)

// === INPUTS ===
useRes = input(defval=true, title='Use Alternate Resolution?')
intRes = input(defval=3, title='Multiplier for Alernate Resolution')
stratRes = timeframe.ismonthly ? str.tostring(timeframe.multiplier * intRes, '###M') : timeframe.isweekly ? str.tostring(timeframe.multiplier * intRes, '###W') : timeframe.isdaily ? str.tostring(timeframe.multiplier * intRes, '###D') : timeframe.isintraday ? str.tostring(timeframe.multiplier * intRes, '####') : '60'
basisType = input.string(defval='SMMA', title='MA Type: ', options=['SMA', 'EMA', 'DEMA', 'TEMA', 'WMA', 'VWMA', 'SMMA', 'HullMA', 'LSMA', 'ALMA', 'SSMA', 'TMA'])
basisLen = input.int(defval=8, title='MA Period', minval=1)
offsetSigma = input.int(defval=6, title='Offset for LSMA / Sigma for ALMA', minval=0)
offsetALMA = input.float(defval=0.85, title='Offset for ALMA', minval=0, step=0.01)
scolor = input(false, title='Show coloured Bars to indicate Trend?')
delayOffset = input.int(defval=0, title='Delay Open/Close MA (Forces Non-Repainting)', minval=0, step=1)
tradeType = input.string('BOTH', title='What trades should be taken : ', options=['LONG', 'SHORT', 'BOTH', 'NONE'])
// === /INPUTS ===

// Constants colours that include fully non-transparent option.
green100 = #008000FF
lime100 = #00FF00FF
red100 = #FF0000FF
blue100 = #0000FFFF
aqua100 = #00FFFFFF
darkred100 = #8B0000FF
gray100 = #808080FF

// === BASE FUNCTIONS ===
// Returns MA input selection variant, default to SMA if blank or typo.
variant(type, src, len, offSig, offALMA) =>
v1 = ta.sma(src, len) // Simple
v2 = ta.ema(src, len) // Exponential
v3 = 2 * v2 - ta.ema(v2, len) // Double Exponential
v4 = 3 * (v2 - ta.ema(v2, len)) + ta.ema(ta.ema(v2, len), len) // Triple Exponential
v5 = ta.wma(src, len) // Weighted
v6 = ta.vwma(src, len) // Volume Weighted
v7 = 0.0
sma_1 = ta.sma(src, len) // Smoothed
v7 := na(v7[1]) ? sma_1 : (v7[1] * (len - 1) + src) / len
v8 = ta.wma(2 * ta.wma(src, len / 2) - ta.wma(src, len), math.round(math.sqrt(len))) // Hull
v9 = ta.linreg(src, len, offSig) // Least Squares
v10 = ta.alma(src, len, offALMA, offSig) // Arnaud Legoux
v11 = ta.sma(v1, len) // Triangular (extreme smooth)
// SuperSmoother filter
// 2013 John F. Ehlers
a1 = math.exp(-1.414 * 3.14159 / len)
b1 = 2 * a1 * math.cos(1.414 * 3.14159 / len)
c2 = b1
c3 = -a1 * a1
c1 = 1 - c2 - c3
v12 = 0.0
v12 := c1 * (src + nz(src[1])) / 2 + c2 * nz(v12[1]) + c3 * nz(v12[2])
type == 'EMA' ? v2 : type == 'DEMA' ? v3 : type == 'TEMA' ? v4 : type == 'WMA' ? v5 : type == 'VWMA' ? v6 : type == 'SMMA' ? v7 : type == 'HullMA' ? v8 : type == 'LSMA' ? v9 : type == 'ALMA' ? v10 : type == 'TMA' ? v11 : type == 'SSMA' ? v12 : v1

// security wrapper for repeat calls
reso(exp, use, res) =>
security_1 = request.security(syminfo.tickerid, res, exp, gaps=barmerge.gaps_off, lookahead=barmerge.lookahead_on)
use ? security_1 : exp

// === /BASE FUNCTIONS ===

// === SERIES SETUP ===
closeSeries = variant(basisType, close[delayOffset], basisLen, offsetSigma, offsetALMA)
openSeries = variant(basisType, open[delayOffset], basisLen, offsetSigma, offsetALMA)
// === /SERIES ===

// === PLOTTING ===

// Get Alternate resolution Series if selected.
closeSeriesAlt = reso(closeSeries, useRes, stratRes)
openSeriesAlt = reso(openSeries, useRes, stratRes)
//
trendColour = closeSeriesAlt > openSeriesAlt ? color.green : color.red
bcolour = closeSeries > openSeriesAlt ? lime100 : red100
barcolor(scolor ? bcolour : na, title='Bar Colours')
closeP = plot(closeSeriesAlt, title='Close Series', color=trendColour, linewidth=2, style=plot.style_line, transp=20)
openP = plot(openSeriesAlt, title='Open Series', color=trendColour, linewidth=2, style=plot.style_line, transp=20)
fill(closeP, openP, color=trendColour, transp=80)

// === /PLOTTING ===
//

//
// === ALERT conditions
xlong = ta.crossover(closeSeriesAlt, openSeriesAlt)
xshort = ta.crossunder(closeSeriesAlt, openSeriesAlt)
longCond = xlong // alternative: longCond[1]? false : (xlong or xlong[1]) and close>closeSeriesAlt and close>=open
shortCond = xshort // alternative: shortCond[1]? false : (xshort or xshort[1]) and close<closeSeriesAlt and close<=open
// === /ALERT conditions.

// === STRATEGY ===
// stop loss
slPoints = input.int(defval=0, title='Initial Stop Loss Points (zero to disable)', minval=0)
tpPoints = input.int(defval=0, title='Initial Target Profit Points (zero for disable)', minval=0)
// Include bar limiting algorithm
ebar = input.int(defval=10000, title='Number of Bars for Back Testing', minval=0)
dummy = input(false, title='- SET to ZERO for Daily or Longer Timeframes')
//
// Calculate how many mars since last bar
tdays = (timenow - time) / 60000.0 // number of minutes since last bar
tdays := timeframe.ismonthly ? tdays / 1440.0 / 5.0 / 4.3 / timeframe.multiplier : timeframe.isweekly ? tdays / 1440.0 / 5.0 / timeframe.multiplier : timeframe.isdaily ? tdays / 1440.0 / timeframe.multiplier : tdays / timeframe.multiplier // number of bars since last bar
//
//set up exit parameters
TP = tpPoints > 0 ? tpPoints : na
SL = slPoints > 0 ? slPoints : na

// Make sure we are within the bar range, Set up entries and exit conditions
if (ebar == 0 or tdays <= ebar) and tradeType != 'NONE'
strategy.entry('long', strategy.long, when=longCond == true and tradeType != 'SHORT')
strategy.entry('short', strategy.short, when=shortCond == true and tradeType != 'LONG')
strategy.close('long', when=shortCond == true and tradeType == 'LONG')
strategy.close('short', when=longCond == true and tradeType == 'SHORT')
strategy.exit('XL', from_entry='long', profit=TP, loss=SL)
strategy.exit('XS', from_entry='short', profit=TP, loss=SL)

// === /STRATEGY ===
// eof

And here is my mql4 transformation...


//+------------------------------------------------------------------+
//| Open Test.mq4 |
//| Copyright 2024, MetaQuotes Ltd. |
//| https://www.mql5.com |
//+------------------------------------------------------------------+
#property copyright "Copyright 2024, MetaQuotes Ltd."
#property link "https://www.mql5.com"
#property version "1.00"
#property strict
// Inputs
extern bool useRes = true;
extern int intRes = 3;
extern string basisType = "SMMA";
extern int basisLen = 8;
extern int offsetSigma = 6;
extern double offsetALMA = 0.85;
extern bool scolor = false;
extern int delayOffset = 0;
extern string tradeType = "BOTH";
extern int slPoints = 0;
extern int tpPoints = 0;
extern int ebar = 10000;
// Constants colors
color green100 = Lime;
color lime100 = Green;
color red100 = Red;
color blue100 = Blue;
color aqua100 = Aqua;
color darkred100 = Maroon;
color gray100 = Gray;
//+------------------------------------------------------------------+
//| Expert initialization function |
//+------------------------------------------------------------------+
int OnInit()
{
//--- initialization code
//---
return(INIT_SUCCEEDED);
}
//+------------------------------------------------------------------+
//| Expert deinitialization function |
//+------------------------------------------------------------------+
void OnDeinit(const int reason)
{
//--- deinitialization code
}
//+------------------------------------------------------------------+
//| Expert tick function |
//+------------------------------------------------------------------+
void OnTick()
{
// Prices array
double closePrice = Close[0];
double openPrice = Open[0];
// Calculating Moving Averages
double closeSeries = iMA(NULL, 0, basisLen, 0, MODE_SMMA, PRICE_CLOSE, 0);
double openSeries = iMA(NULL, 0, basisLen, 0, MODE_SMMA, PRICE_OPEN, 0);
// Determine trend
bool longCond = (closeSeries > openSeries);
bool shortCond = (closeSeries < openSeries);
// Trading conditions based on tradeType
if (tradeType == "BOTH" || tradeType == "LONG") {
if (longCond) {
OrderSend(Symbol(), OP_BUY, 0.1, Ask, 3, 0, 0, "Buy Order", 0, 0, Green);
}
}
if (tradeType == "BOTH" || tradeType == "SHORT") {
if (shortCond) {
OrderSend(Symbol(), OP_SELL, 0.1, Bid, 3, 0, 0, "Sell Order", 0, 0, Red);
}
}
// Stop Loss and Take Profit logic
if (slPoints > 0 || tpPoints > 0) {
double slLevel = 0, tpLevel = 0;
if (slPoints > 0) slLevel = NormalizeDouble(Bid - slPoints * Point, Digits);
if (tpPoints > 0) tpLevel = NormalizeDouble(Ask + tpPoints * Point, Digits);
if (longCond) {
OrderSend(Symbol(), OP_BUY, 0.1, Ask, 3, slLevel, tpLevel, "Buy with TP/SL", 0, 0, Green);
} else if (shortCond) {
OrderSend(Symbol(), OP_SELL, 0.1, Bid, 3, slLevel, tpLevel, "Sell with TP/SL", 0, 0, Red);
}
}
}
//+------------------------------------------------------------------+

however it only takes 2 positions while there are several crossings
If you can correct
please

Next time, if there is a next time, please provide screenshots with the errors in logs!

Attached File(s)

! bbpt (mod_fixed).mq4   16 KB | 268 downloads

Attached File(s)

bbpt(fixed).mq4   8 KB | 287 downloads

NOTE!
When your EA, indicator or script isn't working properly, the first thing to do is look for errors and/or warnings in the logs!!!

hi traders
Please any indicator with time zone of data that numbers the bars like 1,2,3 ... after the time set up start any time frame?

Refer to my word:
Where did you get statement "from H1" ?

BTW: I have a full package licence key from OVO since 2019. Key can be used to maximum of three computers, And i can reset any time, for new user. i do not use any offline charts for now in my trading strategy.
I have enough understanding of all kind of offline charts thir strength and weakness.

Good Day.

=

Please bro kindly help in converting the attached to EA to trade on Daily candle the ea can follow the manual setting since the indicator has ENTRY STOP AND TP LEVELS. Please i will be grateful if it can be done . The ENTRY is the golden line ,Thanks

The ovo.cz Renko and Range Bar charts are always created from M1 data.
It does not matter on which timeframe the generator is running.
Therefore, you will not get any better view of anything by applying the generator indicator to H2 or H3 charts.
H2 and H3 charts are not default timeframes for MT4, so we need to create them offline.
We can't even place the generator indicator on other offline charts - it will not work and MT4 will crash.

So, please explain how can we "create offline [Range Bar] charts using hourly charts like H2, H3" ???

What we could do, though, is use an MTF indicator, on an offline chart, which reads data directly from a given default MT4 timeframe.
Such indicators work fine on ovo.cz Renko or Range Bar charts - I use them all the time.

Thank you very much for the quick fix. I really appreciate your kindness and serices for humanity.
It works well on other time frame.
Actually, the indicator was scripted from TV Attached is the image of the MOD indicator
if I may be a pain in the butt for another request:
Please can you color fill it to look like the TV version.
Here is the code from TV
fill(a,niv_2, color=#008000, transp=50)
fill(b,niv_22, color=#FF0000, transp=50)
fill(niv_22,niv_2, color=color.white, transp=60)

Trend = BullTrend - BearTrend

I aiso attached the image of the MT4 version that was not working on all time frames.
Thank you once again.

If you need to use Heiken Ashi MTF as a referrence in the separate window, then use it for a default MT4 TimeFrame which best represents your referrence trend. I simply use the default H1 chart in the separate window as my referrence trend guide.
However, for a 5pip Range Bar, maybe some other default MT4 Timeframe will be better for you?
In my experience, the H1 trend is sufficient for any Intraday style trading.

BTW, use this indicator:
UPDATE!!!
I have updated this indicator to plot HA in separate window on Renko and Range Bar like this:

Knew the issue was the Atr causing the zero divide just couldn't figure the fix, Thanks to BestTraderEv for his simple fix. Anyway, this would be the filled version, did the atr a little differently (hopefully I didn't mess up the fix), so please check if it is working on all timeframes.