With my lists, I have the repeater output listed first. Yours appear to have the inputs listed first.
DSD+ Fast Lane setup questions
- Thread starter W4KRR
- Start date
- Status
I know but eh protocal from the notes in DSD says to
FMP Frequency Lists
Example data:
; TXfreq, RXfreq, Licensee, Location, Latitude, Longitude, first emission mode, second emission mode
boy there is a lot of moving parts. I too thought that the receiving frequency should be first, then when you edit the FMP.cfg files the "step size" comes into play?
vince48
FMP Frequency Lists
Example data:
; TXfreq, RXfreq, Licensee, Location, Latitude, Longitude, first emission mode, second emission mode
boy there is a lot of moving parts. I too thought that the receiving frequency should be first, then when you edit the FMP.cfg files the "step size" comes into play?
vince48
It wants the transmit frequency of the repeater not the user gear. You've got them reversed.
slicerwizard
Member
Those two lines reference the same RF channel. DSD+ DMR channels 1 and 2 are timeslots 1 and 2 on the first RF channel.
From DSDPlus.txt:
DSDPlus.frequencies
DSD+ uses this file to display frequency information when DSD+ is monitoring
a rest channel or control channel. The frequency records will also be
used to control channel steering for trunked voice following.
Note:
DSD+ uses two channel numbers for each DMR RF channel:
Channel #1 = first RF channel, timeslot 1
Channel #2 = first RF channel, timeslot 2
Channel #3 = second RF channel, timeslot 1
Channel #4 = second RF channel, timeslot 2
Channel #5 = third RF channel, timeslot 1
Channel #6 = third RF channel, timeslot 2
...
For all DMR systems (DMR, Cap+, Con+, TIII), only one channel record has
to be added to the DSDPlus.frequencies file for each RF channel.
You can use the channel number that corresponds to timeslot 1 or 2 and
DSD+ will use the same frequency information for the other timeslot.
You have two entries for the first RF channel and no entry for the second RF channel (so change Con+, 319, 3, 2 to Con+, 319, 3, 3)
Well Sir, the protocol says TXfreq first, the offset's is +5Mhz and +3Mhz for the receiving frequencies. Am I wrong or are the DSD protocol wrong? Please advise.
vince48
vince48
thank you slicerwizard,
this is becoming a moving target. Too many moving parts.
vince48
slicerwizard
Member
DSD+ expects to see the system TX frequency first, then the optional system RX frequency. Your list has the higher numbers (subscriber equipment TX frequencies) first.
I don't think any of this has changed since the DSDPlus.frequencies file was introduced. The order was always site TX freq, site RX freq and DSD+ always used separate channel numbers for each DMR slot.
Ok, thanks, I wont belabor this, but if the output (receiving frequency) frequency is 484.xxxx, wouldn't the transmit frequency be 5 Mhz higher at 489.xxxx? I'm sorry , but am i wrong or just .......?
please do not misconstrue me, but the DSD protocol ask for the transmit frequency frist (higher number)
Thank you in advance for your reply.
vince48
please do not misconstrue me, but the DSD protocol ask for the transmit frequency frist (higher number)
Thank you in advance for your reply.
vince48
slicerwizard
Member
When you write output, receiving and transmit, you have to be clear on whose reference point you are using - the system repeaters? the subscriber units? DSD+?
Radio systems (conventional or trunked) have TX and RX frequencies; they are the frequencies that the system repeaters transmit on and listen to.
Subscriber units (radios) use the same frequencies, but they listen to (e.g. RX) the system TX frequencies and transmit (TX) on the system RX frequencies.
Decoders like DSD+ and UT just listen, so obviously they don't have any TX frequencies. While DSD+ can be tuned to system TX or RX frequencies and can decode repeater outputs as well as signals coming directly from subscriber radios, it, like most decoders, and especially those that can decode control channels, are designed for and almost always used to monitor repeater outputs, aka system TX frequencies. And the nomenclature used (TX vs RX) is from the system's point of view, where TX means what the system transmits on and RX means what the subscribers transmit on (and the system receives)
In North America, UHF bands typically use +3 or +5 MHz as you noted; that means the system RX frequencies are 3 or 5 MHz higher than the matching system TX frequency. So pairs like TX=451.xxxx, RX=456.xxxx are very common. That's system TX is 451, subscriber TX is 456...
DSD+ wants to see a system TX frequency, then an optional system RX frequency in those channel records. So for UHF, lower number, then higher number.
The opposite applies to 800 and 900 MHz systems, as they are -45 and -39 MHz, so system TX frequencies are considerably higher than the matching subscriber TX frequencies.
D
DaveNF2G
Guest
This causes confusion even for experienced users sometimes, especially when trying to translate a codeplug into something DSD+ can use. 
Perhaps a reference in the docs explaining that "TX frequency" means "repeater output", etc., would be useful.
Perhaps a reference in the docs explaining that "TX frequency" means "repeater output", etc., would be useful.
ak4fn
Member
This is my DSD + frequency file for this system Christian County Public Safety Trunking System, Hopkinsville, Kentucky - Scanner Frequencies
Code:
; DSD+ frequency file
;
; you can edit this file while DSD+ is running
;
; line format:
;
; protocol, networkID, siteNumber, OTAchannelNumber, TXfrequency, RXfrequency, sortOrder
;
; for TIII, siteNumber format = area.site
;
;
; use site number = 0 for network-wide definition
;
; use 0.0 for unknown frequencies
;
; use sort order = 0 to sort by OTA channel number
;
;
; protocols:
;
; D-Star
; IDAS
; NEXEDGE48
; NEXEDGE96
; dPMR
; DMR
; Cap+
; Con+
; TIII
; P25
; ProVoice
; KELLY TOWER SITE 2
NEXEDGE96, 25, 2, 255, 453.17500, 453.17500, 0
NEXEDGE96, 25, 2, 274, 453.41250, 453.41250, 0
NEXEDGE96, 25, 2, 287, 453.57500, 453.57500, 0
NEXEDGE96, 25, 2, 297, 453.70000, 453.70000, 0
NEXEDGE96, 25, 2, 308, 453.83750, 453.83750, 0
;Channel Map for Site 1 - Hopkinsville
NEXEDGE96, 25, 1, 213, 452.6500, 452.6500, 0
NEXEDGE96, 25, 1, 257, 453.2000, 453.2000, 0
NEXEDGE96, 25, 1, 283, 453.5250, 453.5250, 0
NEXEDGE96, 25, 1, 295, 453.6750, 453.6750, 0
NEXEDGE96, 25, 1, 311, 453.8750, 453.8750, 0
NEXEDGE96, 25, 1, 405, 460.0500, 460.0500, 0
NEXEDGE96, 25, 1, 416, 460.1875, 460.1875, 0
NEXEDGE96, 25, 1, 438, 460.4625, 460.4625, 0
;Channel Map for Site 3 - Oak Grove
NEXEDGE96, 25, 3, 259, 453.2250, 453.2250, 0
NEXEDGE96, 25, 3, 269, 453.3500, 453.3500, 0
NEXEDGE96, 25, 3, 281, 453.5000, 453.5000, 0
NEXEDGE96, 25, 3, 302, 453.7625, 453.7625, 0
NEXEDGE96, 25, 3, 411, 460.1250, 460.1250, 0
;Channel Map for Todd Co Elkton Tower
NEXEDGE48, 161, 1, 1, 453.18125, 453.18125, 0
NEXEDGE48, 161, 1, 2, 453.19375, 453.19375, 0
NEXEDGE48, 161, 1, 3, 453.27500, 453.27500, 0
NEXEDGE48, 161, 1, 4, 453.66250, 453.66250, 0
NEXEDGE48, 161, 1, 5, 460.10000, 460.10000, 0The DSDPlus.frequencies file is for NEXEDGE48/96, DMR Con+ and DMR TIII trunking systems. It tells DSD+ what the frequencies are for each system and site. DSD+ uses this information to display trunking system activity with matching frequencies in the channel activity window. DSD+ 1.080+ uses this information to follow voice calls. It is not used for conventional scanning.
Conventional scanning of digital voice channels can be done using FMP and DSD+.
The FMP.ScanList file has to be edited (with Notepad) and one line should be
added for each frequency you want to conventionally scan. Each line has three components:
1) the frequency in MHz
2) the digital protocol (controls FMP's bandpass filtering)
3) channel identifying text
examples:
462.5025 DMR Initrode Inc.
938.2000 NXDN48 Bob's Taxi
Pressing 'S' in FMP starts scanning mode. FMP will cycle through your frequency list.
If DSD+ decodes digital voice, FMP will pause (hold) on the current RF channel
until the digital voice ends.
This is all explained in the FMP.txt file.
scanning
FMP can (slowly) scan frequencies
a frequency list, one frequency per line, should be placed in a file
named FMP.ScanList
the format of each line is:
frequency mode description
example:
450.1250 TIII Acme Radio
frequency is in MHz
mode text controls bandpass filter selection
4 kHz modes:
D-STAR
DSTAR
IDAS
NX48
NEXEDGE48
7 kHz modes:
DMR
TRBO
Cap+
Con+
TIII
9.5 kHz modes:
NXDN
NEXEDGE
NEXEDGE96
NX96
P25
12.5 kHz modes
PV
ProVoice
any other text string (analog, LTR, ...)
blank lines in the file are ignored
processing of the FMP.ScanList file stops if a line containing
the string <EOF> is found; frequency entries that you don't want
to scan can be stored in the file after the <EOF> line
pressing S starts scanner mode
pressing Esc exits scanner mode
no other scanning commands (Hold, L/O, etc.) are presently implemented
FMP's scanner mode is designed to be used with DSD+. FMP and DSD+
should be running in the same folder. While DSD+ is decoding
digital voice, FMP will auto-hold on the current RF channel.
If DSD+ is not decoding digital voice, FMP will auto-scan to the
next channel in the scanlist. This behaviour will let you monitor
multiple digital channels, including control or rest channels.
FMP will not get hung up on constant carriers that are not broadcasting
digital voice calls.
racingfan360
Member
- Joined
- Dec 19, 2005
- Messages
- 1,160
> Do I need the viritual cables that were mentioned ?
>You must install the virtual cables, I use (VB-Audio) Free.
Errr.....you don't need virtual cables if you are ONLY using a normal scanner with a discrim tap as the source for DSD+. You do need virtual cable if you want to use a software based source such as FMP.
>You must install the virtual cables, I use (VB-Audio) Free.
Errr.....you don't need virtual cables if you are ONLY using a normal scanner with a discrim tap as the source for DSD+. You do need virtual cable if you want to use a software based source such as FMP.
I don't know what version it started with but you no longer have to use Virtual Cables with FMP. You use TCP link port numbers and match the FMP output port number (256-65535) with the input port in DSDPlus.
chris
chris
Hello, thank you both for the notes. Aside from watching the u tube video are there instructions somewhere that gives you details on how to set this up? The welcome note said to read the notes, I have read over them but this appears to cover what changes were made in each upgrade, nothing specific on how to set things up. From Chris's note it appears I can use TCP link, where can I find info on setting that up? Thanks again for your help.
Scott
Scott
In the help files that come with DSDPlus
chris
chris
- Status
