Date   

locked Re: Controlling IC-9700 with Ubuntu 18.04 #linux

Bill Somerville
 

On 10/05/2021 04:38, william.sussman@... wrote:
Hello,

I am a college student and new to ham radio. For my senior project I decided to attempt EME/Moonbounce. I have an IC-9700 and a PC running Ubuntu 18.04 with WSJT-X v2.2.2. I am having trouble setting up CAT. I think the problem is the Serial Port. None of {/dev/ttyUSB0, /dev/ttyUSB1, USB} works. Any advice would be appreciated.

Thanks,
Will (KD2TGH)

Hi Will,

have you added your user to the dialout group?

sudo adduser $USER dialout

Then restart your desktop session or reboot. Use the 'id' command to check you group memberships.

73
Bill
G4WJS.


locked Re: #CQ Mode

Bill Somerville
 

On 09/05/2021 23:51, JoAnn Donaldson via groups.io wrote:
I can set TX6 to say CQ MO-KS-LA AB8YZ EM12 but when it transmits is says <....> AB8YZ.

JoAnn
AB8YZ
Hi JoAnn,

the standard message formats of WSJT-X 77-bit payload modes like MSK144, FT8, FT4, and FST4 allow for a one to four letter word to be inserted between a CQ and your callsign. The '-' character is not a letter.

73
Bill
G4WJS.


locked Re: unable to run wsjtx #install

Bill Somerville
 

On 09/05/2021 22:23, Regin, OY1R wrote:
i installed wsjtx from software manager in linux mint 20, but when i launch it, nothing happens at all !
executing wsjtx in terminal returns:
wsjtx: error while loading shared libraries: libboost_date_time.so.1.67.0: cannot open shared object file: No such file or directory

libboost-date-time-dev installed
Thanks

Regin OY1R
Hi Regin,

which version of WSJT-X are you installing?

73
Bill
G4WJS.


locked Re: Trying to install WSJT-X ver 2.3.1 #WSJTX_config

Bill Somerville
 

On 09/05/2021 18:54, KB3TC wrote:
Trying to install WSJT-X ver 2.3.1 on Ubuntu  I am not very good with linux but trying. When I tried to install using sudo dpkg -i wsjtx_2.3.1_amd64.deb  it comes back with an errors.
Any help is appreciated. I wanted to try out the new FST4 but I am on an older version. Here is the output from the install :
(Reading database ... 212417 files and directories currently installed.)
Preparing to unpack wsjtx_2.3.1_amd64.deb ...
Unpacking wsjtx (2.3.1) over (2.3.1) ...
dpkg: dependency problems prevent configuration of wsjtx:
 wsjtx depends on libboost-log1.62.0 (>= 1.62.0) | libboost-log1.65.1 (>= 1.65.1) | libboost-log1.67.0 (>= 1.67.0) | libboost-log1.71.0 (>= 1.71.0) | libboost-log1.74.0 (>= 1.74.0); however:
  Package libboost-log1.62.0 is not installed.
  Package libboost-log1.65.1 is not installed.
  Package libboost-log1.67.0 is not installed.
  Package libboost-log1.71.0 is not installed.
  Package libboost-log1.74.0 is not installed.
 wsjtx depends on libboost-log1.71.0; however:
  Package libboost-log1.71.0 is not installed.

dpkg: error processing package wsjtx (--install):
 dependency problems - leaving unconfigured
Processing triggers for gnome-menus (3.36.0-1ubuntu1) ...
Processing triggers for desktop-file-utils (0.24-1ubuntu3) ...
Processing triggers for mime-support (3.64ubuntu1) ...
Processing triggers for man-db (2.9.1-1) ...
Errors were encountered while processing:
 wsjtx
Hi OM,

what version of Ubuntu are you using?

73
Bill
G4WJS.


locked Re: #WSJTX_config #WSJTX_config

Bill Somerville
 

On 09/05/2021 17:55, Wes Elton wrote:
Hi All,
"Highlighting a new country". Under General/Display I've checked the Show DXCC box and under Colours/Decode Highlighting I've checked the New DXCC on band box.
With these settings, I expected the Band Activity window to show me any new DXCC entity highlighted in the selected colour.
What actually happens is that a country already worked is sometimes highlighted!
Can someone please advise what settings I need to change achieve the required new country highlight?

