SDS100/SDS200: Favorites Site Issue

[GregTec86]

I think I found a flaw. If you assign a quick key to sites you can toggle them on and off no problem.

If you turn all sites off I have not found a way of turning them back on unless I hook it back up to Sentinel.

Somehow it doesn't recognize the QK when they are all off but long as you toggle them ON/OFF and leave one on you can recover.

Again if you turn all off I haven't found a way to recover.

 

[werinshades]

I think I found a flaw. If you assign a quick key to sites you can toggle them on and off no problem.

If you turn all sites off I have not found a way of turning them back on unless I hook it back up to Sentinel.

Somehow it doesn't recognize the QK when they are all off but long as you toggle them ON/OFF and leave one on you can recover.

Again if you turn all off I haven't found a way to recover.

Are you using the proper key sequence? I have sites assigned to "department" quick keys 91, 92 for example. If I want to turn off the site assigned to quick key 91, the following sequence is needed:

11 (Favorite List)
(.) 0 (System)
(.) 91 (Department/Site Quick Key)
Yes/Enter

So it looks like this: 11.0.91 Enter

If you assigned a Quick Key to the same department and want to turn off only the department, it will also turn off the Site..

 

[dave3825]

Yeah, like @werinshades describes, I to have sites using the 90 - 99 qk slots on almost all my programmed systems. I have had all sites off and on without issue. Make sure you're entering the proper way as described above.

 

[werinshades]

Yeah, like @werinshades describes, I to have sites using the 90 - 99 qk slots on almost all my programmed systems. I have had all sites off and on without issue. Make sure you're entering the proper way as described above.

Great minds, think alike . Just to add, by using these methods, it doesn't effect scan speeds.

 

[GregTec86]

So I don't have QK for any system just Favorite List and Department/Site Quick Key.

Let's say I have favorite 0 on and there are 3 different sites for it.

I can toggle them on an off doing ..0 or ..1 or ..2

Using the same method I can't get any back on once they are all off.

 

[werinshades]

So I don't have QK for any system just Favorite List and Department/Site Quick Key.

Let's say I have favorite 0 on and there are 3 different sites for it.

I can toggle them on an off doing ..0 or ..1 or ..2

Using the same method I can't get any back on once they are all off

That's why it's always a good idea to utilize quick keys so you can isolate your listening needs. Try changing it up to how we described and see if that works.

 

[GregTec86]

So looks like you have to have a QK in for System to get the Department/Site Quick Key back on.

 

[werinshades]

So looks like you have to have a QK in for System to get the Department/Site Quick Key back on.

Assign a Quick Key to your Favorite List, System, Department and Site(s) if your trying to accomplish a specific goal. But, no flaws with the software in regards to this task.

 

[GregTec86]

Assign a Quick Key to your Favorite List, System, Department and Site(s) if your trying to accomplish a specific goal. But, no flaws with the software in regards to this task.

How not though?

If I only want to assign a QK to Department/Site Quick Keys (DQK) and nothing else I should be able to toggle them all on and off however I need.

Like I said I could get then on and off but if I turned them all off I couldn't get them back on.

 

[GregTec86]

I found this:

If you disable all System QKs or all Department/Site QKs in a Favorites List, you will need to use the full entry that includes the FL to enable the QK.
Example: 3.1.4 to re-enable Department/Site QK 4. (..4 won't work).

Seems like they could fix this. No reason why it can't work this way. Now I am forced to have a QK for everything.

 

[KevinC]

I found this:

If you disable all System QKs or all Department/Site QKs in a Favorites List, you will need to use the full entry that includes the FL to enable the QK.
Example: 3.1.4 to re-enable Department/Site QK 4. (..4 won't work).

Seems like they could fix this. No reason why it can't work this way. Now I am forced to have a QK for everything.

Unfortunately it's been that way since DMA was introduced.

 

[werinshades]

Now I am forced to have a QK for everything.

...as I've been saying, to perform the task you wish to accomplishment, you have to modify your programming.

 

[jtwalker]

I found this:

If you disable all System QKs or all Department/Site QKs in a Favorites List, you will need to use the full entry that includes the FL to enable the QK.
Example: 3.1.4 to re-enable Department/Site QK 4. (..4 won't work).

Seems like they could fix this. No reason why it can't work this way. Now I am forced to have a QK for everything.

I guess it could work if you only have one FL and one system, but I’d say that would be the exception. Department/site quick keys are not unique on the scanner rather subordinate to a system which is subordinate to a FL.

THIFW

 

[GregTec86]

Thanks everyone. Seems like the SDS was an unfinished flawed product that lost support and routine updates after the one guy died.

 

[werinshades]

Thanks everyone. Seems like the SDS was an unfinished flawed product that lost support and routine updates after the one guy died.

Not really. We'd like to see some firmware updates to improve performance, but as far as programming goes, it's been this way for a long time, way before UPMan passed away. The problem here is you'll have individuals saying "I don't use Quick Keys/ they're confusing/no need". Then others (like me), who perform my own programming, and utilize the information from Sentinel, but don't upload directly from the database, don't use location control, don't use zip code method, but instead self-program, use filters, use Volume Offsets, use Quick Keys and can really understand it better. I can't tell you all the "why it's like this or that", but can explain how to work with what we've been given. Good luck on this task, hope you get it to where you want it.

 

[jtwalker]

Thanks everyone. Seems like the SDS was an unfinished flawed product that lost support and routine updates after the one guy died.

Just because quick keys don’t work the way you think they should doesn’t make them flawed, and they have worked this way before SDS models were introduced.

But in general, you have a valid point about these scanners and the passing of UPMan.

 

[GregTec86]

Guess I was expecting something better than my PRO-106 and so far I'm not impressed. I feel like I just got a pretty color screen.

 

[jtwalker]

Guess I was expecting something better than my PRO-106 and so far I'm not impressed. I feel like I just got a pretty color screen.

One word … simulcast.

 

[werinshades]

Guess I was expecting something better than my PRO-106 and so far I'm not impressed. I feel like I just got a pretty color screen.

You have that for sure, but it's obvious you haven't really worked with the scanner's programming structure and everything I described above. The SDS scanners are way beyond where you came from, but the question I have for you is, did you do your homework before you purchased? It's easy to complain about a product if you're unfamiliar with it.

 

[GregTec86]

You have that for sure, but it's obvious you haven't really worked with the scanner's programming structure and everything I described above. The SDS scanners are way beyond where you came from, but the question I have for you is, did you do your homework before you purchased? It's easy to complain about a product if you're unfamiliar with it.

For example:

Hard to know how bad the volume range changes without having one in your hand. Hard to know how bad the squelch increments are without trying it yourself...I could go on.

Just because I may not know the details in an out of this series yet doesn't make me a consumer without a valid complaint.