Team,
After only one night with FST4-60 on 160, it's obvious that if we want
to maintain full IF bandwidth, 1837.5 or 1838 would be a far better
choice, using offsets in the range of 2,000 - 2,500 or 1,500 - 2,000 Hz
respectively. Either puts TX between 1839.5 and 1840. The reason is
simple
Hi Bill,
Please refer to the Quick-Start Guide to Q65:
"Recommended submodes: ...
• Ionospheric scatter on 50 MHz: 30A
• QRP ionospheric scatter on 50 MHz: 120E
• Ionospheric scatter on 144 MHz: 60C
• Troposcatter and rainscatter at 10 GHz: 60D
• Small-dish EME, 10 and 24 GHz: 120E
• Other EME:
I was using WSJT-X 2.2.2 on my Windows 7 box but earlier today I got
notice of release 2.3.0 and installed it. When I did the new version has
no clue about my USB sound card dongle that I was using successfully
with 2.2.2. It shows the Audio input device is just a (blank) green
line or it
Just made a contact with W4TAA, a local, using 30 second T/R sequencing.
What is the recommended T/R sequence timing for Q65 on 6M terrestrial
ionoscatter?
Thanks;
Bill W2PKY
On Wed, Feb 3, 2021 at 5:00 PM Reino Talarmo
wrote:
> Hi Mike,
>
> Please don’t mix AM at all with e.g. Q65 that are
Hi Bill,
Sorry to bother you, what are the mode id character in the UDP message for for
FST4 and SFT4/W ?
73,
Sam W2JDB
-Original Message-
From: Bill Somerville
To: wsjt-devel@lists.sourceforge.net
Sent: Wed, Feb 3, 2021 3:18 pm
Subject: Re: [wsjt-devel] 2.4.0-rc1 Defect - UDP Decode
Hi Mike,
Please don’t mix AM at all with e.g. Q65 that are using frequency-shift keying
and don’t have any amplitude modulation. In most rigs the 25 W versus 100 W is
due to keep amplitude modulation in PA linear range. As such it is not due to
possible high temperature rise.
Your 25 W rule
I will add that many operators aren't aware that their rig can't do full power
on all modes.
Many rigs rated at 100W can only do 25W in AM mode (100% duty cycle) -- the
manuals do show this.
For those rigs I always recommend to the ops to run FT8 at 50W max to avoid
pushing the temperature on
Hi Bill,
for N. America at least 50.275 for terrestrial ionoscatter, and 50.211
for EME have been proposed. In EU testing activity has been lower,
50.305 has been suggested as a possible frequency for terrestrial
operation in the EU over long distances. Nothing is set in stone at this
stage.
Hi:
My bad did reset at frequencies, freqs are 50.275, 50,211.
73'
Edfel
KP4AJ
On Wed, Feb 3, 2021 at 4:16 PM Bill Barrett
wrote:
> Is 50.318 the recommended 6M frequency?
> Could not see the 6M frequency documented, did I miss it?
> Thanks;
> Bill W2PKY
>
> On Wed, Feb 3, 2021 at 4:07 PM
On 03/02/2021 21:02, Edfel Rivera wrote:
Hi:
Please see attachment. Seems to be decoding or the functionality is
correct. Also, what TX power could be used? As TX intervals increase,
Could that cause damage to rig terminals? Thinking of JT65 where TX
power < ~30watts.
BTW, Thank you very
Is 50.318 the recommended 6M frequency?
Could not see the 6M frequency documented, did I miss it?
Thanks;
Bill W2PKY
On Wed, Feb 3, 2021 at 4:07 PM Edfel Rivera wrote:
> Hi:
> Please see attachment. Seems to be decoding or the functionality is
> correct. Also, what TX power could be used? As
Hi:
Please see attachment. Seems to be decoding or the functionality is
correct. Also, what TX power could be used? As TX intervals increase,
Could that cause damage to rig terminals? Thinking of JT65 where TX power
< ~30watts.
BTW, Thank you very much for INNOVATION. Seems like another
On 03/02/2021 20:14, Laurie, VK3AMA wrote:
FYI,
I note in 2.4.0-rc1 the mode identification character in the UDP
Decode message (#2) for Q65 is set to ":", this is currently assigned
to identifying QRA64 decodes.
de Laurie VK3AMA
Hi Laurie,
Q65 supersedes QRA64, QRA64 has been removed
FYI,
I note in 2.4.0-rc1 the mode identification character in the UDP Decode
message (#2) for Q65 is set to ":", this is currently assigned to
identifying QRA64 decodes.
de Laurie VK3AMA
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
Bill,
Another report I received from a K6:
> It fails in FT8 and the new Q65.
> Or even when trying to set preferences.
— John G4KLA
smime.p7s
Description: S/MIME cryptographic signature
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
Hi all,
there is an issue with the macOS version of the above release candidate.
It will crash if started from an icon or the open command. As a
temporary workaround you can start WSJT-X from a terminal with the
following command (adjust for your install location if not /Applications):
Thanks.
Jim
On 2/3/2021 4:54 AM, Steven Franke via wsjt-devel wrote:
Next thought. I called CQ for quite a while set for FST4-60. No responses, but
a guy near Phoenix (I'm near SF) posted me to PSKReporter, probably unattended.
My question is with respect to decoding, if I set up for
Bill,
> which mode
FT8
— John G4KLA
smime.p7s
Description: S/MIME cryptographic signature
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
No, it exits without a crash report.
Sorry for the bad news!
> On Feb 3, 2021, at 2:00 PM, Bill Somerville wrote:
>
> On 03/02/2021 17:45, George J Molnar wrote:
>>
>>
>> Under macOS BigSur (11.2), ver 2.4rc1 loads normally, but closes without
>> error message within a minute. If “monitor”
the same on MAC-OS High Sierra:service exits after the first transmission...
73 de DL8RBL
Am Mi., 3. Feb. 2021 um 20:21 Uhr schrieb Bill Somerville <
g4...@classdesign.com>:
> On 03/02/2021 19:06, John Nelson via wsjt-devel wrote:
> > Bill,
> >
> > 2.4.0-rc1 exits soon after 1st decode consolde
On 03/02/2021 19:06, John Nelson via wsjt-devel wrote:
Bill,
2.4.0-rc1 exits soon after 1st decode consolde log: service exited with
abnormal code 2
But no crash report is generated.
—John G4KLA
Hi John,
which mode?
73
Bill
G4WJS.
___
Bill,
2.4.0-rc1 exits soon after 1st decode consolde log: service exited with
abnormal code 2
But no crash report is generated.
—John G4KLA
smime.p7s
Description: S/MIME cryptographic signature
___
wsjt-devel mailing list
On 03/02/2021 17:45, George J Molnar wrote:
Under macOS BigSur (11.2), ver 2.4rc1 loads normally, but closes
without error message within a minute. If “monitor” is de-selected,
the app does not crash. Behavior same across modes.
*George J Molnar, KF2T*
Hi George,
is there a crash
I have 2.4.0 rc1 64 bit running. The first think I notice is that the
TX output level is approximately 7-8 db greater than v2.3.0.. OK by me
but Intentional ??
AL, K0VM
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
Under macOS BigSur (11.2), ver 2.4rc1 loads normally, but closes without error
message within a minute. If “monitor” is de-selected, the app does not crash.
Behavior same across modes.
George J Molnar, KF2T
(202) 288-8000
FM19ma - Maryland, USA
Would 1838 not be a better choice, there's not much JT65 or JT9 these days
and FST4 replaces them.
Jim Brown wrote:
> Makes sense. More questions, which came up first time I tried to use FST4
> on 160M, set up at 1839 kHz dial, 1050 Hz offset (I have a trash intermod
> carrier at 1840). If I
We are pleased to announce availability of a release candidate for
WSJT-X 2.4.0, introducing a new digital mode called Q65. Timing of this
release is unusual as it follows so closely the General Availability
(GA) release of WSJT-X 2.3.0. This timing anomaly occurs because
development of new
Hi Joe and Bill
Replaced WSJTX Japanese help (HTML version) with 2.3.0 GA.
There is no change in the URL.
Many Thanks.
--
de JH8XVH Yoshi
--
このEメールはアバスト アンチウイルスによりウイルススキャンされています。
https://www.avast.com/antivirus
___
wsjt-devel mailing list
>
> Next thought. I called CQ for quite a while set for FST4-60. No responses,
> but a guy near Phoenix (I'm near SF) posted me to PSKReporter, probably
> unattended. My question is with respect to decoding, if I set up for FST4-60,
> would I also decode shorter period FST (and vice versa)?
On 2/2/2021 3:48 PM, Steven Franke via wsjt-devel wrote:
Increasing or decreasing the width of the search window will increase/decrease
the number of spurious candidates, so a larger search window means longer total
decoding time and higher false decode rate. That’s why we advise users to
30 matches
Mail list logo
