Date   

locked Re: #FIELD DAY

Reino Talarmo
 

Hi Ed and All.

Just a minor issue about special operations contest logs. You need by yourself manage the log in the sense that there is no automatic new log function. Contest log is kept in a database that is independent of the normal log (wsjtx_log.adi). Before a contest you need to reset the contest log File -> Reset Cabrillo log… and after the contest export than log by Export Cabrillo log… Of course you may use any other logging software and forget the wsjt-x tools of use the wsjtx_log.adi file as contest log, if accepted in contest.

73, Reino OH3mA

PS  The database is retained, if wsjt-x is uninstalled and re-installed or a new version is installed.

 

>I believe WSJT-X starts a new log for you just for field Day.

 

Ed.. AB4IQ


locked Re: Replying to CQ, etc.

Jim Shorney
 

I guess you just have to consider it a part of the game then. I you were working a contest for example you wouldn't be getting grids during the QSO. Part of the game. Sometimes fun is hard work. Some logging software allows you to fill empty fields from online sources, maybe that could be an option for you.

73

-Jim
NU0C

On Mon, 22 Jun 2020 01:41:48 +0000 (UTC)
"K8BL BOB LIDDY" <k8bl@...> wrote:

Jim,
I do work them. But since I want their Grid in the WSJT Log so itwill tell me if I still need that Grid or not I have to look them up inQRZ for their Grid. Then, I have to enter it before I log the QSO which is easier than going back later to edit the Log. I will alwayswork whoever calls me, I just need their Grid for the Log. I haveno add-ons, just WSJTX working alone since I have seen non-stopmessages here about tons of problems with multiple programs tryingto work together. Bare-bones WSJT on WIN7 with 30W to an End-Fed LW has given me over 24K Q's so far. FT8/4 Rocks!!!
73,   Bob  K8BL

On Sunday, June 21, 2020, 04:12:47 PM EDT, Jim Shorney <jshorney@...> wrote:


Now you have got me curious. Why not just work them and move on?

73

-Jim
NU0C


On Sun, 21 Jun 2020 19:03:56 +0000 (UTC)
"K8BL BOB LIDDY" <k8bl@...> wrote:

It seems that the EU folks are the ones that often like to starta QSO by not using TX1 with their Grid. Maybe they feel theycan make QSOs quicker that way. That's not my preference sinceI have WSJTX set up to indicate "New Grid On Band". If theydon't send it, I am forced to look it up in QRZ. I run WSJTXby itself.


locked Re: Rig Control Failure FD Mode with N3FJP and JTAlert

Michael WA7SKG
 

Well, I can only go by experience. In my case, I have been using VSPE almost daily to allow two, often three applications work with my radio without issue for over three years. The ONLY unreliability/incompatibility is with WSJT-X. I regularly use fldigi and N3FJP for logging and the two work together with my radio just fine. WSJT-X seems to only work with itself and nothing else. I don't need the headache. I'll just forego FT8 for Field Day.

Michael WA7SKG


Bill Somerville wrote on 6/21/20 7:21 PM:

Michael,
VSPE COM port splitter is a dumb splitter, as in it makes no attempt whatsoever to arbitrate traffic. The RS-232 serial protocol is a one-to-one protocol, it is not a networking protocol, unhandled collisions are bound to occur when two way traffic is attempted by multiple clients. We do not support it, because it does not work reliably. The fact that you have discovered this obvious unreliability is not our problem, sorry.
73
Bill
G4WJS.
On 22/06/2020 03:16, Michael WA7SKG wrote:
Actually, I have multiple applications utilizing CAT control all the time. It works fine, except for WSJT-X. I run fldigi, N3FJP, and MS-DMT simultaneously using VSPE to set up a port splitter. All applications can set and read mode and frequency as well as PTT with no issue. But if I try to add WSJT-X to the mix, it simply wads up and dies.

Michael WA7SKG


Bill Somerville wrote on 6/21/20 7:03 PM:
Michael,

you cannot have two applications directly using the same rig for CAT control. If the N3FJP FD logging application does not support one of the rig server programs that WSJT-X also supports (Hamlib rigctld, Omni-Rig, or something that looks like a rig to each application but is more than a dumb serial port splitter), then you will have to disable rig control in one application or the other. WSJT-X will run fine without CAT control of a rig so long as you can still control PTT. Either VOX or a wire-ored hardware PTT arrangement using RTS or DTR on a pair of serial ports will get you PTT. If you intend to use WSJT-X without CAT control then you should stick to Tx audio offsets above 1500 Hz to make sure any audio harmonics are eliminated. You will also have to ensure that WSJT-X is switched to the same band as your rig or your log entries will be incorrect.

