University of Akron Trunked System (NEXEDGE48 - System ID 83)

[mtindor]

The SOE Patrols are done by a hired company called Block by Block. The link below tells all about it if you scroll down to the Off-Campus Patrol paragraph, with the map right above it with the area South of Exchange highlighted in blue.

https://www.uakron.edu/safety/annual-safety-report/police-authority.dot

Excellent. I was on that page four times today, but never made it down far enough to read that. I appreciate it.

Mike

 

[fpo701]

That's some good info. It make sense. I'll have to listen to the talkgroup a bit more. I could swear I've heard references to locations outside the blue section.

 

[mtindor]

Below is a list of what I've copied so far. PFOC always seem to switch people from TG 105 to their specific talkgroup after contact, at least for the most part. So PFOC will say "switch to COM2". Most of the time I am not listening, so I go by radio aliases in that case.

The list below is a combination of what is in the DB (originally discovered by FPO701) and what I have found as well as what LTR noted for SOE Patrol.

If it says "PFOC related" below, I have not personally heard the exact channel name referenced. But in some cases, Frank FPO701 did and thus the name that is in the DB.

TG 700 is listed as UAPD IO in the DB, because the radio aliases I'm seeing on that talkgroup all mention UAPD in some form or fashion. I'm sure they have access, but not for their everyday operations -- instead to interop with UAkron on UAkron's trunked systems. For instance, I bet they interop on TG 700 with SOE Patrol among others.

and EOHS1 and EOHS2 were not referenced by name. All the radio aliases on those talkgroups have 'EOHS' in them. I'm sure each is a little more specific to a task / department under EOHS.

5   unknown
10  unknown
15  SOE PATROL
40  EOHS 1
45  EOHS 2
70  PARKING ENF
85  CAMPUS SHUTTLE
105 PFOC MAIN
110 PFOC related - db says Electrical
115 PFOC related
120 PFOC related - db says HVAC
125 PFOC related - db says Custodial
130 PFOC related
140 PFOC related
150 COM1
155 COM2
170 PFOC related
175 unknown (aliases have Lock ##-##")
195 REC CENTER
200 ATHLETIC FACILITIES
205 ATHLETIC TICKETS
210 ATHLETIC TRAINERS
235 unknown
250 STUDENT UNION 1
255 STUDENT UNION 2
270 unknown - db says Dining
501 PFOC related - db says Ops
503 unknown
505 PFOC related - db says Painting
601 unknown
700 UAPD INTEROP
730 unknown (aliases have W-Maint##, Wayne###)
750 unknown (aliases have Wayne###)
800 unknown (aliases such as BERT 192)

Mike

 

[fpo701]

Mike,

All the ones you where you have "db says...." were caught by me. The first few days of monitoring the system, I had PFOC (105) unlocked. It was easy to catch the "go to xxx".

You'll also catch them saying "back to PFOC" at the end.

270 is only active during sporting events. I caught it during a football game. Radios were coming over as Dining xxx.

The rest has always been a mystery. The only way to ID the other PFOC talkgroups is to listen in ID SEARCH and have PFOC enabled. They always end with "back to PFOC". I just never catch the start of the conversation.

 

[Jphila20]

When programming a TRX-2, would the same rules apply as for a P25 system that only the control channels need to be entered or do all channels need to be entered? Would Akron U be the C or D type NXDN?
I think this is only NXDN in my area.

Happy Thanksgiving!

Thanks!

 

[jdolina]

For p25 you will only need the control channel(s) in the TRX-2

Looks like UA since there are multiple control channels listed would be type D. My understanding Type C has a dedicated control channel. Type D has multiple

 

[mtindor]

Looks like UA since there are multiple control channels listed would be type D. My understanding Type C has a dedicated control channel. Type D has multiple

Type C systems have an active CC at all times. It doesn't matter that it rotates. What matters is that there is a 24/7 control channel on one of the system frequencies - that's what makes it type C.

Type D has no 24/7 control channel activity. All relevant trunking information is sent on the voice frequencies during voice transmissions and when the voice channels beacon.

Thus, the UAkron NXDN system is Type-C.

Mike

 

[jdolina]

Thanks for the clarification, makes sense.

 

[mtindor]

Thanks for the clarification, makes sense.

I probably do not have the explanation 100% correct either. Taken from Kenwood's site:

NXDN Type-D Trunking is the FB6*-based digital LTR protocol specified by the NXDN Forum. Unlike Type-C trunking, there is no dedicated control channel: trunking is under the control of the home repeater assigned to each radio. And like LTR, there is no registration. This cost-effective solution thus offers spectrum efficiency and simplicity.​

I am not sure if voice channels beacon, and if they do I do not know what type of trunking information (if any) is sent at that time. Based upon what Kenwood's site says, the home repeater handles the trunking.

It's LTR-like. And given that it is LTR-like, I'm going to guess that any active NXDN Type-D frequency trunked frequency will send at least some amount of trunking information. LTR system low-speed data on active channels, regardless of channel, send information about which LCNs are Free (for use).

Mike