Date   

locked Re: WSJT-X to N3FJP AC Log Interface

Jim Cooper
 

On 10 May 2020 at 13:05, Jim Shorney wrote:

We should walk in the shoes of (all) of the
developers before we criticize
We should also pick our software packages
based on the functions they provide vs. the
functions that we want.

Not smart, if you need a truck, to go buy
a mini-Cooper ... also not wise to ask the
mini manufacturer to adapt their design
so it can be a truck.

If you don't like what any of these ham
software packages do, you can always ask
for a refund ...


locked Re: Curved Line in Waterfall

Dave (NK7Z)
 

Hi,

It looks like a carrier started at the bottom of your screen, (or you came upon it at that point), at around 1230 Hz, higher than your dial frequency, and over the period of one minute moved upwards in frequency. This assumes the graticule marks are 100 Hz apart, and 15 seconds apart on the vertical.

This could be pretty much anything, heater, thermostat, controller for stoves, etc... All you really know is some signal moved up in frequency across a one minute period.

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist
ARRL Asst. Director, NW Division, Technical Resources

On 5/10/20 9:17 AM, Brian Wilkins wrote:
I was listening on 17m today. What causes this curved line in the waterfall?
 Link to picture
https://imgur.com/alQtCKV
--
Brian Wilkins
KO4AQF


locked Re: WSJT-X to N3FJP AC Log Interface

Jim Shorney
 

I can appreciate that. I started out with paper logging as well in the mid 70s. I still do a lot manually that today's hams insist on using computer control for, but for logging I find that the software communication improves my accuracy. Yes, I make typos! I always confirm what was logged of course. The software load here is pretty stable, once I set it all up it just keeps running. Of course most of the critical stuff runs in Linux. All bets are off with Windows. What I do see from the volume of support emails in various forums is that the real time sink is keeping CAT running. :)

73

-Jim
NU0C

On Sun, 10 May 2020 18:22:04 +0000
"Chuck K4RGN" <K4rgn@...> wrote:

Personally I choose to run N3FJP ACL independently of WSJT-X (and of fldigi too). It’s little effort to type in the log entry, and it increases the sense of actively operating my station. Also, I’d rather spend my time on other projects than installing even more shack software. I confess that I began with pen and paper logbooks in 1970. But with 7000+ FT8 QSOs I haven’t tired of manual logging yet.

73 Chuck K4RGN


locked Re: WSJT-X to N3FJP AC Log Interface

Chuck K4RGN
 

Personally I choose to run N3FJP ACL independently of WSJT-X (and of fldigi too). It’s little effort to type in the log entry, and it increases the sense of actively operating my station. Also, I’d rather spend my time on other projects than installing even more shack software. I confess that I began with pen and paper logbooks in 1970. But with 7000+ FT8 QSOs I haven’t tired of manual logging yet. 

73 Chuck K4RGN


locked Re: WSJT-X to N3FJP AC Log Interface

Jim Shorney
 

On Sun, 10 May 2020 13:40:27 -0400
"Joe Subich, W4TV" <lists@...> wrote:

Scott has the typical "not invented here" syndrome.
That's a little unfair. Scott's perspective is not unlike that of the WSJT-X developers. He worked to create a functional and useful API geared towards the features of his software that many DO support. He actively supports 100+ software packages (by his count) as well as keeping up with a constant stream of support questions via his support forum and private email. We should walk in the shoes of (all) of the developers before we criticize.

73

-Jim
NU0C


locked Re: WSJT-X to N3FJP AC Log Interface

Jim Shorney
 

On Sun, 10 May 2020 10:24:23 -0700
"Steve Wilson via groups.io" <steve_wilson@...> wrote:

Per Scott's site, that is up to WSJT-X to support, not Scott. That is why I posted here.
It is good that you asked, and I appreciate the additional perspective that G4WJS provided. We have two sides with very busy developers who have constraints on their time. They both make valid points and are really saying pretty much the same thing. Which is OK. There are always workarounds.

Personally, I don't like bridge programs. But others do and that is a good alternative for them. I have always run WSJT-X under Linux. It happily talks to SpotCollector running on a Win7 box. The W3DJS Python script runs quietly in the background on the Linux machine and just does its job. I have tested it both talking to ACL on the Win7 box and ACL under WinXP running in a VM on the Linux machine. There are many ways to handle this.

73

-Jim
NU0C


locked Re: WSJT-X to N3FJP AC Log Interface

Joe Subich, W4TV
 

Scott has the typical "not invented here" syndrome.

The WSJT-X developers have chosen to develop/support a generic
UDP broadcast format that is supported by *several* logging
programs. If Scott chooses not to support that interface
already used by multiple applications, that is between him
and his users. There is/should be no expectation that the
WSJTX developers will write a unique interface to support
Scott's proprietary API.

If you need something that supports Scott's API, use JT-Alert.

If you want avoid JT-Alert, tell Scott to get with the program.

73,

... Joe, W4TV

On 2020-05-10 1:24 PM, Steve Wilson via groups.io wrote:
Per Scott's site, that is up to WSJT-X to support, not Scott. That is why I posted here.


