DSD Frequencies File

Status
Not open for further replies.

rkillins

Member
Joined
Dec 15, 2001
Messages
282
Can anyone see any problem with my DSD frequencies file?
I am unable to get DSD+ to recognize channel 131 of the NexEdge system, or any of the frequencies of the Con+ system.

Code:
;   use sort order = 0 to sort by OTA channel number
;
;
; protocols:
;
;  D-Star
;  IDAS
;  NEXEDGE48
;  NEXEDGE96
;  dPMR
;  DMR
;  Cap+
;  Con+
;  TIII
;  P25
;  ProVoice

NEXEDGE48, 202, 16, 101, 420.05625, 420.05625,0
NEXEDGE48, 202, 16, 105, 420.45625, 420.45625,0
NEXEDGE48, 202, 16, 25, 420.83125, 420.83125,0
NEXEDGE48, 202, 16, 28, 420.93125, 420.93125,0
NEXEDGE48, 202, 16, 131, 420.25000, 420.25000 ,0
Con+, 202, 8, 01, 451.5750, 451.5750,0
Con+, 202, 8, 02, 452.4250, 452.4250,0
Con+, 202, 8, 03, 454.0750, 454.0750,0
 
D

DaveNF2G

Guest
1) Have you tried putting the NEXEDGE frequencies into channel number order?

2) Do both systems actually use the SID of 202? Seems like an odd coincidence.
 

slicerwizard

Member
Joined
Sep 19, 2002
Messages
6,887
Location
Toronto, Ontario
; DSD+ frequency file
;
; line format:
;
; protocol, network ID, site number, OTA channel number, TX frequency, RX frequency, sort order

NEXEDGE48, 202, 16, 101, 420.05625, 420.05625,0
NEXEDGE48, 202, 16, 105, 420.45625, 420.45625,0
NEXEDGE48, 202, 16, 25, 420.83125, 420.83125,0
NEXEDGE48, 202, 16, 28, 420.93125, 420.93125,0
NEXEDGE48, 202, 16, 131, 420.25000, 420.25000 ,0


Line format specification has a space after all commas.


Con+, 202, 8, 01, 451.5750, 451.5750,0
Con+, 202, 8, 02, 452.4250, 452.4250,0
Con+, 202, 8, 03, 454.0750, 454.0750,0


Per the docs, DMR channel numbers should be odd (1, 3, 5), not 1, 2, 3. And those pesky spaces...
 

LimaZulu

Member
Joined
Jul 7, 2011
Messages
184
channel 131

About CH 131 - where your last comma is, you have space BEFORE the comma and not after it. Don't know if this is the case but the right syntax should be with space AFTER the comma
 
Status
Not open for further replies.
Top