---
title: 'MSHV installation in Linux Mint'
url: 'https://ra1ahq.blog/en/mshv-ustanovka-v-linux-mint'
markdown: 'https://ra1ahq.blog/en/mshv-ustanovka-v-linux-mint.md'
lang: en
date: '2021-08-11'
description: 'A radio amateur I know called and warned me about the August meteor shower.Perseids, which peaks on the night of August 12-13. In which you need to work on 144.360 MHz digital mode of communication MSK144 in the MSHV program. Introduction The MSHV program was developed by Hrizimir Hristov LZ2HV. The program has gained the greatest popularity for digital modes MSK144 (meteors), FT8 and FT4 (working on HF and VHF). Installation It'
taxonomy:
  category:
    - blog
  tag:
    - трансивер
    - Linux
    - УКВ
  archives_month:
    - aug_2021
  archives_year:
    - '2021'
---

# MSHV installation in Linux Mint

11 

 August 

 2021 

 ![MSHV installation in Linux Mint](https://ra1ahq.blog/images/7/1/1/c/3/711c3f17895f105c067580edcfcaf97b18d53a17-mshv-title.png)14:39

### MSHV installation in Linux Mint

 [трансивер](https://ra1ahq.blog/en/tag:%D1%82%D1%80%D0%B0%D0%BD%D1%81%D0%B8%D0%B2%D0%B5%D1%80), [Linux](https://ra1ahq.blog/en/tag:Linux), [УКВ](https://ra1ahq.blog/en/tag:%D0%A3%D0%9A%D0%92) 

11 August 2021 14:39

A radio amateur I know called and warned me about the August meteor shower.[Perseids](https://ru.wikipedia.org/wiki/%D0%9F%D0%B5%D1%80%D1%81%D0%B5%D0%B8%D0%B4%D1%8B), which peaks on the night of August 12-13. In which you need to work on 144.360 MHz digital mode of communication **MSK144** in the MSHV program.

### Introduction

The MSHV program was developed by Hrizimir Hristov LZ2HV. The program has gained the greatest popularity for digital modes MSK144 (meteors), FT8 and FT4 (working on HF and VHF).

### Installation

It is possible to compile from source code or install a ready-made DEB package file. I am considering the second method - from the DEB file.

1. Download the DEB file with the file name marked “LM” (from the phrase “Linux Mint”) from the link from the main page of the site <http://lz2hv.org/node/10>, which is called "*Download MSHV Debian Linux 32-bit, 64-bit and ARM (Ubuntu, Raspbian) binaries compiled by Richard - G8JVM*".
2. In Linux Mint 19-20 and Debian 11: we satisfy the dependencies:

    `<pre>sudo apt-get install qtbase5-dev qtchooser qt5-qmake qtbase5-dev-tools<br></br>sudo apt-get install qt5-default<br></br>sudo apt install fftw3 libqt5websockets5 libqt5websockets5-dev</pre>`

Note: In the new versions of Linux Mint 21.04 "Hirsute Hippo" and Debian 11 "Bullseye", installing the *qt5-default* package gives an error. This does not affect the further operation of the program.

3. Fixing packages:

    `<pre>sudo apt-get install -f</pre>`
4. Install the *main* package (sudo rights are also required here). At the time of writing, MSHV has the latest version **258**, recently released **259**:

    sudo dpkg -i MSHV\_259\_LM19\_amd64.deb

or

```
sudo dpkg -i MSHV_259_amd64.deb
```

If there was an error installing the package in the previous step No. 2 `qt5-default`, use the dpkg command with the key **--force-all**:

```
sudo dpkg --force-all -i MSHV_259_LM19_amd64.deb
```

5. You must be given permission to write to the folder **/usr/local/sbin/** for the user group in order to be able to save the configuration (by default, that is, after installing the program, the user has 'root' rights and the MSHV configuration is not saved after closing the program).

The program is installed in the folder **/usr/local/sbin/**, the name of the executable file is in capital letters:**MSHV**. By default, folder permissions belong to `root`, which is incorrect - a regular user will not be able to save the MSHV configuration.

***Solution:***

```
sudo chgrp -R vladimir /usr/local/sbin
```

Where '**vladimir**' is the name of the group to which the user belongs. You can find out which groups a user belongs to using the **whoami** and **groups username** commands. Typically, a Linux user has a corresponding group with the same name. You do not have to grant permissions specifically to the `username` group; you can use any group—such as `dialout` or `sudo`—provided the user is a member of that group.

### Setting up the program

1. Launch the program **MSHV** through the menu "**Start**" - "**Others**" or in the terminal we type **MSHV** and the {Enter} key.
2. Enter your Call sign and square (full GRID locator, for example: KO59dw) in the menu **"Options" - "Macros" - "My Call"**. Press the key **"SET DEFAULT MACROS"** and close the window.
3. Specify the sound card for audio input/output in **"Options"**-**"Sound Settings"**.

For an external sound card I had to select
*Out devices:*
\***pulse: alsa\_output-GeneralPlus\_USB\_Audio\_Device-00.analog.stereo**

or

\***pulse: default**

*Input devices*
\***pulse: alsa\_input.usb-GeneralPlus\_USB\_Audio\_Device-00.mono.fallback**

or

\***pulse: default**.

[ ![Setting up PulseAudio and ALSA audio](https://ra1ahq.blog/images/7/e/c/f/e/7ecfee63f55834d318ab6567b3a784d5a0485100-pulseaudio.png "Setting up PulseAudio and ALSA audio")](https://ra1ahq.blog/images/7/e/c/f/e/7ecfee63f55834d318ab6567b3a784d5a0485100-pulseaudio.png?cropresize=525,700)

3. We configure *the method of controlling the transceiver* in the menu "**Options**" - "**Interface Control**"^
    **\*Port**(serial port or USB-COM virtual port) - I chose** ttyUSB0\**.*** Baud rate**(baud rate) - selected** 38400**- matches the transmission speed of the serial port in the transceiver.
    ***PTT method**(via COM port or CAT commands) - indicated **"PTT via CAT command"***** Rig**(indicate the model of your transceiver), I have -**Yaesu FT-857\*\*

    - Press the wide button "**Start PTT Test**" to check transmission. The transfer is taking place.
        [ ![Configuring transceiver controls](https://ra1ahq.blog/images/b/0/d/e/9/b0de99a65a9636526031608fcb4498ab8de04c69-iface.png "Configuring transceiver controls")](https://ra1ahq.blog/images/b/0/d/e/9/b0de99a65a9636526031608fcb4498ab8de04c69-iface.png?cropresize=525,700)
4. On the menu **"Options"** I checked the box "**Monitor On on startup**" so that the program starts accepting after launch (without having to press the button **"Monitor"**.
5. Operating mode:**"Mode"**-**"MSK144"** for meteors.
6. Setting the half-cycle for transmission - in the main window **"TX FIRST"** for St. Petersburg and Moscow,
    item **"TX/RX"**- duration of the period **30 seconds**.
    [ ![tx_first](https://ra1ahq.blog/images/5/e/7/d/4/5e7d4baac9d18ebf0e4d4965d64598c419535860-txfirst.png "tx_first")](https://ra1ahq.blog/images/5/e/7/d/4/5e7d4baac9d18ebf0e4d4965d64598c419535860-txfirst.png?cropresize=525,700)
7. Frequency **Band**-**VHF/UHF**-**144 MHz** for meteors:

    - in the program and on the transmitter the frequency must be set via CAT **144.360 MHz** USB, The FT-857 transceiver mode for control from a computer must be set to **"DIG"**.
8. Double-clicking on a call sign starts transmission - enabled by default in "**Options**" - "**Decode List Options**" - "**Double Click on Call sets auto on**", we check.
9. Logging is enabled by default in "**Options**" - "**Log Options**" - "**Log Automatically QSO MSK**" we're checking.

10.To view the MSHV hardware log:**"File"**-**"View Log"**, from this window you can export to ADIF: *Menu - Export All in ADIF*.
The QSO log can be exported to any folder by specifying it in the dialog box. For example, for subsequent uploading of a file to eQSL.cc.

11.We adjust the transmission signal level using the ALC indicator of the transceiver - by pressing the button **Tune** in the right part of the window and adjusting the level with the “slider” up and down, we achieve the minimum readings.

12.The reception level should be normal (green sector, near 0db).
[ ![level_rx](https://ra1ahq.blog/images/1/d/3/6/f/1d36f6cd84309b97adb94b0e3d94dc049713bb84-levelrx.png "level_rx")](https://ra1ahq.blog/images/1/d/3/6/f/1d36f6cd84309b97adb94b0e3d94dc049713bb84-levelrx.png?cropresize=525,700)- controlled by the level indicator (VU meter). To adjust the reception level, use the adjacent slider **"RX"**:
[ ![rx](https://ra1ahq.blog/images/9/b/1/c/5/9b1c57a84a360f5f06205d9487ba4da20e91c94d-rx.png "RX")](https://ra1ahq.blog/images/9/b/1/c/5/9b1c57a84a360f5f06205d9487ba4da20e91c94d-rx.png?cropresize=525,700)

13.13. Check [PC time synchronization using NTP protocol](https://ra1ahq.blog/en/poyasnoe-vremya-v-linux)- for example, using the command `systemctl status ntp`- the status must be Active: active (running), time discrepancy with the site <https://time.is> no more than 1 second.

14.Set a point against **C.Q.** and click the button in the center of the window **"Auto Is On"**- automatic sequence (substitution of QSO text using macros and reception and transmission of call signs) - broadcasting will begin **C.Q.** with your call sign. Also, if the window contains the call sign of another radio station (with a single ping - a short burst of signal reflected from the ionized trace of one burnt meteorite) or a “burst” (burst - a stronger and longer burst from several successively burned meteorites or one large “stone” that left a more intense trace behind it) - when you click on the call sign, the corresponding macro should be substituted.

The operation of the "QSO machine" must be checked. If the auto mode does not work for some reason, the QSO stages are performed *manually* by changing the selection of the required macros on the right side of the window.

15.If you press the button **"Auto Is OFF"** or **"Stop TX"**, the broadcast will stop, and the radio station with the MSHV program will remain on reception (“Monitor”).

16.16. Don’t forget to set the correct transceiver power: 100 W is allowed for categories 1 and 2 radio stations and 10 W for category 3. Maximum power on VHF 144 MHz - see.[SCRF decision](https://grfc.ru/grfc/zayav/radioservice/amateur-service/frequency-solutions-of-the-gkrch/) amounts to **100 W**.

17.To work "split" on a general CQ call

- change the value in the QRG field. For example, at 368 [ ![split](https://ra1ahq.blog/images/3/2/b/c/c/32bcc0fced973f9094d47a2188ec9a45ff171f95-split.png "QRG")](https://ra1ahq.blog/images/3/2/b/c/c/32bcc0fced973f9094d47a2188ec9a45ff171f95-split.png?cropresize=525,700)
- below press the button "GEN MSG"
- select the seventh macro option: Tx7 ("CQ 368 ...")
- press the "AUTO IS OFF" button - the inscription changes to "AUTO IS ON" and the transmission begins (in the 1st period).

The allowed range for digital modes is 144.150 - 144.399 MHz, with a signal bandwidth of 2700 kHz SSB. In order not to interfere with SSB stations, it is advisable to stick to the digital mode (MGM) section: 144.360 → 144.399 MHz. Previously, the center of MS (Meteor scatter) activity was the frequency of 144.370 MHz - the calling frequency for digital modes and FSK441; recently, due to the spread of MSK144, the calling frequency has become 144.360 MHz.

There is a chat for contractual contacts [ON4KST](http://www.on4kst.info/chat/login.php?band=2) **prohibited** transmit information related to QSO information such as:

- “I need final RRR”
- “received you with report 47”
- “I received a burst from you”
- “I received the burst, but I can’t fully decode it”
    Such information provided in a chat or by phone immediately makes the QSO invalid.

Correct messages in KST chat of this kind (communication is in English):

- “let’s (now) conduct a sked\* at 144.388 at 1310z, I’ll be there”
    • “due to QRM, let's change the frequency to 5 kHz higher”
    • “let’s take a break for 15 minutes and try from the beginning”
    • “thanks for the QSO” (after the end of the QSO)

(“Sked” (sked) is radio communication by prior agreement between correspondents at an agreed frequency and at an appointed time. Derived from the English word “schedule”.

**Links:**
*[The MSK144 Protocol for Meteor-Scatter Communication](https://www.arrl.org/files/file/QEX_Next_Issue/SeptOct2017/FrankeTaylor.pdf),[mirror](https://physics.princeton.edu/pulsar/k1jt/MSK144_Protocol_QEX.pdf).* [Meteor Scatter (in German)](https://www.darc.de/fileadmin/_migrated/content_uploads/Vortrag_Meteor_Scatter__Dokumentation.pdf)
*[VHF Managers Handbook](https://www.iaru-r1.org/about-us/committees-and-working-groups/vhf-uhf-shf-committee-c5/)- description of the standard MS procedure* <https://groups.io/g/MSHV/topics>
\*[Interesting article about MS on the Mari-El amateur radio site](http://hamradio.mari-el.ru/view_lessons.php)

In the eastern hemisphere, transmissions from west to east and from north to south should occur in period 2 (Western Europe). Transfers from east to west and from south to north - in the 1st period (Russia). The IARU T/R period for Region 1 digital modes (MGM) is set to 30 seconds.

According to the IARU rules, a meteor QSO is completed (full) if both stations have received call signs, reports, and a confident confirmation of reception (at least three RRRs or a receipt R36 combined with the report - where R is confirmation of reception, 36 is a response report). Transmitting 73 at the end of a QSO is not required, but is desirable (since amateur radio tradition and some radio amateurs consider transmitting 73 to be the end of a QSO before recording it in the LOG).

The duration of MS QSO is not regulated, but it is forbidden to break it, i.e. split the QSO into several parts over time. This applies to any radio communication, even SSB or FM. After an unsuccessful QSO or a break, the QSO must begin from the very beginning - *transmitting call signs*.

**MS QSO rating table for report**

| burst duration | signal level or Signal/Noise |
|---|---|
| 2 - up to 0.5 seconds | 6 - below S2 or S/N<5db or Signal/Noise |
| 3 - from 0.5 to 1 second | 7 - from S2 to S3 or S/N=5-10db |
| 4 - from 1 to 5 seconds | 8 - from S4 to S5 or S/W=10-15db |
| 5 - over 5 seconds | 9 - above S5 or S/N>15db |

For example: short “burst” up to 0.5 seconds and S/N 5db - report **27**
Long "burst" 2 seconds and S/N 20db - report **49**

If the reflection is not dense enough, a short-term ping lasting 100 milliseconds (0.1 second) is recorded from a single meteor. In this case, however, the number "1" is not used. The minimum report for MS is **26**.

In the MSHV program, the MSK144 mode uses signal assessment (reports) based on the decibel (dB) scale, just like the FT-8 digital mode. For example, a report of +01 indicates 1 dB above the noise floor within a 2.7 kHz bandwidth.

---

### Example MS QSO

A shortened (without repetitions) example of a typical MS QSO:

| **first station** | **second station** |
|---|---|
| CQ OZ1AA JO32 |  |
|  | OZ1AA R1BBB KO59 |
| R1BBB OZ1AA +10 +10 |
|  | OZ1AA R1BBB R-05 R-05 |
| R1BBB OZ1AA RR73 *(complete QSO)* |  |
|  | OZ1AA R1BBB 73 *(complete QSO)* |

---

### Example MS QSO on two frequencies (QSY)

A shortened (without repetitions) example of a typical MS QSO when working using the QSY method - after establishing contact, switching to a QRM-free frequency. The first station transmits on the general calling frequency 144.360, and in the call offers to switch to 144.367:

| **first station** | **second station** |
|---|---|
| CQ 367 OZ1AA JO32*("general call on the main frequency TX 144.360, and the receiving frequency RX 144.367, invites you to make a QSY there")* |  |
|  | OZ1AA R1BBB KO59 *(**response OZ1AA when you click on the TX call sign the program automatically switches to frequency 144.367**)* |
| R1BBB OZ1AA -07 -07 |  |
|  | OZ1AA R1BBB R+11 R+11 *(**the program is now on frequency 144.367**)* |
| OZ1AA R1BBB RR73 *(complete QSO)* |  |
|  | R1BBB OZ1AA 73*(**TX on the same frequency 144.367**, completion of QSO)* |

### An example of a meteor reflection:

[ ![burst](https://ra1ahq.blog/images/2/5/b/0/1/25b010b5e7212a1c3c289e21b566120c09063770-burst.png "burst")](https://ra1ahq.blog/images/2/5/b/0/1/25b010b5e7212a1c3c289e21b566120c09063770-burst.png?cropresize=525,700)

Received and decoded reflections, if there is an Internet connection, go in the form of spots to the server [pskreporter.info](https://pskreporter.info/), and QSO - on [dxmaps.com](https://www.dxmaps.com/spots/mapg.php?Lan=E)

[ ![map](https://ra1ahq.blog/images/5/5/f/3/4/55f34cb19df30ebc5e4d2b90f9fb6da31ffd9109-screenshot20210812010227.png "map of MSK144 monitors")](https://ra1ahq.blog/images/5/5/f/3/4/55f34cb19df30ebc5e4d2b90f9fb6da31ffd9109-screenshot20210812010227.png?cropresize=525,700)

[ ![map2](https://ra1ahq.blog/images/8/0/f/c/8/80fc811f2213565fb1f5066ea340821facdd2657-screenshot20210812010730.png "map dxmaps")](https://ra1ahq.blog/images/8/0/f/c/8/80fc811f2213565fb1f5066ea340821facdd2657-screenshot20210812010730.png?cropresize=525,700)

### The influence of antennas and station power ("setup" - from the word "setup") on distances during MS QSO

The minimum and maximum distance for MS QSO is 900 and 1500 km. At such distances it is possible to conduct radio communications with simpler antennas (4-5 elements). With a large number of reflections, QSOs are carried out within 5 minutes, since reflections from meteors are literally audible, the reflection from ionized traces is so strong. Above 1500 to 2100 km - there is an area for unstable, difficult conditions where MS reflection signals are weaker: antenna stacks of 9-15 elements (two or four "booms") together with a PA (power amplifier) ​​or a 100 W transceiver are suitable, patience, perseverance with random QSOs and / or organization of skeds is required.

If you draw two circles of the indicated diameters in Google Maps or Yandex Maps, you can estimate with which regions (federal districts) or countries it is possible to establish radio communications. I used pale green to indicate simpler conditions MS 900-1500 km, and pale yellow to indicate more complex conditions (1500-2100 km). Over 21

[ ![Map of potential MS radio contacts](https://ra1ahq.blog/images/d/8/9/d/7/d89d77e608720bc0b90a37f5a028e2084f7544d0-yellowmap.png "Map of potential MS radio contacts")](https://ra1ahq.blog/images/d/8/9/d/7/d89d77e608720bc0b90a37f5a028e2084f7544d0-yellowmap.png?cropresize=525,700)

### Related publications

 [ ![](https://ra1ahq.blog/images/f/3/a/2/c/f3a2c07ef5b32c0308ab703405a5a5ca87b75283-archer-ac600-728.webp) Установка драйвера ядра для Wi-Fi адаптера TP-Link после обновления ОС Debian ](https://ra1ahq.blog/en/ustanovka-draivera-yadra-dlya-wi-fi-adaptera-tp-link-posle-obnovleniya-os-debian) 

 [ ![](https://ra1ahq.blog/images/d/2/5/c/7/d25c7282750b398f71041fb8b90640b692e7e4b8-decibelfmtitle.png) Linux Cinnamon Desktop Applets for Listening to Internet Radio Stations ](https://ra1ahq.blog/en/applety-dlya-rabochego-stola-linux-cinnamon-dlya-proslushivaniya-internet-radiostancii) 

 [ ![No picture](https://ra1ahq.blog/user/themes/mytheme/images/no-image.png) Passing a parameter to a Linux module/driver ](https://ra1ahq.blog/en/peredacha-parametra-modulyu-draiveru-linux) 

 [ ![](https://ra1ahq.blog/images/5/c/4/e/a/5c4ea9c8c3f0b4dd890116d8fe7cbadfdb9814ba-archer-ac600.webp) Installing the TP-Link Archer T600U Nano Wi-Fi adapter driver in Debian 13 "Trixie" ](https://ra1ahq.blog/en/ustanovka-draivera-wi-fi-adaptera-tp-link-archer-t600u-nano-v-debian-13-trixie) 

 [ ![](https://ra1ahq.blog/images/b/f/f/0/f/bff0f99f5897e0420fac9a6eef7254247f39c29d-pulseaudio-equalizer.png) Installing the audio equalizer pulseaudio-equalizer-ladspa on Linux ](https://ra1ahq.blog/en/ustanovka-v-linux-ekvalaizera-zvuka-pulseaudio-equalizer-ladspa) 

[ Backward](https://ra1ahq.blog/en/opyt-ispolzovaniya-aprsdroid-s-radiostanciei-baofeng "Previuous page")

[ Forward ](https://ra1ahq.blog/en/radio-rossii-v-pskovskoi-oblasti "Next page")

## Languages

- [Русский](https://ra1ahq.blog/posts/mshv-ustanovka-v-linux-mint)
- [English](https://ra1ahq.blog/en/mshv-ustanovka-v-linux-mint)
- [Deutsch](https://ra1ahq.blog/de/posts/mshv-ustanovka-v-linux-mint)
- [Français](https://ra1ahq.blog/fr/posts/mshv-ustanovka-v-linux-mint)
- [中文 (简体) (cn)](https://ra1ahq.blog/zh-cn/posts/mshv-ustanovka-v-linux-mint)

## Theme

## RSS feeds

 [ Atom 1.0](https://ra1ahq.blog/en/.atom) [ RSS](https://ra1ahq.blog/en/.rss) 

## Popular tags

 [APRS](https://ra1ahq.blog/en/tag:APRS) [CW](https://ra1ahq.blog/en/tag:CW) [DX](https://ra1ahq.blog/en/tag:DX) [FM](https://ra1ahq.blog/en/tag:FM) [Linux](https://ra1ahq.blog/en/tag:Linux) [VHF](https://ra1ahq.blog/en/tag:VHF) [antennas](https://ra1ahq.blog/en/tag:antennas) [firefox](https://ra1ahq.blog/en/tag:firefox) [morse](https://ra1ahq.blog/en/tag:morse) [soundtrack](https://ra1ahq.blog/en/tag:soundtrack) [video](https://ra1ahq.blog/en/tag:video) [windows](https://ra1ahq.blog/en/tag:windows) [youtube](https://ra1ahq.blog/en/tag:youtube) [КВ](https://ra1ahq.blog/en/tag:%D0%9A%D0%92) [ТВ](https://ra1ahq.blog/en/tag:%D0%A2%D0%92) [УКВ](https://ra1ahq.blog/en/tag:%D0%A3%D0%9A%D0%92) [антенны](https://ra1ahq.blog/en/tag:%D0%B0%D0%BD%D1%82%D0%B5%D0%BD%D0%BD%D1%8B) [безопасность](https://ra1ahq.blog/en/tag:%D0%B1%D0%B5%D0%B7%D0%BE%D0%BF%D0%B0%D1%81%D0%BD%D0%BE%D1%81%D1%82%D1%8C) [длинные волны](https://ra1ahq.blog/en/tag:%D0%B4%D0%BB%D0%B8%D0%BD%D0%BD%D1%8B%D0%B5%20%D0%B2%D0%BE%D0%BB%D0%BD%D1%8B) [путешествия](https://ra1ahq.blog/en/tag:%D0%BF%D1%83%D1%82%D0%B5%D1%88%D0%B5%D1%81%D1%82%D0%B2%D0%B8%D1%8F) [религия](https://ra1ahq.blog/en/tag:%D1%80%D0%B5%D0%BB%D0%B8%D0%B3%D0%B8%D1%8F) [соревнования](https://ra1ahq.blog/en/tag:%D1%81%D0%BE%D1%80%D0%B5%D0%B2%D0%BD%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D1%8F) [спутники](https://ra1ahq.blog/en/tag:%D1%81%D0%BF%D1%83%D1%82%D0%BD%D0%B8%D0%BA%D0%B8) [средние волны](https://ra1ahq.blog/en/tag:%D1%81%D1%80%D0%B5%D0%B4%D0%BD%D0%B8%D0%B5%20%D0%B2%D0%BE%D0%BB%D0%BD%D1%8B) [схемы](https://ra1ahq.blog/en/tag:%D1%81%D1%85%D0%B5%D0%BC%D1%8B) [тесты](https://ra1ahq.blog/en/tag:%D1%82%D0%B5%D1%81%D1%82%D1%8B) [трансивер](https://ra1ahq.blog/en/tag:%D1%82%D1%80%D0%B0%D0%BD%D1%81%D0%B8%D0%B2%D0%B5%D1%80) [управление](https://ra1ahq.blog/en/tag:%D1%83%D0%BF%D1%80%D0%B0%D0%B2%D0%BB%D0%B5%D0%BD%D0%B8%D0%B5) [фотографии](https://ra1ahq.blog/en/tag:%D1%84%D0%BE%D1%82%D0%BE%D0%B3%D1%80%D0%B0%D1%84%D0%B8%D0%B8) 

## Random post

 [ I'll be lucky!](https://ra1ahq.blog/en/random) 

## Archive of posts

- [ October 2026 ✒ 4 ](https://ra1ahq.blog/en/archives_month:oct_2026)
- [ September 2026 ✒ 9 ](https://ra1ahq.blog/en/archives_month:sep_2026)
- [ August 2026 ✒ 6 ](https://ra1ahq.blog/en/archives_month:aug_2026)
- [ July 2026 ✒ 13 ](https://ra1ahq.blog/en/archives_month:jul_2026)
- [ June 2026 ✒ 8 ](https://ra1ahq.blog/en/archives_month:jun_2026)
- [ May 2026 ✒ 2 ](https://ra1ahq.blog/en/archives_month:may_2026)
- [ April 2026 ✒ 6 ](https://ra1ahq.blog/en/archives_month:apr_2026)
- [ March 2026 ✒ 3 ](https://ra1ahq.blog/en/archives_month:mar_2026)
- [ February 2026 ✒ 7 ](https://ra1ahq.blog/en/archives_month:feb_2026)
- [ January 2026 ✒ 8 ](https://ra1ahq.blog/en/archives_month:jan_2026)
- [ December 2025 ✒ 12 ](https://ra1ahq.blog/en/archives_month:dec_2025)
- [ November 2025 ✒ 9 ](https://ra1ahq.blog/en/archives_month:nov_2025)
- [ October 2025 ✒ 8 ](https://ra1ahq.blog/en/archives_month:oct_2025)
- [ September 2025 ✒ 5 ](https://ra1ahq.blog/en/archives_month:sep_2025)
- [ August 2025 ✒ 8 ](https://ra1ahq.blog/en/archives_month:aug_2025)
- [ July 2025 ✒ 6 ](https://ra1ahq.blog/en/archives_month:jul_2025)
- [ June 2025 ✒ 10 ](https://ra1ahq.blog/en/archives_month:jun_2025)
- [ May 2025 ✒ 4 ](https://ra1ahq.blog/en/archives_month:may_2025)
- [ April 2025 ✒ 4 ](https://ra1ahq.blog/en/archives_month:apr_2025)
- [ March 2025 ✒ 4 ](https://ra1ahq.blog/en/archives_month:mar_2025)
- [ February 2025 ✒ 11 ](https://ra1ahq.blog/en/archives_month:feb_2025)
- [ December 2024 ✒ 8 ](https://ra1ahq.blog/en/archives_month:dec_2024)
- [ November 2024 ✒ 2 ](https://ra1ahq.blog/en/archives_month:nov_2024)
- [ October 2024 ✒ 8 ](https://ra1ahq.blog/en/archives_month:oct_2024)
- [ September 2024 ✒ 3 ](https://ra1ahq.blog/en/archives_month:sep_2024)
- [ August 2024 ✒ 5 ](https://ra1ahq.blog/en/archives_month:aug_2024)
- [ July 2024 ✒ 9 ](https://ra1ahq.blog/en/archives_month:jul_2024)
- [ June 2024 ✒ 6 ](https://ra1ahq.blog/en/archives_month:jun_2024)
- [ May 2024 ✒ 7 ](https://ra1ahq.blog/en/archives_month:may_2024)
- [ April 2024 ✒ 5 ](https://ra1ahq.blog/en/archives_month:apr_2024)
- [ March 2024 ✒ 5 ](https://ra1ahq.blog/en/archives_month:mar_2024)
- [ February 2024 ✒ 5 ](https://ra1ahq.blog/en/archives_month:feb_2024)
- [ January 2024 ✒ 6 ](https://ra1ahq.blog/en/archives_month:jan_2024)
- [ December 2023 ✒ 7 ](https://ra1ahq.blog/en/archives_month:dec_2023)
- [ November 2023 ✒ 4 ](https://ra1ahq.blog/en/archives_month:nov_2023)
- [ October 2023 ✒ 8 ](https://ra1ahq.blog/en/archives_month:oct_2023)
- [ September 2023 ✒ 7 ](https://ra1ahq.blog/en/archives_month:sep_2023)
- [ August 2023 ✒ 4 ](https://ra1ahq.blog/en/archives_month:aug_2023)
- [ July 2023 ✒ 7 ](https://ra1ahq.blog/en/archives_month:jul_2023)
- [ June 2023 ✒ 7 ](https://ra1ahq.blog/en/archives_month:jun_2023)
- [ May 2023 ✒ 5 ](https://ra1ahq.blog/en/archives_month:may_2023)
- [ April 2023 ✒ 6 ](https://ra1ahq.blog/en/archives_month:apr_2023)
- [ March 2023 ✒ 5 ](https://ra1ahq.blog/en/archives_month:mar_2023)
- [ February 2023 ✒ 2 ](https://ra1ahq.blog/en/archives_month:feb_2023)
- [ January 2023 ✒ 5 ](https://ra1ahq.blog/en/archives_month:jan_2023)
- [ December 2022 ✒ 7 ](https://ra1ahq.blog/en/archives_month:dec_2022)
- [ November 2022 ✒ 8 ](https://ra1ahq.blog/en/archives_month:nov_2022)
- [ October 2022 ✒ 6 ](https://ra1ahq.blog/en/archives_month:oct_2022)
- [ September 2022 ✒ 9 ](https://ra1ahq.blog/en/archives_month:sep_2022)
- [ August 2022 ✒ 8 ](https://ra1ahq.blog/en/archives_month:aug_2022)
- [ July 2022 ✒ 4 ](https://ra1ahq.blog/en/archives_month:jul_2022)
- [ June 2022 ✒ 9 ](https://ra1ahq.blog/en/archives_month:jun_2022)
- [ May 2022 ✒ 7 ](https://ra1ahq.blog/en/archives_month:may_2022)
- [ April 2022 ✒ 3 ](https://ra1ahq.blog/en/archives_month:apr_2022)
- [ March 2022 ✒ 4 ](https://ra1ahq.blog/en/archives_month:mar_2022)
- [ February 2022 ✒ 6 ](https://ra1ahq.blog/en/archives_month:feb_2022)
- [ January 2022 ✒ 7 ](https://ra1ahq.blog/en/archives_month:jan_2022)
- [ December 2021 ✒ 7 ](https://ra1ahq.blog/en/archives_month:dec_2021)
- [ November 2021 ✒ 7 ](https://ra1ahq.blog/en/archives_month:nov_2021)
- [ October 2021 ✒ 7 ](https://ra1ahq.blog/en/archives_month:oct_2021)
- [ September 2021 ✒ 10 ](https://ra1ahq.blog/en/archives_month:sep_2021)
- [ August 2021 ✒ 6 ](https://ra1ahq.blog/en/archives_month:aug_2021)
- [ July 2021 ✒ 7 ](https://ra1ahq.blog/en/archives_month:jul_2021)
- [ June 2021 ✒ 7 ](https://ra1ahq.blog/en/archives_month:jun_2021)
- [ May 2021 ✒ 7 ](https://ra1ahq.blog/en/archives_month:may_2021)
- [ April 2021 ✒ 4 ](https://ra1ahq.blog/en/archives_month:apr_2021)
- [ March 2021 ✒ 4 ](https://ra1ahq.blog/en/archives_month:mar_2021)
- [ February 2021 ✒ 3 ](https://ra1ahq.blog/en/archives_month:feb_2021)
- [ January 2021 ✒ 4 ](https://ra1ahq.blog/en/archives_month:jan_2021)
- [ December 2020 ✒ 8 ](https://ra1ahq.blog/en/archives_month:dec_2020)
- [ November 2020 ✒ 2 ](https://ra1ahq.blog/en/archives_month:nov_2020)
- [ October 2020 ✒ 3 ](https://ra1ahq.blog/en/archives_month:oct_2020)
- [ September 2020 ✒ 3 ](https://ra1ahq.blog/en/archives_month:sep_2020)
- [ August 2020 ✒ 5 ](https://ra1ahq.blog/en/archives_month:aug_2020)
- [ July 2020 ✒ 5 ](https://ra1ahq.blog/en/archives_month:jul_2020)
- [ June 2020 ✒ 8 ](https://ra1ahq.blog/en/archives_month:jun_2020)
- [ May 2020 ✒ 10 ](https://ra1ahq.blog/en/archives_month:may_2020)
- [ April 2020 ✒ 4 ](https://ra1ahq.blog/en/archives_month:apr_2020)
- [ March 2020 ✒ 2 ](https://ra1ahq.blog/en/archives_month:mar_2020)
- [ January 2020 ✒ 1 ](https://ra1ahq.blog/en/archives_month:jan_2020)
- [ December 2019 ✒ 2 ](https://ra1ahq.blog/en/archives_month:dec_2019)

## Search

## Weather forecast

[На 14 дней](https://world-weather.ru/pogoda/russia/saint_petersburg/14days/)
[world-weather.ru](https://world-weather.ru/)

---

## Navigation

- Parent: [RA1AHQ](https://ra1ahq.blog/en/index.md)
- Previous: [Radio of Russia in the Pskov region](https://ra1ahq.blog/en/radio-rossii-v-pskovskoi-oblasti.md)
- Next: [Experience of using APRSdroid with BaoFeng radio station](https://ra1ahq.blog/en/opyt-ispolzovaniya-aprsdroid-s-radiostanciei-baofeng.md)
