The CNetDrv driver allows communication with the DOOSAN GUARDIAN Serie Powerplant Controller MPU (microprocessor unit) utilizing the Control Network (CNet) communication protocol. The implementation is based on version 2.4 of the Doosan Enerbility specification with version 1.9.1.0 of the GUARDIAN CPU rack (DsMRkIOC.dll) fieldbus driver and version 1.3.0.2 of the GUARDIAN OIS COMM Protocol (IMCS_OIS.dll) fieldbus driver.

Main functions of the driver

• An existing configuration in Engineering Studio or Service Engine from the previous external driver is adopted based on the latest driver source for this external driver.
• The driver can communicate with an MPU without redundancy over one or two Ethernet connections.
• The driver supports dual redundant MPU configurations as well as triple redundant MPU configurations.
1. In a redundant configuration, the driver expects an MPU to act as the master.
• The driver communicates via TCP/IP via Port 6000.
• The driver enables the automatic creation of variables via the Doosan fieldbus drivers and the integrated solution, for generic data and diagnostic data.
• Variables for .SOE data can be created in Engineering Studio using the CSV import function. The SOE.exe external app is used to create a corresponding import file. This app creates a corresponding.TXT file based on the Doosan fieldbus driver's CSV configuration file.
• The variable addressing is offset-based and uses the CSV configuration file created by the GUARDIAN OIS COMM Protocol configuration wizard. This file contains the necessary information about which variables are available for the corresponding areas, the order of the variables and the corresponding data types. The unique code is also included in this file. This code ensures that the variable configuration and the addressing match the project running on the MPU.
• After a TCP connection has been established, the CNet driver expects a heartbeat message from the MPU. This is acknowledged by the driver. If no heartbeat message is received, the TCP connection is closed and reestablished.
• The driver only accepts data from the MPU if the unique code provided by the MPU matches the unique code in the local configuration.
• The driver sends General Data Requests (Message type 0x01H) and receives General Data Response Messages (Message type 0xA1H).
  Attention: When adding variables in GUARDIAN OIS COMM Protocol configuration wizard, they may only be added in the COM_RX or COM_TX node. A variable cannot be added to both nodes.
• The driver sends cyclic requests for general data, diagnostic data and SOE data.
• The driver sends an acknowledgment after SOE data has been received.
• Requests are sent to all configured MPUs via both Ethernet connections.
• Write requests are sent to all configured MPUs via all Ethernet connections. If no response is received to this request, a new attempt is sent.