One-hour forex signals routed from TradingView to DXTrade
Automating a Patient GBPCHF Strategy on DXTrade
This strategy does not allow one indicator to make the decision alone. RSI and Stochastic must first agree that GBPCHF is stretched, Awesome Oscillator must then confirm that momentum has changed, and ATR defines where the resulting trade should admit failure or take profit.
Many trading systems are built like a single doorbell: one condition changes, and an order appears. This strategy behaves more like a door protected by three different keys.
The open-source Buy&Sell Strategy depends on AO+Stoch+RSI+ATR by SerdarYILMAZ combines several momentum and volatility measurements instead of treating one oscillator crossing as sufficient evidence.
The test uses the British Pound / Swiss Franc market on a one-hour TradingView chart. The calculation uses the OANDA GBPCHF feed shown in the historical report, while execution is routed to a separately configured account on the DXTrade platform.
The chart provider and execution destination are deliberately separated. TradingView produces the strategy order. AlgoWay receives the webhook and routes the instruction to DXTrade.
A trade opens only after three analytical keys align
The author describes the long condition as a sequence. RSI and Stochastic must be in oversold territory, then Awesome Oscillator must turn positive. The short condition mirrors that logic: RSI and Stochastic must be overbought, then Awesome Oscillator must turn negative.
RSI measures pressure
RSI estimates whether recent GBPCHF movement has become unusually strong in one direction. In this configuration, the RSI source is Close and its length is 10.
Stochastic checks location
Stochastic examines where price sits relative to its recent range. The configured values are K 12, D 3 and smoothing 3.
Awesome Oscillator turns the final key
The strategy does not enter merely because the market is overbought or oversold. Awesome Oscillator must change sign and confirm that momentum has started moving away from the extreme.
RSI and Stochastic act like two witnesses describing the same event from different positions. One measures directional pressure, while the other measures location inside the recent range. Awesome Oscillator acts as the final witness confirming that momentum has actually changed.
This is not decorative language. The script's entry logic requires agreement between stretched oscillator conditions and a change in Awesome Oscillator direction.
ATR is the emergency plan rather than another entry vote
Average True Range does not decide whether the strategy should buy or sell. ATR measures recent movement and is used by the original script to define stop-loss and take-profit levels.
The configured ATR Length is 14. On the one-hour chart, this means the volatility estimate observes fourteen recent hourly candles.
RSI, Stochastic and Awesome Oscillator build the entry decision. ATR measures how much ordinary GBPCHF movement should be expected when defining the strategy's loss and profit boundaries.
A fixed number of pips can represent very different risk during a quiet session and a volatile session. ATR allows the Pine strategy to adapt its internal exit calculation to the recent movement of the pair.
The exact visible settings behind the report
Fast Length 8 and Slow Length 33 belong to the Awesome Oscillator component in this customized strategy. The shorter window reacts to recent movement, while the longer window represents a slower momentum baseline.
Stochastic K 12 examines the recent trading range. D 3 and smoothing 3 reduce some of the movement in the raw oscillator. RSI Length 10 remains relatively responsive on a one-hour forex chart.
They are not universal GBPCHF parameters. Changing the feed, timeframe, oscillator lengths, ATR length, order sizing or test dates creates a different strategy report.
One-hour trading is slower than the word intraday may suggest
A one-hour chart is usually associated with intraday or day trading because each decision is built from hourly candles rather than daily or weekly bars.
That does not guarantee that every position opens and closes during the same trading session. A signal appearing late in the day can remain active overnight, and a slow GBPCHF movement can continue across several sessions.
It is not scalping
Scalping normally expects frequent decisions from seconds or low-minute charts. This strategy waits for several hourly indicators to align and does not produce that tempo.
It is slow intraday trading
The one-hour chart allows the system to react inside the trading week, but the multi-indicator filter sharply reduces how often a trade is accepted.
It can overlap short swing trading
Positions may survive a session boundary or remain open into another day. Operationally, the strategy can sit between day trading and short-duration swing trading.
The historical report completed 104 trades over approximately thirty-one months. That is only around three to four completed trades per month, or less than one per week on average.
A trader watching this system manually could wait several days for the three analytical keys to align. An automated route removes the need to stare at the chart, but it does not remove the waiting period built into the strategy.
The equity curve is calm because the strategy moves slowly
The visible Strategy Tester period runs from January 2, 2024 through July 25, 2026. The simulation begins with 100,000 USD, uses 10% of equity for the strategy order and executes on the completed candle.
| Test property | Recorded value | Why it matters |
|---|---|---|
| Chart symbol | GBPCHF | Defines the currency pair evaluated by the strategy. |
| TradingView feed | OANDA | Supplies the exact hourly candles used in the simulation. |
| Timeframe | 1 hour | Defines the duration of every indicator observation. |
| Initial capital | 100,000 USD | Provides the starting balance for the historical report. |
| Order size | 10% of equity | Allows the simulated position size to follow account equity. |
| Script execution | On bar close | Waits for the one-hour conditions to be completed. |
A provider change matters on forex. Different GBPCHF feeds can have small differences in highs, lows and closes. Those differences can alter RSI, Stochastic, Awesome Oscillator, ATR and the exact candle on which a signal appears.
A 73.08% win rate produced only a 0.43% total return
Seventy-six of the 104 recorded trades were profitable. The historical win rate reached 73.08%.
A profit factor of 2.055 means recorded gross profit was a little more than twice recorded gross loss during the selected sample.
Maximum drawdown was only 68.96 USD, or 0.07% of the recorded starting capital.
Those figures look exceptionally controlled, but the total simulated profit was only 426.48 USD, or 0.43%, across more than two and a half years.
This report combined frequent winning trades with very small account growth. The strategy was selective and calm, but it did not compound capital quickly under the recorded position sizing.
The result is a useful reminder that win rate, drawdown and total return answer different questions. A smooth curve can still move too slowly for a trader's objective.
Could this rhythm fit a prop-account evaluation?
The recorded drawdown and profit factor make this configuration interesting as a research candidate for accounts governed by strict loss limits.
The difficulty is pace. A strategy earning 0.43% across the entire recorded sample would not reach a typical evaluation target quickly under the same assumptions.
A trader could attempt to increase order size, add more currency pairs or combine several uncorrelated systems. Each of those changes also changes the risk, drawdown, signal overlap and backtest result.
Increasing size can accelerate progress toward a profit target, but it can also accelerate daily loss, total drawdown and the effect of spread, slippage or execution differences.
This strategy may suit a patient evaluation approach better than an aggressive attempt to reach a target in a few sessions. It still does not guarantee that an account will pass.
Before using automation on any evaluation account, review its rules for maximum daily loss, overall drawdown, overnight positions, news trading, automated systems and consistency requirements.
The original author presents the script as an educational example
The TradingView author explicitly states that the strategy was created for learning Pine Script and should not be treated as a direct buy or sell recommendation.
That warning remains relevant even when the historical report looks attractive. Open-source code allows the logic to be inspected, but transparency does not guarantee future profitability.
The appropriate use of this page is technical reproduction: understand the indicators, reproduce the test, connect a demo or small account, inspect every entry and exit, and decide whether the behaviour matches the intended risk.
The recorded DXTrade route uses Hedge or Dual Side mode
The AlgoWay route shown for this experiment uses Hedge/Dual Side.
Hedge/Dual Side
Opposite exposure can be handled independently rather than automatically netted into one position. Entry and exit behaviour must therefore be verified carefully.
Reverse/Netting
An opposite signal works against the current exposure and leaves one resulting net direction. This is a different execution model.
Flat orders
When the TradingView strategy exits through its ATR logic, the webhook must deliver the corresponding flat or closing state to DXTrade.
Hedge mode should not be selected merely because it sounds more flexible. Test long entry, short entry, take-profit exit, stop-loss exit and flat behaviour using the actual DXTrade account configuration.
Creating a neutral DXTrade route in AlgoWay
Open Dashboard >> Trade Webhooks and create a route with TradingView as the source and DXTrade as the destination.
| AlgoWay field | Recorded setup | Purpose |
|---|---|---|
| Platform | DXTrade | Selects the DXTrade execution connector. |
| Trade Type | Hedge/Dual Side | Defines how opposite-direction exposure is handled. |
| URL | Your DXTrade environment URL | Connects AlgoWay to the correct platform environment. |
| Login | Your account login | Authenticates the configured DXTrade session. |
| Password | Your account password | Completes authentication for the route. |
| Account ID | Your account identifier | Selects the account that should receive the order. |
| Quantity Multiplier | Absolute 1 | Passes the incoming strategy quantity without scaling it. |
| News Filter | No | Does not block orders around configured economic events. |
The DXTrade URL is environment-specific. Use the exact URL supplied for the account rather than copying a URL from another trading environment.
Login and Account ID are not necessarily the same value. Enter each field exactly as provided or displayed by the platform.
The full connection procedure is documented in TradingView to DXTrade Webhook Automation Guide with AlgoWay .
A small manual test verifies the execution path
Before the strategy controls the route, open Dashboard >> Webhook Logs and send a small connection test to the configured DXTrade account.
Use the smallest valid GBPCHF quantity accepted by the destination environment. The test should confirm authentication, account selection, symbol resolution, order-size rules and the DXTrade response.
It does not calculate RSI 10, Stochastic 12/3/3, Awesome Oscillator 8/33 or ATR 14. It checks only whether the AlgoWay route can deliver a valid command to DXTrade.
Verify the test in AlgoWay Webhook Logs and in the DXTrade account. Close the test exposure before enabling the final TradingView strategy alert.
The basic alert mirrors TradingView entries and exits
Return to the GBPCHF one-hour chart and confirm the strategy inputs before creating the alert.
Create the alert from the strategy order fills and place this one-line JSON in the Message field:
{"platform_name":"dxtrade","ticker":"{{ticker}}","order_contracts":"{{strategy.order.contracts}}","order_action":"{{strategy.market_position}}","price":{{close}}}{{ticker}}
Inserts the TradingView GBPCHF ticker. Configure Symbol Mapping when the DXTrade environment uses a suffix or another symbol format.
{{strategy.order.contracts}}
Inserts the quantity calculated for the executed TradingView strategy order. A fixed manual test size should not replace it.
{{strategy.market_position}}
Inserts the resulting TradingView strategy state as long, short or flat. The DXTrade route interprets that state according to its configured trade mode.
{{close}}
Inserts the TradingView closing price available when the alert fires. It is a reference value and not a guaranteed DXTrade execution price.
Open Notifications, enable Webhook URL and paste the private AlgoWay URL generated for the DXTrade route.
TradingView keeps a server-side copy of the strategy when the alert is created. After changing the inputs or Strategy Properties, delete the old alert and create it again.
ATR exits inside Pine are not automatically native DXTrade orders
The original strategy calculates its stop-loss and take-profit through ATR. With the basic JSON above, TradingView remains responsible for detecting when those strategy exits occur.
When the Pine strategy exits, the alert sends the resulting strategy state to AlgoWay. This is different from placing a native stop-loss and take-profit on the DXTrade account immediately when the entry is opened.
An internal Pine exit requires TradingView to calculate the exit and deliver another alert. A native account-side protective order can remain active at the destination without waiting for another webhook.
Traders who require native DXTrade protection should adapt the Pine strategy to
calculate explicit levels and send supported stop_loss,
take_profit, sl_price or
tp_price fields. Those values must be tested against the exact
route behaviour before live use.
The first autonomous trade must be verified from signal to exit
An entry appearing on the TradingView chart is only the beginning of the automation test.
- Confirm the TradingView strategy order. Record whether the three analytical keys produced a long or short state and note the strategy quantity.
- Read AlgoWay Webhook Logs. Confirm the received ticker, order action, contracts and DXTrade response.
- Inspect the DXTrade account. Confirm the correct symbol, accepted size and intended exposure.
- Wait for the real strategy exit. Verify that an ATR-based stop-loss or take-profit event produces the expected closing alert and account result.
Testing only the first entry is insufficient for a strategy intended to run unattended. The full lifecycle includes long, short, stop-loss, take-profit, flat behaviour and recovery after a rejected order.
The complete GBPCHF route
What this patient forex experiment establishes
RSI and Stochastic identify stretched GBPCHF conditions. Awesome Oscillator confirms that momentum has changed direction. ATR 14 defines the internal strategy exits.
Across the recorded period, the strategy completed 104 historical trades, produced a 73.08% win rate and a profit factor of 2.055, while maximum drawdown remained at 0.07%.
The same report produced only 0.43% total profit. That combination describes a selective and stable historical system, but also one that may require considerable patience to reach a meaningful target.
AlgoWay connects the TradingView order flow to a neutral DXTrade account using a dedicated route, Hedge/Dual Side mode, account-specific credentials and dynamic TradingView strategy placeholders.
The result may justify further prop-account research, but neither the historical metrics nor the automated connection guarantees that an evaluation will be passed.
Original strategy: Buy&Sell Strategy depends on AO+Stoch+RSI+ATR by SerdarYILMAZ . DXTrade connection manual: TradingView to DXTrade Webhook Automation Guide with AlgoWay .
Direct answers
Direct answers about GBPCHF automation on DXTrade
Can this GBPCHF TradingView strategy be automated on DXTrade?
Yes. TradingView can send the strategy order state and quantity to an AlgoWay webhook, and AlgoWay can route the validated instruction to a configured DXTrade account.
Which indicators are combined by this GBPCHF strategy?
The strategy combines Awesome Oscillator, Stochastic, RSI and ATR. RSI and Stochastic identify stretched market conditions, Awesome Oscillator confirms a momentum change, and ATR defines the strategy's stop-loss and take-profit distances.
Which settings produced the recorded GBPCHF backtest?
The visible configuration used Fast Length 8, Slow Length 33, K 12, D 3, Smooth 3, RSI source Close, RSI Length 10 and ATR Length 14 on the one-hour GBPCHF chart.
Is a one-hour GBPCHF strategy considered day trading?
A one-hour strategy usually belongs to slower intraday or day trading, but some positions can remain open across sessions or into another day. Its practical rhythm can therefore overlap with short-term swing trading.
How frequently did this GBPCHF backtest trade?
The recorded test completed 104 trades from January 2024 through July 2026. That is only about three to four completed trades per month on average, so the strategy requires patience rather than constant activity.
Could this strategy be used for a prop evaluation?
Its low recorded drawdown and relatively high historical win rate may make it interesting for further prop-account research, but the recorded profit accumulated very slowly. It does not guarantee that any evaluation will be passed.
Why does the DXTrade route use Hedge or Dual Side mode?
The recorded AlgoWay route uses Hedge or Dual Side mode. In this mode, opposite exposures may be handled independently, so entry, exit and flat alerts must be tested carefully before the strategy is allowed to control an account.
Does the basic TradingView JSON place native DXTrade stop-loss and take-profit orders?
No. The basic strategy JSON mirrors TradingView order states and quantities. The original strategy can later send an exit when its ATR logic is triggered, but native account-side protective levels require the Pine script and JSON to send supported SL and TP fields.
Which TradingView quantity should be used in the final alert?
The final strategy alert should use {{strategy.order.contracts}} so TradingView sends the quantity attached to the executed strategy order. A small fixed quantity belongs only to the connection test.
What historical results did the GBPCHF test produce?
From January 2, 2024 through July 25, 2026, the TradingView simulation produced 426.48 USD in total profit, a profit factor of 2.055, 76 profitable trades out of 104 and maximum drawdown of 68.96 USD.