Emerson Exchange 365

DeviceNet gateways in the DeltaV system

Can anyone share their experience in configuring DeviceNet gateways in DeltaV? 

john_doe030488

• 20 Jun 2016 3:38 PM
• Cancel

5 Replies

• Fairchild.1969

  

  • 20 Jun 2016 4:00 PM

  Hi
  
  What do you mean by Device net gateway? Never heard of that.
  Do you mean Device net Cards?
  Or do you mean third parts cards from IP to Device net like Anybus?
  
  I came from a plant that they had device net cards controlling different things from IO to motor controls from AB and Toshiba.

  • Cancel
• john_doe030488

  

  • 20 Jun 2016 4:18 PM

  In reply to Fairchild.1969:

  Such as the Turck BL-20:
  old.turck.us/.../

  • Cancel
• Fairchild.1969

  

  • 20 Jun 2016 5:17 PM

  In reply to john_doe030488:

  We didn't have Turck IO however we had Wago IO, AB drives, Tosh drives, MCC starters or Norgren for block valves or weigh scales, auto feeder, and others.
  
  To be honest with out playing with the unit or reading the manual, I can't help you however I can give you some pointers.
  
  1. Do you have the EDS from the manufacture?
  a. The bytes size will probably changed base off card modules. AI, AO, DO, and DI or maybe read different
  2. Do you have test device net segment that you can play with the Turck? If not make one.
  3. Do you have a manual of the turck device?
  a. This will be needed to set the address, baud rate, and anything else by dip switches
  
  Key to device net segments like any communication protocol is the installation of the physical segment.
  The device net card address that can be used is 1 through 62. Address 0 is for the device card itself and 63 for all other. Never produce a duplicates address form 1 through 62.
  The higher the baud rate the shorter distance and not forgiven. Recommend 125 k instead 250 or 500.
  The other issue that you may come across is speed for the IO from my experience.
  
  M or S Series controller can have device net cards however I don't remember what version it started.
  
  Also some devices will flips bits so talk to your local rep for Turck and in remember right the main company out of Minnesota.
  
  Sorry I can't help out

  • Cancel
• Tinh Phan

  

  • 20 Jun 2016 5:36 PM

  In reply to Fairchild.1969:

  Fairchild capture alot info. I just want to add a few comments.
  1) If the Turck I/O is software addressable, use DeltaV Diagnostic to change the device address. The default address of that new device should be at 63. Right click the device address and change it to the next available address. I do believe most DeviceNet devices these days have autobaud detection.
  2) I recommend that you configure one device at a time on the segment. One thing about DeviceNet, it will kick the other device offline if they have the same address.
  3) Make sure you have the right EDS file. Make sure the major revision is the same of the device.
  4) Read DeltaV book online, there are alot of useful info in there.
  
  Best Regards

  • Cancel
• Fairchild.1969

  

  • 20 Jun 2016 7:53 PM

  In reply to Tinh Phan:

  Tinh
  
  Hit the nail on the head about adding one device at a time. Some times devices needs to be power down and remove from the network before the address is accepted by the device.
  When designing your network there are several things that you have to worry about in my opinion and they are listed below:
  1. Number of bytes/words for each devices on device net segment the device net card is limited.
  2. Power consumption of the 24VDC

  • Cancel