Dashboard TZ

Is not implement yet. But I use it for manual trading. But only with normal charts. Drawing is better because I know how tune it. I have search how do it with renko

Cool stuff Brain.

This is the stuff with signals in v0.60

HP, when you force new bar in renko that bar have same time that last closed. When current bar is closed shows correct time. This is affecting my detection bar code

PS: data array are 4 last candles ( 0 is current )

With your observation, my question to HP is still relevant
Time (bar) sensitive indi NOT displaying ...
http://www.forexfactory.com/showthre...87#post9171687
http://www.forexfactory.com/showthre...33#post9171633

If I understand HP, he will not remake Renko driver.

Trend ( v0.65b8 ) - Renko fix

Download it at BtB Demos...

Renko is price based, not time. About your indy problem will be other reason because renko bars have time but is not current time. Its a constant time ( not relevant when date starts )

I not quite understand where does "Renko is price based, not time."

2 drivers Renko. 2 charts. One developer (HP)

MultiRenkoDriverv1.00: On the first chart fibo (and other TIME sensitive) lines displaying.
MultiRenkoDriverv1.05: On the second chart fibo lines don't displaying

Most of the other Renko drivers displays Fibo (and other TIME sensitive) Lines.

Maybe because first build used real time and last used arbitrary time. But better you ask to HP because he knows better that me how works his tool

BidRatio strength...

I was almost driving nuts doing some tests ("number of bars since last open" or "only add trade after x bars") till I saw your post/picture... I noticed that the open time of each renko bar doesn't look OK in v1.05 (no matter what driver settings or time-frame).. and I was about to start trying previous releases, but before that, I wanted to re-read a bit more about this just to try to double-check that I wasn't missing something... and I found that it seems that I'm not alone on this...

By looking at the bottom of your both charts... the timeline... in the chart at the left (v1.00) the date/time seems to be OK, but in the chart at the right (v1.05), it doesn't look OK (just like in mine while using v1.05).

Indeed, I don't know what's the issue neither, o why.. Perhaps Hotpotato can show us some light here...

I just made a quick test with v1.00 and it's seems to be doing "as expected"... just like in denya's picture...

I already explained this but i will do it again.

MT4 charts are time based.
A bar has an open and a close time and the movement in price between those time has no impact on those times.
A renko bar is movement based, it does not care about an open or close time just the movement of the price can generate a bar.

The are two things you absolutely shouldn't do in MT4
1) run out of history room (see brains problems)
2) generate bars beyond the current server time.

We are going to build Renko history from a M1 chart onto a M2 chart.
History files a sequential so we have to start at the beginning and work our way to the now (current server time).

Lets say we build M1 history onto a M2 chart.
We go back a 100 M1 bars and start there, we already know this will generate 50 M2 bars so we have a history start date for the first bar at last m1 bar time - 50 * M2 and if we work our way through 100 M1 bars the last M2 bar will be written at the current server time (last M1 bar time). Forward bars can be written by collecting two M1 bars and writing one M2 bar with 2 minutes bar interval (open/close time).

With movement based bars like Renko using M1 and fi. M2 we can also go back a 100 M1 bars but we have no idea up front how many Renko bars that will generate. It could be 200 and if we use the M2 bar times at the end we will be generating bars way past the current server time into the future.....and that is something MT4 doesn't understand or will accept.
You could take a bar interval of one second instead of two minutes but at 200 Renko bars that would leave your last bar way short of the real (current server time) last bar time.

We could do it the difficult way and build history from the now to the history beginning so we do not need a fixed starting point, solved.
For history it is solved but not for the current and future.

Assuming that we should never pass the server time we could use a bar interval time of 1 second leaving room for 120 Renko bars per (M2) time bar (that's MT4) so we write lets say 2 Renko bars interval 1 second each but the charts shifts because we are two minutes further in time (MT4 is time based).
We can not close the Renko bar because it is not full yet so we have to stretch the time to make the bar close at the last server bar close time.
You are left with a bar open/close time inconsistency because the previous two bars were written with a one second interval and this one with well 120 - 2 = 118 second (or even more) interval. You could persist in the one second interval but going further and further in time your bars will lag more and more which could cause the "missing bar" problem on some indicators.

Another problem are the big moves.
Let's say you got everything on time (M2 chart 1 second Renko bars) and that gbp flash happens again when you have a 5 pip Renko size.
The Renko writter will generate ( i thought it was 1400 pips up and down) 280 1 second bars and writing them to a M2 (120 second) chart will write bars in the future again so bye,bye MT4.

To accommodate Brain's stuff i decided to use an arbitrary history start date (30 days back) and start building from there not knowing where it will end but maintaining a perfect chart timeframe interval between bars.

In short, whatever approach you take to build Renko charts a lot of indicators will fail.
If i change everything for one indicator the next will fail and the next so that is not an option.

I agree things are more complex. But I only want do a comment. In theory renko bars are accommodate to MT4 API, not to my tools. If works like MT4 expected then all indicators using standard MT4 way will work. Maybe if some indicators fails with offline charts is because MT4 have many inconsistencies in his API and some of bugs like overflow history buffer ( they don't answer yet)

So, in brief, by now, there's no way to know in which renko bar an order took place.. either open/closed by using the latest versions of drivers...

Right?

Renko bars time is correlative. If you use M2 you will have 2 minutes shift in every bar. While you work with data provided for that TF is not problem if time is current or one month ago. If you open trade at XXX time bar and you want hold it 3 bars you only have check if current candle is 6 minutes later that candle where was opened the trade

Almost finished... Strength ( top ) vs Stregnth-Bidratio 25 ( middle ) % vs Stregnth-Bidratio 50% ( bottom )

Strength ( v0.60b3 )

+ added bidratio mode ( pure )
+ added bidratio mix ( for Trend/Strength/Velocity modes )

PS: Bidratio is strength of crosses. Is not same that others bidratios

Faster reaction and moew easy to setup

Renko... You can use formulas with bidratio mode too

HP is this ok ? do you have something similar when reload renko? http://screencast.com/t/VZEiiPgfM