You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/CONFIGURE.md
+4-6Lines changed: 4 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ Center Frequency Calculators:
41
41
Configuration File:
42
42
-https://www.radioetcetera.site/trunk-recorder-config-editor/ - tool for using a GUI to create config.json files
43
43
-https://github.com/AlertPageSDR/tr_configurator - If you have a Radio Reference Premium account, you can use this tool to automatically generate a config.json based on the RR data for a given system (or systems)
44
-
-https://github.com/robotastic/trunk-recorder-configs - example configurations for different systems
44
+
-https://github.com/TrunkRecorder/trunk-recorder-configs - example configurations for different systems
45
45
46
46
### Gain
47
47
@@ -229,11 +229,10 @@ There is a list of available Plugins [here](./Plugins.md).
229
229
| compressWav || true | bool | Convert the recorded .wav file to an .m4a file. **This is required for both OpenMHz and Broadcastify!** The `sox` and `fdkaac` packages need to be installed for this command to work. |
230
230
| unitScript ||| string | The filename of a script that runs when a radio (unit) registers (is turned on), affiliates (joins a talk group), deregisters (is turned off), gets an acknowledgment response, transmits, gets a data channel grant, a unit-unit answer request or a Location Registration Response. Passed as parameters: `shortName radioID on\|join\|off\|ackresp\|call\|data\|ans_req\|location`. On joins and transmissions, `talkgroup` is passed as a fourth parameter; on answer requests, the `source` is. On joins and transmissions, `patchedTalkgroups` (comma separated list of talkgroup IDs) is passed as a fifth parameter if the talkgroup is part of a patch on the system. See *examples/unit-script.sh* for a logging example. Note that for paths relative to trunk-recorder, this should start with `./`( or `../`). |
231
231
| audioArchive || true |**true** / **false**| Should the recorded audio files be kept after successfully uploading them? |
232
-
| conversationMode || true |**true** / **false**| Should individual transmissions that are within *timeout* of each other, be grouped together into a single call. |
233
232
| transmissionArchive || false |**true** / **false**| Should each of the individual transmission be kept? These transmission are combined together with other recent ones to form a single call. |
234
233
| callLog || true |**true** / **false**| Should a json file with the call details be kept after successful uploads? |
235
234
| analogLevels || 8 | number (1-32) | The amount of amplification that will be applied to the analog audio. |
236
-
| maxDev ||4000| number | The maximum deviation for analog channels. If you analog recordings sound good or if you have a completely digital system, then there is no need to touch this. |
235
+
| maxDev ||5000| number | The maximum deviation for analog channels. If you analog recordings sound good or if you have a completely digital system, then there is no need to touch this. |
237
236
| digitalLevels || 1 | number (1-16) | The amount of amplification that will be applied to the digital audio. |
238
237
| unitTagsFile ||| string | The filename of a CSV file that provides information about the unit tags. The format for the file is described below. |
239
238
| recordUnknown || true |**true** / **false**| Record talkgroups if they are not listed in the Talkgroups File. |
@@ -279,14 +278,14 @@ By default, Trunk Recorder will record the call from the first site to receive t
279
278
{
280
279
"type": "P25",
281
280
...
282
-
"multiSite": "true",
281
+
"multiSite": true,
283
282
"multiSiteSystemName": "somesharedname",
284
283
"multiSiteSystemNumber": 1
285
284
},
286
285
{
287
286
"type": "P25",
288
287
...
289
-
"multiSite": "true",
288
+
"multiSite": true,
290
289
"multiSiteSystemName": "somesharedname",
291
290
"multiSiteSystemNumber": 2
292
291
}
@@ -487,7 +486,6 @@ The columns are:
487
486
| Tag || The Service Tag for the Talkgroup |
488
487
| Priority || The priority field specifies the number of recorders the system must have available to record a new call for the talkgroup. For example, a priority of 1, the highest means as long as at least a single recorder is available, the system will record the new call. If the priority is 2, the system would at least 2 free recorders to record the new call, and so on. If there is no priority set for a talkgroup entry, a prioity of 1 is assumed. <br/> Talkgroups assigned a priority of -1 will never be recorded, regardless of the number of available recorders. |
489
488
| Preferred NAC || In Multi-Site mode, the preferred NAC (`nnnn`, e.g. `1234`), RFSS/SiteID (`RRRRssss`, e.g. `00010023`), or multiSiteSystemNumber to record a specific talkgroup.|
490
-
| Conversation Mode || Allows for Conversation Mode to be set at the Talkgroup level. This is helpful if you have a busy dispatch channel and want to break it up. This value can be set on only few rows, the rest will default to the System level value. The allowed values are `true` and `false`. |
491
489
| Comment || Use this field to capture comments about a talkgroup. It will be ignored by Trunk Recorder. |
Copy file name to clipboardExpand all lines: docs/DEBUG.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ make
26
26
gdb trunk-recorder core
27
27
```
28
28
29
-
6.*gdb* is a powerful debugging platform. However, all we need is a trace of the crash. After *gdb* has finished loading, type in `bt full` to get a trace. Copy all of the output from *gdb* into a new [GitHub Issue](https://github.com/robotastic/trunk-recorder/issues/new), along with as much information as possible on what maybe causing the crash.
29
+
6.*gdb* is a powerful debugging platform. However, all we need is a trace of the crash. After *gdb* has finished loading, type in `bt full` to get a trace. Copy all of the output from *gdb* into a new [GitHub Issue](https://github.com/TrunkRecorder/trunk-recorder/issues/new), along with as much information as possible on what maybe causing the crash.
30
30
31
31
32
32
# How to Capture an IQ Sample
@@ -67,7 +67,7 @@ Use the settings from the source you are interested in from your config.json fil
67
67
68
68
you would use: `rtl_sdr -f 855700000 -s 2048000 -g 39 -d 41 debug.iq`
69
69
70
-
The file that rtl_sdr generates is in a compact format... which is great but it can't easily be opened by other program. There is a good write-up on it from here (from 2014!). Luckily, some wrote a small program to convert it into a more standard format (complex IQ). I have included it in the /utils folder: [rtlsdr-to-iq.c](https://github.com/robotastic/trunk-recorder/blob/master/utils/rtlsdr-to-iq.c). Compile the program and then copy it to the directory with your recordings and run it against them. Note - the conversion will cause the filesize to increase 4x, so make sure you have enough space.
70
+
The file that rtl_sdr generates is in a compact format... which is great but it can't easily be opened by other program. There is a good write-up on it from here (from 2014!). Luckily, some wrote a small program to convert it into a more standard format (complex IQ). I have included it in the /utils folder: [rtlsdr-to-iq.c](https://github.com/TrunkRecorder/trunk-recorder/blob/master/utils/rtlsdr-to-iq.c). Compile the program and then copy it to the directory with your recordings and run it against them. Note - the conversion will cause the filesize to increase 4x, so make sure you have enough space.
71
71
72
72
73
73
## Playback in GQRX
@@ -81,4 +81,4 @@ You are then going to need a device string with the correct options. Update this
81
81
82
82
## Playing an IQ File as a Source in Trunk Recorder
83
83
84
-
Check out the [config-iq-file.json](https://github.com/robotastic/trunk-recorder/blob/master/examples/config-iq-file.json) config as an example of how to playback an IQ file as a Source. You will probably need to have the `repeat` parameter turned on, unless you have a really long file.
84
+
Check out the [config-iq-file.json](https://github.com/TrunkRecorder/trunk-recorder/blob/master/examples/config-iq-file.json) config as an example of how to playback an IQ file as a Source. You will probably need to have the `repeat` parameter turned on, unless you have a really long file.
Copy file name to clipboardExpand all lines: docs/FAQ.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,5 +46,5 @@ Once **gdb** loads up, use the *backtrace* command to review the execution histo
46
46
47
47
`backtrace`
48
48
49
-
Now you can create a [GitHub Issue](https://github.com/robotastic/trunk-recorder/issues), including the info from **gdb**, along with your config.json and as much info as possible on how to recreate the crash.
49
+
Now you can create a [GitHub Issue](https://github.com/TrunkRecorder/trunk-recorder/issues), including the info from **gdb**, along with your config.json and as much info as possible on how to recreate the crash.
Copy file name to clipboardExpand all lines: docs/Install/INSTALL-DOCKER.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,5 +53,5 @@ Currently, Docker image builds are triggered by the following events:
53
53
54
54
* After every push to the `master` branch the `edge` tag is built and pushed to Docker Hub.
55
55
* Every day at 10 AM UTC the `nightly` tag is built and pushed to Docker Hub.
56
-
* When a new [release](https://github.com/robotastic/trunk-recorder/releases) happens the `<version>` and `latest` tags are built and pushed to Docker Hub.
56
+
* When a new [release](https://github.com/TrunkRecorder/trunk-recorder/releases) happens the `<version>` and `latest` tags are built and pushed to Docker Hub.
@@ -217,7 +217,7 @@ The next step is to [configure Trunk Recorder](../CONFIGURE.md) for the system y
217
217
218
218
## Running trunk recorder.
219
219
220
-
If all goes well you should now have the executable named `trunk-recorder`, and created the `config.json` configuration file as described in the [Wiki](https://github.com/robotastic/trunk-recorder/wiki/Configuring-a-System) and [README](https://github.com/robotastic/trunk-recorder/blob/master/README.md#configure).
220
+
If all goes well you should now have the executable named `trunk-recorder`, and created the `config.json` configuration file as described in the [Wiki](https://github.com/TrunkRecorder/trunk-recorder/wiki/Configuring-a-System) and [README](https://github.com/TrunkRecorder/trunk-recorder/blob/master/README.md#configure).
221
221
222
222
From your build directory (e.g. `trunk-build`) you can now run
Copy file name to clipboardExpand all lines: docs/Install/INSTALL-MAC.md
+27-16Lines changed: 27 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,28 +6,39 @@ sidebar_position: 4
6
6
There are two main "package managers" used on MacOS: [Homebrew](#using-homebrew) and [MacPorts](#using-macports). Trunk-recorder can be installed with dependencies from one or the other
7
7
8
8
## Using Homebrew
9
-
Tested on macOS Ventura 13.2 with the following packages:
9
+
Tested on macOS Sequoia 15.5 with the following packages:
10
10
11
-
- homebrew 3.6.21
12
-
- cmake 3.25.2
13
-
- gnuradio 3.10.5.1
14
-
- uhd 4.4.0.0
15
-
- pkgconfig 0.29.2
11
+
- homebrew 4.5.3
12
+
- cmake 4.0.2
13
+
- gnuradio 3.10.12.0_1
14
+
- uhd 4.8.0.0_1
15
+
- pkgconfig 2.4.3
16
16
- cppunit 1.15.1
17
-
- openssl 3.0.7
18
-
- fdk-aac-encoder 1.0.3
19
-
- sox 14.4.2
20
-
- pybind11 2.10.3
17
+
- openssl 3.5.0
18
+
- fdk-aac-encoder 2.0.3
19
+
- sox 14.4.2_6
20
+
- pybind11 2.13.6_1
21
+
- six 1.17.0
21
22
22
23
#### Install Homebrew
23
24
See [the Brew homepage](https://brew.sh) for more information.
Trunk Recorder can be installed easily by adding the repository to homebrew. More information can be found on [this github repo](https://github.com/TrunkRecorder/homebrew-install). Install can be done easily with the following commands.
32
+
```
33
+
brew tap trunkrecorder/install
34
+
brew install trunk-recorder
35
+
```
36
+
37
+
If you prefer to install packages individually or without adding the repository, it can be done using the instructions below.
The next step is to [configure Trunk Recorder](CONFIGURE.md) for the system you are trying to capture.
134
+
The next step is to [configure Trunk Recorder](../CONFIGURE.md) for the system you are trying to capture.
124
135
125
136
## Running trunk recorder.
126
137
127
-
If all goes well you should now have the executable named `trunk-recorder`, and created the `config.json` configuration file as described in the [Wiki](https://github.com/robotastic/trunk-recorder/wiki/Configuring-a-System) and [README](https://github.com/robotastic/trunk-recorder/blob/master/README.md#configure).
138
+
If all goes well you should now have the executable named `trunk-recorder`, and created the `config.json` configuration file as described in the [Wiki](https://github.com/TrunkRecorder/trunk-recorder/wiki/Configuring-a-System) and [Configuring Trunk Recorder](https://github.com/TrunkRecorder/trunk-recorder/blob/master/docs/CONFIGURE.md).
128
139
129
140
From your build directory (e.g. `trunk-build`) you can now run
Copy file name to clipboardExpand all lines: docs/Install/INSTALL-PI.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ Smaller radio systems can be covered using a Raspberry Pi. If you are interested
10
10
## RaspberryOS (aka Raspbian)
11
11
12
12
### Setup Raspbian
13
-
This is a [good guide](https://desertbot.io/blog/headless-raspberry-pi-4-ssh-wifi-setup) on how to setup a Raspberry Pi in headless mode. This means that you do not have to attach a monitor, keyboard or mouse to it to get it working. The steps below are pulled from this guide.
13
+
This is a [good guide](https://www.tomshardware.com/reviews/raspberry-pi-headless-setup-how-to,6028.html) on how to setup a Raspberry Pi in headless mode. This means that you do not have to attach a monitor, keyboard or mouse to it to get it working. The steps below are pulled from this guide.
14
14
15
15
#### Download and burn the image
16
16
@@ -21,7 +21,7 @@ The first step is to put the Raspberry Pi OS onto a MicroSD card. You will need
21
21
22
22
#### Setup for headless boot
23
23
24
-
After the OS has been written to MicroSD card, we need to change a few files so that the Pi can get on Wifi and also allow for SSH connections. See the [guide](https://desertbot.io/blog/headless-raspberry-pi-4-ssh-wifi-setup) for how to do it using Windows.
24
+
After the OS has been written to MicroSD card, we need to change a few files so that the Pi can get on Wifi and also allow for SSH connections. See the [guide](https://www.tomshardware.com/reviews/raspberry-pi-headless-setup-how-to,6028.html) for how to do it using Windows.
25
25
26
26
-**On a Mac**`touch /Volumes/boot/ssh`
27
27
- Next, add the WiFi info
@@ -66,13 +66,13 @@ deb https://www.deb-multimedia.org bookworm main non-free
66
66
```
67
67
- Download the keys for the apt source and install them:
@@ -210,7 +210,7 @@ The next step is to [configure Trunk Recorder](CONFIGURE.md) for the system you
210
210
211
211
## Running trunk recorder.
212
212
213
-
If all goes well you should now have the executable named `trunk-recorder`, and created the `config.json` configuration file as described in the [Wiki](https://github.com/robotastic/trunk-recorder/wiki/Configuring-a-System) and [README](https://github.com/robotastic/trunk-recorder/blob/master/README.md#configure).
213
+
If all goes well you should now have the executable named `trunk-recorder`, and created the `config.json` configuration file as described in the [Wiki](https://github.com/TrunkRecorder/trunk-recorder/wiki/Configuring-a-System) and [README](https://github.com/TrunkRecorder/trunk-recorder/blob/master/README.md#configure).
214
214
215
215
From your build directory (e.g. `trunk-build`) you can now run
0 commit comments