Here's how to reboot your Raspberry Pi remotely with Fldigi!

I have a weird issue where sometimes my communications nodes running full-time Fldigi begin lagging heavily during transmission, and output nonsense unmodulated garbage instead of the digital signal. I think it’s related to overheating, but I’m not sure yet. It happens on Windows and linux. The solution is to restart fldigi. A very easy way to accomplish this is to trigger the raspberry pi to reboot remotely with a command, and have it already set up to open fldigi automatically upon boot.

This builds on two other posts I’ve made on this topic.

  1. You will be using the Notifications menu to open a program when its triggered by a custom trigger word. Read more about using the notifications menu in this post:
  1. You’ll need to write a desktop file in the autostart menu to automatically open Fldigi when the Raspberry Pi boots up. I wrote about how to do that at the bottom of this post (ignore the part about scheduling reboots):

I am using a desktop file to reboot the pi. I’m sure there are better ways of doing this with Python or something, but this method was within my grasp for now.

The file can be created anywhere, but I put it into the .fldigi folder. Create a new file and call it reboot.desktop

Open your new file and write the following:

[Desktop Entry]
Exec=sudo reboot

Save and close.

Right click on the new desktop file, click on the Permissions tab, and select Anyone in the Execute dropdown:

Open your Notifications menu:

Screenshot_20230430_230331_VNC Viewer

Make a custom notification word or phrase, uncheck ignore duplicates, and select your new desktop file under Run Program. Add and close.

Select the Spot button in the upper right corner of the fldigi main screen so that the little square turns green:

Screenshot_20230430_210523_VNC Viewer

Now, when your system receives the trigger word or phrase, it will execute the desktop file and reboot. Remember that fldigi will not reopen automatically unless you build the autostart desktop file using the instructions linked above.

1 Like

Okay scratch what I just wrote. A brilliant person just printed out to me that you can enter command line straight into the “run program” field.

There is no reason to create the desktop file

In the above instructions, instead of typing the pathway to the desktop file in the run program field, simply write

sudo reboot

Or, if you want a brief delay

Bash -c “sleep 10 && sudo reboot”

I added a sound clip warning of a reboot in 10 seconds.

This revelation opens up a lot of possibilities for remote control and telemetry gathering without having to learn a programming language, especially combined with the FSQ modem’s ability to retrieve files!