www.BrickElectric.com
service must be provided to locate at the server. To read relay module EasyBus Client
Remote Host Name:
Web access URL:
http://192.168.1.105/ getpara[128]=1;
Socket command text:
getpara[128]=1;
To set relay module EasyBus Client Remote Host Name, for example to BrickElectric.com:
Web access URL:
http://192.168.1.105/ setpara[128]=BrickElectric.com;
Socket command text:
setpara[128]=BrickElectric.com;
EasyBus Client Watchdog
In most of networks, router will kill a TCP connection if it is unused for some time period,
an practical time will be 120 seconds. This behavior saves resource for the entire network
but if you really want to keep a long connection between relay module and server, this
behavior will create troubles. Another problem is when the connection is accidently broken,
or the server is unreachable or rebooted at certain moment, the TCP connection will be
lost. You can actively access http interface to reboot the relay module, so it will try to
connect to server again, but you can also use the additional watchdog provided by relay
module, so it will automatically reconnect to the server when no response is received after
some time. The length of this waiting time is also configurable.
If this watchdog is enabled, it is important that your server continuously send
message to the module, otherwise it will automatically disconnect and reconnect
again.
To read relay module EasyBus Client Watchdog:
Web access URL:
http://192.168.1.105/ getpara[127]=1;
Socket command text:
getpara[127]=1;
To set relay module EasyBus Client Watchdog to enable:
Web access URL:
http://192.168.1.105/ setpara[127]=1;
Socket command text:
setpara[127]=1;
Tips:
The higher the value of this parameters, the longer the server un-response time will be
allowed. In good network environment this is recommended so it will save the traffic in
total. For example, setpara[127] = 2, or setpara[127] = 3
, 4 … 9999.
