Greetings, 

I am looking for detailed instructions to add my receiver to the list of servers. I have also checked YouTube but only find how to access radios already on the list.

I would appreciate help in getting started with adding my receiver to the server list.

Thanks, 
George 

Here's a 'new' version of "How to make an SDRC Server"... a step by step, with images procedure. If the images are not here, go to the web gui and read/see them there!

1)  A computer that will be running 24/7 is needed for the SDRC Server to function. Old laptops are handy due to low power consumption and with a battery, they can handle brief power outages without having to be restarted. Since the minimum specifications are very low, I use older Windows 7 Netbooks that only have an Atom processor! This computer MUST have a static IP, otherwise it may change with every power reset. This is done using Windows Network and Internet Settings. Google how to do this for Windows 7 or Windows 10.

2) One must open a port in your ISP's router to allow TCP traffic from outside (WAN)  to the computer hosting the server that now has a static IP assigned. This varies WIDELY from ISP and mfg of specific routers. Google can help you there by specifying the exact model.

3) Start the SDRC Server Manager and you will see the following:



4) Lets start with the "Accounts" tab. Outside users will use an account appropriately named "Guest" in this example. A password is
needed and it does NOT have to be complicated and it automatically gets transferred when a user builds server definitions anyways.
I just happen to use the same one from v1.5 so many years ago. Be sure to place a 'Time Limit' and 'Interval Between' time to limit
server hogs and allow other users to access it. You can also add your own private account (longer times, no interval between) as to access
the server while out on the road (WAN) or while within your network (LAN). Since my servers are mostly out in the repeater shed or barn,
I access them via remotely 99% of the time. When done hit OK



5) Next hit the Radios Tab and make a radio definition providing the SDR is connected and previously working 100% via SDRC.
Process is similar to building definitions in SDRC, use the "Search" button for USB connected SDR's such as Airspy and SDRPlay.



6) When SDR is found hit "Add", if you have more than one SDR to make available, repeat the Search step, but do NOT hit "Replace", hit "Add"!



7) When done with radio definitions, hit "Save"




8) Skip "Firewall", this is where you can 'Whitelist" or "Blacklist" IP addresses. Not needed unless you have
a user that abuses your server.

9) Open the "Network" tab and there's plenty to set here!
        A) You want to place the port you opened in the router and is forwarding TCP packets to the server computer. 
        B) Open the port in Windows Firewall by pressing "Add Port"
        C) Turn on compression and set the max bandwidths for LAN users (you via a computer w/in your network) and WAN users (Internet users). The WAN setting may have to be adjusted
             to your ISP's upload bandwidth. Try running a speed test from a web browser and see how much upload capability you have and adjust the WAN bandwidth accordingly. The HF Airspy's                 are either 768 or 912 kBs so 1MHz bandwidth will allow external users the limit of the SDR.
        D) Users can be either 1, 2, or how many SDR's are available. This is limit of how many incoming connections from the same IP address. I have mine set for two so folks can do an A/B test                 to compare SDR mfgs or antennas that may be connected to the various SDR's.



10) The "Welcome Tab" is what's displayed when users click on "Server Options", "Server". Here is where you can describe the
       station setup so users know what they are using. An email address is handy for comments and issues with the server too!





11) Next is the "On Air" tab
     A) Place the exact name and password used in the 'Accounts' tab for guest users or guest will have to ask you for them. These are exchanged automatically with the remote users when 
          they build definitions.
     B) Do NOT change the data in the red box, that data is how your server talks to Simon's server to show your server is on the air.
     C) Give the station a useful, unique name such as your call sign. This helps when the server is locked up and somebody can email you to alert you via what you have in QRZ.com or                            elsewhere.
     D) IP Address can be left if you have a static public IP address. Mine changes every month, so I use a free DYDNS service that resolves my public IP address. Not sure if the default setting                (blank) will update with every IP change, so I just use the free service.
     E) Antenna, Location and comments are viewable to users when building definitions. VERY handy if, for example, I want to use an HF server that has a 'real' HF antenna and not an indoor                  piece of wire. It's painful when you build a definition, only to find out that it's VHF/UHF only when you wanted HF or visa versa.
     F) When done, hit "Save"!




