I hope you don't mind my tasking you with catching this in a decode log. I can't see what you see.jpryor said:But even with Motorola and P25 I get extra channels at times that are not correct, from poor decode or some other reason.
To jpryor and edmscan ...
Please provide a decode log that spans the time that these bogus channels appeared.
I hope you don't mind my tasking you with catching this in a decode log. I can't see what you see.
edmscan - same goes for you.
Clearing bogus channels is incredibly easy (described in step #1 below). This has a short term benefit of addressing your immediate needs. Make sure you are not the source of bad data. Exercise care when switching your signal receiver from one site to another.
1. On the channels tab, sort the channels by hit count or First Seen time stamp. Valid channels will be much older and tend to have a higher hit count. Delete the channels you know do not belong.
2. Turn on decode logging and go about your day.
3. Check the site window periodically for any bogus channels. Make note of the First Seen time stamp of these channels.
4. Please email any *decode* logs that span that point in time.
Review the following to make sure you've enabled decode logging and not site logs or tuner logging.
UniTrunker | Log Files
The logs you provide might lead to a future bug fix or enhancement.
The logic changed slightly to be consistent across models. You'll have to choose and set a park frequency. At the end of each call, the '15X will move back to that frequency. With your current park frequency of zero, the step of returning to the park channel failed.Using the same set-up values, the parked frequency now shows as 0.00 and it doesn't pick up the initial 15X frequency on start-up.
We had this same conversation a few versions back. You should be able to upgrade while retaining your previously imported data. It shouldn't be necessary to repeat this process with each upgrade.davenf2g said:My trouble is that I am unable to import Trunker data into Unitrunker.
Does anyone have any thoughts .. running the latest version and my control channel refuses to move. It only is right when I start the program.
Using a PSR500 as a signal source but no voice following.
Monitoring an Edacs system. I know Rick .. Edacs. ;-)
Sorry.. Mine moves fine, but is not correct when I start the program.... Motorola.
What is "Chase" on your receiver window set to?
We had this same conversation a few versions back. You should be able to upgrade while retaining your previously imported data. It shouldn't be necessary to repeat this process with each upgrade.
I'll run through the import to see what I can find. As I've said previously, this feature does not see much use so it doesn't get tested with each release.
Release 30
P25
a. RR DB download of "zoned" P25 systems didn't retain all downloaded information.
b. Guard against unlikely (but actually happened) scenario where second TSBK of multi OSP passed the 16 bit CRC check but wasn't a single OSP message. The number in the "follow" TSBKs field was crazy high (100 or more) which caused problems downstream.
c. P25 issues monitor events.
I'm not sure what "P25 issues monitor events" are. Could you please provide a little more information?
Thanks!
DaveNF2G ..
I think Rick mentioned that as it is such a small amount of people that would use the import feature .. it was not high on the radar.
If you are interested .. send me a PM and I can give you my email address and you can send me your Trunker data and I will convert it for you into what Unitrunker will understand.
I don't know about the number of people. However, it does occur to me that, for most affected users, it is a feature that would only be needed once.
That was not the case for me as I chose to stick with the DOS trunkers until Unitrunker could handle everything they covered. It still can't, but my only remaining DOS computer is on its last legs.
I have OpenOffice here. If you have a script or macro that helps the process, I would be interested in seeing that.