AIMS Wave in the Suite

AIMS Wave (license name: The Elliott Wave Indicator) adds Elliott wave structure to the Confluence Indicator Suite. On MT5 it appears as AIMSWaveMT5 in Navigator and as the Wave tab inside the unified dashboard.

Wave answers: which wave is the market in, where are the targets, and is counter-wave risk elevated? Setup 1 Confluence uses those facts together with Box structure — wave alone is not a trade signal.

Attach and activate

1. Activate Elliott Wave Indicator MT5 at my.itradeaims.net — see Install on MT5.
2. Drag AIMSWaveMT5 from Navigator → Indicators → iTradeAIMS onto the chart (or load a saved chart template).
3. Confirm the Wave status pill is live and License Center shows Live Active for Elliott Wave.

You need sufficient history bars on the symbol and timeframe before wave counts populate. If Wave fields show —, wait for more bars or check that Wave is attached.

Wave tab (dashboard)

Open the Wave tab on the iTradeAIMS Dashboard when reviewing Setup 1 or reading Setup 1 Confluence.

Element	What it tells you
Wave count / phase	Current Elliott wave position (for example Wave 3 impulse, Wave 4 pullback)
Target zones	Distance and room toward the next wave target
Counter-wave risk	Whether structure suggests elevated risk against the prevailing count
Direction context	Whether wave bias supports buy or sell alignment with Box

The tab shows raw wave facts. Quality tiers (HIGH, CAUTION, AVOID) appear in Setup 1 Confluence, not on the Wave tab alone.

Wave tab plus on-chart AIMS Wave panel — use both when reviewing Setup 1 Confluence.

On-chart display

Besides the tab, AIMS Wave draws on the chart:

• Wave labels — annotated wave numbers on price structure.
• AIMS Wave histogram — companion visual for wave rhythm (build-dependent).
• Target zone markers — areas where extension or completion risk often rises.

On-chart wave labels pair with the Wave tab — read both before trusting a combined confluence read.

Teaching point: wave count is a structural hypothesis on completed bars. If labels disagree with recent price action, wait for the indicator to refresh after structure closes.

How wave feeds Setup 1 Confluence

Setup 1 Confluence fuses AIMS Wave + AIMS Box Setup 1 lifecycle.

Confluence field	Wave contribution
Direction	Buy/sell when wave bias and box direction agree
Wave / target	Stage (for example Wave 4) and room to next target
Quality	Late-wave extension into targets → often CAUTION or AVOID
Status	WAIT if wave data missing; ARMED when structure aligns but breakout not fired; TRIGGERED when cross-layer rules complete

Common wave scenarios

Wave context	Typical confluence effect
Early impulse (for example Wave 3) with room to target	Supports HIGH or ARMED when Box is READY
Pullback phase (for example Wave 4) with Box Setup 1 READY	Often ARMED — structure valid, waiting on breakout or Banana
Late extension near target zone 1	CAUTION — limited reward to next target (method often cites under ~2R)
Counter-wave risk elevated	Downgrades quality even if Box tab looks READY
Wave fields —	Setup 1 Confluence may show WAIT or UNKNOWN

Bullish completed wave count — Wave tab, on-chart labels, and Setup 1 Confluence read together. Wave alone is context, not a trade signal.

Early impulse context — pair wave stage with Box Setup 1 before reading quality.

Late **Wave 5** extension — often maps to **CAUTION** when reward to the next target is marginal.

Bearish wave context (examples)

Bearish alignment — confirm direction on both Wave tab and Setup 1 Confluence.

Counter-wave risk elevated — quality may downgrade even when Box structure looks valid.

Setup 1 Confluence ARMED (live example)

When Box Setup 1 is confirmed and confluence layers align, Setup 1 Confluence can show ARMED — structure is valid, breakout or Banana may still be pending.

Setup 1 Confluence **ARMED** — Box raw signal confirmed by confluence layers. This is Box + Confluence, not Banana Confluence alone.

