Date   

locked Re: Error Writing Wave File

Bill Somerville
 

On 11/05/2021 21:18, Don N7BT wrote:
This comes up regularly.. I have to shut down and sometimes use Task manager to get out of WSJT.

Any idea on what to do to correct this?
Hi Don,

one likely cause is another application interfering with access to files, your anti-virus product may well do that. Try whitelisting the "%LocalAppData%\WSJT-X" directory in your AV product.

73
Bill
G4WJS.


locked Re: WSJT-X LOSES TUNE AND XMT CAPABILITY #general

Dave Garber
 

more information would be needed,  output power used, radio type operating system wsjt version...

please give details, if you can.



Dave Garber
VE3WEJ / VE3IE


On Tue, May 11, 2021 at 11:45 AM RICHARD GROSS <rgross7068@...> wrote:
I often lose the ability on FT8 and FT4 to Tune or Transmit with Windows 10.. This is only resolved by restarting the program.



locked Error Writing Wave File

Don N7BT
 

This comes up regularly.. I have to shut down and sometimes use Task manager to get out of WSJT.

Any idea on what to do to correct this?


locked Re: Optimum RECEIVE Level dB setting. WSJT-X for FT8 and Q65 #Q65 #AudioIssues #FT8

Martin G0HDB
 

On Tue, May 11, 2021 at 01:07 AM, invl160 Davis wrote:
I am using a TS590SG with version 2.4.0 rc4.  I have been playing with Q65.  Upon not decoding his transmission a friend asked me recently what my receive level setting was on the left hand "level meter".  I said 60.  He said "thats way too high".

Hi Frank, I don't know how the TS590SG behaves but with some rigs, eg. my Icom IC-7610 (and my previous IC-7600), when the AGC is off the audio output from the rig becomes distorted when even modest-strength signals (eg. -85dBm, S3-4) are present at the antenna input.  The presence of any distortion artefacts on the audio being fed from the rig into WSJT-X can really screw up the decoding.

I've found, as has Rob NC0B, that it's best to operate our Icom rigs with the AGC on (with a fast time constant - I use a setting of 0.8secs) and set the various rig and Windows audio level controls so that the WSJT-X audio level 'thermometer' sits at approx the 60dB level when receiving only band noise.  The rig's AGC will ensure that the level of the audio coming out of the rig and going into WSJT-X nevers gets near the clipping threshold - on my 7610 I don't recall ever seeing a reading on the WSJT-X 'thermometer' of more than about 74dB.

You could try operating with your TS590SG's AGC on and setting the audio level controls so that you have a reading of around the 60dB mark, as you have at present, on the WSJT-X 'thermometer'.  At least then you can be confident that you're (almost!) never likely to suffer from the presence of any distortion artefacts on the audio coming out of the rig and going into WSJT-X.

73
--
Martin G0HDB


locked Re: OOB Out of Band Error #IssueReport

Gene Horr
 

The offset was zero.


locked Re: WSJT-X LOSES TUNE AND XMT CAPABILITY #general

Karza
 

I often lose the ability on FT8 and FT4 to Tune or Transmit with Windows 10.. This is only resolved by restarting the program.
Sound like RFI in the shack


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

N3JF
 

On Tue, May 11, 2021 at 09:10 AM, Bill Somerville wrote:

you still haven't told us your name, or what version of WSJT-X you are using.


There's been a lot of posts in this thread... one of which was deleted by the system. That was the one were I gave my name (Julian). Just forgot to include it in the rewrite #24703.

However, from my very first post in this thread, 2nd line:
When I run the Windows latest version of WSJT-X .

Now you have revealed you are using a SIgnaLink USB interface.

Again, from my very first post in this thread, same 2nd line:
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

Bill...

But you should have more luck with one of the Split Operating options if use the SignaLink USB as it was intended to be, use "Settings->Radio->PTT Method->VOX" and turn the SignaLink USB DELAY knob to minimum.

