Willis DXERS'CORNER // REMOTELY from the garden

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

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

Sometimes it just doesn't want to: either it refuses to cooperate with the SDR console and ELAD's own software FDM-SW2 or it doesn't record even though everything is programmed in. I have spent hours, days, weeks troubleshooting without really finding anything. As a diagnosis, I present possible diseases of the fine device.

Diagnosis 1: Refuses to cooperate
Symptom: FDM-SW2 and SDR Console do not recognise the device.
Possible cause: the temperature of the environment is significantly above 30°.
Remedy: Cool down or wait for better weather.

Diagnosis 2: Does not record
Possible cause: software update
Remedy: downgrade to the last version

Diagnosis 3: Does not start
If a connection between the S3 and the SDR console or FDM-SW2 is interrupted during operation by switching off, it is not possible to re-establish the connection, even after a restart. After the PC has been idle for a while, everything runs as usual again. I have repeated this attempt several times and since then I have stuck precisely to my switching sequences: a) Start software b) Switch on unit and later c) Exit software d) Switch off the unit.

Diagnosis 4: As described here

Diagnosis 5: As described here

Posted by Administrator