Differences

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

--- cfnet:cfheader:csharp:index [2026/05/29 05:45] – [Contents] mfranklin
+++ cfnet:cfheader:csharp:index [2026/05/29 06:06] (current) – [Simple Digital Output Example] mfranklin
@@ Line 2: / Line 2: @@
 After [[cfnet:cfheader:development_environment:index|setting up a development environment]], simply [[cfnet:cfheader:connecting_to_usb_host:index|connect the CFHEADER module to the development machine]], and then use Visual Studio, and any .NET language (e.g. C# or VB.NET), to automate the IO modules using the [[https://api.comfiletech.com/csharp/api/ComfileTech.Cfnet.Cfheader.html|ComfileTech.Cfnet.Cfheader API]].
+===== Simple Digital Output Example =====
+<code csharp>
+using ComfileTech.Cfnet.Cfheader;
+var cfheader0 = Cfheader.Instances[0];
+var DOModule0 = cfheader0.DigitalOutputModules[0];
+cfheader0.Open();
+while (true)
+{
+    foreach (var channel in DOModule0.Channels.Concat(DOModule0.Channels.Reverse()))
+    {
+        foreach (var state in new[] { true, false })
+        {
+            channel.State = state;
+            cfheader0.Sync();
+            Thread.Sleep(50);
+        }
+    }
+}
+</code>
+{{ :cfnet:cfheader:automating_io_modules:kitt.mp4?900x506 }}
 Debug the entire solution on the Windows development machine before deploying to an ARM Linux or other target device.  Since the development machine is usually much more powerful than the target device, local edit-run-debug iterations are far more productive.