BM82557
Member
Site 2.4, Berryville, shows new site neighbors of 1.4 and 3.4, neighbor 3.2 (217.79375 MHz) has been previously noted but it's location has not yet been identified.
Rappahannock Electric Cooperative New Sites
- Thread starter BM82557
- Start date
BM82557
Member
Site 3.1, Linden, shows new site neighbors of 1.3, 1.4 and 3.4, neighbor 3.2 (217.79375 MHz) has been previously noted but it's location has not yet been identified.
I found several neighbors for Fredericksburg, Berryville, and Linden, and recently added them to the REC system page. Louisa is too weak to decode neighbors from Fredericksburg (I don't have a good antenna).
I'm using DSD+ Fast Lane, which must have added the ability to show Tait Tier III neighbors in the last several months, as I remember not getting neighbors earlier in 2021.
Dave
I'm using DSD+ Fast Lane, which must have added the ability to show Tait Tier III neighbors in the last several months, as I remember not getting neighbors earlier in 2021.
Dave
- Joined
- Dec 19, 2002
- Messages
- 2,135
There are errors with the RVEC listing in the RR database in. Not only is it
incomplete, some of the associations of frequency sets are wrong. For
example,the listing there for Berryville is not Berryville but a different site
(being frequencies for Linden Mtn. #2 and those listed as Linden Mtn. #2 are
actually Hogback Mtn.) The Berryville site is just S of the city on top
of a pole at a substation pole adjacent to the American Legion giving it
limited range. I suspect that error triggered additional errors in the short
listing. In addition, location numbers in the database are just the FCC numbering
of locations and are not properties of the system itself (thus of no value).
RVEC does number the sites by the system code which are not the same numbers.
Finally, RVEC does not use the "region-site" breakout given in the list
(the numbered regions implied are non-existent) which is derived from
the system code which is why there is no 1-1 listubg in RR. (The FCC itself
does not list the actual frequencies due to it being auctioned blocks.)
All sites were visited to make the table below using control channel monitoring.
Tait III DMR (2 TDM channels on each frequency), Color code 0. Callsign is WRBV929
for 217.000-217.500 frequencies and WRMM943 for 217.500-218. Some frequencies
are used by more than site. Input frequencies for the repeaters are 2 MHz higher.
System code site number-Location-Frequency(channel number)c=control channel
1 Fredericksburg (Spotsylvania Co.) 217.63125(103c/104) 217.70625(115/116)
2 Bowling Green (Caroline Co.) 217.69375(113c/114) 217.76875(125/126)
217.84375(137/138)
3 Blakey Ridge/Banco (Madison Co.) 217.66875(109c/110) 217.74375(121/122)
217.81875(133/134) 217.89375(145/146)
217.96875 (157/158)
4 King William (King William Co.) 217.53125(87/88) 217.60625(99/100)
217.71875(117/118) 217.79375(129c/130)
5 Mineral (Louisa Co.) 217.65625(107c/108) 217.73125(119/120)
217.80626(131/132) 217.88125(143/144)
6 Dunbrooke (Essex Co.) 217.65625(107c/108) 217.73125(119/120)
217.80625(131/132)
7 Linden Mtn. #2(Warren Co.) 217.53125(87c/88) 217.60625(117/118)
217.71875(117/118)
8 Hogback Mtn.(Warren Co.) 217.51875(85c/86) 217.61875(101/102)
217.94375(153/154)
9 Berryville (Clarke Co.) 217.79375(129c/130)
10 Dawn/Hanover (Caroline Co.) 217.06875(13c/14) 217.29375(49/50)
11 Paytes (Spotsylvania Co.) 217.78125(127c/128) 217.85625(139/140)
12 Hustle/Loretto (Essex Co.) 217.15625(27c/28) 217.26875(45/46)
(Sorry about the above format, it looks nice until you hit "Save" and RR deletes
the added blanks to line up the table nicely.
I have gone to Berryville twice for over an hour each time; but only the control
channel was active. I have not seen 217.85625 listed in the database
used at Fredericksburg ; but I have seen it at Paytes in Spotsylvania Co.
Someone else can go to the trouble to submit this to the database-I am too busy
with other projects.
(For those interested, the unused by RVEC region-site is found as in this example
for site number 6 (from 01.00000000.0110 in DSD+): 0110(bin)=6 (dec) -> 110 (bin)
-> 01 10 -> 1 2 -> 1+1 2+2 -> 2.3 or 2-3. But I emphasize the region-site numbers
given by this example and in RadioReference are *not* used by this system.)
incomplete, some of the associations of frequency sets are wrong. For
example,the listing there for Berryville is not Berryville but a different site
(being frequencies for Linden Mtn. #2 and those listed as Linden Mtn. #2 are
actually Hogback Mtn.) The Berryville site is just S of the city on top
of a pole at a substation pole adjacent to the American Legion giving it
limited range. I suspect that error triggered additional errors in the short
listing. In addition, location numbers in the database are just the FCC numbering
of locations and are not properties of the system itself (thus of no value).
RVEC does number the sites by the system code which are not the same numbers.
Finally, RVEC does not use the "region-site" breakout given in the list
(the numbered regions implied are non-existent) which is derived from
the system code which is why there is no 1-1 listubg in RR. (The FCC itself
does not list the actual frequencies due to it being auctioned blocks.)
All sites were visited to make the table below using control channel monitoring.
Tait III DMR (2 TDM channels on each frequency), Color code 0. Callsign is WRBV929
for 217.000-217.500 frequencies and WRMM943 for 217.500-218. Some frequencies
are used by more than site. Input frequencies for the repeaters are 2 MHz higher.
System code site number-Location-Frequency(channel number)c=control channel
1 Fredericksburg (Spotsylvania Co.) 217.63125(103c/104) 217.70625(115/116)
2 Bowling Green (Caroline Co.) 217.69375(113c/114) 217.76875(125/126)
217.84375(137/138)
3 Blakey Ridge/Banco (Madison Co.) 217.66875(109c/110) 217.74375(121/122)
217.81875(133/134) 217.89375(145/146)
217.96875 (157/158)
4 King William (King William Co.) 217.53125(87/88) 217.60625(99/100)
217.71875(117/118) 217.79375(129c/130)
5 Mineral (Louisa Co.) 217.65625(107c/108) 217.73125(119/120)
217.80626(131/132) 217.88125(143/144)
6 Dunbrooke (Essex Co.) 217.65625(107c/108) 217.73125(119/120)
217.80625(131/132)
7 Linden Mtn. #2(Warren Co.) 217.53125(87c/88) 217.60625(117/118)
217.71875(117/118)
8 Hogback Mtn.(Warren Co.) 217.51875(85c/86) 217.61875(101/102)
217.94375(153/154)
9 Berryville (Clarke Co.) 217.79375(129c/130)
10 Dawn/Hanover (Caroline Co.) 217.06875(13c/14) 217.29375(49/50)
11 Paytes (Spotsylvania Co.) 217.78125(127c/128) 217.85625(139/140)
12 Hustle/Loretto (Essex Co.) 217.15625(27c/28) 217.26875(45/46)
(Sorry about the above format, it looks nice until you hit "Save" and RR deletes
the added blanks to line up the table nicely.
I have gone to Berryville twice for over an hour each time; but only the control
channel was active. I have not seen 217.85625 listed in the database
used at Fredericksburg ; but I have seen it at Paytes in Spotsylvania Co.
Someone else can go to the trouble to submit this to the database-I am too busy
with other projects.
(For those interested, the unused by RVEC region-site is found as in this example
for site number 6 (from 01.00000000.0110 in DSD+): 0110(bin)=6 (dec) -> 110 (bin)
-> 01 10 -> 1 2 -> 1+1 2+2 -> 2.3 or 2-3. But I emphasize the region-site numbers
given by this example and in RadioReference are *not* used by this system.)
Last edited:
TJX400
Member
Great information, thank you for sharing! I had a feeling there had to be additional sites.
- Joined
- Dec 19, 2002
- Messages
- 2,135
I noted a typo in my posts... I repeatedly typed "RVEC" when I meant "REC" but caught it too late to fix. (It was caused by being a member of "RVARC").
Last edited:
That would explain why I was never able to catch the LCN or whatever it is called for that frequency a few years ago. Got the data for the other two Fredericksburg frequencies.
- Joined
- Dec 19, 2002
- Messages
- 2,135
The "whatever it is called" is the channel number. For REC, you can convert it to a frequency as follows:
1. If it is even, then let x=that number
2. If it is odd, then let x=that number + 1 (the next even number)
Those two steps take care of the fact that this is two channel TDM so each frequency has two channel numbers (one odd channel number and the next even channel number).
3. Now calculate x*0.00625+216.98125
(yes, I figured that out myself.)
The Sentinel software refers to them as LCNs, but I was told they aren't real LCNs. I captured 51 and 57 for the two Fredericksburg frequencies. Even with that info, the trunking didn't work that great on my scanner, so I monitor the system in conventional mode. I pick up more traffic that way.
- Joined
- Dec 19, 2002
- Messages
- 2,135
You are seeing one number for both TDM channels on each frequency which actually the system identifies as two channels (it has two to identify which TDM channel on the frequency). It is showing 51 for the two TDM 103 and 104 in my list ( 217.63125 ) and showing 57 for the two TDM channels 115 and 116 in my list (217.70625). I have shown what DSD+ identifies as the channel numbers which includes identifying which TDM channel.
Note that if you add 1 your number and then double it and call that x, you can use my Step 3 in my email to get the frequency. Calling them "51" and "57" is just a different way to parse the bits but ignores the fact that each frequency is actually two TDM channels.
- Joined
- Dec 19, 2002
- Messages
- 2,135
I saw that some of the sites I posted (but not all) has been put in the database. Anyway, here is a map I made adding the site numbers and linking neighbors determined from the control channel to the map of sites on the FCC website (the FCC website does not include frequencies from auctions but only bands). 
Has anybody been receiving REC from the Fredericksburg site the last few days? I tried to listen following the storms yesterday but I haven't picked up anything. I figured they would be hopping with storm-related issues. Tried with both my SDS-100 and WS-1080.
CPerk
Member
Definitely I’m wondering same thing , I’m king william . Haven’t had signal on control channel since early May 2022
- Joined
- Dec 19, 2002
- Messages
- 2,135
They have reconfigured the system since my list earlier in the thread.
New control channels are at present (by true site number)
1 Fredericksburg 217.08125
2 Bowling Green 217.30625
3 Blakey Ridge 217.03125
5 Mineral 217.04375
7 Linden 217.06875
8 Hogback 217.05625
11 Paytes (Spotsylvania Co.) 217.16875
I will try to redo my earlier analysis next week to add in the other sites and frequencies.
(The seem to be moving the control channels to be closer together.)
Last edited:
- Joined
- Dec 19, 2002
- Messages
- 2,135
Note that I have now seen 3 voice channels for the Fredericksburg site--one is the other TDM channel on the control channel frequency and the other is the 2 TDM channels for 217.14375.
reconrider8
Member
are their any radios that will monitor that 217 dmr or is it all still dsdplus?
Ok, thanks dlwtrunked.
Yes, there are scanners that will monitor it. My SDS-100 has been able to receive it and my WS-1080 can also receive it. I know the TRX series of radios should be able to receive it, and possibly others. I will say that my experience is that for this particular system, the SDS-100 has worked better in conventional mode rather than trunking. And the Whistler scanners don't do true trunk-tracking on DMR. But you can definitely hear conversations with these scanners.
BM82557
Member
The only CC's I can "see" from my location matches dlw's post --
My 536HP picks them up well also
