Back to product

OFFICIAL USER GUIDE

GUMRAI ORB VX User Guide

From access and TradingView installation to reading MAIN / ADD 1, System SL, TP1–TP6, Runner, dashboard, and alerts with a consistent workflow.

Updated for ORB VX · MAIN + ADD 1 · 6 Targets + Runner

Start in five minutesBack to product
XAUUSD · GUMRAI ORB VX
GUMRAI ORB VX User Guide

Before you begin

This indicator is a planning tool. It does not place broker orders and does not guarantee results. Always verify your actual entry, position size, spread, and account risk before making a decision.

Contents
SECTION 01

Access and TradingView installation

Choose a free trial or paid plan, then add the invite-only indicator to a chart

Free 30-day trial

Sign in, open the ORB VX product page, enter the exact TradingView username, and submit the trial request. No card and no automatic renewal.

Request trial

Paid access: 30 / 90 / 365 days

Choose a one-time plan, add it to the cart, sign in, enter the exact TradingView username, and pay through Stripe. Access time starts only after Gumrai grants the invite.

View access plans
1

Wait for the access-ready email and confirm the username shown in My Indicators.

2

Open TradingView → Indicators, metrics and strategies → Invite-only Scripts, then select GUMORBVX.

3

Open the supported XAUUSD chart and choose the timeframe you can actively monitor.

4

Open Settings and confirm Dashboard, current MAIN / ADD 1 plans, price tags, and alert groups.

5

Create one alert per timeframe using “Any alert() function call”.

6

Begin with Paper Trading. This Pine indicator never places MT4/MT5 orders for you.

TradingView invite-only access is granted by the script author to the submitted username. A TradingView subscription by itself does not include access to GUMRAI ORB VX.

SECTION 02

Know the screen

Read MAIN / ADD 1, Entry Zone, System SL, targets, and the dashboard

MAIN / ADD 1

The arrow and BUY/SELL text identify the direction and leg. MAIN is primary; ADD 1 is a separate conditional add-on.

Entry Zone

A price area to monitor—not an automatic order and not proof that every viewer received the same fill.

TP1–TP6 / RUNNER

Six fixed checkpoints plus a farther Runner level. A check mark means chart price reached that level.

System SL

The invalidation level used by the plan. Calculate your own monetary risk from your actual entry.

Dashboard

Shows the current plan on the right and historical model-plan observations on the left.

Alerts

Reports NEW MAIN, ADD 1, TP1–TP6, Runner, BE, and SL events. It does not place a broker order.

Preparing and entry confirmed are separate states

A gray plan means the setup is still preparing. Wait for the separate entry-confirmed alert before treating it as active. If confirmation fails, the levels disappear and only a small gray NO ENTRY tag remains.

Know the screenOpen full-size image
The active MAIN plan shows its Entry Zone, System SL, TP1–TP6, and Runner together. The dashboard at top right separates historical observations from the current MAIN / ADD 1 state.
SECTION 03

The life of a plan

Understand when a plan starts, changes state, and closes

01

Gray plan prepares

02

Entry is confirmed

03

TP1–TP6 progress

04

BE after TP2 or SL

05

Runner or leg closes

PREPARING is a short live-only state while the system waits for confirmation. The live capture below shows this gray waiting state. It can then collapse into NO ENTRY if confirmation fails, or become a full colored plan after entry confirmation.

Live ORB VX gray MAIN PREPARING plan waiting for entry confirmationOpen full-size image
Live capture: the gray MAIN PREPARING · WAIT FOR ENTRY label and the matching Telegram message show that levels are provisional. Do not treat this as an active entry until the separate entry-confirmed event arrives.
ORB VX candidates collapsed into gray NO ENTRY labelsOpen full-size image
A preparation candidate that fails confirmation does not become an active plan. Its working levels disappear and only the small gray MAIN • NO ENTRY label remains. It is excluded from TP/SL result totals.
ORB VX ADD 1 after entry confirmationOpen full-size image
After confirmation, the temporary gray preparation state is removed and the active plan appears in full color with its Entry Zone, System SL, TP1–TP6, and Runner. This example shows an ADD 1 leg that has reached TP3.
SECTION 04

