Date   

locked VS: [WSJTX] WUB WUB WUB sound and drop-outs, but only at 20m #FT8 #signalink #txaudio

Reino Talarmo
 

Below are the usage recommendations copied from the Palomar Engineer
Palomar Engineering is hardly an authority on this. They are a MERCHANT.
Hi Jim,
What if that table is just compiled from manufacturers datasheets and net pages?
73, Reino OH3mA


locked PSK REPORTER #GeneralGroupInfo

 

My stn is showing on 40 but not the antenna I have set in the freq. tab
It's just showing my location and LOTW sign on psk reporter.
Any thoughts wud be appreciated.


--
Thanks 73's de NU4N/Dave


locked Re: WSJT-X Crashing on transmit #wsjt-x-crashing

Bruce KX4AZ
 

Have you tried running at a lower RF output power to see if it does the same thing?  Or run full power with a dummy load attached.  That way you could make sure it's not related to stray RF coming into the cables, even with ferrite cores in place I have had problems with certain (unbalanced) antenna loads.


locked Dark Mode Anomaly - FT8>MSK144 #IssueReport

Brad, K8ZM
 

v2.3.1 (GA) Dark Mode anomaly 

When STD messages are populated with a callsign (from Dx Call window) and you switch modes from FT8 to MSK144, the Tx5 field generated changes to light blue with white text. If you click on the down arrow, and select the optional message it switches back to a dark field with white text.  For example, if VE3CALL was the DX Call while in FT8 mode, the STD Messages all correctly apply the dark field.  Switching to MSK144 all field backgrounds are fine except the Tx5 field has <VE3CALL N8GLS> 73 as white text on a light blue background.  Clicking on the down arrow from that field and selecting the optional message TNX 73 GL and the dark background is applied, all other fields are fine.  If the STD messages are blank all the field backgrounds are normal (dark background with white text).  This seems to only occur when switching from FT8 to MSk144, if switching from MSK144 back to FT8 the light blue field background goes back to a dark background with white text.  Thought this was worth reporting.

73 de Brad, N8GLS


locked Re: MSK144 Operating the showers (Lyrides)? #QSO_practices #MSK144

Carlos
 

Hi everybody,
I am now QRV on MS-50.280 for at least 2 Months, I am well in working normal QSO.
Now, in a few days; the Lyrides meteor shower is voming up.
Please tell how to operate this issue and not to disturb the other stations.
Should I tick the TxCQ260 ?
Or just call CQ on the Region 1 QRG: 50,280 ??
thanks for answer, 73, Karl OE3JAG


locked Re: Adding an ic9700 cross posted in ham apps group #GeneralGroupInfo

Chip
 

I have. And it frequently locks up (spinning beachball) when I try. What has worked is the following sequence:
1. quit WSJT-X
2. change radios in logging software (MacLoggerDX)
3. launch WSJT-X
4. change configurations in WSJT-X

Even with this though, I sometimes have to start and restart WSJT-X a couple of times.

This is still an improvement over my struggles before without being able to distinquish between the audio inputs. So I'm one step closer.

--Chip/N1MIE

On Apr 13, 2021, at 08:41, Reino Talarmo <reino.talarmo@...> wrote:



By the way have you tried Configurations? Those should work without any need for quitting or restarting.

73, Reino OH3mA

 

Lähettäjä: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] Puolesta Chip via groups.io
Lähetetty: 13 April 2021 00:36
Vastaanottaja: main@wsjtx.groups.io
Aihe: Re: [WSJTX] Adding an ic9700 cross posted in ham apps group #GeneralGroupInfo

 

I thought I knew my way around the Mac pretty well, but that’s a new one on me. I was able to successfully make that work. Seems to work pretty well. It’s still a little quirky to switch between radios, but it works better than before. The only way I’ve found to successfully switch is to quit WSJT-X, switch radios in MacLoggerDX, then restart WSJT-X. The times I’ve done this I have found I sometimes have to restart WSJT-X multiple times and might have to force quit it. That said, I am one step closer to smooth operation than I was before. Thanks.



