BCD396XT inter system delays

[scannermn10]

Hi,
Ive read that there is a delay when moving between
systems on this scanner. Does this apply to moving between the same system type or just between
different aystem types (conventional to p25)? What is
the amount of time when moving to a new system?

Thanks

 

[dave3825]

Set Hold Time sets (in seconds) the amount of time the scanner will scan the system before moving on to the next (unlocked) system. If you select 0 for trunking systems, the scanner stays on the system for at least 1 second. For conventional systems, all unlocked channels will be scanned at least once regardless of this setting. The scanner moves to the next system after the hold time expires, any current transmission ends, and the channel delay time expires. The default setting is 2 seconds for each system. Tip: set your systems to 0.

Scroll to 'Set Hold Time' and press E/yes. Enter the hold time (0-255 seconds) you desire and press E/yes to save and exit.

Set Delay Time for the system sets (in seconds) the amount of time the scanner stays on a channel after the transmission has ended before resuming scanning. This setting applies to all channels in the system. You cannot set the delay on a 'per channel' basis. The default setting is 2 seconds.

Scroll to 'Set Delay Time' and press E/yes. Scroll to the desired delay time (1-5 seconds or Off) and press E/yes to save and exit

 

[scannermn10]

Thanks, while I understand the hold and delay times, my question was about the scanners built in delay in moving to a new system.

For example, regardless of the delay and hold times, after they end how many seconds does it take to move from a existing p25 system to a conventional system? (It was mentioned online to
have the fewest systems to reduce delays going between systems).

 

[ofd8001]

after they end how many seconds does it take to move from a existing p25 system to a conventional system? (It was mentioned online to
have the fewest systems to reduce delays going between systems).

I have not noticed any delay when going from one system to the next system, as long as there is not a hold time for systems.

I suspect the perceived delay occurred when when someone setting a Hold Time for their systems. So if there were 10 systems with each having a hold time of 6 seconds, it would be nearly one minute before reaching the last system in line. But if there were just 5 systems, that brings the "full circle" time down to 30 seconds.

If you are listening to the Minnesota ARMER System in the Twin Cities, you may want to have a low or 0 System Hold Time. That's because of the number of Systems (actually subsystems) associated with this area. (City Center, Hennepin East, West, Minneapolis, Ramsey, and so on.

Are you having much garble/audio cutout with the 396 on the ARMER system? (I was frustrated when visiting family up that way with my x96 scanners and the simulcast distortion). However you might be lucky to be situated near a tower and not have to contend with simulcast distortion.

 

[GTR8000]

By default, the scanner "dwells" on each site's control channel for 2 seconds. If it didn't dwell for at least that much time, it would never be able to catch voice grants. This is completely normal and expected behavior.

 

[wtp]

for any trunking system, the radio does 'housekeeping' for 2 seconds no matter what the hold time is set to.
so, like GTR8000 said it has to listen and see what is going on.