# Waves Trend Signals

## Waves Trend Signals — Trader's Guide (EN)

> **mrD Signals Premium** — How to use **Waves Trend Signals** effectively and combine with **Trend Cloud** to maximize win-rate.

***

<figure><img src="/files/dX6QWBWTf8PnE90HpBrP" alt=""><figcaption></figcaption></figure>

### 1. What are Waves Trend Signals?

Waves Trend Signals are designed to **catch the start of a new trend wave and ride it until exhaustion**. Unlike Contrarian (which catches extreme reversal points), Waves Trend is **selective trend-following** — it only fires when multiple confirmation layers agree.

The engine prints a `STRONG BUY` triangle (▲ green, "STRONG" label) or `STRONG SELL` triangle (▼ red, "STRONG" label) — and every triangle is **the result of multiple filters all giving the green light at once**:

* **Short and medium-term trend agreement**
* **Sufficient signal clarity** (signal exceeds the noise floor)
* **Volume confirmation** (real buying/selling, not a fake breakout)
* **Multiple protective filters passed** (anti-sideways, anti-counter-trend)
*

```
<figure><img src="/files/pU8OOYYXJ7xCjv6TDUUh" alt=""><figcaption></figcaption></figure>
```

> The strength: signals are **rare but high-quality**. The catch: you still need to filter with Trend Cloud — the same triangle can be A+ quality or junk depending on the regime around it.

#### Bar coloring — the fast trend filter

Alongside the triangles, every bar gets colored by the trend logic:

* **Green bar** → price is on the right side of a short-term up trend
* **Red bar** → price is on the right side of a short-term down trend
* **Neutral bar** → "no clear trend" zone → **stay out**

> The bar color is your **regime context**. The triangle is your **entry trigger**.

***

### 2. Profile selector (Signals Swing)

The dropdown **Signals Swing** tunes how strict or loose signals are. **Same triangle, very different responsiveness**:

| Profile                  | Style                                    | Best for                                                         |
| ------------------------ | ---------------------------------------- | ---------------------------------------------------------------- |
| **Short-Term**           | Fast reaction, frequent signals          | **HTF charts** (≥ 1H) or volatile markets                        |
| **Mid-Term** *(default)* | Balanced                                 | Suits most timeframes and assets                                 |
| **Long-Term**            | Strict, fewer but higher-quality signals | **LTF charts** (≤ 1H) — kills intraday noise                     |
| **Auto Detect**          | Picks profile by chart TF                | Let the system decide (high TF → Short-Term, low TF → Long-Term) |

#### Auto Detect logic (worth understanding, not a typo)

> **High TF → less noise → fast settings ok → Short-Term** **Low TF → more noise → heavier filtering → Long-Term**

This isn't a mistake — it's a subtle insight: 1m/5m charts have lots of random noise and need long filters; 1D/1W charts have clean structure and can use short filters to catch waves in time.

#### Quick rules

* Scalping / day-trading (1m–15m chart) → **Long-Term** (kill intraday noise)
* Swing trading (1H–4H chart) → **Mid-Term**
* Position / macro (1D+ chart) → **Short-Term** (responsive)

***

### 3. Why you SHOULD combine with Trend Cloud

> **Waves Trend tells you WHEN to enter. Trend Cloud tells you WHERE to place stops and WHY the trend is still valid.**

#### What Trend Cloud says about your trade

| Trend Cloud                   | STRONG BUY ▲ means...                    | STRONG SELL ▼ means...                   |
| ----------------------------- | ---------------------------------------- | ---------------------------------------- |
| **Green / uptrend**           | Pullback confirmed → **A-grade long**    | Counter-trend → **skip or scalp small**  |
| **Red / downtrend**           | Counter-trend → **skip or scalp small**  | Pullback confirmed → **A-grade short**   |
| **Just flipped**              | Wait 3–5 bars for cloud to settle        | Wait 3–5 bars for cloud to settle        |
| **Dense cloud (high volume)** | Trend has conviction — enter confidently | Trend has conviction — enter confidently |
| **Light cloud (low volume)**  | Weak trend — reduce size                 | Weak trend — reduce size                 |

In short: **Trend Cloud is the regime filter; Waves Trend is the entry trigger inside that regime.**

***

### 4. Recommended setup

#### 4.1 Chart configuration

1. **Indicator overlay** → enable `Trend Cloud`
2. **Signals Detection** → select `Waves Trend Signals`
3. **Signals Swing** → start with `Auto Detect time-frame`; switch manually if you see too many or too few signals
4. (Optional) Enable `DCA Signals Detection` for additional confluence at small pullback points
5. (Optional) Enable `Trail Cloud` for dynamic stop-loss zones

#### 4.2 Pre-trade checklist

* [ ] **Trend Cloud color matches** the signal direction
* [ ] Cloud has held the same color for **at least 5 bars** (no fresh flip)
* [ ] **Cloud is reasonably dense** — not paper-thin
* [ ] **Bar color matches the triangle** (green bar + ▲ / red bar + ▼)
* [ ] Triangle appears **not too far** from current price

