Thank You

Joe Muchnij

If you want to go to the N8GA KiwiSDRs directly, you can do:

http://hill.n8ga.org:8073

(note that "https:" won't work)

Each of the three Kiwis can have up to 8 users at a time.  However, only
the first two users on each one get the full spectrum waterfall display.
Additional users have all the features of the receiver, but they only
get an audio spectrum display.

If you connect to the first Kiwi and it's full, you'll be automatically
redirected to the second, and if that's full, to the third.  If you get
the audio-only display, you can go directly to the second Kiwi by
changing the end of the URL above from "8073" to "8074", or the third by
changing it to "8075".

Depending on how busy things get, I may put timeouts on one or more of
the receivers to keep people from sitting there all day while inactive.
If I do, there will be a password available for friends and family to
bypass that.

We currently have a bad noise problem in the LF/MF frequency range, and
a less-bad one up around 25 - 30 MHz.  I'm going to be troubleshooting
those.  The low frequency one is new, so hopefully it will be easy to
isolate.

73,
John

On 2/23/24 22:30, Jim Bacher, WB8VSU via mvus-list wrote:

I have found SDRs to be a great tool to have in your pocket. At my location I suffer from extreme power line noise on HF. Especially on 75 meters. I use one of two SDRs in Pennsylvania when I check in to the OSSBN. However.... there is a huge caveat when using them. Latency. Depending on the site you connect to there is a one to five second delay from real time. That one second delay can be a deal breaker in a contest. On the OSSBN I have to anticipate when the net control is going to stop transmitting ahead of time and key up my transmitter (at home. I can transmit just fine. I can't HEAR anything). The longer the delay, the tougher it will be to make that contact in a contest. It's tough enough to deal with in a traffic net, but in a contest? That latency might be the difference in making or not making that contact. Keep that in mind when you connect to one.

Sam N8VES

On Saturday, February 24, 2024 at 10:53:55 AM EST, John Ackermann N8UR via mvus-list <mvus-list@lists.febo.com> wrote:  

If you want to go to the N8GA KiwiSDRs directly, you can do:

http://hill.n8ga.org:8073

(note that "https:" won't work)

Each of the three Kiwis can have up to 8 users at a time.  However, only
the first two users on each one get the full spectrum waterfall display.
  Additional users have all the features of the receiver, but they only
get an audio spectrum display.

If you connect to the first Kiwi and it's full, you'll be automatically
redirected to the second, and if that's full, to the third.  If you get
the audio-only display, you can go directly to the second Kiwi by
changing the end of the URL above from "8073" to "8074", or the third by
changing it to "8075".

Depending on how busy things get, I may put timeouts on one or more of
the receivers to keep people from sitting there all day while inactive.
If I do, there will be a password available for friends and family to
bypass that.

We currently have a bad noise problem in the LF/MF frequency range, and
a less-bad one up around 25 - 30 MHz.  I'm going to be troubleshooting
those.  The low frequency one is new, so hopefully it will be easy to
isolate.

73,
John

On 2/23/24 22:30, Jim Bacher, WB8VSU via mvus-list wrote:

mvus-list mailing list -- mvus-list@lists.febo.com
To unsubscribe send an email to mvus-list-leave@lists.febo.com

Hi Sam --

Yes, the latency is a possible problem.  There's a built-in latency in
the signal processing of the radio/computer but at least that's pretty
constant.  The network delays though can vary all over the place.

The KiwiSDR system supports a Time Delay of Arrival mechanism where a
user can log into multiple Kiwis at different locations and use the time
differences for direction finding.  The Kiwis have a GPS so have good
time sync, and there must be same way they can transmit timestamps to
allow that comparison to work despite the varying network delays.

73,
John

On 2/26/24 07:28, Andrew Anderson wrote: