Generic NET Driver: Stopping and Starting the driver using zenon DriverCommand" functions results in "Loading assembly failed""

Generic NET Driver: Stopping and Starting the driver using zenon DriverCommand" functions results in "Loading assembly failed""

Summary

.Net assembly is not loaded any more after stopping and re-starting driver

Description

.Net assembly is not loaded any more after stopping and re-starting driver

Information

In order to get the Driver Extension loaded again by the Generic NET driver, the zenon RT needs to be restarted.

But as soon as the RT project gets reloaded and any driver related configurations were changed, the driver assembly cannot be loaded and the RT needs to be restarted.



Issue Number: 223762
Fixed on Date: 4.8.2020
Versions: 8.20 0 BUILD 67700

    • Related Articles

    • BACnetNG: Driver does not finish reading trendlog object before starting to read another trendlog with maxconcurrentrequest=1

      Description The BACnetNG driver did not finish reading the reading the first trendlog file when the setting for the maximum concurrent requests is set to 1. With specific configurations this can lead to multiple trendlog files being read by the ...

    • zenon Changesets CSV

      Here, you can access a comprehensive list of changes across all maintained versions of the zenon Software Platform as Excel Worksheets. This includes both implemented bug-fixes and new features. Additionally, these lists are available in as Excel ...

    • zenon Changesets Excel

      Here, you can access a comprehensive list of changes across all maintained versions of the zenon Software Platform as Excel Worksheets. This includes both implemented bug-fixes and new features. Additionally, these lists are available in CSV format ...

    • Checklist: Driver(s) cannot establish a reliable communication

      Time estimate: 60 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...

    • Checklist: Communication to TwinCat via BeckhoffNG driver

      Time estimate: 30 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. TwinCAT ADS communication library ...