5/5 → **A+**, full size 4/5 → **A**, full size 3/5 → **B**, half size ≤ 2 → **skip**

***

### 5. Trading playbook

#### 5.1 LONG — `STRONG BUY ▲` in green cloud

| Step           | Action                                                                                                                                               |
| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Entry**      | Market on signal bar close, **or** limit at the Trend Cloud's base line — whichever fills first                                                      |
| **Stop loss**  | A few ticks **below the Trend Cloud's base line**. If broken → trend filter has flipped, exit immediately                                            |
| **TP 1** (1/3) | At nearest swing high or middle band of the Trend Cloud                                                                                              |
| **TP 2** (1/3) | Trail along the dense core of the cloud — exit if price closes below the core                                                                        |
| **TP 3** (1/3) | <p>Hold and trail the base line — exit only when:<br>① an opposite <code>STRONG SELL ▼</code> prints, or<br>② cloud flips red + bar confirmation</p> |

#### 5.2 SHORT — `STRONG SELL ▼` in red cloud

Symmetrical:

| Step           | Action                                                                   |
| -------------- | ------------------------------------------------------------------------ |
| **Entry**      | Market on signal bar close, **or** limit at the base line                |
| **Stop loss**  | A few ticks **above the base line**                                      |
| **TP 1** (1/3) | At nearest swing low or middle band of the cloud                         |
| **TP 2** (1/3) | Trail along the dense core                                               |
| **TP 3** (1/3) | Trail the base line until the cloud flips green or `STRONG BUY ▲` prints |

#### 5.3 Position sizing

* **A+ / A rating** → 100% standard size
* **B rating** → 50% size
* **Counter-trend** (signal against cloud) → **0% — DO NOT enter**

***

### 6. Tips to boost win-rate (advanced)

#### 6.1 Wait for pullback to the base line

The strongest setup: **price pulls back to or near the Trend Cloud's base line** before the triangle fires. You enter right at the trend's "demand zone" (LONG) or "supply zone" (SHORT) — the best risk/reward.

> Rule: if price is already too far from the base line when the triangle prints, **place a limit at the base line** instead of entering at market. Be patient and wait for the pullback.

#### 6.2 Read the signal-clarity meter

When the same triangle prints, check the system's "signal strength" gauge:

* **Weak / sideways** → stand aside, this isn't a real trend
* **Moderate** → enter half size
* **Strong** → full size, can use leverage
* **Very strong** → very clear trend BUT possibly **near a top/bottom** → caution on size

#### 6.3 Check volume confirmation

Before entering:

* **Strong buying pressure + STRONG BUY** → very strong, hold longer
* **Neutral buying pressure + STRONG BUY** → standard
* **Selling pressure dominates + STRONG BUY** → questionable → **skip**

Mirror logic for SHORT. A signal that volume "doesn't support" is almost always a fake.

#### 6.4 Multi-timeframe agreement

Open higher TF charts (e.g. trading 15m → also check 1H + 4H):

| 15m signal | 1H Trend Cloud | 4H Trend Cloud | Decision           |
| ---------- | -------------- | -------------- | ------------------ |
| ▲ BUY      | Green          | Green          | **A+ — full size** |
| ▲ BUY      | Green          | Red            | **B — half size**  |
| ▲ BUY      | Red            | Red            | **Skip**           |
| ▼ SELL     | Red            | Red            | **A+ — full size** |
| ▼ SELL     | Red            | Green          | **B — half size**  |
| ▼ SELL     | Green          | Green          | **Skip**           |

#### 6.5 Avoid the "first triangle after a fresh flip"

The first triangle right after the cloud flips **often has a lower win-rate** because the system is still confirming the new direction. Best practice:

* Wait for the **2nd or 3rd** triangle after the flip, OR
* Wait **5 bars + cloud still same color** before taking the triangle

#### 6.6 Avoid news / low-liquidity hours

Waves Trend signals during news events or thin sessions are **unreliable** because:

* A single news bar can spike the clarity meter temporarily without follow-through
* The volume indicator gets distorted by abnormal volume
* The base line can be falsely "broken"

> Best trading hours: London open, NY open, Tokyo close. Avoid: early Asia for FX, weekends for crypto, 30 minutes before/after major data releases.

#### 6.7 Switch profile based on volatility

| Situation                 | Action                                                         |
| ------------------------- | -------------------------------------------------------------- |
| Quiet, ranging market     | **Step down** profile (Mid → Short-Term) to catch tight ranges |
| Volatile, trending market | **Step up** (Mid → Long-Term) to filter fakeouts               |
| News-day / earnings       | Switch to **Long-Term** + wait for clear pullback              |
| Crypto weekend            | **Long-Term** or disable indicator                             |

#### 6.8 DCA Signals as secondary entry

<figure><img src="/files/7UzPFuvTlRJKBaxEz0ED" alt=""><figcaption></figcaption></figure>

