Odd Site Hold Behavior on both BCDx36HP and SDS100

[cellphone]

This issue appeared a few weeks back in one of the BCDx36HP firmware revisions. I notice it is also present in the SDS100. BCD436HP is firmware 1.23.00 and SDS100 is 1.03.01(main) 1.01.03 (sub).

Instructions for reproducing:
1. Ensure that at least one trunked system in your scan list is avoided.
2. Press channel hold
3. Press system, and start turning the selector knob before the timeout to hold on a system occurs. Keep turning the selector knob and try to advance past the system that is avoided.

You will get struck on the avoided system in a “Site Hold” condition.

-If you press function-site to release the site hold, the scanner will say “Site Hold off”. Then press channel to release the channel hold, the scanner is still in a “Site hold” condition.

This issue occurs if a trunked system is avoided, the scanner is NOT in a system hold state, and the scanner IS in a channel hold state.

Please chime in if you can reproduce.

 

[jonwienke]

I can reproduce this on the 436 (1.23.00) and the SDS100 (1.03.01/1.01.03).

On the 436, "Site Hold" is displayed, but no site hold is actually activated. You can resume scanning by releasing the channel hold.

On the SDS100, a site in the avoided system will be held, and you can't get off the system until you release the site hold and the channel hold.

Logically though, you shouldn't be able to scroll off a system until all channel, site, and department holds active for that system have been released. And you shouldn't be able to scroll off a department unless the channel hold has been released.

Stated another way, scrolling should be disabled if there is a hold active on any subordinate object in the system hierarchy.

 

[wm8s]

What I think must be a related one has burned me a couple of times. If you Channel Hold on a trunked system with talkgroups, and then try to <System> <rotate> through your systems, it will skip over Systems without any talkgroups like they're not there.

This produces odd behavior. For example, while scanning --- i.e., with Channel hold off --- several Systems, some of which have TGs and some of which don't [but which have ID Search on], and you do <System> <rotate>, you can rotate through all systems [i.e., even ones w/o TGs, which show "No Stored TGID" as you dial across them], as expected.

If you then stop rotating --- and thereby enable System hold --- on a System w/o any TGs, it will still be fine, scanning that system and displaying "No Stored TGIDs". But then if you Channel hold, and then <System> <rotate> CW one click then back CCW one click --- which one would think would take you back to the same System you had just left --- it will instead skip that System on the way back CCW [because it doesn't have any TGs].

 

[cistercian]

I saw that last night while fooling around with my sds100. I escaped by function>site>turn encoder.
Normal scanning resumed. at some point in my fooling around I was in a mode that showed every avoid
which listed every system in the state...which was tedious to escape from.

I am just learning it but the site hold bug was weird.

 

[LouieCT]

I saw that last night while fooling around with my sds100. I escaped by function>site>turn encoder.
Normal scanning resumed. at some point in my fooling around I was in a mode that showed every avoid
which listed every system in the state...which was tedious to escape from.

I am just learning it but the site hold bug was weird.

You just helped me so much, i was losing my mind trying to release the site hold.....Thank you!