|
Post by n6krj on Mar 10, 2023 20:07:46 GMT
New to JTDX, experience with WSJT-X. Using v.2.2.159-32A on an Intel Mac running MacOS 11.7.4. When I try to respond to a CQ, with "Enable TX" or double-clicking a call. I'm seeing erratic behavior. 1. Sometimes "it just works". QSO works as expected. 2. Frequently it will Tx 1 to 4 times, and then just quit. 3. Often it just won't Tx at all. Restarting the app sometimes fixes the problem, but more often than not, it does nothing - often just get's worse. Other peculiarities. Seems to ignore USB Output Gain from my IC-7300. I can slide the device volume to zero in MIDI and set the USB AF output level on the radio to zero, and the meter on the right still parks itself at around 140db to 180db. Decoding seems to be working fine. Conversely all these settings work fine in WSJT-X. I do use RUMlogNG as rig control for the IC-7300. RUMlogNG is running a DX Lab Suite Commander server. This works flawlessly under WSJT-X - I'd expect it to work in JTDX as well. Not quite sure what's going on or how to proceed. I'm happy to produce debug logs, but not sure how to do so. Not sure where to get a debug build or how to enable debug logging.
|
|
|
Post by K7GQ on Mar 11, 2023 18:28:46 GMT
#2 - change the JTDX "Sequencing" in Preferences to suit your needs. For myself, if someone hasn't replied after two calls, I stop.
#3 - I find sometimes JTDX is unwilling to call if it finds the other station "busy".
|
|