Closed jonathanendersby closed 7 years ago
I'd just hardcode it, it's not too bad provided you know what exactly what the channel numbers are. The math is in either smartnet-trunking.cc or smartnet-parser.cc, make it a fixed switch case for the channels with a debug message for unknowns, currently it's jut a math thing from the channel number based on the control channel or something.
From the output you are not getting a good decode from the control channel.
Control Channel Message Decode Rate: 2.66667/sec, count: 8
With a smartnet system it sends 43 messages per second, if you are only getting 1 or 2 of them so you are missing a lot of traffic. Mess with your error correction a bit, if you have unitrunker working see what PPM rate it is using and try the same one (pretty sure trunk-recorder wont take decimals so just round up or down).
Also trunk-recorder is only going to spit out the message
Control Channel Message Decode Rate: 2.66667/sec, count: 8
if its below 3 so you might want for testing to remove that if statement in main.cc line 834 so you can see when you get to 43/sec.
Thanks Dylan, I've got a solid lock on the trunk now and am no longer receiving any Decode Rate warnings.
I have a SmartNet system with a control channel near 417mhz and 11 analog channels distributed (with random offsets) between 417 and 419mhz. The entire system falls inside 2.4mhz and I have done the leg work to figure out each channel's frequency (using a couple of rtlsdrs, some patience and unitrunker). I have the system configured and working perfectly inside unitrunker.
Is there an easy way to configure this system in trunk recorder? I expected to be able to configure these channels in the "channels" entity under "system" in the config, but that's only for conventional systems.
Luke suggested that I might need to look in smartnet_trunking.cc, which I have, but it seems to be taking a mathematical approach to determining the various channel's frequencies, where I believe mine are randomly distributed.
My output (which I'm assuming means that it's successfully decoding the trunk):
Is this something that Trunk Recorder already caters for?
Thanks in advance! Jonathan.