Started hearing Saluda Co. S.O. on NXDN today. So far, they are simulcasting on 460.0375 and FleetTalk Carolinas TG 11415. I also heard a Saluda Co. ambulance being dispatched also being simulcast but I wasn't fast enough to get the TG darn it. So far, they are simulcasting on both fleettalk sites in Edgefield, SC.
Saluda County Is Transitioning to NXDN
- Thread starter AB4BF
- Start date
shajoe44
Member
11426 is Saluda Co. Fire
These are all the Saluda talk groups so far: 11415, 11423, 11426, and 11432.
Radio Service was coming in on i17428 and i17434. Don't know what the little "i" denotes, but it was in front of both talk groups on my Arc XT Pro list.
As an aside, Talk Group 2010 is hilarious! Its like the Beverly Hillbillies meets NXDN, lol!
Radio Service was coming in on i17428 and i17434. Don't know what the little "i" denotes, but it was in front of both talk groups on my Arc XT Pro list.
As an aside, Talk Group 2010 is hilarious! Its like the Beverly Hillbillies meets NXDN, lol!
shajoe44
Member
2010 Is a trucking firm that uses Fleettalk
iXXXXXX Is a private call, or individual call AKA an "I-Call". The numbers are the RID (Radio Identification number) If you use ProScan for logging I know you can also see the "source" RID, and the "target" RID. Then the convo is carried on only one of them as far as what is displayed. (SRC i133321, GRP i13322, then all you see is say i13322 for the convo.) It is also a good idea to have an system that can read the "Alias" for RID's, as that can indeed help you ID usage of a TG or I-Call. A lot of Public Safety, and Business users put aliases on the radios so dispatch sees who is calling. You may see something like: E-11, Saluda10, EOC-BASE instead of 1124589 for the RID's. Its come in handy for identifying users on an NXDN TRS here. (BUS 10, BUS 30 etc helped nail down a school transportation dep't., and the aliases of APEX10, APEX01 helped nail down an Property Management Group.
Last edited by a moderator:
shajoe44
Member
I am using DSDPlus and it shows both the radio ID followed by whatever they have entered in relationship to the user of that radio. (PD-10) (Jail 3) etc. It definitely makes it easier to decipher agency using what.
GearJammersc
Member
What is the best scanner that will monitor NXDN ?
Here is a good place to start:
NXDN - The RadioReference Wiki
You should note the Uniden scanners (SDS100, SDS200, BCD436HP, BCD536HP, BCD325P2, and BCD996P2) require a paid upgrade to monitor NXDN. Whistler scanners (TRX-1 and TRX-2) may seem like a better deal because there is no paid upgrade, but they cannot trunktrack NXDN systems. For busy NXDN systems, you will want a scanner that properly tracks the talkgroups.
I use the Uniden BCD536HP, SDS100 and SDS200. All three models work great on NXDN conventional and trucked systems. If monitoring a P25 simulcast system also, I would recommend the SDS100 or SDS200 as they work much better in decoding the simulcast signals as compared to the 536.
GearJammersc
Member
What bout the BCD325P2?
GearJammersc, it looks like you might be in luck. From what this reads, you will need to do a little updating and purchase the upgrade license for NXDN to work.
forums.radioreference.com
NXDN Comes to BCD325P2 and BCD996P2
And a bunch of other fixes and enhancements, too. Version 1.08.00 for both the BCD325P2 and BCD996P2 was just released. This update adds the following major features and enhancements: Support for NXDN systems through a paid upgrade Support P25 patch ID Support EA EDACS patch ID Improved the...
I currently receive Saluda NXDN from three sites, the Little Mountain NXDN, Gilbert NXDN and West Saluda NXDN. Also listed is an East Saluda NXDN tower that looks to be located in the town of Saluda. I've got it programmed, but I have yet to receive anything from it nor do I get any "bars" of signal strength from it. My question is. is it on line, yet?
Darn. I'll have to move my discone to another location to see if I can receive it. I don't believe I'm missing any transmissions while receiving off the other three sites, but, you never know...
BTW, Thanks to Searay!
BTW, Thanks to Searay!
Similar threads
