You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yesterday I was trying to work SV1GA/A on 17M CW like 10,000 other operators. I had a weird occurance 3 times where I would be sending my call clicking on a CW macro button I had defined and all of the sudden it would just be sending my callsign continously.
For my rig control to my Yaesu FTDX-101D I start rigctld in a terminal window before starting QLog so typically I share my rig connection with QLog and WSJT-X using the hamlib rigctl rig. When the looping would occur I would have to kill rigctld to make it stop, after first pressing the breakin button on my rig to stop the transmissions. I'm not sure where the loop is occuring. I was thinking at the time it may have been caused by me hitting the Macro with a double click or something. But I turned break-in on my rig this morning and tried to duplicate it and I couldn't.
I am not sure if the problem may be a bug in QLog or HamLib. I don't remember if QLog was showing an error message or not when it happened, I think the rig may have disconnected and it was still sending but I am not 100%. I will try and pay closer attention if it happens again. I was tuning up and down while in split when I was sending my call, moving around in the mess until I was fortunate enough to get through.
73
Michael, AA5SH
The text was updated successfully, but these errors were encountered:
Yesterday I was trying to work SV1GA/A on 17M CW like 10,000 other operators. I had a weird occurance 3 times where I would be sending my call clicking on a CW macro button I had defined and all of the sudden it would just be sending my callsign continously.
For my rig control to my Yaesu FTDX-101D I start rigctld in a terminal window before starting QLog so typically I share my rig connection with QLog and WSJT-X using the hamlib rigctl rig. When the looping would occur I would have to kill rigctld to make it stop, after first pressing the breakin button on my rig to stop the transmissions. I'm not sure where the loop is occuring. I was thinking at the time it may have been caused by me hitting the Macro with a double click or something. But I turned break-in on my rig this morning and tried to duplicate it and I couldn't.
I am not sure if the problem may be a bug in QLog or HamLib. I don't remember if QLog was showing an error message or not when it happened, I think the rig may have disconnected and it was still sending but I am not 100%. I will try and pay closer attention if it happens again. I was tuning up and down while in split when I was sending my call, moving around in the mess until I was fortunate enough to get through.
73
Michael, AA5SH
The text was updated successfully, but these errors were encountered: