Nov
26
Send a magic SMS to the SIM card of the GSM switch and turn my S3 on and off whenever I want. Thanks to the two 12V inputs on the S3, time switches and direct switches can be selected elegantly. Reason for the measure: reducing the power consumption of the solar system.
Posted by Administrator
Oct
27
Recently I had this problem again: I made a mistake when programming the times for recordings. I only noticed it when I checked its functionality online that evening. The recording wanted to start, but stopped because the S3 could not be initialized due to the error.
Restarting the NUC didn't help. I can't switch the S3 remotely. It is started and ended by a timer. If the S3 is already running after starting the SDR software, it will not connect. I have already developed detailed instructions for this:
http://dxerscorner.tikishop.de/blog/categories/14-ELAD-S3-Special
So if the S3 doesn't start as described, you're out of luck remotely. The remote system is not working.
If you're lucky, everything works again after a restart, but only if the S3 is switched on after starting the software.
This is unacceptable for a device in this price range.
Posted by Administrator
May
17
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.
Start of another instance: C:\Program Files\SDR-Radio.com (V3)\SDR Console.exe /ident=2
Posted by Administrator
Apr
10
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.
Posted by Administrator
