DSD+ FL, missing files solution...

Status
Not open for further replies.

TheButcher

Member
Joined
Jun 12, 2013
Messages
276
I am not the most sharpest tool on the shelf, but why not DSD+ just create any missing files if found on startup ? Duh...


Thanks DSD+ team...
 

slicerwizard

Member
Joined
Sep 19, 2002
Messages
7,650
Location
Toronto, Ontario
Already covered here a few times. If DSD+ has a problem reading a file that actually does exist, what happens to your data if DSD+ decides to create a new empty file?

Edit: IIRC, DSD+ 1.101 will eat all of your data (like all your groups and radios) if it can't read the files when DSD+ starts.
 
Last edited:

u2brent

OAMPT
Premium Subscriber
Joined
Jul 17, 2010
Messages
3,089
Location
KRWDPAXKRS1
If the directions are followed the files would not be missing in the first place.
79312

79311
 

TheButcher

Member
Joined
Jun 12, 2013
Messages
276
Latest DSD+ LF spat the dummy over monitoring a P25 system to do with 'DSDPlus.frequencies' file. I included f info into said file in the past, which I understand is now not necessary any more. So I moved said file elsewhere and ran DSD+ FL again and it complained about missing 'DSDPlus.frequencies' file.

If DSD+ FL created 'DSDPlus.frequencies' file, then all would be peachy...

I basically created a zero byte file and boomfa, problem solved.


But thanks for your input guys...

79313

Latest FL version rans fine for me. No more crashing etc. But I do experience an issue saying that "RTL SDR device #1 is in use" (or #2, as I have 2 of them). Closing all DSD+ FL windows and reloading solves the issue. Strange...
 
Last edited:

slicerwizard

Member
Joined
Sep 19, 2002
Messages
7,650
Location
Toronto, Ontario
a) You never should've put any P25 trunking entries in your frequencies file; they were never required and they can cause problems

b) You shouldn't have removed your frequencies file from the DSD+ folder

c) If you use multiple dongles and don't really care how they get picked/used, specify -i0 (or no -i at all) in your FMP24 command lines

d) If you use multiple dongles and do care how they get picked/used, program each one with a unique serial string and use those strings in your FMP24 command lines
 

TheButcher

Member
Joined
Jun 12, 2013
Messages
276
"a) You never should've put any P25 trunking entries in your frequencies file; they were never required and they can cause problems"

Roger, got you. Thanks! I did read about it. But I know of site frequencies of some far, far away sites. It is handy to know them and populate them. But I guess if one was in range, the "DSDPlus.P25data" file populates this f info. Fair enough (I hate change!).


"b) You shouldn't have removed your frequencies file from the DSD+ folder "

Well I moved it to a backup directory and .rar'ed it and renamed it "Don't Delete!!!" etc (to remind me not to delete it. ...Frequencies backed up). Serves as a reference for me... I then noticed DSD+ bitshing (cant believe this word has been filtered, stupid Males!, lol. I was referring to a Female dog for goodness sake. Oh, modern PC times... I would rather be called a dog than human!). So easily enough, I copied a blank (zero byte file) there and named it "DSDPlus.frequencies" etc. Problem solved. Just would be nice if DSD+ created it in the first place...



"c) If you use multiple dongles and don't really care how they get picked/used, specify -i0 (or no -i at all) in your FMP24 command lines "

Well I do and I have not played with this yet. sounds like ability to specify dongle via serial number (must all be unique, I guess too...) is gold. This is / was a good addition (thanks team). If for example, one had, say, 2 dongles (for simplicity), each had different aerials (beam and vertical for simplicity), one has the tools to specify WHICH one is used. Brilliant.



"d) If you use multiple dongles and do care how they get picked/used, program each one with a unique serial string and use those strings in your FMP24 command lines "

Not got this far, yet... (Time for play!).

Sooo, instead of doing...

"START FMP24 -i1 (etc, etc)"

