Monday, November 16, 2020

Editing the start.sh file for 16-bit Red Pitaya on a Windows Computer

 Bjorn, SM7IUN has brought my attention to a potentially important caveat in editing the start.sh file to activate two entirely separate receivers on an RP-16.

The RP-16 is a Linux device, so the start.sh file must be compatible with Linux.  However, if you edit a Linux file using Windows Notepad, the edited file will come out with <CR><LF> at the end of each line, rather than the Linux standard <LF>.  This, in turn, could result in its no longer working under Linux.  While I have not yet had this problem with my RP-16s, it's worth knowing about.

Fortunately, there is an easy solution - Notepad++.  Written by Don Ho, it is freeware, and senses whether a file selected for editing follows the Linux convention or the Windows and ends lines appropriately.  A worthwhile precaution, I'd say. 

Sunday, November 15, 2020

How to Post Two Receivers' Output to the RBN under Two Different Receiver Names

As outlined in my post a couple of weeks ago, it is not possible, using a single Aggregator, to post spots from the two receivers in an RP-16 to the RBN under separate receiver names.  Fortunately, Dick Williams, W3OA, the author of the Aggregator, has figured out a work-around.  Here's his solution:

1)  Update Aggregator to version 6.2.  Aggregator will now show the name of its executable file in the title bar at the top of its window.  This enables you to determine which Aggregator instance the window refers to.

2) Aggregator was running from C:\Ham Stuff\Aggregator. I created a new folder, C:\Ham Stuff\Aggregator2, and copied Aggregator.exe from the original folder to the new one.  Also copy BADCALLS.txt if you are using that filter.

3) Rename Aggregator.exe in the new folder to Aggregator2.exe.

4) In your first Aggregator instance go to the “Secondary Skimmers” tab, find the line which connects to the second SkimSrv instance, click the “D” button, and uncheck the “Auto Connect?” box.

5) Again in your first Aggregator instance go to the “FT#” tab and uncheck the “Use?” box for each source which receives spots from the “Rig Numbers” on the right half of the FT#StartUp window, i.e SkimSrv2.  Then click the “Apply Changes” button.

6) In your second SkimSrv instance go to the “Operator” tab and update the entries there as necessary.  The callsign should be the SSID you want to use for that Skimmer.  (I used W3OA-2.)

7) Start your second Aggregator instance and go to the “Connections” tab to set the second SkimSrv instance as the “Primary Skimmer Connection” for this Aggregator instance.  While on this tab change the “Local User Port Number” so it's not the same as in the first Aggregator instance.

8) Complete setting up the second Aggregator instance paying particular attention to the “Spot Filters”, “Patt 3Ch.lst”, and “FT#” tabs.  On the “FT#” tab add the sources you disabled in the first Aggregator instance in step 5. Then click the “Apply Changes” button.

9) Return to the first Aggregator instance, go to the “Associate Pgms” tab, and add the second Aggregator instance.  

Ethernet/Internet requirements for 2-receiver Red Pitaya

 Ash KF5EYY/3V8 just reminded me of an additional requirement for running both receivers on an RP-16, to cover 8 bands each.  Each receiver requires about 75 Mbps of Ethernet bandwidth between the receiver and your PC, and it adds up.  This means that your PC must have a gigabit Ethernet port in order to receive two receivers worth of 8-band x 192 KHz data.

My PC has such a port, but like many it was already committed to my Internet router.  Fortunately, Netgear makes a very nice unmanaged Ethernet switch, the GS 308 which retails for under US$20 plus shipping.  All I had to do was plug my receiver, my PC, my KPA-1500 amp and my router into the switch, and it was up and running.  Whew!