TBH, if disabling rig control in the N3FJP FD logging application is as easy as it is in WSJT-X ("Settings->Radio->Rig->None" and "Settings->Radio->PTT Method->VOX", then click "Ok") or simply exit WSJT-X when you are not using it as restarting will bring it right back where you left it, then switching rig control is probably the easiest and quickest option.

73
Bill
G4WJS.

On 22/06/2020 02:44, Michael WA7SKG wrote:
If all I was doing is running FT8, this would be fine. However, most of the time I will be running phone, with WSJT-X and fldigi not running and doing all my logging directly through N3FJP. I want to start N3FJP and leave it running all the time, then start WSJT-X or fldigi as needed to use the digital modes. Then I would stop WSJT-X or fldigi and return to phone. I would like to minimize the transition time between modes and not have to shut everything down and restart the whole works with different sequences between modes.

Michael WA7SKG


neil_zampella wrote on 6/21/20 5:59 PM:
Yes .. Hamlib is built into the WSJT-X executable.    Try starting WSJT-X, JT-Alert, then N3FJP.  I suggest that the reason you're getting the error is that N3FJP is setup to control the rig, if you could turn that off, and let WSJT-X control the rig, you'll be fine.

Neil, KN3ILZ

On 6/21/2020 8:07 PM, Michael WA7SKG wrote:
Additionally, if I go to configurations, all settings are correct, when I hit TEST CAT, the rig changes to 28.335.19 and a box pops up saying "Rig Failure Hamlib error:Command rejected by the rig while exchanging VFOs." Subsequent tests fail for frequency change and mode change.

I guess hamlib must be built into WSJT-X and I don't use it otherwise.

Michael WA7SKG


Michael WA7SKG wrote on 6/21/20 4:45 PM:
Getting ready for Field Day. I have the latest versions of WSJT-X
(2.2.1), JTAlert (2.16.8), and N3FJP Field Day Log (6.3).

My understanding is to start N3FJP > WSJT-X > JTAlert in that order. I have followed the various tutorials and instructions for setting these up. When I start WSJT-X, I get a "Rig Control Error" box asking to set up the rig parameters (IC-7300). These are all correct. Running WSJT-X by itself is no problem. Only when N3FJP is running do I have an issue.

I am obviously missing something. Any suggestions as to what?


locked Re: Replying to CQ, etc.

Jim Brown
 

On 6/21/2020 12:03 PM, K8BL BOB LIDDY wrote:
It seems that the EU folks are the ones that often like to start
a QSO by not using TX1 with their Grid. Maybe they feel they
can make QSOs quicker that way.
On 6M, the vast majority of JA stations call with TX2. It's also common for them to switch to another QSO before giving me RR73. I find this somewhere between dumb and inconsiderate. I've got a 9-call living (for 14 years) in NorCal, so if I'm calling a station who doesn't know me on a band where the other guy is likely using a directional antenna, I'll call with TX1 so that he doesn't turn his antenna in the wrong direction. Without that concern, I would nearly always call with TX2.

I disagree with the advice someone offered that TX3 and TX4 was sufficient. A QSO requires one piece of information in addition to the calls, and RR (or R -6) from both sides. If you CALL with TX3, the other station hasn't given you any info to acknowledge, so it's no QSO.

Now, when in Contest mode, the exchange is grid and the CQing station has sent his grid, I see TX3 as an OK response by the calling station, and RR73 by the CQing station as finishing the QSO.

73, Jim K9YC


locked Re: wsjt-x and fkex 6700 transmit issues

Bill Somerville
 

On 22/06/2020 03:23, Don - kx9q wrote:
Bill

I have also experienced the same issue with the same setup.  So how do you determine what device or devices are getting powered down?

Don - kx9q
Hi Don,

