toggle quoted messageShow quoted text
Gordon, the pictures you sent shows that WSJT is using the callsign GM7WCO/P. Lucky you, someone replied to your call. Unfortunately, Logger32 doesn't know who GM7WCO/P is, it thinks the station replied to someone else and abandoned the cherry-picking session. You say 'both are set up to use my call' ... Sorry, I'm not convinced. I can see WSJT thinks your call is GM7WCO/P, I can't see what Logger32 thinks your call is, so my best guess would be GM7WCO? SeventyThree(s).
On 07/07/2020 1:27 AM nodrog79 via groups.io <nodrog79@...> wrote:
I don't follow sorry. Both are set up to use my call.
On Tue, Jul 7, 2020 at 12:19 AM, Bob wrote:
... it would probably be a good idea if the current Logger32 user and the WSJT user had the same callsigns. That way when a called station responded to the WSJT user, Logger32 would know who it was. SeventyThree(s).
On 07/06/2020 7:07 PM nodrog79 via groups.io <nodrog79@...> wrote:
No issues getting stations to reply. You can see it both on wsjtx and logger32.
On Mon, Jul 6, 2020 at 11:50 PM, Bob wrote:
Can you show me a picture where you have actually been in QSO and you have been cut off?. 73.
On 07/06/2020 6:43 PM nodrog79 via groups.io <nodrog79@...> wrote:
I can see why it gives up after the 3 calls. That's fair enough.
On the other attempts the called station has replied to my call with decent reports. My station should then reply with a report etc and hopefully continue the QSO. Logger32 is telling wsjtx to halt tx.
The latter is happening every time. I call, they reply and the tx halts.