Recent changes to Generic

Discussion for Generic page

juanp — Wed, 20 Aug 2025 18:30:04 -0000

Hello,

I am looking for a devdesc.xml for a driver, such as the Modbus driver, where the number of I/O's can be defined via a value in the parameter tab.
In short, the array size of the I/O mapping not as predefined constant, but rather as a variable.
Could you help me with this?

Thank you in advance.

Discussion for Generic page

wbj0t — Thu, 25 Jan 2024 11:03:31 -0000

Hi, Ingo!
Im very glad to see this page and your work. But I cant understand many of things.
For example: in the IoDrvFb: cDriverName

In the device description I see only libname, and Device name, what the drivername ?:) and many other fields I dont know what to set and how to start tesing them and what for my attention the first time.

And other fields in the iodrv system libs. Where I can learn this? I need to understand every step, every field in the xml and in the Fbs. Thanks you!

And what are u thinking about book of codesys that written by Gary Pratt? Is there information I need about system libs and drivers?

Thank you :)

Discussion for Generic page

alimans — Thu, 02 Nov 2023 11:02:29 -0000

Hi everybody,
As I did not still findout a proper answer for my question no.3 above, it would be highly appreciated if anybody can answer my question. For reference I repeated my question as bellow:

In case of any problem in device or driver (for example disconnecting or cable unplug) How could I send errors to the codesys? What is the best practice to handle such a situation?

Discussion for Generic page

alimans — Thu, 21 Sep 2023 12:51:33 -0000

Thank you for your kind respond, Ingo!

1- The "IoConfigLateInit" trick got the job done! But, still for some functions like "IoDrvWriteParameter" I could not place break point.

2- Regarding the page, as you set it correctly, I mean pages like EtherCAT and so on. A sample page for this you can find as attachment. So how could I write a plugin and use it in my IO Driver? Because my device uses several configuration and also has some diagnostic register that would be perfect if I could show them to the user in a designed UI.

Thank you again for your instructions!

Discussion for Generic page

Ingo — Thu, 21 Sep 2023 05:53:24 -0000

Hi Alimans,
thanks for the feedback!

1) To debug, you can easily set the compiler define "IoConfigLateInit". That will instruct our device object to execute the Init code of your driver in the first Task-Cycle. This way, you can easily set a breakpoint in your library and debug it.
2) Which pages to you mean in detail? Most of them are just coming from specific configurator plugins. So when you see the configuration pages in EtherCAT or Profinet or s.th., those are developed specifically for this fieldbus.

Cheers,
Ingo

Discussion for Generic page

alimans — Sun, 17 Sep 2023 20:17:18 -0000

Hi Ingo,
Thank you for your nice introduction. I have created a library successfully based on your prepared templates and now, I have following questions:
1- How could I possibly debug my developed FB library that implementing the I/O driver interface library. This also can help me to check the data that are going back and forth between device description and the FB library to know better how things are working and which other options I have.
2- I found out that some other device drivers have more tab pages in Codesys (comparing to default 4 tab pages in for example IoDrvFB), how could I generate and configure data in these pages?
Thank you in advance for your kind answer.

Generic modified by i-campbell

i-campbell — Wed, 29 Sep 2021 09:22:03 -0000

--- v17
+++ v18
@@ -29,7 +29,7 @@
 That the device can be uniquely identified in the device repository on every computer in the world, we need to maintain a few IDs. Please register the ID, which you will be using in the [Device Database](/drv/io-drivers/database).

 * Device Type: Either use the matching one from the templates, or use 8000.
-* VendorID: Use 0004, as this is reserved for all public domain drivers
+* VendorID: Use 0003, as this is reserved for all public domain drivers
 * DeviceID: Use a unique one, which you added to the [Device Database](/drv/io-drivers/database)
 * Version: You are free with that, but you should always increase it when you make changes to the device description

Generic modified by Ingo

Ingo — Tue, 23 Mar 2021 15:50:15 -0000

--- v16
+++ v17
@@ -274,6 +274,12 @@
           <default>0</default>
           <name name="local:DWIN">DWORD Input</name>
           <description name="local:DWIN.Desc">DWORD Input</description>