the problem seems to revolve around anything that could carry audio and supports hot-plugging. that boils down to USB and things that carry USB connections. Setting all USB hubs to not be powered down to save energy in their properties under Device Manager, and setting the system Power Plan not to suspend USB devices both are essential. Another problem area is HDMI monitor connections, HDMI carries USB connections and some graphics cards seem to have no easy way to stop them powering down the monitor when idle. As a last resort, there are applications that simulate mouse movements on a regular basis to try and persuade Windows that the system is not idle.

73
Bill
G4WJS.


locked Re: Rig Control Failure FD Mode with N3FJP and JTAlert

Bill Somerville
 

Michael,

VSPE COM port splitter is a dumb splitter, as in it makes no attempt whatsoever to arbitrate traffic. The RS-232 serial protocol is a one-to-one protocol, it is not a networking protocol, unhandled collisions are bound to occur when two way traffic is attempted by multiple clients. We do not support it, because it does not work reliably. The fact that you have discovered this obvious unreliability is not our problem, sorry.

73
Bill
G4WJS.

On 22/06/2020 03:16, Michael WA7SKG wrote:

Actually, I have multiple applications utilizing CAT control all the time. It works fine, except for WSJT-X. I run fldigi, N3FJP, and MS-DMT simultaneously using VSPE to set up a port splitter. All applications can set and read mode and frequency as well as PTT with no issue. But if I try to add WSJT-X to the mix, it simply wads up and dies.

Michael WA7SKG


Bill Somerville wrote on 6/21/20 7:03 PM:
Michael,

you cannot have two applications directly using the same rig for CAT control. If the N3FJP FD logging application does not support one of the rig server programs that WSJT-X also supports (Hamlib rigctld, Omni-Rig, or something that looks like a rig to each application but is more than a dumb serial port splitter), then you will have to disable rig control in one application or the other. WSJT-X will run fine without CAT control of a rig so long as you can still control PTT. Either VOX or a wire-ored hardware PTT arrangement using RTS or DTR on a pair of serial ports will get you PTT. If you intend to use WSJT-X without CAT control then you should stick to Tx audio offsets above 1500 Hz to make sure any audio harmonics are eliminated. You will also have to ensure that WSJT-X is switched to the same band as your rig or your log entries will be incorrect.

TBH, if disabling rig control in the N3FJP FD logging application is as easy as it is in WSJT-X ("Settings->Radio->Rig->None" and "Settings->Radio->PTT Method->VOX", then click "Ok") or simply exit WSJT-X when you are not using it as restarting will bring it right back where you left it, then switching rig control is probably the easiest and quickest option.

73
Bill
G4WJS.

On 22/06/2020 02:44, Michael WA7SKG wrote:
If all I was doing is running FT8, this would be fine. However, most of the time I will be running phone, with WSJT-X and fldigi not running and doing all my logging directly through N3FJP. I want to start N3FJP and leave it running all the time, then start WSJT-X or fldigi as needed to use the digital modes. Then I would stop WSJT-X or fldigi and return to phone. I would like to minimize the transition time between modes and not have to shut everything down and restart the whole works with different sequences between modes.

Michael WA7SKG


neil_zampella wrote on 6/21/20 5:59 PM:
Yes .. Hamlib is built into the WSJT-X executable.    Try starting WSJT-X, JT-Alert, then N3FJP.  I suggest that the reason you're getting the error is that N3FJP is setup to control the rig, if you could turn that off, and let WSJT-X control the rig, you'll be fine.

Neil, KN3ILZ

On 6/21/2020 8:07 PM, Michael WA7SKG wrote:
Additionally, if I go to configurations, all settings are correct, when I hit TEST CAT, the rig changes to 28.335.19 and a box pops up saying "Rig Failure Hamlib error:Command rejected by the rig while exchanging VFOs." Subsequent tests fail for frequency change and mode change.

I guess hamlib must be built into WSJT-X and I don't use it otherwise.

Michael WA7SKG


Michael WA7SKG wrote on 6/21/20 4:45 PM:
Getting ready for Field Day. I have the latest versions of WSJT-X
(2.2.1), JTAlert (2.16.8), and N3FJP Field Day Log (6.3).

My understanding is to start N3FJP > WSJT-X > JTAlert in that order. I have followed the various tutorials and instructions for setting these up. When I start WSJT-X, I get a "Rig Control Error" box asking to set up the rig parameters (IC-7300). These are all correct. Running WSJT-X by itself is no problem. Only when N3FJP is running do I have an issue.

I am obviously missing something. Any suggestions as to what?



