Most of the time I use the PTT to stop the scan. It is not stopping the scan that is the issue, but rather when the audio / carrier stops prior to the Pause time out it jumps to the next channel in the scan list and waits for the time out to finish. If you just wait the scan will start up.F1RMB wrote: ↑Fri Apr 01, 2022 1:31 amHi,
which key are you using to stop the scan, PTT ?
I just tried with the same conditions, and it worls. As soon as I press the PTT key, the scan stops on the current channel.
As Colin mentioned, you have a 30s window to stop the scan to be able to stay on the current channel, as you selected "Pause" scan mode.
Cheers.
---
Daniel
I will try and explain an example: I have the scan running and it operates as you would expect. Now it comes on a repeater that is giving out its scheduled ID. This repeater does both Morse and voice for ID along with some small message, so it lasts apx 15 to 20 seconds. It finishes and the carrier and audio drop. The radio jumps to the next channel in the scan list. It stays on that next channel until the 30 second pause completes (apx 10 to 15 seconds) then the scan starts up and runs.
I have this happen on long repeater IDs and audio of operators using the repeaters.
The bottom line of this is occasionally when I go to respond I am NOT on the channel that paused the scan but rather the following channel in the listing. The result being I am calling out on the wrong channel.
This does not happen always and this is why I took some time to be sure of what was going on before posting about.
The best way I know of observing this is to have a zone of fairly active repeaters and start the scan during the busy time for them, which for me is during the morning and afternoon commutes as there are many mobiles that use the repeaters near me while going to and from work each day. I just watch the display and every so often I will see the scan stop on a dialogue or station ID and when the carrier drops it goes to the next channel in the zone / list and sits there until the 30 second pause completes. Trouble is that it does not do this every time, only once in awhile and I failed in coming up with a way to trigger this behavior every time.