Date   

locked Re: new computer, CAT doesn't work right

Bill Somerville
 

Hi Jon,

have you installed the virtual COM port drivers for the rig on your PC?

Do you have the right COM port selected for CAT (you need the extended COM port)?

As you have Hardware handshaking enabled, do you have RTS enabled in the rig's menu?

73
Bill
G4WJS.

On 03/11/2020 01:12, Jon Ermels via groups.io wrote:
Hi Bill, FT-991A, USB on radio to USB on computer, same as old computer. what baffles me is it turns on the radio and decodes and then says the CAT doesn't work.
Com poer at the 
codex port says, 
Baud 38400 same as radio,
8 data bits,
1 stop bit,
HDW hand shake


73 de NØIGU Jon


On Monday, November 2, 2020, 07:01:18 PM CST, Bill Somerville <g4wjs@...> wrote:


On 03/11/2020 00:45, Jon Ermels via groups.io wrote:
>  old computer worked on same radio, new computer, used it for WSJTX
> before with different radio, CODEX ok, WXJTW version 2.2.2, I get rig
> failure message, hamlib error IO error while testing VFO, cat test in
> settings stays red, it decodes whatever freq the radio is set to but
> says it's on 160M, stills start the radio when WSJTX starts up.

Hi Jon,

which radio? How is it connected to your PC for CAT control? What
settings do you have in "Settings->Radio"
com port 6, as the Port says, ?


73

Bill
G4WJS.



locked Re: new computer, CAT doesn't work right

Jon Ermels
 

Hi Bill, FT-991A, USB on radio to USB on computer, same as old computer. what baffles me is it turns on the radio and decodes and then says the CAT doesn't work.
Com poer at the 
codex port says, 
Baud 38400 same as radio,
8 data bits,
1 stop bit,
HDW hand shake


73 de NØIGU Jon


On Monday, November 2, 2020, 07:01:18 PM CST, Bill Somerville <g4wjs@...> wrote:


On 03/11/2020 00:45, Jon Ermels via groups.io wrote:
>  old computer worked on same radio, new computer, used it for WSJTX
> before with different radio, CODEX ok, WXJTW version 2.2.2, I get rig
> failure message, hamlib error IO error while testing VFO, cat test in
> settings stays red, it decodes whatever freq the radio is set to but
> says it's on 160M, stills start the radio when WSJTX starts up.

Hi Jon,

which radio? How is it connected to your PC for CAT control? What
settings do you have in "Settings->Radio"
com port 6, as the Port says, ?


73

Bill
G4WJS.




locked Re: new computer, CAT doesn't work right

Bill Somerville
 

On 03/11/2020 00:45, Jon Ermels via groups.io wrote:
 old computer worked on same radio, new computer, used it for WSJTX before with different radio, CODEX ok, WXJTW version 2.2.2, I get rig failure message, hamlib error IO error while testing VFO, cat test in settings stays red, it decodes whatever freq the radio is set to but says it's on 160M, stills start the radio when WSJTX starts up.
Hi Jon,

which radio? How is it connected to your PC for CAT control? What settings do you have in "Settings->Radio"?

73
Bill
G4WJS.


locked new computer, CAT doesn't work right

Jon Ermels
 

 old computer worked on same radio, new computer, used it for WSJTX before with different radio, CODEX ok, WXJTW version 2.2.2, I get rig failure message, hamlib error IO error while testing VFO, cat test in settings stays red, it decodes whatever freq the radio is set to but says it's on 160M, stills start the radio when WSJTX starts up.


locked lockups with RC1 version

Wayne Morris
 

I am having unexplained lockups of the program. This never happened before. It will simply stop decoding, I cannot change frequencies, etc. All I can do is close the program and restart it. After restart, it works fine again. I had about 6-8 occurrences yesterday. I tried to determine if there was any correlation between my activities and the lockup but was not able to associate any particular activity with the errors.

I have also noted a number of times that the program switches to receiving but the radio is still in transmit. This also never occurred on the previous version.

