Date   

locked Re: Transferring .adi files to Winlog32

Jim Shorney
 

Depends. The definition of "dupe" varies. I never felt like testing it. Better to get it right going in IMO.

73

-Jim
NU0C

On Tue, 8 Dec 2020 07:48:49 +0000
"Philip Rose via groups.io" <gm3zza@...> wrote:

Doesn’t the logging software automatically ignore records it’s previously imported. My homebrew software does. It checks the wsjtx_log.adi every minute, if its timestamp has changed it reads it and ignores any record earlier than the previous timestamp.

73 Phil GM3ZZA

From: Jim Shorney
Sent: 08 December 2020 02:53
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Transferring .adi files to Winlog32

This is a variation on the process I used to use. My process was to copy WSJTX_log.adi to another "work" folder and DELETE all the old contacts from the copy, save and import. It is simpler than it sounds (SHIFT-CLICK is your friend). The ADIF data format is dead simple once you understand it and it takes only a few seconds once you have it down.

73

-Jim
NU0C

On Mon, 07 Dec 2020 15:55:12 -0800
"ve3ki" <ve3iay@...> wrote:

Instead of deleting the WSJTX_log.adi file, which ruins the program's ability to identify countries, grid squares and call signs that you have worked before, you can use a text editor to copy the QSOs made since your last export  form the wsjtx_log.adi file into a new empty file and import that new file into your logging program.

73,
Rich VE3KI

On Mon, Dec 7, 2020 at 06:28 PM, Alek Petkovic wrote:


As you import the .adi file to your logging program, you must go back into
wsjt-x and into "File" and then scroll down to "Erase wsjtx_log.adi "
If you don't, then you will keep getting the old QSOs repeatedly
duplicating in you logging program.

I've been doing that from day one. I don't know any other way to achieve
it.

73, Alek. VK6APK

Sent from Mail for Windows 10




locked Re: Rig Control Error and Remoterig

LA7NO
 

Thanks for that suggestion.
Will do that later.

73,

P-T, LA7NO



On Tue, 8 Dec 2020 at 22:53, Bill Somerville <g4wjs@...> wrote:
On 08/12/2020 20:30, LA7NO wrote:
>  v2.3.0-rc2 4c05f8
>
> P-T, LA7NO

Hi Per-Tore,

put the attached file into your WSJT-X configuration files directory (on
MS Windows that is the same as the log files directory), restart WSJT-X,
run until the issue occurs, then quit WSJT-X. There will be a new file
on your Desktop called WSJT-X_RigControl.log , send me that file for
analysis please. Please do not post the file to the list as it may be large.

73
Bill
G4WJS.





locked Re: Rig Control Error and Remoterig

Bill Somerville
 

On 08/12/2020 20:30, LA7NO wrote:
 v2.3.0-rc2 4c05f8

P-T, LA7NO
Hi Per-Tore,

put the attached file into your WSJT-X configuration files directory (on MS Windows that is the same as the log files directory), restart WSJT-X, run until the issue occurs, then quit WSJT-X. There will be a new file on your Desktop called WSJT-X_RigControl.log , send me that file for analysis please. Please do not post the file to the list as it may be large.

73
Bill
G4WJS.


locked Re: Rig Control Error and Remoterig

ve3ki
 

According to the message title and your first post in this thread, you are operating remotely using a connected pair of RemoteRig boxes, right? It is not at all unusual to lose CAT control connection to the radio between the two RemoteRig boxes while the audio continues working. A short Internet dropout can cause the software (Hamlib) to detect a communications error and raise an error message, after which the audio can return to normal but the software won't reconnect for CAT control until you respond to the error message by clicking on Retry. 

The solution to this is to use a computer at the radio site and run WSJT-X in that computer controlling the radio directly and operated remotely using remote desktop software. Using this method, Internet dropouts have almost no effect on WSJT-X - their only effect is to cause momentary pauses in the video you see at the control site, and possibly slightly delayed response to some of your mouse clicks.

73,
Rich VE3KI


73,
Rich VE3KI



On Tue, Dec 8, 2020 at 03:08 PM, LA7NO wrote:
And this just now:

Hamlib error: Communication timed out while getting current VFO frequency

P-T, LA7NO


locked Re: FT8 Round Up contest

ve3ki
 

The settings when running WSJT-X from within N1MM+ are separate from the settings when running it stand-alone. Making settings changes in either one has no effect on the other. After starting WSJT-X from N1MM+, you have to use the File > Settings menu in WSJT-X, select the Advanced Tab, and setup the contest exchange there.

73,
Rich VE3KI


