Mobile at last ! New Forest Trip

Having owned the IC-705 for quite some months this was my first time to take it portable. With the weather looking slightly dodgy our group of friends headed to Boulderwood in the New Forest.

Our risk taking with the weather was rewarded with a fantastic, albeit slightly cooler than of late, evening in the New Forest.

Portable in the New Forest in Boulderwood

It was great to go with a friend as although the setup was minimal a helping hand was greatly appreciated. I attached my Alexloop Ham Pack antenna to my Buddipole mast with a bungee which done an excellent job of keeping it secure

bungee, buddipole tripod/mast and ALexloop hampack = nice secure setup

I brought along a couple of fold up tables, one for the ladies ot have their pic-nic on the other for me to setup my radio. I started with just the IC-705 first and tuned to 20m. The quality of the signals away from the QRM of my QTH was simply amazing.

Receive singals where really strong and clear – absence of background noise (QRM)

I did try to reply to the CQ calls, but couldnt get a response this time, but was nethertheless glad to just be trying.

Operating the the Alexloop Ham pack was everything it should be, really easy to tune into the frequency. I was getting SWR of 1.3 to 2 on all the frequencies i tuned. I dare say I could get better as I get more expericned with it, but the gauge on it is fantastic.

Resonence LED in full effect on 20m

As seen in the picture above the LED on the tuning unit shows the power/matching of the antenna to the transceiver. I also used the SWR meter on the IC705. I did bring along my rigexpert (HF) but didnt need it in the end.

Having run 5W on the internal batttery, i then switched to a Lifo battery and got the full 10W portable. My connections to the battery need improvement, but are functional.

I was able to test FT8, and received plenty of signals from around the world. I explained to my friend how FT8 works and our signals on PSKReporter. It was amazing how far we was getting out on 10W and the Alexloop !

2E0fwe portable from the new forest reaches far !

I was unable to make a contact, but I was still gald to be getting out. I need to learn how to adjust the volume control on my linux laptop, as the signal was overloading, i suspect i missed some DX/RX opputnities.

Next we tried WSPR – with the portable battery it was no problem to keep going. I checked the database and my own site and could see that we was getting out nicely, albeit with 10W which is probably the most power I have ever used on WSPR.

WSPR mobile

I must rememer to update my callsign for Mobile operation next time as I only changed it later in WSJT-X.

After digital modes and with the sun / grey line coming in I made one more try on telephony just calling CQ, but alas no responses. I dont feel disappointed, i had limited time and wanted to make sure we got back home all feeling well and having an enjoyable evening, so packed up. Again having a friend help was great, everything was put away with no damage and easily into my camper van.

This was a great first experience of being portable. I really enjoyed it and am sure to keep on trying and will probably make Boudlerwood my goto place. If you ever see me there, dont be shy and am always happy to talk to people who are interested.

Having a great time in Boudlerwood, New Forest with the IC705 and Alex Hampack

This has really added so much more to this already amazing hobby. I can thorougly recommend portable operation !

More vidoes next time, but until then 73

Alan / 2E0FWE

SSTV Update

Have had a great weekend on SSTV on 20m. Thunderstorms are incoming to QTH in IO90BS so have taken the antenna down for now, but will be back once they pass.

I’ve been able to setup an automated upload. The site is here and can also be found on the tabs of the main site. I’ve also subscribed to World SSTV cams, so other amateur radio users can see their reception at my site easily as well.

I’ll take you thru how I setup the Windows and Linux side.

On the Windows host I download and installed KE5RS FTP Widget which is available free with registration info of call/sign location. Run the setup and let it install in the default locations.

The next step on the windows host is to create the local SSTV directory – this is in *addition* to the SSTV images MMSSTV uses.

I opened a command prompt (Start / Run / CMD) and typed the following

cd c:/
mkdir sstvimages

I created a shortcut to the desktop for FTP Widget. This is useful as I found running it as administrator overcome any file permissions issues on the local side. This probably due to the mechanism and file permission settings that MMSTV uses to duplicate the files, running as administrator fixed this.

Create a desktop shortcut, put it next to your MMSTV shortcut if you have one for easy access 🙂

I then run as administrator from the desktop.

