• To anyone looking to acquire commercial radio programming software:

    Please do not make requests for copies of radio programming software which is sold (or was sold) by the manufacturer for any monetary value. All requests will be deleted and a forum infraction issued. Making a request such as this is attempting to engage in software piracy and this forum cannot be involved or associated with this activity. The same goes for any private transaction via Private Message. Even if you attempt to engage in this activity in PM's we will still enforce the forum rules. Your PM's are not private and the administration has the right to read them if there's a hint to criminal activity.

    If you are having trouble legally obtaining software please state so. We do not want any hurt feelings when your vague post is mistaken for a free request. It is YOUR responsibility to properly word your request.

    To obtain Motorola software see the Sticky in the Motorola forum.

    The various other vendors often permit their dealers to sell the software online (i.e., Kenwood). Please use Google or some other search engine to find a dealer that sells the software. Typically each series or individual radio requires its own software package. Often the Kenwood software is less than $100 so don't be a cheapskate; just purchase it.

    For M/A Com/Harris/GE, etc: there are two software packages that program all current and past radios. One package is for conventional programming and the other for trunked programming. The trunked package is in upwards of $2,500. The conventional package is more reasonable though is still several hundred dollars. The benefit is you do not need multiple versions for each radio (unlike Motorola).

    This is a large and very visible forum. We cannot jeopardize the ability to provide the RadioReference services by allowing this activity to occur. Please respect this.

EDACS Patches

Status
Not open for further replies.

dvkeane

Member
Joined
Mar 13, 2002
Messages
5
Reaction score
0
Location
Louisburg, KS
I am curious how a dispatcher on an EDACS system sets up a tg patch. Are the patches "pre-set" or do they have to do it manually, and can individual users be patched without the whole sub-fleet being affected. I am using Etrunker and this has me baffled. Thanks for any insights.

dk
 

smackdaddy

Member
Joined
Aug 31, 2001
Messages
101
Reaction score
16
Hey Dk,

Well I think there are several ways that patches can be setup. These are just from observations that I have made from watching etrunker...

I have seen patches pop up in e-trunker -
1. Patch defined.
2. Talkgroup 123 added to patch xyz.
3. Talkgroup 234 added to patch xyz.
4. Talkgroup 345 added to patch xyz.

The times on events 1-4 is all within one or two seconds. This tells me that the patch is pre-configured.

The other type of patch that I see is this:

1. Patch defined.
2. Radio xxx affiliates
3. Radio yyy affiliates

4. Talkgroup 123 added to patch xyz
5. Radio zzz affiliates
6. Radio aaa affiliates
7. Talkgroup 234 added to patch xyz.

This type of patch seems to come up gradually, and I believe these are manual patches initated on the dispatch console.

My understanding is that patches can only be started using entire talkgroups. The dispatcher adds talkgroups to the patch and all users who are on those talkgroups are interconnected.

I have also seen some rather interesting patches involving EDACS fleet wide talkgroups. One dispatcher seems to like doing this:

1. Patch defined.
2. Talkgroup 01-000 added to patch xyz.
3. Talkgroup 09-141 added to patch xyz.
4. Talkgroup 09-142 added to patch xyz.

This is a more interesting kind of patch. I think that in this situation:

a) Any user on 09-141 or 09-142 will receive and transmit into the patch.
b) Any user on 01-xxx talkgroups will hear the patch, it will override any local traffic on those talkgroups but they can't transmit back into the patch.

Some more interesting notes..

When using "scan" on an LPE-200, I have observed that you will not received patched audio from talkgroups that you are scanning.

For example, your display is showing TG 08-081, and scan is activated. Your radio is programmed to scan 08-082, 08-083.

If 08-082 is added to a patch, your radio will not lock into this as part of the scan. It will only open up and participate in the patch if you actually put the radio on that talkgroup directly.

If you want to scan patches, you will need to have the actual patch talkgroup ID in your radio (ie. 15-152 or whatever). This works for me, but it would be a pain if your system always uses patches.

Regarding Fleet-wide calls, I have observed fleet wide calls on an LPE-200 - it shows "FLEET" in the display instead of "GR xxxx".

I have encountered a couple of weird EDACS systems that are multi-zone. Instead of carrying a talkgroup on the same ID on each system, they patch them between different zones on different talkgroup ID numbers. For example in zone 1 the talkgroup is 11-081 and in zone 2 the same TG is 12-021. They are tied as a patch, which makes scanning the talkgroups a total pain in the butt if you are using an LPE. (Remember what I just said about scanning across patches).

Digital / analog talkgroups and patches...

I have also seen digital talkgroups patched with analog groups. This has always caused the patch to drop to analog to accomodate the analog users. There may be other options, but I suspect that this is pretty common.

Well that's about it, those are purely my observations. Maybe other systems do it differently. I'm sure there are rules / exceptions that I'm not aware of.

Cheers!
SD.
 

WayneH

Forums Veteran
Super Moderator
Joined
Dec 16, 2000
Messages
7,555
Reaction score
95
Location
Your master site
I can't comment on how patches are initiated by a dispatcher but I'm guessing it's the same as for Motorola.

Anyway, once a patch is declared an alias of sorts is announced. All groups included in the patch are given a referrer of sorts to the new patch id.

Patch ids, where a new groups appears typically happen at the very bottom of the group numbering scheme or at the very edge.

Pretty simple all in all.
 

CSHIFTLT

Member
Feed Provider
Joined
Oct 12, 2001
Messages
178
Reaction score
0
Location
Henry
I do not know what you mean by tg, but the understanding of the patches we use are in 2 forms auto and manual,
The auto patch is only active when a valid user acquires the group that is pre detemined and that activates the patch example (state fire- edacs 800 group to 154.280) then when the user acquires a diffrent group the auto patch turns off.(or a predetermined amount of time)
The manual patch is active when dispatch combines 2 or more groups together on the console, but this cannot be in conjunction with the auto patch.
Edacs patches can be analog and/or digitial.
Of course convetional patch is analog on the conventional side but can be analog or digitial on the edacs side. (we have used both and it is better to make all conventional patches analog)

Hopefully this does not sound to confusing, it took me awhile to get m/a com to explain this.

p.s. we run auto patch on 154.280, 463.125, 155.340, 154.905, 45.560 Henry county, GA
 
Status
Not open for further replies.
Top