Modifications
Sauter à la navigation
Sauter à la recherche
← Modification précédente
Modification suivante →
Mydin-async-or-not
(voir la source)
Version du 21 avril 2025 à 21:00
259 octets ajoutés
,
21 avril 2025 à 21:00
→Introduction
Ligne 10 :
Ligne 10 :
In any cases, the myDin library will simplifies the access to the underlaying hardware.
In any cases, the myDin library will simplifies the access to the underlaying hardware.
−
For sure, experimented MicroPython user can use the schematics and
create
their own
code
from top to bottom.
+
For sure, experimented MicroPython user can
also
use the schematics and
creates
their own
software stack
from
the
top to
the
bottom.
−
By creating and
configure
the myDin classes (see later), your code already get a direct access to all the features in the procedural way.
+
By creating and
configuring
the myDin classes (see later), your code already get a direct access to all the features in the procedural way
.
+
+
When calling the additional {{fname|setup()}} and {{fname|run()}} methods the myDin will starts asynchronous processing.
+
+
We strongly encourage to use the asynchronous approach for your projects.
+
+
== Creating myDin ==
+
+
To properly instantiate the DIN controler, you must identifies:
+
# controler board
+
# backplane board
+
+
These information will determine the Python modules to import and the classes names to be used
.
−
By calling the additional {{fname|setup()}} and {{fname|run()}} the myDin will starts asynchronous processing.
−
We strongly recommend to use the asynchronous approach for your projects.
{{MyDin-TRAILER}}
{{MyDin-TRAILER}}
Admin
Bureaucrates
,
Administrateurs
32 908
modifications
Menu de navigation
Outils personnels
Se connecter
Espaces de noms
Page
Discussion
Variantes
Affichages
Lire
Voir le texte source
Voir l’historique
Plus
Rechercher
Navigation
ARDUINO
RASPBERRY-PI
[:: PI Hacking ::]
Particle.IO
Micro Python
Imprimante 3D
Actualités
Modifications récentes
Page au hasard
Aide
Outils
Pages spéciales
Version imprimable