Box READY + confluence CAUTION

A READY Box tab with CAUTION on Setup 1 Confluence usually means structure is valid but wave context adds a downgrade reason — not a dashboard bug.

See Confluence reads and Confluence status model.

Wave and Box together

Many suite setups pair:

1. Box tab — grey zone, Setup 1 lifecycle, filters (Gator, Purple, ATR).
2. Wave tab — whether the box setup sits in a wave phase that supports the direction.

Example review flow:

1. Box shows Setup 1 · READY (not Blocked).
2. Wave shows pullback phase aligned with box direction.
3. Setup 1 Confluence shows ARMED + CAUTION if reward to the next target is marginal.
4. Banana Confluence may still show Waiting until a pullback signal fires.

Wave 4 pullback paired with Box — typical **ARMED** watchlist territory.

Box + wave pullback — read Box tab state before Setup 1 Confluence quality.

Full box methodology: Using AIMS Box levels.

History bars (100–150 rule)

AIMS Wave needs enough closed bars on the chart before Elliott counts stabilize. As a rule of thumb, load roughly 100–150 bars on your symbol and timeframe so you can see a full 1–5 impulse sequence (and the pullback that follows) without the count resetting every few candles.

Check	Why it matters
Zoom out or scroll left	Short history hides Wave 4–5 context
Match timeframe to your setup	M5/M15 teaching examples use different bar counts
Wait after attach	Labels populate after sufficient history loads

The screenshots below walk through the bar-count teaching series on MT5.

Step 1 — confirm enough history is visible before trusting wave labels.

Step 2 — count spans the full 1–5 structure, not just the latest swing.

Step 4 — verify wave context before pairing with Box Setup 1.

Settings tie-in

Indicator property Maximum history bars controls how much data Wave reads — align it with this visibility rule when counts look truncated.

Wave and Banana Confluence

Banana Confluence asks whether pullback facts support the wave + box story. Wave stage indirectly affects whether Banana reads as Continuation, Add-on, Waiting, or Conflict.

If Wave points one way and Banana tab shows INVALID against that direction, treat Banana Confluence cautiously even when Box is READY.

Settings (overview)

Open AIMSWaveMT5 → Properties → Inputs on the chart for core wave logic, display toggles, AO tools, and W5 alerts.

**Inputs** (top) — history search, W4 thresholds, Purple quality, and on-chart label colours.

**Inputs** (lower) — zero levels, AO bar-count tools, and W5 alert toggles.

Key inputs include:

• Completed bars searched for W3 AO peak — how far back wave logic scans.
• Maximum AO histogram bars to colour — AO window display depth.
• Print wave 3/4/5 on price chart — on-chart Elliott labels.
• Alert when W5 is on completed bar 1 — W5 alert master switch.

When W5 completes on the completed bar, AIMS Wave can raise an on-screen alert (if enabled). Pair the popup with the Wave tab and Setup 1 Confluence — late-wave extension often maps to CAUTION or AVOID.

Wave 5 completion alert — dashboard Wave tab and on-chart popup together. Review quality tier before acting.

If wave counts look wrong after a symbol or timeframe change, verify history depth and allow the chart to load enough bars.

Troubleshooting

Symptom	What to check
Wave tab fields —	Wave not attached; insufficient bars; license not live
On-chart labels missing	Wave attached but display toggles off in settings
Wave count seems stale	Wait for bar close; switch timeframe and back; re-attach indicator
Setup 1 Confluence WAIT with good Box	Wave missing or wave stage not yet complete

More: Troubleshooting.

MT4 and TradingView

The full Confluence suite with Wave tab is MT5. AIMS Wave may ship on other platforms as standalone products — those builds do not include Setup 1 Confluence. This page applies to the MT5 suite only.

Related

• Box tab in the suite
• Banana tab in the suite
• Unified dashboard
• How confluence works