Date   

Re: URL for Spots history

Jim Lill
 

as a backup, there's always my site jimlill.com:8088

On 5/15/21 10:47 AM, Edward Hammond wrote:

As far as I know, there's really nothing even close to as good as http://wspr.rocks  ... except I suppose wsprd.vk7jj.com.  :-)

It's fantastic, and having a really handsome and functional site like that adds loads of interest, for me at least, in the WSPR hobby. 

My thanks and congratulations to those responsible.

Edward

W3ENR


On 5/15/21 10:30 AM, Rob Robinett wrote:
The bands are fine
My preferred search:  http://wspr.rocks/

On Sat, May 15, 2021 at 6:57 AM John via groups.io <n0ure=yahoo.com@groups.io> wrote:
What are the URLs for WSPR history? Are the bands dead? I have no spots.

John


--
Rob Robinett
AI6VN
mobile: +1 650 218 8896


Re: URL for Spots history

Edward Hammond
 

As far as I know, there's really nothing even close to as good as http://wspr.rocks  ... except I suppose wsprd.vk7jj.com.  :-)

It's fantastic, and having a really handsome and functional site like that adds loads of interest, for me at least, in the WSPR hobby. 

My thanks and congratulations to those responsible.

Edward

W3ENR


On 5/15/21 10:30 AM, Rob Robinett wrote:
The bands are fine
My preferred search:  http://wspr.rocks/

On Sat, May 15, 2021 at 6:57 AM John via groups.io <n0ure=yahoo.com@groups.io> wrote:
What are the URLs for WSPR history? Are the bands dead? I have no spots.

John


--
Rob Robinett
AI6VN
mobile: +1 650 218 8896


Re: URL for Spots history

Glenn Elmore
 


http://wspr.rocks/ looks fairly normal to me.
What kind of history are you after?

On 5/15/21 7:57 AM, John via groups.io wrote:
What are the URLs for WSPR history? Are the bands dead? I have no spots.

John


Re: URL for Spots history

Rob Robinett
 

The bands are fine
My preferred search:  http://wspr.rocks/

On Sat, May 15, 2021 at 6:57 AM John via groups.io <n0ure=yahoo.com@groups.io> wrote:
What are the URLs for WSPR history? Are the bands dead? I have no spots.

John



--
Rob Robinett
AI6VN
mobile: +1 650 218 8896


URL for Spots history

John
 

What are the URLs for WSPR history? Are the bands dead? I have no spots.

John


Re: Prefix/suffix call signs TX messages (Type 2) don't make it to WSPRnet.org, any solution for this?

Gwyn Griffiths
 

Harry

I am not sure exactly what is not right in your case, but I have checked the spots that Rob's scraper takes from wsprnet.org for the last ten days and there are many examples of transmit callsigns with prefixes and suffixes. For example:

DF4PV/M, DJ2WW/P, EA8/OK2SAM, G0SZI/A, GM4SJB/2, HR9/WA4DT, MM/M0VIK, SM7PNV/2, TA4/G8SCU, W5/VK2ARH, W6LVP/V, W7GDK/7, ZS3D/N

including, I see, your own call as SM7PNV/2.

In your email you wrote "SM7PNV/p", was the lower case p a typo? 
Your example "OZ1/SM7PNV" is exactly the same character count and distribution either side of the / as EA8/OK2SAM which is in the database.

So, I do not think there is a general problem, but I cannot see what you are missing in generating your own Type 2 messages. Sorry.

73
Gwyn G3ZIL


Re: Prefix/suffix call signs TX messages (Type 2) don't make it to WSPRnet.org, any solution for this?

Rob Robinett
 

On Fri, May 14, 2021 at 10:27 AM, Harry Zachrisson - SM7PNV wrote:
SM7PNV
I think there are limits on the number of character+ digits in the type 1 and type 2 message fields in WSPR packets which your callsign/extension may exceed.
There is a good explanation of the WSPR packet format at https://dxplorer.net/wspr/msgtypes.html#:~:text=The%20normal%20WSPR%20message%20%22Type,of%20up%20to%20six%20characters.

For users registered with wsprnet.org, it seems that they use your registered tx/rx 6 character maidenhead location when recording your type 1 messages which contain only the 4 character locator.