12) The Service Tab is last:
      A) BEFORE using as a server, ask yourself if this computer is going to be permanently used as a server, if so, keep the 'Start Type' default which starts the server (A Windows Service that runs in the background!) every time the computer is turned on. If it's not checked, one must run the Server Manager to start every time. Herein lies the problem, users experiment with the Server Manager, then give up. In the background, the Windows service is running (can see it via task manager)... constantly pinging Simon's server saying I'm here, but in reality there's a router port not open, Windows firewall port not open, the IP address of the server computer has changed, etc. Those are the servers listed with the yellow triangles with an exclamation point inside on the list of servers. So, if the installation is permanent, leave it checked. If the computer is going to be purposed for some other task, remember to uncheck it and use the "Remove" service button!





13) When the install button is hit, the server will start sending data every 30 seconds to alert Simon's server and allow external users to 'see' it. After 30 seconds, if all goes well,
       you should see the following under the "On Air" tab:



14) You can monitor your server's activity via the following link, and also get an idea of where activity is. Only the center frequency and bandwidth is available, but maybe soon the actual frequency in use will be made public?
Bookmark the following, severs are listed in alphabetical order:
http://onairv3.sdrspace.com/onair-v3.xml

Here's the 'Theoretical' server I just built:




73 Kriss KA1GJU
Home of the Super Station SDRC Servers in NH, USA (FN2mw)

Nice work, Kriss!

Thank you.

Thanks Kriss!

This is something I need to get around to doing. So far I haven't found a 'round 2 it' of time yet. When I'm ready, I will reread your little mini-lesson.

Dave Aichelman     N7NZH     Grants Pass, Oregon

If you operate nearby, either get a receiver front end protector or install a relay to disconnect antenna during TX or when personal rig is powered up. I use both methods or non at all if there
is plenty of distance between the TX and RX antennas. Server #2 have the receiver front end protector, server #4 has the relays, and #1 and #3 have no protection due to being +300' away.

I steal power from the auto tuner port, so when a user uses one of my remote HF TXR's or my own personal use HF rigs, the sensitive SDR's are protected. Here a crude Windows Paint drawing 
of Server #4's protection:



73 Kriss KA1GJU

I use these, but they have been out of stock for months, and price just went up:

https://www.arraysolutions.com/surge-and-rf-protection/as-rxfep

But here’s another option:

http://www.crosscountrywireless.net/receiver_protection_unit.htm

Lastly…

https://www.dxengineering.com/parts/dxe-rg5000hd?seid=dxese1&gclid=Cj0KCQiApL2QBhC8ARIsAGMm-KFmle7UJ_2ShFI37dOtIt6S7T9g2edk-OOsrdtqGrx1UPuPoVc_BR0aAm4_EALw_wcB


73 Kriss KA1GJU 

Thanks Kriss,
All great options,

Thought i would mention 2 that I use:

If you are ok with the Freq range (10 M or higher), then this is a great (and cheap $4.95 ) option from eBay. It is pin diode based, like most of these
10M-6GHz 0dBm SMA PIN Diode RF Limiter Radio Frequency Limiter Amplitude limiter
https://www.ebay.com/itm/312623587269

A more recognizable name, mini-circuits also has a great option (inline SMA): great for HF/VHF not so much UHF
Mini-Circuits VLM-33-S+30-3000MHz SMA RF Coaxial Power Limiter 15542
They regularly come up on eBay for $25 or so, but beware there are several listed at much higher prices, so be patient (put a ebay saved search on the model number and eventually it will hit at the right price)

73 de k1jbd
bammi

Kriss:

At least in my view on two different browsers (Chrome and Firefox) somehow your images that were available last week aren't visible now in this thread.

Hello Curt,
   Yes... I think it's a limitation on how much GB of stored space on the groups.io site. Our local radio club has the same problem. We have to thin out the images/videos posted or get capped at XX GB of storage. Maybe Simon culls the herd or Groups.io does it automatically?
I'll try and find which computer sent the images and try an upload to files section. Grrrrr

73 Kriss KA1GJU