Hi Allan
I see exactly the same as you with RS232 PTT.
I hadn't monitored the state of the Test PTT button. As you observe, if
this turns red during a receive period then the following transmission has
no audio. If the button does not turn red during a receive period the
following transmission
WSJT-X 220-rc2 - WSPRnet manual upload issue:
I am using wsjtx-2.2.0-rc2-win64.exe, WINDOW 10
WSPRnet is accept manualy upload of WSPR LOG, ALL_WSPR.TXT here.
http://wsprnet.org/olddb
But, 2.2.0-rc2's ALL_WSPR.TXT is not allow.
The reason is probably deleted the S level from ALL_WSPR.TXT.
When I
Gentlemen,
To start with, my system is a Dell 1650, i7 @3.40 GHz, 16GB RAM, W10 pro
64bit. I do not use CAT but instead use RTS on COM1 for opto-isolated
PTT and XFR isolation for audio in and out of the sound-card, and have
done so without issue since 2006.
Two problems : -
1. I have f
Hi all!
Excellent idea!
I wish those who call endless CQ on wrong period on 50 MHz would use it.
Maybe: similar approach as TX1/TX2 or RRR/RR73 selection. (double click on Next
near TX6)
TX6 may be marked as:
CQ S52D JN76 (1)
CQ S52D JN76 (2)
indicating number of periods between two CQs.
Press
On Mon, May 25, 2020 at 3:33 PM Rik Strobbe wrote:
>
> For now I do the manually (via the enable TX button), but if others find
> this useful as well it might be considered to add it as an option in WSJT-X?
>
In my opinion, this should be the default, for FT8 and FT4.
73, Paul K6PO
___
Bill and Joe,
As a summary for readers I have identified that MANY false decodes being
observed were observed ESPECIALLY using the “flipping” of the bits that results
in a /R. Subsequently there has also been a bit of chatter re field days etc.
and the use of non-standard suffixes even in the f
Hi Bruce,
On 5/25/2020 5:44 PM, Bruce H. Bern K3NQ wrote:
Program version: (beta) WSJT-X 2.2.0-rc3; My system: Win 10 Pro X64; Intel
Core i7-3930K; CPU@3.2 GHz; RAM=24Gb; Radio Kenwood TS-990, Baud rate:
115,200; data bits, stop bits, handshake all default
Precis of problem: If a transmit freq
Hello,
on a quiet band I find it useful to call CQ every second round (once a minute
in FT8).
That allows me to monitor both even and odd periods inbetween the CQ's and as
the duty cycle is only 25% I can CQ for a long period without overheating the
TX.
For now I do the manually (via the enable
I also observed split issues with the identical setup on my IC-7300, only
with Windows 10.
After installing rc2, in FT-8 mode the rig was receiving on 7.074 when set
for 40M, but was transmitting on 14.074 on 20M on split! Apparently,
whatever was previously in VFO B was retained.
73
Artie KD0GY
Hello,
I am observing some split operation issues with WSJT-X 2.2.0-rc2 on macOS and
IC-7300.
My Setup:
Computer: macOS Catalina 12.15.4
Rig: Icom IC-7300
WSJT-X 2.2.0-rc2
WSJT-X Radio Tab:
Rig: Icom IC-7300
Serial Port: /dev/cu.SLAB_USBtoUART
Baud Rate: 115200
Data Bits: Eight
Stop Bits: One
H
We declared that a completed QSO had a 599 signal report... Since the 59 or
599 is given automatically by most contest logging programs, this is not a
real deciding element of the exchange. With the successful exchange of the
location data either there or absent, this is actually a better signal
re
Hi Bruce,
On 5/25/2020 2:53 PM, Bruce H. Bern K3NQ wrote:
Using latest Win-10, if attempting to place the transmit frequency below
200 Hz, the display crashes
I can't reproduce the effect you describe.
If it's reproducible for you, please follow instructions for bug reports
here in the User
Using latest Win-10, if attempting to place the transmit frequency below 200
Hz, the display crashes
Thanks,
Bruce K3NQ
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Dave
A few of us have seen the same problem with this type of PTT control with
rc2. Devel team are aware.
73
Charlie G3WDG
On Mon, 25 May 2020 at 17:43, David Tiller wrote:
> FYI team, I also reported an issue with PTT with RC1 that does not seem to
> be solved in RC2. I believe the issue wa
Hi Jim,
Of course it would be trivial to enable display of characters G and H as
"pseudo-classes" in the ARRL Field Day message formats used for MSK144,
FT4, and FT8. But I don't see this as a very desirable message format
for state QSO parties. A few problems, for example:
- Operators wo
Hi,
There are 8 characters available for the Field Day contest overlay to
designate class of operation. Currently A-F are used, and if G and H are
activated it will allow for 256 combinations of the transmitter number
(1-32) and the letters. Right now only 192 combinations are available.
Why th
Hi Georg,
as you say "Preferences" I assume you are using macOS. What o/s version
are you using please?
73
Bill
G4WJS.
On 25/05/2020 17:38, Georg Isenbürger wrote:
Joe et al,
while using „Configurations“ I was not able to get back into „Preferences“
anymore. Showed a menue similar to „Conf
Joe et al,
while using „Configurations“ I was not able to get back into „Preferences“
anymore. Showed a menue similar to „Configurations“.
73’s Georg
> Am 25.05.2020 um 18:17 schrieb Joe Taylor :
>
> Hi Jim,
>
> On 5/25/2020 3:04 AM, Jim Brown K9YC wrote:
>> Thanks VERY much for this one:
>>
FYI team, I also reported an issue with PTT with RC1 that does not seem to be
solved in RC2. I believe the issue was the initialization of the cat state for
rigs that cannot be queried.
The command I was previously asked to run returns '0' each time, so it seems to
be something else.
dtiller$
Hi Jim,
On 5/25/2020 3:04 AM, Jim Brown K9YC wrote:
Thanks VERY much for this one:
"Hold Tx frequency no longer cleared when switching between modes."
We're halfway there -- TX frequency defaults to 1500 Hz when I've
returned from MSK144 to FT8. Is it possible to remember prior setting of
TX
FWIW, I'm getting the same error in another computer with another rig (
IC-703 ) as well.
Here's the trace:
~/ham/hamlib/hamlib-prefix_20200525/bin$ ./rigctld -m 3055 -r
/dev/ttyUSB0 -s 19200 -P RTS -v
main: #1 vfo_mode=0
Recommend using --vfo switch for rigctld if client supports it
rigc
Hi Grant,
Thanks for sharing your concerns about band plans. Of course we are
aware that almost any newly suggested frequency may step on some toes.
As stated in the Release Notes, our currently selected trial frequencies
follow guidelines being considered by IARU, ARRL, and other amateur
ra
Gentlemen.
Let me begin by thanking the team for all the enjoyment you've brought into the
amateur radio hobby.
I'm currently running WSJT-X v2.1.2 and keying my sequencer with an
opto-coupled transistor connected
to PTT com1 RTS. I'm using a Windows 7 pro operating system and a flex 5000
radi
Hi Ryan,
thanks for that clarification. I'm not sure why your system has so many
languages enabled. The issue is a WSJT-X defect anyway, it is trying to
do something clever to make life easier for potential translators and
the code isn't quite right. It will be sorted out for the next release.
t_vfo None failed with 'Invalid parameter'
Hamlib: icom_get_freq: set_vfo failed? retval=Invalid parameter
Hamlib: icom_get_freq: unknown VFO? VFO=None
I also compiled the latest (20200525) Git snapshot of hamlib, but it gives the
same
error, trace below:
karza@carole:~/ham/hamlib/hamlib
Hi Bill,
Yes. Although I haven't specifically installed any additional languages, I see
33 languages listed in System Preferences -> Language and Region including
Catalan. English is the only one selected as primary. It's possible these
were installed by the Xcode installer -- that is the on
Hi Uwe,
RRR, understood. I just wanted to show that as a general concept hiding
decodes may not be a good strategy unless there was some underlying
information to base that on. For example we could choose to hide low
confidence decodes altogether but that would be a regression in
functionalit
Joe,
The choice of 20m extension frequency is going to bring FT8 into direct
conflict with many many PSK and Olivia operators. The choice of 14.071 is
about the worst choice that could have been made.
I know there are a few who still like JT65 on 20m - but the number of users
many evenings on PSK
Hi Bill,
Agreed. Just one clarification: I didn’t want to let all /R decoded be
discarded unless in a special operation activity mode, ONLY THE AP DECODES OF
/R CALLSIGNS, so that true /R callsigns are still displayed when in normal FT8
mode. The idea is to filter out some more false decodes
Hi Michael,
On 25.5.2020 15.18, Black Michael via wsjt-devel wrote:
Does it work when WSJT-X is connected to the rig instead?
Yes, direct connection works fine.
'Kari
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.source
Bill,
You are completely preaching to the informed here with knowledge of what, how,
why and even some of the maths involved ☺ But thanks again.
The issue is that the software picks one of these out and then you respond,
then abort or manually over-ride to the Tx6.
There is a clear pattern tha
Hi Uwe,
that is a possible option but we must be careful. For example a user
being deprived of sight of messages that happened to contain '/R'
suffixes may misunderstand that they should be enabling the relevant
contest mode. Also the same argument would apply to '/P' suffixes, would
you be h
Bill,
Just an idea: Wouldn't it make sense to discard all the /R ?a2 decodes
unless a special operation mode is set?. My observation also with the prior
WSJT-X versions was, that if there are false decodes, most often they are /R
decodes. Couldn't that significantly reduce rate of false decodes wit
Hi Steve,
Have you analyzed how many of the low level decodes, say below -18 dB, are
false positives compared to all decodes? That figure will be a nice
educational information. It requires some manual treatment of ALL.TXT file,
but most of the work can be automated.
73, Reino OH3mA
-Original
Steve,
please don't equate AP assisted decodes with low levels (I prefer the
term weak signals). AP decoding techniques, like the other FEC
mechanisms, allow missing information to be recovered. Weak signals are
not the only cause of missing information, truncated or otherwise
interrupted sig
Bill,
Fully aware of that :-) Yet you have asked for reports when these occur. I am
in a far-away land to many where low-level, low confidence signals are the norm
and not the exception. Around 40% of the 40 contacts made today with the new
version have been > -18dB. Without the reduced confide
On 25/05/2020 12:04, Stephen VK3SIR wrote:
Folks,
I just picked up a false decode that can be replicated when played back
through WSJT-X 2.2.0 rc2:
104945 -23 -0.5 1623 ~ VK3VM FH9ZZV/R ND49 ? a2
Research suggests this is not a genuine call and is definitely a false decode
Folks,
I just picked up a false decode that can be replicated when played back
through WSJT-X 2.2.0 rc2:
104945 -23 -0.5 1623 ~ VK3VM FH9ZZV/R ND49 ? a2
Research suggests this is not a genuine call and is definitely a false decode
(i.e. ND49 = middle of Southern Ocean). I hav
On 25/05/2020 04:07, Ryan Woolley wrote:
After installing rc2 over rc1 on 10.15.4, the language defaults to
Catalan. Launching from Terminal with -l en or -l en-us has no
effect, and System Preferences -> Language and Region -> Apps -> wsjtx
reports "wsjtx doesn't support additional languages"
Hi, in my view goalposts are fine with the white line beneath the RX one
and the waterfall background no longer quite black.
Window resize issue on turning menus off has gone.
Nothing else checked yet.
Alan G0TLK
___
wsjt-devel mailing list
wsjt-
> Am 25.05.2020 um 02:40 schrieb Jim Charboneau :
>
> This version has dropped the connection to my radio 5 time in 30 minutes.
>
> Radio --- Flex 6300
> SDR Software -- SmartSDR v. 1.11.12
>
> Thought you should know.
>
> 73
> Jim
> KC1BB
> ___
>
Thanks VERY much for this one:
"Hold Tx frequency no longer cleared when switching between modes."
We're halfway there -- TX frequency defaults to 1500 Hz when I've
returned from MSK144 to FT8. Is it possible to remember prior setting of
TX frequency?
I think the goalpost markers are improved
42 matches
Mail list logo
