Photo taken near [Astlehn/Fischbach](https://www.openstreetmap.org/?mlat=47.062377833333336&mlon=10.959586666666667#map=15/47.062377833333336/10.959586666666667).
lastmod: 2024-09-22T12:53:48+0000
lastmod: 2024-09-28T23:48:06+0000
comment: false
showDate: false
@ -17,7 +16,6 @@ showAuthor: false
sharingLinks: false
feed_exclude: true
---
## Who Am I
@ -56,13 +54,13 @@ I usually participate in the following [Winlink](https://winlink.org/) nets:
| 2 | the first non-standard mode provided by the device firmware, if any |
| auto | Pick a suitable mode automatically using heuristics |
| max | Pick the highest-numbered available mode |
| keep | Keep the mode selected by firmware (the default) |
| auto | Pick a suitable mode automatically using heuristics |
| max | Pick the highest-numbered available mode |
| keep | Keep the mode selected by firmware (the default) |
More details can be found in {{<manloader.conf5>}}.
## Manual sections
| Section | Description |
| :--- | :--- |
| 1 | Section 1 of the manual describes **user commands** and tools, for example, file manipulation tools, shells, compilers, web browsers, file and image viewers and editors, and so on |
| 1 | Section 1 of the manual describes **user commands** and tools, for example, file manipulation tools, shells, compilers, web browsers, file and image viewers and editors, and so on |
| 2 | Section 2 of the manual describes the Linux **system calls**. A system call is an entry point into the Linux kernel. Usually, system calls are not invoked directly: instead, most system calls have corresponding C library wrapper functions which perform the steps required (e.g., trapping to kernel mode) in order to invoke the system call. Thus, making a system call looks the same as invoking a normal library function. |
| 3 | Section 3 of the manual describes all **library functions** excluding the library functions (system call wrappers) described in Section 2, which implement system calls. |
| 4 | Section 4 of the manual describes **special files (devices)**. |
| 5 | Section 5 of the manual describes various **file formats**, as well as the **corresponding C structures**, if any. |
| 6 | Section 6 of the manual describes the **games** and funny little programs available on the system. |
| 7 | Section 7 of the manual provides **overviews on various topics**, and describes conventions and protocols, character set standards, the standard filesystem layout, and miscellaneous other things. |
| 3 | Section 3 of the manual describes all **library functions** excluding the library functions (system call wrappers) described in Section 2, which implement system calls. |
| 4 | Section 4 of the manual describes **special files (devices)**. |
| 5 | Section 5 of the manual describes various **file formats**, as well as the **corresponding C structures**, if any. |
| 6 | Section 6 of the manual describes the **games** and funny little programs available on the system. |
| 7 | Section 7 of the manual provides **overviews on various topics**, and describes conventions and protocols, character set standards, the standard filesystem layout, and miscellaneous other things. |
## Encoding videos with ffmpeg
This is not an Arch way of encoding videos, but since I do this on my...
You may know other package managers commands, but I only use these.
@ -87,7 +86,7 @@ You may know other package managers commands, but I only use these.
The files taken from the snapshot tool on my macbook.
~~~plain
```plain
33K 00_locales.png
61K 01_control-software.png
157K 02_mmdvmhost.png
@ -96,11 +95,11 @@ The files taken from the snapshot tool on my macbook.
69K 05_exp_mmdvmhost-dmrnetwork.png
212K 06_exp_dmrgw-dmrnetwork1.png
236K 07_exp_dmrgw-dmrnetwork2.png
~~~
```
Three to four minutes later (all three commands):
~~~plain
```plain
17K 00_locales.png
33K 01_control-software.png
81K 02_mmdvmhost.png
@ -109,14 +108,14 @@ Three to four minutes later (all three commands):
32K 05_exp_mmdvmhost-dmrnetwork.png
127K 06_exp_dmrgw-dmrnetwork1.png
144K 07_exp_dmrgw-dmrnetwork2.png
~~~
```
### By view
~~~plain
```plain
25K opti_01.png
13K opti_02.png
~~~
```
 
@ -126,7 +125,7 @@ Do you see much difference?
I added this to my fishs configuration (when I used fish for a while).
~~~fish
```fish
# file: "~/.config/fish/functions/opti.fish"
function opti --description "Optimizes .png files"
# Author: Dominic, OE7DRT <dominic@oe7drt.com>
@ -163,11 +162,11 @@ function opti --description "Optimizes .png files"
pngcrush -rem gAMA -rem alla -rem cHRM -rem iCCP -rem sRGB -rem time -ow "$argv[$i]";
end
end
~~~
```
And I made one for the jpeg version too:
~~~fish
```fish
# file: "~/.config/fish/functions/jopti.fish"
function jopti --description "Optimizes .jpg files"
# Author: Dominic, OE7DRT <dominic@oe7drt.com>
@ -202,4 +201,4 @@ function jopti --description "Optimizes .jpg files"
{{<figurecaption="`pydf` in combination with the alias from above displays a short and colored output when you list your diskspace with `df`"src="11_df_output.png"alt="an example output of `pf`">}}
It takes time to gather enough information. Get back to this in a few days and
you will get more useful information. Because we save the databases in the
@ -214,9 +213,9 @@ PiStar does not mount the volumes read-only!**
Once you finished your setup, make the filesystem read-only again.
~~~console
```console
$ rpi-ro
~~~
```
## Start setting up your Pi-Star MMDVM
@ -231,16 +230,16 @@ the **Apply Changes** button. So when hitting the button wait a few seconds
This setup uses some talk groups from IPSC2/DMR+ and the rest from Brandmeister.
Specifically these talkgroups are:
* Timeslot 1
* TG 1 - TG 7
* TG 10 - TG 89
* TG 100 - TG 199
* Timeslot 2
* DMR+ reflectors with TG 9
* TG 232
* TG 8181 - TG 8189
* TG 8191 - TG 8199
* GPS data sent as private calls to 9057
- Timeslot 1
- TG 1 - TG 7
- TG 10 - TG 89
- TG 100 - TG 199
- Timeslot 2
- DMR+ reflectors with TG 9
- TG 232
- TG 8181 - TG 8189
- TG 8191 - TG 8199
- GPS data sent as private calls to 9057
All other talkgroups are routed to the Brandmeister network. Private calls are
also routed to Brandmeister.
@ -251,7 +250,6 @@ This is where we actually start. At the first start either connect your
Raspberry Pi to an ethernet port or look out for a WiFi network called
Pi-Star Setup.
{{<figuresrc="01_control-software.png"alt="Control Software configuration"caption="Make sure to use Duplex Repeater in order to use different RX and TX frequencies.">}}
### MMDVMHost
@ -286,9 +284,9 @@ for Hotspot Security. That makes sure, that only you can add a Hotspot with your
callsign. Also select the IPSC2 server of your choice and set the wanted
