Differences

This shows you the differences between two versions of the page.

--- mos:using_the_modular_output_system [2024/09/18 01:12]
optrix
+++ mos:using_the_modular_output_system [2024/09/18 01:39] (current)
optrix
@@ Line 1: / Line 1: @@
 ====Using the Modular Output System====
-If you'd like to use the Modular Output System in your own projects, the system is relatively easy to use.
+If you'd like to use the [[mos:welcome|Modular Output System]] in your own projects, the system is relatively easy to use.
 ===Include the Library===
@@ Line 19: / Line 19: @@
 This creates an instance of the Output Engine. You pass a name that identifies your application.
-Calling 'start' may block for a few moments, depending on the output configuration. This varies, as some output types are //outgoing// (they only **send** data) while some are //incoming// (they host a service for other systems to query).
+Note that calling 'start' may block for a few moments, depending on the output configuration. This varies, as some output types are //outgoing// (they only **send** data) while some are //incoming// (they host a service for other systems to query).
 ===Writing Key/Value Pairs===
@@ Line 35: / Line 36: @@
 </code>
+===Closing===
+When finished, you should call 'Stop'.
+<code python>
+oe.Stop()
+</code>
+This will stop any HTTP, Modbus/TCP, OPC-UA or other services that were brought up by the Modular Output System.

Using the Modular Output System