My system is Windows 10, HRD for CAT control and logging, JT Alert, and Yaesu FTdx101MP.
--
73, Wayne, AC5V


locked macOS Transmit Audio Problem

David Kaplan
 

I'm running macOS Catalina 10.15.7, and recently intentionally erased my iMac and added all the programs back manually (rather than a restore) to delete 6 years of crud (a technical term). Now I have WSJT-X 2.3.0 rc1 installed and am having an audio problem. The audio pref panels shows USB Audio Codec for transmit and receive, and receive populates the waterfall and decodes many stations.

My problem is that my IC-756Pro III keys, but does not transmit any audio. I checked and the power slider on the right side of WSJT-X is at its highest (for testing). I'm using a Timewave Navigator and checked that the controls haven't changed since I successfully transmitted before these changes, and I'm not hearing any audio from the Navigator.  I tried testing on WSJT-X 2.2.2 but had the same problem.

Any thoughts on where to investigate next?

Thanks & 73,

David, WA1OUI


locked V2.3.0-rc1 won't allow clicking on a station once transmitting.

Carl - WC4H
 

I tried to search for this but did not find it.  I hope I'm not repeating the issue.

On all previous versions of 2.x.x, if I clicked on a station by mistake or if I want to call someone other than "call 1st" auto selection, I could double click on another station and call them.

V2.3.0-rc1 is not letting me do that.  Once it starts transmitting I can only hault or let it finish the cycle.

This feature is very important, otherwise one can never change the Call 1st station selected by the program.  There are many times when 2 or 3 stations call at once and I want to change the Call 1st selection.

73.
Carl - WC4H


locked Re: Issues MACOS WSJTX

tommaso.guidi@...
 

OK ,

Thank you very much, it works, all works.

Bye IK5ZAK


Il 02/11/2020 21:40 Bill Somerville <g4wjs@...> ha scritto:


Hi Tommaso,

the link in the message thread below is to download a new sysctl.conf file. The one on the installer DMG is incorrect for WSJT-X v2.3.0 RC1.

The cp command is copying the new sysctl.conf file to the /etc/ directory and assuming you download the new file to your Downloads directory it will be like this:
sudo cp ~/Downloads/sysctl.conf /etc/
Then after you reboot you should be able to start WSJT-X v2.3.0 RC1.

73
Bill
G4WJS.

On 02/11/2020 20:30, tommaso.guidi via groups.io wrote:
I followed instuctions in "readme.txt" file, I putted sysctl.conf on the desktop, then in the terminal string sudo  cp  /Volumes/WSJT-X/sysctl.conf , unfortunately at the check with sysctl -a | grep sysv.shm the answer its like in the snapshot attachment. (no changement are applied)
It seems there is something wrong in the syntax.

Il 02/11/2020 20:59 Bill Somerville <g4wjs@...> ha scritto:

 
On 02/11/2020 12:37, tommaso.guidi via groups.io wrote:
--
Inviato da Libero Mail per Android

Hello,
I installed the software FT8 WSJTX for MACOS but when at start shows 
an error message about "shared memory". In attachment screenshots and 
system skills.
Thank you
Tommaso Guidi IK5ZAK

Hi Tommaso,

see the link at the bottom of this old message which contains a revised 
sysctl.conf file suitable for WSJT-X v2.3.0 RC1 running on macOS.

https://wsjtx.groups.io/g/main/message/16844

73
Bill
G4WJS.






locked Re: Issues MACOS WSJTX

Bill Somerville
 

Hi Tommaso,

the link in the message thread below is to download a new sysctl.conf file. The one on the installer DMG is incorrect for WSJT-X v2.3.0 RC1.

The cp command is copying the new sysctl.conf file to the /etc/ directory and assuming you download the new file to your Downloads directory it will be like this:
sudo cp ~/Downloads/sysctl.conf /etc/
Then after you reboot you should be able to start WSJT-X v2.3.0 RC1.

73
Bill
G4WJS.

