BDC396T UASD Software-Group Quick key Disabling/Lockout

[steve_eg]

I'm hoping that it's something that I'm doing wrong, but I've noticed that locking out groups within systems using the quick keys doesn't seem to work too well. Has anyone noticed a slight "glitch" in the software when it comes to disabling groups within systems using the Group Quick Keys? Locking out systems by disabling the System Quick Keys works well, but then I have to go through the systems, to lock out unwanted groups.

Am I just missing something?

Outside of this, the software is great!

Thanks,

Steve

 

[BHinAZ]

Steve,

I am not sure if I totally understand the question, but the following may be what is happening since it appears you are thinking "lock out" and "disable" are the same thing.

Lock out and disable functions are independent of each other. Lock out can apply to any group, even if it is not assigned to a quick key. However, enable/ disable is used for activating/deactivating a quick key assigned group.

Locking out a group assigned to a quick key overrides the enable status for that quick key. In otherwords, you can have a group enabled, but it still will not scan if the group has been locked out. (This is also true for the system level.)

Here is what is confusing on the UASD software. The top of the Group maintenance screen has a check box titled Lockout, which is to the right of the quick key assignment box. A check mark in this box impacts the "lockout" status for the group, not the "disable" function. Since the Lockout check box is next to the quick key assignment box, one would think this is for the quick key disable function, but it is not.

The group quick key enable/disable status is carried in the UASD Configuration file, not the system database files.

To set the enable/disable status for a group quick key, you need to edit the Configuration file. Bring up the Config file, then select one of the tabs on the top that says Quick Keys. The displayed screen has a drop down list where you the select the system you want, then change the status (enable/disable) for the group quick key in question. You will need to know the group number ahead of time since the screen does not display the group alpha discription.

You can get a better understanding of how the lock out function differs from the disable function by playing with it in the scanner. Press menu and slect the programming function. Edit the group in question, and set the lockout on or off. Go back to scanning and you will notice the status of the group quick key line, where the "*'" or the group number is displayed, does not change.
Go back thru the menus to "unlock" the group.

The main point to all of this is that "lockout" and "disable" are independent of each other, and the "lockout" status overrides the "enabe" status for a quick key.

Once I figured this out, the software has been working as it should.

 

[steve_eg]

Thanks for the response-sorry I wasn't really clear when I asked the question. My using the term "lockout" might have confused the issue a bit, let me clarify-

When I go into the Configuration Editor, I (typically) select Systems 1,2,3,4,5 (I don't routinely turn on 0,6-12) unless I'm travelling in those areas).
In system 1, I turn on groups 1,2, and 0. 3 through 9 are other parts of the county that I don't usually monitor. (Again, unless I'm travelling out that way)

When I write it to the scanner, System 1 shows every group enabled, despite the fact that I only enabled groups 1,2 and 0. When I look in the usc file in Notepad, I see that it does appear the selected systems should be locked out:

=============
GroupQuickKeys,"IL StClairCo CNV",1100000001
=============

IL StClairCo CNV is my system, and the ones and zeros represent my groups, but when I write this configuration to the scanner, all groups are enabled.

This is occurring on all systems, I've only displayed this one as an example.

Am I missing something?

Thanks again,

Steve

 

[wolter]

Realize that every time you write a system to the scanner with the UASD, that particular system must either be deleted prior or the scanner must be reset.

So it is as if you're writing that system and its groups to the scanner for the very first time. Your enable/disable settings no longer exist. And there is no enable/disable group function in the software. Therefore, every time you write any system to the scanner, every group within that system(s) will be enabled.

 

[UPMan]

there is no enable/disable group function in the software

Actually, there is. It is on the "Quick Keys" tab in the configuration file.

 

[wolter]

You learn something new every day. . .

It does say that they are enabled by default unless it is included in the list.

 

[steve_eg]

