Hey there Rick
I see you have a udate out looks good why no notice?
I see you have a udate out looks good why no notice?
Sorry Monty - you're too quick for me.why no notice?
Hi there
1) When I try to operate the SCOPE the software get stuck no scope screen apear
but in regular operation the software decode control channel
I think its sensitivity to noise is less good then the trunk88
controller that trunk88 can decode the unitrunker cant decode
Ronen - 4Z4ZQ
Ronen Pinchooks (4Z4ZQ) WebSite
For those who haven't installed the new vesion yet, a suggestion.
Keep the old version in a separate directory in case you need to go back. Copy your existing data files to the new version's directory so any problems won't screw up your data. After you've made sure the new version works ok for you, you can delete the old directory.
This tip applies to any software that does not update itself via the operating system's install utility.
I'll test this out. Do you end up with two systems?- In the following workflow: Hitting plus on the systems screen, entering the newly created "unknown" system, entering a SID, and downloading - the resulting downloaded system remains type "unknown". User has to manually change to the right system type.
This is partly by design. Anyone finding such a system in the DB - please submit the system ID, active control channel frequency and site number (if any) to the RR database. There are a few cases where the same system ID has been re-used so the program will eventually need to prompt the user to choose which system they want. That's on my TODO list. In cases like this where the SID was given explicitly - it should presume the user understands the consequences and carry out the request. I think the code assumes a system ID - and doesn't know what to do when there isn't one.Motorola systems in which the RRDB has no defined/specified system ID will not download. This may be as you intended; I know you can leave out the SID and download by Motorola sysid instead.
That's a bug.Went to my UT DB and opened that system (if I recall right, that's the RENIR P25 system in Quebec). Hit "download", expecting it to pull the updated data into the existing system and provide the table listing changes and asking me to accept or reject, as with other systems I've downloaded recently. Instead, a second copy of SID 5492 was created in the UT DB.
Good info. I'll check this out.More on the LTR talkgroup issue: A talkgroup shows up in the RRDB as 0-10-129. Stored in the UT DB (XML file) as "10129". When UT's options are set to "Decimal" for LTR display, the program shows this as "1-07-145". When UT's options are set to "Hexadecimal", the resulting displayed group is "1-07-91". Haven't tried to monitor an LTR system yet to see what exactly will come across/be displayed when the signal is received.
Please don't forget the data archive feature. If the "Take Me Back" button does not work for you, you can manually rollback to an earlier version of your saved data. Look in your Unitrunker data folder. See all those files named "Unitrunker.xml.1 ... Unitrunker.xml.2 ... and so on? The higher the number - the more recent the file. Look at the date and file size for an idea of which file to use. Copy the file (do not rename) to Unitrunker.xml (no numeric suffix) before running Unitrunker. That's the file it will load.You must have posted that for a reason, I went back to an older version, but, I had to start from scratch.![]()
Hi, I love this program, been waiting a long time for this up date. But I wanted to let you know I believe it still has bugs or I am not doing something right? I can not get the signal to the program like I could with the older version. When I give it all the info I believe it needs and tell it to run it does nothing. It also stops responding when I click on the scope to check the signal. Any suggestion or are these bugs? Thanks.
Please don't forget the data archive feature. If the "Take Me Back" button does not work for you, you can manually rollback to an earlier version of your saved data. Look in your Unitrunker data folder. See all those files named "Unitrunker.xml.1 ... Unitrunker.xml.2 ... and so on? The higher the number - the more recent the file. Look at the date and file size for an idea of which file to use. Copy the file (do not rename) to Unitrunker.xml (no numeric suffix) before running Unitrunker. That's the file it will load.
That should save your a$$ in most cases.
I have a hot fix for the 'scope problem. Stand by ...When I try to operate the SCOPE the software get stuck no scope screen apear
but in regular operation the software decode control channel