Mydin-advanced-usage - Historique des versions

Admin : /* Add scheduler task */

2025-04-29T21:27:34Z

Add scheduler task

Admin : /* Add scheduler task */

2025-04-29T21:21:45Z

Add scheduler task

Admin : /* Add scheduler task */

2025-04-29T20:48:31Z

Add scheduler task

Admin : /* Activating watchdog */

2025-04-29T20:37:38Z

Activating watchdog

Admin : /* Activating watchdog */

2025-04-29T20:33:30Z

Activating watchdog

Admin : /* Activating watchdog */

2025-04-29T20:32:54Z

Activating watchdog

Admin : /* Activating watchdog */

2025-04-29T20:27:52Z

Activating watchdog

Admin : /* Using setup() */

2025-04-29T20:25:47Z

Using setup()

Admin : /* Activating watchdog */

2025-04-29T20:25:19Z

Activating watchdog

Admin : /* Activating watchdog */

2025-04-29T20:21:30Z

Activating watchdog

← Version précédente		Version du 29 avril 2025 à 21:27
Ligne 184 :		Ligne 184 :
	'''Now, glue the snipset into the final code:'''		'''Now, glue the snipset into the final code:'''

−	The content here below can be found in	+	The content here below can be found in the [https://github.com/mchobby/micropython-mydin/blob/main/examples/din_controlers/common/async-scheduler.py async-scheduler.py] example:
		+
		+	<syntaxhighlight lang="python">
		+	from mydin import configure
		+	from mydin.pico import Pico3Mod
		+	from mydin.backplane.relays import TwoRelay3Mod
		+	import time, sys, asyncio
		+
		+	import schedule
		+
		+	din = configure( Pico3Mod, TwoRelay3Mod )
		+
		+	# === Define & schedule Jobs ==================
		+	async def job_relay2():
		+	global din
		+	din.rel2.on()
		+	din.leds[1].on()
		+	await asyncio.sleep(30) # Wait 30 Sec
		+	din.leds[1].off()
		+
		+
		+	async def job_toggle_led( led_idx ): # Job with parameter
		+	global din
		+	din.leds[led_idx].toggle()
		+
		+	schedule.every(1).minutes.do( job_relay2 )
		+	schedule.every(3).seconds.do( job_toggle_led, 2 ) # Toggle led 2 of 0..3
		+	schedule.every(7).seconds.do( job_toggle_led, 3 ) # Toggle led 3 of 0..3
		+	# --- Other examples of scheduling ---
		+	# schedule.every(10).seconds.do(job_with_argument, name="MicroPython")
		+	# for h in range( 8, 17 ):
		+	# schedule.every().day.at("%02i:00" % h).do( upd_auth_file_job, drawer )
		+	# schedule.every().day.at("20:00").do( upl_log_file_job, drawer )
		+
		+	# === Main DIN tasks ===================
		+	counter = 0
		+	async def loop( din ):
		+	""" called again and again (like Arduino) """
		+	global counter
		+	counter += 1
		+	# Place your loop code here
		+	print( "loop iteration %3i " % (counter ) )
		+	await asyncio.sleep( 5 )
		+
		+
		+	# === Running Din Project ==============
		+	def create_tasks( async_evloop ):
		+	scheduler_task = async_evloop.create_task( schedule.run_forever() )
		+
		+	din.setup( setup=None, loop=loop, on_tasks_create=create_tasks )
		+	din.run()
		+	</syntaxhighlight>
		+
		+	As the tasks and jobs displays {{fname\|print()}} statements, we can view the activity in the REPL session:
		+
		+	<nowiki>mcu localtime: 1/1/2000 2:22:27
		+	Pico3Mod.run() entering...
		+	USER Loop Setup...
		+	USER Tasks Setup...
		+	running event_loop...
		+	loop iteration 1
		+	DEBUG: Running job <Job object at 20023b40>
		+	DEBUG: Jobs to await: 1
		+	loop iteration 2
		+	DEBUG: Running job <Job object at 20023b40>
		+	DEBUG: Jobs to await: 1
		+	DEBUG: Running job <Job object at 20026530>
		+	DEBUG: Jobs to await: 1
		+	DEBUG: Running job <Job object at 20023b40>
		+	DEBUG: Jobs to await: 1
		+	loop iteration 3
		+	DEBUG: Running job <Job object at 20023b40>
		+	DEBUG: Jobs to await: 1
		+	DEBUG: Running job <Job object at 20026530>
		+	DEBUG: Jobs to await: 1
		+	loop iteration 4
		+	[EXIT] run app exit!
		+	event_loop ends!</nowiki>

← Version précédente		Version du 29 avril 2025 à 21:21
Ligne 143 :		Ligne 143 :
	== Add scheduler task ==		== Add scheduler task ==
	The {{fname\|on_tasks_create}} parameter of the call {{fname\|1=din.setup( setup=None, loop=loop, on_tasks_create=create_tasks )}} allow the ''user_code'' to add one or more asynchronous tasks.		The {{fname\|on_tasks_create}} parameter of the call {{fname\|1=din.setup( setup=None, loop=loop, on_tasks_create=create_tasks )}} allow the ''user_code'' to add one or more asynchronous tasks.
		+
		+	One of the most interesting task to create is a scheduler!
		+
		+	A scheduler like [https://github.com/mchobby/micropython-aioschedule micropython-aioschedule] can do much more than executing a job every minute or so. A scheduler can execute a task every day at a given time, or every Tuesday, every Saturday, a given date, etc.
		+
		+	The following code snippet shows the schedule of two job... jobs defined as '''async functions''' because aioschedule is asynchronous implementation.
		+
		+	<syntaxhighlight lang="python">
		+	import schedule
		+
		+	# === Define & schedule Jobs ==================
		+	async def job_relay2():
		+	global din
		+	din.rel2.on()
		+	din.leds[1].on()
		+	await asyncio.sleep(30) # Wait 30 Sec
		+	din.leds[1].off()
		+	din.rel2.off()
		+
		+
		+	async def job_toggle_led( led_idx ): # Job with parameter
		+	global din
		+	din.leds[led_idx].toggle()
		+
		+	schedule.every(1).minutes.do( job_relay2 )
		+	schedule.every(3).seconds.do( job_toggle_led, 2 ) # Toggle led 2 of 0..3
		+	schedule.every(7).seconds.do( job_toggle_led, 3 ) # Toggle led 3 of 0..3
		+	</syntaxhighlight>
		+
		+	Now, let's use the {{fname\|on_tasks_create}} parameter to create a new asyncio task that runs the scheduler.
		+
		+	<syntaxhighlight lang="python">
		+	def create_tasks( async_evloop ):
		+	# new task to register
		+	scheduler_task = async_evloop.create_task( schedule.run_forever() )
		+
		+	din.setup( setup=None, loop=loop, on_tasks_create=create_tasks )
		+	</syntaxhighlight>
		+
		+	'''Now, glue the snipset into the final code:'''
		+
		+	The content here below can be found in

← Version précédente		Version du 29 avril 2025 à 20:48
Ligne 142 :		Ligne 142 :

	== Add scheduler task ==		== Add scheduler task ==
		+	The {{fname\|on_tasks_create}} parameter of the call {{fname\|1=din.setup( setup=None, loop=loop, on_tasks_create=create_tasks )}} allow the ''user_code'' to add one or more asynchronous tasks.

← Version précédente		Version du 29 avril 2025 à 20:37
Ligne 119 :		Ligne 119 :

	The example [https://github.com/mchobby/micropython-mydin/blob/main/examples/din_controlers/common/async-watchdog.py async-watchdog.py], visible here below, shows how to activate the watchdog. No need to call the {{fname\|din.feed_watchdog()}} because it is already called at every execution cycle of the ''userloop'' .		The example [https://github.com/mchobby/micropython-mydin/blob/main/examples/din_controlers/common/async-watchdog.py async-watchdog.py], visible here below, shows how to activate the watchdog. No need to call the {{fname\|din.feed_watchdog()}} because it is already called at every execution cycle of the ''userloop'' .
		+
		+	{{dbox-gray\| it is possible to lock the ''userloop'' by pressing and holding down the button 1. Keep it down long enough and the watchdog will reset the microcontroler! }}

	<syntaxhighlight lang="python">		<syntaxhighlight lang="python">

@@ Ligne 135 : / Ligne 135 : @@
 din.setup( setup=None, loop=loop )
-# Watchdog resets if loop() stay locked for 2 sec
+din.setup_watchdog( 2000 ) # Watchdog resets if loop() stay locked for 2 sec
 din.run()
 </syntaxhighlight>
 == Add scheduler task ==

@@ Ligne 116 : / Ligne 116 : @@
 Please note that once started, a watchdog cannot be disabled!
-Most of microcontroler do have an hardware watchdog. Once the watchdog started (its timeout set), do not forget to update it (feed it) before it reach the timeout... otherwise it will reset the microcontroler.
+Most of microcontroler do have an hardware watchdog. Once the watchdog started (set its timeout), you will have to ping it (feed it) before it reach the timeout... otherwise it will reset the microcontroler.
 The example [https://github.com/mchobby/micropython-mydin/blob/main/examples/din_controlers/common/async-watchdog.py async-watchdog.py], visible here below, shows how to activate the watchdog. No need to call the {{fname|din.feed_watchdog()}} because it is already called at every execution cycle of the ''userloop'' .
 == Add scheduler task ==

@@ Ligne 76 : / Ligne 76 : @@
 The parameter must be the reference to a regular function accepting a "din" object as parameter.
-'''Good practice:''' instead of defining global variable, it is recommended to add a new attribute on the "din" object. By doing so, the ''userloop''' can easily access the new object.
+'''Good practice:''' instead of defining global variable, it is recommended to add a new attribute on the "din" object. By doing so, the ''userloop'' can easily access the new object.
 The following [https://github.com/mchobby/micropython-mydin/blob/main/examples/din_controlers/pico3mod/async-qwiic-bme280.py async-qwiic-bme280.py example] show how to create such reference and how to retreive it in the ''userloop''. The sensor is a [https://shop.mchobby.be/fr/cartes-breakout/684-bme280-capteur-temperaturehumiditepression-i2cspi-stemmaqtqwiic-3232100006843-adafruit.html BME280 sensor wired] on the I2C bus.

@@ Ligne 118 : / Ligne 118 : @@
 Most of microcontroler do have an hardware watchdog. Once the watchdog started (its timeout set), do not forget to update it (feed it) before it reach the timeout... otherwise it will reset the microcontroler.
-The example [https://github.com/mchobby/micropython-mydin/blob/main/examples/din_controlers/common/async-watchdog.py async-watchdog.py], visible here below, shows how to activate the watchdog. As it is feed at every execution of the ''userloop'', no need to call the {{fname|din.feed_watchdog()}} .
+The example [https://github.com/mchobby/micropython-mydin/blob/main/examples/din_controlers/common/async-watchdog.py async-watchdog.py], visible here below, shows how to activate the watchdog. No need to call the {{fname|din.feed_watchdog()}} because it is called at every execution cycle of the ''userloop'' .
 == Add scheduler task ==