|FORMAT:||PDF EPUB MOBI TXT|
ERLAUTERUNG:Tia openness handbuch
In my previous postwe looked at how Openness formats the XML files that it uses to create objects in TIA Portal. After reviewing some examples, we concluded that creating code in XML can be very complicated and that it is best to use existing blocks to generate XML using Openness.
However, another way to look at it is that by writing your desired code once, you can use Openness to automatically generate the code as much as needed. By creating XML templates, your Openness application can be used to quickly generate new code from an existing codebase. When a customer wants to order a conveyor system, they choose from the dozens of available modules and arrange them in the configuration that suits their needs.
For large systems, this can become very tedious and time-consuming. However, you can take your modules, export them to XML, and with a little tweaking, allow Openness to automatically insert the relevant data and create the code for you. The first step of automating your code generation is to create your template files. Each module has the same block interface.
As long as they are part of the final TIA Portal project, we just need a template for creating the block calls and assigning the tags. This XML needs to be broken into 2 parts: the XML for the tag table, where we will add tags, and the XML for a tag, which we will fill in with the relevant data. To create these templates, delete the data that we will replicate, and add a placeholder that your application will use to perform the replacement.
How you get this data is up to you. An easy solution is to read in a user-created Excel table, such as the following. The application would create the input and output tags for each module and could be set up to give specific tag names depending on the section and module.
A similar process could be done for the global data block. The format is similar to that of the tag table. The resulting templates would look something like the code below. Creating the instance data block template is very simple since each data block can be in a separate XML file. All that needs to be filled in is the function block name, the data block name, and the datablock number. This assumes that each module has the same block interface.
If any module was different, it would need its own instance data block template. Finally, we can create our template for the block calls. We will need 2 templates again; one for the network, and one for the constant that will be linked to the iInModuleID parameter. The block calls will require filling in all the input and output parameters, as well as the function block and instance data block. Once all the code elements have been generated from templates, they can be imported into the project.
If all goes well, your project is now ready to run the system! While setting up these templates is a difficult and time-consuming process, it can have a lot of benefits in the long run. Once the templates are created, any future projects can be created with a few lines in Excel and the click of a button. It also makes code updates easy. Any changes to a template will be reflected in all projects that are then generated from the template. By letting Openness handle the low-level, repetitive details of your code, you can quickly layout a project architecture that makes use of clean, reusable code.
Learn more about our PLC Programming and TIA Development Services. Contact us for more information. Name required Name Is Required. Email required Email Is Required Invalid Email Address. Comment Is Required. Notify me of followup comments via e-mail. Blog Categories. What is a Template For? Creating a Template The first step of automating your code generation is to create your template files.
Here are my templates for the tag table and tags. Comments There are currently no comments, be the first to post one. Post a comment Name required Name Is Required Email required Email Is Required Invalid Email Address Comment Is Required Enter the code shown above:. Related Services HMI and SCADA Programming Iconics Programming Ignition Designer Programming Rockwell FactoryTalk Siemens DNP3 Driver. Related Blog Posts.
Using TIA Portal and the Openness API to reduce engineering cost and time while increasing quality. As an engineer, I love solving new and interesting problems. As a business owner, I love increasing efficiency and quality. Increased efficiency helps to reduce project costs and increased quality helps to keep my clients happy. These two things combined help my business to grow.
By automating the routine parts of your engineering processes, you can create a win-win-win situation:. All of these ideas can be used to save your company time and money while improving the quality of your machines. Companies around the world are already using Openness to increase their competitiveness.
Openness provides a digital link between EPlan schematics, the TIA Selection Tool, and TIA Portal. During the planning stage of a project, the EPlan schematics are drawn up. These schematics contain the electrical detail for a project including:. This exchange of data is done automatically using the Openness interface at the click of a button.
Not only does this save time, but it also reduces copy-paste mistakes and increases the quality of a project. Any changes made during the commissioning stage of a project can be exported from TIA Portal and imported directly into EPlan to ensure that the as-built data is as accurate as possible.
With one push of a button, you can create the hardware configuration and IO tag table in TIA Portal from an external data source. At companies like Beuhler, the machines are composed of standard modules. Each standard module is controlled by a standard software block which is part of a library.
The decomposition of the machine is fed into a code generator application. The code generator can, based on rules, create calls to the software block and parameterize the interface automatically. Using Openness, the generated code, in XML format, can be imported and compiled in TIA Portal. Since the code generator and the software blocks are already tested, the control program contains no errors.
Of course, every project has some special requirements that have to be programmed manually. The control program is only half of the story. Most machines are equipped with an HMI to control and visualize the process.
SiVArc uses the control program, a library of visualization objects, and a set of custom rules to automatically create the visualization for a machine. SiVArc eliminates the need to manually create the visualization objects and link them to tags in the controller, which is time-consuming and error-prone. Since SiVArc generates the visualization based on your library of HMI objects and custom rules, it also helps to ensure that all of your visualization applications follow company standards and are structured in the same way.
By automating these three routine tasks, you can save time and money while increasing the quality of your projects. You can also eliminate copy-paste errors that create delays during commissioning. Are you interested in improving the execution of your automation projects? Contact me today to discuss how you can leverage automation and standardization to reduce the cost and time of projects while increasing the quality of the result.
How Reducing Engineering and Commissioning Costs Can Dramatically Impact Your Profitability. Thoughts on the value of a well-structured engineering team for engineering managers. Get informative, insightful content delivered to your inbox every week.
Home Knowledge Base Services. Book a Consultation. Import the Project Planning Data. Latest articles. More Articles. Learn Something New Every Week Get informative, insightful content delivered to your inbox every week. Thank you for subscribing to our newsletter!