B
As the North American Director of PLCopen I would like to receive as many thoughts as possible about what ideal PLC controller software would be. I plan to use this information to propose new PLCopen standards to improve IEC 61131.
I am asking for the thoughts, complaints, and ideas from control engineers to improve the IEC 6131 standard.
Standards always require input and ideas from users to improve them and have them broadly adopted. They also take time. Think about how long it took to get fieldbus standards where device from multiple vendors actually worked together on the same standard open network! The PLCopen organization is dedicated to improving the standard and users' are in the best position to recommend improvements.
The best example of this in the standardization of packaging controls using IEC 61131 and the PackSoft standards to standardize improve and simplify controls. PLCopen now has a standard set of function blocks that support this.
More user input is required to insure the standard continues to evolve and invite anyone to provide input. I will be compiling a report for the organization and anyone contributing will be provided a copy of the report. You can email or call me.
Bill Lydon
Director, PLCopen North America
A non-profit organization.
414-427-5853
[email protected]
PLCopen Current Major Activities
Links provided for more information.
* Safety PLC Function Blocks
Textual introduction: http://plcopen.org/tc5.htm
Overview: http://plcopen.org/TC5/tc5_safety_overview.htm
Positioning against other standards: http://plcopen.org/TC5/tc5_safety_positioning.htm
The specification itself (.pdf): http://plcopen.org/forms/safety_dl_info.htm
Presentation: http://plcopen.org/TC5/plc_open_safety_pres_final.zip
BGIA improvement: http://plcopen.org/TC5/tc5_safety_v10_approved.htm
First PLCopen safety certification: http://plcopen.org/TC5/tc5_safety_certification.htm
Suppliers of Safety Certified Products: http://plcopen.org/TC5/safety_certification/compliance_suppliers_safety.htm
* Motion
There has been a great deal of work in this area which is continuing. http://plcopen.org/TC2/Motion/tc2_motion_overview.htm
* Benchmarking
This is an important activity so that users can compare products from different vendors. http://plcopen.org/TC3/benchmarking.htm
XML
The PLCopen TC-6, XML standard is important because it is a way for users to easily share applications between multiple control vendors and work directly with simulation and CAD systems. The PLCopen XML standard enables the coupling of control applications to higher level tools such as simulation of the factory floor, and CAD tools. Applications interchange using XML between control vendor editors is finally a way to insure portability of applications between various control vendors products. XML is the software industry interchange standard for all of computing therefore it is the natural choice.
http://plcopen.org/tc6.htm
I am asking for the thoughts, complaints, and ideas from control engineers to improve the IEC 6131 standard.
Standards always require input and ideas from users to improve them and have them broadly adopted. They also take time. Think about how long it took to get fieldbus standards where device from multiple vendors actually worked together on the same standard open network! The PLCopen organization is dedicated to improving the standard and users' are in the best position to recommend improvements.
The best example of this in the standardization of packaging controls using IEC 61131 and the PackSoft standards to standardize improve and simplify controls. PLCopen now has a standard set of function blocks that support this.
More user input is required to insure the standard continues to evolve and invite anyone to provide input. I will be compiling a report for the organization and anyone contributing will be provided a copy of the report. You can email or call me.
Bill Lydon
Director, PLCopen North America
A non-profit organization.
414-427-5853
[email protected]
PLCopen Current Major Activities
Links provided for more information.
* Safety PLC Function Blocks
Textual introduction: http://plcopen.org/tc5.htm
Overview: http://plcopen.org/TC5/tc5_safety_overview.htm
Positioning against other standards: http://plcopen.org/TC5/tc5_safety_positioning.htm
The specification itself (.pdf): http://plcopen.org/forms/safety_dl_info.htm
Presentation: http://plcopen.org/TC5/plc_open_safety_pres_final.zip
BGIA improvement: http://plcopen.org/TC5/tc5_safety_v10_approved.htm
First PLCopen safety certification: http://plcopen.org/TC5/tc5_safety_certification.htm
Suppliers of Safety Certified Products: http://plcopen.org/TC5/safety_certification/compliance_suppliers_safety.htm
* Motion
There has been a great deal of work in this area which is continuing. http://plcopen.org/TC2/Motion/tc2_motion_overview.htm
* Benchmarking
This is an important activity so that users can compare products from different vendors. http://plcopen.org/TC3/benchmarking.htm
XML
The PLCopen TC-6, XML standard is important because it is a way for users to easily share applications between multiple control vendors and work directly with simulation and CAD systems. The PLCopen XML standard enables the coupling of control applications to higher level tools such as simulation of the factory floor, and CAD tools. Applications interchange using XML between control vendor editors is finally a way to insure portability of applications between various control vendors products. XML is the software industry interchange standard for all of computing therefore it is the natural choice.
http://plcopen.org/tc6.htm