+          <defaultmapping>
+              <element name="Byte0">Byte0</element>
+              <element name="Byte1">Byte1</element>
+              <element name="Byte2">Byte2</element>
+              <element name="Byte3">Byte3</element>
+          </defaultmapping>
         
 ~~~

Generic modified by Ingo

Ingo — Mon, 29 Jun 2020 06:57:59 -0000

--- v15
+++ v16
@@ -356,6 +356,22 @@
         
 ~~~

+### Arrays
+***IEC:***
+~~~ST
+abyBuffer : ARRAY [0..10] OF BYTE;
+~~~
+
+***DevDesc:***
+~~~xml
+<arraytype name="myArray" basetype="std:BYTE">
+    <firstdimension>
+        <lowerborder>0</lowerborder>
+        <upperborder>10</upperborder>
+    </firstdimension>
+</arraytype>
+~~~
+
 # Driver Interface
 Please always start with a template, when you start writing a driver. This will give you a good skeleton of your driver. Anyway, this chapter contains a few basic informations about specific interface functions.

Generic modified by Ingo

Ingo — Fri, 13 Mar 2020 07:28:41 -0000

--- v14
+++ v15
@@ -248,20 +248,101 @@
 **DevDesc:**

 ~~~xml
+  <types namespace="local">
+   <structtype name="Channel4Byte">
+      <component identifier="Byte0" type="std:BYTE">
+        <default>
+        <visiblename name="local:Byte0">Byte0</visiblename>
+      </default></component>
+      <component identifier="Byte1" type="std:BYTE">
+        <default>
+        <visiblename name="local:Byte1">Byte1</visiblename>
+      </default></component>
+      <component identifier="Byte2" type="std:BYTE">
+        <default>
+        <visiblename name="local:Byte2">Byte2</visiblename>
+      </default></component>
+      <component identifier="Byte3" type="std:BYTE">
+        <default>
+        <visiblename name="local:Byte3">Byte3</visiblename>
+      </default></component>
+    </structtype>
+    </types>
+    ...
+        <parameter type="local:Channel4Byte" parameterid="1000">
+          <attributes download="true" offlineaccess="write" functional="false" channel="input" onlineaccess="readwrite">
+          <default>0</default>
+          <name name="local:DWIN">DWORD Input</name>
+          <description name="local:DWIN.Desc">DWORD Input</description>
+        </attributes></parameter>
+~~~
+
+### Bit Channels
+
+**IEC:**
+
+~~~
+TYPE DUT :
+STRUCT
+   BYTE1 : BYTE;
+   BYTE2 : BYTE;
+   BYTE3 : BYTE;
+   BYTE4 : BYTE;
+END_STRUCT
+END_TYPE
+~~~
+
+**DevDesc:**
+
+~~~xml
+    <bitfieldtype name="Bitfield" basetype="std:BYTE">
+      <component identifier="Bit0" type="std:BOOL">
+        <default>
+        <visiblename name="local:Bitfield.Bit0">Bit0</visiblename>
+      </default></component>
+      <component identifier="Bit1" type="std:BOOL">
+        <default>
+        <visiblename name="local:Bitfield.Bit1">Bit1</visiblename>
+      </default></component>
+      <component identifier="Bit2" type="std:BOOL">
+        <default>
+        <visiblename name="local:Bitfield.Bit2">Bit2</visiblename>
+      </default></component>
+      <component identifier="Bit3" type="std:BOOL">
+        <default>
+        <visiblename name="local:Bitfield.Bit3">Bit3</visiblename>
+      </default></component>
+      <component identifier="Bit4" type="std:BOOL">
+        <default>
+        <visiblename name="local:Bitfield.Bit4">Bit4</visiblename>
+      </default></component>
+      <component identifier="Bit5" type="std:BOOL">
+        <default>
+        <visiblename name="local:Bitfield.Bit5">Bit5</visiblename>
+      </default></component>
+      <component identifier="Bit6" type="std:BOOL">
+        <default>
+        <visiblename name="local:Bitfield.Bit6">Bit6</visiblename>
+      </default></component>
+      <component identifier="Bit7" type="std:BOOL">
+        <default>
+        <visiblename name="local:Bitfield.Bit7">Bit7</visiblename>
+      </default></component>
+    </bitfieldtype>
    <structtype name="local:Channel4Byte">
