DSDPlus Syntax of FMP-FreqList.CSV entries please ?

[mw0cqu]

Hi all,

Not being located in the US, I do not have the luxury of the per state lists you all enjoy over there for FMPxx.

I have downloaded one of them to try and reverse engineer it in order to build my own for this side of the atlantic, but there are many things that don't seem to
make sense or are perhaps defaulted (e.g. ",0,")

Ive googled , looked on youtube, checked the FL release notes....no luck.

So can someone let me in on the secret syntax of the "magic line" format in FMP-Freqlist.csv please ?

e.g. <frequency>,<mode>,<Address in quotes>,<licencee>,

That's the level of detail I'm craving , not populated content! - just a "what goes where in what order" please.

Many thanks

73

'CQU

 

[cg]

Looking at it, it seems very straightforward.
<frequency in MHz 8 decimals>, 0, "<licensee name>", "<transmitter location>", <latitude dd.dddd>, <longitude ddd.dddd>, "<callsign>", "<mode & service code>"
I would imagine that anything in quotes is placed verbatim on the screen.
Don't forget to change the file name and location in the FMPx.CFG files

chris

 

[mw0cqu]

Hi Chris,

Thanks for your input, I disagree on a couple of things. Here's how I see it :

the zero (second field) must be a default for something? even if its "unknown" ?

Using 2 example lines from the US Files:

155.9175, 0, "THURSTON 9-1-1 COMMUNICATIONS", "1205 FRANZ STREET SE/LACEY/THURSTON", 47.0361, -122.8157, "6K00F3E", "11K2F3E" ; WA
155.9175, 0, "THURSTON 9-1-1 COMMUNICATIONS", "2703 PACIFIC AVENUE/OLYMPIA/THURSTON", 47.0433, -122.8643, "6K00F3E", "11K2F3E" ; WA

Obviously the ";WA" is a comment that identifies state and as a comment isn't used.

But where you think "<callsign>", "<mode & service code>" I see two variants of FM bandwidth:

6K00F3E--
Bandwidth: 6.00 kHz
Modulation Type: [F] Angle-modulated, straight FM
Modulation Nature: [3] Single analog channel
Information Type: [E] Telephony, voice, sound broadcasting

11K2F3E--
Bandwidth: 11.2 kHz
Modulation Type: [F] Angle-modulated, straight FM
Modulation Nature: [3] Single analog channel
Information Type: [E] Telephony, voice, sound broadcasting

in addition, I see "/" used which I assume is a "new line" formatter which I assume:

makes long lines like this

into shorter
lines
like
this

So we have the bulk of it - But I hope (as dsd coders do float around here) that the zero field can be explained and the need for 2
modulation types can also be clarified.

73 de 'CQU

 

[morfis]

My interpretation of what you showed:

Output frequency, Input frequency, Licensee, Location Name, Latitude, Longitude, first emission mode, second emission mode ;comment

You will be using the Output frequency so Input is not needed so is set to '0'
No idea why it has positions for two emmission modes or even if the second one should be entered in the way shown in your example. Could it be a 'text' descriptor for the mode/bandwidth?
Most fields can be left blank if not required (or known) but (possibly) not the second frequency field
The '/' is within the quotes so proabably doesn't create new lines, just used to make it clearer that the text splits the specific address from the locality and township.

Easiest way to tell would be to create a Gogleth version and try it?

 

[mw0cqu]

hm...actually the comment <IS> used ?? how odd !

 

[mw0cqu]

And as you say because its inside the quotes the Slashes dont get picked up ... as illustrated below

Odd that the dsd guys didnt include a "comment line" in the config file?
I now also see the purpose of lat and long (fmp-map)

 

[morfis]

The Long/Lat in combination with the centre and range figures in the config file also allow 'location based scanning' - though with those parts of the config not exposed in the menus it would be a bit awkward to change?

 

[mw0cqu]

commenting on:

You will be using the Output frequency so Input is not needed so is set to '0'

I would if I tuned across an input frequency ....

 

[morfis]

commenting on:

You will be using the Output frequency so Input is not needed so is set to '0'

I would if I tuned across an input frequency ....

I imagine you could enter the input in the second field if you wanted to......is it then just a label like the rest of the fields or does it have some actual functionality?....no idea as I don't use FMP for sacnning and comments based on what you have written in this thread

 

[mw0cqu]

I think the last piece of the jigsaw puzzle is the modulation types - does FMPxx interact with that ?
e.g. if I put in an AM mode code into the CSV, will fmpxx switch to AM ?

Also what about networks? I have DSD+FL tracking and labelling networks 100% But in FMPxx I see no way to
tie up an fmp frequency with a network ID ? could that be the role of "0" ? (although I agree input freq would make the most sense)

73 de 'CQU

 

[morfis]

I think the last piece of the jigsaw puzzle is the modulation types - does FMPxx interact with that ?
e.g. if I put in an AM mode code into the CSV, will fmpxx switch to AM ?

Also what about networks? I have DSD+FL tracking and labelling networks 100% But in FMPxx I see no way to
tie up an fmp frequency with a network ID ? could that be the role of "0" ? (although I agree input freq would make the most sense)

I suspect the only way to tie them up would be to label them as being part of a network (which I guess you'd do in the licensee/user part anyway).
The scanlist doesn't look as though it is any more than a list of frequencies to be scanned rather than something which can interact with the digital decoding side of things. The emission modes being in quotes suggests they are just text labels within the file and your screenshot supports that idea (good UHF range you have there....).

 

[cg]

So you are saying that you have not been able to create a file that works?
It really is only:
<frequency>, 0, "<text>", "<text>", latitude dd.dddd, longitude ddd.dddd, "<text>","<text>"
The text can be whatever you want it to say. The lat & long gives the distance from your base location that you have entered in the FMPx.CFG file



The file that is downloaded from the DSDPlus site is a dump from the FCC database. It wouldn't be too difficult to create your own from any other frequency database using Excel and Notepad.

chris

 

[slicerwizard]

The Canadian .csv file starts with this:

; TXfreq, RXfreq, Licensee, Location, Latitude, Longitude, first emission mode, second emission mode


and here's a representative line:

410.5375, 415.5375, "Metrolinx", "NEWMARKET, ONT. 18110 YONGE ST", 44.0639, -79.4872, "16K0F3EJN", ""


So tuning to a license's repeater input or output should cause FMPx to display the license info.

Frequencies can be licensed for more than one mode; I've seen some that are licensed for both analog and digital modes - probably because they're transitioning or planning to. However, I don't see any .csv records where that second emissions mode field is actually populated.

Latitude/longitude yields bearing and distance values; calculated distance limits FMPx's searches for matching records. Task Manager says it also affects FMPx's memory consumption.

When mousing over spectrum, closest matching record's text fields get displayed on screen. When tuning, all in-range matches are displayed in FMPx console window, and when TCP/direct linking is used, closest match is sent to DSD+; beyond that, I suspect you're over-thinking it.