Nexedge 4.8k System 13

Status
Not open for further replies.

DaveH

Member
Joined
Jul 29, 2001
Messages
3,287
Location
Ottawa, Ont.
Interesting....you may be right. 150.950 NXDN was periodically interrupted by LTR burst but frequency is used at several sites, so maybe some have been converted.

Dave
 

DaveH

Member
Joined
Jul 29, 2001
Messages
3,287
Location
Ottawa, Ont.
Heard a CC on 153.260 during enhanced conditions, which may belong to the same system. However, getting slightly odd network/site IDs from DSD+, such as R13-32 and R13-56, plus some neighbours with very large site numbers (didn't copy them down). Safe to assume it's network 13, sites 32 and 56?

Dave
 

mtindor

OH/WV DB Admin
Database Admin
Joined
Dec 5, 2006
Messages
10,408
Location
Carroll Co OH / EN90LN
Heard a CC on 153.260 during enhanced conditions, which may belong to the same system. However, getting slightly odd network/site IDs from DSD+, such as R13-32 and R13-56, plus some neighbours with very large site numbers (didn't copy them down). Safe to assume it's network 13, sites 32 and 56?

Dave

Yes, safe to assume Network 13, Sites 32 and 56. The large site numbers have always been the result of bad decodes. I see that alot when I'm doing tropo DXing and working with weak signals. It is to be expected. Fortunately, you obviously think sanely. Just forget about those things that do not seem sane and figure that it was bad decoding.

Just a caution to you - DB admins are supposed to enter in NXDN system IDs without L or R, but from time to time you might find an entry in the DB that is prefixed with L or R because it was added before that policy was set. So, when looking in the DB for NXDN system IDs, if DSDPlus shows it with an L or an R, search for it with the L or R and without the L or R when you search in the DB. And if you happen to discover an NXDN system in the DB whose system ID is prefixed with L or R, simply make a submission to that system and request that the admin remove the L/R from the system ID and just make a note of the area on the system page.

I'd agree with MCIUPA regarding it being Mobiltech. You might consider submitting your sysid 13 findings to that trunked system. Obviously an admin would have to create a new system that was specifically NXDN48, but if you submit it to the LTR system then a local NY admin who is used to working those submissions can easily create the new system based upon that info. Otherwise, if you submit it as a new system, a local NY admin won't see the submission and it will get generically added by a global admin.

Mike
 
Status
Not open for further replies.
Top