Bingo! That's it! Delay was always at minimum, but the VOX setting in WSJT-X fixes everything. I tried to edit my last post, with radio settings, to include the WDH menu item, setting the filter as wide as it will go (3000), but it doesn't look like the system updated the post.


The reason you have a live mic, throughout your transmission not just at the beginning, is because you are using the USB mode on your rig, I believe the only way to kill the mic audio in USB mode on that rig is to unplug the mic! Use USB-DATA mode as that mutes the mic.


Makes sense. Now USB DATA is working properly. Several contacts made, no walking up the band, audio sounds good, and no live mic!

Very cool! Thank you. I think all issues have been fixed!


locked Re: #WSJTX_config #WSJTX_config

Bill Somerville
 

On 11/05/2021 17:43, Wes Elton wrote:
Hi Bill,

Thanks for your response and understood.
What about the second part to my post (see the P5ABC GW3DEF example.)  Is this a feature that you consider could be incorporated in a later release of WSJT-X?
Can you point me at the software experts so that I could ask the question please?

Thanks again. Stay Safe.
Wes. GW3RIH.
Hi Wes,

currently only CQ and QRZ messages are highlighted for performance reasons. If you are running on MS Windows then the excellent companion application JTAlert can do what you ask. There are also logging applications on Windows and other platforms that can also highlight calls in the WSJT-X decode windows based on your preset DXing goals configured in those applications.

73
Bill
G4WJS.


locked Re: #WSJTX_config #WSJTX_config

Wes Elton
 

Hi Bill,

Thanks for your response and understood.
What about the second part to my post (see the P5ABC GW3DEF example.)  Is this a feature that you consider could be incorporated in a later release of WSJT-X?
Can you point me at the software experts so that I could ask the question please?

Thanks again. Stay Safe.
Wes. GW3RIH.


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

Bill Somerville
 

On 11/05/2021 16:58, N3JF wrote:
I think I may have a usable solution to the FT-891 walking up the band, thanks to Bruce N7XGR who contacted me off-line.

Bruce and I tried several different things, radio settings, WSJT-X settings etc. Then Bruce asked if I had set "Split Operation" to NONE. I had not. I had it set to Fake It", like I have with all my other radios in the past. That setting stopped WSJT-X from changing TX frequency, so it now stays on xx.074.0 for both RX and TX. I'm not sure this is a fix, or the way it "should" be, but it's a usable workaround. Maybe that's just how this radio works, being as it's quite an old radio.

The problem with the Signalink USB making the microphone live for a very short time at the beginning of every FT8 transmission... that's fixed by setting PTT control to RTS and using the same COM port as defined in the radio's CAT control section. If you have PTT Control set to CAT and you're not monitoring your transmissions on another nearby radio, you probably don't know that the Signalink is making the mic active.

As for using DATA mode... forget it! It simply doesn't work properly! The only reason I wanted to use DATA mode was so that I didn't have to keep going to the radio's menu and setting 11-07: SSB BFO to USB (and back to AUTO when I'm done). DATA mode forces the mode to USB so the constant switching of 11-07 wouldn't be required. Oh well.

So, here are my radio settings. They work for FLRig, WSJT-X, Winlink, FLDigi. Some are redundant because they're not used (08-02: PSK TONE, for example) but I left them in so that if anyone wanted to use these settings, they could choose PSK or OTHERS.

FT-891 Settings:
05-06: CAT RATE: 19200
05-08: CAT RTS: DISABLE
08-01: DATA MODE: OTHERS
08-02: PSK TONE: 1500
08-03: OTHER DISP: 1500
08-04: OTHER SHIFT: 1500
08-05: DATA LCUT FREQ: 100
08-06: LCUT SLOPE: 6db/Oct
08-07: DATA HCUT FREQ: 4000
08-08: DATA HCUT SLOPE: 6db/Oct
08-09: DATA IN SELECT: REAR
08-10: DATA PTT SELECT: DAKY
08-11: DATA OUT LEVEL: 50
08-12: DATA BFO: USB

