[wsjt-devel] Tr: Re: [SPAM] Re: WSJT Reporting to PSK Reporter

Sorry, I forgot the attachments.   Envoyé: vendredi 1 février 2019 à 08:41 De: t...@gmx.fr À: wsjt-devel@lists.sourceforge.net Objet: Re: [wsjt-devel] [SPAM] Re: WSJT Reporting to PSK Reporter Hi George,   Thanks for the tip.   I don't think the speed of PSKReporter is to blame for anythin

Re: [wsjt-devel] [SPAM] Re: WSJT Reporting to PSK Reporter

Hi George,   Thanks for the tip.   I don't think the speed of PSKReporter is to blame for anything. Yesterday (and before yesterday) I made some contacts and quickly I could see the one and only reporting from 9M2CNC, a station using a Red Pitaya. I do not know how it could resolve my location

[wsjt-devel] FT8 diversity patch

Hello! Following some discussion on this forum, where I was too noisy, make me think. When joining two uncorrelated FT8 frames (taken on exactly same frequency, but not at the same time) main problem is how to synchronize all tones? My solution is to shift frames 7 times and do decoding after

Re: [wsjt-devel] Microsoft Update Bug Has Bitten

What rig driver are you using in WSJT-X? Mike On Thursday, January 31, 2019, 2:04:49 PM CST, berger...@aol.com wrote: FLEX 6700 using DAX audio, WIN 10 ver 1803 OS build 17134.523 HP I7 computer, SSDR 2.4.9 and WSJT-x V2.0.0 In a message dated 1/31/2019 13:55:26 Eastern Standard Time

Re: [wsjt-devel] WSJT Reporting to PSK Reporter

Bill, many thanks for providing the link to that information, your suggestion works thank you. I’m not sure what you mean by “ ..not bother reading..” as following the link you gave in your email allowed me to see your message for the first time. My experience of trying to send own messages eit

Re: [wsjt-devel] Microsoft Update Bug Has Bitten

Flex software is at 2.4.9 WSJT-x is at 2.0.0 Too many numbers! George J Molnar KF2T - Virginia, USA > On Jan 31, 2019, at 4:08 PM, Richard Solomon wrote: > > Let me try that. > > Tnx, Dick, W1KSZ > > Sent from Outlook > From: Al Pawlowski > Sent: Thursday, January 31, 2019 10:15 AM > To: WS

Re: [wsjt-devel] Microsoft Update Bug Has Bitten

Let me try that. Tnx, Dick, W1KSZ Sent from Outlook From: Al Pawlowski Sent: Thursday, January 31, 2019 10:15 AM To: WSJT software development Subject: Re: [wsjt-devel] Microsoft Update Bug Has Bitten Try turning up the “sleep after” an

Re: [wsjt-devel] Microsoft Update Bug Has Bitten

Ver. 2.4.9 ?? I am using Ver. 2.0.0, I didn't know there were other versions . 73, Dick, W1KSZ Sent from Outlook From: Bill Barrett Sent: Thursday, January 31, 2019 10:33 AM To: WSJT software development Subject: Re: [wsjt-devel] Microso

Re: [wsjt-devel] FT8 4m frequencies - was FT8 Freqs

Asked around on ON4KST and no-one has any strong view Lot of stations setting up skeds on 70.154 so would say unless there is a dev issue then for FT8 Region 1 it would be beneficial to set default in table to 70.154 73’s Tom GM8MJV (IO85) On 30 Jan 2019, at 16:21, Tom Melvin wrote: >

Re: [wsjt-devel] Microsoft Update Bug Has Bitten

FLEX 6700 using DAX audio, WIN 10 ver 1803 OS build 17134.523 HP I7 computer, SSDR 2.4.9 and WSJT-x V2.0.0 In a message dated 1/31/2019 13:55:26 Eastern Standard Time, wsjt-devel@lists.sourceforge.net writes: What is your rig and audio setup? de Mike W9MDB On Thursday, January 31, 2019, 12:51