On Tue, Dec 8, 2020 at 02:27 PM, n6rsh wrote:
Hi,

 I know the contest is over but I had a problem with the set-up with N1MM+. Everything worked fine except the exchange. I couldn't seem to get it to send the required report for the RU contest. When I run WSJT-X alone WITHOUT N1MM+ it works fine. WSJT sends our the proper exchange (ex 579 NE). However when I run WSJT WITH N1MM+ it sends out a normal FT8 exchange (ex -03 DN81). despite setting WSJT in contest mode in the advanced settings). What did I do wrong?

I would like to have this working for next year's contest. 
Thanks & 73,
Steve - N6RSH


locked Re: Rig Control Error and Remoterig

renzociarpella@gmail.com
 

Hi Bill,

ICOM 756-PRO

Connected  with CIV-17

Rig: Flrig Flrig   (somtimes Commander DXLab)

Interval: 1

PTT:   CAT

Test CAT and PTT POSITIVES

AUDI: SignLink USB

That's All.

Take care.

Renzo I6KZR

sally7.ns0it:992

www.i6kzr.it


Il 08/12/2020 21:02, Bill Somerville ha scritto:

Hi Renzo,

which rig do you have and how i it connected to your PC for CAT control?

73
Bill
G4WJS.

On 08/12/2020 18:55, renzociarpella@... wrote:

I get this error warning in the last two versions and it is always the same.
RFi is to be excluded because for reasons of antennas crash I cannot transmit, therefore only RX, much less USB because I would not understand why when I use the COMMANDER.exe program of the DXLab suite the problem does not arise.
And then the warning indicates that it is "Hamlib error: Invalid parameter to obtain the current VFO".

My help ends here, thank you for what can be done.

Renzo I6KZR

snap

Il 08/12/2020 18:50, neil_zampella ha scritto:

I only mentioned it because you mentioned audio.   RFi was mentioned as a possibility as you did not say it occurred when you're receiving only in your original post, just that you're not noticing any issues on receive audio.

Is the CAT connection USB?   Are all power saving settings turned off?

Neil, KN3ILZ

On 12/8/2020 11:30 AM, LA7NO wrote:
Yes, I am aware of it being a CAT error.
The fault is also coming when only receiving, so RFI is out of the question.

P-T, LA7NO






locked Re: Rig Control Error and Remoterig

LA7NO
 

 v2.3.0-rc2 4c05f8

P-T, LA7NO


locked Re: Rig Control Error and Remoterig

LA7NO
 

I've just downloaded the manual:

"PC CONTROL COMMANDREFERENCE FOR THETS-480HX/ SAT TRANSCEIVER"

Guess I will have a look on the actual traffic using my serial port monitor.

P-T, LA7NO


locked Re: Rig Control Error and Remoterig

LA7NO
 

And this just now:

Hamlib error: Communication timed out while getting current VFO frequency

P-T, LA7NO


locked Re: Rig Control Error and Remoterig

Bill Somerville
 

On 08/12/2020 19:59, LA7NO wrote:
Thanks, Reino.
Silly oversight from me.

I get this one:

Hamlib error: Command rejected by the rig while opening connection to rig

P-T, LA7NO
Hi Per-Tore,

which version of WSJT-X are you using?

73
Bill
G4WJS.


locked Re: Rig Control Error and Remoterig

Bill Somerville
 

Hi Renzo,

which rig do you have and how i it connected to your PC for CAT control?

73
Bill
G4WJS.

On 08/12/2020 18:55, renzociarpella@... wrote:

I get this error warning in the last two versions and it is always the same.
RFi is to be excluded because for reasons of antennas crash I cannot transmit, therefore only RX, much less USB because I would not understand why when I use the COMMANDER.exe program of the DXLab suite the problem does not arise.
And then the warning indicates that it is "Hamlib error: Invalid parameter to obtain the current VFO".

My help ends here, thank you for what can be done.

Renzo I6KZR

snap

Il 08/12/2020 18:50, neil_zampella ha scritto:

I only mentioned it because you mentioned audio.   RFi was mentioned as a possibility as you did not say it occurred when you're receiving only in your original post, just that you're not noticing any issues on receive audio.

Is the CAT connection USB?   Are all power saving settings turned off?

Neil, KN3ILZ

On 12/8/2020 11:30 AM, LA7NO wrote:
Yes, I am aware of it being a CAT error.
The fault is also coming when only receiving, so RFI is out of the question.

P-T, LA7NO



locked Re: Rig Control Error and Remoterig

LA7NO
 

Thanks, Reino.
Silly oversight from me.

I get this one:

Hamlib error: Command rejected by the rig while opening connection to rig

P-T, LA7NO


locked Re: Rig Control Error and Remoterig

renzociarpella@gmail.com
 