Do...

"START FMP24 -ixxxxxxxx"

Where "xxxxxxxx" is the unique serial number of the dongle?

Will give that a try!


Thanks for your step by step help.



ps. Got to play with the IP feature too. I would like to have a dongle in say, a different City... (For reference... "DSDPlus -i192.168.1.123:20000")

pps. It would be fantastic, in the "DSDPlus.txt" help file to include some examples of invoking strings and different examples of this...
 

TheButcher

Member
Joined
Jun 12, 2013
Messages
276
Nope. Should be....

START FMP24 -i"xxxxxxxx"

...got to include " either side of the 8 digit serial number number string...

Cheers...
 

slicerwizard

Member
Joined
Sep 19, 2002
Messages
7,650
Location
Toronto, Ontario
"a) You never should've put any P25 trunking entries in your frequencies file; they were never required and they can cause problems"

Roger, got you. Thanks! I did read about it. But I know of site frequencies of some far, far away sites. It is handy to know them and populate them. But I guess if one was in range, the "DSDPlus.P25data" file populates this f info. Fair enough (I hate change!).
Add those known sites to the .P25 data file...

"b) You shouldn't have removed your frequencies file from the DSD+ folder "

Well I moved it to a backup directory and .rar'ed it and renamed it "Don't Delete!!!" etc (to remind me not to delete it. ...Frequencies backed up). Serves as a reference for me... I then noticed DSD+ bitshing (cant believe this word has been filtered, stupid Males!, lol. I was referring to a Female dog for goodness sake. Oh, modern PC times... I would rather be called a dog than human!). So easily enough, I copied a blank (zero byte file) there and named it "DSDPlus.frequencies" etc. Problem solved. Just would be nice if DSD+ created it in the first place...
The file came with DSD+ 1.101; only way to have a problem is if you nuke the file.

"c) If you use multiple dongles and don't really care how they get picked/used, specify -i0 (or no -i at all) in your FMP24 command lines "

Well I do and I have not played with this yet. sounds like ability to specify dongle via serial number (must all be unique, I guess too...) is gold. This is / was a good addition (thanks team). If for example, one had, say, 2 dongles (for simplicity), each had different aerials (beam and vertical for simplicity), one has the tools to specify WHICH one is used. Brilliant.
Exactly.

"d) If you use multiple dongles and do care how they get picked/used, program each one with a unique serial string and use those strings in your FMP24 command lines "

Not got this far, yet... (Time for play!).

Sooo, instead of doing...

"START FMP24 -i1 (etc, etc)"

Do...

"START FMP24 -ixxxxxxxx"

Where "xxxxxxxx" is the unique serial number of the dongle?

Will give that a try!
Close. I see you've got it sorted out now.

Thanks for your step by step help.
No prob.

ps. Got to play with the IP feature too. I would like to have a dongle in say, a different City... (For reference... "DSDPlus -i192.168.1.123:20000")
Yep, looks right to me. I've done it on a local network.
 

TheButcher

Member
Joined
Jun 12, 2013
Messages
276
"Add those known sites to the .P25 data file..."

Ah yea, good idea! Pressing "L" site loader comes up with blanks. Putting them in there should solve that. Thanks again!



"The file came with DSD+ 1.101; only way to have a problem is if you nuke the file."

Could be unnuked, but never mind...



"Yep, looks right to me. I've done it on a local network. "

That would be my first (baby) step. Doing it over the internet will be the next step. I doubt FMP24 would be a 'web server' though, although networking is not a strong point of mine. A router may be? No clue. Might have to ask a mate who is knowledgeable.
 

slicerwizard

Member
Joined
Sep 19, 2002
Messages
7,650
Location
Toronto, Ontario
FMP24 is a server of sorts. It listens for incoming TCP connections. Router port forwarding would be needed so incoming connections can reach FMP24. Shouldn't take more than that.
 
Status
Not open for further replies.
Top