&L(0,"*");
Help
Barionet Scheduler application
This application is designed to schedule IO actions and communication events which are configurable on the setup page.
In the Barionet main setup under config tab "TIME" must be defined a time server (e.g.192.53.103.108) and your time zone, this is required
that the Barionet gets a proper time.
Note, this BCL application is using the european summer-/winter time change rules!
It is not possible to define a date, that means the action/event is repeated every day if the setup is not changed.
The following setup items are available :
Timer 1-10
Here define the time string in the format "hhmmss" (e.g. "091530" for 09:15:30) in 24 hour mode.
If no timer is set then the event/action is not executed.
Default is an empty field.
Action 1-10
Select here the output or relay from the menu.
Note, you should only select the outputs or relays which are available on your Barionet (e.g. Barionet50 has no outputs)!
Value
Here define the value that should be executed on the output/relay.
0 = turn OFF (inactive)
1 = turn ON (active)
999 = toggle, when on, then switch to off or vice versa
2-9999 = toggle output/relay for n*100 ms, e.g. if you define 50 then it toggles for 5 seconds
Event 1-6
This function allows to send scheduled UDP, TCP, HTTP/CGI and serial messages.
In the Event field define the message string inclusive header, the header defines the type of communication.
Use the following syntax :
udp://ipaddress:port number/command
or
http://ipaddress:port number/command
or
com1://command
e.g.
udp://192.168.1.20:12301/setio,1,1
or
http://192.168.1.20:80/rc.cgi?o=1,1
or
tcp://192.168.1.20:12302/setio,1,1
or
com1://testmessage
If the port number for a HTTP line is 80 then you can also omit it
(e.g. http://192.168.1.20/rc.cgi?o=1,1)
For UDP, TCP and HTTP is featured also with an optional delay parameter.
To enable it define the timing (in ms) in brackets after the protocol, e.g. :
udp://(1000)192.168.1.20:12301/setio,1,1
or
http://(1000)192.168.1.20:80/rc.cgi?o=1,1
or
tcp://(1000)192.168.1.20:80/setio,1,1
If you omit the brackets with timing then it will be executed without delay.
The delay together with UDP is causing an empty UDP package and the defined delay timing before the UDP message with the defined content is sent.
The delay together with HTTP and TCP is causing a longer (default 1000 ms + defined timing) waiting time until the TCP connection must be established.
For serial messages the timing is ignored. Note the delay feature has also impact on matching the following Timers, in worst case when the timing between
two Timer settings is very close then it could happen that a Timer is missed!
Each Event field allows max. 70 chars!