On 02/11/2020 20:30, tommaso.guidi via groups.io wrote:
I followed instuctions in "readme.txt" file, I putted sysctl.conf on the desktop, then in the terminal string sudo  cp  /Volumes/WSJT-X/sysctl.conf , unfortunately at the check with sysctl -a | grep sysv.shm the answer its like in the snapshot attachment. (no changement are applied)
It seems there is something wrong in the syntax.

Il 02/11/2020 20:59 Bill Somerville <g4wjs@...> ha scritto:

 
On 02/11/2020 12:37, tommaso.guidi via groups.io wrote:
--
Inviato da Libero Mail per Android

Hello,
I installed the software FT8 WSJTX for MACOS but when at start shows 
an error message about "shared memory". In attachment screenshots and 
system skills.
Thank you
Tommaso Guidi IK5ZAK

Hi Tommaso,

see the link at the bottom of this old message which contains a revised 
sysctl.conf file suitable for WSJT-X v2.3.0 RC1 running on macOS.

https://wsjtx.groups.io/g/main/message/16844

73
Bill
G4WJS.



locked Re: Issues MACOS WSJTX

tommaso.guidi@...
 

I followed instuctions in "readme.txt" file, I putted sysctl.conf on the desktop, then in the terminal string sudo cp /Volumes/WSJT-X/sysctl.conf , unfortunately at the check with sysctl -a | grep sysv.shm the answer its like in the snapshot attachment. (no changement are applied)
It seems there is something wrong in the syntax.

Il 02/11/2020 20:59 Bill Somerville <g4wjs@...> ha scritto:


On 02/11/2020 12:37, tommaso.guidi via groups.io wrote:

--
Inviato da Libero Mail per Android

Hello,
I installed the software FT8 WSJTX for MACOS but when at start shows
an error message about "shared memory". In attachment screenshots and
system skills.
Thank you
Tommaso Guidi IK5ZAK
Hi Tommaso,

see the link at the bottom of this old message which contains a revised
sysctl.conf file suitable for WSJT-X v2.3.0 RC1 running on macOS.

https://wsjtx.groups.io/g/main/message/16844

73
Bill
G4WJS.



locked cannot access audio from sdr after w10 update (AGAIN)

diyer
 

after w10 updated I wstjx says it cannot access audio.  I've read lots of posts but can't sort them out.
Do I need to tell wstjx where to get the audio?  Like in this dialog box?


that talks about input to the sound card, but what I want is input to wstjx, how does wstjx know where to get input to wstjx?

I checked access audio w10 control panel and it seems to set ok, see below

I clicked the 

but nothing happens.




I know that I have fixed this problem before but I made so many changes before that I can't remember what actually solved the problem.  I think the problem is that wstjx does not know where to get its audio input.  I have not been using a virtual audio cable before nor did I have any patch cables bridging output to input somewhere.

Many other posts talk about a problem getting audio out to xmit.  I'm not trying to xmit yet.  burn that bridge later.
73


locked Re: Issues MACOS WSJTX

Bill Somerville
 

Hi Brian,

it is not a script. On macOS kernel parameters can be adjusted by rebooting with a sysctl.conf file in place, the parameters required adjust the amount of shared memory available to processes.

73
Bill
G4WJS.

On 02/11/2020 19:27, Brian Wilkins wrote:
I believe there is a script you need to run or can run the shmem commands yourself. This can also be added to your startup script for your user like a .bashrc 

On Mon, Nov 2, 2020 at 2:24 PM tommaso.guidi via groups.io <tommaso.guidi=libero.it@groups.io> wrote:

--
Inviato da Libero Mail per Android

Hello,
I installed the software FT8 WSJTX for MACOS but when at start shows an error message about "shared memory". In attachment screenshots and system skills.
Thank you
Tommaso Guidi IK5ZAK




--
Brian Wilkins
KO4AQF



locked Re: Issues MACOS WSJTX

Bill Somerville
 

On 02/11/2020 12:37, tommaso.guidi via groups.io wrote:

--
Inviato da Libero Mail per Android

Hello,
I installed the software FT8 WSJTX for MACOS but when at start shows an error message about "shared memory". In attachment screenshots and system skills.
Thank you
Tommaso Guidi IK5ZAK
Hi Tommaso,

