added blog posts
@ -52,10 +52,6 @@ publishDir = "/var/www/htdocs/dk1mi.radio/"
|
||||
name = "Tags"
|
||||
weight = 4
|
||||
url = "/tags/"
|
||||
[[menu.main]]
|
||||
name = "Links"
|
||||
weight = 5
|
||||
url = "/links/"
|
||||
[[menu.main]]
|
||||
name = "FediHams"
|
||||
weight = 6
|
||||
@ -75,7 +71,7 @@ publishDir = "/var/www/htdocs/dk1mi.radio/"
|
||||
[[menu.footer]]
|
||||
name = "Fediverse"
|
||||
weight = 6
|
||||
url = "https://social.fedihams.net/@DK1MI"
|
||||
url = "https://mastodon.radio/@DK1MI"
|
||||
[[menu.footer]]
|
||||
name = "QRZ"
|
||||
weight = 7
|
||||
|
@ -17,7 +17,7 @@ The FediHams network is neither topic nor location based. All can jump in, have
|
||||
# Diagram
|
||||
The following diagram shows how everything is connected:
|
||||
|
||||
![image](/img/diagram_2.jpg)
|
||||
![image](/img/diagram.jpg)
|
||||
|
||||
# What you can do with this
|
||||
|
||||
|
@ -21,9 +21,6 @@ showthedate: false
|
||||
### Backup
|
||||
* [Restic and Backblaze B2](https://harshadsharma.com/2018/04/restic-and-backblaze-b2-for-backups)
|
||||
|
||||
### Monitoring
|
||||
* [PING.GG](http://ping.gg/) - The world's simplest monitoring service
|
||||
|
||||
### Logging
|
||||
* [GoAccess](https://goaccess.io/) - open source real-time web log analyzer and interactive viewer that runs in a terminal in \*nix systems or through your browser.
|
||||
|
||||
|
172
content/post/cloudlog-on-openbsd.md
Normal file
@ -0,0 +1,172 @@
|
||||
---
|
||||
title: "Installing Cloudlog on OpenBSD"
|
||||
type: post
|
||||
author: micha
|
||||
date: 2023-01-24T16:00:00+02:00
|
||||
tags:
|
||||
- Ham Radio
|
||||
- Logging
|
||||
url: /cloudlog-on-openbsd/
|
||||
---
|
||||
|
||||
This page will guide you through the steps required to install [Cloudlog](https://www.magicbug.co.uk/cloudlog/) onto an OpenBSD web server that is using the OHMP stack (that's OpenBSD, httpd, MariaDB and PHP). Most of the text has been taken from the page [Installation on a FreeBSD Server](https://github.com/magicbug/Cloudlog/wiki/Installation-on-a-FreeBSD-Server) and adapted to OpenBSD. You can find [this guide also in the Cloudlog wiki](https://github.com/magicbug/Cloudlog/wiki/Installation-on-an-OpenBSD-Server).
|
||||
|
||||
# Prerequisites
|
||||
|
||||
* Operating System: [OpenBSD](https://www.openbsd.org/) (tested on OpenBSD 7.2)
|
||||
* Web server: [httpd](https://man.openbsd.org/httpd)
|
||||
* Database: [MariaDB](https://mariadb.org)
|
||||
* [PHP](https://www.php.net) 8.0
|
||||
|
||||
# Installation
|
||||
## 1. Prepare Server Stack
|
||||
|
||||
Installing OpenBSD, database server and web server are tasks that are outside the scope of this guide but there are plenty of resources to help you get started. Have a look at this [guide](http://www.h-i-r.net/p/setting-up-openbsd-relayd-based-httpd.html) or at the corresponding man pages.
|
||||
|
||||
Once you have your server stack installed, make sure that the required additionally packages are available. Example of installing PHP80 and required packages:
|
||||
|
||||
```
|
||||
# doas pkg_add php-mysqli mariadb-server curl php-curl
|
||||
```
|
||||
|
||||
Please choose version 8.0 when asked by the installer.
|
||||
|
||||
## 2. Download Cloudlog using Git
|
||||
|
||||
For ease of installation and updating, it is recommended to acquire the Cloudlog application files using [Git](https://git-scm.com/). If GIT is not yet installed on your system use `pkg_add git` to obtain it.
|
||||
|
||||
The `git clone` command is used to fetch the latest build of Cloudlog from the repository on [GitHub](https://github.com/magicbug/Cloudlog). This command downloads the application files in their current state on the _master_ branch:
|
||||
|
||||
```
|
||||
# doas git clone https://github.com/magicbug/Cloudlog.git [output_directory]
|
||||
```
|
||||
Replace _output_directory_ with the full path to the directory where you'd like the application files to be created locally (don't include the square brackets). In this example, we use the DocumentRoot directory "/var/www/htdocs/cloudlog":
|
||||
|
||||
```
|
||||
# doas git clone https://github.com/magicbug/Cloudlog.git /var/www/htdocs/cloudlog
|
||||
```
|
||||
|
||||
## 3. Set Directory Ownership and Permissions
|
||||
|
||||
During normal operation, Cloudlog will need to write to certain files and directories within the root Cloudlog directory (i.e. where you extracted the files in the previous step). You'll need to set the permissions and ownership on these directories appropriately.
|
||||
|
||||
The following folders need to be writable by PHP:
|
||||
|
||||
* /application/config/
|
||||
* /application/logs
|
||||
* /assets/qslcard/
|
||||
* /backup
|
||||
* /updates
|
||||
* /uploads
|
||||
* /images/eqsl_card_images/
|
||||
|
||||
|
||||
⚠️ **Warning 1**: The following commands assume that you are using the OpenBSD _www_ webserver group. You should verify this is the case and modify the commands below appropriately if it is something different.
|
||||
|
||||
⚠️ **Warning 2**: Replace `/var/www/htdocs/cloudlog` in the below commands with the appropriate directory if you cloned the Git repository somewhere else in the previous step.
|
||||
|
||||
**⚠️ Warning 3**: It is your responsibility to ensure you protect your system from intruders/attacks. These commands and permissions are just examples used to get Cloudlog up and running and are not a guide on how to achieve a secure system. You should review these permissions after installation and make appropriate changes if you determine that finer-grained access control is needed.
|
||||
|
||||
First, set ownership using:
|
||||
```
|
||||
# doas chown -R root:www /var/www/htdocs/cloudlog/application/config/
|
||||
# doas chown -R root:www /var/www/htdocs/cloudlog/application/logs
|
||||
# doas chown -R root:www /var/www/htdocs/cloudlog/assets/qslcard/
|
||||
# doas chown -R root:www /var/www/htdocs/cloudlog/backup
|
||||
# doas chown -R root:www /var/www/htdocs/cloudlog/updates
|
||||
# doas chown -R root:www /var/www/htdocs/cloudlog/uploads
|
||||
# doas chown -R root:www /var/www/htdocs/cloudlog/images/eqsl_card_images/
|
||||
```
|
||||
|
||||
Then grant write permissions on these directories to the group:
|
||||
```
|
||||
# doas chmod -R g+rw /var/www/htdocs/cloudlog/application/config/
|
||||
# doas chmod -R g+rw /var/www/htdocs/cloudlog/application/logs
|
||||
# doas chmod -R g+rw /var/www/htdocs/cloudlog/assets/qslcard/
|
||||
# doas chmod -R g+rw /var/www/htdocs/cloudlog/backup
|
||||
# doas chmod -R g+rw /var/www/htdocs/cloudlog/updates
|
||||
# doas chmod -R g+rw /var/www/htdocs/cloudlog/uploads
|
||||
# doas chmod -R g+rw /var/www/htdocs/cloudlog/images/eqsl_card_images/
|
||||
```
|
||||
|
||||
More info about granting PHP write permissions can be read [here](https://unix.stackexchange.com/questions/35711/giving-php-permission-to-write-to-files-and-folders)
|
||||
|
||||
## 4. Create a SQL Database and User
|
||||
|
||||
Cloudlog needs a MySQL database to store application and user settings, along with user data such as logbooks.
|
||||
|
||||
We'll cover the basic steps for creating a blank database but we won't go into much detail for the specific steps relating to securing your database server. Please refer to [the MySQL documentation](https://dev.mysql.com/doc/refman/8.0/en/mysql-secure-installation.html) as a starting point.
|
||||
|
||||
Anyhow, the following commands will help you set up the database system and perform some first security measures:
|
||||
|
||||
```
|
||||
# doas /usr/local/bin/mysql_install_db
|
||||
# doas rcctl start mysqld
|
||||
# doas /usr/local/bin/mysql_secure_installation
|
||||
```
|
||||
|
||||
After this, let's start by using the `mysql` command to connect as the _root_ user. If your server is already configured for something else then you may have another user configured with the ability to create databases - you can substitute that username if so. Read more about connecting with the `mysql` client in [the MySQL documentation](https://dev.mysql.com/doc/mysql-getting-started/en/#mysql-getting-started-connecting).
|
||||
|
||||
```
|
||||
# doas mysql -u root -p
|
||||
```
|
||||
|
||||
Now issue the following command to create a database for Cloudlog, replacing `db_name` with a name of your choice. Note this name down as you'll need it later for the Cloudlog install wizard.
|
||||
|
||||
```sql
|
||||
CREATE DATABASE db_name;
|
||||
```
|
||||
|
||||
Next, create a user and grant it privileges on the Cloudlog database. Creating a new user is optional if you already have a valid non-root user on the MariaDB server. Remember to again replace `db_name` with the name you chose previously for the database, `user1` with the name of the user to create and `password1` with a strong password! Keep the username and password safe as you'll need these for the Cloudlog install wizard later.
|
||||
|
||||
```sql
|
||||
CREATE USER 'user1'@localhost IDENTIFIED BY 'password1';
|
||||
GRANT ALL PRIVILEGES ON db_name.* TO 'user1'@'localhost';
|
||||
QUIT
|
||||
```
|
||||
|
||||
## 5. Make some important file accessible to httpd
|
||||
|
||||
OpenBSD's httpd is running inside a chroot and therefore sees '/var/www/' as '/'. This again means that httpd's worker processes can't access files residing in '/etc', for example. We can make these certain files accessible by copying them into the chroot directory. It is probably also possible to link them but this has not been tested by me.
|
||||
|
||||
```
|
||||
# doas mkdir -p /var/www/etc/ssl
|
||||
# doas cp /etc/ssl/cert.pem /var/www/etc/ssl/
|
||||
# doas cp /etc/resolv.conf /var/www/etc/
|
||||
# doas cp /etc/services /var/www/etc/
|
||||
```
|
||||
|
||||
## Configure PHP and enable modules
|
||||
|
||||
We need to configure some items inside the file `/etc/php-8.0.ini` that are required by Cloudlog:
|
||||
|
||||
Please find and adapt the following line:
|
||||
|
||||
```
|
||||
allow_url_fopen = On
|
||||
```
|
||||
|
||||
Also uncomment the following modules inside the above mentioned file:
|
||||
|
||||
```
|
||||
extension=bz2
|
||||
extension=curl
|
||||
extension=mbstring
|
||||
extension=openssl
|
||||
```
|
||||
|
||||
## 6. Run the Cloudlog Install Wizard
|
||||
|
||||
You need to run the install wizard. At this point, please open `<url-to-cloudlog>/install` and follow the guide.
|
||||
|
||||
When you have completed the install wizard, do the following:
|
||||
|
||||
* Create a new admin account (Admin Dropdown) and delete the demo account
|
||||
* Update Country Files (Admin Dropdown)
|
||||
* Create a station profile (Admin Dropdown) and set it as active
|
||||
|
||||
* If you want to know if the person you're working uses LoTW, run: `https://<URL-To-Cloudlog>/index.php/lotw/load_users`. This is the initial run, but we'll run this every week from cron momentarily.
|
||||
|
||||
# Post-Install Tasks
|
||||
|
||||
The OpenBSD install tutorial ends here and refers to the probably more regularily updated [Linux Installation Guide](https://github.com/magicbug/Cloudlog/wiki/Installation) for the post-install tasks.
|
16
content/post/cloudlogoffline2qrz.md
Normal file
@ -0,0 +1,16 @@
|
||||
---
|
||||
title: "Offline/Mobile logging to QRZ.com with CloudLogOffline"
|
||||
type: post
|
||||
author: micha
|
||||
date: 2023-02-10T22:00:00+02:00
|
||||
tags:
|
||||
- Ham Radio
|
||||
- Logging
|
||||
url: /cloudlogoffline-to-qrz/
|
||||
---
|
||||
|
||||
Do you ever wanted to log QSOs offline with an Android/iOS/Desktop app and then upload them to the QRZ logbook? Now you can. Since I am not capable of developing such an app and there is already a really good app with CloudlogOffline, I have developed CloudlogOffline2QRZ. It is a simple Python application that pretends to be a Cloudlog instance.
|
||||
|
||||
It offers a similar API to Cloudlog and forwards all transmitted QSOs to the QRZ.com logbook. This way you can use CloudlogOffline e.g. on your smartphone for logging and then upload the QSOs to QRZ.com via CloudlogOffline2QRZ.
|
||||
|
||||
You can find the code and more information [here](https://codeberg.org/mclemens/CloudlogOffline2QRZ).
|
18
content/post/coax-relay-wall-mount.md
Normal file
@ -0,0 +1,18 @@
|
||||
---
|
||||
title: "Wall Mount for CX600 Coaxial Relays"
|
||||
type: post
|
||||
author: micha
|
||||
date: 2023-01-26T18:00:00+02:00
|
||||
url: /coax-relay-wall-mount/
|
||||
tags:
|
||||
- Ham Radio
|
||||
- 3D Printing
|
||||
---
|
||||
|
||||
I've designed a simple snap-on wall mount for CX600 coxial relays:
|
||||
|
||||
![image](/img/coaxrelais_wallmount_1.jpg)
|
||||
|
||||
![image](/img/coaxrelais_wallmount_2.jpg)
|
||||
|
||||
You can [download the design on Thingiverse](https://www.thingiverse.com/thing:5811418).
|
41
content/post/dual-band-slim-jim.md
Normal file
@ -0,0 +1,41 @@
|
||||
---
|
||||
title: "Building a Dual Band Slim Jim Antenna"
|
||||
type: post
|
||||
author: micha
|
||||
date: 2023-03-26T16:00:00+02:00
|
||||
url: /dual-band-slim-jim/
|
||||
tags:
|
||||
- Ham Radio
|
||||
- antenna
|
||||
- DIY
|
||||
---
|
||||
|
||||
While looking for a 70cm/2m antenna suitable for travelling, I came across the "Praesidenten Antenne" on the net: http://oe1iah.at/Hardware/Antennen/SlimJim2-70.shtml. You can download the referenced PDF also from my server: [PraesidentenAntenne.pdf](/img/PraesidentenAntenne.pdf). The construction of this antenna is quite simple. The parts needed for my version are:
|
||||
|
||||
* approx. 1.4m 240 Ohm cable
|
||||
* BNC socket with already soldered coaxial cable
|
||||
* cable tie
|
||||
* superglue
|
||||
* heat shrink tubing
|
||||
|
||||
![image](/img/pres_ant_1.jpg)
|
||||
|
||||
I followed the instructions linked above and first build the lower part with the soldered BNC socket:
|
||||
|
||||
![image](/img/pres_ant_2.jpg)
|
||||
|
||||
Then, following the instructions, cut out the two 5mm pieces from one of the wires, soldered the bridge further up and applied heat shrink tubing to all the modified parts of the cable:
|
||||
|
||||
![image](/img/pres_ant_4.jpg)
|
||||
|
||||
![image](/img/pres_ant_5.jpg)
|
||||
|
||||
At the top end I glued a cable tie into the 240 Ohm wire and fixed it with a heat shrink. I hollowed out the eyelet of the cable tie by cutting out the inner plastic part:
|
||||
|
||||
![image](/img/pres_ant_3.jpg)
|
||||
|
||||
The following picture shows how easy it is to hang the antenna on a curtain rod, for example:
|
||||
|
||||
![image](/img/pres_ant_6.jpg)
|
||||
|
||||
First tests with an HT showed that I could hit more repeaters from inside the house with this antenna than with any of my rubber antennas. Building the antenna was fun and I will take it with me to my next business trip to do make some repeater contacts from the hotel room.
|
47
content/post/ft8.md
Normal file
@ -0,0 +1,47 @@
|
||||
---
|
||||
title: "ChatGPT on FT8 and its impact on the amateur radio hobby"
|
||||
type: post
|
||||
author: micha
|
||||
date: 2023-02-18T10:00:00+02:00
|
||||
tags:
|
||||
- Ham Radio
|
||||
- FT8
|
||||
url: /chatgpt-ft8/
|
||||
---
|
||||
|
||||
I thought it would be fun to let one controversial technology have an opinion about the other controversial technology so I asked ChatGPT about the advantages and disadvantages of the digital mode. I think that both answers are very interesting:
|
||||
|
||||
### Q: Please explain why FT8 is a good thing for the hobby of amateur radio
|
||||
|
||||
A: "FT8 is a popular digital mode used in the hobby of amateur radio. Here are a few reasons why FT8 can be considered a good thing for the hobby:
|
||||
|
||||
It is efficient: FT8 is designed to work even in difficult propagation conditions and can reliably decode weak signals. This makes it an efficient mode for making contacts, especially when conditions are not favorable for other modes.
|
||||
|
||||
It is accessible: FT8 is easy to use and requires minimal technical knowledge to get started. It has a simple interface, and the software automates many of the technical aspects of operating in this mode.
|
||||
|
||||
It is popular: The popularity of FT8 has made it easier to find contacts on the airwaves, which can be especially helpful for those who live in areas with fewer active radio amateurs.
|
||||
|
||||
It is useful for scientific research: Because of its ability to reliably decode weak signals, FT8 is useful for scientific research, including studies of propagation and space weather.
|
||||
|
||||
It is inclusive: FT8 is a mode that can be used by anyone, regardless of their physical ability, age, or location. This makes it a great way for people to connect with others around the world and learn about different cultures and languages.
|
||||
|
||||
Overall, FT8 can be considered a good thing for the hobby of amateur radio because it is efficient, accessible, popular, useful for scientific research, and inclusive."
|
||||
|
||||
|
||||
|
||||
|
||||
### Q: Please tell me why FT8 is bad for the hobby of amateur radio
|
||||
|
||||
A: "While FT8 is a popular digital mode in the hobby of amateur radio and has many benefits, there are also some potential downsides that some people might consider "bad". Here are a few reasons why some people might see FT8 as a negative for the hobby:
|
||||
|
||||
It is impersonal: Because FT8 is highly automated, some people feel that it lacks the personal interaction and human connection that they enjoy in other modes. The standardized messages and quick exchanges may not allow for the same level of conversation and rapport-building as other modes.
|
||||
|
||||
It is less challenging: Some people feel that the ease of use of FT8 makes it less challenging than other modes, which can be a downside for those who enjoy the technical aspects of the hobby and want to push their skills and equipment to the limit.
|
||||
|
||||
It is less social: The highly automated nature of FT8 means that there is less opportunity for socializing with other operators on the airwaves. In contrast, other modes like voice (SSB) or CW (Morse code) may allow for more conversation and social interaction.
|
||||
|
||||
It contributes to overcrowding on certain bands: The popularity of FT8 means that certain bands can become crowded with users all trying to make contacts using the mode. This can lead to frustration and difficulty making contacts, especially for those who prefer other modes.
|
||||
|
||||
It may discourage new operators from learning other modes: Because FT8 is so popular and easy to use, some people worry that new operators may be drawn to the mode and not develop the skills and experience to use other modes that require more technical knowledge.
|
||||
|
||||
Overall, while there are many benefits to FT8, some people may see it as a negative for the hobby of amateur radio because of its perceived lack of personal interaction, challenges, and social aspects, as well as its potential to overcrowd certain bands and discourage new operators from learning other modes."
|
21
content/post/ham-radio-rss-feeds.md
Normal file
@ -0,0 +1,21 @@
|
||||
---
|
||||
title: "Ham Radio RSS Feeds"
|
||||
type: post
|
||||
author: micha
|
||||
date: 2023-03-12T08:00:00+02:00
|
||||
tags:
|
||||
- Ham Radio
|
||||
- RSS
|
||||
url: /ham-radio-rss-feeds/
|
||||
---
|
||||
|
||||
I have compiled an OPML file which contains a large number of ham radio related RSS feeds. At the moment there are two categories:
|
||||
|
||||
* Fediverse Hams: Web sites of ham radio operators that are active in the Fediverse
|
||||
* Ham Radio: Everything else (news sites, personal blogs etc.)
|
||||
|
||||
You can download the latest version here: https://codeberg.org/mclemens/Ham-Radio-RSS-Feeds/raw/branch/main/hamradio.opml
|
||||
|
||||
The git repository can be found here: https://codeberg.org/mclemens/Ham-Radio-RSS-Feeds
|
||||
|
||||
Please help me with this with additions and corrections by sending PRs, opening issues or [contacting me directly](/about/).
|
@ -11,11 +11,9 @@ tags:
|
||||
- 3D Printing
|
||||
---
|
||||
|
||||
I was looking for a small, lightweigt, affordable but powerful battery for portable ham radio use and decided to buy a Miady 12,8V 7,2Ah LiFePO4 battery.
|
||||
In search of a compact, lightweight and affordable battery that has enough capacity for hours of portable ham radio operations, I came across the infamous Miady 12,8V 7,2Ah LiFePO4 battery which comes with an integrated battery management system (BMS) and can be bought for less than 40 EUR. After some initial testing I decided that this battery fits my needs but I was not happy with the idea of having cables soldered to the battery hanging loosely around. I wanted the battery to have two connectors that are integrated into the battery.
|
||||
|
||||
After some initial testing I decided that this battery fits my needs but I was not happy with the idea of having a PowerPole cable soldered to battery hanging loosely around. I wanted the battery to have two PowerPole connectors (e.g. for the transceiver and the power amplifier) and they should be somehow integrated into the battery.
|
||||
|
||||
The solution was a custom designed 3D printed lid with integrated PowerPole connectors that will be glued to the top of the battery:
|
||||
The solution was a custom designed 3D printed cap with integrated PowerPole connectors that is glued to the top of the battery:
|
||||
|
||||
![image](/img/miady_hat_2.jpg)
|
||||
|
||||
|
37
content/post/pota-da-0013.md
Normal file
@ -0,0 +1,37 @@
|
||||
---
|
||||
title: "Activation of DA-0013 Stromberg-Heuchelberg Nature Park"
|
||||
type: post
|
||||
author: micha
|
||||
date: 2023-02-19T08:00:00+02:00
|
||||
url: /pota-activation-da-0013/
|
||||
tags:
|
||||
- Ham Radio
|
||||
- POTA
|
||||
---
|
||||
|
||||
Yesterday I had a very successful activation of POTA park "DA-0013 Stromberg-Heuchelberg Nature Park". I found a nice spot but had to fight with strong winds so I wasn't able to work on 20m for a longer time since my antenna was flexing a lot. Most of the total 51 contacts were made on 10m followed by 12m.
|
||||
|
||||
![image](/img/da-0013-1.jpg)
|
||||
|
||||
Working conditions:
|
||||
* Xiegu X5105
|
||||
* [PAC-12 vertical telescopic antenna](/review-pac-12-antenna/)
|
||||
* MX-P50M amplifier with 40W output
|
||||
|
||||
![image](/img/da-0013-2.jpg)
|
||||
|
||||
Worked entities:
|
||||
* USA (MA, OH, GA, TX, KY, NY, NC, RI, DE, MI, IN, SC, PA, TN, WI)
|
||||
* Venezuela
|
||||
* Canada
|
||||
* Italy
|
||||
* Poland
|
||||
* Germany
|
||||
* England
|
||||
* Spain
|
||||
* Northern Ireland
|
||||
* Portugal
|
||||
|
||||
![image](/img/da-0013-3.jpg)
|
||||
|
||||
![image](/img/da-0013-4.jpg)
|
@ -11,24 +11,12 @@ url: /solar-powered-shack/
|
||||
|
||||
I have always been fascinated by the infrastructural independence of ham radio stations. You can use them to communicate with people around the world without being dependent on the infrastructure of large companies - apart from the power supply. In order to free myself from this dependency, i have now decided to test the use of a photovoltaic system. For this I have acquired the following:
|
||||
|
||||
* 30W solar panel
|
||||
* 100W solar panel
|
||||
* 2x 100W solar panel
|
||||
* Victron SmartSolar MPPT charge controller
|
||||
* 22Ah AGM battery
|
||||
* 100Ah AGM battery
|
||||
|
||||
The solar panels are mounted on a flat roof at a 30 degree angle facing south and connected to the MPPT charge controller in the shack via a 2.5mm2 cable. The Power Pole distributon block is now directly connected to the load output of the charge controller and draws its power from the AGM battery.
|
||||
|
||||
In order to reduce the power consumption in the shack, I swapped the old shack laptop for an even older android tablet with Termux installed. The tablet is connected to the PV system via a DC/DC converter.
|
||||
|
||||
After 2 weeks now, despite the sometimes very bad weather, I can say that the system is fully sufficient for my purposes. The following is a list of consumers:
|
||||
|
||||
* Yaesu FT-817 UHF/VHF/HF QRP rig
|
||||
* ATU-100 automatic tuner
|
||||
* LED shacksign (I know...)
|
||||
* 7" Kindle Fire with Lineage OS
|
||||
* chargers for my HTs
|
||||
* DC 12V to AC 230V converter
|
||||
|
||||
Very happy so far!
|
||||
|
||||
Update: Added a second panel with 100W and edited this post.
|
||||
In the event of an emergency, if the sun's energy is not sufficient, the shack has a petrol-powered emergency generator available.
|
||||
|
@ -1 +1 @@
|
||||
{"Target":"css/styles.3fe40362df50d49db5018ca03fa5231ecd0fb34469614033aae05e1bf138441ff02925c097d2dc7c53e5792268d26daf9bc0477fcd58c396295764ec6769982c.css","MediaType":"text/css","Data":{"Integrity":"sha512-P+QDYt9Q1J21AYygP6UjHs0Ps0RpYUAzquBeG/E4RB/wKSXAl9LcfFPleSJo0m2vm8BHf81Yw5YpV2TsZ2mYLA=="}}
|
||||
{"Target":"css/styles.c05d68261bf086a9d7713c4f8a6215a3601608e267a816a7ee58f139b3d1aae51222aae2081c8e0c6bd35e1334773b7a16283022f31f92afd93bb37e5e822e66.css","MediaType":"text/css","Data":{"Integrity":"sha512-wF1oJhvwhqnXcTxPimIVo2AWCOJnqBan7ljxObPRquUSIqriCByODGvTXhM0dzt6FigwIvMfkq/ZO7N+XoIuZg=="}}
|
BIN
static/img/PraesidentenAntenne.pdf
Normal file
BIN
static/img/coaxrelais_wallmount_1.jpg
Normal file
After Width: | Height: | Size: 85 KiB |
BIN
static/img/coaxrelais_wallmount_2.jpg
Normal file
After Width: | Height: | Size: 166 KiB |
BIN
static/img/da-0013-1.jpg
Normal file
After Width: | Height: | Size: 186 KiB |
BIN
static/img/da-0013-2.jpg
Normal file
After Width: | Height: | Size: 145 KiB |
BIN
static/img/da-0013-3.jpg
Normal file
After Width: | Height: | Size: 142 KiB |
BIN
static/img/da-0013-4.jpg
Normal file
After Width: | Height: | Size: 506 KiB |
BIN
static/img/diagram_transparent.png
Normal file
After Width: | Height: | Size: 28 KiB |
BIN
static/img/pres_ant_1.jpg
Normal file
After Width: | Height: | Size: 103 KiB |
BIN
static/img/pres_ant_2.jpg
Normal file
After Width: | Height: | Size: 151 KiB |
BIN
static/img/pres_ant_3.jpg
Normal file
After Width: | Height: | Size: 109 KiB |
BIN
static/img/pres_ant_4.jpg
Normal file
After Width: | Height: | Size: 86 KiB |
BIN
static/img/pres_ant_5.jpg
Normal file
After Width: | Height: | Size: 81 KiB |
BIN
static/img/pres_ant_6.jpg
Normal file
After Width: | Height: | Size: 107 KiB |