Fieldbus control loop limitation

  • Thread starter Lorenzo Cecchini
  • Start date
L

Thread Starter

Lorenzo Cecchini

Hi all,

Please, I'm getting confused with the limitation of ONE control loop for segment.

What does it mean?

The limitation is for the scan time or the power supply?

Could you give me some example?
 
This is NOT a constraint from the Fieldbus protocol. It is a practical constraint to make sure that traffic on the segment does not interfere with control loop timing. If you know that the control loop(s) are slow, then you can
have more loops per segment. It's just a matter of data throughput on the 31.25 kbps H1 link.

Dick Caro
===========================================
Richard H. Caro, Certified Automation Professional, CEO, CMC Associates,
2 Beth Circle, Acton, MA 01720
Tel: +1.978.635.9449 Mobile: +.978.764.4728
Fax: +1.978.246.1270
E-mail: [email protected]
Web: http://www.CMC.us
Buy my books:
http://www.isa.org/books
Automation Network Selection
Wireless Networks for Industrial Automation
http://www.spitzerandboyes.com/Product/fbus.htm
The Consumer's Guide to Fieldbus Network Equipment for Process Control
Buy this book and save 50% or more on your next control system!!!
===========================================
 
J
It is not limited to one loop per bus. You can have many loops per bus, even for fast loops.

UOP require 250/300 ms for many loops and we have met this requirement even with two loops per bus plus monitoring points.

A key to putting more loops per bus is using devices that execute blocks fast. Check on block execution time before purchasing devices.

Cheers,
Jonas
 
Top