Also, consider the band activity window shows a station working a country new to me, e.g P5ABC  GW3DEF -5 is displayed. I (we) need P5.
Given WSJT-X creates a logbook of all past contacts, is there a setting that would check in the log and then highlight that P5ABC as a wanted country?
If not currently available, could this be a feature included in a future update?
I'd appreciate any/all advice. 73 es stay safe Wes. GW3RIH.
Hi Wes,

only CQ or QRZ messages are scanned for highlighting.

73
Bill
G4WJS.


locked Re: WSJT-X Windows - FT-891 Data Mode doesn't receive any signals - Audio sound like broken speaker #FT8 #Yaesu

Komkit Listisard
 

Check the width setting.  FT891 have a very bad habit of not remembering the width setting.  Verify if it is set to 3KHz,  891 like to go back to 500Hz setting.

73, Kit W3KIT


locked Controlling IC-9700 with Ubuntu 18.04 #linux

william.sussman@...
 

Hello,

I am a college student and new to ham radio. For my senior project I decided to attempt EME/Moonbounce. I have an IC-9700 and a PC running Ubuntu 18.04 with WSJT-X v2.2.2. I am having trouble setting up CAT. I think the problem is the Serial Port. None of {/dev/ttyUSB0, /dev/ttyUSB1, USB} works. Any advice would be appreciated.

Thanks,
Will (KD2TGH)


locked #CQ Mode

JoAnn Donaldson <joannplano2005@...>
 

I can set TX6 to say CQ MO-KS-LA AB8YZ EM12 but when it transmits is says <....> AB8YZ.

JoAnn
AB8YZ


locked Trying to install WSJT-X ver 2.3.1 #WSJTX_config

KB3TC
 

Trying to install WSJT-X ver 2.3.1 on Ubuntu  I am not very good with linux but trying. When I tried to install using sudo dpkg -i wsjtx_2.3.1_amd64.deb  it comes back with an errors.
Any help is appreciated. I wanted to try out the new FST4 but I am on an older version. Here is the output from the install :
(Reading database ... 212417 files and directories currently installed.)
Preparing to unpack wsjtx_2.3.1_amd64.deb ...
Unpacking wsjtx (2.3.1) over (2.3.1) ...
dpkg: dependency problems prevent configuration of wsjtx:
 wsjtx depends on libboost-log1.62.0 (>= 1.62.0) | libboost-log1.65.1 (>= 1.65.1) | libboost-log1.67.0 (>= 1.67.0) | libboost-log1.71.0 (>= 1.71.0) | libboost-log1.74.0 (>= 1.74.0); however:
  Package libboost-log1.62.0 is not installed.
  Package libboost-log1.65.1 is not installed.
  Package libboost-log1.67.0 is not installed.
  Package libboost-log1.71.0 is not installed.
  Package libboost-log1.74.0 is not installed.
 wsjtx depends on libboost-log1.71.0; however:
  Package libboost-log1.71.0 is not installed.

dpkg: error processing package wsjtx (--install):
 dependency problems - leaving unconfigured
Processing triggers for gnome-menus (3.36.0-1ubuntu1) ...
Processing triggers for desktop-file-utils (0.24-1ubuntu3) ...
Processing triggers for mime-support (3.64ubuntu1) ...
Processing triggers for man-db (2.9.1-1) ...
Errors were encountered while processing:
 wsjtx


locked #WSJTX_config #WSJTX_config

Wes Elton
 

Hi All,
"Highlighting a new country". Under General/Display I've checked the Show DXCC box and under Colours/Decode Highlighting I've checked the New DXCC on band box.
With these settings, I expected the Band Activity window to show me any new DXCC entity highlighted in the selected colour.
What actually happens is that a country already worked is sometimes highlighted!
Can someone please advise what settings I need to change achieve the required new country highlight?

