------------------------------------------------------------------------------------------
Split from IOLink_Device FB Error 8601.

Some resolutions:

The diagnostics.subfunctionStatus value of 16#0000_8011 from the IOLink_Device block typically indicates a "write data" error, specifically an error related to the length of the data being written. Here's a breakdown of what each part of this status code represents:

• 16#: Indicates that the following characters represent a hexadecimal value.
• 0000: Typically reserved for general status or no error.
• 8011: This portion of the status code provides additional information about the error.

In this case:

• 80: Indicates a write error.
• 11: Further specifies the type of write error, in this case, it suggests a length mismatch error

Now, double-check the length of the data array being written and ensure that it matches the length specified in the function call.

The question is, What is the correct length?

IOLink_Device Block commands:

• To perform a Power-cycle, you need to change the index number to : 16#0021
• To perform a device reset, you need to change the index number to : 16#0020

I tried to update the post as I am trying to resolve the problem, so sorry for the amount of posts 

But here is the last comment that works for me:

After the power-cycle, the fault persist, but a new errors in the module starting to pop-up.

1. DO NOT use the GSD file gsdml-v2.34-balluff-bni-pnt-508-105-z015-20190301.xml.
2. USE gsdml-v2.34-balluff-bni-pnt-508-105-z015-20210401.xml

You can download the GSD file on: https://www.balluff.com/sv-se/products/BNI005H

Even if the version of both of the GSDs are V2.34, the gsdml-v2.34-balluff-bni-pnt-508-105-z015-20190301.xml do not work.

Hey,

Here is the GSDML :)