Member Login
Search
Jump to a Date
Sponsored Communities
Cool stuff
Neat Stuff

Visit our shop for nerds in control lifestyle products.
Thermal Overload
The threads that wouldn't die...
- PC reliability?
- Windows, real time
- PID loops
- PCs vs. PLCs
- Replacing people
- MS 'monopoly'?
- Software quality
- Where do we go from here?
- Why pay?
- PC reliability?
- Windows, real time
- PID loops
- PCs vs. PLCs
- Replacing people
- MS 'monopoly'?
- Software quality
- Where do we go from here?
- Why pay?
Fortune
One nice thing about egotists: they don't talk about other people.
RSS Feed
www.control.com/rss/
To get a personalized feed, become a member at no cost.
Dear all,
I am looking for software to calculate Foundation Fieldbus H1 microcycle. Any tips will be appreciated.
Thanks in advance,
Ricardo Almarza
I am looking for software to calculate Foundation Fieldbus H1 microcycle. Any tips will be appreciated.
Thanks in advance,
Ricardo Almarza
There is no generic software available to estimate schedule macrocycle. The exact macrocycle schedule is determined by the control system engineering software.
The macrocycle schedule consists of a real-time (RT) slots and a non-real-time "background" slot (NRT). The amount of time allocated is unique to each control system. Some systems have "optimization" algorithms to ensure control response and display update are ideal.
For engineering purposes it may be a good idea to experiment with the system you have to see what macrocycle you get with different loading. Based on this you get rules of thumb such as: * For 250 ms: 1 loop (valves) + 9 transmitters * For 500 ms: 2 loops (valves) + 8 transmitters * For 1000 ms: 3 loops (valves) + 7 transmitters
You can do this offline (without devices connected) because all the timing data required by the engineering tool is in the EDDL and CFF files.
Depending on if you do Control-in-the-Field (CIF) or Control-in-the-Controller (CIC) you get different macrocycle. Some systems read monitoring transmitters RT others use NRT so this makes a difference. Function block execution time also plays a large role. Use fast devices for short control period.
Cheers,
Jonas
The macrocycle schedule consists of a real-time (RT) slots and a non-real-time "background" slot (NRT). The amount of time allocated is unique to each control system. Some systems have "optimization" algorithms to ensure control response and display update are ideal.
For engineering purposes it may be a good idea to experiment with the system you have to see what macrocycle you get with different loading. Based on this you get rules of thumb such as: * For 250 ms: 1 loop (valves) + 9 transmitters * For 500 ms: 2 loops (valves) + 8 transmitters * For 1000 ms: 3 loops (valves) + 7 transmitters
You can do this offline (without devices connected) because all the timing data required by the engineering tool is in the EDDL and CFF files.
Depending on if you do Control-in-the-Field (CIF) or Control-in-the-Controller (CIC) you get different macrocycle. Some systems read monitoring transmitters RT others use NRT so this makes a difference. Function block execution time also plays a large role. Use fast devices for short control period.
Cheers,
Jonas
From Control Engineering magazine...
Related articles from Control
Engineering magazine- Liquid level sensor: Non-mechanical optical technology extends application possibilities
- Wireless manager for instrumentation and control devices
- Level sensor: Magnetostrictive device extends mounting options
- New podcast: One road to wireless instrumentation
- Tutorial: Instrumentation / DCS integration languages, part 1, EDDL
- Rockwell Automation introduces virtual design and production software utility
- FactoryTalk industry-specific applications launched
- Upgraded communication modules make PLC to PLC communications easier
- Torque: Hall-effect sensor, reaction torque sensor, torque data acquisition
Above articles copyright 2008 Reed Business Information.
Subject to its Terms of Use.
Your use of this site is subject to the terms and conditions set forth under Legal Notices and the Privacy Policy. Please read those terms and conditions carefully. Subject to the rights expressly reserved to others under Legal Notices, the content of this site and the compilation thereof is © 1999-2008 Control Technology Corporation. All rights reserved.
Our Advertisers
Help keep our servers running...
Patronize our advertisers!
Patronize our advertisers!