Also, consider the band activity window shows a station working a country new to me, e.g P5ABC  GW3DEF -5 is displayed. I (we) need P5.
Given WSJT-X creates a logbook of all past contacts, is there a setting that would check in the log and then highlight that P5ABC as a wanted country?
If not currently available, could this be a feature included in a future update?
I'd appreciate any/all advice. 73 es stay safe Wes. GW3RIH.


locked Off Topic but relevant - RE: [WSJTX] Loss of QSO data when logging previous QSO. #logging #IssueReport

Bob Turner
 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Philip Rose via groups.io
Sent: Saturday, May 8, 2021 2:17 PM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Loss of QSO data when logging previous QSO. #logging #BugReport

 

Thanks Bill, I doubled clicked the partner’s report and that doesn’t populate the DX Grid. I have a personal problem that I can’t always double-click fast enough.

 

73 Phil GM3ZZA

 

Sent from Mail for Windows 10

 

From: Bill Somerville
Sent: 08 May 2021 18:20
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Loss of QSO data when logging previous QSO. #logging #BugReport

 

On 07/05/2021 15:31, Philip Rose via groups.io wrote:

> I have had the following scenario a couple of times. When I am completing a QSO, I send RR73 and wait for the QSO partner to either repeat his report, send 73 or send nothing before logging the QSO. If I am called by another station, I double click on that to start the QSO. I then log the first QSO. When I log it the DX Call and DX Grid of the second station are removed and the auto-sequencing stops.

> Is there a way to stop the act of logging from removing the details OF A NEW QSO.

> -- 73 Phil GM3ZZA

 

Hi Phil,

 

"Settings->Reporting->Clead DX call and grid after logging" controls

that behaviour. OTOH you can always double-click the message from the

second caller again to restart the sequencing with correct details.

 

73

Bill

G4WJS.

 

 


--
73 Phil GM3ZZA


locked VS: VS: [WSJTX] Copy And Paste Not Working #general

Reino Talarmo
 

Hi David,

You explained that behaviour completely, thanks!
Well, there could be a lot of other minor issues WSJT-X could do better, but once your know what is happening you should just “obey” the “rules”, I think.

73, Reino OH3mA

 

Lähettäjä: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] Puolesta David - AK2L
Lähetetty: 09 May 2021 02:41
Vastaanottaja: main@WSJTX.groups.io
Aihe: Re: VS: [WSJTX] Copy And Paste Not Working #general

 

Hi Reino,
Thanks for responding.  To answer your question... Yes, I can paste into Notepad just fine.
I think I see the problem.  Perhaps you can test this to see if you get the same behavior.
If I select a call sign with an extra space such as "3D2ZK ", copy it to the clipboard, and then try to paste it into WSJT-X, it fails to paste.
If instead I select a call sign with no extra spaces such as "3D2ZK", it seems to work.
Perhaps the clipboard handler in WSJT-X could be more forgiving by trimming whitespace off of the text rather than rejecting it completely.
AK2L, David


locked Re: Detected dropped audio source samples and Syslog #AudioIssues #logging

Richard Waterman
 

That's great, many thanks Bill.

73, Richard, G4KRW


locked Re: T/R 30s seems to be a default now in -RC4 #MSK144 #Q65

NR4U Bob AFMARS
 

Hello Bill,
Saturday, May 8, 2021, 6:10:10 AM, you wrote:
----------------------------------------------------

Hi Bob,
where different parameters are used for different bands and/or
modes we would always recommend using configurations
----------------------------------------------------
Thanks Bill, and others, especially Gary too(blushing_shy), I am setting up the configurations now.
And Like Roger, I will have at least 12, hi hi ...three rigs plus the SDR-for-RX variations

again, thanks for the reply(s)


--
Best regards,
Bob KD7YZ



--
--
Bob KD7YZ in NE Kentucky


locked Re: No PWR out on Tx #FT8

DF3ED
 

Hello Bob,

I see the same effect when I push the tune button before.
In the windows sound window I see that sound output
switches to the time when wsjt is in receive state and
sound output stops when wsjt switches to transmit state.
It is an inversion .....

Restart of wsjt without using tune button normaly helps me.

I think it is a bug .....
--

73 de DF3ED
Peter