run as administrator to avoid permission issues
Select Properties to open the configuration settings
Configure the paths

Now if you have not used FTP in the past the cocent of local and remote paths will be new, and each FTP client will have its own interpretation of how to set it. Usually the remote system is a Linux/Unix system and the actual full remote path is typically /home/sstvimagesusename/images but the FTP Widget takes the login from the FTP Server and uses the short path name, in this case images.

You’ll need to set the local drive to the one created in the DOS prompt earlier. In image name properties, only change the name if you really must, this is important as the crude template i will provide below depends on the filenames matching. You’ll also want to keep the Image history to what ever you iike, by default its 3, I upped it to 12 as this gives a better log of the images.

On the Linux side I’m using vsftpd. I dont mind saying that running FTP in 2021 is slightly unusual, most file transfers are done over SSH / SFTP more recently, but FTP still has its purposes.

I would suggest running vsftpd as it has options for TLS/SSL as well as chrooting. ‘chrooting’ is a method of ‘jailing’ a user to their own location, so in the worst case the credentials are discovered, the only space they can easily access is that of their own home directory, not the ntire OS filesystem (old FTPs that allowed system access could easily be used to accessing /var/log/ and from there discovering other usernames and ‘brute forcing’ the credentials).

Here is the full example vfstpd.conf , you dont need all of this, but from the default you can see the deltas.

# Example config file /etc/vsftpd.conf
#
# The default compiled in settings are fairly paranoid. This sample file
# loosens things up a bit, to make the ftp daemon more usable.
# Please see vsftpd.conf.5 for all compiled in defaults.
#
# READ THIS: This example file is NOT an exhaustive list of vsftpd options.
# Please read the vsftpd.conf.5 manual page to get a full idea of vsftpd's
# capabilities.
#
#
# Run standalone?  vsftpd can run either from an inetd or as a standalone
# daemon started from an initscript.
listen=NO
#
# This directive enables listening on IPv6 sockets. By default, listening
# on the IPv6 "any" address (::) will accept connections from both IPv6
# and IPv4 clients. It is not necessary to listen on *both* IPv4 and IPv6
# sockets. If you want that (perhaps because you want to listen on specific
# addresses) then you must run two copies of vsftpd with two configuration
# files.
listen_ipv6=YES
#
# Allow anonymous FTP? (Disabled by default).
anonymous_enable=NO
#
# Uncomment this to allow local users to log in.
local_enable=YES
#
# Uncomment this to enable any form of FTP write command.
write_enable=YES
#
# Default umask for local users is 077. You may wish to change this to 022,
# if your users expect that (022 is used by most other ftpd's)
#local_umask=022
#
# Uncomment this to allow the anonymous FTP user to upload files. This only
# has an effect if the above global write enable is activated. Also, you will
# obviously need to create a directory writable by the FTP user.
#anon_upload_enable=YES
#
# Uncomment this if you want the anonymous FTP user to be able to create
# new directories.
#anon_mkdir_write_enable=YES
#
# Activate directory messages - messages given to remote users when they
# go into a certain directory.
dirmessage_enable=YES
#
# If enabled, vsftpd will display directory listings with the time
# in  your  local  time  zone.  The default is to display GMT. The
# times returned by the MDTM FTP command are also affected by this
# option.
use_localtime=YES
#
# Activate logging of uploads/downloads.
xferlog_enable=YES
#
# Make sure PORT transfer connections originate from port 20 (ftp-data).
connect_from_port_20=YES
#
# If you want, you can arrange for uploaded anonymous files to be owned by
# a different user. Note! Using "root" for uploaded files is not
# recommended!
#chown_uploads=YES
#chown_username=whoever
#
# You may override where the log file goes if you like. The default is shown
# below.
#xferlog_file=/var/log/vsftpd.log
#
# If you want, you can have your log file in standard ftpd xferlog format.
# Note that the default log file location is /var/log/xferlog in this case.
#xferlog_std_format=YES
#
# You may change the default value for timing out an idle session.
#idle_session_timeout=600
#
# You may change the default value for timing out a data connection.
#data_connection_timeout=120
#
# It is recommended that you define on your system a unique user which the
# ftp server can use as a totally isolated and unprivileged user.
#nopriv_user=ftpsecure
#
# Enable this and the server will recognise asynchronous ABOR requests. Not
# recommended for security (the code is non-trivial). Not enabling it,
# however, may confuse older FTP clients.
#async_abor_enable=YES
#
# By default the server will pretend to allow ASCII mode but in fact ignore
# the request. Turn on the below options to have the server actually do ASCII
# mangling on files when in ASCII mode.
# Beware that on some FTP servers, ASCII support allows a denial of service
# attack (DoS) via the command "SIZE /big/file" in ASCII mode. vsftpd
# predicted this attack and has always been safe, reporting the size of the
# raw file.
# ASCII mangling is a horrible feature of the protocol.
#ascii_upload_enable=YES
#ascii_download_enable=YES
#
# You may fully customise the login banner string:
#ftpd_banner=Welcome to blah FTP service.
#
# You may specify a file of disallowed anonymous e-mail addresses. Apparently
# useful for combatting certain DoS attacks.
#deny_email_enable=YES
# (default follows)
#banned_email_file=/etc/vsftpd.banned_emails
#
# You may restrict local users to their home directories.  See the FAQ for
# the possible risks in this before using chroot_local_user or
# chroot_list_enable below.
chroot_local_user=YES
#
# You may specify an explicit list of local users to chroot() to their home
# directory. If chroot_local_user is YES, then this list becomes a list of
# users to NOT chroot().
# (Warning! chroot'ing can be very dangerous. If using chroot, make sure that
# the user does not have write access to the top level directory within the
# chroot)
chroot_local_user=YES
chroot_list_enable=YES
# (default follows)
chroot_list_file=/etc/vsftpd.chroot_list
#
# You may activate the "-R" option to the builtin ls. This is disabled by
# default to avoid remote users being able to cause excessive I/O on large
# sites. However, some broken FTP clients such as "ncftp" and "mirror" assume
# the presence of the "-R" option, so there is a strong case for enabling it.
#ls_recurse_enable=YES
#
# Customization
#
# Some of vsftpd's settings don't fit the filesystem layout by
# default.
#
# This option should be the name of a directory which is empty.  Also, the
# directory should not be writable by the ftp user. This directory is used
# as a secure chroot() jail at times vsftpd does not require filesystem
# access.
secure_chroot_dir=/var/run/vsftpd/empty
#
# This string is the name of the PAM service vsftpd will use.
pam_service_name=vsftpd
#
# This option specifies the location of the RSA certificate to use for SSL
# encrypted connections.
rsa_cert_file=/etc/ssl/private/vsftpd.pem
rsa_private_key_file=/etc/ssl/private/vsftpd.pem
ssl_enable=YES