Re: [wsjt-devel] Microsoft Update Bug Has Bitten

Hello berger...@aol.com I noticed two key things in your post that stand out as the possible problem. You mention you are using Flex SmartSDR and that when you close the program with the window X in the top right, it remains in the background consuming CPU time. There is a known random sporadic i

Re: [wsjt-devel] Microsoft Update Bug Has Bitten

What is your rig and audio setup? de Mike W9MDB On Thursday, January 31, 2019, 12:51:07 PM CST, bergeracb--- via wsjt-devel wrote: I have been fighting this problem for months so I don't know if it is a Microsoft update or not.When it strikes me nothing I do to either SSDR or WSJT-

Re: [wsjt-devel] Microsoft Update Bug Has Bitten

I have been fighting this problem for months so I don't know if it is a Microsoft update or not.When it strikes me nothing I do to either SSDR or WSJT-X makes any difference in allowing wsjt-x to transmit. Closing WSJT-X with the red X at this stage only moves WSJT-X to the background tasks sect

Re: [wsjt-devel] Microsoft Update Bug Has Bitten

Hello Dick- This may or may not help your issue; There is a problem in V2.4.9 that causes the Tune button not to work. I have found the problem when operating multiple panadapters that are on different modes. IE Working CW on a panadapter and then clicking TX on WSJT that's on a different panadapt

Re: [wsjt-devel] Microsoft Update Bug Has Bitten

Try turning up the “sleep after” and “screen off after” controls so that your computer does not go to sleep and screen does not power down. The audio connection (via VAC) between WSJT-X and my SDR program goes out after wakeup from sleep, and/or screen off, which is fixed only when WSJT-X and th

Re: [wsjt-devel] Microsoft Update Bug Has Bitten

Richard Solomon kirjoitti 31.1.2019 klo 18.43: I recently had an update installed by Microsoft. I now find that if I leave FT8 running for a time, I can no longer Transmit (Tune button does not work). If I am active on FT8 all is well, so I can only surmise Microsoft has re-arranged my Compu

[wsjt-devel] Microsoft Update Bug Has Bitten

I recently had an update installed by Microsoft. I now find that if I leave FT8 running for a time, I can no longer Transmit (Tune button does not work). If I am active on FT8 all is well, so I can only surmise Microsoft has re-arranged my Computer. Any ideas what I should look for ? Tnx, Dick

Re: [wsjt-devel] [SPAM] Re: WSJT Reporting to PSK Reporter

Phil, May I recommend JT-Bridge by SM0THU as a replacement for JT-Alert on your Mac? It works well. There have been several episodes of slow (or no) performance on PSKReporter lately. I understand the volume of traffic is extremely high and taxing Phil’s free service and volunteer time. Geor

Re: [wsjt-devel] Received report not being logged

On 31 Jan 2019 at 6:14, Gene H wrote: > Yes, we have noticed this routinely with compound callsigns. It likely > is related to the complexity of compound callsigns and lack of number of > bits to send all information. I noticed if you hover your mouse over the > *Settings > General* tab on top

Re: [wsjt-devel] Received report not being logged

Noticed the same thing here when working any call that invokes the display of the call inside < >. I now look at the reports and the start time in the log window every QSO before hitting OK to send to the log(s).73 de KV4ZY Doug Original Message Subject: [wsjt-devel] Received re

Re: [wsjt-devel] Received report not being logged

Yes, we have noticed this routinely with compound callsigns. It likely is related to the complexity of compound callsigns and lack of number of bits to send all information. I noticed if you hover your mouse over the *Settings > General* tab on top of the *Station Details* "Message generation f

[wsjt-devel] Received report not being logged

Hello all, I'm running WSJT-X v2.0.0 r784f75 on a PC with 32-bit Win 7 Pro. I've discovered that for a few of my recent QSOs the received-report field didn't get populated when the QSO was logged. I first spotted this when I looked at my QSOs as picked up via UDP by the Logger32 app, and then