Enable `DCA Signals Detection` to get small green/red dots at intermediate pullbacks. When:

* **STRONG BUY ▲** appears on 1H + 15m chart has a **green DCA dot** within a few bars after → **double confluence** → very strong setup
* Mirror logic for SHORT

#### 6.9 Dynamic stop loss along the base line

Instead of a fixed stop, use a **dynamic trailing stop hugging the Trend Cloud's base line**: as the base line rises (LONG), the stop rises with it → automatically protects profit when trend continues, automatically exits when trend weakens.

#### 6.10 Don't scale into losing trades

Waves Trend signals are already heavily filtered. If a trade doesn't move in your favor within **3–5 bars after entry** → the reversal/continuation likely failed → **cut the loss immediately**, never average down.

***

### 7. Common mistakes to avoid

1. **Entering against cloud color** — the #1 reason for losing trades. Always confirm Trend Cloud direction first.
2. **Ignoring bar color** — neutral bar = no clear trend = skip.
3. **Stop loss too tight** — Waves Trend fires after confirmation, the next bar may have a wide range. Place stop **below the base line**, not at the signal bar's low/high.
4. **Wrong profile for the timeframe** — Long-Term on 1D chart yields almost no signals; Short-Term on 1m chart is chaos.
5. **Disabling Trend Cloud "to see signals better"** — you just removed the most important regime filter.
6. **Entering counter-trend even on a high rating** — if the cloud is opposite, NEVER enter, even if it "feels right".
7. **Trading when signal clarity is low** — that's the noise zone, not a trend.
8. **Forgetting to check volume confirmation** — volume opposite to signal direction is a major red flag.

***

### 8. Quick reference card

```
╔══════════════════════════════════════════════════════════╗
║       CHECKLIST WAVES TREND + TREND CLOUD                ║
╠══════════════════════════════════════════════════════════╣
║ 1. Trend Cloud color matches triangle?         [Y/N]     ║
║ 2. Cloud held color ≥ 5 bars?                  [Y/N]     ║
║ 3. Cloud dense (high accumulated volume)?      [Y/N]     ║
║ 4. Bar color matches triangle?                 [Y/N]     ║
║ 5. Volume agrees with signal direction?        [Y/N]     ║
║ 6. Higher TF cloud agrees?                     [Y/N]     ║
║                                                          ║
║ 6/6 → A+, 100% size + leverage candidate                 ║
║ 5/6 → A,  100% size                                      ║
║ 4/6 → B,   50% size                                      ║
║ ≤3  → SKIP                                               ║
╠══════════════════════════════════════════════════════════╣
║ ENTRY  : market on triangle OR limit at                   ║
║          the Trend Cloud's base line                      ║
║ STOP   : just past the base line                          ║
║ TP1    : nearest swing / middle band cloud  (1/3)         ║
║ TP2    : trail dense cloud core             (1/3)         ║
║ TP3    : trail the base line                (1/3)         ║
╚══════════════════════════════════════════════════════════╝
```

***

### 9. FAQ

**Q. I see no signals at all?** A. Four common causes:

1. You're on **Long-Term** profile + high TF chart (1D/4H) → too few signals — switch to Mid or Short-Term.
2. Market is **sideways** → signal clarity below threshold → correctly blocked, do not force.
3. **Counter-trend filter** is blocking — check that short / mid / long trends agree.
4. **Persistently weak volume** → wait for volume to appear.

**Q. Signals are too noisy?** A. Step up the profile (Short → Mid → Long) or wait for Trend Cloud confirmation. Mid-Term is the best balance for most assets.

**Q. Does it work on every market?** A. Best on **assets with real volume**: BTC/ETH, FX majors, large-cap indices, blue-chip stocks. On synthetic CFDs, penny stocks, exotic forex pairs, volume confirmation may be inaccurate.

**Q. Can I use it below 1m or above 1W?** A. Sweet spot: **5m – 1D**. Below 1m: spread/fee eats profit. Above 1W: too few signals for statistical reliability.

**Q. Can I automate this?** A. Yes — use the built-in alert blocks. We recommend adding a "Trend-Cloud-color" filter on your webhook receiver: e.g. only forward `BUY` alerts when the cloud is currently green.

**Q. Should I use Waves Trend or Contrarian?** A. Different purposes:

* **Waves Trend** = trend-following, enter with the running trend
* **Contrarian** = reversal, catch tops/bottoms reversal points
* You can use both on the same chart: Contrarian flags the reversal, then Waves Trend confirms and rides the new trend.

***

> **Final word**: Waves Trend Signals is **disciplined trend-following**. The system ensures you only enter when **the trend is truly established AND volume confirms**. Trend Cloud is not optional — it's the **regime filter that turns this from a good system into an excellent one**. Always use them together, always run the checklist, always size positions by rating.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.mrd-indicators.com/feature/tradingview-indicators/mrd-signals-premium-eng/waves-trend-signals.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
