AutomationDirect DirectNET

See purchasing information for more details
Download Free Demo

Product Overview

The AutomationDirect DirectNET device driver works in conjunction with KEPServerEX to provide data exchange between OPC clients and DirectNET protocol-compliant PLCs. KEPServerEX automatically optimizes your data acquisition based on client demand. Data integrity is ensured with our extensive error handling.



  • Supports Ethernet Encapsulation
  • All data types supported
  • Modem Support
    • Automatic Dial Configuration
    • Multiple Phone Number Management


  • Koyo DirectNet Hex Mode Protocol

Supported Devices

  • DL-05
  • DL-06
  • DL-230
  • DL-240
  • DL-250
  • DL-260
  • DL-330
  • DL-340
  • DL-350
  • DL-430
  • DL-440
  • DL-450

Available Languages

  • English

Application Support

  • DDE Format CF_Text and AdvancedDDE
  • NIO Interface for iFIX
  • OPC .NET Service (OPC .NET) Version 1.00
  • OPC Alarms and Events (OPC AE) Version 1.10
  • OPC Data Access (OPC DA) Versions 1.0a, 2.0, 2.05a, and 3.0
  • OPC Unified Architecture (OPC UA) Clients
  • SuiteLink and FastDDE for Wonderware

Release Notes



  • Fixed an issue that prevented all communications with devices.



  • Fixed an issue that prevented the driver from communicating with devices.



  • Corrected an issue where the driver would produce a syntax error during tag validation if the data type was not supported. Some clients add items with a set data type regardless of the address. The driver now responds with bad type, allowing the driver library to validate again with the default type.
  • Fixed an issue where Data Words Timers (V0-V377) and Counters (V1000-V1177) default to the BCD data type even if the address was a bit within data type; bit within BCD is not supported. For V addresses with bit-access syntax, the driver now defaults to the Short data type for the bit range 0 to 15 and to the Long data type for bit range 16 to 31.


  • Enhanced error handling when receiving unexpected responses, and special detection of a K-Sequence response to a DirectNet inquiry. On receiving a K-Sequence response to a DirectNet inquiry, an error message will be logged, all tags will be failed, and the driver will continue to silently retry for good communications.