-      <component identifier="Byte0" type="std:BYTE">
+      <component identifier="Byte0" type="local:Bitfield">
         <default>
         <visiblename name="local:Byte0">Byte0</visiblename>
       </default></component>
-      <component identifier="Byte1" type="std:BYTE">
+      <component identifier="Byte1" type="local:Bitfield">
         <default>
         <visiblename name="local:Byte1">Byte1</visiblename>
       </default></component>
-      <component identifier="Byte2" type="std:BYTE">
+      <component identifier="Byte2" type="local:Bitfield">
         <default>
         <visiblename name="local:Byte2">Byte2</visiblename>
       </default></component>
-      <component identifier="Byte3" type="std:BYTE">
+      <component identifier="Byte3" type="local:Bitfield">
         <default>
         <visiblename name="local:Byte3">Byte3</visiblename>
       </default></component>
@@ -275,85 +356,6 @@
         
 ~~~

-### Bit Channels
-
-**IEC:**
-
-~~~
-TYPE DUT :
-STRUCT
-   BYTE1 : BYTE;
-   BYTE2 : BYTE;
-   BYTE3 : BYTE;
-   BYTE4 : BYTE;
-END_STRUCT
-END_TYPE
-~~~
-
-**DevDesc:**
-
-~~~xml
-    <bitfieldtype name="Bitfield" basetype="std:BYTE">
-      <component identifier="Bit0" type="std:BOOL">
-        <default>
-        <visiblename name="local:Bitfield.Bit0">Bit0</visiblename>
-      </default></component>
-      <component identifier="Bit1" type="std:BOOL">
-        <default>
-        <visiblename name="local:Bitfield.Bit1">Bit1</visiblename>
-      </default></component>
-      <component identifier="Bit2" type="std:BOOL">
-        <default>
-        <visiblename name="local:Bitfield.Bit2">Bit2</visiblename>
-      </default></component>
-      <component identifier="Bit3" type="std:BOOL">
-        <default>
-        <visiblename name="local:Bitfield.Bit3">Bit3</visiblename>
-      </default></component>
-      <component identifier="Bit4" type="std:BOOL">
-        <default>
-        <visiblename name="local:Bitfield.Bit4">Bit4</visiblename>
-      </default></component>
-      <component identifier="Bit5" type="std:BOOL">
-        <default>
-        <visiblename name="local:Bitfield.Bit5">Bit5</visiblename>
-      </default></component>
-      <component identifier="Bit6" type="std:BOOL">
-        <default>
-        <visiblename name="local:Bitfield.Bit6">Bit6</visiblename>
-      </default></component>
-      <component identifier="Bit7" type="std:BOOL">
-        <default>
-        <visiblename name="local:Bitfield.Bit7">Bit7</visiblename>
-      </default></component>
-    </bitfieldtype>
-   <structtype name="local:Channel4Byte">
-      <component identifier="Byte0" type="local:Bitfield">
-        <default>
-        <visiblename name="local:Byte0">Byte0</visiblename>
-      </default></component>
-      <component identifier="Byte1" type="local:Bitfield">
-        <default>
-        <visiblename name="local:Byte1">Byte1</visiblename>
-      </default></component>
-      <component identifier="Byte2" type="local:Bitfield">
-        <default>
-        <visiblename name="local:Byte2">Byte2</visiblename>
-      </default></component>
-      <component identifier="Byte3" type="local:Bitfield">
-        <default>
-        <visiblename name="local:Byte3">Byte3</visiblename>
-      </default></component>
-    </structtype>
-    ...
-        <parameter type="local:Channel4Byte" parameterid="1000">
-          <attributes download="true" offlineaccess="write" functional="false" channel="input" onlineaccess="readwrite">
-          <default>0</default>
-          <name name="local:DWIN">DWORD Input</name>
-          <description name="local:DWIN.Desc">DWORD Input</description>
-        </attributes></parameter>
-~~~
-
 # Driver Interface
 Please always start with a template, when you start writing a driver. This will give you a good skeleton of your driver. Anyway, this chapter contains a few basic informations about specific interface functions.

</component></component></component></component></structtype>