11-07: SSB BFO: USB (when using digital modes on lower bands)  or AUTO (for voice)


WSJT-X Settings:
CAT for rig control (with COM port for your radio);
19200 baud;
USB mode (not Data/Pkt),
PTT control is RTS (with Signalink USB) and same COM port as CAT - This stops mic audio mixing with digital data at beginning of TX
Split Operation: None

Thanks to everyone for your help.

OM,

you still haven't told us your name, or what version of WSJT-X you are using.

Now you have revealed you are using a SIgnaLink USB interface. With that you should not be using RTS or CAT PTT as the SignaLink USB has its own PTT system. Ensure you have the DELAY knob set to minimum, as with rigs that do not accept CAT QSY commands while transmitting, the "Settings->General->Allow Tx frequency changes while transmitting" option unchecked alone is not enough to avoid the rig being in Tx mode when WSJT-X sends CAT commands.

Using "Settings->Radio->Split Operating->None" defeats an important feature of WSJT-X CAT control that allows you to transmit at any audio offset without generating nasty audio harmonics. Without setting one of the "Settings->Radio->Split Operating" options you should really restrict Tx audio offsets to 1500 Hz or higher. But you should have more luck with one of the Split Operating options if use the SignaLink USB as it was intended to be, use "Settings->Radio->PTT Method->VOX" and turn the SignaLink USB DELAY knob to minimum.

The reason you have a live mic, throughout your transmission not just at the beginning, is because you are using the USB mode on your rig, I believe the only way to kill the mic audio in USB mode on that rig is to unplug the mic! Use USB-DATA mode as that mutes the mic.

73
Bill
G4WJS.


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

N3JF
 
Edited

I think I may have a usable solution to the FT-891 walking up the band, thanks to Bruce N7XGR who contacted me off-line.

Bruce and I tried several different things, radio settings, WSJT-X settings etc. Then Bruce asked if I had set "Split Operation" to NONE. I had not. I had it set to Fake It", like I have with all my other radios in the past. That setting stopped WSJT-X from changing TX frequency, so it now stays on xx.074.0 for both RX and TX. I'm not sure this is a fix, or the way it "should" be, but it's a usable workaround. Maybe that's just how this radio works, being as it's quite an old radio.

The problem with the Signalink USB making the microphone live for a very short time at the beginning of every FT8 transmission... that's fixed by setting PTT control to RTS and using the same COM port as defined in the radio's CAT control section. If you have PTT Control set to CAT and you're not monitoring your transmissions on another nearby radio, you probably don't know that the Signalink is making the mic active.

As for using DATA mode... forget it! It simply doesn't work properly! The only reason I wanted to use DATA mode was so that I didn't have to keep going to the radio's menu and setting 11-07: SSB BFO to USB (and back to AUTO when I'm done). DATA mode forces the mode to USB so the constant switching of 11-07 wouldn't be required. Oh well.

So, here are my radio settings. They work for FLRig, WSJT-X, Winlink, FLDigi. Some are redundant because they're not used (08-02: PSK TONE, for example) but I left them in so that if anyone wanted to use these settings, they could choose PSK or OTHERS.

FT-891 Settings:
05-06: CAT RATE: 19200
05-08: CAT RTS: DISABLE
08-01: DATA MODE: OTHERS
08-02: PSK TONE: 1500
08-03: OTHER DISP: 1500
08-04: OTHER SHIFT: 1500
08-05: DATA LCUT FREQ: 100
08-06: LCUT SLOPE: 6db/Oct
08-07: DATA HCUT FREQ: 4000
08-08: DATA HCUT SLOPE: 6db/Oct
08-09: DATA IN SELECT: REAR
08-10: DATA PTT SELECT: DAKY
08-11: DATA OUT LEVEL: 50
08-12: DATA BFO: USB

