Date   

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

neil_zampella
 

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?


locked Re: #FIELD DAY

Hank Garretson
 

Make sure you additionally check Special Operating Activity in upper-left corner.

Contest, Cope Exuberantly,

Hank, W6SX


On Sun, Jun 21, 2020 at 3:37 PM robert kupps <nhiskups@...> wrote:
Hi Charles<
go to Advanced in the preferences>
here’s mine for FD
robert W6INO


On Jun 21, 2020, at 1:10 PM, Charles Fricks, AF5FB <clavier@...> wrote:

What box do you put them in?

W6INO

~~~~~~~~~~~~~~~~~~~~~~~~~~~
Twenty years from now, you will be more disappointed by the things you didn't do than by the ones you did do. 
 So, throw off the bowlines. Sail away from the safe harbor. Catch the trade winds in your sails. Explore. Dream. Discover.
 -Mark  Twain







locked Re: #FIELD DAY

robert kupps
 

Hi Charles<
go to Advanced in the preferences>
here’s mine for FD
robert W6INO


On Jun 21, 2020, at 1:10 PM, Charles Fricks, AF5FB <clavier@...> wrote:

What box do you put them in?

W6INO

~~~~~~~~~~~~~~~~~~~~~~~~~~~
Twenty years from now, you will be more disappointed by the things you didn't do than by the ones you did do. 
 So, throw off the bowlines. Sail away from the safe harbor. Catch the trade winds in your sails. Explore. Dream. Discover.
 -Mark  Twain






locked Re: Disable TX After 73

Frode Igland
 

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

Charles Fricks, AF5FB
 

What box do you put them in?


locked Re: New Windows 10 update and audio selection

Morris WA4MIT
 

Hi Dave only thing that changed here was the audio settings in WSJTX select settings then audio and in this window my normal selections had changed to something else so in the drop down I re-selected my normally used sound card which is the on=board sound in my ham PC. I use two sound cards one for ham use and one for PC use. This was the only thing I had to change. Sorry this is late response but have not been back on forum I hope you found what was wrong by now Dave.
73 Morris WA4MIT


locked Re: #audio_issues #microphone #AudioIssues

Gregory Reichenbach
 

Here's the solution I eventually found, which worked:

In HD Audio Manager, click on "connector settings" (the folder icon at the upper right)
Check the box marked "enable auto popup dialog, when device has been plugged inf"
Unplug the "headset jack" (connected to the rig), then plug back in
The dialog pops up, asking "which device did you plug in?"
Check the box marked "headset"

Thanks again everyone
Greg W8GSR


locked Re: Replying to CQ, etc.

Jim Shorney
 

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: wsjt-x and fkex 6700 transmit issues

Bill Somerville
 

On 21/06/2020 20:45, Neal Pollack wrote:
Geoff:

While I am glad that "something" worked for you, USB suspend/sleep has absolutely nothing to do with Flex ethernet control.  It is not a "virtual USB port".   WSJT-X controls the Flex radio over ethernet using TCP UDP packets.  Nothing else.   I have a Flex 6600, and have seen the same exact issue with no TX after long idle periods.  Killing and restarting WSJT-X always fixes it.  But the WSJT-X code is not doing anything with USB ports in this configuration.   The issue does seem tied to the virtual AUDIO ports. I tried your USB suspend setting, and I still get the NO TX issue after long idle times.   I am leaning toward thinking there may be some similar timeout issue with Windows 10 audio devices, or a slow memory leak or bug in WSJT-X with regard to this.  In all cases, restarting WSJT-X fixes it, so you can't blame the Windows 10 USB layer or the Flex DAX layer.   Let's keep hunting....

Neal
Neal,

you are missing the point. The virtual audio devices provided by DAX are amongst the devices that get re-enumerated when some other device is powered own to save power. The fact that your rig is connected to you PC via via Ethernet is not particularly relevant to the issue you are suffering.

73
Bill
G4WJS.


locked Re: Disable TX After 73

VE3KTN
 

Hello Reino, and thanks for the background.  I just had to tear myself away from this crazy North America 6m opening this afternoon - my fingers are getting tired  :-P.

Oh boy.  I thought my last post describing in detail what I see would be the last, but .....

Observing again and more closely what happens after sending CQ and letting the autosequencer go, if I set TX4 to "RRR", then it waits for the remote response of "73" without disabling TX.  If it receives that 73, my rig will transmit back a TX5 and at the same time the TX Enable goes white (i.e. indicating that it is disabled even though TX5 is in progress), then drops to TX6 and is ready for the next QSO.  All of this independent of the "Disable TX after sending 73" setting.  It seems a bit redundant to send both the TX4 and TX5, but that's the way it is and the CQ originator has to wait another 15 seconds to send his TX5 (unless he forces a TX Halt).

All of this would seem to support my point that there must be a better way to end the autosequence than trapping on "73".  Maybe in V3.0.0 ?  ;-)

Oh, and BTW, auto launching of the Log QSO window is independent of the message selected for TX4.  It will pop up after TX4 if set to "RR73" and after TX5 if TX4 is set to "RRR" and TX5 is the default "73" message.

I'm almost afraid to set TX4 to "RRR" and TX5 to a free text not containing "73".

73,
Hugo, ve3ktn.


locked Re: wsjt-x and fkex 6700 transmit issues

Neal Pollack
 

Geoff:

While I am glad that "something" worked for you, USB suspend/sleep has absolutely nothing to do with Flex ethernet control.  It is not a "virtual USB port".   WSJT-X controls the Flex radio over ethernet using TCP UDP packets.  Nothing else.   I have a Flex 6600, and have seen the same exact issue with no TX after long idle periods.  Killing and restarting WSJT-X always fixes it.  But the WSJT-X code is not doing anything with USB ports in this configuration.   The issue does seem tied to the virtual AUDIO ports. I tried your USB suspend setting, and I still get the NO TX issue after long idle times.   I am leaning toward thinking there may be some similar timeout issue with Windows 10 audio devices, or a slow memory leak or bug in WSJT-X with regard to this.  In all cases, restarting WSJT-X fixes it, so you can't blame the Windows 10 USB layer or the Flex DAX layer.   Let's keep hunting....

Neal


locked Re: Problem: WSJT-x Tx audio disconnects from Flex DAX after sitting idle #AudioIssues

Steve Phillips - NS4P
 

You might also use Device Manager to check the settings under Ports (COM & LPT).  For my Icom 7610 the Icom virtual serial port drivers created entries there that also needed the Power Management settings changed.

Steve - NS4P


locked Re: Replying to CQ, etc.

K8BL BOB LIDDY <k8bl@...>
 

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
-=-=-=-=-=-=-=-=-=-=-=-