TrunkView 2.0/BCD396T Incompatibilty

[subclavius]

You'll see a similar post in the Uniden section. I apologize for the cross-post, but I'm desperately looking for a fix for my scanner, and I also feel I should warn anyone with a 396 who is thinking of trying TrunkView 2.00.

Long story short, after running the band scan feature on TrunkView 2.0, my 396 now drops ANY signal every two seconds, for the duration of about half a second. This seems to be the interval the TrunkView band scan was controlling the receiver with, but now my 396 drops the signal every two seconds even when TrunkView is not being used.

Reloading the Uniden firmware and previous configuration hasn't fixed the problem. Now I'm off to the TV Yahoo group to see if they can help. Unless there's something I'm overlooking, I would STRONGLY recommend anyone with a Uniden 396T to stay away from TrunkView 2.00.

[subclavius]

I fixed the problem by reseting the scanner's memory. I think I'll lay off the MPT1327 stuff for a while................

[Saint]

Originally Posted by subclavius

I fixed the problem by reseting the scanner's memory. I think I'll lay off the MPT1327 stuff for a while................

Use Unitrunker for decoding MPT1327, it works perfect.
Steve

[DaveNF2G]

So you've posted two separate threads slamming a piece of software that is not at fault in your problem. Nice.

[morfis]

Originally Posted by Saint

Use Unitrunker for decoding MPT1327, it works perfect.
Steve

It might work reasonably well but Trunkview has a whole host of features that Unitrunker doesn't. I like Unitrunker for Motorola systems.

As for the original post.......I've been running TV with a 396T since the beta control for it was introduced and have had no problems with the radio.

[UPMan]

If audio was dropping every 2 seconds then either Close Call or Priority got turned on. Likely has nothing to do with the software (unless the software sent an erroneous command to turn on the feature).

[morfis]

Originally Posted by UPMan

If audio was dropping every 2 seconds then either Close Call or Priority got turned on. Likely han nothing to do with the software (unless the software sent an erroneous command to turn on the feature).

Trunkview initiates and starts a quicksearch - it does nothing to Close Call or Priority settings.

[Napalm]

Just to add to what Morfis said...

With a scanner that has a "front panel" and controls, there's no need to use Trunkview's Bandscan feature. Might as well initiate your own search from the controls on the radio - the radio's own search is much faster than TV anyway.

FYI's, I just ran the Bandscan from trunkview on my BCT-15 and neither CC nor Priority were enabled after I came out of the scan.

I'd politely suggest it was user error in this case.

[Unitrunker]

Originally Posted by UPMan

If audio was dropping every 2 seconds then either Close Call or Priority got turned on. Likely has nothing to do with the software (unless the software sent an erroneous command to turn on the feature).

Those were my thoughts too.

Originally Posted by morfis

It might work reasonably well but Trunkview has a whole host of features that Unitrunker doesn't.

TV most definitely does. UniTrunker provides basic decoding. Having the program control the radio that provides the control data so that the software knows the exact frequency of the current control channel would allow any program to do a better job of distinguishing two or more systems programmed with the same system ID - a common problem with MPT1327 systems. On of these days I'll get around to that.

[morfis]

Originally Posted by Unitrunker

.
..... allow any program to do a better job of distinguishing two or more systems programmed with the same system ID - a common problem with MPT1327 systems. On of these days I'll get around to that.

Is this a common problem in the US? My experience around Europe and the East has been otherwise.

I'll look forward to the Unitrunker version that incluses the features from TrunkView/PTrunk/Trunksniffer Pro and therefore to be able to use it exclusively

[Unitrunker]

Originally Posted by morfis

Is this a common problem in the US?

Must be. Lots of 2309 and/or 2319 system ids.

[morfis]

Originally Posted by Unitrunker

Must be. Lots of 2309 and/or 2319 system ids.

In the same radio area?

System Idents are re-used but not usually within the same geographical proximity.

Life would be easier if the sysid was allocated centrally like the Motorola ones - though I have never come across two systems with the same ID causing each other problems (limited monitoring of civvy stuff in the USA)

[Jay911]

Originally Posted by morfis

In the same radio area?

Yes; I described this back when I was using TV. 3 systems in my area (were) using 2319.

[morfis]

Originally Posted by Jay

Yes; I described this back when I was using TV. 3 systems in my area (were) using 2319.

Have you tried monitoring them with the most recent version of TV? It allows you to have multiple sites with the same ID but differing profiles and select the relevent one when monitoring.

(probably ought to be a separate thread now)

[pyeman99]

Originally Posted by morfis

Have you tried monitoring them with the most recent version of TV? It allows you to have multiple sites with the same ID but differing profiles and select the relevent one when monitoring.

(probably ought to be a separate thread now)

I'm using TV 2 ,no problem with 396 in UK works quite normally.
Set up as UP Man says.
Regards Keith.