Ok rc4 is deep past for me.
Liked On: 30.01.2024, 17:56
FC is set automatically, common band false, dxped band true. Can be verified from Dxped menu.
Liked On: 21.01.2024, 13:59
Hound in JTDX 1. changes available message sequences and counters on repeating. 2. Does Frequency control. Frequency control is done only when: 1. Some kind of split is configured and working...
Liked On: 20.12.2023, 21:16
Hound in JTDX 1. changes available message sequences and counters on repeating. 2. Does Frequency control. Frequency control is done only when: 1. Some kind of split is configured and working...
Liked On: 20.12.2023, 20:36
Hound in JTDX 1. changes available message sequences and counters on repeating. 2. Does Frequency control. Frequency control is done only when: 1. Some kind of split is configured and working...
Liked On: 20.12.2023, 19:04
Exactly.
Liked On: 24.09.2023, 12:23
Exactly.
Liked On: 22.09.2023, 15:12
Exactly.
Liked On: 22.09.2023, 10:55
I intentionally removed enabling Tx from udp. Only way to prevent using JTDX as a slave for qso robots using udp. Sry.
Liked On: 19.09.2023, 21:50
Exactly, when weak cpu and decoding time goes more than 15 sec, then next period will be bypassed.
Liked On: 28.07.2023, 11:45
Exactly, when weak cpu and decoding time goes more than 15 sec, then next period will be bypassed.
Liked On: 28.07.2023, 09:48
Exactly, when weak cpu and decoding time goes more than 15 sec, then next period will be bypassed.
Liked On: 28.07.2023, 09:19
Exactly, when weak cpu and decoding time goes more than 15 sec, then next period will be bypassed.
Liked On: 28.07.2023, 08:40
if last logged QSO was VP8KCC on 10m and next try to log was VP8KCC on 20m then it looks like bug in JTDX, it traps to double logging protection, incorrectly.
Liked On: 01.06.2023, 15:01
if last logged QSO was VP8KCC on 10m and next try to log was VP8KCC on 20m then it looks like bug in JTDX, it traps to double logging protection, incorrectly.
Liked On: 30.05.2023, 10:36