The wsprdaemon.org clone of the wsprnet.org spot database makes no modifications of the spots delivered by the wsprnet.org API.  If anyone sees they don't match, then there is a bug I am not aware of.


Prefix/suffix call signs TX messages (Type 2) don't make it to WSPRnet.org, any solution for this?

Harry Zachrisson - SM7PNV
 

I have been generating Type 2 messages but I can't see the prefix or suffix in the data on wsprnet.org.(e.g transmitted SM7PNV/p or OZ1/SM7PNV is shown as SM/PNV) 
I am guessing it is not reported from the WSJT-X client to WSPRnet.
They seem to be intact in pskreporter though.

Anyone that has information around this?
It just seems strange that WSPR has support for it in both the transmit and receive side but it does not show up in the database, or did I miss something?

73
//Harry - SM7PNV


Re: No Space for tmp files

John
 

Rob,
the df looks normal. The OS is at 32%, all the other devices 1-3%.
I will rebuild the OS.

Thanks for all the hard work.
John


Re: No Space for tmp files

Rob Robinett
 

Maybe I misled you.
Start by seeing the state of your file systems by executing 'df'
I would expect that your will see that the /tmp file system is 100% full/;   /tmp/wsprdaemon should be 10-30%% full most of the 2 minute wspr cycle.
/tmp should be cleared by a reboot.
WD doesn't clear the /tmp/wsprdaemon file system.  It does delete old wav files, which would occupy the most space on  /tmp/wsprdaemon. 
I only truncate or clear any log files created when you start WD, so if you run at log levels 1 or greater, eventually the  /tmp/wsprdaemon file system will become 100% full.
Fixing that 'logging fills up  /tmp/wsprdaemon' problem is part of my work on WD V3.0.


