Walton County Fire - Rescue (FL)

[caterpillar16]

I have pulled in the SLERS frequencies from the database for all of the towers in my area. I am yet to hear any radio traffic. I was under the impression the WCFR traffic was not encrypted. I am using as SDS100. Does anyone know for sure if they operate in the clear?

 

[Enforcer52]

Did you also get the TGIDs for Walton county? If you only pulled the tower frequencies you are not going to receive any of the TGIDs. Fire TGIDs are in the clear.

List shows 5 towers in Walton county.

 

[caterpillar16]

Yes, I have those pulled in also.

 

[Enforcer52]

You using the antenna that came with the scanner or an outside antenna. If factory antenna and you are trying to receive inside a residence, take the scanner outside and see if it picks up. Also squelch set to 2.

With 5 towers around the county you should be picking up the Fire Dept.

EDIT: Do you have Walton and Okaloosa County towers programmed in? The Mossy Head tower is the only tower that covers Crestview.

 

[caterpillar16]

I am only attempting to listen when passing through Walton County. I do have the Walton County and Okaloosa towers loaded. I can't remember the exact antenna I have, but it is a Remtronix that I recently replaced the stock antenna with.

 

[Enforcer52]

Do you have the ProVoice upgrade? Database says following:

System Notes​

The new state system is DES ProVoice with ESK and Extended Addressing.

 

[caterpillar16]

Yes, I ran the PV upgrade a few weeks ago.

 

[Enforcer52]

I imported the system into ProScan directly from the database (see image below).

I immediately noticed that the TGIDs pulled in completely different than the TGIDs listed when you view the database. Not sure what that means as I am not familiar with ProVoice. Maybe someone who is can jump in and explain why the TGIDs are different.

You might want to try what is pulled from the database just to see.

 

[Enforcer52]

Here is a .hpe file to try with what was pulled from the RR database.

 

[caterpillar16]

I have TGs 20753 - 20757 programmed in using ProScan. Are you thinking these are wrong? Where did you get those other TG IDs? I don't see them in the RR DB.

 

[Enforcer52]

The RR database showed me the TGs of 1300 and 20573-20757. But when I downloaded the SLERS system with ProScan the TGs were changed. I just downloaded the system again to check if there was a glitch, and it came across the same.

Did you enter the TGs manually? I am thinking you did since you are not a subscriber. If so unzip the file and try importing the .hpe file I sent you, and see if that starts receiving.

 

[caterpillar16]

No, I haven’t entered anything manually. I’m not seeing those other talk groups in the RR database. Basically I pulled everything into the radio using sentinel and then I edited out the stuff I don’t want using ProScan.

 

[Enforcer52]

I checked, Sentinel does show the TGs in the 20000 series, but Proscan pulls in different TGs. I would import the .hpe file I sent and add it to the programming and see if it picks up. If it doesn't work you can always delete it.

You can use either program to import the file.

Hopefully someone from your area will chime in that is familiar with the system setup.

 

[caterpillar16]

I’ll give that a shot. Thank you!

 

[caterpillar16]

Just loaded your file. I’ll give it a shot next time I’m in that area.

 

[Enforcer52]

Let me know if it works.

 

[RMason]

I immediately noticed that the TGIDs pulled in completely different than the TGIDs listed when you view the database. Not sure what that means as I am not familiar with ProVoice. Maybe someone who is can jump in and explain why the TGIDs are different.

It looks like the TGIDs are being converted from DEC format to AFS Format during the process of importing the RR data into Proscan. However, I am not convinced that the conversion from DEC to AFS shown in Proscan is correct for the extended addressing - TGIDs over 2047.

The system notes for this system indicate that this system is DES ProVoice with ESK and Extended Addressing. Plain EDACS can uniquely identify just over 2000 talkgroups. Extended addressing provides unique IDs for over 65000 talkgroups. I am not 100% convinced that the conversion from DEC to AFS shown in Proscan is correct for the extended addressing - TGIDs over 2047. For example, multiple talkgroups in the imported data are converted to 10-021. So, something looks to be amiss. It is interesting to note that when I look at this system in Sentinel, the TGID for 1300 is converted to 10-024. The other TGIDs are shown in DEC format.

I suggest that the OP enable ID Search to see what TGs are active. Hopefully someone from your area will chime in who is familiar with the system setup.

 

[ProScan]

I imported the system into ProScan directly from the database (see image below).

I immediately noticed that the TGIDs pulled in completely different than the TGIDs listed when you view the database.

Good catch. It's fixed in the next release.

 

[ProScan]

It looks like the TGIDs are being converted from DEC format to AFS Format during the process of importing the RR data into Proscan. However, I am not convinced that the conversion from DEC to AFS shown in Proscan is correct for the extended addressing - TGIDs over 2047.

The system notes for this system indicate that this system is DES ProVoice with ESK and Extended Addressing. Plain EDACS can uniquely identify just over 2000 talkgroups. Extended addressing provides unique IDs for over 65000 talkgroups. I am not 100% convinced that the conversion from DEC to AFS shown in Proscan is correct for the extended addressing - TGIDs over 2047. For example, multiple talkgroups in the imported data are converted to 10-021. So, something looks to be amiss. It is interesting to note that when I look at this system in Sentinel, the TGID for 1300 is converted to 10-024. The other TGIDs are shown in DEC format.

I suggest that the OP enable ID Search to see what TGs are active. Hopefully someone from your area will chime in who is familiar with the system setup.

Regarding ProScan EDACS systems: Should the TGIDs 2047 and under be converted to AFS and over 2047 not converted?

 

[ProScan]

ProScan now imports same as Sentinel which is like this.