locked Re: Rig Control Failure FD Mode with N3FJP and JTAlert

Michael WA7SKG
 

Actually, I have multiple applications utilizing CAT control all the time. It works fine, except for WSJT-X. I run fldigi, N3FJP, and MS-DMT simultaneously using VSPE to set up a port splitter. All applications can set and read mode and frequency as well as PTT with no issue. But if I try to add WSJT-X to the mix, it simply wads up and dies.

Michael WA7SKG


Bill Somerville wrote on 6/21/20 7:03 PM:

Michael,
you cannot have two applications directly using the same rig for CAT control. If the N3FJP FD logging application does not support one of the rig server programs that WSJT-X also supports (Hamlib rigctld, Omni-Rig, or something that looks like a rig to each application but is more than a dumb serial port splitter), then you will have to disable rig control in one application or the other. WSJT-X will run fine without CAT control of a rig so long as you can still control PTT. Either VOX or a wire-ored hardware PTT arrangement using RTS or DTR on a pair of serial ports will get you PTT. If you intend to use WSJT-X without CAT control then you should stick to Tx audio offsets above 1500 Hz to make sure any audio harmonics are eliminated. You will also have to ensure that WSJT-X is switched to the same band as your rig or your log entries will be incorrect.
TBH, if disabling rig control in the N3FJP FD logging application is as easy as it is in WSJT-X ("Settings->Radio->Rig->None" and "Settings->Radio->PTT Method->VOX", then click "Ok") or simply exit WSJT-X when you are not using it as restarting will bring it right back where you left it, then switching rig control is probably the easiest and quickest option.
73
Bill
G4WJS.
On 22/06/2020 02:44, Michael WA7SKG wrote:
If all I was doing is running FT8, this would be fine. However, most of the time I will be running phone, with WSJT-X and fldigi not running and doing all my logging directly through N3FJP. I want to start N3FJP and leave it running all the time, then start WSJT-X or fldigi as needed to use the digital modes. Then I would stop WSJT-X or fldigi and return to phone. I would like to minimize the transition time between modes and not have to shut everything down and restart the whole works with different sequences between modes.

Michael WA7SKG


neil_zampella wrote on 6/21/20 5:59 PM:
Yes .. Hamlib is built into the WSJT-X executable.    Try starting WSJT-X, JT-Alert, then N3FJP.  I suggest that the reason you're getting the error is that N3FJP is setup to control the rig, if you could turn that off, and let WSJT-X control the rig, you'll be fine.

Neil, KN3ILZ

On 6/21/2020 8:07 PM, Michael WA7SKG wrote:
Additionally, if I go to configurations, all settings are correct, when I hit TEST CAT, the rig changes to 28.335.19 and a box pops up saying "Rig Failure Hamlib error:Command rejected by the rig while exchanging VFOs." Subsequent tests fail for frequency change and mode change.

I guess hamlib must be built into WSJT-X and I don't use it otherwise.

Michael WA7SKG


Michael WA7SKG wrote on 6/21/20 4:45 PM:
Getting ready for Field Day. I have the latest versions of WSJT-X
(2.2.1), JTAlert (2.16.8), and N3FJP Field Day Log (6.3).

My understanding is to start N3FJP > WSJT-X > JTAlert in that order. I have followed the various tutorials and instructions for setting these up. When I start WSJT-X, I get a "Rig Control Error" box asking to set up the rig parameters (IC-7300). These are all correct. Running WSJT-X by itself is no problem. Only when N3FJP is running do I have an issue.

I am obviously missing something. Any suggestions as to what?


locked Re: Replying to CQ, etc.

K8BL BOB LIDDY <k8bl@...>
 

Tony,

Thanks for your comments. I don't work many JA's with 30W
and a LW, so your info is news to me. I do see it a lot from EU's.

I have my WD Timer set for 10 minutes since I sometimes walk
away doing other things and find it fun to come back and see that
I worked someone. Maybe some Stations set their timers for a very
long time for various reasons.

My intent was not trying to tell anyone how they should operate. I
was merely sharing a pet peeve of mine. Some folks look for reasons
to be "offended".  I have two words for them - "f--- off!".

GL/73,    Bob  K8BL

P.S.  I tried responding direct, but your adr kept getting bounced.

On Sunday, June 21, 2020, 08:50:32 PM EDT, Tony Collett via groups.io <tony.nbs@...> wrote:


