On 12/01/2021 15:37, Williams, G (af8c) via groups.io wrote:

Hello,
Comments from the peanut gallery.  Even if it's just an FYI. See https://discussions.apple.com/thread/135487

--73, Glenn, AF8C

Glenn,

you appear to have replied to the wrong conversation topic.

That link says nothing about why a /etc/sysctl.conf file does not work on macOS 11 (Big Sur) running on M1 hardware. Note that it works just fine on Big Sur running on Intel hardware and has worked on versions of macOS for a long long time.

73
Bill
G4WJS.

Hello,
Comments from the peanut gallery.  Even if it's just an FYI.   See  https://discussions.apple.com/thread/135487

--73, Glenn, AF8C

Here it is.

On Tue, Jan 12, 2021 at 10:20 AM Bill Somerville <g4wjs@...> wrote:

Hi Jim,

can you send me your ~/Library/Preferences/WSJT-X.ini file please?

73
Bill
G4WJS.

On 12/01/2021 14:59, James Quick wrote:

I can run 2.3.0-rc2 good with no trouble.

Jim Quick / N4ULE
jimn4ule@...

On Jan 12, 2021, at 9:55 AM, Bill Somerville <g4wjs@...> wrote:

On 12/01/2021 14:51, James Quick wrote:

Installed WSJT-X 2.3.0-rc3 on my Mac running Big Sur and it starts but then I get this error. Here is a screenshot of the error I get. Any help or advice will be a big help.

73

<Screen Shot 2021-01-11 at 11.37.12 AM.png>

Jim Quick / N4ULE

Hi Jim,

is there any sign of a system crash report?

73
Bill
G4WJS.

On Tue, Jan 12, 2021 at 09:24 AM, Austin 2E0MNV wrote:

Just because I have sent RR73 does not mean he has received it.   There have been occasions when the operator has refused to log me because he did not get my RR73.

The issue is, WSJTX stops transmitting immediately after RR73.  You have to click in two separate places on the screen after RR73 is sent, in anticipation that you may need to send it again because the last one went into outer space.  You do not know he got your RR73 until he sends 73 back.  If you set the option to continue transmitting after RR73, it transmits the unwanted CQ, which is unhelpful.

It happened to me 3 times yesterday and all the operators failed to log me even though we exchanged signal reports.  I suspect it was because they did not receive my RR73 for whatever reason.  They expect RR73 or they do not log.

I know there is an RRR option.  However, in this scenario, I transmit RRR, he receives it and sends RR73.  But then I have to send 73, and if he does not get this last 73, he will not log the contact.  There is no option in WSJTX to send 73 more than once.  There is only option to send a CQ after 73 which is a useless option unless you are the calling station.  

Austin:

As far as you're concerned a QSO is complete when you've sent either your RRR or RR73 so you can (and should) log the QSO as soon as that stage in the sequence has been reached.  It's not necessary for you to wait until you've received a 73 from the other station before logging the QSO - their final 73 is simply a courtesy.

I acknowledge that it can be helpful to receive a 73 because it does confirm that your RRR or RR73 has been received by the other station but it's not an essential part of the QSO.  Also, if you feel that the other station might not have received your RR73 or RRR because of QSB, QRM or whatever then there's nothing to stop you, as the operator of your station, sending your RR73 or RRR again even if doing so necessitates a couple of extra mouse-clicks - after all, you're supposed to be in control of what gets transmitted.

I don't see any need whatosever in having the software automatically send multiple RRRs or RR73s (or even 73s) - it's all under your control, and in any event there's no certainty that multiple re-sends of RRR or RR73 would get through any better than the first one if the station at the other end is suffering from QRM or if signals had faded significantly.

From the other side, if you're in a QSO and you've sent your R-xx report but for whatever reason (QSB, QRM etc) you haven't copied an RRR or RR73 from the other station then I acknowledge that you don't know that your report has been received; in this situation you, as the operator, can either initiate re-sending your report maybe a couple more times and hope that you eventually receive the RRR or RR73 that confirms that your report has been received, and/or you can log the QSO anyway with a comment to the effect that from your perspective the QSO was only partially complete because you hadn't received the other station's RRR or RR73 because of QRM or whatever.  By doing that you will at least have a record in your log of the exchange of reports and you can at a later date if necessary use that, along with the relevant extracts from your ALL.TXT file, to provide evidence that the essential information was exchanged and hence the QSO was valid.

--
Martin G0HDB

I can run 2.3.0-rc2 good with no trouble.

Jim Quick / N4ULE
jimn4ule@...

None!

Jim Quick / N4ULE
jimn4ule@...

Installed WSJT-X 2.3.0-rc3 on my Mac running Big Sur and it starts but then I get this error. Here is a screenshot of the error I get. Any help or advice will be a big help.