11-07: SSB BFO: USB (when using digital modes on lower bands)  or AUTO (for voice)

Menu -> WDH -> 3200

WSJT-X Settings:
CAT for rig control (with COM port for your radio);
19200 baud;
USB mode (not Data/Pkt),
PTT control is RTS (with Signalink USB) and same COM port as CAT - This stops mic audio mixing with digital data at beginning of TX
Split Operation: None

Thanks to everyone for your help.


locked WSJT-X LOSES TUNE AND XMT CAPABILITY #general

RICHARD GROSS
 

I often lose the ability on FT8 and FT4 to Tune or Transmit with Windows 10.. This is only resolved by restarting the program.


locked VS: VS: [WSJTX] #CQ Mode

Reino Talarmo
 

Hi  JoAnn,

Why it should not allow more than two characters after CQ? At least I want to make a directed call such as (CQ ASIA OH3MA KP20).
To be honest there most probably is no validity check in the source coding handling. That task would be very demanding and it better to leave checking to the operator.

73, Reino OH3mA

 

Lähettäjä: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] Puolesta JoAnn Donaldson via groups.io
Lähetetty: 11 May 2021 03:16
Vastaanottaja: main@WSJTX.groups.io
Aihe: Re: VS: [WSJTX] #CQ Mode

 

Reino OH3mA

 

   I have discovered this. If you not doing a Contest like Field Day, the software should not allow you to put no more that 2 extra characters (CQ MO AB8YZ EM12) in the TX6 line. At least it shows <...> AB8YZ in the TX Window.

 

JoAnn

AB8YZ

 

 

On Monday, May 10, 2021, 7:03:26 PM CDT, Reino Talarmo <reino.talarmo@...> wrote:

 

 

Hi,

You can put after CQ only one to four letters of exactly three numbers, no special characters, if I remember correctly. So your try fails at least due to the length.

73, Reino OH3mA

 

Lähettäjä: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] Puolesta JoAnn Donaldson via groups.io
Lähetetty: 10 May 2021 01:51
Vastaanottaja: WSJT-x Group <main@wsjtx.groups.io>
Aihe: [WSJTX] #CQ Mode

 

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

 

JoAnn

AB8YZ




locked VS: [WSJTX] #CQ Mode

Reino Talarmo
 

Hi JoAnn,

 

There is no bug! Your message does not follow the rules and the source coding/field definitions try their best meaning that some part of the character string is taken to be a vanity call that is encoded using a hash as marked < . . . >. In that situation locator does not fit into the message and only your call is there in addition to that hashed one.
Your proposal what should happen is a total re-thinking how a “nonsense” message should be encoded, hi! Actually I perhaps missed what was your proposal; did you mean that the sent message should have been “CQ MO-K” ?

73, Reino OH3mA

 

Lähettäjä: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] Puolesta JoAnn Donaldson via groups.io
Lähetetty: 11 May 2021 03:24
Vastaanottaja: main@WSJTX.groups.io
Aihe: Re: [WSJTX] #CQ Mode

 

Kari, oh2gqc

 

In that case, it should stop after the 7th character (CQ TEST). This is a bug and should be an easy fix.

 

JoAnn

AB8YZ

 

 

On Monday, May 10, 2021, 7:04:45 PM CDT, Karza <kari.sillanmaki@...> wrote:

 

 

On 10.5.2021 1.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,

your message doies not confotm to the WSJT-X protocol specification.

I assume you want to send an directed call to MO, KS or LA areas?

Unfortunately you can not do it like that, you can only send 1 to 4 characters after your CQ, such as "CQ MO", "CQ QRP", "CQ TEST" etc.

No hyphens, spaces or other punctuation characters are allowed.

See https://physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.3.1.html#PROTOCOLS

73's de Kari, oh2gqc




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

