Trunk-Recorder Error?

[bburkett]

I have been running Trunk-Recorder for a couple days and audio has been perfect! Working much better for me than SDRTrunk.

That said, I have received this error several times:
...
[2023-12-31 13:39:22.145847] (info) [icorrs] Started with Control Channel: 854.137500 MHz
[2023-12-31 13:39:22.146878] (info) P25 Trunking two-stage decimator - Initial decimated rate: 100000 Second decimated rate: 25000 FA: 6250 FB: 12500 System Rate: 1600000
[2023-12-31 13:39:22.153920] (info) P25 Trunking ARB - Initial Rate: 1600000 Resampled Rate: 25000 Initial Decimation: 16 System Rate: 24000 ARB Rate: 0.96
Allocating 15 zero-copy buffers
Allocating 15 zero-copy buffers
Allocating 15 zero-copy buffers
[2023-12-31 13:39:22.875892] (info) [icorrs] Decoding System Site RFSS: 001 SITE ID: 010 (001-010)
[2023-12-31 13:39:22.875961] (error) [icorrs] 0C TG: 2268 Freq: 0.000000 MHz Not Recording: no source covering Freq
[2023-12-31 13:39:23.939529] (info) Error - can't set XOR Mask for TDMA
[2023-12-31 13:39:25.983199] (info) [icorrs] Decoding System ID 152 WACN: BEE00 NAC: 150
[2023-12-31 13:42:21.215417] (info) [icorrs] 2C TG: 2268 Freq: 855.812500 MHz Starting P25 Recorder Num [6] TDMA: true Slot: 0 QPSK: true
[2023-12-31 13:42:26.867134] (info) [icorrs] 2C TG: 2268 Freq: 855.812500 MHz Unit ID set via Control Channel, ext: 641113 current: -1 samples: 0
[2023-12-31 13:42:30.386587] (info) [icorrs] 2C TG: 2268 Freq: 855.812500 MHz Unit ID set via Control Channel, ext: 71177 current: -1 samples: 0
[2023-12-31 13:42:43.019661] (info) Currently Active Calls: 1
[2023-12-31 13:42:43.019690] (info) [icorrs] 2C TG: 2268 Freq: 855.812500 MHz Elapsed: 22 State: recording
[2023-12-31 13:42:43.019730] (info) [ 6 ] State: idle
...

This occurred right after startup and not after that.

My config.json file contents:
{
"ver": 2,
"sources": [
{
"center": 854791700,
"rate": 1600000,

"ppm":-1.2,
"gain": 48,
"debugRecorders": 0,
"digitalRecorders": 6,
"driver": "osmosdr",
"device": "rtl=0"
}, {
"center": 856100000,
"rate": 1600000,

"ppm": -1.2,
"gain": 48,
"digitalRecorders": 6,
"driver": "osmosdr",
"device": "rtl=1"
}, {
"center": 857408300,
"rate": 1600000,
"error": 0,
"ppm": -1.2,
"gain": 48,
"lnaGain":15,
"digitalRecorders": 6,
"driver": "osmosdr",
"device": "rtl=2"
}
],
"systems": [
{
"control_channels": [854137500,857012500],
"type": "p25",
"talkgroupsFile": "icorrs_talkgroups_12-31.csv",
"audioArchive": false,
"callLog": false,
"recordUnknown": true,
"shortName": "icorrs",
"modulation": "qpsk"
}
],
"captureDir": "/home/bob/dockers/trunkrecorder/recordings/",
"plugins": [
{
"name": "rdioscanner_uploader",
"library": "librdioscanner_uploader.so",
"server": "http://192.168.0.53:3001",
"systems": [{
"shortName": "icorrs",
"apiKey": "c9570601-8a01-43eb-b3b4-6b6339151be1",
"systemId": 152
}
]
}
]
}

Any ideas on cause? I couldn't find anything in my searches.

Also, I am running 3 RTLSDR v3 and I haven't been able to find a list of applicable parameters that I can use in my config.json file. So far just testing to find ones that work. Can anyone point me to a list of parameters specifically for the RTLSDRs?

One last one: What is acceptable Hz error? ...and should it be changing?

Thanks for you time!

~Bob

 

[mrlindstrom]

Trunk recorder has a very active discord that’s linked in their GitHub page, you’ll find a lot more help there:

GitHub - TrunkRecorder/trunk-recorder: Records calls from a Trunked Radio System (P25 & SmartNet)

Records calls from a Trunked Radio System (P25 & SmartNet) - TrunkRecorder/trunk-recorder

github.com

 

[bburkett]

Thank you, sir! I'll be headed there!

Happy New Year!
~Bob

 

[Kingscup]

It looks like the error could be that frequency that was used was outside of the range of the SDR. You might need another SDR to cover that frequency.

 

[rosecitytransit]

Note how it says "Freq: 0.000000 MHz". Basically, it's a spurious message and can be ignored.

 

[bburkett]

Note how it says "Freq: 0.000000 MHz". Basically, it's a spurious message and can be ignored.

Thanks! I asssumed that may be the case.

 

[tadsmith]

On startup, it needs to wait until it receives a specific control channel message to identify the frequency band plan. It can take a second.