On Apr 12, 2021, at 12:29, ALLAN LOVETT via groups.io <allanl3561@...> wrote:

 

For the Mac, you can use the Audio Midi Setup App (usually in the Utilities folder in Applications) to create new Aggregate devices (like IC9700 in and IC9700 out and IC7300 in and IC7300 out which use the inputs and outputs of the USB Audio Codec for the correct radio. These will show up as additional audio devices that you can choose. You will have to initially use trial and error ( or just connect one at a time) to find out which is which, since both Audio codec from the two radios have the same name as you pointed out

 



73,

--de Chip (N1MIE) FN41bn

 





locked Re: WSJT-X Crashing on transmit #wsjt-x-crashing

Bill Somerville
 

On 13/04/2021 12:28, Panther 353PA wrote:
I am running WSJT-X on a Raspberry Pi 400. This error occurs on both 2.3.1 and 2.40.-rc4 versions with Hamlib 4.1 installed. I am using a USB data cable with a ferrite and about 5 turns through it and an IC-705. I use the same cable on my Macbook without issue. Less than five seconds into transmit the application crashes with no message and the radio is stuck in transmit mode. From the WSJT-X log I found the following;

[SYSLOG][2021-04-13 02:14:17.304476][00:00:11.327444][error] handle_transceiver_failure: reason: Hamlib error: Command rejected by the rig
rig.c(1488):set_cache_freq return(0)
rig_set_vfo: return -9, vfo=VFOB
rig.c(2516):rig_set_vfo return(-9) while exchanging VFOs
[RIGCTRL][2021-04-13 02:14:17.305876][00:00:11.328842][error] error: Command rejected by the rig
frame.c(355):icom_transaction return(-9)
icom.c(3661):icom_set_ptt return(-9)
rig.c(2650):rig_set_ptt return(-9)
[SYSLOG][2021-04-13 02:14:29.470977][00:00:23.493949][warning] Detected dropped audio source samples: 2,064 (0.043 S)
[SYSLOG][2021-04-13 02:14:43.297421][00:00:37.320392][info] Log Finish
I am stumped. Thoughts?

OM,

so I can see what is happening put the attached file into your WSJT-X configuration files directory (~/.config/), restart WSJT-X, do the minimum steps to reproduce the issue, then quit WSJT-X. There will be a new file on your Desktop called WSJT-X_RigControl.log , send me (g4wjs <at> classdesign <dot> com) that file for analysis please?

Once you have sent the log file delete the log file and the log configuration file to return to normal operation.

73
Bill
G4WJS.


locked Re: WSJTX does not register with pulsaudio for playback

Bill Somerville
 

On 13/04/2021 11:30, petko.marek@... wrote:
Hi all,

I am facing exactly the same issue as Ted Wood does. I have Xubuntu 20.04.2 LTS. Originally I had WSJT-X 2.0.2 from the repository, then I switched to WSJT-X 2.3.1.

My WSJT-X audio devices are set to default on both transmit and receive. I only have one on-board sound card in a laptop. On receive I can see WSJT-X in the Recording tab of the Pulseaudio Control Panel as ALSA Plug-in. On transmit I do not see anything except system sounds. (Other apps like Firefox produce sounds just fine.)

I tried deleting the $HOME/.config/WSJT-X.ini and $HOME/.local/share/WSJTX/ as suggested, but it did not cure the problem. However, on random occasions, say 1 out of 50 attempts, I can hear beep after pressing the TUNE button right after the WSJT-X starts. And the WSJT-X shows in the Pulse Audio Control Panel. I could not find any consistency when it does beep and when not.

As well as Ted, I cannot close the WSJT-X properly. When pressing the [X] button, the window disappears, but the process keeps running and needs to be terminated by the kill command. This is consistent and every time.

I should also mention that before I replaced HDD in my laptop, I had very old Xubuntu version installed, I reckon it could have been 16.04 or 18.04 and there it just worked. The WSJT-X was also one of the early 2.x.x versions.

Any suggestions are welcome. I have to admit that this looks like a bug to me, since all other apps work just fine with sound.

Marek

Hi Marek,

what do the following commands print?

pactl list short sources
pactl list short sinks

73
Bill
G4WJS.


locked Re: European FT8 contest - any published results? #FT8

Pete Ritter K5CPR
 

I entered and submitted my log. I received no acknowledgement. I could find no results from past contests on the web site. There is a link to archives but the only material I found there was announcements of previous years' contests. 

I hope it isn't somebody's idea of a prank. 


locked Re: WUB WUB WUB sound and drop-outs, but only at 20m #signalink #txaudio #FT8

Jim Brown
 

On 4/13/2021 9:33 AM, Karl Beckman wrote:
Below are the usage recommendations copied from the Palomar Engineer
Palomar Engineering is hardly an authority on this. They are a MERCHANT.

73, Jim K9YC


locked Re: WUB WUB WUB sound and drop-outs, but only at 20m #signalink #txaudio #FT8

Karl Beckman WA8NVW - NNV5BH
 
Edited

Sorry for the simple typo that seems to have upset the entire rather vocal ham community.  I meant to type '73' instead of '72', but then I missed reading table note 7 regarding the non-availability of larger core sizes and substitution of type 75 for many uses.
Below are the usage recommendations copied from the Palomar Engineer web page https://palomar-engineers.com/ferrite-products/ferrite-cores/ferrite-mix-selection
...

The table below gives our recommended applications for various mixes and effective frequency ranges

Mix # Material Initial Permeability RFI/EMI Common Mode Suppression Range Tuned Circuits – Coil
Wide Band Transformer
31  (1) MnZn 1500 1-300 MHz 1:1 only, <300 MHz
43 (2) NiZn 800 25-300 MHz < 10 MHz 3-60 MHz
52 (6) NiZn 250  200-1000 MHz < 20 MHz 1-60 MHz
61 (3) NiZn 125 200-1000 MHz  <100 MHz 1-300 MHz
73 (7) MnzN 2500 < 50 MHz < 2 MHz <10 MHz
75/J (4) MnZn 5000 150 KHz – 10 MHz  < .75 MHz  .1-10 MHz


Notes
...

(4) Mix 75 (also known as Mix J) is a high permeability MnZn ferrite intended for a range of broadband and pulse transformer applications and common-mode inductor designs. Excellent for common mode suppression on AM broadcast frequencies from 500 KHz-1.8 MHz.  Also very useful for medical instrument transducer isolation, inverter assemblies, inductive motors and control units. Curie temperature >140 C. Mix 75 is available in TOROIDS,   SLIP ON BEADS, ,and SNAP ON SPLIT BEADS,

  • Optimized to solve low-frequency EMI issues between 150 kHz and 10 MHz
  • Suppresses common-mode noise up to 30 MHz
  • Replaces expensive line filters to mitigate conducted noise
  • Split core performance closely resemble solid cores, allowing seamless transitions from test to production

Applications:

  • Automotive: Inverter assemblies, inductive motors
  • Consumer Electronics: Power supplies, peripheral cables
  • Medical: Transducer isolation, human-machine interfaces
  • White Goods: Control units, motors

(7) Mix 73 only available in small bead size, for larger inside diameter requirements, use mix 75 or 77

Feel free to discuss among yourselves the relative performance  of your favorite blend, remembering that the RF freq inducing trouble is 14 MHz.  And a toroid from Fair-Rite is NOT the same as a ferrite toroid.

[p.s.  JIM K9YC - I've read and downloaded your excellent papers and understand the principles involved in Pin 1.  I'm also one of (numerous) contributors to the Motorola R56 Site Standards document.]


- - 
Karl  WA8NVW  OH
WA8NVW@...
in WSJTX@groups.io


locked Re: European FT8 contest - any published results? #FT8

Kermit Lehman
 

Thanks, Geza.


Yes, I think the contest is fake and the web site is a promotional site for MSHV and WSJT-Z.  


Z for Zombie contest..


I do like the "contest " for low pressure practice.  FT contesting is trickier than it looks and I need practice.


73,

Ken, AB1J

-----Original Message-----
From: Geza Szabados-Hann <dg5lp@...>
To: main@WSJTX.groups.io
Sent: Tue, Apr 13, 2021 2:58 pm
Subject: Re: [WSJTX] European FT8 contest - any published results? #FT8

No results found from neither form last year, nor from this year. It seems to be a fake contest organized by a fake-club.
No answer on e-mail requests, no responsible contest manager, no list of members  etc., but a very detailed
description how to use MSHV on the contest. Evil be to him who evil thinks..

73,

Geza, DG5LP




locked Re: IC-7400 and WSJTX V1.9.1 #WSJTX_config

Karl Beckman WA8NVW - NNV5BH
 

DAVE -
Previous postings to initiate this thread were made in November 2018, and reflect the current WSJT-X version at that time.  It helps to read back to the beginning of the thread before resurrecting out-of-date queries.
--
Karl  WA8NVW  OH
WA8NVW@...
in WSJTX@groups.io


locked Re: European FT8 contest - any published results? #FT8

Geza Szabados-Hann
 

No results found from neither form last year, nor from this year. It seems to be a fake contest organized by a fake-club.
No answer on e-mail requests, no responsible contest manager, no list of members  etc., but a very detailed
description how to use MSHV on the contest. Evil be to him who evil thinks..
73,
Geza, DG5LP


locked WSJT-X Crashing on transmit #wsjt-x-crashing

Panther 353PA
 

I am running WSJT-X on a Raspberry Pi 400. This error occurs on both 2.3.1 and 2.40.-rc4 versions with Hamlib 4.1 installed. I am using a USB data cable with a ferrite and about 5 turns through it and an IC-705. I use the same cable on my Macbook without issue. Less than five seconds into transmit the application crashes with no message and the radio is stuck in transmit mode. From the WSJT-X log I found the following;

[SYSLOG][2021-04-13 02:14:17.304476][00:00:11.327444][error] handle_transceiver_failure: reason: Hamlib error: Command rejected by the rig
rig.c(1488):set_cache_freq return(0)
rig_set_vfo: return -9, vfo=VFOB
rig.c(2516):rig_set_vfo return(-9) while exchanging VFOs
[RIGCTRL][2021-04-13 02:14:17.305876][00:00:11.328842][error] error: Command rejected by the rig
frame.c(355):icom_transaction return(-9)
icom.c(3661):icom_set_ptt return(-9)
rig.c(2650):rig_set_ptt return(-9)
[SYSLOG][2021-04-13 02:14:29.470977][00:00:23.493949][warning] Detected dropped audio source samples: 2,064 (0.043 S)
[SYSLOG][2021-04-13 02:14:43.297421][00:00:37.320392][info] Log Finish
I am stumped. Thoughts?


locked Re: WSJTX does not register with pulsaudio for playback

petko.marek@...
 

Hi all,

I am facing exactly the same issue as Ted Wood does. I have Xubuntu 20.04.2 LTS. Originally I had WSJT-X 2.0.2 from the repository, then I switched to WSJT-X 2.3.1.

My WSJT-X audio devices are set to default on both transmit and receive. I only have one on-board sound card in a laptop. On receive I can see WSJT-X in the Recording tab of the Pulseaudio Control Panel as ALSA Plug-in. On transmit I do not see anything except system sounds. (Other apps like Firefox produce sounds just fine.)

I tried deleting the $HOME/.config/WSJT-X.ini and $HOME/.local/share/WSJTX/ as suggested, but it did not cure the problem. However, on random occasions, say 1 out of 50 attempts, I can hear beep after pressing the TUNE button right after the WSJT-X starts. And the WSJT-X shows in the Pulse Audio Control Panel. I could not find any consistency when it does beep and when not.

As well as Ted, I cannot close the WSJT-X properly. When pressing the [X] button, the window disappears, but the process keeps running and needs to be terminated by the kill command. This is consistent and every time.

I should also mention that before I replaced HDD in my laptop, I had very old Xubuntu version installed, I reckon it could have been 16.04 or 18.04 and there it just worked. The WSJT-X was also one of the early 2.x.x versions.

Any suggestions are welcome. I have to admit that this looks like a bug to me, since all other apps work just fine with sound.

Marek



locked VS: [WSJTX] Transmit poser #GeneralGroupInfo

Reino Talarmo
 

Do you mean by input DC power to your final amplifier or RF input to an external power amplifier?

Well, that recommendation is two-folded, with a typical 100 W rig 30-35 W is (really) safe output power to keep rig’s temperature in safe limits.

The second is based an idea that FT8 is a low power mode. That as such is misleading as FT8 is a weak signal mode i.e. received signal is weak. It is recommended to use an output power which returns to you signal report around zero or less, it depends on propagation and YMMV.

73, Reino OH3mA

 

Lähettäjä: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] Puolesta rm77027@...
Lähetetty: 13 April 2021 03:12
Vastaanottaja: main@WSJTX.groups.io
Aihe: [WSJTX] Transmit poser #GeneralGroupInfo

 

