3.14  piWebCAT  . MySQL Font, HeidiSQL - database backups

Please download and install MySQL front  (free database editor)

(HeidiSQL is a good alternative.)

Use   File | Open connection  > New

Give it a name-  why not piWebCAT

Host = - or whatever else is the IP address of your RPi

Port = 3306 - always

user = piwebcat

password = feline

database = radios


It should connect to the database  

Familiarise yourself with  the program.

Note the object browser (table metadata definitions) and data browser tabs.

As supplied, the micro SD card image has configurations for:

  • FTdx101D  using direct piWebCAT (ASCII)  text system
  • FT847, FT818  and FT920 using the older (YAESU5) Yaesu 5 byte system.
  • IC7000    using Icom CI-V
  • A learning progression of Transceiver-H-A, -H-B and -H-C using Hamlib.
    These use --vfo mode for dual VFO systems (Working with my FTdx101D)
  • A learning progression of Transceiver-H-A-NV, -H-B-NV and H-C-NV using Hamlib.
    These do not use --vfo mode. working with my Icom IC7000.
    Use with most Icom transceivers and other  which do not provide CAT access to
    the background VFO.

Exporting the database

Highlight the database: radios in the left column

Right mouse click  >  export  > to SQL file  . choose folder filename   > open

Choose Structure & data  & drop before create.

You have just backed up the whole radios database content (tables) !!

To restore the backup in the future, highlight radios  then R mouse - import  >  SQL file.

Warning:  .. As soon as you click import, the import runs and overwrites your database.
  (  You are not asked to confirm   .... it just happens!)

The drop before create option means that the SQL file will destroy all the tables
before restoring them from file.

You now have a back up of my configuration (There is also one on the website!)

You can safely play!

SQL scripts

I provide some prewritten SQL scripts.

The most important is the one to duplicate a source radio to a new radio within the database.
This involves duplicating the source radio's records in each table.
The identifying rig field in the copy has the name of the new radio.
The unique Id fields in the records have new unique values.