Closed Mode MOT: bleed over

Status
Not open for further replies.

royalzapper

Member
Joined
Apr 17, 2004
Messages
80
Reaction score
1
Location
Hamilton County [Ohio]
We have a Digital Scanner Team located in Hamilton County, Ohio
that meets weekly and have set up a Cloning program that is shared
weekly with our local Radio Shack Stores.

The Hamilton County, Ohio TRS System is programmed in the PRO-96
and the PRO-2096 using the Win 96 Software.

Hamilton County TRS (APCO-P25 9600 baud)
System Type: Project 25 Standard
System Voice: APCO-25 Common Air Interface Exclusive

When the Radio is functioning correctly (In the Open Mode),
the Radio always stops on all transmissions except those you
specifically locked out. The display shows MOT: ID # of talkgroups
that are not stored in the Radio’s ID list. If the transmission is
that of a stored talkgroup, Radio will display the Alpha Tag.

When the Radio is functioning correctly (In the Closed Mode),
the Radio only stops on the transmissions and displays its Alpha Tag
of talkgroups that have been stored in the Radio’s ID list. You will
not receive transmissions of talkgroups you have locked out.

Showing on Radio Display,
When in Scan Mode under the Bank # Open Mode (+) Closed Mode (-)

We are aware of this function changing from Alpha Tag Display
to ID # Display.
By default, your Radio displays the stored Alpha Tag when receiving a
talkgroup transmission. You can toggle the display to show the Alpha
Tag or the talkgroup ID # by pressing TEXT while the radio is stopped
on a talkgroup transmission.

We have found some PRO-96 and PRO-2096 units that have a problem!

Lets call this problem "Closed Mode MOT: bleed over".

Banks are in Closed Mode but function as if they are in Open Mode!

The Radio will show stored Alpha Tags and receive transmissions of
the stored talkgroups.

When the Bank is set up in the Closed Mode, the problem is receiving
transmissions of talkgoups that haven’t been programmed in the
Radio’s ID list. The Radio will display the MOT: ID #.
Also if you lockout this MOT: ID # that was displayed, the Radio will
lockout a different talkgroup that is stored in the Radio’s ID list,
and doesn’t enter or lockout the MOT: ID # that was shown on the
display.

When the Radio is functioning correctly (In the Closed Mode),
You should never have MOT: ID # on the display and receive a
transmission of a talkgroup that is not stored in the Radio’s ID
list.

Would like to know if others are aware of … or having this problem!
Maybe this is only a local problem!

royalzapper

:arrow: add to this post on 7/22/2005

If you reply to this post
Please advise what type of Trunking System
is programmed in you Radio?

36 or 96 baud and give the name of the system.

Turn your Radio on & During Welcome screen display press the 3 button
What is your CPU, DSP application and DSP vocoder versions

Display will show
CPU: F1.3
DSP-App: F1.2
DSP-Voc: F1.0

We have seen this problem on CPU 1.2,1.3 & 1.4

royalzapper
 

Al42

Member
Joined
Apr 29, 2005
Messages
3,457
Reaction score
0
Location
Long Island, NY, USA
royalzapper said:
When the Bank is set up in the Closed Mode, the problem is receiving transmissions of talkgoups that haven’t been programmed in the Radio’s ID list. The Radio will display the MOT: ID #.
Also if you lockout this MOT: ID # that was displayed, the Radio will
lockout a different talkgroup that is stored in the Radio’s ID list,
and doesn’t enter or lockout the MOT: ID # that was shown on the
display.
This is probably the point that gives it away.

Next time this happens, note down the TGID that's being received, and the TGID that gets locked out. (Do it for a few different ones.) I'm willing to bet that the one that gets displayed has status bits set, and the one that gets locked out is the same TGID with no status bits.

Divide the TGID# by 16. A TGID that gets monitored even though it's not programmed (in closed mode) will not be evenly divisible by 16. Multiply the whole number of the result by 16 and you'll have the real TGID - and the TGID that gets locked out. (The difference between the two numbers is the sum of the status bits.)

This is just a guess, but let's see if I'm correct.
 

DonS

Member
Joined
Jun 17, 2003
Messages
4,099
Reaction score
-2
Location
Franktown, CO
Al42 said:
Next time this happens, note down the TGID that's being received, and the TGID that gets locked out. (Do it for a few different ones.) I'm willing to bet that the one that gets displayed has status bits set, and the one that gets locked out is the same TGID with no status bits.

Divide the TGID# by 16. A TGID that gets monitored even though it's not programmed (in closed mode) will not be evenly divisible by 16. Multiply the whole number of the result by 16 and you'll have the real TGID - and the TGID that gets locked out. (The difference between the two numbers is the sum of the status bits.)

This is just a guess, but let's see if I'm correct.

According to the original post, this is a P25 system. No status bits.
 

LFRfreak

Member
Joined
Jul 19, 2003
Messages
238
Reaction score
11
Location
Mount Juliet, TN
I Have The Same Problem

I have been having the exact same problem with my PRO-96 in Colorado. The system that I monitor is Motorola APCO-25 9600 baud, Common Air Interface Exclusive.

Here is what my radio shows:

CPU: F1.4
DSP-App: F1.2
DSP-Voc: F1.0

If we put our heads together, we just might be able to figure this one out!

-LFRfreak
 
Status
Not open for further replies.
Top