Today is...
Tuesday, June 19, 2018
Welcome to Control.com, the global online
community of automation professionals.
Featured Video...
Featured Video
A demonstration of EtherCAT control of linear motors using the CTC EtherCAT master.
Our Advertisers
Help keep our servers running...
Patronize our advertisers!
Visit our Post Archive
DeviceNet vs ProfiBus
Looking to connect an old industrial robot with 3 CNC machines and conveyor. The robot uses DeviceNet, Should I upgrade to Profibus or not?

Hi,
First of all I want to start with the note that I don't have any background in BUS communication. After I got that off my chest I will ask my question.

A custumer bought an old KUKA robot with DeviceNet communication. He has 3 CNC machines with I/O interface. I need to integrate these machines with the robot, and also to a conveyor that I will supply and some safety peripheral products like safety fence, laser scanners, and emergency stops.

I have 2 options:

1. Use the robot as it is:
Buy 3 Remote I/O to DeviceNet , supply the conveyor with a DeviceNet communication and connect the safety system to the DeviceNet network

2. Add a ProfiBus communication to the robot for 1500USD:
Buy 3 Remote I/O to ProfiBus, supply the conveyor with a ProfiBus communication and connect the safety system to the ProfiBus network.

The distance between the systems is fairly small- all the systems will be in a zone of 15mx15m.

I have no past experience in bus communication... What option should I choose?

By Ikhtiander - on 30 May, 2018 - 2:36 am

Hi Eliko2000,

What I can suggest you is to use Devicenet master (since DN master card usually built to KUKA) communicated KUKA to Devicenet based remote IO module which should be compatible with your safety peripherals. Then your safety peripheral will be controlled by your KUKA using hard wire through device net communication.

First you need to identify what IO channel available at your safety peripheral side (digit input or digital output or analog input or analog output). Then you should be able to get each IO channel spesification:

DI: dry or wet, sinking our sourcing, what voltage (24, 120, 220, or ..) , etc

DO: dry or wet, sinking our sourcing, what voltage (24, 120, 220, or ..) , load capacity (A) etc

AI: mA or V , 2/3/4 wire, active/passive, etc

AO: mA or V , 2/3/4 wire, active/passive, load capacity (mA), etc

After you decided what IO module type to be used and how many, you will need to connect these IO modules to Devicenet network as a Devicenet slave to Kuka devicenet master and start your configuration using KUka software tools.

Hope this helps,
Ikhtiander