I take it you are running two receivers? Seems to me a software solution is
possible.
Do we need to do any more than just average the two? In your example doesn't
look like time delays are needed for steering.
Mike W9MDB
On Tuesday, December 5, 2023 at 09:18:28 AM CST, robert evans L
Having used diversity reception techniques as
far back as the 70s and knowing it was used in
the 40s to improve RTTY reception for mil comms,
that improvement is possible.
An early technique used 2 coherent R-390As and
dual fsk demod unit. The antennas were often
of different polarization becaus
”,
sometimes with a considerable improvement in S/N.
73, Reino OH3mA
From: Christopher Wawak via wsjt-devel
[mailto:wsjt-devel@lists.sourceforge.net]
Sent: Tuesday, December 5, 2023 1:15 PM
To: WSJT software development
Cc: Christopher Wawak
Subject: Re: [wsjt-devel] WSPR and Diversity Receive
On Tue, Dec 5, 2023 at 3:35 AM Ben Gelb via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> Have I actually improved the SNR
> substantially? Or is it possible I am just affecting the SNR
> calculation (I think it is roughly measuring the average noise level
> in the 2.5kHz window, and com
I have been messing around with WSPR decoding on 630m with a pair of
phase-locked receivers and two receive antennas.
I have put together some software to save two sets of coherent samples
for each 2-minute period, and then after the fact I can combine the
two sets of samples w/ a configurable rel
Hello to you all,
this might not be favoured by all but give the idea a chance, on the WSPR
decode window, the UTC time is shown in the left most column, could this
field be augmented with the Julian day of the year also? for those who do
not know what the Julian day is, simply its the day number
In WSPR mode, displayed "Drift" is frequency change in Hz over the full
transmission.
-- Joe, K1JT
On 6/20/2022 11:41 AM, Pino Zollo via wsjt-devel wrote:
Please how shall I interpret Drift = 3 in a WSPR message ?
In which unit is it expressed ?
Thanks
Pino ZP4KFX
___
Please how shall I interpret Drift = 3 in a WSPR message ?
In which unit is it expressed ?
Thanks
Pino ZP4KFX
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Hi Serge,
I can find no record of an email from you last August.
The best published reference to the WSPR protocol and the WSPRnet
database is this one:
J. Taylor, K1JT, and B. Walker, W1BW, "WSPRing Around the World," in
QST, November 2010, pp. 30-32.
A copy of the paper's manuscript is a
Hi, this is Serge, ON4AA,
mostly known from https://hamwaves.com/propagation/
I am writing to this mailing list in a desperate attempt to contact Prof. Joe
Taylor, K1JT.
Late last August, I tried reaching Joe on his Princeton e-mail address but got no response, most probably due to the
pandem
Hi Joe,
The reason I was compiling the WSPR source was for the FMT tools. Guess
I need to RTFM again and use WSJT-X for FreqCal. I've not participated
in the ARRL Frequency Measurement Test, but I guess I wrongly assumed
the FMT tools are needed for that.
73
Stan
KM4HQE
On 3/4/22 13:32, Joe T
Hi Stan,
Compiling the old (circa 2014) version of WSPR is fine as a learning
exercise. It can give you a lightweight program that's relatively easy
to modify and play with. As Tom noted, however, it will not provide top
WSPR performance. It has not been kept up to date, and we view it as
In wspr2.f90 there is likely a line above line 68 that looks like this:
integer iclock(12)
Try changing it to:
integer iclock(33)
I haven't been paying attention to this thread but if you're trying to
build wspr0 I can tell you that it is not really great at decoding WSPR.
WSJT-X (in WSP
I got it to compile successfully by changing
integer iclock(12)
to
integer iclock(33)
in wspr2.f90
Don't know that was the "right thing" to do, but it seems to work.
73
Stan
KM4HQE
On 3/4/22 12:17, Stan Gammons via wsjt-devel wrote:
> I fetched the source using git clone https://git.code.s
I fetched the source using git clone https://git.code.sf.net/p/wsjt/wspr
wsjt-wspr and tried to build it on Kubuntu 20.04 but I get this error
Warning: Legacy Extension: Comma before i/o item list at (1)
gfortran -O2 -Wall -fbounds-check -fno-second-underscore -Wno-conversion
-Wno-character-trun
Thanks Warren.
73
Stan
KM4HQE
On 3/3/22 20:04, halst...@gmail.com wrote:
> Stan,
>
> WSPR source: https://sourceforge.net/p/wsjt/wspr/ci/master/tree/
>
> WSPR-X source: https://sourceforge.net/p/wsjt/wsprx/ci/master/tree/
>
> JTSDK packages to help you build the source:
> https://sourceforge.n
Not a Google fan, but thanks Dave.
Looks like it's for a Raspberry Pi. Not a problem, I have a Rasberry Pi 4. I'll
give it a whirl tomorrow.
73
Stan
KM4HQE
On 3/3/22 19:54, Dave Slotter, W3DJS wrote:
> Simple googling results:
>
> https://github.com/JamesP6000/WsprryPi
>
> On Thu, Mar 3, 2022
Stan,
WSPR source: https://sourceforge.net/p/wsjt/wspr/ci/master/tree/
WSPR-X source: https://sourceforge.net/p/wsjt/wsprx/ci/master/tree/
JTSDK packages to help you build the source:
https://sourceforge.net/projects/jtsdk/
Links obtained from: https://physics.princeton.edu//pulsar/K1JT/devel.
Simple googling results:
https://github.com/JamesP6000/WsprryPi
On Thu, Mar 3, 2022, 8:16 PM Stan Gammons via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> Is the source code for WSPR available somewhere? I tried to install the
> .deb package on Kubuntu 20.04 but it fails with the "ca
Is the source code for WSPR available somewhere? I tried to install the
.deb package on Kubuntu 20.04 but it fails with the "cannot satisfy
dependencies" error.
73
Stan
KM4HQE
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://l
While working with Rob, AI6VN, and Phil, VK7JJ on making sure that the
WsprDaemon package was uploading all of the WSPR spots it decoded I saw
that my own upload success rate for a single instance of WSJT-X 2.4 on a
Pi4 could be below 90%. This led to a more in-depth study with the
headline fin
On 07/09/2021 14:39, Brett G4FLQ via wsjt-devel wrote:
Attitudes to data protection differ across the pond and maybe across
other stretches of water too. Also between scientists and citizens.
However there is unanimity that the subject has all the appeal of an
expected tax demand!
The good ne
Attitudes to data protection differ across the pond and maybe across other
stretches of water too. Also between scientists and citizens. However there
is unanimity that the subject has all the appeal of an expected tax demand!
The good news is that a new dawn for understanding WSPR beckons through
Hi Phil,
nothing at all. I'm still in debt with you since I looked into your
Reed-Solomon Berleykamp-Massey decoder C source codes twenty years ago
or so which, along with Peterson's Error Correcting Codes book, gave me
the opportunity to learn something more than I was teached at university.
Se
On 5/16/21 09:15, Nico Palermo wrote:
> Hi Phil,
>
> I don't know what Joe used in WSPR but, for instance, he told me that
> he generated the sync sequence used in Q65 by means of direct optimization
> of its autocorrelation function, not in an algebraic way, so that its
> lateral peaks
> were mini
On 5/16/21 09:57, Joe Taylor wrote:
> Hi Phil,
>
> There was no generator polynomial, as such. Rather, the sync vector
> was chosen for its good autocorrelation properties simply by looking
> at a very large number of randomly generated bit patterns of the
> required length and weight.
>
> --
Hi Phil,
There was no generator polynomial, as such. Rather, the sync vector was
chosen for its good autocorrelation properties simply by looking at a
very large number of randomly generated bit patterns of the required
length and weight.
-- 73, Joe, K1JT
On 5/16/2021 3:53 AM, Phil
Hi Phil,
I don't know what Joe used in WSPR but, for instance, he told me that
he generated the sync sequence used in Q65 by means of direct optimization
of its autocorrelation function, not in an algebraic way, so that its
lateral peaks
were minimum only in a limited time shift interval.
I guess
Does anyone have the PN generator polynomial for the WSPR sync vector?
The source code seems to have only the generated (sub)sequence, not the
algorithm for generating it.
Thanks!
Phil
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
htt
I have been having problems using WSPR with band hopping. Power output
is set at 200 mw and tune at 2.5 watts. After a while the tune power
will drop to output power or lower, tune does not come on after band
change and may come on during a transmit/receive sequence on one band.
Both remembe
On 04/01/2021 04:15, Peter Sumner wrote:
Hi,
for a while now I have been using a PI 4 for my WSPR activities and
it has always been hit n miss as to whether my spots get to WSPRNET.
In the end it was like 3 months of unsuccessful activity reporting
that forced me to reformat the SD card and u
Hi,
for a while now I have been using a PI 4 for my WSPR activities and it has
always been hit n miss as to whether my spots get to WSPRNET. In the end it
was like 3 months of unsuccessful activity reporting that forced me to
reformat the SD card and update to the BUSTER release of Raspian.. All
Glad to report that the crashes with 2.2.2 when band hopping in WSPR seems
to be fixed in 2.3.0-rc2
dave
k2lyv
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Hi,
I am attempting a WSPR decoder on a single board computer using its
analog to digital converter for sampling. It won't be able to do 12,000
samples per second. Looking a /wsprd/ I see it reduces the /wav/ file by
a large factor. It also looks like the /C2/ processing only use 375
complex
Hi Jason,
the source encoding of the transmitter power in WSPR messages is
complex. As far as I can see the message type is interleaved with the
dBm power value, this was probably done when type 2 and type 3 WSPR
messages were introduced to support compound callsigns and 6-digit grid
squares.
Thanks Bill, that was my reading of it as well, but since the dropdown box
in WSJT-X had those smaller values, I wasn't sure if I was missing
something. I am still curious why those values were inserted if there is no
plan to implement them. If the devs have any further information about
this, I'd
On 08/10/2019 16:50, Jason Milldrum wrote:
So my question then is whether there is any support for power levels
below 0 dBm in the actual WSPR payload yet?
Hi Jason,
the source encoding of WSPR messages restricts the power value p to 0 <=
p <= 60 dBm. There is no space in the payload to store
First off, my apologies if this is not the right place for this question or
if this has been answered already. I searched the listserv archives for an
answer but couldn't find anything.
At some point, WSPR mode in WSJT-X added power levels from -30 dBm to -3
dBm. I recently had a request to add th
On 1/24/19 6:44 AM, Bill Somerville wrote:
> I am fairly confident that given a mode that might have the sensitivity
> of WSPR-15, on LF bands, with similar or less bandwidth and similar T/R
> period to WSPR-2, users would consider upgrading their transmitters for
> the necessary frequency stabi
On 24/01/2019 11:00, N1BUG wrote:
On 1/24/19 5:41 AM, Bill Somerville wrote:
On the new lower LF bands a decoder can take advantage of the far more
stable propagation than is found on the higher short-wave bands.
Coherence across significant periods of time allows assumptions that
frequency and
On 1/24/19 5:41 AM, Bill Somerville wrote:
> On the new lower LF bands a decoder can take advantage of the far more
> stable propagation than is found on the higher short-wave bands.
> Coherence across significant periods of time allows assumptions that
> frequency and phase of a signal are esse
On 24/01/2019 10:29, N1BUG wrote:
I want to inquire one more time about WSPR-15. Is this mode finally
declared forever abandoned or is there still some hope it will find
its way into WSJT-X?
Hi Paul,
there has been some work on a WSPR-LF mode that should perform at least
as well as WSPR-15, o
I want to inquire one more time about WSPR-15. Is this mode finally
declared forever abandoned or is there still some hope it will find
its way into WSJT-X?
I must emphasize WSPR-15 is the miracle beacon and propagation study
mode for LF, where it is still used every day. As one example:
recently
I used to be able to click on the 'Schedule' button and see the schedule. But
a few days ago I changed the schedule slightly and now the 'Schedule' button
does nothing, whether or not the 'Band Hopping' checkbox is ticked.
However, it is still scheduling receives. But it doesn't transmit in thi
The only thing noted here, other than CQ every sequence, was that if you
forget to uncheck 'hound' and move to WSPR, the Enable TX shuts off
immediately after a decode cycle.
N4AU/Bobby
--
Bobby Chandler
bob...@bellsouth.net
n...@arrl.net
---
WSPR mode, Menus OFF/ON:
When the menu is turned off and turned on again, Band Activity and Rx Frequenc
y are displayed.
JH3XCU - Hideo.
--
Check out the vibrant tech community on one of the world's most
engaging tech s
Somehow this guy ended up with mode "WSPR-2" in his INI file (from an earlier
version 1.6.0 perhaps?).It causes wsjtx to crash since m_TRperiod never gets
set in widegraph.cpp and is basically a random value.
Should WSPR-2 be mapped to WSPR mode if seen? All the "if" checks elsewhere
don't see
On 08/12/17 15:04, David Tiller wrote:
Barry,
I think it's operating as designed. From the manual at
http://physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-1.8.0.html#WSPR
"If you will be transmitting as well as receiving, select a suitable
value for *Tx Pct* (average percentage of
__
From: Barry Jackson
Sent: Friday, December 8, 2017 9:55 AM
To: WSJT software development
Subject: [wsjt-devel] wspr transmit periods random
Hi all,
I have been testing WSPR in wsjtx-1.8.0 and despite having TX Pct 33%
transmissions are apparently random.
I am seeing TX periods separat
Hi all,
I have been testing WSPR in wsjtx-1.8.0 and despite having TX Pct 33%
transmissions are apparently random.
I am seeing TX periods separated by 1,2,3 and even 5 consecutive periods
of RX. I was not in the room so was not interfering with anything.
Cheers,
Barry
G4MKT
Sample:
1432
- Original Message -
> Hi,
>
> two more problems which have been spotted during the WSJT-X package
> Fedora review [1] and I think it's worth to report upstream:
>
> - GUIcontrols.txt, prefixes.txt, wsjtx_changelog.txt all have CR + LF
> line endings
> - jt9 binary has executable stack
On 03/09/2017 11:24, Richard Lamont wrote:
That reminds me. When running (r8067 under Ubuntu MATE 16.04) there
seems to be a second process called jt9. Is this right? I haven't used
the mode jt9 for over two months.
Hi Richard,
yes that is correct. The name of the executable is confusing, I be
On 03/09/17 10:54, Jaroslav Skarvada wrote:
> two more problems which have been spotted during the WSJT-X package
> Fedora review [1] and I think it's worth to report upstream:
>
> - jt9 binary has executable stack
That reminds me. When running (r8067 under Ubuntu MATE 16.04) there
seems to be a
Hi,
two more problems which have been spotted during the WSJT-X package
Fedora review [1] and I think it's worth to report upstream:
- GUIcontrols.txt, prefixes.txt, wsjtx_changelog.txt all have CR + LF
line endings
- jt9 binary has executable stack
73! Jaroslav, OK2JRQ
[1] https://bugzilla.red
FYI, WSJT-X Fedora review request:
https://bugzilla.redhat.com/show_bug.cgi?id=1487776
I am attaching patch which I had to use. I think it could be beneficial
for other distros as well, so please consider it's inclusion upstream
(it shouldn't break the current behavior), it does the following:
-
RR, good idea! -- Joe, K1JT
On 8/31/2017 7:31 PM, Jaroslav Skarvada wrote:
Hi Joe,
thanks for info. I have WSJT-X packaging on my todo list, but I didn't know
that it completely superseded WSPR-X. But no problem, I will probaly close
the WSPR-X inclusion request and will open new one for WSJT-
Hi Joe,
thanks for info. I have WSJT-X packaging on my todo list, but I didn't know
that it completely superseded WSPR-X. But no problem, I will probaly close
the WSPR-X inclusion request and will open new one for WSJT-X
73! Jaroslav, OK2JRQ
- Original Message -
> Hi Jaroslav,
>
> Tha
Hi Jaroslav,
Thanks for your email. I wish I could have saved you the effort already
put into this task, because I do not recommend packaging WSPR-X for any
platform or distribution. WSPR-X is obsolete, and no longer supported.
Its functions are limited, and anyway now much better served by
Hi,
I am trying to get WSPR-X into Fedora [1].
During the packaging I have found few issues:
- I had to apply the attached patch in order to compile the
code under Fedora, otherwise it wanted to link with the palir-02.dll
- in the SVN few source files had executable permission set
- files in S
loyd Kirk<mailto:ll...@gcis.biz>
Sent: Monday, July 10, 2017 3:07 PM
To: wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>
Subject: [wsjt-devel] WSPR frequency on 80 meters
I might have missed it somewhere but all my newer wsjtx builds now have
3.5726 as the ws
On 10/07/2017 07:06, Lloyd Kirk wrote:
I might have missed it somewhere but all my newer wsjtx builds now
have 3.5726 as the wspr frequency.
It was and (still being used) 3.5926 I do not know when it was changed.
Lloyd Kirk
WB5HUP
Hi Lloyd,
you did indeed miss the messages. When we switch th
On 10/07/17 07:06, Lloyd Kirk wrote:
> I might have missed it somewhere but all my newer wsjtx builds now have
> 3.5726 as the wspr frequency.
> It was and (still being used) 3.5926 I do not know when it was changed.
On July 6, 2017 Bill G4WJS posted to this list in the thread "WSJT-X:
Working fre
I might have missed it somewhere but all my newer wsjtx builds now have
3.5726 as the wspr frequency.
It was and (still being used) 3.5926 I do not know when it was changed.
Lloyd Kirk
WB5HUP
--
Check out the vibrant te
I have just returned from a month of hiking through CT and EA1 lands
Upon my return, I fired up the computer, rebuilt the latest wsjtx from
source, and launched it. I did not notice that the WSPR transmit frequency
had changed from my normal 1440 Hz to 1635 Hz. The latter is outside the
norm
On 10/17/2016 10:03, Black Michael wrote:
> Sent this to the list but didn't see it show up the archive. Perhaps
> the HTML is messing things up so trying this again.
> Seems like a lot of my posts with patches are not showing up or at least
> nobody is replying about them.
>
> de Mike W9MDB
It w
N0AN reported problems with using tuning with WSPR hopping. I've confirmed
some bad behavior.
First off, he (and I) believe one should tune on Rx-only also. So this small
patch enables that so any band change causes tuning (or should)
Should this be another option?
Index: WSPRBandHopping.cpp
=
When band hopping in WSPR can we please have receive and transmit levels
remembered for each band.
When scanning between 40 to 10 meters the noise levels can very great
and my radio does not have a memory for each band.
Thank you everyone who help in this fine effort.
John
TI4/N0URE
--
version running thru the weekend .
Best regards and have a very good day .
Jean Louis F5DJL
-Message d'origine-
De : Steven Franke [mailto:s.j.fra...@icloud.com]
Envoyé : jeudi 18 août 2016 01:35
À : Joe Taylor
Objet : Re: [wsjt-devel] WSPR-2 Question about difference of rep
>> De : Bill Somerville [mailto:g4...@classdesign.com]
>> Envoyé : jeudi 18 août 2016 00:35
>> À : wsjt-devel@lists.sourceforge.net
>> Objet : Re: [wsjt-devel] WSPR-2 Question about difference of reported
>> frequencies between version 1.6 and 1.7
>>
>&g
point me to the obvious !
>
> Best regards
>
> Jean Louis F5DJL
>
> De : Bill Somerville [mailto:g4...@classdesign.com]
> Envoyé : jeudi 18 août 2016 00:35
> À : wsjt-devel@lists.sourceforge.net
> Objet : Re: [wsjt-devel] WSPR-2 Question about difference of reported
obvious !
Best regards
Jean Louis F5DJL
De : Bill Somerville [mailto:g4...@classdesign.com]
Envoyé : jeudi 18 août 2016 00:35
À : wsjt-devel@lists.sourceforge.net
Objet : Re: [wsjt-devel] WSPR-2 Question about difference of reported
frequencies between version 1.6 and 1.7
On 17/08
On 17/08/2016 23:28, f5djl wrote:
Clearly from the list below of RX reported frequency , they are
suspicious from 10 m to 23 cm : ie 1296.501465 is reported instead
of the expected 1296.501500 .
1296.501465
Hi Jean Louis & all,
that error is within the bounds of a single precision flo
--
De : Steven Franke [mailto:s.j.fra...@icloud.com]
Envoyé : dimanche 14 août 2016 19:27
À : Joe Taylor
Objet : Re: [wsjt-devel] WSPR-2 Question about difference of reported
frequencies between version 1.6 and 1.7
Hi Jean Louis,
I did a couple of experiments here to see if I could reproduc
ranke [mailto:s.j.fra...@icloud.com]
Envoyé : dimanche 14 août 2016 19:27
À : Joe Taylor
Objet : Re: [wsjt-devel] WSPR-2 Question about difference of reported
frequencies between version 1.6 and 1.7
Hi Jean Louis,
I did a couple of experiments here to see if I could reproduce the results
desc
Hi Jean Louis,
I did a couple of experiments here to see if I could reproduce the results
described in your item 1.
1. I transmitted a WSPR signal using WSJT-X 1.7 r7032 using my GPSDO-referenced
TS-480 and received that signal using my Gnuradio/USRP1 SDR which is referenced
to the same GPSDO
Hi Guys,
The excellent updates to the WSPR-X decoder over the last few months certainly
produce more spots but there could be more!
It is a well known fact that WSPR-X is more time sensitive at signal end rather
than signal start.
If you live in an area populated by many hams you probably do no
Hi All,
further to this thread on WSPR spotting I have just made a change that
deals with spots not being sent after a period of network
inaccessibility, for example losing a WiFi connection for a period of
time. The Qt service we use for all network traffic does not recover
automatically from
t;KI7MT"
> To: wsjt-devel@lists.sourceforge.net
> Sent: Monday, February 8, 2016 12:34:10 PM
> Subject: Re: [wsjt-devel] WSPR SegFault on Decode
>
> Hi Russ,
>
> There is no pressing need to use JTSDK to build WSJT, WSPR or WSJT-X on
> Linux. All of the apps can
the map. Thanks for
the help.
73, Russ - K5TUX
- Original Message -
From: "KI7MT"
To: wsjt-devel@lists.sourceforge.net
Sent: Monday, February 8, 2016 12:34:10 PM
Subject: Re: [wsjt-devel] WSPR SegFault on Decode
Hi Russ,
There is no pressing need to use JTSDK to build
uot;KI7MT"
> To: wsjt-devel@lists.sourceforge.net
> Sent: Monday, February 8, 2016 11:01:58 AM
> Subject: Re: [wsjt-devel] WSPR SegFault on Decode
>
> Hi Russ,
>
> I'm assuming you are comping from source here. How did you install the
> build and runtime pac
ss - K5TUX
- Original Message -
From: "KI7MT"
To: wsjt-devel@lists.sourceforge.net
Sent: Monday, February 8, 2016 11:01:58 AM
Subject: Re: [wsjt-devel] WSPR SegFault on Decode
Hi Russ,
I'm assuming you are comping from source here. How did you install the
build and run
Hi Russ,
I'm assuming you are comping from source here. How did you install the
build and runtime package dependencies for WSPR?
73's
Greg
On 02/08/2016 08:55 AM, Russ Woodman wrote:
> Hi,
>
> Just built WSPR 4.0r6470 from the SVN on my Linux machine running Debian
> Jessie. I can start the
Hi,
Just built WSPR 4.0r6470 from the SVN on my Linux machine running Debian
Jessie. I can start the application and configure it with no problems. Rig
control is working. During the receive cycle, WSPR operates correctly. When it
goes to decode the received data, it segfaults. Here is what I
Hi Bill,
Point taken on the server load issue. I would think the server
administrator(s) would load balance inbound requests, but that is their
call.
I was thinking more along the lines of remote operations where
networking is not available at all or when one needs to connect via
Satlinks for sho
On 02/02/2016 17:58, KI7MT wrote:
> Having the ability to cache / store decodes offline then resume
> uploading when networking / wsprnet.org is available or on demand
> uploads would be a nice feature.
Hi Greg,
I'm not sure it is all that desirable, if the server is off line for an
extended peri
Hi Bill,
FWIW, the original WSPR application has the same problem. If wsprnet.org
is down or networking fails for whatever reason, the spots are not
cached; essentially it is a one shot deal, either they get posted or the
decodes are lost.
There are a few comments in the original source code ment
On 02/02/2016 00:26, Bill Somerville wrote:
> I will look into it tomorrow when I can get some
> time in the shack.
Hi Eric,
having spent a few hours monitoring WSPR traffic I think WSJT-X is
mostly working as expected. I believe what you were seeing is in
response to the wsprnet.org server not
On 02/02/2016 01:12, Eric NO3M wrote:
> Just a heads up. Not sure how reproduce-able it will be; last hour or
> so multiple spots are going through fine. I originally thought it may
> have been an issue on wsprnet's side due to all the recent problems
> there, but decided to run tcpdump and saw t
Just a heads up. Not sure how reproduce-able it will be; last hour or
so multiple spots are going through fine. I originally thought it may
have been an issue on wsprnet's side due to all the recent problems
there, but decided to run tcpdump and saw that not all the spots where
getting sent.
On 01/02/2016 23:26, Eric NO3M wrote:
> Sniffing the traffic sent to wsprnet.org using tcpdump confirms that
> only one spot is sent during a cycle (or in the case of 2316z, two made
> it out).
Hi Eric,
thanks for the report. I will look into it tomorrow when I can get some
time in the shack. The
Not sure if this has been brought up previously...
Only the first of several WSPR decodes are being reported, see data below:
WSJT-X v1.7.0-devel r6447:
2304 -2 -0.20.4756100 WG2XIQEM12 37 1122
23047 -1.00.4757220 WG2XKAFN33 30386
2306
KF2T wrote:
> Happy Christmas, Joe...
>
> After a longer stare at the waterfall, the lower traces appear
> not to be WSPR-2. They look a lot like it, but keep on going much
> longer. Perhaps I haven't been as attentive as I should have been!
Indeed, the signals just below the 30m WSPR band are fro
Happy Christmas, Joe...
After a longer stare at the waterfall, the lower traces appear not to be
WSPR-2. They look a lot like it, but keep on going much longer. Perhaps I
haven't been as attentive as I should have been!
George J. Molnar
@GJMolnar
> On Dec 25, 2015, at 11:20 AM, Joe Taylor wro
Testing 1.7 (6298, Mac OSX) and note a small possible error. On 30m WSPR,
decodes are shown on what appears to be the correct frequency (10140.2 or so),
but the waterfall display paints them about 200 Hz low, outside of the WSPR
safe area marker.
Geo/KF2T
George J. Molnar
@GJMolnar
Hi John,
Looks fine to me. Only thing I know of that's planed for the WSPR branch
is updating the docs, and fixes like what you've provided here.
73's
Greg, KI7MT
On 11/28/2015 08:26, John Nelson wrote:
> Hi Greg,
>
> I've gone back to work on wspr-v4.0 for Mac OSX. There are a couple of
> c
Hi John,
Looks fine to me. Only thing I know of that's planed for the WSPR branch
is updating the docs, and fixes like what you've provided here.
73's
Greg, KI7MT
On 11/28/2015 08:26, John Nelson wrote:
> Hi Greg,
>
> I've gone back to work on wspr-v4.0 for Mac OSX. There are a couple of
> c
Hi Greg,
I've gone back to work on wspr-v4.0 for Mac OSX. There are a couple of
corrections that need to be made to configure.ac in areas specific to OSX:
Could you look at these please. I won't commit while work seems to be ongoing
in this repo.
--- John G4KLA
--- configure.ac(re
Hi Bill and all,
FYI, related to minor thread "Redundant Information in the WSPR Receive
Window" a few minutes ago: with r6149 I have made the necessary change
in the v1.6.0 branch to correct this unwanted behavior.
-- Joe, K1JT
-
Hi Joe and Richard -
>> Up to now WSPR-15 has not been implemented in any version of WSJT-X. If
>> there is sufficient interest, this capability could be added to some future
>> release.
For what it’s worth, I believe that the current wsprd will work with wspr-15
files. I made those changes
On Fri, 20 Nov 2015 11:52:10 -0500
Joe Taylor wrote:
> Up to now WSPR-15 has not been implemented in any version of WSJT-X. If
> there is sufficient interest, this capability could be added to some
> future release.
>
> -- Joe, K1JT
Hi Joe
apparently its quite popular on the LF bands
1 - 100 of 435 matches
Mail list logo
