BCD436HP/BCD536HP: ATTN: UPMAN: FW 1.11.16: Custom search channel spacing is still wrong

[phyberoptics]

I just upgraded to FW 1.11.16, hoping the channel spacing glitch was fixed, but no.

The channel spacing glitch issue is this: the interval resets on 100 kHz increases which is absolutely wrong.

For example: Custom search 3, 15kHz spacing. Search from say 142.830 to 143 Mhz. Steps are:

142.830
142.845 Correct
142.860 Correct
142.875 Correct
142.890 Correct
142.900 Incorrect

Next step SHOULD be 142.905 but is instead
142.900 (WRONG).

If I scan in reverse, a valid channel of 142.725 gets missed.

142.830
142.815 Correct
142.800 Correct
142.790 Incorrect
142.775 Incorrect
142.760 Incorrect
142.745 Incorrect
142.730 Incorrect as 142.725 is a valid channel step and IC licensed, scanner would miss this on a custom search.

As a result, my searches get off track. I *could* use 5kHz stepping but why?

Can this please be addressed / explained?

Thank you!

 

[SOFA_KING]

Good catch!

It would appear everyone and everything is focused on DMR and Cap+ to the point of testing nothing else. If I were directing the testing, I would assign a tester to a limited set of test parameters, and not just a broad spectrum where anything goes. Naturally most testers would favor the new toy...DMR. But everything else, basic or not, still matters and has to be fully tested. Conventional, search, analyze, whatever.

Phil

 

[phyberoptics]

Yeah, I guess UPMan is too busy to see this.