Hi Frank,
On 10/19/2018 9:47 AM, Frank Kirschner KF6E wrote:
One thing I haven't seen discussed on this reflector is improving the
S/N by narrowing the receiver bandwidth. It is no surprise that
decreasing the bandwidth received increases the S/N, by 10 to 15 dB,
sometimes more. When I see a
Thanks!
Hasan
On Fri, Oct 19, 2018 at 8:35 AM Bill Somerville
wrote:
> On 19/10/2018 14:26, Hasan al-Basri wrote:
>
> Bill,
>
> I downloaded and installed the 32 bit OpenSSL software this morning.
> (after I had downloaded and copied the the *.csv file yesterday as a short
> term fix)
> ...and
One thing I haven't seen discussed on this reflector is improving the S/N
by narrowing the receiver bandwidth. It is no surprise that decreasing the
bandwidth received increases the S/N, by 10 to 15 dB, sometimes more. When
I see a station I want calling at -24 or so, I can narrow the BW and get
When reducing the BW, the signal doesn't change, but the amount of noise
does, and that changes the S/N. In a system that didn't do optimum digital
filtering, reducing the BW to match that of the signal provides a S/N
improvement. In SSB, for example, increasing the BW to more than the signal
BW
Frank, seems indeed to work! Just tested during RX of station KG4HF with
bandwidth of either 3 kHz or 500 Hz. See the following S/N comparison.
Astonishing!
73 de Uwe, DG2YCB
Von: Frank Kirschner [mailto:frank.kirsch...@gmail.com]
Gesendet: Freitag, 19. Oktober 2018 15:48
An: WSJT
Yes, that makes sense. I should have realized that the narrow filtering had
to be done somewhere.
Frank
On Fri, Oct 19, 2018 at 11:19 AM George J. Molnar wrote:
> If I recall correctly, the S/N calculation is made in WSJT-X based on a
> fixed value somewhere around 2.8 kHz. Applying a wider or
Dear Frank,
I allow myself to answer instead of the development team, they will correct
later if i'am wrong.
Reducing the receiver bandwidth, in general case, will not help improve the
signal-to-noise ratio in WSJT-X. Or if it is the case it is because you output
a too strong BF signal and
Bill,
I downloaded and installed the 32 bit OpenSSL software this morning.
(after I had downloaded and copied the the *.csv file yesterday as a short
term fix)
...and the copy fix worked. So, I thought I would do the full fix.
After the install, I went to the colors tab where the Fetch button
A decrease of bandwidth by a factor of 6 will increase reported SNR by
approximately 16dB.But that's just a matter of what noise reference you
use...not any real change in the signal level.If you used signal peak instead
of RMS the SNR reported would be really lowit's all relative to the
If I recall correctly, the S/N calculation is made in WSJT-X based on a fixed
value somewhere around 2.8 kHz. Applying a wider or narrower bandwidth to the
decoder will provide numerically different values, but not affect decoding
performance UNLESS the narrowed bandwidth had an incidental
Only reason to narrow BW is reduce the voltage into the ADC if it is over
driven by broadband noise or an undesired signal. Attenuation may help but at
the loss of dynamic range.
DE N2LO~>
Sent from Xfinity Connect Application
-Original Message-
From: j...@princeton.edu
To:
So no one else on the Mojave is having audio issues? Going back to 1.9.1
worked fine.
The odd part is that Mojave asked to use the Microphone (which it never
did with RC2 or 1.9.1).
I had RC2 and installed RC3 and it asked to use the microphone. No joy.
So I found a copy of 1.9.1, renamed it,
...keeps crashing on launch. Installed it on the desktop and launched it from
the command line. Could be Mojave related...
> Am 19.10.2018 um 18:33 schrieb Hisashi T Fujinaka :
>
> So no one else on the Mojave is having audio issues? Going back to 1.9.1
> worked fine.
>
> The odd part is that
Hisashi,
When you started with Mojave, did you visit the Audio tab (WSJT-X >
Preferences) and select your preferred Audio stream - USB Audio Codec or
similar? What Audio link do you use between your rig (whicg rig?) and your
computer?
— John G4KLA
smime.p7s
Description: S/MIME
The exception, I assume, is with a strong local signal in the passband that
causes clipping or requires reduction in rf gain. I use the notch filter
for that OR get on the same tx phase with him.
Glen W6GJB
On Fri, Oct 19, 2018, 8:51 AM Frank Kirschner wrote:
> Yes, that makes sense. I should
HI John,
Hope all is well at your end.
I’ve just given WSJT-X_2.0.0-rc3 a try with my MacPro, OS 10.11.6 El Capitan
but I’m having trouble when the software tries to go into transmit
during a QSO. I get the following error,
Subprocess Error failed with exit code 2.
The details box shows
Georg,
> ..keeps crashing on launch.
It would help if you give me some error messages; which mode were you using?
Note that other users are running wsjtx on Mojave so I suspect that there is
something else problematic with your setup rather than the version of OSX.
— John G4KLA
smime.p7s
1.) I've noticed that JTAlert spots can now be clicked to start a
contact. I changed nothing in WSJTx since v1.9.1 to make it work with
previous RC's and just lived without the clickable spots until RC3.
2.) The larger UP and DN arrows are a great enhancement. Better target
for mouse clicks.
Hello,
I have been using wsjt-x 2.0.0 rc2 and cqrlog 2.3.0-1 together for FT8
successfully since the wsjt-x 2.0.0 rc2 came out. I recently upgraded
to wsjt-x 2.0.0 rc3 and still using it with cqrlog 2.3.0-1 am seeing
wsjt-x crash with the following error message:
Running: /usr/bin/jt9 -s
I'm running RC#3 and I'm seeing this for the first time. Not sure if it is
unique to Ver 3.0 or just something 've newer ran across in earlier
versions
230415 -18 -2.2 2962 ~ W7QQF/IMAGE
73
Jim Parks NY0J
---
This email has been checked for viruses by Avast antivirus software.
This is people using JT65HF Image Controller. Google “easypal” - not my cup of
tea and I think it’s silly but different strokes...
> On Oct 19, 2018, at 7:08 PM, wrote:
>
> I’m running RC#3 and I’m seeing this for the first time. Not sure if it is
> unique to Ver 3.0 or just something ‘ve
Jim,
That has nothing to do with RC3. It is from someone sending a link for image
exchange in a manner similar to EasyPal in the latter days (Hybrid). They are
simply sending a server link for a picture which will be opened in everyone's
software just as in EasyPal. There are two or more
I am new to this list and would like to suggest the use of ”+” rather than ”L”
to be consistent with the AR-Cluster spots that add a + to the right to show
the call is a LoTW user.
Richard AA5VU
___
wsjt-devel mailing list
Hi John
This is a known problem. There was some message traffic about this here a
day or two ago.
Bill's solution (as a temporary workaround) is to double click 'TX1 now'
button which disables it and forces you to send from TX2. There is a tool
tip associated with this button.
73
Charlie
>
Thanks Bill and Charlie,
I persisted with an exchange with OE100KFV and eventually got through the QSO
with manual intervention.
Just seen your emails - I missed the traffic earlier about this. I’ll check
whether my manual intervention iswhat you suggested.
Bill, ft8code -t crashes. I
This morning in response to an (unusual?) call sign: E770D (zero D)
registered in QRZ.COM
Snippet from ALL.TXT.Using 77 bit FT8
084130 5 0.1 471 ~ CQ E770D
084200 0 0.1 472 ~ CQ E770D
181019_084215 Transmitting
On 19/10/2018 11:19, John wrote:
This morning in response to an (unusual?) call sign: E770D (zero D)
registered in QRZ.COM
Snippet from ALL.TXT.Using 77 bit FT8
084130 5 0.1 471 ~ CQ E770D
084200 0 0.1 472 ~ CQ E770D
181019_084215 Transmitting 14.078 MHz FT8: E770D G4KLA I
27 matches
Mail list logo
