On 04/08/2024 1:06 am, Gary McDuffie via wsjt-devel wrote:
But he’s not seeing them in the band activity window
Perhaps the OP is experiencing the long standing "Start new period
decodes at top" bug.
de Laurie VK3AMA
___
wsjt-devel ma
s complete.
That confirms the adif handling defects in Wsjtx.
Blank lines and multi-line records are acceptable per the adif specs.
de Laurie VK3AMA
(JTAlert author)
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge
a single record
which is still considered adif compliant.
de Laurie VK3AMA
(JTAlert author)___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
RC5 does not produce udp decode messages (#2) for SuperFox decodes.
Is this a defect or by design?
Without the decodes there is no way for JTAlert to notify a station they
were called by the fox nor to highlight their callsign (the called
station) in the Activity display.
de Laurie VK3AMA
On 02/06/2024 6:49 am, Black Michael via wsjt-devel wrote:
I just put a patch in Hamlib to ensure PTT gets turned off if it's on during a
band change.
Will this change make the existing (and long standing) "Allow Tx
frequency changes while transmitting" option obsolete?
de Laurie
On 02/06/2024 6:49 am, Black Michael via wsjt-devel wrote:
I just put a patch in Hamlib to ensure PTT gets turned off if it's on during a
band change.
Will this change make the existing (and long standing) "Allow Tx
frequency changes while transmitting" option obsolete?
affects all other QT based
applications installed like JTDX and MSHV.
This should not be needed to fix one specific broken area of the Wsjtx UI.
Hopefully one of the Wsjtx devs will respond.
de Laurie VK3AMA
(JTAlert author)
___
wsjt-devel mailing list
wsjt
personal fork of Wsjtx
behaves correctly, why cant the same code be applied to Wsjtx?
de Laurie VK3AMA
(JTAlert author)
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
tton size based on text font metrics is not
correctly calculating the width for high dpi situations.
My C++ skills are 30 years out-of-date so am unable to offer any advice
as to the cause.
de Laurie VK3AMA
___
wsjt-devel mailing list
wsjt-d
-.. . / -- .- .-. -.- / -. --... -.-- -..
DE MARK N7YD
A long standing defect that I gave up on getting the devs to correct.
All other UI controls inducing the Tx1-6 buttons are scaled correctly
except these buttons!
Here's mine, like you replicated across multiple devices.
de Laurie VK3AMA
is 2.50.8 or later, it has an ATNO Alert. See the Help file
Tutorials section.
de Laurie VK3AMA
(JTAlert author)
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
ing wrong since GridTracker works
perfectly. I am struggling to think of what to check and how to debug.
Thanks,
John
Did you not see my reply to your other message (posted over 3 hours ago)
on the same topic posted to the WSJTX support group?
https://wsjtx.groups.io/g/main/message/43351
de Lau
and alter their operating behavior.
de Laurie VK3AMA
(JTAlert author)
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
OH1KH
This is not a bug. WSJT-X has always behaved this way, emitting a UDP
status message with each character typed.
I would not like to see this long-standing behavior changed.
de Laurie VK3AMA
(JTAlert author)___
wsjt-devel mailing list
wsjt-devel
of the WD is not being reported
in the UDP Status message. That is, when the Hound WD is triggered it is
not setting the WD flag in the status message.
de Laurie VK3AMA
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https
flag in the UDP Status message (#1)
de Laurie VK3AMA
(JTAlert author)___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
flag when
the WD is triggered.
de Laurie VK3AMA
(JTAlert author)___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
, and the big black
blob of color in the WSJTX window provides the visual warning not to
double-click that decode.
de Laurie VK3AMA
(JTAlert author)___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt
Frode,
I recall that you are using JTAlert, is that correct? JTAlert is
stripping the non-numeric characters from the power field before sending
it to HRDLogbook. No attempt is made to decipher the meaning of the
alpha character, they are simply stripped.
de Laurie VK3AMA
_
On 16/08/2022 9:52 am, Laurie, VK3AMA via wsjt-devel wrote:
HamSpots has a couple of thousand callsigns that have their spots
permanently blocked because of repeated occurrences of wrong-band
spotting by the callsign
I neglected to add, that the majority of those habitual wrong-band
in the database.
de Laurie VK3AMA
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
-X is released with this breaking change. This will be a PITA
IMHO, the new ARRL DIGI mode should have been given a unique *previously
unused* number. It should have been 8 and the old 6 & 7 retained for FOX
& HOUND respectively.
de Laurie VK3AMA
(JTAlert author)_
ew ARRL DIGI mode should have been given a unique *previously
unused* number. It should have been 8 and the old 6 & 7 retained for FOX
& HOUND respectively.
de Laurie VK3AMA
(JTAlert author)
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
there?
The received report will be available as a dedicated field in the logged
QSO message when you log the QSO with that station.
It is not available as a dedicated field in any of the other UDP
messages unless you parse the decode message when that station calls you.
de Laurie VK3AMA
.
de Laurie VK3AMA
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
UDP Server
interface set to the loopback device. If WSJT-X is bound to the loopback
device for the UDP Server settings then you need to tell JTAlert to
explicitly to look for the UDP traffic on the loopback interface.
de Laurie VK3AMA
___
wsjt-dev
.
Where am I going wrong?
Thanks;
Bill
244 was a typo on my part., 224 is correct. Have you checked the JTAlert
help file, WSJT-X UDP Setup" topic?
de Laurie VK3AMA
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
On 4/11/2021 12:43 pm, Bill Barrett via wsjt-devel wrote:
This is from 2.5.0, first and second instance on Win11
does anyone know why they are different?
Thanks;
Bill W2PKY
You're running multiple WSJT-X instances with incompatible udp server
settings. You have one instance running unicast
se decodes.
If JTDX is truly offering superior decoding have any patches been
submitted to the wsjtx dev-team by the jtdx people?
de Laurie VK3AMA
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
I second this request!
I see this very frequently in the PSKReporter spot feed utilized by
HamSpots.
de Laurie VK3AMA
On 28/06/2021 9:36 am, Peter Sumner wrote:
Hello to the WSJT-X community,
Would the DEV team consider including some logic to abort the upload
of decodes in progress
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.sourc
most entry. This
is a departure from the traditional JTAlert automatic setting of the
necessary parameters as there is now no reliable way to determine the
WSJT-X settings and if the loopback interface is being used
de Laurie VK3AMA
On 10/01/2021 9:46 am, Rich - K1HTV wrote:
With WSJT-X version 2.2.2
to configurations or setting of unique udp ports. I
expect to make this beta release publicly available for testing within
the new couple of days.
de Laurie VK3AMA
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net
but simply putting windows into and out of
hibernation which will restore previously running processes and their
running state.
de Laurie VK3AMA
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists
Laurie VK3AMA
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
On 2/06/2020 9:17 am, Bill Somerville wrote:
On 01/06/2020 23:36, Laurie, VK3AMA wrote:
Tracked down the JTAlert non-coloring of decodes in the release
candidates.
2.1.2 works correctly, but the -rcs don't (tested both rc2 & rc3)
when the decode string contains a positive report. Rep
t; FIELD DAY
* 4 -> RTTY RU
* 5 -> WW DIGI
* 6 -> FOX
* 7 -> HOUND
de Laurie VK3AMA
<http://physics.princeton.edu/pulsar/k1jt/wsjtx-2.2.0.tgz>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
nd containing the "VK3AMA R-12" string
correctly colors while "VK3AMA R+12" fails with the only difference is
the number sign in the string sent to WSJT-X.
de Laurie VK3AMA
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
,
Associating JTAlert running with missing data in a WSJT-X Log window is
a "Red Herring", there is 100% NO association between the two.
de Laurie VK3AMA
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/list
process*, they are all still left running becoming zombie processes.
Force killing JTAlert significantly increases the risk of corruption of
the config.sqlite database file and the decodes database.
de Laurie VK3AMA
___
wsjt-devel mailing list
wsjt-devel
-Contest configuration title then click,
that's the second click.
de Laurie VK3AMA
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
configurations
in WSJT-X, one for you desired contest and the other non-contest. Once
setup, it is a single click using the "Configuration" menu to switch
between contest and non-contest.
de Laurie VK3AMA
___
wsjt-devel mailing list
unpredictable results.
There have been some further FT4 specific changes to JTAlert since
2.13.4. The latest build is 2.13.7, I strongly suggest you upgrade to
that build, there is no reason to stay with 2.12.10.
de Laurie VK3AMA
___
wsjt-devel mailing list
On 22/03/2019 9:13 am, Black Michael via wsjt-devel wrote:
What is FT8Startup.exe ???
It's not a part of WSJT-X.
de Mike W9MDB
Google returns results indicating it is part of the RBN FT8 spotting
http://www.reversebeacon.net/pages/Spotting+FT8+41
de Laurie VK3AMA
Please Ignore.
I noted the this is part of the UDP Protocol after reviewing
NetworkMessage.hpp
de Laurie VK3AMA
On 3/03/2019 5:58 pm, Laurie, VK3AMA wrote:
I was capturing localhost UDP data today and observed that an ADIF
record is transmitted on the UDP Server port (2237) when a QSO
I was capturing localhost UDP data today and observed that an ADIF
record is transmitted on the UDP Server port (2237) when a QSO is
logged. Is this a new undocumented feature or testing code that slipped
into the release?
de Laurie VK3AMA
___
wsjt
then that this is not working.
de Laurie VK3AMA
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
On 5/12/2018 9:14 am, Bill Somerville wrote:
if the signals are 75-bit FT8 signals then they will not be decoded,
they are incompatible.
Doh! My Homer Simpson moment!
As they are test files that I routinely use, they were created long ago
and are of course 75 bit.
de Laurie VK3AMA
& rc5.
Is this a defect?
de Laurie VK3AMA
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
of operation.
de Laurie VK3AMA
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
of the new v2.0 changes).
Is this by design, defect or oversight?
de Laurie VK3AMA
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
on PSKReported and such.
de Mike W9MDB
Mike,
+1 from me.
de Laurie VK3AMA
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
ckground? I was able to
produce the blank line effect by doing that.
de Laurie VK3AMA
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
(that is I have not received any advice to the contrary) in the
Callsign click setup of WSJT-X.
de Laurie VK3AMA
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
orts.
de Laurie VK3AMA
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
ham radio to rely on the internet, get yourself a chat
client and hang up your mic.
IMO, it is very likely that an Internet dependant mode will not be
accepted for award purposes or by Contest organisers.
de Laurie VK3AMA
___
wsjt-devel mailing
On 12/08/2018 8:53 AM, Bill Somerville wrote:
Hi Laurie,
the URI has been the same since WSJT-X v1.3 at least, probably since
it started spotting there.
73
Bill
G4WJS.
OK Bill,
Well that kills my explanation of what is the cause of no spots ;)
de Laurie VK3AMA
if it is
due to an old WSJT-X build.
de Laurie VK3AMA
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
name. You *must* use
*report.pskreporter.info* (previously various other domain names would
work). This is something to check if your reports are not being displayed.
de Laurie VK3AMA
--
Check out the vibrant tech
the "Unable
to communicate with the WSJT-X process" error posted.
de Laurie VK3AMA
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.lin
or Mike,
What was the solution?
de Laurie VK3AMA
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
On 3/08/2018 4:03 AM, Frank Kirschner wrote:
Mike Black got me set up with JTAlertX, and it's working well. Thanks.
73,
Frank
KF6E
Frank or Mike,
What was the problem?
de Laurie VK3AMA
--
Check out the vibrant
NOT JTAlert. JTAlert
never prompts you to log the QSO, there is no such code in JTAlert.
de Laurie VK3AMA
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link
time of the most recent change
to the header of the file. Ideally a list of changes, but a single line
date/time stamp would suffice.
Thanks for your consideration.
de Laurie VK3AMA
--
Check out the vibrant tech community on
Attached
de Laurie VK3AMA
On 29/06/2018 2:41 PM, Black Michael via wsjt-devel wrote:
I just tried this and see the correct answer for the logging packet.
Here is part of the two packets I got for logging from each config
where the station callsign is correct for that config W9MDB and W9MDB
is still using the station_call from the first configuration.
de Laurie VK3AMA
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link
r solution and is
more in-your-face.
de Mike W9MDB
Mike,
Excellent suggestion.
Adding if WSJT-X is set to NA Contest mode would also be a worthwhile
addition to the Status reporting message IMO.
de Laurie VK3AMA
--
er field (0004 in this case).
00064c4f47474552 is correct for that field. The Time QTime field
follows the the ID field per the spec.
adbccbda0002000400064c4f47474552 is correct.
de Laurie VK3AMA
--
C
om that received
in the decode.
DECODE time : [72465000 -> 20:07:45]
SEND TO WSJT-X time : [0451ba68 -> 0451ba68 -> 20:07:45]
Not sure how both 72465000 & 0451ba68 can represent the same time value.
Try using the Time value received in the decode packet.
de Laurie VK3AMA
ignores the
packets for non-CQ decodes. If WSJT-X changes to action those
currently-ignored packets there should be no need for a JTAlert change.
de Laurie VK3AMA
--
Check out the vibrant tech community on one
than WSJT-X. There were
recent reports of Z6 Calls being incorrectly logged as ZA coming from JTDX
From the latest JTDX release notes...
Discarded all changes done to Z6 prefix support: it has been supported
in all versions 18.1 and new changes violated WSJT-X protocol.
de Laurie VK3AMA
On 18/02/2018 7:50 AM, Black Michael via wsjt-devel wrote:
Testing if email group is working yet.
de Mike W9MDB
Took 2 days (based on your posting date/Time) for it to appear in my inbox.
de Laurie VK3AMA
--
Check
On 23/11/2017 8:58 AM, Laurie, VK3AMA wrote:
On 23/11/2017 7:31 AM, Dan Malcolm wrote:
WSJT-X is pretty good at running QSO’s with ‘split’ frequency
operation. JTAlert is essential for smooth QSO tracking and
logging. What I am missing is logging the separate frequencies for a
split QSO
" yet they are different. The QSO Logged
packet definition is incorrect, perhaps it should be named "Dial
frequency + Tx DF (Hz)" as that is what is being conveyed in the packet
data.
de Laurie VK3AMA
it is correctly conveying the Dial frequency.
de Laurie VK3AMA
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link
ogged" packet, that is the Dial frequency (Hz).
The UDP protocol "Status" packet does provide Tx DF and Rx DF values.
JTAlert would need to be extended to utilise those values when logging a QSO
de Laurie VK3AMA
by the protocol?
I realise that there are no combined keys with mouse double-click
currently implemented within WSJT-X (based on the help window)
de Laurie VK3AMA
--
Check out the vibrant tech community on one of the world's most
for SO_REUSEPORT or SO_REUSEADDR flags and doesn't support
UDP multicast.
JTAlert is undergoing a ground-up rewrite (still some months away from
release) using a modern compiler that allows for setting of SO_REUSEPORT
and SO_REUSEADDR and also supports joining a multicast group.
de Laurie VK3AMA
, why are the two status packets, one for start
decoding and the second for finished decoding still being sent?
I would hate to loose this ability and would have to restrict my testing
to older WSJT-X versions which is not ideal going forward.
de Laurie VK3AMA
any decode packets between these status packets.
RC1 behaves normally.
de Laurie VK3AMA
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link
Configuration and Session files for analysis. I want to
check when JTAlert received the change in band (to 6m) notification from
WSJT-X
de Laurie VK3AMA
--
Check out the vibrant tech community on one of the world's most
.
de Laurie VK3AMA
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt
Please disregard this request.
I can do what I need without the need for the reserving characters for
future modes.
de Laurie VK3AMA
On 26/07/2017 8:16 AM, Laurie, VK3AMA wrote:
Can the team pre-assign some mode-identification characters (displayed
in the WSJT-X decodes and used
ice on the
HamSpots server and avoid the need to fast track a JTAlert release.
Thoughts?
de Laurie VK3AMA
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.
to their right could be taken up by the slider.
de Laurie VK3AMA
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link
perceive there is a problem
with the software.
That's my 2cents.
de Laurie VK3AMA
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
, people will complain of perceived broken behaviour.
Having the slider adjacent to a non-related level indicator is the problem.
de Laurie VK3AMA
--
Check out the vibrant tech community on one of the world's most
engaging
off sending spots to HamSpots (use
the [Alerts -> Send Spots to HamSpots.net] menu)
--
de Laurie, VK3AMA
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! h
the 15s T/R period of FT8.
Regarding the broken JTAlert docking with WSJT-X when a configuration
switch is made, that is now fixed for the next release. (I used the
Close event to set a flag indicating that the hWnds needed to be
refreshed which are then updated on the next Heartbeat).
de Laurie
created a dedicated FT8 mode page on HamSpots
http://HamSpots.net/ft8/
de Laurie VK3AMA
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link
the fix.
Regarding T10 usage, there is only a small number of users, primarily EU
based. I have not seen any significant uptake of the mode, there appears
to be only a small number of regular spotters of the mode.
de Laurie VK3AMA
--
aracter chosen by
JTDX for the T10 mode and would explain an earlier message that
indicated that a FT8 spot on HamSpots appeared as T10 (likely came from
JTAlert which spots "~" decodes as T10).
de Laurie VK3AMA
calappdata% and starts with default settings that will need adjusted
per the user requirements and are independent of the installed JTAlert
Station Callsign.
de Laurie VK3AMA
--
Check out the vibrant tech commun
, it
comes back completely.
Do you have a solution for me please?
regards,
73,
PA3KVE
Kees
Kees,
Are you using JTAlert and have the docking option enabled? If so, then
to avoid the blank waterfall window, start WSJT-X before JTAlert, close
the Waterfall window then start JTAlert.
de Laurie VK3AMA
l greatly influence the level of activity to be
expected by any particular receiving station.
Your waterfall image, while it shows a lot of activity, does not
indicated a crowded band, IMO.
de Laurie VK3AMA
--
Check out th
will be released with
an announcement of a change to the time_on handling and the applicable
WSJT-X versions.
de Laurie, VK3AMA
--
Check out the vibrant tech
On 4/12/2016 10:27 AM, Bill Somerville wrote:
> I propose adding the WSJT-X version and revision to the UDP heartbeat
> message.
Bill,
This works for me. Thanks.
de Laurie VK3AMA
--
Check out the vibran
rtant enough to have the version number in the window
title and the build number in the "About" window to uniquely identify to
the end-user which version/build they are running, then someway to
expose this uniqueness in a UDP message needs also to be
introduce functionality that I may want to utilise programmatically,
yet that functionality may not involve any UDP changes and subsequently
the UDP #, you propose, will not alter and I am still where I am today,
unable to identify the build.
de Laurie VK3AMA
the
value from the Gui title, but that is not ideal. There have been times,
especially with somany users now running pre-release version of WSJT-X
that I have needed to know the build number to alter JTAlert behaviour.
Thanks
de Laurie VK3AMA
1 - 100 of 156 matches
Mail list logo
