Hi have made a indicator from the chat for ttm  4*(AVGH6.1+AVGL6.1)<AVGO6.1+AVGC6.1+2*(AVGH6+AVGL6+AVGC6)  I PUT IT IN CUSTOM PCF%TRUE INDICATOR

PLOT STYLE DOTS

COLOUR GREEN 

PERIOD 1

SIMPLE 

THE FORMULA 

 THEN WHEN IT IS PLOTED ON THE LAYOUT IT SHOWS THE GREEN DOTS WHEN IT IS TRENDING AND NOME WHEN IT IS NOT ( GOOD )  BUT IT IS GIVING ME ANOTHER LINE OF DOTS BELOW THE 1ST LINE, HOW DO I GET RIDE OF THIS EXTRA LINE

Try plotting the following as the Formula in a Custom PCF Indicator instead (not a Custom PCF % True Indicator).

100 / ABS(4 * (AVGH6.1 + AVGL6.1) < AVGO6.1 + AVGC6.1 + 2 * (AVGH6 + AVGL6 + AVGC6))

Thank you

What do I change in the formula posted by Bruce to make it below:

2 day instead of 1 day

3 day

4 day

week

I want to plot all of them on daily chart, is there a way to do that?

There isn't a way to get the calculations from the plots of of the 2, 3, 4 day and weekly charts from version 12/16 to plot on the daily charts.

It is possible to get the rolling 2, 3, 4 day and weekly charts from version 7 to plot on the daily charts.

2 day

100 / ABS(4 * (MAXH2.2 + MAXH2.4 + MAXH2.6 + MAXH2.8 + MAXH2.10 + MAXH2.12 + MINL2.2 + MINL2.4 + MINL2.6 + MINL2.8 + MINL2.10 + MAXH2.12) < O3 + O5 + O7 + O9 + O11 + O13 + C2 + C4 + C6 + C8 + C10 + C12 + 2 * (MAXH2 + MAXH2.2 + MAXH2.4 + MAXH2.6 + MAXH2.8 + MAXH2.10 + MINL2 + MINL2.2 + MINL2.4 + MINL2.6 + MINL2.8 + MINL2.10 + C + C2 + C4 + C6 + C8 + C10))

3 day

100 / ABS(4 * (MAXH3.3 + MAXH3.6 + MAXH3.9 + MAXH3.12 + MAXH3.15 + MAXH3.18 + MINL3.3 + MINL3.6 + MINL3.9 + MINL3.12 + MINL3.15 + MAXH3.18) < O4 + O7 + O10 + O13 + O16 + O19 + C3 + C6 + C9 + C12 + C15 + C18 + 2 * (MAXH3 + MAXH3.3 + MAXH3.6 + MAXH3.9 + MAXH3.12 + MAXH3.15 + MINL3 + MINL3.6 + MINL3.9 + MINL3.12 + MINL3.15 + MINL3.18 + C + C3 + C6 + C9 + C12 + C15))

4 day

100 / ABS(4 * (MAXH4.4 + MAXH4.8 + MAXH4.12 + MAXH4.16 + MAXH4.20 + MAXH4.24 + MINL4.4 + MINL4.8 + MINL4.12 + MINL4.16 + MINL4.20 + MAXH4.24) < O5 + O9 + O13 + O17 + O21 + O25 + C4 + C8 + C12 + C16 + C20 + C24 + 2 * (MAXH4 + MAXH4.4 + MAXH4.8 + MAXH4.12 + MAXH4.16 + MAXH4.20 + MINL4 + MINL4.4 + MINL4.8 + MINL4.12 + MINL4.16 + MINL4.20 + C + C4 + C8 + C12 + C16 + C20))

weekly

100 / ABS(4 * (MAXH5.5 + MAXH5.10 + MAXH5.15 + MAXH5.20 + MAXH5.25 + MAXH5.30 + MINL5.5 + MINL5.10 + MINL5.15 + MINL5.20 + MINL5.26 + MAXH5.30) < O6 + O11 + O16 + O21 + O26 + O31 + C5 + C10 + C15 + C20 + C25 + C30 + 2 * (MAXH5 + MAXH5.5 + MAXH5.10 + MAXH5.15 + MAXH5.20 + MAXH5.25 + MINL5 + MINL5.5 + MINL5.10 + MINL5.15 + MINL5.20 + MINL5.25 + C + C5 + C10 + C15 + C20 + C25))

Bruce: Thanks for quick response.

Does it mean, I need to install version 5 and will it affect any of my current charts/layouts/watchlists/etc?

