# Frequency range with CW to avoid FT8 spots

**URL:** https://forum.hamalert.org/t/frequency-range-with-cw-to-avoid-ft8-spots/2411
**Category:** Feature Requests
**Created:** [March 30, 2026, 11:10am UTC](https://forum.hamalert.org/t/frequency-range-with-cw-to-avoid-ft8-spots/2411 "2026-03-30T11:10:27Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![SM0HRP](https://forum.hamalert.org/letter_avatar_proxy/v4/letter/s/a183cd/32.png) [@SM0HRP](https://forum.hamalert.org/u/SM0HRP)
#### Post date: [March 30, 2026, 11:10am UTC](https://forum.hamalert.org/t/frequency-range-with-cw-to-avoid-ft8-spots/2411/1 "2026-03-30T11:10:27Z")

</div>

Is there a a way to have fixed frequencies (identified frequencies as CW) as an option to automatically identifies as Cw and not FT8. Now I get a massive amount of CW alerts when actually they are on FT8.

---

<div class="post-metadata">

### Author: ![N8FYL](https://forum.hamalert.org/letter_avatar_proxy/v4/letter/n/aca169/32.png) [@N8FYL](https://forum.hamalert.org/u/N8FYL)
#### Post date: [March 30, 2026, 7:49pm UTC](https://forum.hamalert.org/t/frequency-range-with-cw-to-avoid-ft8-spots/2411/2 "2026-03-30T19:49:24Z")

</div>

I configure my trigger for Mode: CW, and sources RBN, Cluster, and PSK Reporter and I don’t seem to see any reports for FT items. 73, John/N8FYL

---

<div class="post-metadata">

### Author: ![SM0HRP](https://forum.hamalert.org/letter_avatar_proxy/v4/letter/s/a183cd/32.png) [@SM0HRP](https://forum.hamalert.org/u/SM0HRP)
#### Post date: [March 30, 2026, 7:57pm UTC](https://forum.hamalert.org/t/frequency-range-with-cw-to-avoid-ft8-spots/2411/3 "2026-03-30T19:57:28Z")

</div>

Thanks. I did not have the sources added. I hope this will do it.

---

<div class="post-metadata">

### Author: ![SM0HRP](https://forum.hamalert.org/letter_avatar_proxy/v4/letter/s/a183cd/32.png) [@SM0HRP](https://forum.hamalert.org/u/SM0HRP)
#### Post date: [March 30, 2026, 8:06pm UTC](https://forum.hamalert.org/t/frequency-range-with-cw-to-avoid-ft8-spots/2411/4 "2026-03-30T20:06:42Z")

</div>

Still this spot.

 ![IMG_5235](https://forum.hamalert.org/uploads/default/original/1X/534a177f88dc273b0f3d121177839c112aaa79bf.png)

---

<div class="post-metadata">

### Author: ![HB9DQM](https://forum.hamalert.org/user_avatar/forum.hamalert.org/hb9dqm/32/5_2.png) [@HB9DQM](https://forum.hamalert.org/u/HB9DQM)
#### Post date: [March 31, 2026, 7:12am UTC](https://forum.hamalert.org/t/frequency-range-with-cw-to-avoid-ft8-spots/2411/5 "2026-03-31T07:12:44Z")

</div>

That spot came from the RBN and was marked as CW, so from HamAlert’s point of view, it was correct to send an alert. Could it have been a pirate on 28.040 CW perhaps?

If you want to avoid this particular case, I’d recommend that you remove RBN from your “Source” condition.

---

<div class="post-metadata">

### Author: ![SM0HRP](https://forum.hamalert.org/letter_avatar_proxy/v4/letter/s/a183cd/32.png) [@SM0HRP](https://forum.hamalert.org/u/SM0HRP)
#### Post date: [March 31, 2026, 12:34pm UTC](https://forum.hamalert.org/t/frequency-range-with-cw-to-avoid-ft8-spots/2411/6 "2026-03-31T12:34:30Z")

</div>

Hi! Ok I see. I got perhaps 20 pcs like that. I will try. It is quite common they send Ft8 spots as CW from RBN. Happy Easter!