#
# Uncomment this to indicate that vsftpd use a utf8 filesystem.
#utf8_filesystem=YES
#
force_local_logins_ssl=NO
force_local_data_ssl=NO

#
#
allow_writeable_chroot=YES

The important settings are

chroot_local_user=YES
chroot_list_enable=YES
allow_writeable_chroot=YES

And the create a vsftpd.chroot_list by echoing the username of the sstvftp user into the required config, i.e.

echo "sstvusername > /etc/vsftpd.chroot_list"

Obviously if you already have vfstpd setup and you should know about chrooting, so use >> rather than > as to not to truncate the chroot_list file.

Now create the Linux local sstv user, this will be the same as the username just echoed

sudo bash
useradd sstvusername -m -d /home/sstvusername sstvusername
passwd sstvusername
su - sstvusername
mkdir images

Be sure to keep a log of the password, of course you can always reset it, but it makes setting the FTP Widget properties easier.

You will then want to add the HTML template. Now i make no apologies for how awful this HTML is, but it will get you up and running, i’m planning to do redo this in HTML4, CSS and what ever JavaScript is necessary.

curl https://hamradio.knipmeyer.co.uk/sstv/ > index.html

You will then need to make your webserver (typically apache) serve home directory content. Rather than re-write the excellent tutorial already provided by Apache, follow this. You may have alternative configurations/different http servers, but Apache is simple and well supported.

With the Unix side complete, its time to finish off the settings for the FTP Widget and SSTV.