No, you don't actually have to install TC2000 version 7, but it the formulas aren't going to match the charts in version 12/16.

You can install version 7 without affecting version version 12/16. It uses charts with rolling bars where the most recent bar has x number of bars. So the weekly bar always has 5 trading days for example.

In v12/16, the weekly bar is based on calendar weeks.

I tried adding to v7 but getting formula error: divide by zero.

The division by zero error is on purpose. This is what makes it not plot dots when it is false.

Yes, i figured it out but I tried to use weekly formula above on daily chart and it is coming up as blank for any symbol - fb, amd, wynn

I haven't tried it in TC2000 v7, but I don't think the Custom Indicator in v7 even has a Dot Plot Style to use to try to produce the desired effect.

The mention of v7 was merely to point out that it has completely different types of time frames. The 2, 3, 4 day and weekly time frames in v12/16 are fixed. They start and stop at fixed points on the calendar.

The 2, 3, 4 day and weekly time frames in v7 all end on the current trading day and are exactly 2, 3, 4 and 5 trading days long.

The dots being plotted on the daily chart in v12/16 will match the time frames from v7 and will not match the time frames from v12/16.

Oh! So is thr any approximate way to plot them in v12/16 or as of now it is not available!

You can plot the Custom PCF Indicators using the Dot Plot Style in a Daily Time Frame in TC2000 v12/16. The dots being plotted are just not going to match the v12/v16 time frames. the dots are going to match the v7 time frames.

Got it, so now how do I plot all of them merged into 1 indicator panel, something like below:

Indiactor panel:

---------------------------------------------------------------

1 day dots

2 day dots

3 day dots

4 day dots

week dots

Result dots : If all of the above rows has a dot in that column then show a dot in this row in that column

---------------------------------------------------------------

What you can do in TC2000 v12/16 is add multiple TTM Trend time frames as watchlist columns. I have them  stacked from 5 minute to daily with a 1 minute refresh rate on the columns.

This is extremely useful for getting multiple time frame alignment right in one's trades.

Keep in mind that the formula in this post is not identical to TTM Trend. I call it HA_Trend for Heiken Ashi Trend because it uses a 6-day HA average and compares it to the avg. 6-day range of the stock ending yesterday.

Telework: Thanks for the suggestion, will try it out.

I am trying to build a visual representation on the chart just the way it is done in TOS so I can visually confirm for several symbols and then use it as a scan along with other indicators to identify candidates.

You want to add the indicators to the same pane and scale.

Adding and Moving Indicators (7:19)

You may also want to do something like use different colors for the dots and change the 100s at the beginning of the formulas to different values for the different formulas so they plot at different levels instead of overtop of each other.

Implemented.

Last Q: I tried to combine all formulas above into a single formula (indicator) but it appears that v12.4 cannot handle it and keeps going into Not responding mode. is it due to # of calculations in single indicator?

The calculations are not designed to be implemented into a single indicator. Keep in mind that the indicator doesn't plot specifically because it generates an error. So if you have five indicators that generate error messages when they aren't supposed to plot you are going to have serious issues if you are trying to combine them into a single formula. The errors would conflict with each other and make it so the indicators wouldn't plot when they should.

ah haa! that would explain why it became very slow.

This is how it looks now.

Thanks for your help :-)

You're welcome. I don't know why the errors would make things slow though.

IsItPossible:  That looks really good what you have implemented. 

Why is it that this can be done on version 7 but not v12/16?

Would be useful for me if this could be done for 15, 30, 60, and 120 min charts.

Never mind, i saw above the explanation as to how the time frames work differently in v7 vs. 12/16.

Certainly would be nice if we could mix time frames for some of these indicators.

Here is an example of a watchlist that has stacked HA_Trend, stacked ATR Stops and stacked Squeeze in one view.

IsItPossible:  It looks like you implemented the formulas on v12 and not v7 as mentioned.  I don't think you are getting multiple time frames on your daily chart. It does not look right to me.

Bruce said it would only work on v7

Telework

He should be using only daily.

Think of it more like multiple "lengths" vs. timeframes.

This way V12 should match V7.

Thanks