73

Jim Quick / N4ULE

Hi Jim,

is there any sign of a system crash report?

73
Bill
G4WJS.

Installed WSJT-X 2.3.0-rc3 on my Mac running Big Sur and it starts but then I get this error. Here is a screenshot of the error I get. Any help or advice will be a big help.

73

Hi Bill
I spent a couple of hours yesterday trying to create the LaunchDaemon.  It was quite difficult to follow all the steps I found in a YouTube video.  Anyway I did complete
the file but it didn't work for me.  Obviously my next to nil knowledge of Apple coding is the issue not the instructions.!

I did see a note in a posting on theis WSJTX group  about making sure that file sysctl.conf is on your computer.  i search on my iMac but can't find that file.  I have a 2017 iMac Ver 11.1 MacOS Big Sur
The note about sysctl.conf referenced a README note about how to install it.  I looked in all the folders associated with the WSJT-X but cannot find the notes about sysctl.conf

Can you direct me to it.

73 Frank VO1HP

Hi Frank,

the sysctl.conf file is right next to the ReadMe.txt file on the WSJT-X installer DMG, but as said before it does not work on macOS running on M1 hardware for some unknown reason. As explained in the latest ReadMe.txt file shipped with the WSJT-X v2.3.0 RC3 beta release, the relevant sysctl commands have to be run manually to adjust the kernel shared memory configuration for the current system session.

73
Bill
G4WJS.

The readme file is not copied to the user's system when wsjtx is installed.  readme can be found inside the wsjtx .dmg install package which you download.
Hope this helps.
Austin
2E0MNV

Hi Bill
I spent a couple of hours yesterday trying to create the LaunchDaemon.  It was quite difficult to follow all the steps I found in a YouTube video.  Anyway I did complete
the file but it didn't work for me.  Obviously my next to nil knowledge of Apple coding is the issue not the instructions.!

I did see a note in a posting on theis WSJTX group  about making sure that file sysctl.conf is on your computer.  i search on my iMac but can't find that file.  I have a 2017 iMac Ver 11.1 MacOS Big Sur
The note about sysctl.conf referenced a README note about how to install it.  I looked in all the folders associated with the WSJT-X but cannot find the notes about sysctl.conf

Can you direct me to it.

73 Frank VO1HP

Hello,

I use DV9/VE7HQT as my call since my QTH is in the Philippines.

When I answer a CQ of another ham with a non-standard DX prefixed call sign, we were both stuck in a never ending loop since we both could not send the dB signal strengths.

For those who use non-standard call sign, how do you complete your QSOs with another ham who also has a non-standard call sign? I've read the developer's note regarding non-standard calls, but it doesn't offer any advice on this issue.

73,
Sherwin

This is very easily fixed by the user .. just press the DOWN arrow next to your Tx frequency to reset the Rx frequency to what you're using.  

Neil, KN3ILZ

WSJT-X 2.3.0-rc3

The wsprd command will fail if no -a parameter specified, should use "." as default path.

>wsprd
Error: inaccessible data directory: '(null)'
Usage: wsprd [options...] infile
       infile must have suffix .wav or .c2

Options:
       -a <path> path to writeable data files, default="."

according change logs of WSJT-X 2.3.0-rc3:

• wsprd: Fails gracefully if data directory does not exist.

I think that might be a bug while apply this feature to wsprd?

Hi Michael.

thanks for the issue report, this is fixed for the next release and the default -a path will be honoured.

73
Bill
G4WJS.

Bill,
I guess I did not explain this well enough. In simple terms, when ever I send a CQ then WSJT-X makes sure that RX is lined up with TX and NOT back somewhere else from the previous QSO/
Charlie
W4EBB

Thank you
I am using a Mac so JT Alert is not available.  I was considering JT Bridge, but not sure if it's quite the same thing.
I periodically check all the bands for FT4, but 30m stands out as being particularly quiet.

In a way it is good that the FT4 sub bands are quieter because it makes it easier for smaller stations to work DX.

Hi Austin,

if you have JTAlert running you can see how many station are on each mode in each bands, which helps when chasing QSO's as you are not wasting time hunting on dead bands

the figures are world wide, so i tend to find anything with less than 100-120 stations are pretty dead, 400 - 700 stations is good, 700+ is crowded and you will be lucky to get many contacts

the "callsign per band" window drops down if you hover over the band area ringed in red, key to column colours at bottom blue=ft8, yellow=ft4 etc

its a really useful feature

Peter

2E0PWX

I never seem to hear any FT4 on 30m?  Do I have the correct frequency?  10.140MHz?
I listen every day and I'm not hearing any FT4 on the 30m band.  Is it not a thing?

Austin 2E0MNV

---

This email has been scanned by iomartcloud.
http://www.iomartcloud.com

---