FTP Widget Settings

Follow the settings given above, putting in your FTP address, either the hostname or IP address. i.e. myftpserver.bob52.com, <n>.<n>.<n>.<n>. You don’t ned to put in the URI ( ftp:// ) .

The next step is to configure MMSTV to copy the received files into the FTP SSTVPics directory.

History tab, right click, Auto Copy, Assign another folder name

In SSTV goto the History tab and right click the image, select ‘auto copy to another folder’ and assign the folder name to the SSTV c:\sstvimages directory.

With that your received files will now not only be stored locally, they will be automatically FTP’d to your webserver ! If everything goes well, you’ll end up with a page whereby other SSTV users can see how their images are being received and a nice catalogue of recent images for yourself.

Your own SSTV reception page !

The next optional step is to setup registration with World SSTV Cams.

Complete the fields to add your site

Complete the fields to add your site, and with that your site will be added for the whole world to see with thumb-nail updates of the most recent reception of images !

Welcome to the World SSTV site !

I hope this gets you up and running with the exciting and interesting world of SSTV !

Having a great time on SSTV

Recently I started to experiment with SSTV (again) on my IC7300 and Windows desktop.

I’ve not been able to get it to work with the band select, but the audio in, out and importantly PTT fine. I saved the main SSTV calling frequency to my IC7300 (14.2300 USB) and just recall that when i want to use SSTV.

I’ve learned to use, but not to rely on, other KiwiSDRs and other sites that scan SSTV images. Most of the time I am seeing one side of the QSO on the remote sites, a good example of this is the slowscan tv site in the Netherlands.

The conditions have been pretty bad lately, but once in a while I get a really good QSO via SSTV, an example from today below with IV3VBM. I’m using 50W into a 6BTV with conditions being reported as ‘poor’

I am really enjoying SSTV – during the day and overnight I can leave MMSSTV running to receive great pictures, and also look back to see how the propagation has varied. I was amazed to receive these transmissions from the US last night !

As you can see the propergation is clear to see as the quality of the pictures vary.

I’m now working out how to automate the upload and ‘most recent’ pictures to the hamradio website, it shouldnt take me long, but as every life is keeping me very busy !

I hope this encourages other users to try out SSTV, its great way of having a digital QSO with personalized content, so why not give it a go.

Until next time, stay safe and 73 !

Alan / 2E0FWE

15m DX at night ?!

Was just playing about on my radio with FT8, having had one phone QSO on 20m to Italy, then a number of FT8 on 20m as well, thought, lets give 15 meters a try. Having never really persisted at using 15m, it was an ideal time as I could keep an eye on WSJT-X and tidy/file stuff at the same time.

The band looked completely empty when I started, but as the CQ’s keep transmiting, lo and behold I was rewarded with a contact !

FT8 15m contact

There was even some reports to see on PSKReporter !

Reaching far on 15m with 50W of power

I was really suprised, and impressed, with how well the 6BTV is doing, its such a great antenna and I’m getting more out of it every time I have time to use it on the frequencys I previously didnt really use.

Moral of the story is, if the band looks dead, still give it a go ! you never know who you might contact !

10m skip FT8

Having kept an eye on the Kiwi WebSDR I could see plenty of activity on the 10m band, a sure sign that the ‘skip’ from the ‘E Layer’ had picked up. For those ‘new’ to skip, there is an excellent write up here by VK3FS on the behaviour of this ionospheric band.

Here I’ll be showing over the course of just a few short hours how the E-layer built up, the collapsed.

10m skip at 18:04 UTC in IO90BS

Tuning to the 10M frequency for FT8, 28.074, there was allot of activity, transmissions from Europe where coming in the strongest, and even as far as Brazil in South America. It was incredble to see the band so ‘alive’

pskreporter on 10m transmitting 40w

I started transmitting on what had now become a very noisy channel, with plenty of DX around Europe coming in very strong. My own signal from the Hustler 6BTV and 40 watts of power resulted in the QSO’s started to roll in, with little to no reties.

Racking up the QSO’s on FT8

Grid Tracker really came into its own here, making logging to QRZ effortless so I was able to focus on QSO’s rather than uploading ADIF files. This resulted in 2 confirmed QSO’s almost immediately, with an impressive the furthest being 950 miles to IS0SLM in Dolianova.

Band conditions at 19:22 UTC showing the changed in the ‘E Layer’ propagation

Just as quickly the band and opened up, the conditions returned back to the regular behaviour for the E-layer, as seen in the 19:22 and 19:39 signal spectrum from WSJTX.

Band conditions at 19:39 – signals were getting much weaker in WSJTX Wide Graph

By 20:30 I could still be heard but the 6BTV, a vertical and with that being non-directional, wasn’t pulling in the weaker signals for a QSO to be completed.

10m reach at 20:33 with 40W

My reception reports via Pskreporter showed a big difference. I’d be interested to know if this was a phenomenon of the grey-line as the sun set or just the charge in the E-layer collapsing and limiting propagation again.

9 10m QSOs with some great reports and distances

I was still really happy in this ‘short’ time to get so many FT8 QSO’s via 10m. It really is a fascinating band, and one I will do more research with as I continue to improve the performance of the 6BTV and also work 6m with my Yagi antenna

Is skip season coming ?

The great thing of having a WebSDR is the ability to monitor a huge amount of the HF spectrum visibly.

CB Operators on 27Mhz – mostly SSB, heard alot of French and Irish.

Seeing a sudden surge of red comms in the KiwiSDR, I then set about transmitting WSPR packets. And sure enough, I was reaching Italy with 5W on 10M !

WSPR on 10M with 5W

I still have my 2M/70cm and 6M beam to complete, but this really motivates me to get that done sooner rather than later, I hope the ‘skip’ season is around for a while, but it wont for me thats for sure !

In the mean time, here is an excellent video from Oxford Shortwave Youtube channel, demonstrating the reach he has on his 2m antenna, something I’d reallly like to do with FT8 as well !

The ‘coolest’ FT8 contact yet ?

Was one of those nights when I couldn’t get my head down after a great Easter bank holiday weekend, so had a little play on FT8 in the small hours. Having used WSJT-X for quite some time I wanted to experiment with other FT8 software, and gave JTDX a try. I followed the setup documents and was soon transmitting and receiving. Some say JTDX has better decode than WSJT-X – I think time will tell.

Tonight (Or is that very early this morning) I had what must be the coolest FT8 contact yet tho

DT8A – 8482 mi on the South Shetland Islands

I have never heard of the “South Shetland Islands” until they appeared in the JTDX log – I was quick to click and respond, then patiently wait in the hope my call got responded to. Sure enough, with a few minutes and on 20 watts of power DT8A responded and my signal report was received. What I do with all FT8 contacts is to check the QRZ page and read up to add a little more ‘this is more than just a signal report’ to the QSO, I was amazed at DT8A’s page and the fantastic photos !

In particular as my good lady is South Korean, I found it very interesting that Mr Lee was stationed in such a remote part of the world !

So glad to have reached Mr Lee and I hope his work/research in the South Shetlands goes really well !

Uni assignment takes over blog!

Hi all !

Not sure how many people read this on a regular basis, but needless to say apologies for the absence of updates in recent weeks. I’ve got loads of updates to do, with pictures and videos but my MSc has taken over my life at the moment (outside of work).

Good news one of my modules on Web Technologies i’ve embraced my course and my hobby and am using WSPR data, amongst others, as one of the components of a website I am building.

You’ll find the code over on github.

In the mean time, stay safe and keep well !

Alan, 2E0FWE

ICOM 7300 & SM-50

My HF Telephony problem

Whilst i enjoy a ‘ragchew’ on the IC-705 via D-STAR, the Internet and ‘Bit Encoding Rate’ (BER) has more to do with the quality of the received signal than an actual radio wave. (I use a Pi-Star hot-spot as there is no DSTAR repeater nearby IO90).

With that I know that the IC-7300 is a very capable radio on its own, but even with previous antennas having access to all bands did I ‘try’ telephony that much, preferring to stick to digital communications via the computer. I thought it was time to give it a try and get used to operating telephony on the IC-7300.

The inspiring video section !

I checked out this video and it gave very good examples of setting up the audio for various transmit types. If you have a 7300 it well worth the watch and I’m sure the same principals apply to other radios.

Setup the 7300 for optimal audio

Tim, G5TM, has a great video on calling CQ. Having watched the video I was up for trying calling CQ on the 40 meter dipole I am currently using !

G5TM with great advice on calling CQ

I started calling CQ not expecting any replies, but amazingly on 50W on a dipole I did ! My first QSO on 40m was with IZ6TGS. He was obivously a really experienced operator and it was amazing to reach him ! I was immeadilty drawn to how unprepared I was to ‘log’ – when doing FT8, its so well setup it make it easy. Suddenly I was trying write down the call sign and any other details. Thankfully Adrio was a patient and great operator, we managed to give a report each way and I had made my first HF SSB contact !

It did really show I needed some ‘help’ with logging and operating. Having seen both M0MCX and G5TM operate live on air (its great watching a live stream!) they use a free piece of software called N1MM Logger. You can see them both as they start the QSO they are typing in the call sign and any details they can garner. My problem was that I was restricted to the hand-microphone and my Windows PC neither has a screen or keyboard attached as I connect via Remote Desktop Protocol (RDP). Whilst having recently tided my shack-tables up, there is still limited space on my 7300 table.

I was able to come up with the following solution !

Keyboard and Screen Technology

They keyboard and mouse come as a set from Amazon, the Perixx PERIDUO-212 Wired Mini Keyboard fits nicely on the keyboard shelf under the 7300, along side the BHI Dual In-Line Filter. For £16.99 this was a really good piece of kit, obviousy its not as good as the keyboard i use on my mac, but then i’m mostly using it for typing out call signs and reports, not developing stuff 🙂

I combined this with the 7 Inch Small HDMI Monitor with VGA which cost £36.99. Even at 7 inches and a respectable 1024×600 resolution, I could easily see NIMM with no problem when using my radio. It fits very nicely on the desk and comes with a fairly decent stand. I’ve not even had to fix it to the table and its staying up nicely.

SM-50

The last part of the equation, is no doubt, the most important. Whilst having a QSO i struggled to write down the call sign as my hand had a handmic in it. Whilst there are many microphones out there, the SM-50 is the recommended microphone within the 7300 manual and importantly receives very good reviews on eham. It is not a cheap microphone, nor is it expensive, as my son can attest in his experience of sound engineering, microphones can get *Very* expensive depending on what you want to record and where.

I orderd the SM-50, i was very impressed with how sturdy the base and the flexability of the neck. I could bend this perfectly over to me a few inches from my mouth to make operating alot easier.

The SM-50 is a fantastic microphone for the 7300

I went about setting the 7300 following the videos above and adjusting the microphone gain on the underside of the SM-50 to match the 7300. I also read the manual on how to setup recording my ‘best’ voice for 7300 so i could replay my CQ call.

This also made listening via Wesbree WEBSDR very easy and amazingly i could hear myself ! During this time my CQ call on repeat was picked up by DK4EI. We had a great QSO, his setup amazing, but i was happy with 50W and a dipole to come thru with a 5/9 report into Germany!

Conclusion

If you have been on ‘digital modes’ during the solar minimum, and also maybe slightly nervous of going on HF, i can say its worth putting the effort in to get onto SSB/Telephony.

My key points are

  1. As per Tim’s video sound enthusiastic/engaging – I took my time and made a ‘good’ recording/playback feature of the 7300 – it works !
  2. Set up your audio/microphone well and for the audience/conditions, the pileup busting video is really good for this. I’ve not had to change my settings, and i get great audio reports
  3. Get your logging software, or pen/pad easily to hand, fill in details as you go, it makes the QSO more rewarding and you can spot people again !
  4. Get a good microphone, for me the SM-50 suited *my* needs and had good reviews. You may want a different type of microphone and use it in a different way (VOX/PTT/Foot PTT, up/down buttons, on a bracket.. SO MANY FACTORS).

I am getting (braver?) better at HF QSOs and am currently limited to 40 meters, so you might hear me put the shout out during the evenings and night. Until then I really hope to have a QSO with you !

Stay safe / 73

Alan / 2E0FWE