We are advised to use around 30-35 watts on FT8. Input or output?
73
Roger/K0kon


locked VS: [WSJTX] Adding an ic9700 cross posted in ham apps group #GeneralGroupInfo

Reino Talarmo
 

By the way have you tried Configurations? Those should work without any need for quitting or restarting.

73, Reino OH3mA

 

Lähettäjä: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] Puolesta Chip via groups.io
Lähetetty: 13 April 2021 00:36
Vastaanottaja: main@wsjtx.groups.io
Aihe: Re: [WSJTX] Adding an ic9700 cross posted in ham apps group #GeneralGroupInfo

 

I thought I knew my way around the Mac pretty well, but that’s a new one on me. I was able to successfully make that work. Seems to work pretty well. It’s still a little quirky to switch between radios, but it works better than before. The only way I’ve found to successfully switch is to quit WSJT-X, switch radios in MacLoggerDX, then restart WSJT-X. The times I’ve done this I have found I sometimes have to restart WSJT-X multiple times and might have to force quit it. That said, I am one step closer to smooth operation than I was before. Thanks.



On Apr 12, 2021, at 12:29, ALLAN LOVETT via groups.io <allanl3561@...> wrote:

 

For the Mac, you can use the Audio Midi Setup App (usually in the Utilities folder in Applications) to create new Aggregate devices (like IC9700 in and IC9700 out and IC7300 in and IC7300 out which use the inputs and outputs of the USB Audio Codec for the correct radio. These will show up as additional audio devices that you can choose. You will have to initially use trial and error ( or just connect one at a time) to find out which is which, since both Audio codec from the two radios have the same name as you pointed out

 



73,

--de Chip (N1MIE) FN41bn

 


 

I tried PSK reporter this morning and the counter is not showing reports. I am on 40 FT8 and the antenna shows on reporter a 30/60 OFCD. I have my antenna for Hustler vertical/40-80 vee. I even e-mailed Phillip but heard nothing yet??
--
Thanks 73's de NU4N/Dave


locked Re: FT-8 CQ's not answered #FT8

Fred Kepner
 

Hi Rich,

To me, it sounds like you may not be transmitting.  I would start by calling CQ a few times and then checking https://pskreporter.info/pskmap.html for your callsign.  If no one is hearing you, then you aren't getting out and we'll know where to start troubleshooting.

73
Fred
K3FRK

16021 - 16040 of 40097