Unitrunker Too Many LCN's

[air-scan]

Unitrunker shows 34 LCN's with many unused for Site 001 but definitely not that many
Oklahoma City Site Details (Oklahoma Wireless Interoperability Network (OKWIN) (P25)) (radioreference.com)


How do I set it to only show Site 001 LCN's?

 

[GTR8000]

Delete the invalid channels. If they keep coming back, you're probably experiencing periods of weak/unreliable decoding that is adding some junk to the site/system. Only thing you can really do is improve the signal as best you can, and delete any invalid channels as soon as you notice them.

 

[air-scan]

Delete the invalid channels. If they keep coming back, you're probably experiencing periods of weak/unreliable decoding that is adding some junk to the site/system. Only thing you can really do is improve the signal as best you can, and delete any invalid channels as soon as you notice them.

That worked. I restarted it and those extras didn't come back for now. Time will tell but I am confident they won't come back.
Thanks!

 

[GTR8000]

It's very tough to achieve 100% perfection with so many variables, not the least of which is the hardware receiving the control channel signal. Even if you have a $200 AirSpy with a high quality Yagi antenna pointed right at the nearest simulcast subsite...there are still going to be brief periods where the signal fades or the PC has a momentary spike in CPU usage that leads to somewhat degraded decoding, however brief.

A Motorola ASTRO 25 system using implicit signaling (which is what the OKWIN system is) puts out 40 messages per second over the control channel. That's nearly 3.5 million messages per day that Unitrunker is decoding. Frankly, it's remarkable that the accuracy is as good as it is with that much data being received, decoded, and processed.

 

[air-scan]

It's very tough to achieve 100% perfection with so many variables, not the least of which is the hardware receiving the control channel signal. Even if you have a $200 AirSpy with a high quality Yagi antenna pointed right at the nearest simulcast subsite...there are still going to be brief periods where the signal fades or the PC has a momentary spike in CPU usage that leads to somewhat degraded decoding, however brief.

A Motorola ASTRO 25 system using implicit signaling (which is what the OKWIN system is) puts out 40 messages per second over the control channel. That's nearly 3.5 million messages per day that Unitrunker is decoding. Frankly, it's remarkable that the accuracy is as good as it is with that much data being received, decoded, and processed.

Just started up UniTrunker again to see if those extras would come back because I was doubting my own words. I am pleased my doubts were not reality because those extras didn't return so it was possibly a fluke why they appeared anyway. I suspect it was background services causing
momentous cpu spikes while I was setting up Unitrunker for OKWIN when those extras LCN's showed up.

 

[air-scan]

Today I reinstalled Unitrunker after I had rebuilt the SSD from factory USB drive. Tested it for a few days and slowly adding back software. The excess LCN problem resurfaced then I thought about it. I was importing the database from within the Systems tab in the Unitrunker main window. That also downloaded every single frequency in the entire Oklahoma Wireless Interoperability Network.

I tried to delete the excess but they came back....

then.......

Deleted the entire system from the systems tab in the main window. Redownloaded the system in the Site window Calls tab where you see the calls in realtime. No excess LCN's!

I was used to Unitrunker v1 and now v2 being a bit different I have to change my habits.

So really it was not a problem. Seems to be by design for those who do plenty of driving around Oklahoma that already have the frequencies there in chase mode! For people like me that don't go outside of the city limits please just download the system within the site window calls tab.

In a nutshell....importing the OKWIN system from systems tab shows the excess LCN's in the site window calls tab. Importing the system from within the site window calls tab doesn't show the excess LCN's. They do still appear in the systems tab but won't show in the site window calls tab.