locked WSJT-X Windows - FT-891 Data Mode doesn't receive any signals - Audio sound like broken speaker #FT8 #Yaesu

N3JF
 

The following is all about FT8 on the FT-891:

When I run the Windows latest version of WSJT-X and configure it to talk directly to my FT-891 through a Signalink USB, it works great when the communication mode is set to USB.

If I change the mode to Data/Pkt in WSJT-X, the audio coming from the radio's speaker becomes very quiet. If I turn it up, the audio sounds like a broken speaker... popping and crackling. The received audio tone out of the speaker is very low. Transmit audio sounds fine. When WSJT-X transmits, it'll adjust the TX frequency according to the TX frequency set in the Waterfall, but it doesn't always properly RESET it to 7.040MHz. When this happens, the transmitter "walks down the band".

If I configure WSJT-X to use FLRig and Data/Pkt mode, and set FLRig to use DATA-U, I hear more normal FT8 tone, but they're considerably more "muffled". In fact, I don't think I've made a single contact using DATA mode!

If I configure both FLRig and WSJT-X to use USB, I make contacts all day long.... However... when the radio first keys up, the microphone is live for about 1/4 - 1/2 a second and I can hear room noise/feedback while listening to my transmitted audio on another radio.  If I configure WSJT-X to talk directly to the FT-891 (no FLRig involved), the same thing happens... unless I configure WSJT-X to use RTS for PTT (RTS is disabled in the radio menu). I cannot do the same thing when using FLRig as all the available ports give me an error message.