Entry Zone and System SL

Separate the planned price area from your actual fill

Treat Entry Zone as the model’s visible working range. The gray state is preparation only; the colored state begins after entry confirmation. The center line remains the plan reference, so a different execution price changes the monetary distance to System SL and every target.

1Check the live spread
2Measure actual entry to SL
3Set risk before entry
Entry Zone and System SLOpen full-size image
Read the leg name first, then its Entry Zone and its own red System SL. In this example MAIN and ADD 1 overlap visually but remain two independent plan legs.
SECTION 05

Managing overlapping MAIN and ADD 1

Keep each leg’s Entry Zone, System SL, and risk separate

MAIN

The primary leg. Read its own MAIN Entry Zone and MAIN System SL. Your real fill may differ from the label, so calculate monetary risk from your actual MT4/MT5 order.

ADD 1

A separate add-on leg that can appear while MAIN is still active. It has its own Entry Zone and System SL and must not be treated as a free or riskless increase.

When MAIN and ADD 1 overlap

  • Track them as two legs; each leg keeps the Entry Zone and System SL shown beside its own label.
  • If you place both orders manually, attach and manage each SL separately in MT4/MT5.
  • Combined account risk = MAIN risk + ADD 1 risk. Reduce lot size or skip ADD 1 if the total exceeds your limit.
  • Do not widen either System SL to make two orders share one farther stop. A wider stop changes the plan risk.
Managing overlapping MAIN and ADD 1Open full-size image
MAIN and ADD 1 can sit close together, but each label points to its own Entry Zone and red System SL. Use the leg name to match every order with the correct protection level.
MAIN and ADD 1 reaching targets and RunnerOpen full-size image
Both legs may progress through targets at different entry prices. Check marks describe price reaching a plan level; they do not prove that a user opened both legs or received the same fills.
SECTION 06

TP1–TP6, Runner, and staged exits

Read the target ladder and an educational scale-out / BE framework

TargetPlan distanceRole
TP1~500 ptFirst checkpoint
TP2~800 ptProtection checkpoint
TP3~1,200 ptContinuation target
TP4~1,750 ptExtended move
TP5~2,500 ptLonger extension
TP6~3,500 ptFinal fixed target
RUNNERBeyond TP6Optional remainder

Every target is a chart-plan reference, not a command or guarantee. Actual MT4/MT5 fills, spread, slippage, and lot size can change the result.

ORB VX model scale-out assumptions

These percentages explain dashboard PF, expectancy, and drawdown calculations. They are not personalized trade advice. Test the same rules in Paper Trading before considering live use.

TP110%The model realizes 10%; 90% remains.
TP210%Another 10% is realized; 80% remains and BE becomes active for that leg.
TP35%Another 5% is realized; 75% remains.
TP45%Another 5% is realized; 70% remains.
TP5 / TP60%Milestone alerts only in the model; no additional portion is realized.
RUNNER70%The model closes the remaining 70% only if Runner is reached; otherwise BE or SL may end the leg earlier.

When to consider break-even

The dashboard state is BE AFTER TP2. For manual orders, wait until the relevant MAIN or ADD 1 leg has actually confirmed TP2, then account for spread/commission before moving protection toward the actual entry. Moving to the label price can still lock a loss if your real fill was worse.

Never increase risk after entry

Do not move a System SL farther away, average into a losing plan without a new ADD 1 signal, or treat an unreached target as guaranteed. If combined MAIN + ADD 1 risk exceeds your limit, reduce size or skip the add-on.

SECTION 07

Every signal tag and plan state

Read Entry, TP, Runner, BE, SL, and per-leg result labels

▲ MAIN BUY / ▼ MAIN SELLThe primary leg and direction. This is a chart plan, not a filled broker order.
ADD 1 PLANA separate conditional add-on leg with its own Entry Zone and SL.
ENTRY ZONEThe visible range around the plan entry reference.
SLThe System SL assigned to that specific leg.
TP1–TP6Fixed price checkpoints. A ✓ means chart price reached that level.
RUNNERThe farthest model level; a ✓ means Runner was reached.
ACTIVE / TPx HITThe latest progress state for the live leg.
BE AFTER TP2After TP2, the model protects the remaining portion at the entry reference.
SYSTEM SL REACHEDThe leg ended at System SL before TP2 protection became active.
BE EXIT AFTER TP2The remaining portion returned to the entry reference after TP2.
Result labelClosed labels combine leg, direction, outcome, and model R result—for example MAIN BUY • TP4 • +x.xxR.
Every signal tag and plan stateOpen full-size image
This completed example shows independent MAIN and ADD 1 levels, per-target check marks, and Runner labels. Match every tag to its leg before acting.
SECTION 08

