Differences

This shows you the differences between two versions of the page.

--- users:dagnall53:using_schedules [2019/05/20 18:55] – dagnall53
+++ users:dagnall53:using_schedules [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1
@@ Line 1: / Line 1: @@
-Index
-  * [[:users:Dagnall53:Description|WiRocs Description]]
-  * [[:users:dagnall53:rocdisplaytop|RocDisplay Compatibility]]
-  * [[:users:Dagnall53:OLED |Oled Display]]
-I have modified a simple schedule created by Jan VanderBorden
-{{ :users:dagnall53:rocrailoledscheduletest.zip | Test Workspace to illustrate Schedule}}\\
-{{:users:dagnall53:oled_schedule_test.jpg?400 |}}This workspace is based around a "Location" (Haarlem). In the Details, Actions, for this Location object, you will see that when the "scheduleupdate" state is met, Rocrail sends out a lot of actions.
-Taking just one example:
-  ACTION "row1" sends the parameter "{L1F0w3T0} Tijd{L0F4w30T0} 60:1{L1T1F0}  spr {L0W103T1F0SC}{}"
-  to TEXT object "tx1", which is set to interface "bus 50, Address60, display1.
-So, every time the schedule is updated, this code will set up the Top two lines of the OLED on Address 60. It displays Tidj (Time) in the far left column of row 1, and the words " 60:1" in large characters in the middle, and the current time on the top right (line 0) , and "spr" on line 1 far right.
-The text program shows "60:1" to help check which display is showing what..\\ In "proper use" the "60:1" would be replaced with "HAARLEM".
-Action row2 is more complex and uses lots of text variables to show the main timetable.
-The text variables are extracted from the schedule by the "scedule.xml" script.
-For simplicity in the text all the OLEDS show the same schedule.
-There are also two push buttons to test the WiRocS sound effects.
-----
----Expected Node setup---
-{{:users:dagnall53:rocnet_address_50.jpg?400 |}}The workspace expects a WiRocS node with Address 50, and has been tested with up to 3 OLEDS. In my example the node has the name "8266 test Node"