unitrunker system/site question

[nikoz1200]

Been running unitrunker for the last few days...and dig it. One thing I can't figure out is the color codes on the frequencies. Red is the control channel, white i think is voice... what is brown? by what i can guess it is data channels from other cells, but i can't be sure.

anyone?

 

[Hir8ed_2]

Go to www.snapfiles.com and download colormapper. It will give you the color codings on demand.

 

[SCPD]

From your other post it looks like you figured this out ...

Brown channels are alternate or back-up control channels. Red of course is the active control channel.

-rick

 

[MattSR]

It seems to decoding the adjacent site OSW incorrectly, as most of the Brown channels i have on Unitrunker are the CC's for adjacent sites.

 

[SCPD]

Hi Matt;

Quit the program, delete the channels (or the HZ file) and re-start the program. Keep the radio tuned to only one site. If you set the receiver to jump from site to site, you'll have this problem. Please let me know if you see incorrect channels (eg. channels from adjacent sites) appear after re-starting the program.

-rick

 

[MattSR]

Hi rick,

I only have the one CC programmed into the scanner, and I have had to edit the systems .HZ file every few days.

Reception from this site can vary from 100% to below 80% at times, and this generally occurs when reception is not so great. I know the OSW's for alternate CC's and adjacent sites CC's are identical (The difference is determined by the Site ID) which leads me to think that there may be a bug in the software.

Heres a screenshot showing the System messsges detecting the CC for Cell 44 as Chan 25B, and in the channel readout for site 48, Chan 25B is being detected as an alternate CC.

This isnt an isolated instance, if I let the software run long enough all the other adjacent CC's will end up in there as well.

Kind Regards, and keep up the good work,
Matt

 

[MattSR]

Also, 1A9 is incorrect - the true alternate for this site is 1E4.

 

[SCPD]

Reception from this site can vary from 100% to below 80% at times, and this generally occurs when reception is not so great. I know the OSW's for alternate CC's and adjacent sites CC's are identical (The difference is determined by the Site ID) which leads me to think that there may be a bug in the software.

Thanks Matt. This is excellent feedback. I think I know the problem ... missing or dropped OSWs. The program tries to avoid accepting data under these circumstances but not all combinations are easy to predict.

If you have the time and inclination, you can clear your HZ file (again) and re-start the program. Run the program with Logging turned on. I can't remember if the 1st public beta has logging - probably not (but the 2nd public beta will). If not, you will need to run the Packets program side-by-side. Windows XP allows this. If you have Windows 2K or earlier vintage this may not work.

Let the program run while logging data to a file. When you see an erroneous channel appear - stop the program. The log file will most likely show what command sequences resulted in false channels being added to the site. Please send me a ZIP of the log file and I'll see what I can do to catch / avoid this situation.

-rick

 

[MattSR]

No problems - I am running the packets program (dumping to a text file) When I can replicate this I will send you the logs

Matt

 

[Jay911]

Rick,

PM's apparently don't allow file attachments, so here we go in this thread.

Attached is 753f.zip, containing a very brief logfile snippet captured as instructed above. I had to invert the signal so Packets would capture it, but it did receive, and I got just what I was expecting, to be honest.

With my BC245 set on manual/hold on 868.2125 (Mot channel 688), the default control channel for site 3 of 753f, I am getting ~88% decode rate (though I was getting 100% a few days ago from the same setup - weather vagaries, perhaps). In any case, I removed all spurious frequencies from site 3 in the Moto753F.HZ file, leaving only channels 602, 608, 614, 622, 628, 634, 642, 654, 662, 674, 682, 688, 694, 702, 708, and 714 in the listing - 16 frequencies. Upon running UniTrunker (and Packets, as quickly as I could manage at the same time), I immediately got 2B2 (690), 29C (668), 278 (632), 261 (609), 25D (605), 259 (601), and 288 (648) popping onto the channel listing.

For what it's worth, 601 = Site 1's primary control channel, 605 = Site 4's primary, 609 = Site 5's primary, 632 = Site 6's alternate, 648 = Site 3's alternate, 668 = Site 3's other alternate, and 690 = Site 2's primary.

I can find references to everything except channel 609 in the log snippet.

Hope this helps!

 

[SCPD]

I'll have to come back to this issue after the next beta release. I suspect this has been fixed. I can see differences in what has been posted here - both screenshots and log files - and the soon-to-be second public beta.

For the alternate and adjacent site data channels - these should appear under the "View -> Channels" display - next to the appropriate site number. The channels for the adjacent sites should not - of course - appear on the current site.

-rick

 

[dfoutch]

