users:dagnall53:using_schedules
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
users:dagnall53:using_schedules [2019/05/20 19:09] – dagnall53 | users:dagnall53:using_schedules [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | Index | ||
- | * [[: | ||
- | * [[: | ||
- | * [[: | ||
- | |||
- | |||
- | To help test the code, and gain experience, I have modified a simple schedule created by Jan VanderBorden | ||
- | {{ : | ||
- | |||
- | |||
- | {{: | ||
- | Taking just one example: | ||
- | ACTION " | ||
- | to TEXT object " | ||
- | | ||
- | 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 ("font F4" | ||
- | |||
- | NOTE: This example workspace shows " | ||
- | |||
- | Because the action is called regularly, it can be convenient to change the rocdisplay commands in this action to see how they affect the message. | ||
- | |||
- | 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 " | ||
- | |||
- | 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/using_schedules.1558372187.txt.gz · Last modified: 2019/05/20 19:09 by dagnall53