Job Processor Call
#Firmware/v320
The simplest way to glue the job processor and run scheduled items (both from the job and the jobs libraries):
job.run()
#Firmware/v310 (was job.second)
This function is the entry point of the job dispatch processor.
The simplest method is to assign x.onsecond:
x.onsecond = job.second
The jobs are dispatched and executed from the thread context of job.second.
i.e. When x.onsecond = job.second, the jobs are run from the context of the LuaSecond thread.
The x.onsecond call prototype has changed in #Firmware/v310 to include both the UTC time of the call and the last SecondsAlive value.
i.e.
x.onsecond(utc, secondsalive)
Prior to #Firmware/v310 , the x.onsecond would delay one second between calls. Now, it is a one second interval.
If any call within x.onsecond takes longer than one second, then repeated calls will be made to catch up.
In other words, x.onsecond will be called once for every single change in secondsalive. This is necessary so the the job processor does not miss any timed events.