TradingView Pine Script: How Do Timeframes Work?

What are Timeframes and Why are They Important?

In TradingView, a timeframe represents the interval at which data points (open, high, low, close, volume) are aggregated to form a single bar or candle on the chart. Timeframes are crucial because they influence the signals and patterns you observe. Different timeframes reveal different aspects of price action, allowing traders to analyze trends and make decisions from multiple perspectives. A shorter timeframe, such as 1 minute, provides more granular detail but can be noisy. A longer timeframe, like 1 day, smooths out the noise but might delay signals.

Default Chart Timeframe vs. Script Timeframe

It’s important to distinguish between the chart’s timeframe (the timeframe you’re currently viewing) and the script’s timeframe (the timeframe your script uses for calculations). By default, Pine Script operates on the chart’s timeframe. However, you can explicitly request data from different timeframes within your script, providing flexibility in your analysis and strategy development. This is where request.security() comes in.

Requesting Data from Different Timeframes

The request.security() Function

The request.security() function is the cornerstone of multi-timeframe analysis in Pine Script. It allows you to retrieve data from a symbol and timeframe different from the chart’s current timeframe. This is essential for creating indicators or strategies that consider data from multiple resolutions.

Syntax and Parameters of request.security()

The basic syntax of request.security() is as follows:

request.security(symbol, timeframe, expression)

• symbol: A string representing the ticker symbol of the asset you want to retrieve data from (e.g., “AAPL”, “BTCUSDT”). Use syminfo.tickerid for the current chart’s symbol.
• timeframe: A string specifying the timeframe. Examples: “5”, “15”, “60”, “240”, “1D”, “1W”, “1M”.
• expression: The expression you want to calculate on the requested timeframe. This could be close, high, low, volume, or any other valid Pine Script expression.

Specifying the Timeframe in request.security()

The timeframe parameter in request.security() is critical. It dictates the resolution of the data being fetched. Common timeframe values include:

• Minute-based: “1”, “5”, “15”, “30”, “60” (for 1 minute, 5 minutes, 15 minutes, etc.)
• Hour-based: “1H”, “2H”, “4H”
• Day-based: “1D”
• Week-based: “1W”
• Month-based: “1M”

Choose the timeframe based on the specific analysis you want to perform. Higher timeframes are often used for identifying overall trends, while lower timeframes provide more detailed price action data.

Timeframe Considerations and Best Practices

Data Alignment and Potential Issues

When using request.security(), be mindful of data alignment. The data from different timeframes might not align perfectly with the chart’s bars. For example, if you’re on a 5-minute chart and requesting 1-hour data, each 1-hour value will only update every 12 bars. This can lead to unexpected behavior if not handled carefully.

Avoiding Repainting When Using Higher Timeframes

Repainting is a common issue when using higher timeframes. It occurs when an indicator’s values change retroactively as the higher timeframe bar completes. To mitigate this, use the lookahead parameter in request.security() to access historical data, thus using barmerge.gaps_off to prevent repainting.

Choosing the Right Timeframe for Your Strategy

The ideal timeframe depends on your trading style and strategy. Day traders might focus on shorter timeframes (1-15 minutes), while swing traders might prefer hourly or daily charts. Consider the holding period of your trades and the level of detail required for your analysis.

Practical Examples of Timeframe Usage

Calculating Moving Averages on a Higher Timeframe

This example calculates a 200-period moving average on the daily timeframe and plots it on the chart:

//@version=5
indicator(title="Daily 200 MA", overlay=true)

dailyMA = request.security(syminfo.tickerid, "1D", ta.sma(close, 200))

plot(dailyMA, color=color.red)

Identifying Support and Resistance Levels from Multiple Timeframes

This example fetches high and low prices from a weekly timeframe to identify potential support and resistance zones:

//@version=5
indicator(title="Weekly High/Low", overlay=true)

weeklyHigh = request.security(syminfo.tickerid, "1W", high)
weeklyLow = request.security(syminfo.tickerid, "1W", low)

plot(weeklyHigh, color=color.green, style=plot.style_linebr)
plot(weeklyLow, color=color.red, style=plot.style_linebr)

Creating Multi-Timeframe Indicators

You can combine multiple timeframes in a single indicator to gain a more comprehensive view of price action. For example, you could calculate a faster moving average on a lower timeframe and a slower moving average on a higher timeframe to identify potential trend changes.

Limitations and Alternatives

Timeframe Limitations in Free TradingView Accounts

Free TradingView accounts have limitations on the number of request.security() calls allowed per script. This can restrict the complexity of your multi-timeframe indicators.

Alternatives for Aggregating Data Across Timeframes

If you need to aggregate data across timeframes without using request.security() excessively, consider using loop-based techniques or external data sources. These methods can be more complex but offer greater flexibility.