I live in Oakdale and using a PRO-96 I listen to Washington County Simulcast on 853.7375: SY40F T0105 BEE07 Site 005 Site DB ID:5827 Site NAC: N/A Lat: N44.99917 Lon: W-92.96278. The tower is just North of 34st (HWY 5) off of Hadley and the top of the tower would be line of sight with my location if not for trees
On the Armer-Site-Map-2016-10-01.pdf it shows a lot of tower sights with ID’s as “Z-1:S-5-7”. What do these ID’s signify and which one corresponds to the tower listed above?
On RR looking at the System Frequencies Names I see 29 sites that are listed as Simulcast. All say “Site Location: Various Minnesota”, some have specific Lat/Lon locations and others are not so specific, but some also have “Site Location: Simulcast 2 towers; Downtown Minneapolis and Downtown St. Paul” (Minneapolis City Center for example), or “Site Location: Citation Cable/Lino/Bethel/Stacy” (Anoka Co. for example). So where specifically are these sites (towers?) and are the frequencies listed for this site all being transmitted from this site (tower)?
Using Pro96Com decode Control channel 853.7375 data stream I see:
Site Information > Adjacent Site Information:
Site ID SysID CH Frequency Related To
101(T0101) 40F 00-1477 860.23750 Minneapolis City Center Simulcast
102(T0102) 40F 00-0381 853.38750 Anoka Co Simulcast
103(T0103) 40F 00-0409 853.56250 Dakota Co Simulcast
106(T0106) 40F 00-0233 852.46250 Chisago - Isanti Simulcast
192(T015C) 40F 00-0597 854.73750 Rush City – Prison 092 (5C) Chisago
196(T0160) 40F 00-0307 852.92500 Lino Lakes – Prison 096 (60) Anoka
197(T0161) 40F 00-1285 859.03750 Oak Park Heights – Prison 097 (61) Washington
199(T0163) 40F 00-1357 859.48750 Stillwater – Prison 099 (63) Washington
203(T0203) 40F 00-0173 852.08750 Ramsey County Simulcast 003 (3) Ramsey
214(T020E) 40F 00-0513 854.21250 Plymouth - Statewide Temp 014 (E) Statewide
340(T0328) 40F 00-0067 851.42500 Goodhue Co. Simulcast 040 (28) Goodhue
Note that of the 11 Adjacent Sites only 6 are Simulcast sites so that says that non-simulcast sites can be linked with a simulcast site?
I thought simulcast meant for example that if a unit in Dakota Co. wanted to communicate with the Washington Co. TG 3750 (WA Fire N) it could go through the Dakota Co. system and the communication would be simulcast over both sites on the sub frequencies related to each site so each can hear. So if I was monitoring WA Fire N on Washington 853.2625 I would be switched to a sub frequency and hear it, or if monitoring WA Fire N on Dakota 853.5625 I would be switch to one of their subs and would hear it as well. So where (how) do the non-simulcast sites in the above list relate to being heard on the Washington Co. data stream?
I have one bank in the PRO-96 with Washington Co. CC and the Washington Co. TG’s I want. I also have these same TG’S in another bank with the Dakota Co. CC. On Dakota I only hear some of my Washington TG’s, it’s not like all of them that are being transmitted on Washington are also being transmitted (simulcast?) on Dakota.
With our ARMER system does “Simulcast” mean simultaneous transmission of the audio/data on -multiple- frequencies, on multiple tower sights? Or does it mean the audio/data on the –same- frequency, on multiple tower sights?
For a few years now I have been playing with a SDR DVB-T USB stick receiver, BCD396XT, and PRO-96. I never had any luck getting a good audio decode with the SDR, the BCD396XT was fair during the winter and very poor during the summer, and the PRO-96 was poor all the time. I recently pulled the PRO-96 off the shelf and did the VR4 adjustment, now I’m getting 70%-98% decoding and 99% clear audio on Washington Co. so I’ll see what it’s like come spring. Obviously my problem with the first two were more of a signal issue than a hardware, the PRO-96 was hardware. As for listening to the Washington Co., if the site referred to above (T0105) is the –only- source for the frequency my radio is receiving then most likely my summer decoding problem is due to multipath vs the radio(s) hardware and the natural capture effect of FM if multiple on frequency signals are present.
Tnx for any comments.
George
On the Armer-Site-Map-2016-10-01.pdf it shows a lot of tower sights with ID’s as “Z-1:S-5-7”. What do these ID’s signify and which one corresponds to the tower listed above?
On RR looking at the System Frequencies Names I see 29 sites that are listed as Simulcast. All say “Site Location: Various Minnesota”, some have specific Lat/Lon locations and others are not so specific, but some also have “Site Location: Simulcast 2 towers; Downtown Minneapolis and Downtown St. Paul” (Minneapolis City Center for example), or “Site Location: Citation Cable/Lino/Bethel/Stacy” (Anoka Co. for example). So where specifically are these sites (towers?) and are the frequencies listed for this site all being transmitted from this site (tower)?
Using Pro96Com decode Control channel 853.7375 data stream I see:
Site Information > Adjacent Site Information:
Site ID SysID CH Frequency Related To
101(T0101) 40F 00-1477 860.23750 Minneapolis City Center Simulcast
102(T0102) 40F 00-0381 853.38750 Anoka Co Simulcast
103(T0103) 40F 00-0409 853.56250 Dakota Co Simulcast
106(T0106) 40F 00-0233 852.46250 Chisago - Isanti Simulcast
192(T015C) 40F 00-0597 854.73750 Rush City – Prison 092 (5C) Chisago
196(T0160) 40F 00-0307 852.92500 Lino Lakes – Prison 096 (60) Anoka
197(T0161) 40F 00-1285 859.03750 Oak Park Heights – Prison 097 (61) Washington
199(T0163) 40F 00-1357 859.48750 Stillwater – Prison 099 (63) Washington
203(T0203) 40F 00-0173 852.08750 Ramsey County Simulcast 003 (3) Ramsey
214(T020E) 40F 00-0513 854.21250 Plymouth - Statewide Temp 014 (E) Statewide
340(T0328) 40F 00-0067 851.42500 Goodhue Co. Simulcast 040 (28) Goodhue
Note that of the 11 Adjacent Sites only 6 are Simulcast sites so that says that non-simulcast sites can be linked with a simulcast site?
I thought simulcast meant for example that if a unit in Dakota Co. wanted to communicate with the Washington Co. TG 3750 (WA Fire N) it could go through the Dakota Co. system and the communication would be simulcast over both sites on the sub frequencies related to each site so each can hear. So if I was monitoring WA Fire N on Washington 853.2625 I would be switched to a sub frequency and hear it, or if monitoring WA Fire N on Dakota 853.5625 I would be switch to one of their subs and would hear it as well. So where (how) do the non-simulcast sites in the above list relate to being heard on the Washington Co. data stream?
I have one bank in the PRO-96 with Washington Co. CC and the Washington Co. TG’s I want. I also have these same TG’S in another bank with the Dakota Co. CC. On Dakota I only hear some of my Washington TG’s, it’s not like all of them that are being transmitted on Washington are also being transmitted (simulcast?) on Dakota.
With our ARMER system does “Simulcast” mean simultaneous transmission of the audio/data on -multiple- frequencies, on multiple tower sights? Or does it mean the audio/data on the –same- frequency, on multiple tower sights?
For a few years now I have been playing with a SDR DVB-T USB stick receiver, BCD396XT, and PRO-96. I never had any luck getting a good audio decode with the SDR, the BCD396XT was fair during the winter and very poor during the summer, and the PRO-96 was poor all the time. I recently pulled the PRO-96 off the shelf and did the VR4 adjustment, now I’m getting 70%-98% decoding and 99% clear audio on Washington Co. so I’ll see what it’s like come spring. Obviously my problem with the first two were more of a signal issue than a hardware, the PRO-96 was hardware. As for listening to the Washington Co., if the site referred to above (T0105) is the –only- source for the frequency my radio is receiving then most likely my summer decoding problem is due to multipath vs the radio(s) hardware and the natural capture effect of FM if multiple on frequency signals are present.
Tnx for any comments.
George