To answer Roger's initial question - I've only experienced this with stations "in demand". I call them with Tx1 but somehow get Tx3 back so I log a QSO without me ever sending my report. I guess they are treating data as an expedition type QSO and reports are superfluous? Never had it in answer to my CQ though.

Bob K8BL - I've yet to have a JA station answer my CQ call with anything other than Tx2, it isn't that common a practice in Europe yet.

And while I agree with the comments re software JTAlert does not always (in my experience) provide the locator unless you have already worked the station. Since WSJT highlights the worked before status by using its own Log.ADI file unless you edit that file or enter the Locator before you hit the log QSO button you are left with your peeve!

Does seem to me BTW that there are still way too many that insist on not using split. I thought WSJT was programmed so that if you called on someones frequency but they answered somebody else then your Tx was disabled.

There must be a different program out there that doesn't do this as I watched a Spanish station on 10m the other night that continually called a station on their frequency without any form of watchdog timeout and despite that station somehow managing lots of QSO's with other callers. Now that would peeve me off! 

73's Tony G4NBS


locked Re: Rig Control Failure FD Mode with N3FJP and JTAlert

Bill Somerville
 

Michael,

you cannot have two applications directly using the same rig for CAT control. If the N3FJP FD logging application does not support one of the rig server programs that WSJT-X also supports (Hamlib rigctld, Omni-Rig, or something that looks like a rig to each application but is more than a dumb serial port splitter), then you will have to disable rig control in one application or the other. WSJT-X will run fine without CAT control of a rig so long as you can still control PTT. Either VOX or a wire-ored hardware PTT arrangement using RTS or DTR on a pair of serial ports will get you PTT. If you intend to use WSJT-X without CAT control then you should stick to Tx audio offsets above 1500 Hz to make sure any audio harmonics are eliminated. You will also have to ensure that WSJT-X is switched to the same band as your rig or your log entries will be incorrect.

TBH, if disabling rig control in the N3FJP FD logging application is as easy as it is in WSJT-X ("Settings->Radio->Rig->None" and "Settings->Radio->PTT Method->VOX", then click "Ok") or simply exit WSJT-X when you are not using it as restarting will bring it right back where you left it, then switching rig control is probably the easiest and quickest option.

73
Bill
G4WJS.

On 22/06/2020 02:44, Michael WA7SKG wrote:

If all I was doing is running FT8, this would be fine. However, most of the time I will be running phone, with WSJT-X and fldigi not running and doing all my logging directly through N3FJP. I want to start N3FJP and leave it running all the time, then start WSJT-X or fldigi as needed to use the digital modes. Then I would stop WSJT-X or fldigi and return to phone. I would like to minimize the transition time between modes and not have to shut everything down and restart the whole works with different sequences between modes.

Michael WA7SKG


neil_zampella wrote on 6/21/20 5:59 PM:
Yes .. Hamlib is built into the WSJT-X executable.    Try starting WSJT-X, JT-Alert, then N3FJP.  I suggest that the reason you're getting the error is that N3FJP is setup to control the rig, if you could turn that off, and let WSJT-X control the rig, you'll be fine.

Neil, KN3ILZ

On 6/21/2020 8:07 PM, Michael WA7SKG wrote:
Additionally, if I go to configurations, all settings are correct, when I hit TEST CAT, the rig changes to 28.335.19 and a box pops up saying "Rig Failure Hamlib error:Command rejected by the rig while exchanging VFOs." Subsequent tests fail for frequency change and mode change.

I guess hamlib must be built into WSJT-X and I don't use it otherwise.

Michael WA7SKG


Michael WA7SKG wrote on 6/21/20 4:45 PM:
Getting ready for Field Day. I have the latest versions of WSJT-X
(2.2.1), JTAlert (2.16.8), and N3FJP Field Day Log (6.3).

My understanding is to start N3FJP > WSJT-X > JTAlert in that order. I have followed the various tutorials and instructions for setting these up. When I start WSJT-X, I get a "Rig Control Error" box asking to set up the rig parameters (IC-7300). These are all correct. Running WSJT-X by itself is no problem. Only when N3FJP is running do I have an issue.

I am obviously missing something. Any suggestions as to what?



locked Re: Rig Control Failure FD Mode with N3FJP and JTAlert

Michael WA7SKG
 

