![Jt alert hrd 6](https://kumkoniak.com/46.jpg)
![jt alert hrd 6 jt alert hrd 6](https://www.k0pir.us/wp-content/uploads/2018/04/Snapshot_51.jpg)
HRD v5 and V6 users need to upgrade their JTAlert version to 2.10.0 to avoid logging and spotting the wrong mode (FT8 spotted/logged as T10 or JT9).
![jt alert hrd 6 jt alert hrd 6](https://www.pestingers.net/pages-images/ham-stuff/digital-modes/digital-software/jtalert/jtalert-qth.jpg)
This version has full support for FT8 and the 15sec T/R period. "New JTAlert 2.10.0 is available for download. So far I am impressed but the extra 73 transmission means you don't go back to calling CQ after you have sent a successful RRR and received a 73 from the receiving station.
- WSJT-X Version 1.8.0 Release Candidate 1.
- When a successful packet was received the program went onto the next step in the transmission sequence - transmitting two or three RRR's until a 73 was received for instance. I also noticed it coped well with hiccups in reception where nothing was received or decoded from the answering station in the middle of a QSO.
These tend to take around 1 second at around the 13th second of the receive cycle. I believe you need a fast PC though to cope with decodes. Overs are 15 seconds long so FT8 can cope with fading QSOs. I didn't have to add FT8 to HRD as some people have queried on the HRD peer support Facebook group as it was done automatically.įT8 Waveform in the waterfall. It all worked seamlessly and the logging was intercepted by JTAlert and passed via QSO Relay to Ham Radio Deluxe logging module. Then the program went back to transmitting CQ again. SP6ECQ G8YPH 73 - this was transmitted automatically as a courtesy