Hi Forrest,
I expect that it won't be long before we can release RC7. Keep your
fingers crossed for us.
73 de Uwe, DG2YCB,
Am 24.09.24 um 20:48 schrieb Forrest Fleming via wsjt-devel:
Hi John,
Would you mind making the resulting build available? I understand if
it's not ready for public rele
VFO B is “0 Hz” for about half a second. Then the correct frequency is set.
These abnormalities were not there a few weeks ago. Anyone else of the FT-991 /
FT-991a users observing the same?
73 de DG2YCB,
Uwe
German Amateur Radio Station DG2YCB
Dr. Uwe
Hi Tony,
Very likely the slider weirdness is due to a bug in Qt. It occurs primarily on
MacOS 12 (Monterey). In case you are able to build from source, please try it
using Qt 5.15.2. This should fix it.
Unfortunately I don't have a Mac computer myself, otherwise I would provide you
with a
Hi Tobi,
I am also using a FT-991. Maybe before we write long emails: Do you have
TeamViewer and are you available via Skype or Google Meet or so? If yes,
please send me a private email and I will try to help you get it working.
73 de DG2YCB,
Uwe
Hi Reino,
Before I answer your questions, a few general comments. WSJTX has internally
several timers that keep all processes clean and prevent unwanted effects. The
normal user doesn't even notice all this, and that's intended. This is exactly
how it should be with the new Tune watchdog. If yo
Cc: Carey Fisher
Betreff: Re: [wsjt-devel] SUGGESTION
Make it a programmable (up to 10 minutes) time, default to 2 minutes.
On Sun, Mar 6, 2022 at 12:19 PM DG2YCB, Uwe via wsjt-devel
wrote:
Hi all,
Since I had similar requests for such a function in the past, I already
programmed a
Hi all,
Since I had similar requests for such a function in the past, I already
programmed a time limit for the TUNE button a few weeks ago. This will be
included in the next WSJTX release. 10 seconds is of course much too short, but
I think 2 minutes is reasonable. This should be long enoug
; Are you using rig split? Richard is.
>
> There is a problem in there for rig split.
>
> Mike W9MDB
>
>
>
>
>
>
>
>
>
>
>
>
> On Sunday, January 16, 2022, 11:03:11 AM CST,
> DG2YCB, Uwe via wsjt-devel wrote:
>
>
>
&g
Richard,
Can you rule out that this is not an RF interference? Because my FT-991 runs
flawlessly with WSJTX v2.5.4 on Linux Mint 20.2.
73 de Uwe DG2YCB
Von: Richard Shaw via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Gesendet: Sonntag, 16. Januar 2022 17:05
An: WSJT softwar
Hi Yoshi,
Try the following.
1. Revert WSJTX to v2.5.2.
2. Copy the file "libhamlib-4.dll" (usually in C:\WSJT\wsjtx\bin) to any other
place of your computer (or simply rename it to "libhamlib-4.dll_2.5.2".
3. Update WSJTX again to v2.5.4
4. Rename the "libhamlib-4.dll" file from v2.5.4
I can offer my FT-991 for the tests. (I have the old model, NOT FT-991A.)
73 de Uwe, DG2YCB
Von: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Gesendet: Donnerstag, 4. November 2021 13:36
An: WSJTX Group; WSJT Software Development
Cc: Black Michael
Betreff: [wsjt-
AVX either (Intel Pentium I).
73 de DG2YCB,
Uwe
German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: dg2...@gmx.de
Info: www.qrz.com/db/DG2YCB
-Ursprüngliche Nachricht-
Von: Bill Somerville [mailto:g4...@classdesign.com]
Gesendet: Mittwoch, 9. Juni 202
4WJS.
On 16/02/2021 12:27, DG2YCB, Uwe wrote:
Hi Bill,
Why are you not open to such a solution? Would certainly help to increase the
extremely small number of FST4 users. It takes too long to switch
configurations.
But: I've already found a solution for myself. In my wsjt-x_improved v
f: Re: [wsjt-devel] Please save the T/R sequence lengths for each mode
separately
On 16/02/2021 10:16, DG2YCB, Uwe wrote:
Hi Bill,
Please let wsjt-x save the T/R sequence lengths for each mode separately.
Why? Because for FST4 on 160m, FST4-A60 seems to become something like a
"standard&quo
Hi Bill,
Please let wsjt-x save the T/R sequence lengths for each mode separately.
Why? Because for FST4 on 160m, FST4-A60 seems to become something like a
"standard", and for Q65 on 6m Q65-A30. But as wsjt-x currently saves only
one T/R sequence lengths setting, each time the users have to chan
Gustavo,
Are you sure you are using WSJT-X? Version number "2.2.0-rc155" looks more
like JTDX. I know that there are a couple of bugs in JTDX at the moment.
Maybe it's worth trying WSJT-X instead.
73 de Uwe, DG2YCB
Von: Gustavo Barona C. [mailto:gubar...@cable.net.co]
Gesendet: Donnerstag, 2
Hi Bill and Mike,
For your information: I have just compiled wsjt-x v2.3.0-rc3 with a freshly
created hamlib (Build Date: 21-01-2021 at 11:16, source files from hamlib
master repository). Result: My Yaesu FT-991 seems to work without any
problems. Frequency changes and TX / RX work perfectly in bo
Hi Bill,
I would also like to offer you to do the tests with my FT-991. Let me know what
to do.
73 de Uwe, DG2YCB
-Ursprüngliche Nachricht-
Von: Bensay 1 [mailto:bensam...@hotmail.com]
Gesendet: Mittwoch, 20. Januar 2021 17:24
An: WSJT software development
Betreff: Re: [wsjt-devel] Reque
RO
model of the same size has a warranty of 5 Years or 1200 TB written!
73
Bill
G4WJS.
On 08/01/2021 09:48, DG2YCB, Uwe wrote:
Hi Bill,
Thank you for your answer. In principle it worked, but even without the
wsjtx_log_config.ini file, too much unnecessary things are logged in my
opinion
we, DG2YCB
Von: Bill Somerville [mailto:g4...@classdesign.com]
Gesendet: Donnerstag, 7. Januar 2021 21:57
An: wsjt-devel@lists.sourceforge.net
Betreff: Re: [wsjt-devel] wsjtx_syslog.log
On 07/01/2021 20:49, DG2YCB, Uwe wrote:
Hello Bill,
I just noticed that WSJT-X v2.3.0-rc3 (64-bit) crea
Personally, I would really appreciate it if WSJT-X had this function. This
additional data would significantly enhance the wsjtx_log.adi file. In addition
to QRZ.com, hamQTH.com should be supported (free xml access).
73 de Uwe, DG2YCB
Von: Dave Slotter, W3DJS [mailto:slotter+w3...@gmail.
/2020 12:06, DG2YCB, Uwe wrote:
Many thanks, Bill! That helps a lot.
I found the file wsjtx_syslog.log already, and I saw for example that it
contains dozens of lines about audio dropouts. When CPU load of my computer
is high, these lines occur more often (understandable) although all decodes
se
@lists.sourceforge.net
Betreff: Re: [wsjt-devel] How to configure the new internal system and data
logging facility?
On 23/11/2020 09:43, DG2YCB, Uwe wrote:
- A new internal system and data logging facility used to provide
trace, debug, information, warning, error, and fatal
- A new internal system and data logging facility used to provide
trace, debug, information, warning, error, and fatal error
messages. The verbosity and filtering of messages is user definable
via a configuration file. Without a configuration file a basic log
is written wi
ble to boot on such AMD computers unless hardware acceleration is
disabled. Unbelievable!
73 de DG2YCB, Uwe
Am Donnerstag, den 24.09.2020, 00:07 +1000 schrieb Adrian:
> Can you start as user; Uwe instead of using sudo ? Pulseaudio etc
> will probably be more friendly to your user profile .
&
en 23.09.2020, 13:49 +0100 schrieb Bill Somerville:
> sudo adduser dialout $USER
73 de DG2YCB, Uwe
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
a XR16850
What am I doing wrong? Do I have to configure something else?
73 de DG2YCB, Uwe
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Hi Mike,
Find enclosed the debug.txt file. (I’ve included some more lines.)
73 de Uwe, DG2YCB
Von: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Gesendet: Dienstag, 2. Juni 2020 21:21
An: 'WSJT software development'
Cc: Black Michael
Betreff: Re: [wsjt-devel]
Hi Bill and others,
I have the same error here at my PC: WSJT-X v2.2.0 GA cannot communicate with
my FT991 via normal Com Port. Audio works normal, but CAT control is broken.
When I click on “Test CAT” the error message “Rig failure Hamlib error…”
occurs. Connection via OmniRig still works w
rlying technology and to apply informed decision making to comprehend what
is displayed. After all the consequences of trying to communicate with an
invalid station whose callsign was printed in a false decode is not serious,
maybe some embarrassment and a little wasted time.
73
Bill
G4WJS.
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
e->setVisible(b);
As said, if line 5736 is disabled (//) or changed to
if(i==14 and (!b)) ui->cbHoldTxFreq->setVisible(b); ,
then the error is gone.
73 de Uwe, DG2YCB
Von: DG2YCB, Uwe [mailto:dg2...@gmx.de]
Gesendet: Mittwoch, 20. Mai 2020 15:16
An: 'WSJT software developm
Joe,
FYI: The error that Hold TX Frequency button is always unchecked after some
mode changes, results from line 5736 in mainwindow.cpp. If that line is
disabled (//), the error disappears and the Hold TX Frequency button remains
enabled.
5735 if(i==14) ui->cbHoldTxFreq->setVisible(b);
, DG2YCB
-Ursprüngliche Nachricht-
Von: Joe Taylor [mailto:j...@princeton.edu]
Gesendet: Montag, 18. Mai 2020 15:31
An: WSJT software development
Betreff: Re: [wsjt-devel] CTRL+V no longer working
Hi Uwe,
On 5/18/2020 09:12, DG2YCB, Uwe wrote:
> I remember that with WSJT-X th
Many thanks Bill for your competent answer.
73 de Uwe, DG2YCB
Von: Bill Somerville [mailto:g4...@classdesign.com]
Gesendet: Montag, 18. Mai 2020 15:22
An: wsjt-devel@lists.sourceforge.net
Betreff: Re: [wsjt-devel] CTRL+V no longer working
On 18/05/2020 14:12, DG2YCB, Uwe wrote:
Hi,
I
Hi,
I remember that with WSJT-X there was the option to press CTRL+V to save the
last periods .WAV, regardless of the menu settings. I just tried it, but
nothing happened. Was that somehow deactivated? (I am using WSJT-X
v2.2.0-rc1 x64, Windows 10 pro with German Keyboard.)
73 de Uwe, DG2YCB
_
Hi Grant, Joe, Bill,
I've seen that a couple of times too. It seems to be happening suddenly. I
have not yet found any real correlation with any action or constellation,
but I suspect that it primarily happens when the CPU usage has increased to
100% in between (e.g. when other software is running
Hi Bill,
I have observed at least ten times that the decode button suddenly keeps its
turquoise color and the decoding seems to hang somehow. It is automatically
reset at the next decoding time. I saw this with the official file
wsjtx-2.2.0-rc1-win64.exe from the WSJT home page as well as with all
Hi Bill,
WSJT-X v.2.2.0-rc1 really works well. The new ft8 decoder is great! WSJT-X
now even beats JTDX in terms of the number of decodings. Huge improvement!
However, I (still) observe two minor bugs / unwanted behaviors:
1.) When coming back from hound mode Hold Tx Freq box is always uncheck
Hi Bill
Consider my last post obsolete. I found it. It is in mainwindow.cpp in under
void MainWindow::createStatusBar() . (lines 2235 - 2273). Move it one
position to the left. Now it looks like that:
73 de Uwe, DG2YCB
___
wsjt-devel mailing list
w
Hi Bill,
Hope you are well in times of Corona.
I observed a small bug in WSJT-X's UI: When width of the main program window
is set below a certain value and when you the switch from any FT or JT mode
to either MSK144 or ISCAT mode, the width of the program window expands
unnecessarily. One can re
view a QSO
which is mandatory to be logged took place even after one single exchange of
signals between two stations.
73 de Uwe, DG2YCB
Von: DG2YCB, Uwe [mailto:dg2...@gmx.de]
Gesendet: Donnerstag, 27. Februar 2020 17:19
An: 'WSJT software development'
Betreff: Re: [wsjt-devel] FT
IMO wsjt-x should auto-log all incomplete QSOs when at least one successful
exchange of the two callsigns was there. Just let wsjt-x automatically add 'QSO
incomplete' at Comments.
73 de Uwe, DG2YCB
___
wsjt-devel mailing list
wsjt-devel@lists.sourc
Hi Bill, Ted, Ria, Mike, and others,
Thanks a lot for your answers. I’ve forwarded your advice to that OM. He was
not yet aware of these possible causes, and he is very grateful for your help!
73 de Uwe, DG2YCB
___
wsjt-devel mailing list
wsjt-devel@l
Here is what I mean:
http://www.dg2ycb.duckdns.org/wsjt-x_band_change_bug.mp4
IMO band changes make sense most, immediately when one RX cycle has been
finished, because of course I don't want to lose the next cycle. However, in
practice this means +- 1 second before or after the end of one cycle
, DG2YCB
Von: DG2YCB, Uwe [mailto:dg2...@gmx.de]
Gesendet: Donnerstag, 20. Februar 2020 16:36
An: 'WSJT software development'
Betreff: AW: [wsjt-devel] Band change @ wsjt-x: decodes of old cycle falsely
detected/reported as from new band
Here is what I mean:
http://www.dg2ycb.duckdn
is recommended to stop monitoring for the duration of
band change and erase Band activity display.
73, Reino oh3mA
From: DG2YCB, Uwe [mailto:dg2...@gmx.de]
Sent: 20. helmikuuta 2020 12:20
To: wsjt-devel@lists.sourceforge.net
Subject: [wsjt-devel] Band change @ wsjt-x: decodes of old cycle f
Hi Joe, Steve, Bill et al.,
I don't know if it's already known: At WSJT-X v2.1.2 0068f9 after changing
the band, remaining decodes of the old cycle are still falsely detected as
from the new band. And likely, these decodes are then also reported to PSK
Reporter or HamSpots for the wrong band. Woul
devel@lists.sourceforge.net
Betreff: Re: [wsjt-devel] Building WSJT-X from sources - need help
Uwe,
you'd get faster help by heading to the JTSDK support group on Groups.IO.
Neil, KN3iLZ
On 11/27/2019 9:57 AM, DG2YCB, Uwe wrote:
Hi, I am trying to build WSJT-X from sources on my Win 10, 64 bit system
Hi, I am trying to build WSJT-X from sources on my Win 10, 64 bit system,
but need some help.
I've downloaded and installed JTSDK64-Tools-3.1.0 and JTSDK64-Apps-3.1.0.2
and run through all steps described in Readme.md Everything looked good, but
at MSYS2 step 5 "Build hamlib" failed ("QT version
WSJT-X 2.1.1 64-bit works well so far on my Win 10 system. Also no OmniRig
issues so far. Thanks for this new release.
One thing: "Hold Tx Freq" setting is still not remembered when coming back
from F/H mode. IMO would be worth to be fixed, as it could cause
accidentally QRM.
73 de Uwe, DG2YCB
Hi,
Fortunately, there are only very few false positive decodes at wsjt-x
v.2.1.0 (64 bit). But I've noticed for a long time that 99 to 100% of the
false positive decodes are /R call signs. They are decoded at a2 to a6
level. Current example from 160m: "191045 -24 -1.4 378 ~ DG2YCB BO4BIG /R R
FQ9
Hi Bill and all,
The point I didn't consider was that two reports cannot be combined in one
slot. Means, when there are currently no RR73 messages, the free capacity of
those slots will be unused. Somehow unsatisfactory, but logical.
73 de DG2YCB,
Hi Bill,
I recently observed the following (likely unwanted) behavior when switching
from FT8 to MSK144 and back:
1.) Width of wsjt-x's main window is always increased when switching to
MSK144 (although not needed) and old width is not remembered when switching
back to FT8
2.) "Hold Tx Freq" is
Hi Hasan,
An interesting observation! What if you uncheck the boxed “Color Band
Activity…” and/or “Highlight Band Activity…”? Is the error still there or is it
gone?
I had in the past also some (other) troubles with JTAlert, but it turned out
that some files on my computer must
I've had it five times now, that when trying to open "Settings" WSJT-X 2.1.0
64-bit showed an empty window. After restarting WSJT-X behaves normal again.
I haven't seen that with any of the prior versions. Will try a clean
installation to see if it changes anything. My setup: WSJT-X v2.1.0 64-bit @
has
changed
> Anyone else experiencing that with the 64-bit version?
Yes.
Tune power also.
IC-7300, Win 10 x64 Pro.
73, Paul K6PO
On Mon, Jul 15, 2019 at 8:52 AM DG2YCB, Uwe wrote:
Many thanks for the new GA version! Works well so far here on my computer
(64-
Many thanks for the new GA version! Works well so far here on my computer
(64-bit Windows).
One observation: With the new 64-bit GA version I needed to increase PWR
slider from around 50 % to now nearly 100 % to get sufficient audio level at
my FT-991. Old settings resulted in a few mW TX output. W
Hi,
I just saw on 2m a FT8 signal which had strange splatters about 270 and
2*270 Hz below the main signal, the splatters narrower than the main
transmission. There was only this station on the band. What may be the
reason for these splatters?
73 de Uwe, DG2YCB
__
I’ve not yet seen the results, but your this approach really looks like
something which could bring a substantial progress regarding the timing issue.
Reason why I am supporting a warning message is that, besides field days, I saw
dozens of OMs/YLs who are not aware at all that system time o
Sam,
alltext.exe works great, BUT there is one big disadvantage: Once the ALL.txt
file is opened with alltext.exe, the ALL.TXT file is locked by Windows. And due
to that WSJT-X is showing error messages “Cannot open …ALL.TXT” because the
file is in use (see screen shot). Is there a fix for this
A very good idea to set up time beacons, Reino! I like this approach!
However, as a short-term solution IMO dev team should find a way to use the
EXISTING data set of DT values for a pop-up saying that very likely time is
not synced correctly, plus an option to correct time by one click. Look t
f: Re: [wsjt-devel] 2nd instance hangs when 1st instance needed to be
re-started
On 22/06/2019 09:30, DG2YCB, Uwe wrote:
Hi,
Very often I am running two instances of WSJT-X concurrently. Works
perfectly. However, for all versions of WSJT-X the 2nd instance hangs when
the 1st instance needed to
Hi,
Very often I am running two instances of WSJT-X concurrently. Works
perfectly. However, for all versions of WSJT-X the 2nd instance hangs when
the 1st instance needed to be re-started (e.g. when USB soundcard was
temporally lost). Behavior is 100 % reproducible. At the 2nd instance
"Decode" fi
Same experience here. Best S+P never ever called anyone!
73 de Uwe, DG2YCB
Von: Jon Anhold [mailto:j...@anhold.com]
Gesendet: Freitag, 14. Juni 2019 22:11
An: WSJT software development
Betreff: Re: [wsjt-devel] Best S+P button
For what it's worth, my experience matches David's.
M
Hi,
Just made the following observation: With v2.1.0-rc7 "Highlight by Mode" is
not remembered. Checked that box, closed and started WSJT-X again, and the
box is always unchecked. Error is reproducible here at my computer. Someone
else having this issue?
73 de Uwe, DG2YCB
___
Hi,
Is there a chance to get the optional highlighting of 73 / RR73 messages?
Would be really nice if you implement such a feature. (Best would be on
Colors tab.) Why? Because many stations do not call CQ anymore, or if, then
only every 10 minutes or so, so that such callsigns in practice are not
I did a couple of QSOs with rc7, both during Mock Contest (RU mode) and as
well as a number of standard QSOs. Here are my observations:
(1) The new FT4 protocol works fine. MUCH better than the old one!!! No
unreasonable loops anymore. When there is a visible trace, now usually
signal is being dec
Hi Tom,
I had the same issue here with my 64-bit version of WSJT-X. Just installed the
following 64-bit version of OpenSSL, and "Fetch now" now works fine:
https://slproweb.com/download/Win64OpenSSL_Light-1_0_2s.exe
Restart WSJT-X after installation.
73 de Uwe, DG2YCB
-Ursprüngliche Nachri
Same here. Win 10 64 bit version not starting.
73 de Uwe, DG2YCB
Von: Jari A [mailto:oh2...@gmail.com]
Gesendet: Sonntag, 2. Juni 2019 20:55
An: WSJT software development
Betreff: [wsjt-devel] Bug report
win 7 64 bit
Does not start, reboot does not help.
FYI
Best rgds,
:Jari /
Hi,
I just saw on 14.080 MHz an interesting signal. TX/RX cycle like FT4, but
bandwidth like FT8. Signal could not be decoded. Is someone testing a new,
unpublished mode?
73 de Uwe, DG2YCB
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforg
Am I right, that the QT bug has already been fixed today? “Continuous
Integration: Passed” (see https://bugreports.qt.io/browse/QTBUG-75024 and
https://codereview.qt-project.org/#/c/258395/)
73 de Uwe, DG2YCB
Von: john [mailto:j...@thelongs.us]
Gesendet: Donnerstag, 9. Mai 2019 18:40
Sorry, thought you meant the 73/RR73 highlighting...
73 de DG2YCB,
Uwe
German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: dg2...@gmx.de
Info: www.qrz.com/db/DG2YCB
-Ursprüngliche Nachricht-
Von: DG2YCB, Uwe [mailto:dg2...@gmx.de]
Gesendet
How can I enable that, Bill?
73 de DG2YCB,
Uwe
German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: dg2...@gmx.de
Info: www.qrz.com/db/DG2YCB
-Ursprüngliche Nachricht-
Von: Bill Somerville [mailto:g4...@classdesign.com]
Gesendet: Sonntag, 5. Mai
Hi Joe, Bill, and others,
I kindly like to propose a small additional feature in WSJT-X: It would be
good to have a checkbox, where when enabled also the 73/RR73 messages are
highlighted like CQ. Why? Because more and more DX stations - if at all -
call CQ only every 10 minutes or so, and hence
Next curious observation: WSJT-X 64 bit and JTDX in parallel, listening to 6m
band, both connected to the same audio source, no QSO running, only a few
stations on band, with both programs saving all audio files to my SSD. Results:
From time to time JTDX decodes more callsigns. So far so good (o
audio
samples for that.)
73 de Uwe, DG2YCB
Von: DG2YCB, Uwe [mailto:dg2...@gmx.de]
Gesendet: Freitag, 3. Mai 2019 14:09
An: 'WSJT software development'
Betreff: Re: [wsjt-devel] FT8 decoding sensitivity: WSJT-X vs. JTDX
Bill,
Decode is already set to "Deep" plus AP. But
9 12:46
An: wsjt-devel@lists.sourceforge.net
Betreff: Re: [wsjt-devel] FT8 decoding sensitivity: WSJT-X vs. JTDX
On 03/05/2019 11:32, DG2YCB, Uwe wrote:
Example 2: Today (190503_084800) on 20m. I am trying to make a QSO with
LZ497OM. LZ497OM's signal is weak, but the frequency is free. JTDX de
21:38
An: wsjt-devel@lists.sourceforge.net
Betreff: Re: [wsjt-devel] Sometimes difficult to get FT4 QSOs completed
On 30/04/2019 20:28, DG2YCB, Uwe wrote:
Here one example of a QSO which needed a loop of reports until it came to “73”.
Clear band, sufficient signal strength. Why is this
Hi, just made a couple of FT4 QSOs. Works well. However, sometimes it's
somewhat difficult to get the QSOs completed. Endless exchange of reports
but no 73 or RR73 message. Is anyone else experiencing this?
73 de Uwe, DG2YCB
___
wsjt-devel mailing l
releases: Maybe it is possible
somehow optionally to reduce the total height of the control panel (e.g.
reducing horizontal spaces, reducing size of clock, or making fields a little
smaller). Would help those using laptop computers.
73 de DG2YCB,
Uwe
Hi,
One minor issue: The layout for the various fields in WSJT-X v2.0.0 is
somewhat different when "Menus" is enabled or disabled. (My preferred layout
is that when menus are enabled, but usually I like the menus disabled.). Not
a big deal, but maybe it can be corrected for the next release.
L
I just had a funny hash collision. Was calling , got - for what
reasons ever - a reply " DG2YCB", clicked on that and then started
a QSO with myself (which I of course stopped):
190121_194115 Transmitting 1.84 MHz FT8: DG2YCB
190121_194145 Transmitting 1.84 MHz FT8: DG2YCB
194145 -24
me…
73 de DG2YCB,
Uwe
German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: dg2...@gmx.de
Info: www.qrz.com/db/DG2YCB
Von: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Gesendet: Sonntag, 13. Januar 2019 17:47
An: wsjt
Re: [wsjt-devel] User-specific CAT commands?
On 12/01/2019 19:15, DG2YCB, Uwe wrote:
Hi,
I am using WSJT-X together with my Yaesu FT-991. Everything works fine so
far, including CAT Control either direct via serial port or with OmniRig in
between. However, using WSJT-X's band
0C;AC000;", because "FA014074000;" is already generated by the
built-in CAT control. After a band change, WSJT-X would the send a
combination of the standard command for frequency change plus that
user-specific CAT command. (As default fields for user-specific CAT commands
shall be empty.)
Yes, would be great to some more information 4-character qualifiers. Just
tested it with "CQ LOTW DG2YCB JO42", but transmitted was "CQ L DG2YCB
JO42".
73 de Uwe, DG2YCB
-Ursprüngliche Nachricht-
Von: Martin Davies G0HDB [mailto:marting0...@gmail.com]
Gesendet: Donnerstag, 3. Januar 2
Dan, does your PC time eventually need to be synchronized? Check deviation at
https://time.is/
73 de Uwe, DG2YCB
Von: Dan Malcolm [mailto:k4...@outlook.com]
Gesendet: Dienstag, 11. Dezember 2018 20:30
An: 'WSJT software development'
Betreff: Re: [wsjt-devel] Is it just me? v2.0?
Than
Had the same here. I unchecked the box, clicked on "OK" and then checked the
box again and clicked on "OK" once again. Now power level is being retained.
73 de Uwe, DG2YCB
-Ursprüngliche Nachricht-
Von: dgb [mailto:n...@bayland.net]
Gesendet: Montag, 10. Dezember 2018 18:40
An: wsjt-deve
version of WSJT-X? I would
support that.
73 de DG2YCB,
Uwe
German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: dg2...@gmx.de
Info: www.qrz.com/db/DG2YCB
Von: m...@oz5xn.dk [mailto:m...@oz5xn.dk]
Gesendet: Freitag, 7. Dezember 2018
Hi Joe,
Please find afterwards a few suggestions for minor improvements/corrections.
(citing the existing text = blue color, red color = suggested
improvements/corrections, other comments = black color)
1.1. New in Version 2.0
Minor typo, as already mentioned by Charlie:
- IMproved suppor
Gary,
One possibility to check what they might have answered is running two instances
of WSJT-X in parallel, one v2.0.0 and one v1.9.1. I am doing that and saw that
a number of others seems to do it as well. Can be helpful, as there are
currently lots of 75 bit messages above 2 KHz as well as 7
It also happened to me many times. For example today three times out of four
QSOs. Two times I started a QSO, but after first report no more decoding. Each
time good signals around -13 dB. PC time synchronized within +- 5 ms. First I
thought that it was always QRM from 75 bit signals, but more a
ound colors.)
Hope this observation helps.
73 de Uwe, DG2YCB
Von: DG2YCB, Uwe [mailto:dg2...@gmx.de]
Gesendet: Mittwoch, 28. November 2018 09:36
An: 'Bill Somerville'; wsjt-devel@lists.sourceforge.net
Betreff: Re: [wsjt-devel] Color scheme: "on band" always highe
1127 142545 20181127
142715 20m 14.076956 DG2YCB
JO42gb
73 de DG2YCB,
Uwe
German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: <mailto:dg2...@gmx.de> dg2...@gmx.de
Info: <http://www.qrz.com/db/DG2YCB> www.qrz.com/db/DG2YCB
Hi,
In addition to the already discussed "worked before" bug, there is another
inconsistency in the color scheme logic, which from my point of view is a
more general issue: How is a new call highlighted, which is also a new CQ
zone (and eventually also a new ITU zone, et cetera)? According to m
Can someone translate the DXpedition Mode User Guide into Italian? Seems to
be really necessary .
73 de Uwe, DG2YCB
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
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
Sorry there was a typo. I meant of course “Worked B4 instead of New Call?”
instead of Worked B4 instead of New Band?
As reported by several OMs New Call (and also New Call on Band) is not properly
working. Only a small portion of “New Calls” are colored as they should. In
addition to tha
As reported by several OMs New Call (and also New Call on Band) is not properly
working. Only a small portion of “New Calls” are colored as they should. In
addition to that, I see the general problem, that a “New Call” in many cases is
also a “New Grid” or even a “New DXCC”.
To overcome the
1 - 100 of 117 matches
Mail list logo
