All four stations were strong. K1JT started out at +15 on 20 meters, but
within 20 minutes had dropped to -23 (late afternoon band change). 30 dB
change in about 20 minutes...talk about catching the band moving!
Completed with all 4 stations, but one completion was aided by a trick on
my end.
> On Mar 7, 2018, at 9:59 AM, Lawrence Lopez wrote:
>
> I found the really liked the new format of the waterfall.
> It was much less critical to adjust in order to get data.
The waterfall has no bearing on the ability to decode. It isn’t even needed.
Gary - AG0N
I could copy all 4 stations fairly well. I was able to get a signal
report from the fox on all bands, but only completed the contact on 40
meters. On the other bands I got stuck sending my signal report. It
appeared as though the fox was initiating new QSO's and not finishing
previous
Smeared is going to get some people angry emails about power, even though
they aren’t running power. Hope it works out
Ria
N2RJ
On Wed, Mar 7, 2018 at 2:30 PM Gary McDuffie wrote:
>
>
> > On Mar 7, 2018, at 9:59 AM, Lawrence Lopez wrote:
> >
> > I found
Hi Gary..
Not for decoding but find and fit into most free space.
BTW, I have it smooth too now, no changes, just upgraded.. I liked it more
like before it was..
Now I feel like glasses needed..
But somebody maybe like it or don't want to wear glasses and that way it is
more comfortable? :-)
Magnificent summary. Bravo!
-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu]
Sent: Wednesday, March 7, 2018 12:28 PM
To: WSJT software development
Subject: [wsjt-devel] DXpedition Mode Test Results
Hi all,
Here are a few highlights of
Hi Rockwell,
The development routine ft8d is not what you want for a stand-alone
command-line decoder. It is not kept up-to-date. Every now and then, when we
are testing a new feature or debugging a particular issue, we’ll bring it up to
date for that purpose. But at any given instant in time,
On 3/7/18 01:33, Игорь Ч via wsjt-devel wrote:
> Playing out silence in place of the lost packets is not a good idea:
> it will distrurb sychronization and will bring wrong Delta Time values
> to the weak signals at demodulation. I would suggest usage of some
> averaging instead of the silence.
On 07/03/2018 17:42, John Zantek wrote:
The OTA tests were a hoot, even with the hound-on-hound nonsense and
the unfortunate DQRM from XE.
Did anyone collect and mention the final numbers for the foxes? I
thought N1DG said ~190 for 30M, but I sense the total 40M QSO’s may
have been quite
Looks like you are building on Linux with JTSDK?
You need to edit /usr/local/bin/jtsdk and change the http: entries to
https:Also edit the jtsdk-wsjtx file to do the same
de Mike W9MDB
On Wednesday, March 7, 2018, 12:08:44 PM CST, Wolfgang
wrote:
Hello Mike,
Hello Mike,
(JTSDK-QT 5.5 ) C:\JTSDK)svn relocate
http://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx
https://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx
svn: E155024: Invalid source URL prefix:
'http://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx' (does not overlap target's
URL
Hi,
I made the QSO (TU Joe K1JT), but after it the DECODER went stuck no more
decoding even if the band was full of stations.
I had to close the program and started it again ...
After a while the problem appeared again; this time the button DECODE did
remain blue fixed. ...I was changing
Thank you, Bill. I agree…reaching 120 Qph will put a serious dent in the armor
of those who argue that the FT8 rate isn’t worth the effort vs SSB or CW. I
know there were some DXpedition vets in the foray last night, and I hope it was
an eye-opener for them.
N0AN’s comment exactly echoes
On 07/03/2018 18:08, Wolfgang wrote:
(JTSDK-QT 5.5 ) C:\JTSDK)svn
relocatehttp://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx
https://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx
svn: E155024: Invalid source URL prefix:
'http://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx' (does not overlap
I just got notified that from sourceforge that this problem has been fixed now.
de Mike W9MDB
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!
Hi all,
Here are a few highlights of results from last night's public test of
FT8 DXpedition Mode:
- The overwhelming majority of participating Hounds operated as
intended, and according to instructions. I copied 190 unique Hound
callsigns during the 2300 hour (when I was acting as Fox on
Hi Mike
Just throwing it out there - ‘FD’ while may be common on cw etc for some
contests the CQ xx characters are generally taken as State / Providence /
Region - while FD is not a US State - it could well apply to another country.
Hardcoding it into one app does cause more confusion.
The
Joe and everyone:
Thanks for the summary of what worked and didn’t last night. The bug in the
RR73 logic explains a lot.
Here are a few things I noticed:
Apart from our friend in Mexico, who simply made a mistake, I noticed a few
other instances of people transmitting on top of the Fox’s
> On Mar 7, 2018, at 1:27 PM, Joe Taylor wrote:
>
> I'm sure there is more to be said, but that will do for now. Depending on
> programming progress and on my own travel schedule, we may schedule another
> public test within a few weeks.
Thanks for the great job, Joe.
- Of course, some Hounds did not operate as intended. Several kept trying to raise Fox by calling below 1000 Hz.
Perhaps the software should block attempts to send Tx1 below 1000 Hz if Hound mode is enabled, and show a popup message
explaining why transmission did not start.
73 Alex
Hi
Been having lots of fun with WSJT-X. I recently became active on 630m
using my Kenwood TS-590SG and a Transmit transverter 80m in, 630m out
(3.2mhz offset).
http://njdtechnologies.net/the-mf-solutions-630-meter-transmit-downconverter
If I add an offset to the Frequencies Setting for 630m
On 3/6/18 08:05, Bill Somerville wrote:
>
> Our experience of users using the Elecraft remote kit using IP streaming
> is that latency and delay are a problem, this being because of our
> dependence on external wall clock synchronization. Can RTP provide
> absolute time-stamp information that we
Hello friends I am developing an integration software with WSJT-X that is
working very well, but I still lack one last thing send a request to
connect to another station via UDP port Can anyone please tell me how to
list the UDP communication command with WSJT-x? thank you so much
PY5JAP
JOSE
Some of the participants may have been deliberately breaking the rules as part
of the test.
It wasn't made clear, in advance, whether we should simply pretend the fox was
real to simulate a genuine deep DX pileup, or do weird stuff to check how
resilient the whole thing is.
I guess the team
On 07/03/2018 17:03, Black Michael via wsjt-devel wrote:
What does your "svn info" show?
Hi Mike,
I use git-svn and I use svn+ssh access as I have write access but here
is the equivalent:
$ git svn info
Path: .
URL: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx
Repository Root:
Hi All,
seems as http is no a good protocol today.
(JTSDK-QT 5.5 ) C:\JTSDK)svn list http://svn.code.sf.net/p/wsjt/wsjt/tags
svn: E175013: Unable to connect to a repository at URL
'http://svn.code.sf.net/p/wsjt/wsjt/tags'
svn: E175013: Access to '/p/wsjt/wsjt/tags' forbidden
But
svn list
Is there a downside to doing a macro expansion like this?
I've got this working and it only affects the display and not what's
transmitted. Takes advantage of unused country codes which I suppose someday
might be used..though X countries are fairly rare and calling for them even
more rare. Q
On 07/03/2018 17:19, Black Michael via wsjt-devel wrote:
Is there a downside to doing a macro expansion like this?
Hi Mike,
the obvious one is other applications not following suit. Changing the
interpretation of messages unilaterally is a recipe for confusion. At
least with the "E9aa"
Yup...that works
svn relocate http://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx
https://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx
They must've shutdown non-https access.
de Mike W9MDB
On Wednesday, March 7, 2018, 11:15:49 AM CST, Bill Somerville
wrote:
On
What other applications? Is anybody interpreting the directed calls for any
purpose besides JTAlert giving it a "#" ??
To me it's a tradeoff between "confusion" where non-macro users would see the
2-letter code and wonder what it's for and possibly ask questionsand the
ability to have "CQ
The OTA tests were a hoot, even with the hound-on-hound nonsense and the
unfortunate DQRM from XE.
Did anyone collect and mention the final numbers for the foxes? I thought N1DG
said ~190 for 30M, but I sense the total 40M QSO’s may have been quite
significant, since my screen was REALLY
On 3/6/18 08:05, Bill Somerville wrote:
> not very hard at all. The audio in WSJT-X is via a Qt I/O Device
> abstraction and making a UDP server that joins a multicast group to
> receive and send audio would only require a thin layer to manage
> datagram reception and transmission converting
To Bill (and Joe),
It just occurred to me that I could multicast my receiver output to you
in the frequency domain. UDP already provides the necessary framing. We
just define that as a new RTP "codec type".
I use fast convolution with overlap-and-save for filtering, so as long
as I tell you the
Hello Phil,
>I implemented RTP in about a page of C code, not counting all of the
>UNIX/Linux system calls needed to set up multicast sockets. That's
>actually the only hard part. With RTP I just check that the next packet
>is in sequence, drop any old duplicates, and play out silence in place
>of
On 03/07/2018 10:39 AM, Hans Piehler wrote:
Hi Hans,
> I started FT8 with a small equipment FT817. In this configuration I made
> some QSO.
>
> The picture FT817 show the settings and the screen. It seems to work right.
>
> Than I changed to my home station FT920. There ist the picture FT920
>
Perhaps one of the Fox channels can include a randomized ID (even like CQ PH0X
FM29), not to exceed 9 minutes? Might help pileup management.
George J Molnar
Washington, DC
@GJMolnar | KF2T
>
--
Check out the vibrant
While on 20M FT8 a few days ago I saw 5B4AIF and called him. It appeared that
he was using the DXpedition mode (N=1). While sending a RR73 message to one
station, it was followed by a semicolon and my call and report. I had called
the 5B4, hundreds of Hertz higher in frequency. When he answered
Morning all, I was only able to participate in the last 20 minutes of the 20m
test and most of the 30m test. Due to propagation, l was not able to decode the
fox on either band although I saw many hounds calling and providing their
signal reports.
I had set up wsjtx the night before in hound
My observations.
I was only able to participate during the first 20 minutes of the 20 meter
test at 2300z. Joe was decoding around -18 during the time and I was calling
using barefoot power. According to pskreporter, Joe heard me but I was never
called.
So my question is why I was never called?
On 07/03/2018 09:39, Hans Piehler wrote:
Now all stations are in the above range more than 2000.
I think this is not the normal range to compare with the FT817.
If I change the mode from DIG to USB, I have all stations in the
normal range but
no modulation comes to the backside connector.
Hello dear OM's,
I started with FT8 and a small equipment FT817. In this configuration I made
some QSO.
The picture FT817 show the settings and the screen. It seems to work right.
Than I changed to my home station FT920. There ist the picture FT920 with
the settings
and screen.
Now all
I found the really liked the new format of the waterfall.
It was much less critical to adjust in order to get data.
True the contrast was lower but could see much more information
was available.
The previous version 1.8.0 did note seem to able to show weak signals.
On Wed, Mar 7, 2018 at 11:26
It took me a few days to get it the way I wanted it but I like it way better.
Jim S.
N2ADV
-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: Wednesday, March 7, 2018 11:27 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT-X 1.9.0 rc2
Been that way for a day and others are having problems too
What does your "svn info" show?
Path: .
Working Copy Root Path: C:\JTSDK\src\wsjtx
URL: http://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx
Relative URL: ^/branches/wsjtx
Repository Root: http://svn.code.sf.net/p/wsjt/wsjt
Repository UUID:
Jim --
I don't think you had to scramble. If Fox calls you, your Tx3 message
will be sent (somewhere in 300-900 Hz), even if Tx Enable is not engaged.
-- Joe
On 3/7/2018 11:05 AM, James Shaver wrote:
Yep, twice the timer had expired on me right as the “Fox” called me and
I
Bill,
TX timeout timer is about right. Prevents non-stop (when not being heard)
QRM from Hounds. Also, when it times out, you have time to let a couple
cycles go by and see where in the band it might be best to call (look for
hole).
I did this multiple times (let it expire), watched the pileup,
Hi Jim,
Check out item 12 in the Hound instructions:
“12. After you receive a signal report from Fox, WSJT-X will automatically send
your next transmission as message Tx 3 (“R+rpt”) at a randomly chosen frequency
between 300 and 900 Hz. Note that WSJT-X will send this message even if Enable
Thanks, Steve and Joe both - my sleep-deprived brain completely failed to
register that part.
Jim S.
-Original Message-
From: Steven Franke [mailto:s.j.fra...@icloud.com]
Sent: Wednesday, March 7, 2018 11:13 AM
To: WSJT software development
Subject: Re: [wsjt-devel] Timer
Hi Jim,
Is this a problem with sourceforge? If so, has anybody reported the problem?
Updating '.':
svn: E175013: Unable to connect to a repository at URL
'http://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx'
svn: E175013: Access to '/p/wsjt/wsjt/branches/wsjtx' forbidden
de Mike W9MDB
On 07/03/2018 16:18, Black Michael via wsjt-devel wrote:
Is this a problem with sourceforge? If so, has anybody reported the
problem?
Updating '.':
svn: E175013: Unable to connect to a repository at URL
'http://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx'
svn: E175013: Access to
On 07/03/2018 16:21, Ron Schwartz wrote:
The 1.9.0 rc2 waterfall now appears ‘smeared’ and weak traces are not
as visible as earlier versions (see attached). Is this an intentional
change?
Hi Ron,
it has been changed, the intent was to improve the visibility of weak
signals. Please try
Great job with the test last night. I did find the 2 minute timer to be a real
pain, however. I understand you do not want a robot operation, but a 5 or 10
minute timer would be less frustrating.
When the software shuts off the Enable TX, how do we know that we are still on
the correct
Yep, twice the timer had expired on me right as the “Fox” called me and I had
to scramble.
Jim S.
N2ADV
From: Bill Turner via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: Wednesday, March 7, 2018 11:03 AM
To: WSJT Software Development
Cc: Bill Turner
Subject: [wsjt-devel]
I missed that in the documentation - thanks for that, Joe! My cat was very put
out when I made a mad dash for the mouse ;)
I'll apologize to her later.
Jim S.
N2ADV
-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu]
Sent: Wednesday, March 7, 2018 11:09 AM
To: WSJT
54 matches
Mail list logo