Hi Glenn,
You might like the FST4 QSO mode. Same operating procedure as FT8, but
depending on cycle length it can decode below -30 dB.
It is mostly used on 630m but I also had (transatlantic) contacts on 160m.
https://wsjt.sourceforge.io/FST4_Quick_Start.pdf
73
Stefan
On 07.12.23 16:46,
Yes, for WSPR/FST4W signal reports are essential.
For FT8 etc. it probably doesn't matter much, but that was not the topic.
73
Stefan
On 01.12.23 13:33, Black Michael via wsjt-devel wrote:
And does anybody even look at that data anyways?
___
I would also prefer if the strongest signal would be uploaded.
73
Stefan
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Hi,
Every few weeks there is someone in the WSPR facebook groups or support
forums looking for help because their callsign appears to be used by
someone else.
This is usually the result of a hash collision and it's pretty
cumbersome to fix, because we have to find and contact the original
On 02.06.23 07:03, Peter Sumner via wsjt-devel wrote:
A reboot of the PI brings things back to life for a period of time
(seems to vary) but in the end my status and spot on WSPRnet stop appearing.
Looking to see if anyone has come across anything similar or any good
pointers on what might be
Hi,
cmake generated an error:
CMake Error at CMakeLists.txt:56 (file):
file failed to open for reading (No such file or directory):
~/bin/wsjtx-2.6.0/src/hamlib-4.5.tar.gz.md5sum
I think CMakeLists.txt should be:
6c6
< set (__hamlib_upstream hamlib-4.5.3)
---
> set (__hamlib_upstream
I missed that. Thanks!
73
Stefan
On 30.11.22 20:45, Steven Franke via wsjt-devel wrote:
Stefan,
Please see the Release_Notes.txt for 2.6.0-RC5. The second item is as follows:
- Upload FST4W-900 spots to wsprnet with TR code 15 instead of 16.
I believe that this addresses your request.
Hi Mike
Thanks for posting it on the wsprnet forum.
It seems that no one there could help with that either.
So it would be good if it could be changed in WSJT-X before the final
release of 2.6.0.
73
Stefan
On 23.11.22 14:03, Black Michael via wsjt-devel wrote:
This was covered in the
Hi,
When WSPR and FST4W spots are uploaded to wsprnet, there is an
additional field to designate the mode.
From wsjtx/Network/wsprnet.ccp lines 274 to 288
it was intended to use different mode IDs for WSPR and FST4W in order to
distinguish between the two modes in the wsprnet database.
Hi Marco & group
On 19.10.21 20:00, Marco Calistri via wsjt-devel wrote:
My doubt now is that same issue could happens to others colleagues which
are using WSJT-X for Linux, for this reason I would like to have some
feedback on this topic.
I have the same issue and had reported it a few
On 14.08.21 00:36, Phil Karn via wsjt-devel wrote:
>
> Has anyone seen a collision in practice?
There was a hash collision between KB8OIS and VK3KCX (Hash 17637):
https://wsprnet.org/drupal/node/8466
And between WX4BK and OZ0RF (Hash 3245):
https://wsprnet.org/drupal/node/8014
73
Stefan
On 07.08.21 10:08, John Nelson via wsjt-devel wrote:
Yes, because IPs in this range are on a blacklist because of spf problems:
dnsbl.spfbl.net
That's not an issue. Half of the internet is on that list. This list is
only used for mailservers to block dynamic ip addresses.
"This IP has
12 matches
Mail list logo