That's just it-I disable the system Quick Keys that I don't want (this works fine). Then I select the individual system from the dropdown menu, disable those Group Quick Keys that I don't want, save the config and write it to the scanner (using the "erase" option) and when the scanner comes back online, I've got to go back through each system and manually disable the groups that I don't want to hear.

Thanks,

Steve

 

[whsbuss]

That's just it-I disable the system Quick Keys that I don't want (this works fine). Then I select the individual system from the dropdown menu, disable those Group Quick Keys that I don't want, save the config and write it to the scanner (using the "erase" option) and when the scanner comes back online, I've got to go back through each system and manually disable the groups that I don't want to hear.

Thanks,

Steve

I think the problem is a bug in the UASD software. When I manually program the scanner using HyperTerm I can disable the groups.

Here's the command (in PRG mode):

QGL, [sys-index], 1210000000

Notice the "2" in the group QKs. This disables the group.

If you look at the configuration file:

SystemQuickKeys,1110000001,0000111110,1111111111,1111111111,1111011111,1111111111,1111111111,1111111111,1111111111,1111111111
GroupQuickKeys,"Bucks Cnty MOT",1000111111

The SystemQuickKeys command (QSL) where 1=enable, 0=don't assign, and 2=* or turn off. Even though there are no "2" in the SystemQuickKeys command, when I manually do a QSL command I get

QSL,1111221220,2222000002,0000000000,0000000000,0000200000,0000000000,0000000000
,0000000000,0000000000,0000000000

However, when I do a QGL command for the GroupQuickKeys for the Bucks MOT system I get:

QGL,1111000000

When I manually enter QGL,[sys-index],1222000000

everything works correctly. Its possible the UASD program is sending a "1" instead of a "2" to program the QSL and QGL.

 

[whsbuss]

Here's a follow-up....

I edited the config file and changed the System and Group enable/disable bits to "2" and it works when I upload it to the scanner using UASD.

SystemQuickKeys,1112222221,2222111112,1111111111,1111111111,1111211111,1111111111,1111111111,1111111111,1111111111,1111111111
GroupQuickKeys,"Bucks Cnty MOT",1222111111
GroupQuickKeys,"Montg Cnty Conv",1211111111
GroupQuickKeys,"Montg Co East MOT",1111212111
GroupQuickKeys,"Montg Co West MOT",1112212111

 

[steve_eg]

That did the trick! I edited the usc file manually in Notepad (useful for everything from writing html to scanner maintenance), and that corrected it.

Thanks for the tip!!


On a side note, will this be corrected in a future release of the UASD app? Granted, it's not a big deal, and I'm sure the developers at Uniden have higher priority things going, but it'd be nice to know it'll work at some point.

Thanks again!


-Steve

 

[whsbuss]

That did the trick! I edited the usc file manually in Notepad (useful for everything from write html to scanner maintenance), and that corrected it.

Thanks for the tip!!


On a side note, will this be corrected in a future release of the UASD app? Granted, it's not a big deal, and I'm sure the developers at Uniden have higher priority things going, but it'd be nice to know it'll work at some point.

Thanks again!


-Steve

I hope so. UPMan usually reads this forum. Its definately a bug.

 

[loumaag]

Actually the problem is a little bigger than first reported. I decided to play a little bit and loo what happend.

I copied my "working" configuration file (the one I normally use) and called it Test.usc. I then loaded the software and pulled up Test for edit. All I did, because I wanted to be prompted to "Save" was change the Squelch setting by one digit. After saving my System Quick Keys were all wrong:

Before Save:
SystemQuickKeys,2122222200,0000000022,0000000202,0000000220,0000000000,
0000000000,0000000000,0000000000,0000000000,0000000000

After Save:
SystemQuickKeys,0100000000,0000000000,0000000000,0000000000,0000000000,
0000000000,0000000000,0000000000,0000000000,0000000000

(BTW, I broke those lines with a LF/CR so they would not cause scrolling, they are not broken in the files.)

 

[whsbuss]

Yep. I saw that too. You have to re-edit the config file to change it back again until a fix is made.