locked Re: FT8 Logging Problem!

 

I wondered why people didn't use the "proper sequence". I like to plot my contacts on a map - I use an API available from DxAtlas, and the centre of a prefix area is not good enough. I also download contact details from eQSL and LotW which a lot of times updates gridsquares to the 6 character version.

73 Phil GM3ZZA

On 10 May 2020 16:46, Reino Talarmo <reino.talarmo@...> wrote:

Hi Steve,

Sending message 2 as the first message does not indicate a contest mode at all. Those users just want to save one timeslot.

Reino OH3mA

 

From: WSJTX@groups.io [mailto:WSJTX@groups.io] On Behalf Of Steve Kavanagh via groups.io
Sent: 10. toukokuuta 2020 17:35
To: WSJTX@groups.io
Subject: Re: [WSJTX] FT8 Logging Problem!

 

I had one case where a station (not in contest mode) called me using message 2, so he never sent his grid.  As I understand it, WSJT-X is supposed to switch the non-contest-mode station into contest mode when a contest-mode exchange is received, but this combination of events didn't produce a valid contest QSO.  Not sure if there is a software fix.

I think those of us who are interested in VHF contests need to put on a big educational push so that those VHFers who are not particularly interested in contests learn about contest modes and how and when to use them....they only give up a signal report.  I think the same is true of HF digital contesting, but I have spent less time at that and don't have as much of a feel for how many contest-mode compatibility problems exist there.

73,
Steve VE3SMA



--
73 Phil GM3ZZA


locked Re: WSJT-X to N3FJP AC Log Interface

Steve K6WW
 

Per Scott's site, that is up to WSJT-X to support, not Scott. That is why I posted here.


locked Re: WSJT-X to N3FJP AC Log Interface

Dave Garber
 

if you would rather not use jtalert, then gridtracker will listen on a udp port, and log to a few different logging programs, as selected.

just another option for you
Dave Garber
VE3WEJ / VE3IE


On Sun, May 10, 2020 at 10:56 AM Steve Wilson via groups.io <steve_wilson=yahoo.com@groups.io> wrote:
I know that N3FJP can be interfaced to WSJT-X via JTAlert, but I'd like to toss out my vote for a direct interface. :-)

73!

Steve  K6WW


locked Re: Curved Line in Waterfall

Brian Wilkins <bwilkins@...>
 


Bob

You had me at first. I live on the Space Coast and thought I missed one!

Thanks for the info


On Sun, May 10, 2020 at 12:29 PM K8BL BOB LIDDY <k8bl@...> wrote:
Brian,

That was from a Space-X launch today.

Actually, it's a drifting carrier detected on the WSJTX Waterfall. You'll
see that often on various Bands. Also, you can often see a straight vertical
line from a solid carrier or an interrupted one from CW.

73,     Bob  K8BL

On Sunday, May 10, 2020, 12:17:53 PM EDT, Brian Wilkins <bwilkins@...> wrote:


I was listening on 17m today. What causes this curved line in the waterfall?


 Link to picture

--
Brian Wilkins
KO4AQF

--
Brian Wilkins
KO4AQF


locked Re: Curved Line in Waterfall

 

Birdie drifting. 

On May 10, 2020, at 12:17, Brian Wilkins <bwilkins@...> wrote:


I was listening on 17m today. What causes this curved line in the waterfall?


 Link to picture

--
Brian Wilkins
KO4AQF


locked Re: Curved Line in Waterfall

K8BL BOB LIDDY <k8bl@...>
 

Brian,

That was from a Space-X launch today.

Actually, it's a drifting carrier detected on the WSJTX Waterfall. You'll
see that often on various Bands. Also, you can often see a straight vertical
line from a solid carrier or an interrupted one from CW.

73,     Bob  K8BL

On Sunday, May 10, 2020, 12:17:53 PM EDT, Brian Wilkins <bwilkins@...> wrote:


I was listening on 17m today. What causes this curved line in the waterfall?


 Link to picture

--
Brian Wilkins
KO4AQF


locked Re: FT8 Logging Problem!

Roger
 

And a surprising number of them send RRR and later 73 so they're not actually saving a cycle.

I like to receive the grid so I treat them as in incomplete QSO.

Roger G4HZA

On 10/05/2020 16:46, Reino Talarmo wrote:
Hi Steve,
Sending message 2 as the first message does not indicate a contest mode at all. Those users just want to save one timeslot.
Reino OH3mA
From: WSJTX@groups.io [mailto:WSJTX@groups.io] On Behalf Of Steve Kavanagh via groups.io
Sent: 10. toukokuuta 2020 17:35
To: WSJTX@groups.io
Subject: Re: [WSJTX] FT8 Logging Problem!
I had one case where a station (not in contest mode) called me using message 2, so he never sent his grid. As I understand it, WSJT-X is supposed to switch the non-contest-mode station into contest mode when a contest-mode exchange is received, but this combination of events didn't produce a valid contest QSO. Not sure if there is a software fix.
I think those of us who are interested in VHF contests need to put on a big educational push so that those VHFers who are not particularly interested in contests learn about contest modes and how and when to use them....they only give up a signal report. I think the same is true of HF digital contesting, but I have spent less time at that and don't have as much of a feel for how many contest-mode compatibility problems exist there.
73,
Steve VE3SMA