Why doesn't WSJT-X work when it's connected directly to the FT-891 in DATA mode (deep popping/crackling audio from the speaker, WSJT-X doesn't hear ANY signals)?

Why does WSJT-X keep the mic live for a short period in USB mode before it starts transmitting FT8 tones?

Why does WSJT-X (intermittently, but very frequently) not correctly restore the radio to the correct receive frequency after transmitting?

I appreciate any help!

73


locked Re: VS: [WSJTX] Copy And Paste Not Working #general

David - AK2L
 

Hi Reino,
Thanks for responding.  To answer your question... Yes, I can paste into Notepad just fine.
I think I see the problem.  Perhaps you can test this to see if you get the same behavior.
If I select a call sign with an extra space such as "3D2ZK ", copy it to the clipboard, and then try to paste it into WSJT-X, it fails to paste.
If instead I select a call sign with no extra spaces such as "3D2ZK", it seems to work.
Perhaps the clipboard handler in WSJT-X could be more forgiving by trimming whitespace off of the text rather than rejecting it completely.
AK2L, David


locked Re: Loss of QSO data when logging previous QSO. #logging #IssueReport

 

Thanks Bill, I doubled clicked the partner’s report and that doesn’t populate the DX Grid. I have a personal problem that I can’t always double-click fast enough.

 

73 Phil GM3ZZA

 

Sent from Mail for Windows 10

 

From: Bill Somerville
Sent: 08 May 2021 18:20
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Loss of QSO data when logging previous QSO. #logging #BugReport

 

On 07/05/2021 15:31, Philip Rose via groups.io wrote:

> I have had the following scenario a couple of times. When I am completing a QSO, I send RR73 and wait for the QSO partner to either repeat his report, send 73 or send nothing before logging the QSO. If I am called by another station, I double click on that to start the QSO. I then log the first QSO. When I log it the DX Call and DX Grid of the second station are removed and the auto-sequencing stops.

> Is there a way to stop the act of logging from removing the details OF A NEW QSO.

> -- 73 Phil GM3ZZA

 

Hi Phil,

 

"Settings->Reporting->Clead DX call and grid after logging" controls

that behaviour. OTOH you can always double-click the message from the

second caller again to restart the sequencing with correct details.

 

73

Bill

G4WJS.

 

 


--
73 Phil GM3ZZA


locked Re: Detected dropped audio source samples and Syslog #AudioIssues #logging

Bill Somerville
 

On 08/05/2021 17:42, Richard Waterman wrote:
Hello,

I would be grateful if someone could answer a couple of questions for me:

Summary:
1. Am I right in believing that wsjtx_syslog.log started life when wsjt-x 2.3.0 was released?
2. Looking at the Syslog file, I see that I am getting frequent warnings "Detected dropped audio source samples".  What is the likely cause? Why do some warnings have a negative number?

Detail behind my questions:
I am running Windows 10 Pro, latest update on an i&-6700T processor with 16Gb RAM
Processor load rarely exceeds 20% loading (as seen using task manager) and is typically 4-5%
Running wsjt-x 2.3.1
Running latest JTAlert
Running Omnirig
Running Task Manager
Running TeamViewer
Other than that, just background Windows processes.

Warnings occur even with only a couple of stations received on an afternoon 80m band
Here is a short sample from earlier today:

[SYSLOG][2021-05-08 14:25:44.385395][64:53:48.030945][warning] Detected dropped audio source samples: -672 (-0.014 S)
[SYSLOG][2021-05-08 14:25:59.398520][64:54:03.043840][warning] Detected dropped audio source samples: 624 (0.013 S)
[SYSLOG][2021-05-08 14:27:59.400122][64:56:03.044920][warning] Detected dropped audio source samples: 576 (0.012 S)
[SYSLOG][2021-05-08 14:28:59.398204][64:57:03.042325][warning] Detected dropped audio source samples: 480 (0.01 S)
[SYSLOG][2021-05-08 14:32:44.400249][65:00:48.043285][warning] Detected dropped audio source samples: 576 (0.012 S)
[SYSLOG][2021-05-08 14:32:59.389673][65:01:03.032795][warning] Detected dropped audio source samples: -528 (-0.011 S)
[SYSLOG][2021-05-08 14:33:44.401526][65:01:48.044568][warning] Detected dropped audio source samples: 528 (0.011 S)
[SYSLOG][2021-05-08 14:37:44.390367][65:05:48.031884][warning] Detected dropped audio source samples: -480 (-0.01 S)
[SYSLOG][2021-05-08 14:45:29.392119][65:13:33.030680][warning] Detected dropped audio source samples: -480 (-0.01 S)

Radio is a KX3 interfaced via a ZLP Electronics USB Data interface with built in soundcard.
Radio left monitoring on receive 24/7.  No transmission, so there is no Rx/Tx switching

With regards to my syslog question, I occasionally look in the wsjt-x log directory (usually when I think ALL.txt might be getting a bit large) and this time noticed wsjtx_syslog.log.  Not seen that before.  Looking through release notes, I see a mention of additional logging in the notes for 2.3.0_rc2.  I installed 2.3.0 on 5th Feb 2021 and the earliest syslog file I have starts entries from 5th Feb.  There are three syslog files stored in the logs subdirectory of the log directory, dated 01 March 2021, 01 April 2021 and 01 May 2021.  The current syslog file is in the base log directory and is updated dynamically as warnings occur. Presumably, it will be saved to the logs directory on 01 June 2021.

Additional syslog questions: how many files will be kept before "rotation" occurs, as mentioned in the release notes and how do I configure what is logged?  I can't find anything in the user guide.

Would really appreciate any info.

73, Richard, G4KRW
Hi Richard,

small numbers like that can be ignored, we had to set the cut off somewhere. Negative numbers indicate more samples than expected. The counts are for each period of the current mode, there is never an exact expected count due to latencies between soundcard and software. In summary, you have nothing to worry about, if the discrepancies are of the order of 0.5 seconds and happen often then you would have a problem with your audio streaming throughput or system timekeeping.

Log files are rotated monthly or if they exceed a certain size, old rotated logs are deleted. IIRC 12 old logs are kept, the total amount of log data will be small. There are options to increase the logging verbosity using a configuration file, but for most users the default with no logging configuration file will be fine.

73
Bill
G4WJS.


locked Re: T/R 30s seems to be a default now in -RC4 #MSK144 #Q65

Gary - AG0N
 

On May 7, 2021, at 04:35, KD7YZ Bob <kd7yz@...> wrote:

Can't we have Q65 default to 30s and MSK144 always default to 15s when we touch the mode choice?
Thirty seconds is the normal time for MSK144.

Gary - AG0N

12541 - 12560 of 37039