|
Locked
Re: WSJTX On Mac OS Catalina
Keith Kaiser
Bill,
toggle quoted message
Show quoted text
I ran it from Terminal and got this; Apparatus:~ keithkaiser$ /Applications/wsjtx.app/Contents/MacOS/wsjtx At line 1 of file /Users/bill/wsjtx-prefix/src/lib/gen65.f90 Fortran runtime error: Actual string length is shorter than the declared one for dummy argument 'msgsent' (-6148914694099828714/22) Segmentation fault: 11 I’m not at all sure what all that means. Keith, WA0̷TJT
|
|
|
|
Locked
Re: WSJTX On Mac OS Catalina
jamesforslund <coloradodui@...>
Thanks Nathan,
It was just a matter of getting the cursor properly placed and the password entered correctly entered into the non-expanding space. The memory is correct now, but now WSJT-X 2.10 is crashing before it opens. WSJT-X 2.01 is not. Jim-KE0OIR |
|
|
|
Locked
Re: WSJTX soundcard control
Jim Bacher - WB8VSU
Steve, I hit that issue anytime the computer goes to screen saver. I am still looking for what is being impacted by the screen saver. I have turned off power saving on all USB device, but still have not found the setting to clear the issue.
toggle quoted message
Show quoted text
If your on a desktop turn off power saving and manually turn off the monitor. Jim Bacher, WB8VSU wb8vsu@... https://trc.guru
|
|
|
|
Locked
Re: Not QSLing FT8 but operating...
Roger
On 01/11/2019 18:57, Sidney Frissell wrote:
Part of the “not sending 73” problem may be that the manual for WSJT-x says that when RR73 is Sent the QSO is over.thus some hams bail out when the get a RR 73 and don’t send the last 73.RR73 is fine. You can actually see some operators stop the Tx a few seconds into the 73. |
|
|
|
Locked
Re: WSJTX soundcard control
Switch to Linux :) On Fri, Nov 1, 2019 at 12:50 PM Steve Lund <k6um.elist@...> wrote:
Kingston, WA K7VE |
|
|
|
Locked
Re: WSJTX soundcard control
On 01/11/2019 19:49, Steve Lund wrote:
I've gone through various Windows10 settings & control panel setting all windows sounds to the Dell monitor speakers.Hi Steve, the correct way to ensure Windows, and other applications using the default audio playback device, sounds going to your rig is to make sure that the Windows Default playback device (the one with the green tick) is not the device connected to your rig. If you only have a single sound card then you must ensure that all Windows sounds are turned off and that no other applications that can generate sounds are running. MS Windows tends to automatically make an available sound card the default sound card if the current default sound card goes away. Using the HDMI audio on a monitor device as the default sound device can be problematic as the monitor going to sleep to save power may cause the associated audio device to go away. Note that WSJT-X does not control any audio device, that is the job of the operating system and drivers, it merely requests audio streams to or from some named audio devices. 73 Bill G4WJS. |
|
|
|
Locked
Re: WSJTX On Mac OS Catalina
On 01/11/2019 19:34, Keith Kaiser
wrote:
I have this in my sysctl.conf what is different with what you have? Because I can’t run WSJT-X in Catalina and would like to. kern.sysv.shmmax=14680064 kern.sysv.shmmin=1 kern.sysv.shmmni=128 kern.sysv.shmseg=32 kern.sysv.shmall=17920 Hi Keith, what error message are you getting? If you are not getting an error message or crash report then try running WSJT-X from a terminal like this: /Applications/wsjtx.app/Contents/MacOS/wsjtx and report back what happens. Reviewing this message from the WSJTGroup Yahoo Groups support group should help: https://groups.yahoo.com/neo/groups/wsjtgroup/conversations/messages/39675 73 |
|
|
|
Locked
WSJTX soundcard control
Steve Lund
Has anyone figured out how to keep the soundcard from getting taken over by Windows? I don't know how many times I've started calling a station and there is no TX output, RX works fine. Going to Settings->Audio and switching the Soundcard Output setting to another soundcard & back always works. But, I then miss a few TX cycles. I've gone through various Windows10 settings & control panel setting all windows sounds to the Dell monitor speakers. I've attempted to turn off all Windows sounds. But, every once in while I hear a windows sound coming through the K3 audio. When this happens, WSJTX no longer has control of the pc soundcard. Is there any hope of fixing this? Steve, K6UM I'm using Win10Pro-64. |
|
|
|
Locked
Re: WSJTX On Mac OS Catalina
Keith Kaiser
I have this in my sysctl.conf what is different with what you have? Because I can’t run WSJT-X in Catalina and would like to.
toggle quoted message
Show quoted text
kern.sysv.shmmax=14680064 kern.sysv.shmmin=1 kern.sysv.shmmni=128 kern.sysv.shmseg=32 kern.sysv.shmall=17920 On Nov 1, 2019, at 2:19 PM, Gary Rogers <cgaryrogers190@...> wrote: |
|
|
|
Locked
Re: WSJTX On Mac OS Catalina
Gary Rogers
Ok thanks
toggle quoted message
Show quoted text
Sent from my iPhone On Nov 1, 2019, at 12:05 PM, Nathan Broderick via Groups.Io <nathanbroderick@...> wrote: |
|
|
|
Locked
Re: Not QSLing FT8 but operating...
Jim Cooper
On 1 Nov 2019 at 12:57, Sidney Frissell wrote:
the manualWSJTX@groups.io forI think that is only specifically said for Fox/Hound ... when the FOX sends RR73 your QSO with the fox is logged in their log. w2jc |
|
|
|
Locked
Re: Not QSLing FT8 but operating...
Sid Frissell
Part of the “not sending 73” problem may be that the manual for WSJT-x says that when RR73 is Sent the QSO is over.thus some hams bail out when the get a RR 73 and don’t send the last 73.
toggle quoted message
Show quoted text
I always let the QSO run out the sequence and send a last 73.. Takes 30 seconds of your life to be polite! Sid, NZ7M Sent From Sid Frissell's iPad On Nov 1, 2019, at 9:46 AM, Charles Hein <chein@...> wrote:
|
|
|
|
Locked
Re: Not QSLing FT8 but operating...
Wilson A. Caselli <wcaselli@...>
I agree with you 100% Roger!
toggle quoted message
Show quoted text
Courtesy is contagious! Wilson A. Caselli WCaselli@... On Nov 1, 2019, at 1:09 PM, groups@... wrote: |
|
|
|
Locked
Re: Not QSLing FT8 but operating...
Robert D. Bowers
I've seen entries and posts about how FT8 was "Killing Amateur
Radio!". I remember hearing something like that when I was first
licensed... about how SSB ("Donald Duck") was killing Amateur Radio,
ditto for Computers, ditto for Packet, ditto for PSK31. The most
vocal people were the single-mode-only people, especially CW. For a
while (in the early 80s) I could copy CW, but as my health
progressed, it became more and more spotty. That put me in a
negative category with the complainers, who insisted I hadn't tried
hard enough. I've done some computer CW, but prefer other modes. I
happen to really like JT65 and its new version FT8.
toggle quoted message
Show quoted text
FT8 and JT65 are cutting-edge stuff, enabling people to work others when they couldn't even hear them (I've experienced that several times over the years) - signals so low that CW wouldn't get through. That's just one aspect of Amateur Radio - the development of new techniques and technologies - and experimentation. A friend and I have also noticed things on HF (using JT65) which aren't supposed to be possible - for instance, one day I worked a guy over a 400 miles distance with around a single milliwatt into a dipole at 55 ft - from a watt downward the signal report on both ends remained stable (-14 or so) - I think on 40m (have to see if I can find the log - may have lost it in a computer crash). That was back when Joe (a friend of mine) was working on JT65-HF. I'm not too thrilled with robotic stations, but do see where they could have their place (learning more about propagation, for instance). I figure "whatever floats your boat" - but don't like the attitude that was shown. I personally like homebrewing - and can't afford new gear anyway. Many times I've encountered the "if you can't afford new, you don't belong!" attitude. "Whatever floats your boat" should be a common attitude. Not contempt. Bob N4FBZ On 11/1/19 1:32 PM, Andrew OBrien
wrote:
I understand the varying opinions on the decisions to QSL or not QSL , just surprised someone who apparently has contempt for the mode would bother to be on the air with it. The idea that it might be a 'robot" station is intriguing however. |
|
|
|
Locked
Re: Not QSLing FT8 but operating...
Andrew OBrien
Wilson, I agree... that is what I do. I assumed this gentleman would not even upload his FT8 QSOs to ARRL. I'll have to look and see.
Andy K3UK |
|
|
|
Locked
Re: Not QSLing FT8 but operating...
Andrew OBrien
I understand the varying opinions on the decisions to QSL or not QSL , just surprised someone who apparently has contempt for the mode would bother to be on the air with it. The idea that it might be a 'robot" station is intriguing however.
Andy K3UK |
|
|
|
Locked
Re: Not QSLing FT8 but operating...
Robert D. Bowers
I've never been lucky enough to get through any pileup, much less
work a dxpedition. I gave up on that a LONG time ago, so I don't
know.
toggle quoted message
Show quoted text
On 11/1/19 1:07 PM, Jim Cooper wrote:
On 1 Nov 2019 at 12:44, "Robert D. Bowers" <n4fbz@...> wrote:From my memory, 73s (conclusion of exchange) was necessary to consider it completeddo you send 73 when you work a dxpedition in a pileup? if not, does it count? |
|
|
|
Locked
Re: Not QSLing FT8 but operating...
Roger
On 01/11/2019 17:07, Jim Cooper wrote:
On 1 Nov 2019 at 12:44, "Robert D. Bowers"Not in my book |
|
|
|
Locked
Re: Not QSLing FT8 but operating...
Roger
On 01/11/2019 16:44, Robert D. Bowers wrote:
From my memory, 73s (conclusion of exchange) was necessary to consider it completed from the introduction of JT65. I use WSJT-X and it's automatically generated. A reduced exchange was considered adequate in only certain cases - like moonbounce or meteor scatter.I don't care if 73 is a compulsory part of the QSO or not. I just regard a failure to transmit it as discourteous . Roger GW4HZA |
|
|
|
Locked
Re: Not QSLing FT8 but operating...
Jim Cooper
On 1 Nov 2019 at 12:44, "Robert D. Bowers"
<n4fbz@...> wrote: From my memory, 73s (conclusion ofdo you send 73 when you work a dxpedition in a pileup? if not, does it count? |
|
|