To all RFRScanner and Elad SDR user,

Important updates 
RFRScanner version 1.2.3 SEP/27/24
Converter  version 1.0.2 SEP/27/24

1)

Import the Elad actual Station Memory Data using the TCP connection > [Import SW2].
This Elad procedure is limited to 9.999 Records (4 digit), 'BUG'. Manual is saying 100.000, 5 digit.
To overcome this restriction i have added a new procedure.
You exchange your data in (SW2) on the fly.

RFRScanner > Options > 'Transfer XML file to RFRScanner (SW2) Memory List'       (in (F4) dbStations View.)

           A xml file created by RFRScanner or the Converter must exist.

You don't need the TCP connection and the FDM-SW2.

If you have "xml" files you can use this very fast proc.


A)

This proc is reading 'XML' files created only by RFRScanner or the Converter.exe.
Including only 3 Fields: Frequency, Station, Mode.               (HAM Band is added during conversation)
(this xml files can be imported by the Elad FDM-SW2 Station Memory > Load)


B)

(If you have already (your) Data in your actual Elad FDM-SW2 Menu Station Memory loaded, download it using the TCP connection [Import SW2]).
(only max. 9.999 rec are imported into the RFRScanner " (SW2) "List )
Once imported you can create a xml file using the "TCP connection" > [Upload] procedure. Converting the (SW2) data List into a xml file.
You can "Add" RFRScanner (SW2) data to a existing xml file or save as new file with a name.
This xml file can be used as mentioned in  A) .

In other words, now you use the TPC connection [Import SW2] only if there is no xml file containing the
actual FDM-SW2 Data "Loaded".




Let's create a xml file with the Converter Default Sessions.

Create your 'xml' file with the Converter program.
- select Session: Example_by_Delimiter.cfg

                  'has more then 30.000 records
                  'eliminating the Char " & " that Elad can't read and is in various Freq Files you download.
                  'This proc takes a while x a big file. (Translating twice)


- Run: [Translate] 
       
                  'creating a data list with upto 8 fields. OmniRig connection possible.


- Input a FileName into: [Input FileName]

                  'overwrite 'existing' possible.


- Menu [Translate x Elad] > (2) Translate into xml File.

                  'extract Data: Frequency, Station, Mode

When terminated > follow the messages. Xml file is in your Converter Folder.
Copy it into your ELAD > FDM-SW2 > Memories Folder.
Open the FDM-SW2. Menu > Station Memory > Load. Select this xml File you created.
- => [Apply]  wait until Waterfall is restarting.  (with 30.000 rec it takes a while)
- => [Close]



2)

TCP connection > [Upload]: 2 selections Yes + No - RFR (SW2) to new xml file  OR  RFR (SW2) add to existing xml file

There is no Record limit.

[Upload] is not really uploading to FDM-SW2. We create the xml files FDM-SW2 can 'Load'.
[Upload] is reading the RFRScanner (SW2) data in "F4".
Read above: B) .
The FDM-SW2 - Station Memory - "Load" procedure" is not limited like the FDM-SW2 export/ RFRScanner Import proc.

Now you have all possible features for manipulating  Frequency Data with your Elad SDR.

Read menu > Help + all ( H )buttons + Tooltips.

The Kbd Shortcut "^NumPat4" is now connected with "Recorder > Stop" Button.
This is useful because the "Escape" Key is starting or interrupting (Pause) the registration but not stopping without opening the Recorder (F3). You can change this Shortcut.


http://www.intrasystem.it/Frequency/Frequency.html

Intrasystem
Raimund
.