Telework: Yes, it does not work correctly :-(

How did you create HA_trend for different timeframes!!! is that working right?

I have yet to implement it on v7, its a cumbersome process to implement in v7...

To add HA_Trend to multiple watchlists columns, each with a different time frame, first save the basic formula as a PCF.

4*(AVGH6.1+AVGL6.1)<AVGO6.1+AVGC6.1+2*(AVGH6+AVGL6+AVGC6)

Then simply add a new watchlist column and select the PCF. You then can choose the time frame and how the condistion is displayed.... dot, check mark, etc.  You can also choose "When False" to display a different color.

Add multiple times and select a different time frame for each.

Modified the above fiormula to get better results:

100 / ABS( ((AVGH6.1 + AVGL6.1) / 2 <  ((AVGO6.1 + AVGC6.1)/2 + (AVGH6 + AVGL6 + AVGC6))/4)
or ((AVGH6.1 + AVGL6.1) / 2 < C)  )

It provides very good entry but the exit needs to be tweaked further, tried multiple things but didnt work, any help is appreciated.

I compared modified with your original formula above and another formula provided by Bruce below: (check it out)

100 / abs ((O + H + L + C) / 4 > ((4 * MAXH5.1 + XAVGO3.2 + XAVGH3.2 + XAVGL3.2 + XAVGC3.2 + ABS(4 * MAXH5.1 - XAVGO3.2 - XAVGH3.2 - XAVGL3.2 - XAVGC3.2) + 2 * (XAVGO3.3 + XAVGH3.3 + XAVGL3.3 + XAVGC3.3) + ABS(4 * MAXH5.1 + XAVGO3.2 + XAVGH3.2 + XAVGL3.2 + XAVGC3.2 + ABS(4 * MAXH5.1 - XAVGO3.2 - XAVGH3.2 - XAVGL3.2 - XAVGC3.2) - 2 * (XAVGO3.3 + XAVGH3.3 + XAVGL3.3 + XAVGC3.3)) + XAVGO3.4 + XAVGH3.4 + XAVGL3.4 + XAVGC3.4 + XAVGO3.5 + XAVGH3.5 + XAVGL3.5 + XAVGC3.5 + ABS(XAVGO3.4 + XAVGH3.4 + XAVGL3.4 + XAVGC3.4 - XAVGO3.5 - XAVGH3.5 - XAVGL3.5 - XAVGC3.5) + 2 * (XAVGO3.6 + XAVGH3.6 + XAVGL3.6 + XAVGC3.6) + ABS(XAVGO3.4 + XAVGH3.4 + XAVGL3.4 + XAVGC3.4 + XAVGO3.5 + XAVGH3.5 + XAVGL3.5 + XAVGC3.5 + ABS(XAVGO3.4 + XAVGH3.4 + XAVGL3.4 + XAVGC3.4 - XAVGO3.5 - XAVGH3.5 - XAVGL3.5 - XAVGC3.5) - 2 * (XAVGO3.6 + XAVGH3.6 + XAVGL3.6 + XAVGC3.6)) + ABS(4 * MAXH5.1 + XAVGO3.2 + XAVGH3.2 + XAVGL3.2 + XAVGC3.2 + ABS(4 * MAXH5.1 - XAVGO3.2 - XAVGH3.2 - XAVGL3.2 - XAVGC3.2) + 2 * (XAVGO3.3 + XAVGH3.3 + XAVGL3.3 + XAVGC3.3) + ABS(4 * MAXH5.1 + XAVGO3.2 + XAVGH3.2 + XAVGL3.2 + XAVGC3.2 + ABS(4 * MAXH5.1 - XAVGO3.2 - XAVGH3.2 - XAVGL3.2 - XAVGC3.2) - 2 * (XAVGO3.3 + XAVGH3.3 + XAVGL3.3 + XAVGC3.3)) - XAVGO3.4 - XAVGH3.4 - XAVGL3.4 - XAVGC3.4 - XAVGO3.5 - XAVGH3.5 - XAVGL3.5 - XAVGC3.5 - ABS(XAVGO3.4 + XAVGH3.4 + XAVGL3.4 + XAVGC3.4 - XAVGO3.5 - XAVGH3.5 - XAVGL3.5 - XAVGC3.5) - 2 * (XAVGO3.6 + XAVGH3.6 + XAVGL3.6 + XAVGC3.6) - ABS(XAVGO3.4 + XAVGH3.4 + XAVGL3.4 + XAVGC3.4 + XAVGO3.5 + XAVGH3.5 + XAVGL3.5 + XAVGC3.5 + ABS(XAVGO3.4 + XAVGH3.4 + XAVGL3.4 + XAVGC3.4 - XAVGO3.5 - XAVGH3.5 - XAVGL3.5 - XAVGC3.5) - 2 * (XAVGO3.6 + XAVGH3.6 + XAVGL3.6 + XAVGC3.6)))) + (4 * MINL5.1 + XAVGO3.2 + XAVGH3.2 + XAVGL3.2 + XAVGC3.2 - ABS(4 * MINL5.1 - XAVGO3.2 - XAVGH3.2 - XAVGL3.2 - XAVGC3.2) + 2 * (XAVGO3.3 + XAVGH3.3 + XAVGL3.3 + XAVGC3.3) - ABS(4 * MINL5.1 + XAVGO3.2 + XAVGH3.2 + XAVGL3.2 + XAVGC3.2 - ABS(4 * MINL5.1 - XAVGO3.2 - XAVGH3.2 - XAVGL3.2 - XAVGC3.2) - 2 * (XAVGO3.3 + XAVGH3.3 + XAVGL3.3 + XAVGC3.3)) + XAVGO3.4 + XAVGH3.4 + XAVGL3.4 + XAVGC3.4 + XAVGO3.5 + XAVGH3.5 + XAVGL3.5 + XAVGC3.5 - ABS(XAVGO3.4 + XAVGH3.4 + XAVGL3.4 + XAVGC3.4 - XAVGO3.5 - XAVGH3.5 - XAVGL3.5 - XAVGC3.5) + 2 * (XAVGO3.6 + XAVGH3.6 + XAVGL3.6 + XAVGC3.6) - ABS(XAVGO3.4 + XAVGH3.4 + XAVGL3.4 + XAVGC3.4 + XAVGO3.5 + XAVGH3.5 + XAVGL3.5 + XAVGC3.5 - ABS(XAVGO3.4 + XAVGH3.4 + XAVGL3.4 + XAVGC3.4 - XAVGO3.5 - XAVGH3.5 - XAVGL3.5 - XAVGC3.5) - 2 * (XAVGO3.6 + XAVGH3.6 + XAVGL3.6 + XAVGC3.6)) - ABS(4 * MINL5.1 + XAVGO3.2 + XAVGH3.2 + XAVGL3.2 + XAVGC3.2 - ABS(4 * MINL5.1 - XAVGO3.2 - XAVGH3.2 - XAVGL3.2 - XAVGC3.2) + 2 * (XAVGO3.3 + XAVGH3.3 + XAVGL3.3 + XAVGC3.3) - ABS(4 * MINL5.1 + XAVGO3.2 + XAVGH3.2 + XAVGL3.2 + XAVGC3.2 - ABS(4 * MINL5.1 - XAVGO3.2 - XAVGH3.2 - XAVGL3.2 - XAVGC3.2) - 2 * (XAVGO3.3 + XAVGH3.3 + XAVGL3.3 + XAVGC3.3)) - XAVGO3.4 - XAVGH3.4 - XAVGL3.4 - XAVGC3.4 - XAVGO3.5 - XAVGH3.5 - XAVGL3.5 - XAVGC3.5 + ABS(XAVGO3.4 + XAVGH3.4 + XAVGL3.4 + XAVGC3.4 - XAVGO3.5 - XAVGH3.5 - XAVGL3.5 - XAVGC3.5) - 2 * (XAVGO3.6 + XAVGH3.6 + XAVGL3.6 + XAVGC3.6) + ABS(XAVGO3.4 + XAVGH3.4 + XAVGL3.4 + XAVGC3.4 + XAVGO3.5 + XAVGH3.5 + XAVGL3.5 + XAVGC3.5 - ABS(XAVGO3.4 + XAVGH3.4 + XAVGL3.4 + XAVGC3.4 - XAVGO3.5 - XAVGH3.5 - XAVGL3.5 - XAVGC3.5) - 2 * (XAVGO3.6 + XAVGH3.6 + XAVGL3.6 + XAVGC3.6))))) / 64)

IsItPossible:  It looks quite good. Most of the time it is very similar to what I am using but there were just a few instances where it signaled an entry one dot earlier. I wish I could tell what it is actually doing without spending an inordinate amount of time pouring over the numbers.

You might be interested that I am actually using a slight modification of the original formula which uses an equal weighting of a 5 day and 6 day look back period which I found signaled earlier on some occasions without disrupting the continuity of the trend signal staying intact during a move. Here is the formula that i'm currently using:

2 * (AVGH5.1 + AVGL5.1 + AVGH6.1 + AVGL6.1) < AVGO6.1 + AVGC6.1 + 2 * (AVGH6 + AVGL6 + AVGC6)

And try out those stacked HA_Trend time frames as watchlist columns as I outlined above. It really helps to stay on the right side of the higher level trend AND be in only those stocks that have all time frames aligned.

One other note is that you will find that if your formula is very long then the refresh rate granularity will be limited when you add HA_Trend as a watchlist column.  The shorter formulas allow for a 1 minute refresh rate which is fairly important for getting near real time feedback for the indicator.

100 / ABS( ((AVGH6.1 + AVGL6.1) / 2 <  ((AVGO6.1 + AVGC6.1)/2 + (AVGH6 + AVGL6 + AVGC6))/4)
or ((AVGH6.1 + AVGL6.1) / 2 < C)  )

is plotting dots and is exactly same as

4*(AVGH6.1+AVGL6.1)<AVGO6.1+AVGC6.1+2*(AVGH6+AVGL6+AVGC6)

without addition of

or ((AVGH6.1 + AVGL6.1) / 2 < C)

The above addition helps to fire the trigger earlier providing good entry, however it also entends the exit which I am trying to eliminate.

Thanks for sharing your modified formula, will test that one.

Finally found another way to resolve this in v12 with a diferent formula and it appears to work awesome......

Use this formula: Custom indicator => select dots

100/ABS(
(H + L + O + C)/4 > ((XAVGH6 + XAVGL6 + XAVGO6 + XAVGC6)/4)
and (H + L + O + C)/4 > ((XAVGH12 + XAVGL12 + XAVGO12 + XAVGC12)/4)
and (H + L + O + C)/4 > ((XAVGH18 + XAVGL18 + XAVGO18 + XAVGC18)/4)
and (H + L + O + C)/4 > ((XAVGH24 + XAVGL24 + XAVGO24 + XAVGC24)/4)
and (H + L + O + C)/4 > ((XAVGH30 + XAVGL30 + XAVGO30 + XAVGC30)/4)

)

Not my invention but thanks to whoever shared it on another forum.

Armed with a better understanding of how Heikin Ahsi closes are constructed I played around with a bunch of different variants tonight and came up with one that I think works quite well.

I'm currently using a 9-period exponential moving average of Heikin Ashi coupled with a 4-period front weighted average of price. I found the that weighted moving average made for more timely signals than calculating the mid point of the range.

Different moving average periods can be substituted with the tradeoff being a slightly earlier entry signal but with more false signals to bump you out of the trend. Longer settings keeps you in the trend longer if you can stomach pullbacks and usually only delays the entry signal by one bar at most.

HA_Trend:  3 WMA & Heikin Ashi  7 EMA

100 / ABS ((3 * C + 2 * C1 + C2) / 6 < (XAVGO7.1 + XAVGH7.1 + XAVGL7.1 + XAVGC7.1) / 4)

HA_Trend:  4 WMA & Heikin Ashi 9 EMA

100 / ABS ((4 * C + 3 * C1 + 2 * C2 + C3) / 10 < (XAVGO9.1 + XAVGH9.1 + XAVGL9.1 + XAVGC9.1) / 4)

HA_Trend:  5 WMA & Heikin Ashi 10 EMA

100 / ABS ((5 * C + 4 * C1 + 3 * C2 + 2 * C3 + C4) / 15 < (XAVGO10.1 + XAVGH10.1 + XAVGL10.1 + XAVGC10.1) / 4)

  HA_Trend:  5 WMA & Heikin Ashi 13 EMA

100 / ABS ((5 * C + 4 * C1 + 3 * C2 + 2 * C3 + C4) / 15 < (XAVGO13.1 + XAVGH13.1 + XAVGL13.1 + XAVGC13) / 4)

Great discussion and sharing, I have yet to implement this in v7.

Have you tried this on v12?

If I understand what you are saying.

You should get the same results.

No reason for V7.

Thanks

ISitPossible

Tried to set up formula and it did not work for me, please help

IsItPossible:  I'm implementing everything on v16. The formulas you provided simply use longer moving averages but they are not going to get the same result as being able to integrate multiple time frames into a single indicator. And the other solution provided for v7 only  works on the daily time frame anyhow which is not granular enough for what I do.

Therefore, i'm just sticking with having the multiple time frames in watchlist columns. This coupled with the indicator at the bottom of the chart and the ability to toggle different charts using the Function keys gives me everything I need.

I watched my new formula in action with the market today and it is really good. One of the most valuable tools in the 'ol arsenal!

Telework

used your formula

100 / ABS ((4 * C + 3 * C1 + 2 * C2 + C3) / 10 < (XAVGO9.1 + XAVGH9.1 + XAVGL9.1 + XAVGC9.1) / 4)

but get an error "divide by zero"

any help ? thanks !

isitabubble: with the 100 / ABS form you need to create with a customer PCF indicator and NOT a custom % true indicator. That's the only thing I can think of that might be causing you an issue.

telework: it worked thanks, did not select the "dot plot"