locked Curved Line in Waterfall

Brian Wilkins <bwilkins@...>
 

I was listening on 17m today. What causes this curved line in the waterfall?


 Link to picture

--
Brian Wilkins
KO4AQF


locked Re: FT4 Freq for 15M

Bill Somerville
 

On 10/05/2020 15:46, David Perry wrote:
What is the FT4 frequency for 15 meter band?  Is it 21,140 kHz?

73,

Dave, N4QS
Hi Dave,

that is the FT4 working frequency suggestion provided with WSJT-X, if your WSJT-X application and rig are not switching to that frequency when switching to 15m in FT4 mode then you may need to reset the "Settings->Frequencies->Working Frequencies" table by right-clicking the table body and selecting "Reset". Of course you are also free to add one or more other working frequencies to that table, for example if contest organizers recommend them, or simply if you find FT4 activity elsewhere and want those frequencies easily selectable from the WSJT-X main window. The normal rules apply, you may operate on any free frequency within your local band plan recommendations for narrow band digital modes.

73
Bill
G4WJS.


locked Re: WSJT-X to N3FJP AC Log Interface

Bill Somerville
 

On 10/05/2020 15:56, Steve Wilson via groups.io wrote:
I know that N3FJP can be interfaced to WSJT-X via JTAlert, but I'd like to toss out my vote for a direct interface. :-)

73!

Steve  K6WW
Hi Steve,

the WSJT-X development team is small and focused on weak signal communications modes, we have no wish to implement and support numerous different interfaces to the plethora of QSO logging applications. That would be an unnecessary drain on our resources, particularly where those applications do not run on all the platforms that WSJT-X is supported on. Instead we provide a documented protocol that other applications can interoperate with, that protocol provides more than just logged QSO details, it also provides near real-time information of decodes printed, and the status of the WSJT-X user interface. It also provides messages for external applications to initiate QSOs, highlight text in the WSJT-X Band Activity window, and change some user interface controls in WSJT-X. The protocol, when implemented properly, also allows multiple applications to interoperate with any number of WSJT-X instances, all running concurrently.

Where the authors of logging, or other third party applications, do not have the inclination or resources to implement the WSJT-X UDP Message Protocol then there is space for other developers to implement bridging applications to fill that gap. An excellent example of that, although not the only one, is the JTAlert application by Laurie, VK3AMA. So that begs the question: what is wrong with the use of JTAlert to bridge between WSJT-X and AC Log, and have you asked Laurie if such deficiencies can be addressed within JTAlert?

73
Bill
G4WJS.


locked FT4 Freq for 15M

David Perry
 

What is the FT4 frequency for 15 meter band?  Is it 21,140 kHz?

73,

Dave, N4QS


locked Re: Block specific callsign from decoding

John
 

Joe, I wish I had you patience and wisdom.

John
VE3KKQ

---------- Original Message ----------
From: Joe <k1ike_mail@...>
Date: May 10, 2020 at 9:44 AM


On 5/10/2020 8:59 AM, John wrote:
Yup, has happened to me more than once, calling CQ South America (SA) and I
get
a guy calling me from the USA.
So the program responds automaically, what do you fellas suggest, work him,
don't log him?,
I think that we all have to take into consideration that FT8 is very new
mode of operation and there are many, many inexperienced operators out
there in the ether world. If you meet an inexperienced ham on SSB you
have the ability to gently correct the new ham. FT8 mode does not allow
this interaction.

So, please be patient with me and others. Maybe an email using QRZ to
find our email address would help. I've been a ham for 60+ years but
feel like a neophyte on FT8. Lots to learn and sometimes I'll make mistakes.

73, Joe, K1ike


locked Re: WSJT-X to N3FJP AC Log Interface

Jim Shorney
 

That would be nice but I would understand if Scott does not add this. He already has a perfectly functional API system, the WSJT-X developers just choose not to support it. Only intensive lobbying by ACL users seems likely to change this and with most ops stuck on JTAlert this has not been happening.

An alternative is to use the Python script created by W3DJS, https://github.com/dslotter/wsjtx_to_n3fjp/ . It works great talking cross platform from Linux to Windows, but of course Windows only users would need to install Python.

https://www.python.org/downloads/windows/

73

-Jim
NU0C

On Sun, 10 May 2020 11:41:38 -0400
"Joe Subich, W4TV" <lists@...> wrote:

That's something Scott would need to do. WSJT-X already broadcasts
the information (using a standard UDP format) - Scott needs to listen
on the appropriate port and log the data when he sees the "Log"
packet.

73,

... Joe, W4TV


On 2020-05-10 10:56 AM, Steve Wilson via groups.io wrote:
I know that N3FJP can be interfaced to WSJT-X via JTAlert, but I'd like to toss out my vote for a direct interface. :-)

73!

Steve  K6WW