Read every dashboard row

Understand live MAIN / ADD status and historical model observations

Historical model observations

TP1–TP6 / RUNNERCount and percentage of closed legs whose chart price reached each level.
LOSS < TP1Legs that returned to System SL before reaching TP1.
CLOSED LEGSTotal MAIN and ADD 1 legs that reached an ending state in the loaded history.
CYCLESNumber of setup cycles; one cycle may contain MAIN and ADD 1 legs.
CYCLE PFHistorical model ratio for the displayed cycle assumptions—not brokerage account PF.
EXPECTANCYAverage historical model result per cycle, expressed in R.
MAX DDLargest historical model drawdown in R under the displayed assumptions.
MAIN / ADD 1Sample size, model PF, and expectancy separated by leg type.
ADD USEDHow many cycles accepted ADD 1 and its share of all cycles.
WIN POINTS (HIST)Summed historical favorable plan distance; not account profit.
BE AFTER TP2Count of legs whose protection state advanced after TP2.
MODELThe loaded model name and the MAIN + ADD 1 structure.

Current cycle: MAIN and ADD 1

▲ MAIN BUY / ▼ MAIN SELLThe primary leg direction and visible Entry Zone.
ADD 1 WAIT / BUY / SELLWhether the add-on is waiting, active, or has a direction.
SLEach leg’s own System SL. A dash means no active value for that leg.
TP1–TP6 / RUNNERLive target prices; ✓ means chart price reached the level.
TP6 HITThe current cycle reached its final fixed target.
BE AFTER TP2Protection state expected after the relevant leg confirms TP2.
CYCLE RISKCurrent combined planned risk for the visible cycle.
HIST MAX RISKLargest comparable model risk observed in loaded history.
MAIN TP1 / ADD 1 TP1Historical TP1 reach rate separated by leg type.
ACTIVE LEGSHow many MAIN / ADD legs are currently active.
SL BEFORE TP1Historical point total from legs stopped before TP1.
PLAN HISTORY ON / OFFWhether previous plan drawings are retained on the chart.
SYSTEM READYThe indicator is calculated and ready; this does not mean an MT4/MT5 order is open.
Read every dashboard rowOpen full-size image
ORB VX dashboard sample. The left half summarizes historical model observations. The MAIN and ADD 1 columns on the right show the current cycle; they never confirm a broker order or realized account P&L.
SECTION 09

Choose a timeframe

Use a timeframe you can monitor and never mix levels across charts

01

Use a chart above 1 minute

ORB VX shows USE TF > 1m on a 1-minute chart. Choose a supported interval above 1 minute; the supplied example uses 15m.

02

Keep each chart independent

A MAIN / ADD 1 cycle, targets, and dashboard history belong to that chart interval. Never copy its levels to another timeframe.

03

Match the alert interval

Create the alert from the same chart and keep the alert interval identical to the chart interval.

Choose a timeframeOpen full-size image
This guide uses a 15-minute XAUUSD example. Confirm SYSTEM READY in the dashboard before relying on labels or alerts.
SECTION 10

TradingView Alerts and Telegram

Configure Any alert() function call and separate personal from public alerts

  1. 01

    Open TradingView Alert from the same chart and timeframe you want to monitor.

  2. 02

    Select GUMORBVX as the first Condition.

  3. 03

    Choose “Any alert() function call”. The Pine script controls event frequency internally.

  4. 04

    Keep the alert interval identical to the chart—for example, use 15m for the 15m chart.

  5. 05

    Choose the TradingView notifications you want: App, toast, email, or sound. Webhook is only for a service you own and understand.

  6. 06

    Create a separate alert for every timeframe you actively use.

  7. 07

    After changing indicator settings or receiving a new script version, recreate the relevant alerts so the server snapshot matches.