If all I was doing is running FT8, this would be fine. However, most of the time I will be running phone, with WSJT-X and fldigi not running and doing all my logging directly through N3FJP. I want to start N3FJP and leave it running all the time, then start WSJT-X or fldigi as needed to use the digital modes. Then I would stop WSJT-X or fldigi and return to phone. I would like to minimize the transition time between modes and not have to shut everything down and restart the whole works with different sequences between modes.

Michael WA7SKG


neil_zampella wrote on 6/21/20 5:59 PM:

Yes .. Hamlib is built into the WSJT-X executable.    Try starting WSJT-X, JT-Alert, then N3FJP.  I suggest that the reason you're getting the error is that N3FJP is setup to control the rig, if you could turn that off, and let WSJT-X control the rig, you'll be fine.
Neil, KN3ILZ
On 6/21/2020 8:07 PM, Michael WA7SKG wrote:
Additionally, if I go to configurations, all settings are correct, when I hit TEST CAT, the rig changes to 28.335.19 and a box pops up saying "Rig Failure Hamlib error:Command rejected by the rig while exchanging VFOs." Subsequent tests fail for frequency change and mode change.

I guess hamlib must be built into WSJT-X and I don't use it otherwise.

Michael WA7SKG


Michael WA7SKG wrote on 6/21/20 4:45 PM:
Getting ready for Field Day. I have the latest versions of WSJT-X
(2.2.1), JTAlert (2.16.8), and N3FJP Field Day Log (6.3).

My understanding is to start N3FJP > WSJT-X > JTAlert in that order. I have followed the various tutorials and instructions for setting these up. When I start WSJT-X, I get a "Rig Control Error" box asking to set up the rig parameters (IC-7300). These are all correct. Running WSJT-X by itself is no problem. Only when N3FJP is running do I have an issue.

I am obviously missing something. Any suggestions as to what?


locked Re: Replying to CQ, etc.

K8BL BOB LIDDY <k8bl@...>
 

Jim,

I do work them. But since I want their Grid in the WSJT Log so it
will tell me if I still need that Grid or not I have to look them up in
QRZ for their Grid. Then, I have to enter it before I log the QSO 
which is easier than going back later to edit the Log. I will always
work whoever calls me, I just need their Grid for the Log. I have
no add-ons, just WSJTX working alone since I have seen non-stop
messages here about tons of problems with multiple programs trying
to work together. Bare-bones WSJT on WIN7 with 30W to an End-
Fed LW has given me over 24K Q's so far. FT8/4 Rocks!!!

73,   Bob  K8BL


On Sunday, June 21, 2020, 04:12:47 PM EDT, Jim Shorney <jshorney@...> wrote:



Now you have got me curious. Why not just work them and move on?

73

-Jim
NU0C


On Sun, 21 Jun 2020 19:03:56 +0000 (UTC)
"K8BL BOB LIDDY" <k8bl@...> wrote:

> It seems that the EU folks are the ones that often like to starta QSO by not using TX1 with their Grid. Maybe they feel theycan make QSOs quicker that way. That's not my preference sinceI have WSJTX set up to indicate "New Grid On Band". If theydon't send it, I am forced to look it up in QRZ. I run WSJTXby itself.


locked Re: #FIELD DAY

Charles Fricks, AF5FB
 

Found it--thanks!


locked Re: Rig Control Failure FD Mode with N3FJP and JTAlert

neil_zampella <neilz@...>
 

Yes .. Hamlib is built into the WSJT-X executable.    Try starting WSJT-X, JT-Alert, then N3FJP.  I suggest that the reason you're getting the error is that N3FJP is setup to control the rig, if you could turn that off, and let WSJT-X control the rig, you'll be fine.

Neil, KN3ILZ

On 6/21/2020 8:07 PM, Michael WA7SKG wrote:
Additionally, if I go to configurations, all settings are correct, when I hit TEST CAT, the rig changes to 28.335.19 and a box pops up saying "Rig Failure Hamlib error:Command rejected by the rig while exchanging VFOs." Subsequent tests fail for frequency change and mode change.

I guess hamlib must be built into WSJT-X and I don't use it otherwise.

Michael WA7SKG


Michael WA7SKG wrote on 6/21/20 4:45 PM:
Getting ready for Field Day. I have the latest versions of WSJT-X
(2.2.1), JTAlert (2.16.8), and N3FJP Field Day Log (6.3).