william.sussman@...
 

Thank you all!

I had already added my user to the dialout group, but never rebooted. That solved the issue.

I decided to upgrade both Ubuntu and WSJT-X. Now I'm using Ubuntu 20.04 with WSJT-X v2.3.1.

I have G-5500DC Az/El rotators supporting two M2 antennas: 2MCP14 (2m) and 436CP30 (70cm). Each antenna connects to a Mirage mast-mount preamplifier: KP-2-2M and KP-2-440, respectively. These ultimately connect to the IC-9700.

What settings do you recommend for EME/Moonbounce? I plan to use just 2m (not 70cm) with JT65. Is that reasonable?

Thank you again,
Will (KD2TGH)


locked Re: #CQ Mode

Karza
 

JoAnn,

On 11.5.2021 3.23, JoAnn Donaldson via groups.io wrote:

In that case, it should stop after the 7th character (CQ TEST). This is a bug and should be an easy fix.

it's not a bug. Please note that JT-protocols use sophisticated algorithms to compress QSO data. Data is not sent character by character as in RTTY or PSK, for example.

( See this https://physics.princeton.edu/pulsar/k1jt/FT4_FT8_QEX.pdf for details )

So, you can set TX6 to something like "CQ MO AB8YZ EM12", "CQ KSMO AB8YZ EM12",  "CQ DX AB8YZ EM12", "CQ YLCA AB8YZ EM12",  "CQ TEST AB8YZ EM12"  or the like, as long as the 'extra' text is  at most 4 characters. long.

73's de Kari , oh2gqc



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

N3JF
 

On Tue, May 11, 2021 at 04:41 AM, William Smith wrote:
Sounds like a problem with intermittent CAT control, try reducing your baud rate?
Thanks for the suggestion. I agree and I tried lower baud rates but that didn't fix the problem. I think I have a solution that works.... I'll write that in a new post.


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

William Smith
 

Sounds like a problem with intermittent CAT control, try reducing your baud rate?

73, Willie N1JBJ

On May 10, 2021, at 8:07 PM, N3JF <n3jf@...> wrote:

The biggest issue, is WSJT-X not resetting the RX frequency to xx.074.00 at the end of a QSO and it "walking" up the band randomly during a QSO!


locked Re: OOB Out of Band Error #IssueReport

Bill Somerville
 

On 11/05/2021 02:16, Gene Horr wrote:
Possible bug report.  I was getting "OOB" errors one one band - 6m.  Everything else worked fine.

The error occurred with two different radios and with both direct connections and going through Ham Radio Deluxe.
The software would sometimes work when going to this band and then later display random numbers in the frequency window with an OOB error.  Other times would immediately produce an OOB error.
If the radio was set to None, the frequency changed manually in the radio, and 6m selected from the band box the software would work and log correctly.

The cause appears to be an entry in the Station Information window under [Settings], [Frequencies].  There was a single entry for 6m.  When this entry was removed the software started working with no problems on 6m.
Hi Gene,

if you enter a transverter offset for a band in the "Settings->Radio->Frequencies->Station Information" table then when you change to that band the offset will be applied and your rig must be able to tune to the offset frequency.

73
Bill
G4WJS.


locked OOB Out of Band Error #IssueReport

Gene Horr
 

Possible bug report.  I was getting "OOB" errors one one band - 6m.  Everything else worked fine. 

The error occurred with two different radios and with both direct connections and going through Ham Radio Deluxe.
The software would sometimes work when going to this band and then later display random numbers in the frequency window with an OOB error.  Other times would immediately produce an OOB error.
If the radio was set to None, the frequency changed manually in the radio, and 6m selected from the band box the software would work and log correctly.

The cause appears to be an entry in the Station Information window under [Settings], [Frequencies].  There was a single entry for 6m.  When this entry was removed the software started working with no problems on 6m.

12181 - 12200 of 36728