Reflections about a remote mediumwave listeners station

Another possibility is to start and stop the SDR console script-controlled. In this case, the SDR console is started after the idle state. When the recording is finished, the programme is terminated and the PC is put into hibernation mode. I use this option to protect the SDR console from possible errors. They can occur if the console is opened and taken into hibernation mode.

Script for exiting:

@echo
cls
taskkill /IM "SDR Console.exe" /T /F
exit

I integrated the script into the WOSB software with a "bat to exe converter". This software can also be used to initialise the start of the console.

The script technique works flawlessly and also in operation with 2 SDRs, which record at two antennas at different times.

The situation: I operate a remote station in the garden with only 12 V as an MW DXer. Unattended recordings are the basic requirement for this. The station switches on or off in several time intervals. That was hardly a problem with the S2, but the S3 refused to work after the restart.

The NUC is put to sleep by means of the WOSB software and started from there. An example:

xx45h: the NUC is woken up, the SDR console starts or has already started
xx50h: the S3, which was previously de-energized, is supplied with energy by means of a timer
xx55h: the recording starts

After the end of the recording, the NUC is first put to sleep. Only then is the S3 disconnected from the power. After restarting at a different time, the S3 is switched on again and connects smoothly to the SDR console.

If you stick to this guideline, nothing can really go wrong.

And before I forget: only one USB3 port of the USB3 controller may be occupied by the S3. So check your controller.