richster
Member
I would like to start off and say that the new firmware (v1.42) corrected the 246T dropping I-Calls. The 246T now scans, searches, and holds on any and all I-calls on both Motorola and EDACS systems with no drops. Bravo to Uniden on a job well done.
These are "quirks" I have found while dealing with I-Calls on an EDACS system only. The second quirk may occur on a motorola system as well, but I have not ran into a situation where I can test it. I-Calls on our local Motorola system are few and far between, so testing for this second quirk may take a while.
On our local EDACS system "Sasktel Fleetnet" I have 1500 radios and 350 groups logged with Etrunker. One of the MAJOR users of this system is our Provincial power company, Sask Power. Sask Power has around 30 talkgroups, but 90% of thier comms are I-Calls. The LID's for Sask Power range from 1000 to 1800, and I have logged almost 200 radios belonging to Sask Power in our area alone. I have started to identify and alpha-tag these Sask Power radios by thier name, and have created a new system just for these radios because there are so many. You can only have 200 groups and/or radio ID's per system.
This is the first quirk. Lets say LID 1000 is talking to LID 1400. LID 1000 is the Control Center, and LID 1400 is a guy named Mark. Well as the Control Center is talking, the 246T is displaying "Mark" instead. It seems when the 246T stops on an I-Call on an EDACS system, it displays the "target" LID instead of the person who is talking. This does get kinda confusing, but I'm starting to get used to it.
The second quirk is this. I have another system that is the exact copy of the Sask Power system, except it is made to track the talkgroups of "Sasktel Fleetnet", and other I-Calls that are not Sask Power. Obviously I have a group created with the "I-Call Wildcard .i00000". With this wildcard I receive all I-calls, incuding the Sask Power guys I have already indentified. Well I don't want to listen to Sask Power I-Calls, that's what the other system called Sask Power is for, so I figured if I see a Sask Power LID, I'll just lock it out. Well once you lock out that LID it doesn't actually lock out that LID, it locks out the wildcard .i00000 instead. It seems you cannot lock out "individual" LID's on a system that has the wildcard LID in it. It will lockout the .i00000 and not the exact LID.
I have found a way around this, and it seems to work. To track non-Sask Power I-Calls on "Sasktel Fleetnet", I created another system and set it to track I-Calls only. In group 1, I put in the I-Call wildcard. In group 2 I put in every Sask Power LID, and then locked out that 2nd group. This way I can receive all other I-Calls on the "Fleetnet" system without Sask Power I-Call interference.
So in summary this is how I have it set up to effectively listen to Fleetnet the way I want.
System 1 - Fleetnet with I-calls turned off. Programmed with around 80 Talkgroups (RCMP, EMS, Fire...etc)
System 2 - Fleetnet with I-calls only. Programmed with almost 200 Sask Power LID's, most of them alpha-tagged.
System 3 - Fleetnet with I-calls only. Programmed with the I-Call wildcard, and in another group those 200 Sask Power LID's with this group locked out. This enables me to listen to "Non Sask Power I-Calls only".
GASP! Well thats about it. Maybe in a future firmware upgrade (if there is another one), Uniden can at least fix the first quirk. Following who is talking is major task. Thanks for reading.
Regards,
Richster.
These are "quirks" I have found while dealing with I-Calls on an EDACS system only. The second quirk may occur on a motorola system as well, but I have not ran into a situation where I can test it. I-Calls on our local Motorola system are few and far between, so testing for this second quirk may take a while.
On our local EDACS system "Sasktel Fleetnet" I have 1500 radios and 350 groups logged with Etrunker. One of the MAJOR users of this system is our Provincial power company, Sask Power. Sask Power has around 30 talkgroups, but 90% of thier comms are I-Calls. The LID's for Sask Power range from 1000 to 1800, and I have logged almost 200 radios belonging to Sask Power in our area alone. I have started to identify and alpha-tag these Sask Power radios by thier name, and have created a new system just for these radios because there are so many. You can only have 200 groups and/or radio ID's per system.
This is the first quirk. Lets say LID 1000 is talking to LID 1400. LID 1000 is the Control Center, and LID 1400 is a guy named Mark. Well as the Control Center is talking, the 246T is displaying "Mark" instead. It seems when the 246T stops on an I-Call on an EDACS system, it displays the "target" LID instead of the person who is talking. This does get kinda confusing, but I'm starting to get used to it.
The second quirk is this. I have another system that is the exact copy of the Sask Power system, except it is made to track the talkgroups of "Sasktel Fleetnet", and other I-Calls that are not Sask Power. Obviously I have a group created with the "I-Call Wildcard .i00000". With this wildcard I receive all I-calls, incuding the Sask Power guys I have already indentified. Well I don't want to listen to Sask Power I-Calls, that's what the other system called Sask Power is for, so I figured if I see a Sask Power LID, I'll just lock it out. Well once you lock out that LID it doesn't actually lock out that LID, it locks out the wildcard .i00000 instead. It seems you cannot lock out "individual" LID's on a system that has the wildcard LID in it. It will lockout the .i00000 and not the exact LID.
I have found a way around this, and it seems to work. To track non-Sask Power I-Calls on "Sasktel Fleetnet", I created another system and set it to track I-Calls only. In group 1, I put in the I-Call wildcard. In group 2 I put in every Sask Power LID, and then locked out that 2nd group. This way I can receive all other I-Calls on the "Fleetnet" system without Sask Power I-Call interference.
So in summary this is how I have it set up to effectively listen to Fleetnet the way I want.
System 1 - Fleetnet with I-calls turned off. Programmed with around 80 Talkgroups (RCMP, EMS, Fire...etc)
System 2 - Fleetnet with I-calls only. Programmed with almost 200 Sask Power LID's, most of them alpha-tagged.
System 3 - Fleetnet with I-calls only. Programmed with the I-Call wildcard, and in another group those 200 Sask Power LID's with this group locked out. This enables me to listen to "Non Sask Power I-Calls only".
GASP! Well thats about it. Maybe in a future firmware upgrade (if there is another one), Uniden can at least fix the first quirk. Following who is talking is major task. Thanks for reading.
Regards,
Richster.