see the link at the bottom of this old message which contains a revised sysctl.conf file suitable for WSJT-X v2.3.0 RC1 running on macOS.

https://wsjtx.groups.io/g/main/message/16844

73
Bill
G4WJS.


locked Re: Issues MACOS WSJTX

Brian Wilkins <bwilkins@...>
 

I believe there is a script you need to run or can run the shmem commands yourself. This can also be added to your startup script for your user like a .bashrc 

On Mon, Nov 2, 2020 at 2:24 PM tommaso.guidi via groups.io <tommaso.guidi=libero.it@groups.io> wrote:

--
Inviato da Libero Mail per Android

Hello,
I installed the software FT8 WSJTX for MACOS but when at start shows an error message about "shared memory". In attachment screenshots and system skills.
Thank you
Tommaso Guidi IK5ZAK




--
Brian Wilkins
KO4AQF


locked Issues MACOS WSJTX

tommaso.guidi@...
 

--
Inviato da Libero Mail per Android

Hello,
I installed the software FT8 WSJTX for MACOS but when at start shows an error message about "shared memory". In attachment screenshots and system skills.
Thank you
Tommaso Guidi IK5ZAK


locked Hamlib error

 

Rig is an Apache ANAN 100D (Protocol 1).  WSJT-X v2.2.2 and c2.3.0-RC1 both give me a Hamlib error: “Hamlib error: Protocol error while getting current VFO frequency.  I have also tried with both Thetis and PowerSDR latest versions.  This started right after a Win10 update.  It all worked fine before that.  I have searched the web, tried rigctl, without success.  As Microsoft does with audio, it may very well be an enumeration error but I’m at a loss as to how to fix it.

Before anyone asks: I have rebooted and reinstalled everything I can think of.

 

Is there any help available from this forum?

 

__________

Dan – K4SHQ

CFI/II

 


locked Re: sound device settings changed

Bob McGraw - K4TAX <rmcgraw@...>
 

Could be....... but if you have used any other application to play music or video, those applications may change the levels and may change the soundcard choice.   And they may not reset them once they are closed.  Some do, some don't.  I do a good bit of audio editing on my computer that is used for the digital modes.  I've found that if changes occur, I know exactly where to look, what the values should be, and thus able to resolve any issues with little concern.  

I do take Windows 10 Pro updates automatically and have not found any issues with the result of updates.    NOW .......one thing I do not do is leave the computer on when not using it.   A close friend who is a security analyst has advised that if the computer is left on, unattended, this is an invitation for hackers to implant viruses, malware, or look for other personal data on your computer.    It just depends on your level of system security, which he also says, most do not have adequate firewall protection.    He says it is like leaving your house unlocked when you are away. 

If you don't have a UPS or the battery in the UPS is weak, during a power outage, even a brief one, the computer will shut down.  And the shut down will not close programs or exit programs correctly.   As to what the applications might leave, or the condition they might leave things, is totally unpredictable.  A good quality UPS is always needed and it should be tested on a regular basis.  Say at least once a month.

My rules:   (a)  Don't leave the computer on when not being used.  (b) always close any application correctly when finished before shutting off the computer.  

73
Bob, K4TAX


locked Re: Windows Sound Device Names

Ron / W4MMP
 

Hi AL,

Yes, and that is what I have been doing for quite a while.   I name the audio adapter that MSCC accesses to MSCC and the audio adapter that digital applications access to DIGITAL.  The issue presented in this tread is that WSJT-X does not pick up the new name even after reboot but Bill provided a solution to this.  Also as he has mentioned,  the new beta version will not experience this problem since it will enumerate the audio devices every time the audio device list drop down is accessed. 

73,
Ron / W4MMP
On 11/2/2020 10:34, Al Groff via groups.io wrote:

Ron,
  windows can, and often, does rename sound devices when it does an update.  You can correct the naming ( until the next update ) by renaming the devices in the Manage Audio device ( sounds) window.  ( or even make the names something of your own choosing. )
 

