ANYBUS Profibus to Devicenet for IRC5

ChrisB

Hi

 

I need to setup a system where a S7-315 PLC needs to communicate to a IRC5. I have purchaced a ANYBUS Profibus Slave / Devicenet Master to convert the profibus on the PLC to Devicenet on the robot but can't get it to work and I dont know where the problem is.

 

If I run diagnostics on the ANYBUS device, it tells me that "Device not intialized".

 

Is there anybody that can give me advice.

 

Thanks

 

Klaus

have you set up the unit type correct?

I have used same product with out problems.

Here is my setting in EIO.cfg

 

****************************************************'

 #
EIO_UNIT_TYPE:-Name "DN_AnybusProfibusDevicenet" -BusType "DNET" -DN_VendorId 90
-DN_ProductCode 12 -DN_DeviceType 12 -DN_ExplicitMsgEnabled
-DN_C1Type "COS" -DN_C1Interval 50 -DN_C1OutputSize -1 -DN_C1InputSize -1#
EIO_UNIT: -Name "BOARD11" -UnitType "DN_AnybusProfibusDevicenet" -Bus "DeviceNet1"
-DN_Address 11

ChrisB

I managed to get it working, was a problem on the PLC side.

 

I am now trying to get comms between the ANYBUS gateway and two robots but I'm not sure if you can have two masters on the same bus because my robots has to be a slave and a master a the same time. What do I do with the V+ and V- lines, do I connect all of them together.

 

Thanks

Klaus

you can only have one master. i think you can get a devicenet slave to your robot

osku

Hi

Robots can act as master/slave at the same time. If two (or more) robots are connected to same bus, you just have to make sure you change the address of the masters so that two masters are not using the same address.

If your Anybus device is Profibus slave - DN master, I think you should define your robots as slaves. Then it might be possible for Anybus master to connect to both slaves (robots). I'm not familiar with the Anybus device, but at least their brochure says it should be possible  

The configuration Klaus sent is correct, but with that configuration robot acts as a master for the Anybus device. If you want to run your robot as a slave, you should change the unit type parameter to DN_INTERNAL_SLAVE, like this:

#
EIO_UNIT:

-Name "BOARD11" -UnitType "DN_INTERNAL_SLAVE" -Bus "DeviceNet1"

IRC5 uses the same address for the master and the slave, so if your robots DN master is defined to use address 2, the slave will also use address 2. Therefore you should change the address of the second robot for example to 3. It can be changed under I/O parameters - Bus - DeviceNet1 - DeviceNet Master Address.

Please tell how it works as I'm also a bit interested in this Anybus converter

And for the voltages... You should have all V+ connected together and all V- together, but make sure you feed the voltage only from one place. As default the DN voltage is connected to one of the IO-unit connectors inside the IRC5 cabinet door (comes from XT31 connector), so if you have several robots in the same physical bus, you can detach voltage feed from other robots and leave only one connected.

Good luck!

 

-Osku

Fb-CIA

Hi,

 I?_Tm working on a project with the same configuration you are talking about.

• 2 IRC5
• 1 Anybus DeviceNet Scanner/Master
• 1 DeviceNet IO nodes (from Wago) for each robot

I?_Tve been making some test and the response is:

1. The two robot mast have different DeviceNet address (in my case a set robot 1 with address 2 (default) and robot 2 with address 3)
2. Both robot are master of respective DeviceNet IO nodes (normal configuration that you use when you have just one robot)
3. Both robots are slave of the Anybus (address 10).

• Create a new UnitType copying the DN_INTERNAL_SLAVE and setting the right input/output byte size. For instance:
     -Name "AnyBusIS" -BusType "DNET" -VendorName "HMS"
     -ProductName "Internal DeviceNet Slave" -InternalSlave
     -DN_C1OutputSize 10 -DN_C1InputSize 10
• Crete a new unit with the type you have just created.
     -Name "AnyBusIO" -UnitType "AnyBusIS" -Bus "DeviceNet1"
     -UnitLabel "anybus_io" -RegainCommunicationReset  -DN_Address 10
  This unit will be DeviceNet slave with the address you can read in the in the EIO.cfg where the  BUS are defined.
  In the following case address is 3:
     -Name "DeviceNet1" -BusType "DNET" -ConnectorID "PCI1"
     -ConnectorLabel "First DeviceNet" -DN_MasterAddress 3
• Create the signal you need on the unit just created

This configuration is working fine.

NOTE: Since a controller can?_Tt manage two units configured as DN_INTERNAL_SLAVE, it is NOT possible to connect directly the two robot.

Best regards

Fabio

www.ciaautomazione.it

Henrik Berlin

Moved to RobotWare forum.