TradingView Alerts and TelegramOpen full-size image
Correct alert structure: GUMORBVX as the condition, Any alert() function call, and an interval that matches the chart. Indicator setting changes do not update an existing alert snapshot, so recreate it after important changes.
EXAMPLE ALERT MESSAGE
GUMRAI ORB VX • TP2 REACHED • BE ACTIVE
MAIN • BUY
Entry Zone: 4357.33 - 4359.33
SL: 4353.33
TP1: 4363.33 • TP2: 4366.33
TP3: 4370.33 • TP4: 4375.83
TP5: 4383.33 • TP6: 4393.33
RUNNER: 4408.33

Prices above are only an example of the human-readable layout. Your live alert uses the current leg, direction, and calculated levels.

TradingView’s official alert() guide

Your personal TradingView alerts

Created from your own chart and TradingView account. You can receive them through the TradingView app, pop-ups, email, or sound, depending on your account settings.

Gumrai Signals on Telegram

A public channel fed by alerts operated by Gumrai. Joining the channel lets you receive that shared feed; it does not connect your personal TradingView alerts to Telegram.

The product does not currently include personal Telegram delivery. Sending your own TradingView alerts to Telegram requires your own bot and webhook service. Never use or request Gumrai’s private gateway credentials.

Join Gumrai Signals
SECTION 11

Settings to know

Control dashboard size, price tags, history, context, and alert groups

Dashboard

Show or hide the summary panel. Dashboard size offers five levels; Large is the largest.

Show current MAIN / ADD 1 plans

Keep the active legs, Entry Zones, SLs, targets, and labels visible.

Show previous plans

Retain older plan zones in gray for chart-history review.

Previous legs to keep

Limit how many completed legs remain drawn to reduce chart clutter.

Show MAIN / ADD result labels

Show the ending state for each completed leg.

Price tag text size

Choose one of five text sizes for prices shown in chart labels.

Universal session boxes / ORB boxes

Optional market-context layers; they do not place orders.

Session High / Low and labels

Control session reference levels, labels, and how many recent sessions remain.

Enable alerts

Master switch for Pine alert() events.

Plan preparing

Notify when a gray candidate plan appears and is still waiting for entry confirmation.

MAIN / ADD entry confirmed

Notify separately when the plan changes from gray preparation to an active colored plan.

TP / Runner

Include target and Runner notifications.

SL / BE

Include stop and break-even state notifications.

Settings to knowOpen full-size image
ORB VX Inputs shown in TradingView. Display controls only change what you see. Alert group switches control which Pine events can be emitted; after changing them, recreate the corresponding TradingView alert.
SECTION 12

Reading multiple plan outcomes

Review closed legs and the current plan without mistaking them for broker executions

Reading multiple plan outcomesOpen full-size image
This image shows completed plan legs on the left and the current MAIN plan on the right. Read each leg from its own Entry / result labels. A check mark means price reached that level; gray labels are retained history, not a new signal.

How to read the result

Read the closed legs on the left separately from the current MAIN plan on the right. Follow each leg from its Entry label to the last checked target or closing result label.

What the plan represents

These are chart-model observations, not brokerage P&L or proof of a user fill. You remain responsible for every MT4/MT5 order, stop, size, and exit.

SECTION 13

Troubleshooting and FAQ

Check access, dashboards, old zones, check marks, and alerts

I cannot find the indicator

Confirm that invite-only access is active for the exact TradingView username and search under Invite-only Scripts.

The dashboard or zones are missing

Open indicator Settings, enable Dashboard and Entry/TP/SL lines, then confirm the supported symbol and timeframe.

Old zones are missing

Enable Show previous plans. Old plans are intentionally gray.

A completed TP has no check mark

Wait for the chart to finish loading, confirm the correct timeframe, and compare the candle high/low with the exact target.

Alerts are missing or too frequent

Check the alert log, condition, and interval. Recreate alerts after a settings or script-version change.

GUMRAI ORB VX

Ready to see the product options?

Review access periods or request a 30-day full-version trial.

Back to product