Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

Edge HMI

Add a Koyo DirectLOGIC PLC as a tag integration source

Add a Koyo DirectLOGIC PLC as a tag integration source

  • Last UpdatedOct 29, 2026
  • 3 minute read

Use the Tag Integration feature to add a Koyo DirectLOGIC PLC (supplied by AutomationDirect) as a source for your project.

This tag integration is based on our KOYO driver, which communicates with Koyo DirectLOGIC PLCs over both serial and Ethernet communication.

Before you begin, you should do the following:

  • Review the manufacturer's documentation for your Koyo DirectLOGIC PLC;

  • Read our documentation for the KOYO driver (on the ribbon, go to the Help tab, and then in the Documentation group, click Communication Drivers);

  • Note the Module Name, Module ID and/or IP address of the device; and

  • Use AutomationDirect's DirectSOFT software to export the device's program elements as a .csv file. For more information, see Export .csv file from a Koyo DirectLOGIC PLC program.

The device does not need to be running when you add it as a tag integration source for your project, because live browsing of tags is not supported for this type of tag integration. Your project will use the information contained in the .xml file to reference the device's elements.

The device should be running and accessible during project run time, however, so that your project can communicate with it.

To add a Koyo DirectLOGIC PLC as a tag integration source:

  1. On the ribbon, go to the Project tab, and then in the Settings group, click Communication.

    The Project Settings dialog box is displayed, with the Communication tab selected.

    Project Settings: Communication tab

  2. Under Tag Integration, click Add.

    The Tag Integration Source dialog box is displayed.

    Tag Integration Source dialog

  3. In the Type list, select Integrated (if it is not already selected).

  4. In the Provider list, select AutomationDirect Koyo.

  5. In the Name box, type an appropriate name for the source.

    The value that you type here will be added as a prefix to the names of the tags on the device. This helps you to distinguish between tags from different sources. The default is DEV, which is short for "device".

  6. Click Add.

    The Koyo Tag Integration dialog box is displayed.

    Koyo Tag Integration dialog

  7. In the Communication Mode list, select the type of communication used by the device.

    Option

    Description

    Serial

    Direct serial communication.

    EthernetName

    Ethernet communication by Module Name, when a broadcast router is used.

    EthernetIP

    Ethernet communication by IP address.

    EthernetID

    Ethernet communication by Module ID, when a broadcast router is used.

  8. In the Device box, type the Module Name, Module ID or IP address of the device.

    The format of this value depends on what you selected for the communication mode.

  9. If you selected EthernetIP for the communication mode, you can also specify a custom port in the Port Number box.

    If you do not specify a custom port, the default port is 28784.

  10. Select the .csv file that you exported from the device's program.

    1. To the right of the CSV File box, click Browse.

      A standard Open dialog box is displayed.

    2. Use the file browser to locate and select the .csv file.

      In most cases, the file should be located in the Config sub-folder of your project folder (for example, <project name>\Config\program.csv).

    3. Click Open.

    The selected file is displayed in the CSV File box.

  11. Click OK to finish the configuration and add the source to your project.

If the source is added successfully, the device's tags will be immediately available in the Object Finder. For more information, see Use the Object Finder to select integrated tags.

Live browsing is not supported for this type of tag integration, which means that if the device's program is updated and its elements are changed, those changes will not be reflected in the tag integration. To see the changes, you will need to export the elements again as a new .csv file. The new file should be saved in the same location as the old one; if it is not, you will also need to update the CSV File setting in the tag integration.