Rick & All
My 2cents: The extra CCs include the alt site CCs, coming from a data line starting with "Smartzone Peerinfo,....Dchan='hex' 'dec'" frequency, telling the radio what CC freq to check if this site is down. I think this is normal and good. Its the extra voice channels I don't understand. From Greenfield Site 30. Indiana Safe-T.
NetInfo, Sys=7829, Cell=<26>, uses DChan=293 867.4875, Band=821, Wide, Astro, Analog
NetInfo, Sys=7829, Cell=<02>, uses DChan=3FB 868.8750, Band=821, Wide, Astro, Analog
Smartzone PeerInfo, SysId=7829, DChan=293 867.4875
Smartzone PeerInfo, SysId=7829, DChan=3BE 868.9750
Non-Net ID=7829, DChan=3F9 868.8250
NetInfo, Sys=7829, Cell=<19>, uses DChan=3BE 868.9750, Band=821, Wide, Astro, Analog
NetInfo, Sys=7829, Cell=<24>, uses DChan=2BA 868.4625, Band=821, Wide, Astro, Analog
Net ID=7829, DChan=3F9 868.8250
NetInfo, Sys=7829, Cell=<01>, uses DChan=2A2 867.8625, Band=821, Wide, Astro, Analog
NetInfo, Sys=7829, Cell=<24>, uses DChan=2BA 868.4625, Band=821, Wide, Astro, Analog
NetInfo, Sys=7829, Cell=<01>, uses DChan=2A2 867.8625, Band=821, Wide, Astro, Analog
Smartzone PeerInfo, SysId=7829, DChan=3FB 868.8750
Smartzone PeerInfo, SysId=7829, DChan=2CD 868.9375
NetInfo, Sys=7829, Cell=<26>, uses DChan=293 867.4875, Band=821, Wide, Astro, Analog
Net ID=7829, DChan=3F9 868.8250
NetInfo, Sys=7829, Cell=<24>, uses DChan=2BA 868.4625, Band=821, Wide, Astro, Analog
Smartzone PeerInfo, SysId=7829, DChan=2BA 868.4625
NetInfo, Sys=7829, Cell=<25>, uses DChan=2CD 868.9375, Band=1, Wide, Astro, Analog
NetInfo, Sys=7829, Cell=<24>, uses DChan=2BA 868.4625, Band=821, Wide, Astro, Analog
NetInfo, Sys=7829, Cell=<19>, uses DChan=3BE 868.9750, Band=821, Wide, Astro, Analog
Smartzone PeerInfo, SysId=7829, DChan=2A2 867.8625
Net ID=7829, DChan=3F9 868.8250
Smartzone PeerInfo, SysId=7829, DChan=2CD 868.9375
Smartzone PeerInfo, SysId=7829, DChan=2BA 868.4625
NetInfo, Sys=7829, Cell=<02>, uses DChan=3FB 868.8750, Band=821, Wide, Astro, Analog
Smartzone PeerInfo, SysId=7829, DChan=2A2 867.8625
NetInfo, Sys=7829, Cell=<25>, uses DChan=2CD 868.9375, Band=1, Wide, Astro, Analog
NetInfo, Sys=7829, Cell=<26>, uses DChan=293 867.4875, Band=821, Wide, Astro, Analog
NetInfo, Sys=7829, Cell=<24>, uses DChan=2BA 868.4625, Band=821, Wide, Astro, Analog
NetInfo, Sys=7829, Cell=<02>, uses DChan=3FB 868.8750, Band=821, Wide, Astro, Analog
Non-Net ID=7829, DChan=3F9 868.8250
NetInfo, Sys=7829, Cell=<24>, uses DChan=2BA 868.4625, Band=821, Wide, Astro, Analog
NetInfo, Sys=7829, Cell=<01>, uses DChan=2A2 867.8625, Band=821, Wide, Astro, Analog
Smartzone PeerInfo, SysId=7829, DChan=2CD 868.9375
NetInfo, Sys=7829, Cell=<25>, uses DChan=2CD 868.9375, Band=1, Wide, Astro, Analog

dean

 

[SCPD]

My 2cents: The extra CCs include the alt site CCs, coming from a data line starting with "Smartzone Peerinfo,....Dchan='hex' 'dec'" frequency, telling the radio what CC freq to check if this site is down. I think this is normal and good.

A quick update to all on this issue where CC's from adjacent sites are erroneously added to the currently monitored site. I've seen this recently on a local SZ system where signal quality ranged from good to poor over the better part of a day. It is related to poor signal (crappy data) fooling the program into displaying incorrect info. I'm working on some ways to fix this.

-rick