My understanding is to start N3FJP > WSJT-X > JTAlert in that order. I have followed the various tutorials and instructions for setting these up. When I start WSJT-X, I get a "Rig Control Error" box asking to set up the rig parameters (IC-7300). These are all correct. Running WSJT-X by itself is no problem. Only when N3FJP is running do I have an issue.

I am obviously missing something. Any suggestions as to what?




    

Virus-free. www.avg.com


locked Re: Possible log bug

Tony Collett
 

Bengt, the band was open earlier at 1221 according to your log, look at your all text back at that time. Is it possible that you heard AB4IQ back then and called him without a reply then went on to call CQ without clearing the call field/messages? I think that might fool WSJT into thinking the QSO started when you entered his call.

Might be wrong but as I haven't seen any other suggestions.......

GL with the DX
73
Tony G4NBS


locked Re: Replying to CQ, etc.

Tony Collett
 

To answer Roger's initial question - I've only experienced this with stations "in demand". I call them with Tx1 but somehow get Tx3 back so I log a QSO without me ever sending my report. I guess they are treating data as an expedition type QSO and reports are superfluous? Never had it in answer to my CQ though.

Bob K8BL - I've yet to have a JA station answer my CQ call with anything other than Tx2, it isn't that common a practice in Europe yet.

And while I agree with the comments re software JTAlert does not always (in my experience) provide the locator unless you have already worked the station. Since WSJT highlights the worked before status by using its own Log.ADI file unless you edit that file or enter the Locator before you hit the log QSO button you are left with your peeve!

Does seem to me BTW that there are still way too many that insist on not using split. I thought WSJT was programmed so that if you called on someones frequency but they answered somebody else then your Tx was disabled.

There must be a different program out there that doesn't do this as I watched a Spanish station on 10m the other night that continually called a station on their frequency without any form of watchdog timeout and despite that station somehow managing lots of QSO's with other callers. Now that would peeve me off! 

73's Tony G4NBS


locked Re: Rig Control Failure FD Mode with N3FJP and JTAlert

Michael WA7SKG
 

Additionally, if I go to configurations, all settings are correct, when I hit TEST CAT, the rig changes to 28.335.19 and a box pops up saying "Rig Failure Hamlib error:Command rejected by the rig while exchanging VFOs." Subsequent tests fail for frequency change and mode change.

I guess hamlib must be built into WSJT-X and I don't use it otherwise.

Michael WA7SKG


Michael WA7SKG wrote on 6/21/20 4:45 PM:

Getting ready for Field Day. I have the latest versions of WSJT-X
(2.2.1), JTAlert (2.16.8), and N3FJP Field Day Log (6.3).
My understanding is to start N3FJP > WSJT-X > JTAlert in that order. I have followed the various tutorials and instructions for setting these up. When I start WSJT-X, I get a "Rig Control Error" box asking to set up the rig parameters (IC-7300). These are all correct. Running WSJT-X by itself is no problem. Only when N3FJP is running do I have an issue.
I am obviously missing something. Any suggestions as to what?


locked Re: Replying to CQ, etc.

David AD4TJ
 

Bob, I am in agreement with you on this. I hate it when I get called by someone without using a grid; so if the QSO is completed I have no idea what grid I just worked, unless I manually go to QRZ to look them up, and hope they were working from that grid, and not portable somewhere else.

David AD4TJ

On Sunday, June 21, 2020, 3:04:10 PM EDT, K8BL BOB LIDDY <k8bl@...> wrote:


Carl,

Thanks for your comments/opinions. Just keep in mind that
my issues were my personal pet peeves. Everyone has them
and most people are afraid or too polite to express them. I am
not in either case. I appreciate your input greatly.

It seems that the EU folks are the ones that often like to start
a QSO by not using TX1 with their Grid. Maybe they feel they
can make QSOs quicker that way. That's not my preference since
I have WSJTX set up to indicate "New Grid On Band". If they
don't send it, I am forced to look it up in QRZ. I run WSJTX
by itself.

TNX/73,     Bob  K8BL

P.S.  What I got from Carey did not include his Call. I found it
    later by searching his name. Here's what I got FYI:

On Sunday, June 21, 2020, 12:05:04 PM EDT, <careyfisher@...> wrote:


Wow, you sure have a lot of pet peeves! Do you have a list of rules people should use when contacting you?

-------------------------------------------------------------------------------------------------------

On Sunday, June 21, 2020, 02:19:24 PM EDT, Carl - WC4H via groups.io <wc4h.dx@...> wrote:

Bob, read carefully, Carey did include his name and call.

Roger,  technically speaking the 4 components that make a contact a valid QSO are:
Band, Mode, the QSO partner's callsign, and the time of the QSO (Normally in UTC and ARRL uses Start Time).

Report and grid are notably NOT required to have a valid QSO as is no other information.

So, my guess is that the folks that call you with Tx3 are looking for the minimum info required.  If you answer RR73, they come back with a 73 and you have fullfilled the content of the 4 components.

I have gotten Tx3 calls also.  I just let the program respond with RR73 and I get a 73 back and log it.

It's not ideal if you are looking for grids and want WSJT-X to highlight the caller with the appropriate color.  If you upload to LoTW, the and the QSO partner is in LoTW, you will still get credit for that grid.

I always remind people to think of a DX Expedition.  Extremely minimal info to work the most people possible, and nobody complains that they did not get a 73 or a grid.  They are just happy to get that ATNO. 

73.

Carl - WC4H


locked Rig Control Failure FD Mode with N3FJP and JTAlert

Michael WA7SKG
 

Getting ready for Field Day. I have the latest versions of WSJT-X
(2.2.1), JTAlert (2.16.8), and N3FJP Field Day Log (6.3).

My understanding is to start N3FJP > WSJT-X > JTAlert in that order. I have followed the various tutorials and instructions for setting these up. When I start WSJT-X, I get a "Rig Control Error" box asking to set up the rig parameters (IC-7300). These are all correct. Running WSJT-X by itself is no problem. Only when N3FJP is running do I have an issue.

I am obviously missing something. Any suggestions as to what?



--
73,
Michael WA7SKG

"Any day you do not learn one new thing is a wasted day."


locked Re: Disable TX After 73

Hasan Schiers N0AN
 

Fried, I do the same thing just click Enable TX near the end of your last transmission and it will either call CQ or repeat RR73, whichever is required!

Any further automation is a slippery slope to autobot ops. 

This is fast enough to work short lived sporadic E openings efficiently,  especially if you double click on TX1 so you start qsos with TX2, saving 15 seconds.

73, N0AN 

Hasan


On Sun, Jun 21, 2020, 5:25 PM Frode Igland <frodeigland2@...> wrote:
From: VE3KTN
Date: Sun, 21 Jun 2020 09:21:10 PDT

...
It's too bad the logic is set up to detect the "73" string instead of just whether TX4 is being sent, as I've pointed out in a similar parallel thread on this forum.  This way, I can't send my 73 and hold off the TX inhibit to wait for the return 73 - I (and the remote) will have to be satisfied with an RRR.

...

Hugo,

All it takes to keep everything smooth is to check the "Enable TX" button as soon as you send the RR73 (and "Enable TX" is disabled). If your QSO partner returns with R+report, RR73 will automatically be sent again, because obviously he/she did not copy your first RR73, and still don't know if you received his/her report. If your QSO partner returns with 73, he/she received everything, and your next CQ is sent. No sequence is lost, and the operation is very efficient. Having to click "Enable TX"  is just enough 1. to avoid robot automation, 2. to keep us busy, and 3. to keep our attention on what is going on with our radios, which of course is where we should keep our attention.

73 Frode LA6VQ





locked Re: #FIELD DAY

Ed Pflueger <ab4iq@...>
 

File, Settings, Advanced.  Check special operating activity, then put 1D NTX, STX, or WTX.  Since you are more North than South or West I would say NTX.  It Goes in the FD EXCH Box.  So you would say 1D NTX in the same box. Now until you get thru with Field Day leave that box unchecked.  Otherwise you will be giving out a report of 1D NTX rather than your grid.

 

Hope this helps.  We are running N1MM Logger with WSJT-X for FD but you can just run WSJT-X by itself.  Make sure when the logging page comes up it is blank.  I believe WSJT-X starts a new log for you just for field Day.

 

Ed.. AB4IQ

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Charles Fricks, AF5FB
Sent: Sunday, June 21, 2020 3:11 PM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] #FIELD DAY

 

What box do you put them in?