I get this error warning in the last two versions and it is always the same.
RFi is to be excluded because for reasons of antennas crash I cannot transmit, therefore only RX, much less USB because I would not understand why when I use the COMMANDER.exe program of the DXLab suite the problem does not arise.
And then the warning indicates that it is "Hamlib error: Invalid parameter to obtain the current VFO".

My help ends here, thank you for what can be done.

Renzo I6KZR

snap

Il 08/12/2020 18:50, neil_zampella ha scritto:

I only mentioned it because you mentioned audio.   RFi was mentioned as a possibility as you did not say it occurred when you're receiving only in your original post, just that you're not noticing any issues on receive audio.

Is the CAT connection USB?   Are all power saving settings turned off?

Neil, KN3ILZ

On 12/8/2020 11:30 AM, LA7NO wrote:
Yes, I am aware of it being a CAT error.
The fault is also coming when only receiving, so RFI is out of the question.

P-T, LA7NO




locked Re: W10 build 2004 and WSJT-X only showing the Windows Default audio device w/USB

N5ZY
 

You do have a point - for the amount of time I've wasted trying to fix this issue and with no solution in sight.. maybe I do need to buy a Pi 4... I'm sure I will trade one problem for another problem but.. it can log via IP.. so I could still run Log4OM on windoze and just move WSJT-X over to a Pi... or in my case I guess two Pi's so I can continue running 6m and HF simultaneously.

Ugh.. ok... 


locked Re: Rig Control Error and Remoterig

Reino Talarmo
 

Hi,

Have you tried to click Show Details on that error message window?

73, Reino OH3mA

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of LA7NO
Sent: 8. joulukuuta 2020 21:43
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Rig Control Error and Remoterig

 

The only info I get from WSJT-X, is the shown error window. The same pops up every time.
And, yes, you are right in saying that there can be different  actual comms errors that could result in the same general message.
Maybe the only way to find out for sure, is to have a look into the source code...

P-T, LA7NO


locked Re: Rig Control Error and Remoterig

LA7NO
 

The only info I get from WSJT-X, is the shown error window. The same pops up every time.
And, yes, you are right in saying that there can be different  actual comms errors that could result in the same general message.
Maybe the only way to find out for sure, is to have a look into the source code...

P-T, LA7NO


locked Re: Expiring Version?

Reino Talarmo
 

At opening it informs Jan 19, 2021
73, Reino OH3mA

-----Original Message-----
From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of John, K9MM
Sent: 8. joulukuuta 2020 21:29
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Expiring Version?

What is the expiration date for WSJT-X 2.3.0-rc2?

73, John


locked Re: Rig Control Error and Remoterig

Bill Somerville
 

Peter,

Per-Tore, LA7NO, has not shared the details of the error message, you cannot possibly assert that you have seen the same error when you do not know anything about it other than it is a general CAT control issue.

73
Bill
G4WJS.

On 08/12/2020 19:25, 2E0PWX wrote:
that error is what i get when i run WSJT-x without FLRig running or if FLRig crashes / loses comms


or when the wrong rig is specified in the setup transciever page

confirm the BAUD, stopbits, retries etc are configured correctly, and ensure the USB to serial adapter has not been confirmed to shut down to save power



peter

2E0PWX

On Tue, 08/12/2020 17:20, neil_zampella wrote:

That's not an audio error, that's a rig control error (CAT) error.    Audio would show a completely different error message.

As to what is causing it, does it happen on certain bands?   If so, it could be RFi in the shack.

Neil, KN3ILZ

On 12/8/2020 11:08 AM, LA7NO wrote:
We use TS-480SAT remote over a Remoterig RRC-1258MkII Internet link..
We are experiencing frequent Rig Control Error.




While this message is up, the radio audio is normal. We can also not hear any oddities on the received audio.
So, the problem is rather intermittent. Pressing Retry, and all is well again.
Radio COMport is set to 9.600 Baud

We expect the fault is due to deficiencies on the Internet link from our provider.
We wonder if there is anything at all we can do on our side to improve on the situation.
Exactly what in Hamlib is triggering this error?

Best 73,

Per-Tore / LA7NO



locked Re: Expiring Version?

John, K9MM
 

What is the expiration date for WSJT-X 2.3.0-rc2?

73, John


locked FT8 Round Up contest

n6rsh
 

Hi,

 I know the contest is over but I had a problem with the set-up with N1MM+. Everything worked fine except the exchange. I couldn't seem to get it to send the required report for the RU contest. When I run WSJT-X alone WITHOUT N1MM+ it works fine. WSJT sends our the proper exchange (ex 579 NE). However when I run WSJT WITH N1MM+ it sends out a normal FT8 exchange (ex -03 DN81). despite setting WSJT in contest mode in the advanced settings). What did I do wrong?

I would like to have this working for next year's contest. 
Thanks & 73,
Steve - N6RSH

16401 - 16420 of 35419