Delta Industrial Automation

Tips & Tricks


Fieldbus Tips&Tricks

CANopen, Modbus RS485/RS232, Modbus TCP/IP, Ethernet IP, Profibus, Bacnet, Ethercat

New product Announcement – DVPPF02-SL

Do you need cost effective Profibus distributed I/O??

DVPPF02-SL is the new PROFIBUS DP slave communication module.
Only avaliable for left side high speed module, it supports the loop data transmission between PROFIBUS DP master and several slaves.

The DVPPF02-SL have auto-detection baud rate feature, and a maximum data transmission length of 100 words, input and 100 words output.

To take a look on the product specifications, don´t hesitate to download the product announcement
DVPPF02-SL Announcement

Before using DVPPF02-SL, download the GSD file and load in to the PROFIBUS DP main station.

DVPPF02-SL Manual

In a few days it will be available on the web site, but meanwhile you can download it here.
Web Link to Delta GSD files

IFD9506 (part 3 of 3)

We arrive to the end of the IFD9506 monographic with the definitive application (and some final desert).
In this case we use the IFD9506 to add any Delta product to a Ethernet network.
In fact with the new firmware V1.07 is possible to add until 100 devices below the Ethernet gateway!!

And as a final climax, one last example of how to use IFD9506 as a gateway between one Ethernet HMI and some RS485 Delta periphericals (EX2, SV and DTB).

Have fun!

How to use IFD9506
Technical Announcement_DCISoft_V1_07

And put ethernet in our life ;)

IFD9506 (part 1 of 3)

Let’s play with Ethernet!

Industrial Ethernet has become the last 10 years as the replacement for the serial communication.  Not only because the speed, but for the simple compatibility with our main tools, the computers…

Each automation brand have their own protocol based on Ethernet (Profinet, Ethernet/IP, Ethernet Powerlink, etc…).
In Delta, we have been playing with Modbus from the beginning, so in the moment that we decide to enter to ethernet, the natural choice was Modbus TCP/IP.

But what happen with all the devices already in the factories working with Modbus RS232 or RS485 ?

To solve this need, we develop IFD9506.
This device is used to convert from Ethernet Modbus TCP/IP to serial communication Modbus.
And the following weeks we’ll share with you all several typical applications and functionalities of this device.

To start, we are going to use the simple communication HMI-PLC-DTB and we’re going to add two IFD9506 to achieve to communicate both three devices trough Ethernet as the picture shows.

To achieved, use the attached application tutorial.
HMI + IFD9506 + PLC.pdf
And take a look at the last page and our first approach to web server!

EDS Builder

Everytime you need to insert your devices inside some Devicenet or CanOpen network, the master would need some driver.
Those drivers are called EDS files.
That EDS file is different for every drive, and it may be configured depending of the data that we want to send to the master.

Delta have many Inverter and Servodrives models able to communicate trough CANOpen or Devicenet, because of that I would like to introduce you to a software tool to create that specific EDS files for each drive and application.

EDSBuilder V1.01, just released a month ago, we’ll be able to create the EDS file compatible with any brand CANOpen or Devicenet network.
Of course, Delta already have CANOpen master to controll them, but this is another history.

Software EDS Builder V1.01

To use this software, we will need the device to communicate, and some IFD6500 (USB-RS485 converter) to communicate with the device.

And once you have it, just follow the instruction of the following tutorial  “How to create EDS via EDSBuilder”

name: den-eindhoven
Password: BuPd2175


PLC-Link (PLC to PLC)

I have been a long time that I would like to post this post.

PLC-Link is a Delta protocol to share easily memory area between 2 PLC’s.
Basically, the big advantage of PLC-Link is to work with Delta PLC’s as Remote I/O units.

Furthermore, you can use Delta PLC as Remote I/O or any other Delta device (Servodrive, Inverter, etc..) because the protocol used to share the info is Modbus.
Today we’ll focus on how to communicate one PLC master with 2 PLC slaves.

Network Structure:

The communication will be Modbus RS485, so the wiring is so simple, two twisted pairs from connector to connector.

We decide to use 9600, 7, E, 1, ASCII, but you can use higher baudrate. In fact the new S2 PLC series (SS2, SX2, SA2, ES2 and EX2) can reach 921Kbps!!

Memory Mapping:
The plan is to share 6 registers from the slave 1 and put it inside the memory of the master.
And on the other way around too, put 6 registers of the master on the memory of the Slave one.

See below table

As you could see on the Slave software we transform the first three shared words to Slave Inputs and Outputs.
This is the proper way to read remotely the I/O of the slave into the master.


Program Master
Program Slave 1
Program Slave 2

Alternate mirror all together
name: den-eindhoven
Password: BuPd2175

Remember to enable PLC-link on network 5 to start to share.
And if some trouble occurs just try to reset the communication with the RESET_Com Symbol.


RTU-EN01 application

Inside the Delta Fieldbus Solutions range, we provide several different field-bus (Modbus, Ethernet, CanOpen, Profibus, DeviceNet, etc…) and almost for all of them we have Remote Terminal Units (RTU) to help us to solve us a lot of long distance troubles.

In this case the application is with the Ethernet Modbus TCP/IP Field-bus (RTU-EN01).
This device is designed to setup remote I/O trough Ethernet Modbus TCP/IP, but it has also another capability.
This device could be the node to have a whole modbus network below him. like the picture attached.

So below I’ll try to show you how to access to those slave PLC’s from the SV28 Master like a remote I/O modules. Of course you can connect in spite of PLC’s some inverter, servomotor or temperature controller.

The example consists in receive in the 28SV Master the DI/DO status of the 14SS slaves with ID:4 and 5.

1. We need to map the Master memory with the remote DI/DO of the slaves (for example):
ID:5 : Y0~Y7 map to D200 ( CoiltoD.dvp )
ID:4 : Y0~Y7 map to D300 ( CoiltoD_2.dvp )

2. Open the DCI Soft, and detect the DVPEN01-SL. Go to Data Exchange and set as the picture below

3. The detect the RTU-EN01 and configure the IP address as you configured in the Data Exchange thumb index

4. Finally download the examples attached and in theory you have to see the next
Master D100 map to Y0~Y7
Master D200 map to Y10~Y17
( refer to DtoCoil_2.dvp)

5. By the way, don’t forget to configure the comunication port of the RTU-EN01 with the same protocol as the 14SS Slaves!

Now you only have the problem to decide how big is your network!

Blog at

Up ↑