{{dbox-orange| Backplane class '''must implements''' the {{fname|attach( controler )}} method.<br />The {{fname|attach( controler )}} method is called by [[Mydin-async-or-not#Step_2:_create_instances|configure()]] to expose the backplane properties into the controler object. }}
{{dbox-orange| Backplane class '''must implements''' the {{fname|attach( controler )}} method.<br />The {{fname|attach( controler )}} method is called by [[Mydin-async-or-not#Step_2:_create_instances|configure()]] to expose the backplane properties into the controler object. }}
+
+
== DinControler ==
+
=== Header ===
+
+
* '''Ancestor''' : None
+
* '''Class''' : '''DinControler'''
+
* '''Module''' : controler
+
* '''DIN Size''': Any modules
+
* '''Descr''' : Base class responsible for starting the asynchronous execution. It puts every mechanism in place to initiate the setup then start asynchronous tasks including the userloop task. A this level, the DinControler doesn't know anything about the underlaying microcontroler used. DinControler also takes care of the process termination.
+
+
Details about '''DinControler''' class are available at [[Mydin-async-or-not#Step_5_:_asynchronous_tasks|"asynchronous tasks" details]]. Here is the process behind the {{fname|run()}} method.