Then reboot and you should be good until the next major update.  Don't forget to reboot ( restart ) after you make the change.

AL, K0VM



On 11/1/2020 9:53 AM, Ron / W4MMP via groups.io wrote:
Howdy,

After not operating WSJT-X for a while,  I found one of the Windows updates messed up the sound devices configuration.  The device configurations were fine but the updates messed with the device names. The device names were corrected.
I run an old school audio setup.   Two USB audio adapters wired back to back (adapter-1 speaker to adapter-2 microphone, and reverse for the other microphone and speaker).  Adapter-1 is named MSCC (for the SDR application I run).  Adapter-2 is named DIGITAL.   This adapter is accessed by digital applications (WSJT-X,  fldigi and such).  I do this simply for convenience and my sanity.   The issue is WSJT-X does not pick up the configured name of the device.  It was just a tad confusing because WSJT-X reports adapter-2 as MSCC which is not the name of the adapter.   I have performed all the normal stuff like rebooting the PC and stop/starting WSJT-X a number of times.   So, is this a Windows issue or WSJT-X issue?







locked Re: Windows Sound Device Names

Al Groff
 

Ron,
  windows can, and often, does rename sound devices when it does an update.  You can correct the naming ( until the next update ) by renaming the devices in the Manage Audio device ( sounds) window.  ( or even make the names something of your own choosing. )
 

Then reboot and you should be good until the next major update.  Don't forget to reboot ( restart ) after you make the change.

AL, K0VM



On 11/1/2020 9:53 AM, Ron / W4MMP via groups.io wrote:
Howdy,

After not operating WSJT-X for a while,  I found one of the Windows updates messed up the sound devices configuration.  The device configurations were fine but the updates messed with the device names. The device names were corrected.
I run an old school audio setup.   Two USB audio adapters wired back to back (adapter-1 speaker to adapter-2 microphone, and reverse for the other microphone and speaker).  Adapter-1 is named MSCC (for the SDR application I run).  Adapter-2 is named DIGITAL.   This adapter is accessed by digital applications (WSJT-X,  fldigi and such).  I do this simply for convenience and my sanity.   The issue is WSJT-X does not pick up the configured name of the device.  It was just a tad confusing because WSJT-X reports adapter-2 as MSCC which is not the name of the adapter.   I have performed all the normal stuff like rebooting the PC and stop/starting WSJT-X a number of times.   So, is this a Windows issue or WSJT-X issue?






locked Re: has auto gone weird?

chas cartmel
 

It was auto, which is why I was confused.
Cheers


73 Charlie

G4EST

www.g4est.me.uk

Stay safe out there

 

 

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Reino Talarmo
Sent: 02 November 2020 12:57
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] has auto gone weird?

 

Hi Charlie,

Based on the information in the snip SP5FCZ never sent you a report, but preferred to try that Japan station. I doubt that he logged your QSO.

I am surprised, which messages your station sent to him as you did not received a report from him. Did you used Tab1 or Tab2?

73, Reino OH3mA

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of chas cartmel
Sent: 2. marraskuuta 2020 14:00
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] has auto gone weird?

 

I should add I manually tried to resend message to SP5FCZ when I notices the software had switched stations.

73 Charlie

G4EST

www.g4est.me.uk

Stay safe out there

 

 

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of chas cartmel
Sent: 02 November 2020 11:42
To: WSJTX@groups.io
Subject: [WSJTX] has auto gone weird?

 

I must be doing something wrong. My system seems to have connected to 2 stations automatically and I have no idea if QSO with SP5FCZ actually completed.
Only Auto Seq ticked.



Please advise what I did wrong?

 

 

Best Regards
Charles Cartmel

BE CAREFUL

STAY SAFE

 

 

This email has been scanned by BullGuard antivirus protection.

For more info visit www.bullguard.com

 

This email has been scanned by BullGuard antivirus protection.

For more info visit www.bullguard.com


This email has been scanned by BullGuard antivirus protection.
For more info visit www.bullguard.com

18841 - 18860 of 36726