Re: [wsjt-devel] ALL.TXT RX freq is not RX DIAL freq

2024-07-30 Thread Reino Talarmo via wsjt-devel
My humble opinion is that the reported frequency should be sum of the frequency display and the waterfall frequency. That’s in case those are really what is actually transmitted. Joe’s case is a bit different and in that sense a selection may be needed. 73, Reino OH3mA From: Black Micha

Re: [wsjt-devel] ALL.TXT RX freq is not RX DIAL freq

2024-07-30 Thread Hasan N0AN via wsjt-devel
The problem with adding the DF offset is when the frequency is published/spotted, (like on QRZ or DXSummit), it is listed as 14.09175...which is NOT the frequency that you need your radio tuned to for CAT control. If you click on a spot and have CAT control, you will be on the wrong freq. In the

Re: [wsjt-devel] ALL.TXT RX freq is not RX DIAL freq

2024-07-30 Thread Black Michael via wsjt-devel
There's a difference between the cluster spotting system and pskreporter. Cluster spotting includes CW for example (and primarily too) where you need to know the carrier frequency and you have your own custom offset tone. FT8-type modes are notably different.  On the cluster spotting you will g

Re: [wsjt-devel] ALL.TXT RX freq is not RX DIAL freq

2024-07-30 Thread Hasan N0AN via wsjt-devel
Mike, Tnx clarification, 73 N0AN On Tue, Jul 30, 2024, 8:21 AM Black Michael wrote: > There's a difference between the cluster spotting system and pskreporter. > > Cluster spotting includes CW for example (and primarily too) where you > need to know the carrier frequency and you have your own

Re: [wsjt-devel] ALL.TXT RX freq is not RX DIAL freq

2024-07-30 Thread Alan via wsjt-devel
Maybe I've missed the point on this thread, but since WSJT-X is only a USB signal why can't we keep it simple and report/log just the Rx dial frequency? That then avoids complicated and maybe unknown Tx offset and split calculations, with other people being able to find the Tx easily also with

Re: [wsjt-devel] ALL.TXT RX freq is not RX DIAL freq

2024-07-30 Thread Andy Durbin via wsjt-devel
"So for computer control, it is much better to not include the offset in the frequency in the spot...so you don't have to do math in your head or guess at the offsets, for your vfo to be set to the proper freq. 73, N0AN" I am in complete agreement with this. I would also add that it is not corre

Re: [wsjt-devel] ALL.TXT RX freq is not RX DIAL freq

2024-07-30 Thread Black Michael via wsjt-devel
SSB may be suppressed carrier but is NOT MFSK. CW, Phone, and Digital are 3 separate modes. CW -- we want carrier because we set our own tone offset.  You still have to look at where they have their tone offset. Phone -- suppressed carrier -- tone offset does not matter at all so your comparison

[wsjt-devel] Fw: ALL.TXT RX freq is not RX DIAL freq

2024-07-30 Thread Andy Durbin via wsjt-devel
"Digital -- we need need the "real" transmit frequency -- i.e. the tone offset." When I spot an FT8 station with manual entry to DXSummit.fi I always enter the suppressed carrier frequency. If you check there you will see that most spotters do the same. When I use DXKeeper to make a spot it u

Re: [wsjt-devel] ALL.TXT RX freq is not RX DIAL freq

2024-07-30 Thread Gary McDuffie via wsjt-devel
> On Jul 30, 2024, at 08:25, Alan via wsjt-devel > wrote: > > Maybe I've missed the point on this thread, but since WSJT-X is only a USB > signal why can't we keep it simple and report/log just the Rx dial frequency? My mind follows this very easily. Posting a carrier frequency of their t

Re: [wsjt-devel] ALL.TXT RX freq is not RX DIAL freq

2024-07-30 Thread k0vm via wsjt-devel
You  will  find them by going  to  the dial frequency.. They'll be in the pass band to  decode if they're strong enough. If you put your dial on their tx frequency, you'll never decode them. They'll be below  your rx passband. AL, K0VM On 7/30/2024 3:44 PM, Gary McDuffie via wsjt-devel wrote:

Re: [wsjt-devel] ALL.TXT RX freq is not RX DIAL freq

2024-07-30 Thread Hasan N0AN via wsjt-devel
I think the proposed solution is worse than alleged problem. All one has to do is enter or select the drop down freq...CAT will change the VFO, the resulting passband will be 0 - 3000 Hz or whatever your rx supports..and the signals will be there. What is the problem? It's not as if we are in a F

Re: [wsjt-devel] ALL.TXT RX freq is not RX DIAL freq

2024-07-30 Thread Gary McDuffie via wsjt-devel
> On Jul 30, 2024, at 15:11, k0vm via wsjt-devel > wrote: > > If you put your dial on their tx frequency, you'll never decode them. > They'll be below your rx passband. > AL, K0VM Is that supposed to argue with my comment (which is what you replied to)? Gary - AG0N _

Re: [wsjt-devel] ALL.TXT RX freq is not RX DIAL freq

2024-07-30 Thread Andy Durbin via wsjt-devel
"All one has to do is enter or select the drop down freq...CAT will change the VFO, the resulting passband will be 0 - 3000 Hz or whatever your rx supports..and the signals will be there." Where in the user guide does it say that these are the only methods of tuning the rig that are acceptable?

Re: [wsjt-devel] ALL.TXT RX freq is not RX DIAL freq

2024-07-30 Thread Joe Taylor via wsjt-devel
Well, Andy, I've now told you twice what you need to do. If you want to do it another way, WSJT-X is open source so you can do so. If you want to submit patches or updates for the User Guide, you can do so. WSJT-X is a cooperative project: we encourage and depend on helpful input from users.