I think its safe to submit 13629 as EFD Dispatch and 13635 as EPD Dispatch. I’m picking up the signal real good at my office near Richmond and Emery Rds in Warrensville Hts. I’m using a HP-1 with version 2.03 firmware. I’m finding that the old firmware works the best with the Marcs-IP system.
MARCS-IP ("New MARCS") Site and Talkgroup Discussion
Swipesy
Member
My reception for MARCS-IP on my PSR-500 and PSR-800 comes off of a YAGI pointed at the Chagrin Tower and Geauga Tower on Pekin Road. Maybe Euclid is not linked with those towers.
I got one hit off EPD for 3 seconds off the Cuyahoga co site(s) whereas I get Lakewood off Nimisila - like 40 miles away.
~~
Now getting EDP and EFD off Nimisila...
I am wondering if "Nimisila" is actually located somewhere else... ???
~~
Now getting EDP and EFD off Nimisila...
I am wondering if "Nimisila" is actually located somewhere else... ???
Last edited:
jpadley85
Member
I have confirmed the following based on my recording/logs.
13629 - Euclid FD Dispatch (Channel 1)
13652 - Eulcid FD Channel 2
13629 - Euclid FD Dispatch (Channel 1)
13652 - Eulcid FD Channel 2
Swipesy
Member
Ed I have wondered about Nimisia also. Does not make sense that I get so many hitsvhere in Western Geauga County off that tower. It makes me think that Nimisilia is sharing tower freq with other towers.
Why does the Nimisila site have two primary control channels listed .. could that be the problem ?
Could one of these be another tower . maybe Richfield ?
Just some thoughts ...
Could one of these be another tower . maybe Richfield ?
Just some thoughts ...
Swipesy
Member
I see what's going on with Nimisila and Cuyahoga County. The problem isn't two primaries in Nimisilla. That's perfectly fine, but odd looking. It just shows that both have been primary CCs at some time.
The issue you might be having is that the frequency 774.78125 is listed in both sites. It is listed as a control channel on Cuyahoga County and a voice channel in Nimisila.
This would only be a problem if the radio you are using needs the non-CC frequencies entered. I use CC-only mode, so I only have that frequency entered of the Cuyahoga site. If you have it as part of the Nimisila site, you are probably picking it up. You're really listening to the Cuyahoga site off the Richfield tower (most likely), but within your Nimisila site because of the inclusion of 774.78125 in its frequencies
If you can, only program the control channels for each site. That should clear things up.
Does that make sense?
The issue you might be having is that the frequency 774.78125 is listed in both sites. It is listed as a control channel on Cuyahoga County and a voice channel in Nimisila.
This would only be a problem if the radio you are using needs the non-CC frequencies entered. I use CC-only mode, so I only have that frequency entered of the Cuyahoga site. If you have it as part of the Nimisila site, you are probably picking it up. You're really listening to the Cuyahoga site off the Richfield tower (most likely), but within your Nimisila site because of the inclusion of 774.78125 in its frequencies
If you can, only program the control channels for each site. That should clear things up.
Does that make sense?
Last edited:
The reason why any non-simulcast site has one or 3+ control channels listed, or multiple primaries, is because somebody in that area won't fire up Unitrunker or Pro96Com and get updated, accurate information and submit it to the DB.
All non-simulcast sites have two CCs [except for maybe correctional sites, which may be set up different]. Pretty much a general rule though that non-simulcast MARCS and MARCS-IP sites have two control channels. Anything less in the DB means we have incomplete information, and anything more in the DB means that people have submitted additional information over time just saying "blah is now the control channel" without runnning Unitrunker or Pro96Com and letting us know exactly wht the current CC/AC are.
So if anyone happens to be in an area where a non-simulcast site lists 1 control channel or 3+ control channels, please consider running a trunking program, gathering accurate information about that particular trunked site, and submitting an update.
There actually may be some sites in the DB now for which NONE of the control channels are correct. Many of the sites came online early on in the IP buildout, and they often used "temporary" frequencies. And those sites usually have updated FCC licenses specific to the site now. But if nobody checks with a trunking program to see if the information we have jives with what the control channel is spitting out, we'll never know if we need to make corrections.
This isn't a rant at you KWs -- it's a plea to everyone to consider checking out what the trunked site is telling you with Pro96Com or Unitrunker, and then letting us know if we need to update information.
Mike
Mike
W8RMH
Feed Provider Since 2012
Good idea about running Pro96Com.
I submitted updates for Franklin Co Simulcast, Bixby, and Discovery sites form Pro96Com.
I was not getting anything on Franklin Co Simulcast and found that it has 2 new CCs which were the old CCs taken from the FC service analog system - 857.6125 and 857.2625.
Pro96Com still shows 858.2625 as a Franklin Co Simulcast alternate control channel, yet at the same time I am receiving it as the new active control channel for the Service System.
I submitted updates for Franklin Co Simulcast, Bixby, and Discovery sites form Pro96Com.
I was not getting anything on Franklin Co Simulcast and found that it has 2 new CCs which were the old CCs taken from the FC service analog system - 857.6125 and 857.2625.
Pro96Com still shows 858.2625 as a Franklin Co Simulcast alternate control channel, yet at the same time I am receiving it as the new active control channel for the Service System.
I've found that when you get conflicting data like that, it's best to rename each site's file in Pro96Com [if you can find it -- it gets put in some stupid place I think], and then fire up Pro96Com and let it repopulate.
I'm not sure how good it is about _removing_ data that once existed but now isn't indicative of the current system state.
Mike
As for your Discovery submission, keep in mind that the only time non-CC/AC channels show up is when they are used [or in the case of the lowest channel on the site, when the CWID occurs]. So just because one frequency is listed in the DB but is not showing up on your end, it could simply be that you hadn't monitored Bixby long enough for that voice channel to be used. Sure, it could be that it isn't part of that site anymore, but it could just as easily be that you didn't sit on the CC and monitor long enough for activity to occur and so you didn't see it.
Mike
W8RMH
Feed Provider Since 2012
I picked up on that after I submitted it and started checking the other sites within range. First time I used Pro96Com since I got my HP-2.
Last edited:
W8RMH
Feed Provider Since 2012
859.2625 is still an AC on FC.
I'd appreciate it if you would answer my comments in your open tickets. Click on your username at the top of RR, then click on Submissions, and then review your open tickets that I own.
The more you say, the more confused I'm getting. we need to dialog in one place, not a little bit in the ticket and then a little bit here. I have to try to put all of those pieces together.
Thanks
Mike
W8RMH
Feed Provider Since 2012
I did. I will resubmit everything again when I get time and try to make it more clear.
I can confirm that TG 13664 is Euclid FD Ch-3. I'll submit.
I could use a second set of ears on 42011 and 42001 (two zeros vs two ones).
The DB currently lists 42011 as 72JDC, Sandusky County Juvenile Detention Center. This morning I'm getting traffic off the Cuyahoga County site on 42001 identifying itself as 72JDC.
Its probably just a typo in the DB. Hopefully, someone closer can help confirm the correct talkgroup ID.
The DB currently lists 42011 as 72JDC, Sandusky County Juvenile Detention Center. This morning I'm getting traffic off the Cuyahoga County site on 42001 identifying itself as 72JDC.
Its probably just a typo in the DB. Hopefully, someone closer can help confirm the correct talkgroup ID.