On Thu, May 13, 2021 at 6:47 PM John via groups.io <n0ure=yahoo.com@groups.io> wrote:
I did wd -z
rm -rf /tmp/*
I got a list of sum system type files and some with lots of numbers, but many showed bussy.
I did sudo rm -rf /tmp/*
got  cannot remove /tmp/wsprdaemon device or resource bussy.  ( even with the wd -z) ??

I thought that the tmp files were on RAM disk and would go away with a cold restart.

John



--
Rob Robinett
AI6VN
mobile: +1 650 218 8896


Re: No Space for tmp files

John
 

I did wd -z
rm -rf /tmp/*
I got a list of sum system type files and some with lots of numbers, but many showed bussy.
I did sudo rm -rf /tmp/*
got  cannot remove /tmp/wsprdaemon device or resource bussy.  ( even with the wd -z) ??

I thought that the tmp files were on RAM disk and would go away with a cold restart.

John


Re: No Space for tmp files

Rob Robinett
 

Then you need to clean out /tmp which is a separate file system from /tmp/wsprdaemon

WD -z
rm  -rf /tmp/*
WD -a

On Thu, May 13, 2021 at 4:33 PM John via groups.io <n0ure=yahoo.com@groups.io> wrote:
That did not work for me.
the exact error is:
/home/pi/wsprdaemon/wsprdaemon.sh: Line 729: cannot create temp file for here-document: No space left on device
This occurred 15 times after WD -s. I assume there is one for each real channel.
and one more at the bottom for line 3691
I see this when I do WD -s just after WD -a

John



--
Rob Robinett
AI6VN
mobile: +1 650 218 8896


Re: No Space for tmp files

John
 

That did not work for me.
the exact error is:
/home/pi/wsprdaemon/wsprdaemon.sh: Line 729: cannot create temp file for here-document: No space left on device
This occurred 15 times after WD -s. I assume there is one for each real channel.
and one more at the bottom for line 3691
I see this when I do WD -s just after WD -a

John


Re: No Space for tmp files

Rob Robinett
 


Stop WD
EXecute:  rm -rf   /tmp/wsprdaemon/*
Start WD

On Thu, May 13, 2021 at 3:27 PM John via groups.io <n0ure=yahoo.com@groups.io> wrote:
I have messed up and need a pointer to fix my mess.
I left the Tail of the spots.log file running.
Now wsprdaemon is giving errors "..no space for tmp file' at line 729.
What directory on mt Pi 4 can I purge to clear my mess?

John

--
Rob Robinett
AI6VN
mobile: +1 650 218 8896


No Space for tmp files

John
 

I have messed up and need a pointer to fix my mess.
I left the Tail of the spots.log file running.
Now wsprdaemon is giving errors "..no space for tmp file' at line 729.
What directory on mt Pi 4 can I purge to clear my mess?

John


Re: wsprdaemon on Nvidia Jetson Nano

Rob Robinett
 

I'm impressed!
When you are done with OpenAcc I have another SW project I would welcome help on ;=)

On Fri, May 7, 2021 at 3:37 PM John via groups.io <n0ure=yahoo.com@groups.io> wrote:
Wsprdaemon is now running well on the Jetson Nano, about 15% faster than pi 4. I built WSJT-X 2.3.1 from the source then copied the wsprd program to the bin directory.
Next project: apply OpenAcc to wsprd.

John



--
Rob Robinett
AI6VN
mobile: +1 650 218 8896


Re: wsprdaemon on Nvidia Jetson Nano

John
 

Wsprdaemon is now running well on the Jetson Nano, about 15% faster than pi 4. I built WSJT-X 2.3.1 from the source then copied the wsprd program to the bin directory.
Next project: apply OpenAcc to wsprd.

John


WD successfully run on a Chromebook

Glenn Elmore
 

I was recently out in a "quiet place" to make noise floor measurements of my active antenna system.  I did indeed find such a place which could reach the noise floor limitations of my system and propagated noise up to mid-HF.  At the same time I decided to try to spot WSPR on the only computer I had with me, a Chromebook. As you may know the Chromebook is rather "cloud based". It doesn't like to do much of anything off line in a location of the sort I was using. The Chromebook runs Chrome OS but also has a virtual linux machine app available.  This is a command-line-only application with no GUI. However,  I did manage to install Rob's wsprdaemon on it (after manually installing by changing a "." to a "-" in the libfftw library install request) so that it installed OK.  

Because I had no Internet connection at the remote site where I was measuring and I had left the GPS antenna at home, I had to manually adjust the portable Kiwi's clock using a time/frequency station.  That left only the time synchronization  to be set. This turned out to be the hardest  and I finally just set the Chromebook while on the Internet and left it running while I drove to the remote site.  There may be a way to allow the Linux application to set the Chromebook time but I haven't yet found it. The usual 'data ...' method was not allowed.

But the good news is that in a pinch, if stuck with only a Chromebook, wsprdaemon and a Kiwi can successfully spot WSPR and noise data and then once returned to Internet access, load it into the databases.

Glenn n6gn


Re: wsprdaemon on Nvidia Jetson Nano

Rob Robinett
 

WD installs the arm64 version wsprd, but WSJT-x builds that for the Pi.
You will probably need to compile wsprd from sources to get it to run on your nano.

On Sat, May 1, 2021 at 7:05 AM Jim Lill <jim@...> wrote:

the nano uses 64bit-ARMv8.... does wsprd (or wsjtx-x) support that?

On 5/1/21 9:21 AM, John via groups.io wrote:
I never see the wsprd process listed in the TOP display.
I went to the wsprdaemon/bin dir and did a 
wsprdaemon@wsprdaemon-desktop:~/wsprdaemon/bin$ ./wsprd
-bash: ./wsprd: cannot execute binary file: Exec format error
command and got this error.
Did I do this correctly?
Is the correct response?
John



--
Rob Robinett
AI6VN
mobile: +1 650 218 8896


Re: wsprdaemon on Nvidia Jetson Nano

Jim Lill
 

the nano uses 64bit-ARMv8.... does wsprd (or wsjtx-x) support that?

On 5/1/21 9:21 AM, John via groups.io wrote:
I never see the wsprd process listed in the TOP display.
I went to the wsprdaemon/bin dir and did a 
wsprdaemon@wsprdaemon-desktop:~/wsprdaemon/bin$ ./wsprd
-bash: ./wsprd: cannot execute binary file: Exec format error
command and got this error.
Did I do this correctly?
Is the correct response?
John

281 - 300 of 512