In this guide, we walk through the essential steps for downloading, configuring, and commissioning a WinCC Unified Comfort Panel using Siemens TIA Portal. You will learn how to set network parameters, configure users and security, enable encrypted transfers, and successfully load your project to the device. As Siemens Solutions Partners, we also provide tips for common commissioning tasks to save time and prevent headaches in the field.

All example screenshots were captured using TIA Portal V20 and an MTP700 Unified Comfort Panel (6AV2 128-3GB06-0AX1), but the same concepts apply across the WinCC Unified Comfort Panel family.

Pre-requisites

Before you begin commissioning, your system must meet certain prerequisites. For instance, your TIA Portal project must be set up with the appropriate hardware, network connections, and screens developed, and your WinCC Unified Comfort Panel must be powered on. Here is how you download your project and commission your WinCC Unified Comfort Panel.

Change IP Address

On the WinCC Unified Comfort Panel, go to Network and Internet, then Network settings. Here, select the port you wish to set the IP address for, then select Specify an IP address. Enter your desired IP address and subnet mask and click the Set IP address button.

Configure Users

To configure users, go to “Security settings” > “Users and roles” in the TIA Portal project tree. From there, create an administrator user, set a password, and assign it all roles. Feel free to learn more about Users and roles, by seeing a previous guide about setting up basic user profiles for WinCC Unified Runtime.

Configure Encrypted Transfer

An encrypted transfer ensures secure download of project files to your WinCC Unified Comfort Panel. On the panel, navigate to Service and commissioning > Transfer. Enable the Enable transfer checkbox and create a password.

In TIA Portal, go to Runtime settings under your HMI. In the General section, enable the Activate encrypted transfer checkbox and enter the same password that you created on your WinCC Unified Comfort Panel.

Download to the Unified Comfort Panel

Finally, it is time to download your developed screens and configured TIA Portal project to the WinCC Unified Comfort Panel. To do so, click on your HMI in the Project tree, then click the Download button in the toolbar. This opens the Extended download to device window.

From here, set the Type of PG/PC Interface to PN/IE, and the PG/PC Interface to your network adapter, and click Start search. If you do not see your device, you can see all compatible devices by selecting the drop-down menu above the table of possible target devices and choosing Show all compatible devices. When you see your HMI appear in the table, select it and click Load.

In the Load preview window, select Full download and click Load. Check to ensure that the option to download all users and authentication settings is selected. If successful, you should then see your TIA Portal screens loaded onto the WinCC Unified Comfort Panel!

Trusting the PLC Communication Certificate

By default, the Only allow secure PG/PC and HMI communication setting in your TIA Portal project for your PLC is enabled. Enabling this means that during the download of your TIA Portal Project to the PLC and HMI, a PLC communication certificate will be automatically generated and transferred to your WinCC Unified Comfort Panel. But this PLC communication certificate needs to be trusted by completing the following steps.

Go to Security>Certificates on the WinCC Unified Comfort Panel. In the Certificate store dropdown menu, select Other Certificates. Here you should see your certificate, and press Trust. Then, restart the HMI runtime software.

Additional Settings to Apply to Your HMI Panel

Beyond core commissioning steps, there are a handful of additional settings that can be helpful for further improving system reliability and maintainability. While they aren’t required for every project, these settings are commonly used to help reduce downtime, manage system access, and recover information and settings in the event of outages or reboots. Consider the settings below as they apply to your unique project requirements. Storage Device Set Up

Storage Device Set Up

When commissioning a WinCC Unified Comfort Panel, it is often recommended to activate the Automatic Backup option. This will ensure that the HMI device’s data is backed up to the storage device. If the WinCC Unified Comfort Panel becomes inoperable, you can simply purchase a replacement and insert it into the new HMI to resume operation.

To do this, slot in a SIMATIC HMI Memory (SD) Card into the X50 SYSTEM slot of the Unified Comfort Panel. Note, the system memory card of the comfort panel must be a SIMATIC HMI Memory Card.

Slotting in the storage device will cause a System memory card plugged dialog window to pop up. Click OK. This takes you to the settings Service and Commissioning/ Automatic Backup screen.

Here, click the Start button, and OK in the Start automatic backup dialog window to activate Automatic Backups. Once preparation is complete, the Status box will display automatic backup active.

Restrict Control Panel Access

To limit access to certain system settings, go to Security and Control panel access on the WinCC Unified Comfort Panel and click the checkbox to Enable password protection for control panel. This option requires a user with proper access to log in to use the WinCC Control panel, reducing the risk of accidental or unauthorized changes.

Automatic Runtime Start

To set a delay time before the automatic start of a project, click the icon with a wrench and a play button. This will open the Runtime Properties page. Locate the Automatic runtime start section and select a time from the “Waiting time(s)” dropdown menu. This is a very helpful setting to allow for some time before the automatic start to access the control panel.

Enable Smart Server Access

Enabling Smart Server Access allows VNC access to the WinCC Unified Comfort Panel.

To enable this setting in TIA Portal, go to Runtime settings, > Remote Access, >  Smart Server. Click the Enable Smart Server checkbox. You must then configure unique passwords for each User1 and User2.

If you wish to allow a user with that password to access the WinCC Unified Comfort Panel, click the Authorize User# for remote access to the panel checkbox. Upon your next download, the Smart Server will be enabled on the WinCC Unified Comfort Panel.

Firmware updates

Depending on the panel and the version of TIA Portal you are using, you may need to update the device firmware prior to commissioning. If this is the case, follow these steps:

1. It can be helpful to connect to the maintenance port on the HMI (PN-X2).
2. Right-click the HMI in the Project Tree while the device is offline. Go to HMI device maintenance and select Update operating system.
3. TIA Portal will now prompt you to connect to the HMI via ethernet. Enter the IP address of the PN-X2 port. A pop-up with a progress bar should appear on the HMI, and a pop-up will appear on TIA Portal stating the firmware is being transferred.

Date and time

Operators can also set a date and time on their panel by clicking the world icon in the sidebar menu. This will open the Language, Region and Formats/Date and time UI, allowing you to set your local date and time.

Synchronizing Time

If the clocks between the HMI and PLC are not synchronized, HMI communication may be limited or blocked. If the HMI still cannot read tags from the PLC after following the steps above, first ensure the correct time zone is selected for the PLC. Then check the clock on the PLC through Online and Diagnostics. Under Functions > Set Time, select Take from PG/PC Interface to synchronize the PLC with your PC.

Conclusion

Commissioning a WinCC Unified Comfort Panel is about more than getting screens to load. Proper network configuration, security settings, and runtime behavior all play a critical role in building a reliable, maintainable HMI system. By taking the time to configure encrypted transfers, user access, certificates, and startup behavior correctly, you set your system up for long-term success in the field.

Whether you are bringing a new HMI online, modernizing an existing system, or troubleshooting communication and security challenges, we can support you at any stage of the project. Partner with DMC to streamline your Siemens automation efforts and commission your systems with confidence.

The post How to Commission a WinCC Unified Comfort Panel appeared first on DMC, Inc..

We’ve picked up some pointers while helping clients migrate their existing WinCC projects. These are our best practices for navigating that transition, with practical tips and tricks to make the process as smooth as possible.

Why Upgrade from Comfort to Unified?

Comfort is Phasing Out: As WinCC Comfort is gradually being retired, moving to WinCC Unified will ensure that your projects remain supported and functional.

Scarcity of Technology and Hardware: Comfort hardware will become increasingly rare, making upgrading worthwhile to maintain project viability and avoid future headaches.

While this blog isn’t a full-blown tutorial on WinCC Unified, it focuses on providing useful tips, tricks, and common pitfalls you might encounter when converting your projects. Our primary focus is on version 18 of Unified, though many of these insights are relevant for earlier versions like V16 and V17, which come with their own set of challenges, and also future versions.

Using the Data2Unified Conversion Tool

The Data2Unified Conversion Tool from Siemens is a great starting point for converting your projects. This tool handles about 50%-90% of the conversion process for you, depending on what elements are present in your project.

How to Use the Tool:

1. Install the Data2Unified Conversion Tool.
2. In Portal, ensure you’ve added a Unified panel to your original Comfort project.
3. Right-click on your Comfort panel in the project, find the Data2Unified tool in the context menu, and select “Start.” The tool will begin processing your project.

4. Once your project loads, you’ll choose what you want to convert. Be sure to select the Unified panel as your target. Update the file name and path if needed, and then click “Save file.” For larger projects, this process might take a while, so it can be a good idea to run it overnight.

Limitations to Keep in Mind:

• Basic Navigation: The tool often produces basic navigation outputs that may need refinement.
• Faceplates: These aren’t converted automatically, so they’ll need manual attention.
• Displays and Lists: Alarm lists, trend displays, graphic displays, and similar elements require manual adjustment.
• VBA Scripts: Review and convert these scripts manually if necessary.
• Artifacts: Be on the lookout for issues like blinking elements or rotated vertical text.

Advantages of WinCC Unified

1. Improved Navigation:

• Screen Windows: WinCC Unified allows you to design screens larger than your display and embed them in smaller windows, which automatically adds scroll bars. This feature helps keep your project organized and user-friendly. In the below example, notice the scroll bar at the bottom of the zone section that lets you slide between different zones.

• Consistent Navigation: Set up a main screen with different windows for the header, content, and navigation. This setup creates a cohesive user experience and makes navigation more intuitive.

2. Simplified Popup Architecture:

• Faceplate Popups: You can use scripting to open faceplates as popups. This reduces the number of screens you need and simplifies your project. However, if you need to handle multilingual text, be aware that the OpenFaceplateInPopup function doesn’t support text arguments in multiple languages.

Tips for Converting Faceplates

When moving faceplates from Comfort to Unified, direct copying won’t work. Here’s a step-by-step approach to make the conversion easier:

1. Copy Visual Elements: Move elements from the faceplate definition to a blank screen.
2. Run the Conversion Tool: Use the tool on this new screen to convert sizes, positions, fonts, and colors (all aesthetic properties).
3. Create a New Faceplate: Group select all objects from the conversion tool, and create a new faceplate.
4. Re-link Dynamics: Manually update dynamizations and tag linking.
5. Event Interface: Configure it as needed.

If your faceplates are complex, this approach can save a lot of time, as the conversion tool will handle all visual properties, allowing programmers to focus on quickly re-linking tags.

Leveraging JavaScript Scripting in Unified

WinCC Unified supports JavaScript, adding a new level of flexibility. You can use it to enhance screens, events, and object properties, making your HMI more powerful and customizable.

1. Nested Faceplates:

• Benefits: Nested faceplates allow for advanced graphics and cleaner architecture.
• Cautions: Avoid overusing nested faceplates and complex scripts to prevent performance issues. Efficiently manage variables and use Global Definitions to keep your code organized and avoid artifacts in the HMI simulator.

Additional Resources

For further reading and detailed guidance, check out these resources:

• SIMATIC WinCC Unified Tips and Tricks for Scripting (JavaScript)
• Data2Unified Tool Documentation
• “Getting Started with WinCC Unified”
• Developing Unified JavaScript with VSCode

Upgrading from WinCC Comfort to Unified might seem like a big task, but with the right approach and tools, you can handle the transition smoothly.

Are you looking to upgrade your existing systems to WinCC Unified? DMC’s team of Automation engineers have extensive experience and can help with conversions and migrations of any size. Contact us today to discuss your project needs.

The post Upgrading from WinCC Comfort to WinCC Unified appeared first on DMC, Inc..

The DMC Drinkbot is a robotic bartender powered by Siemens automation hardware. It was originally created in the DMC Denver office in 2016 using a Siemens S7-1200 PLC interfaced by a 7″ SIMATIC Comfort Panel.

Eight years after creation as Siemens has begun to phase out their COMFORT HMI Panels, DMC wanted to give Drinkbot an HMI upgrade. We received a new MTP700 Unified Comfort Panel that runs TIA Portal V19 WinCC Unified programs to show off the latest and greatest of Siemens HMI technology. This guide will walk through the steps taken to upgrade Drinkbot and the new features developed.

Background and Operational Overview

The DMC Drinkbot uses PROFINET communication for a Siemens G120 VFD drive controlled by an S7-1200 PLC. The user can choose drinks on a SIMATIC key panel or the MTP700 Unified Comfort Panel HMI that this blog focuses on. The user can choose between 44 standard drink recipes made from 8 bottles of alcohol and 6 mixers. There is also a custom drink option where the user can select any ingredient available based on the current configuration of the Drinkbot. 

Without replacing any bottles on the machine, the ability to make alcoholic drinks can be toggled. If the Drinkbot is taken to an event where alcohol is not permitted, the bottles may also be swapped out for flavored syrups and soda water to make “Italian sodas”. The Italian soda switch overrides the selectable recipes limiting the machine to the new available ingredients. The settings screen for these configurations is accessible by selecting the DMC logo in the upper left corner where the user can view alarms and diagnostics and change the machine mode. The motion axis of the Drinkbot can also be manually operated for demonstration and debugging purposes.

For a detailed history of the development of Drinkbot, refer to the following two blogposts.

DMC Engineers Serve up a Siemens S7 Powered DrinkBot

Adding Siemens MindSphere Tracking to the DMC DrinkBot

Data 2 Unified

About half of the work for creating the Unified program was accomplished using the Data2Unified tool by Siemens. This tool does a great job taking an older Comfort program and converting it to Unified, maintaining the basic layout and functionality of most HMI Elements and Controls. For some deprecated elements, the tool will even generate custom VBA scripting to maintain original functionality.

There are current limitations to this tool as the conversion will notably not create alarm lists, faceplates, and navigation elements. Additionally, due to WinCC Unified’s aspect flexibility, it is typically worth touching up the screens’ layout and aesthetics. The custom scripting that is auto-generated may also need to be redone as more efficient element functions can be created manually without scripts. Typically, the automatically generated scripts will function as intended, but the script will be written in unconventional and overcomplicated language. Double-checking these scripts and replacing them with standard functions where applicable is good practice.

After running the conversion, most of the Drinkbot settings screens were recreated to match the previous comfort program to maximize the ease of configuring the system during events. The cleaning sequence screens that use basic elements were converted seamlessly into Unified. Settings screens, like the alarms and diagnostics, were easily replaced with drop-in standard Siemens resources.

The bulk of the work left out by the tool was completed when modernizing the faceplates for drink selection and the recipe management system talked about in the following section.  

Recipe Conversion

In the Comfort program, there was a built-in recipe management feature that the developer could create their own data type and store recipes locally on the HMI panel to be written onto the PLC when selected. In the Drinkbot Comfort HMI the recipe list included 44 drinks detailing their ingredients and quantities.

This recipe feature was a convenient way to store information and access data to be written into the instructions of the PLC. In WinCC Unified, this feature was removed, so this storage was recreated using a user-defined type and a data block on the PLC.

The dbHMI data block stores all of the original recipe data using integers to signify ingredient quantities and a single string for the name of the recipe. Memory on the PLC is conserved by these simple UDTs, provided that the bottle setup in the Drinkbot is always the same. For simplicity, to set up the Drinkbot, the user consults a printout that lists all of the ingredient bottle positions. The string and 18 integers are then fed to the HMI through a multiplexed array 11 recipes at a time.

The 11 recipes are selected to be read based on the page of the HMI drink list the user is currently reading. The last display recipe on the page is number 12 that is left intentionally blank. A custom drink faceplate is opened when the custom button is pressed that displays all possible ingredients in the Drinkbot. The user can select how many of each ingredient to make their drink based on if alcohol is toggled on or the Drinkbot is displaying Italian Sodas. Once completed the ‘Make Drink’ button populates the display recipe 12 and once the Drinkbot completes the cycle the recipe is cleared.

To access standard drinks that access one of the stored recipes, 11 faceplate buttons are displayed on each page. These simple faceplates display the drink name based on page number and intake the recipe parameters once selected. They serve as an in between display button to open a nested faceplate that will display the selected drink in detail. The nested standard drink faceplate used in reading and writing recipe data is talked about in the next section.

Faceplates and Scripting

In the Comfort HMI, having a local way to manage the recipes within the HMI made development simpler as a single popup recipe screen could read the ingredients for each drink and display all possible options at once in a matrix.

The Drinkbot is intended to be used at live events in a fast paced setting so for the WinCC update, the drink recipe popup should prioritize readability and information efficiency. The new Unified program uses a standard drink faceplate that only displays ingredients used in a particular drink recipe.

The maximum ingredient amount in the original 44 drinks was 3 alcohols and 3 mixers. Custom scripting is used to take the recipe fed into the faceplate and populate the drink name plus the ingredients with their amounts. The script takes in the name and amount of each drink in ounces and automatically fills out each box for how many ingredients exist in each recipe. The user then has controls to make the drink and stop the process midway if needed.

For taking Drinkbot to events where alcohol is not an option, the machine can also be configured to dispense “Italian sodas” using soda water and flavored syrup. Selecting this mode locks the display page to an Italian soda mode and makes the button faceplates open a nested Italian soda faceplate. All Italian soda recipes only include up to two syrups and eight ounces of soda so the faceplate is simplified and resized.

For information on how to create a faceplate in WinCC unified, refer to the guide here: Creating Faceplates in WinCC Unified

Conclusion

The updated HMI program improves the usability and functionality of the COMFORT version. The custom scripted nested faceplates using the new recipe storage system in Unified make it easier to order a drink. To celebrate the completion of the WinCC Unified upgrade the DMC Chicago office had a happy hour party to have the Drinkbot make cocktails and entertain.

The post DMC’s Drinkbot Gets an HMI Upgrade to WinCC Unified appeared first on DMC, Inc..

The Simatic Step 7 manager uses the S7ONLINE access point for communication on the PC/PG interface. By default, the access path on S7ONLINE is set to none as simulating a WinCC HMI program will run disconnected of the PLC program through Simatic manager. The HMI in this state will not display tags read from the PLC but will use HMI local tags and should be fully navigable.

Connection Parameters

The easiest tool to use for establishing a simulator connection is the Siemens Communication Settings tool located in the control panel. Opening the tool will provide you with all possible connection modules on the computer as well as their respective parameters and diagnostics tools. From the address menu you can configure your IP address in the network connections menu of your PC.

To establish simulator-hardware connection, open the Access points menu. Select S7ONLINE and open the dropdown arrow. From here you can select the interface parameter which should match the same pathway that the PC uses to communicate with the hardware. The module property should auto populate and match the network connection name you configured.

In older versions of TIA Portal there is an interface configuration tool found in the Windows control panel named Set PG/PC Interface. From here, you can set the same pathway that will enable communication between the simulator and PLC.

After opening the tool, navigate to the Access path tab and select S7ONLINE as the access point. In the box below you will see all available interfaces for the path to take. Select the module in the list that matches the communication method you are using to talk to your hardware.

After selecting the correct module, you can close the tool and launch your WinCC simulation from Simatic Manager or TIA Portal. Provided that you are in contact, the S7ONLINE point should update your simulation with real data coming from the PLC.

Troubleshooting

If the Set PC/PG tool opens but does not display the S7ONLINE access point, it may be resolved by downloading a Siemens PC_Identifier hotfix support package linked below.

SIMATIC S7-PLCSIM Advanced V4.0

Troubleshooting the PLC connection can follow the same path as a typical process to go online with hardware. Ensure that you have a stable ethernet connection to the PLC you are attempting to communicate with. On the S7ONLINE path that you configured, note the module name that auto populated when the interface parameter was assigned. In your Windows taskbar search “view network connections.” Then, in this menu locate the ethernet driver that has the same module name as on the S7ONLINE path you are trying to use. In the popup window, go to properties then IPv4 and assign your own IP address on the same subnet and mask as the desired PLC. Once complete you should be able to ping the IP of your PLC from the command prompt.

If the simulated instance of your HMI still does not communicate with the PLC, stop the simulation and verify that the PC/PG interface selected when trying to go online with the PLC is the same as configured in either of the tools. Redownloading the program and verifying run mode is active may also assist with troubleshooting measures.

The post Simulating Siemens WinCC Unified HMI with Real PLC Data appeared first on DMC, Inc..

Siemens TIA Portal V18 and WinCC Unified offer effective solutions for setting up user logins, increasing the safety of your operations as a result. In this guide, we’ll walk you through the process of adding local users, runtime rights, and protecting your HMI features in a few simple steps.

Setting Up Users and Rights

The first step is to set up the user profiles for your project. You can set specific rules for password complexity under ‘Security settings’ > ‘Settings.’

Next, navigate to ‘Security settings’ and then to ‘Users and roles.’

In the ‘Users’ tab you can create a new local user profile. To do this, you will need to click on ‘<Add New User>’ and then ‘Add new local user.’ Next, you can enter in a ‘User name’ and ‘Password.’ Here you can also define a timeout, which will automatically log the user out after a certain amount of time. This is also where you will assign roles to each listed user, but we’ll return to this after setting up some roles.

Assigning Roles 

Next, let’s go over ‘Roles’ and ‘Rights.’ Each role is comprised of a set of selected rights. ‘Runtime rights’ are what we will reference while programming protected or user restricted features on the HMI.

To create and name your own custom rights, navigate to the ‘Roles’ tab and then to the ‘User-specific runtime rights.’ Here you can create new rights with custom names and descriptions.

As an example, I have created 4 levels of rights and users as shown above: ‘Admin,’ ‘Maintenance,’ ’Technician,’ and ‘Operator.’ Admin will have the highest level of rights, followed by Maintenance, then Technician, and finally Operator with the lowest level of rights.

To set up the roles for our example setup, return to the ‘Runtime rights’ tab, and then click on ‘Operator’ in the Roles window. This screen will show the HMIs and PLCs available in the project.

For this example, we will set up the runtime rights for the WinCC Unified SCADA device by clicking on the drop down, selecting the device, and then selecting the custom runtime right we created earlier: ‘Operator Rights.’ Since ‘Operator’ has the lowest level of rights, we will only check ‘Operator Rights’ for the ‘Operator’ role.

For the other 3 roles, we will assign the rights as shown below:

Technician – Operator Rights, Technician Rights

Maintenance – Operator Rights, Technician Rights, Maintenance Rights

Admin – Operator Rights, Technician Rights, Maintenance Rights, Admin Rights

When set up this way, a feature that needs to be protected by a user login can be sorted according to the permission hierarchy rules we defined earlier.

The ‘Admin’ user can access anything protected by one of our custom rights, but the ‘Operator’ user can only access those protected by ‘Operator Rights.’ There are many other system defined rights available in which you can also assign to your custom roles if needed.

Creating User-Restricted HMI Features

Next, we will go through how to reference these roles while programming protected features on the HMI. In the example below, we want to restrict the ability to interact with the I/O Field to the Admin user. Navigate to the ‘Security’ dropdown and select ‘Admin Rights’ for the Authorization field.

This will limit interaction with this IO Field to the Admin user only. If you wanted a different level of access, you could choose from any of the other rights available to tailor the access to your needs. This setting is available for most other objects available in WinCC Unified. For anything that you want to restrict with a user login, you can set an Authorization level here.

Downloading User information to HMI

After you’ve made user or role changes it is important to set the dropdown below to ‘Reset to start values.’ This ensures that your changes get updated in runtime.

That’s it! Your basic user login setup is complete. By following the steps outlined in this guide, you can establish user authentication mechanisms tailored to your equipment’s requirements.

The post Setting Up Basic User Profiles and Login for WinCC Unified Runtime appeared first on DMC, Inc..

To accomplish this task in the PLC code, a duplicate datablock can be created to store on the SD card, data can be split up into readable and writeable chunks, and triggers can be created for reading and writing to the SD card. The steps to implement this solution are below:

Step 1: Creating the datablock that will be stored on the SD card

Duplicate the datablock that is to be periodically saved to the SD card. In the duplicated datablock’s properties, set the attribute for “Only store in load memory” to true. This will make sure the datablock is stored on the SD card. All other options can remain the same.

Step 2: Splitting up your data

The “WRIT_DBL” instruction will be used to write the data in a later step. When using this instruction, data with the datatype “Struct” cannot be written. Only UDTs and arrays can be written to another data block. To accommodate this, split the data into sections that can be written to the SD card, and write each section inside of a datablock writing sequence.

Step 3: Writing the Data to the SD Card

To write the data to the SD card, the source block of the “WRIT_DBL” should be set to the data block that is being backed up; the destination block should be set to the corresponding data block on the SD card. If the data was split into sections, make sure to specify the section being copied and written on both the source and destination parameters.

The busy signal is an important component of the reading and writing process. The sequence should only move on to writing the next section when the busy signal is low. The busy signal can be high for several scans, and each write instruction should be given time to finish before moving on to the next one to avoid problems with the writing process.

Step 4: Reading the Data from the SD Card

Reading data from the SD card works similarly to the writing process. Just use the “READ_DBL” instruction. To trigger a read from the SD card on startup, use the Memory bit for “FirstScan” as one of the triggers for the read sequence. The same guidance from the data writing step on using the busy signal applies to the read sequence.

Step 5: Create the Trigger for Reading and Writing

To make a trigger for the reading or writing of the sequence, the timer, button, or any other kind of trigger should be tied to a Boolean. Use that Boolean to set off the write or read sequence. The active signal latches ON using the busy signal and the sequence trigger to complete the sequence without getting interrupted. If the sequence is running, the “bActive” boolean is ON until the sequence is completed.

Stepping through the sequence is controlled by the busy signal. The final step of the sequence should reset the sequence back to the beginning to wait for the next trigger.

Learn more about our Siemens PLC Programming expertise and contact us today for your next project.

The post Using an SD Card for Retentive Memory – Siemens PLC appeared first on DMC, Inc..

To address this problem, Siemens released the Version Control Interface (VCI) in TIA Portal V16. Let’s take a look at how this tool can enable better version control practices.

What is the VCI?

The name “Version Control Interface” is a little misleading on the surface. It does not actually perform any version control operations: rather, it provides a mechanism to synchronize text files between your TIA Portal project and your version control system. Specifically, it imports and exports elements of your project to XML files. These XML files are added to a workspace, which is just a folder on your PC.

If this folder is a version control repository, you can then back those files up, as well as import any changes from the repository back into your project.

A workspace is created with the “Add new workspace” option under the project-level “Version control interface.” Once created, the workspace must be configured by selecting a folder. If you have an add-in for a version control system, that can be configured as well (at the time of this blog, there are no add-ins available yet).

Figure 1. Configuring the workspace.

Exporting Objects

To start using the VCI, you need to export items from your project to the workspace. Currently, the VCI only supports program blocks, PLC tag tables, and PLC data types. Once you have these objects in your project, open the workspace, and drag the desired items from the project view into the workspace view.

You can drag individual items, folders, or the entire PLC to export all objects at once. Note that any item must be compiled to be exported; TIA Portal will give you a prompt that will compile all the objects you have selected. Once the export has finished, your workspace will have folders and files matching the exported items.

Figure 2. The workspace after exporting items. Here, the PLC’s program blocks are shown in the workspace view.

Synchronizing the Project and Workspace

Now that your objects have been exported, you can see that each item in the project view have a green circle. This icon shows the comparison between the project and workspace and uses the same color code as performing a PLC comparison. Since we just exported our items, everything is the same. Let’s go ahead and make some changes to the code in our project.

Figure 3. The workspace after making changes to the TIA Portal project.

I made some changes to fbMain and the IO Tags tag table. These objects now have an icon indicating that there is a difference between the project and the workspace. The small star on the icon shows which side was more recently changed; in this case, it is on the project side.

On the top of the VCI window, there are several buttons that can be used to choose which direction to synchronize the changes. Since I only made changes in the project, I will choose to “Export changes to workspace,” then use the “Synchronize” button to execute this operation. The project changes will then be exported to the workspace and all the objects will show the green icon again.

Comparing Objects

This process works to import changes from the workspace into the project. The XML files produced by the VCI are a bit dense and hard to work with. Typically, you would not be making changes directly to these files, but, instead, using a version control system to load files that another developer had modified and exported. 

For this example, I have loaded a change to my IO Tags tag table in the workspace. The icon for the tag table changes to indicate that a more recent change has been made; however, I would prefer to know what changes I am loading before I execute the operation. Since the XML files are very difficult to read and understand, we will use Siemens’ Simatic Automation Compare Tool for this purpose. 

The Simatic Automation Compare Tool provides a way to view the XML file as it would appear in TIA Portal, as well as see differences between the workspace and project files. It can be downloaded from Siemens’ website. After installing, go to your TIA Portal settings, and set it as a comparison program for the VCI.

 Figure 4. Setting the Simatic Automation Compare Tool as an option for VCI.

Now, if you go back to the workspace, you can open a comparison between your project objects and workspace object by right clicking the project object.
 

Figure 5. Executing comparison between project and workspace.

The compare tool will then be opened, and the comparison displayed. In this case, you can see that I added “Q_Output3” in my file. I can then choose to import this file into my project to get the latest changes.
 Figure 6. Comparison of project and workspace files.

Merging Changes

Both of the above examples involved only changing either the project object or the workspace object. What would happen if changes were made to both? For example, if another developer modified the same function block you did, you would need to reconcile those differences.

There’s no way to manage differences between the project and workspace in a more granular way. To do so, you would need to use an external utility to merge both XML files that you want to reference. If you’re using a version control system, this functionality is built in and can be done with a standard text editor (I’m a big fan of Visual Studio Code).

Otherwise, you can use any one of a plethora of programs for comparing and merging text files. Once you have merged your text files, the resulting file can be imported into your project as normal.

Final Thoughts

Overall, the VCI is a step in the right direction. As someone who gets a lot of use out of version control systems, it is nice to see more PLC platforms starting to incorporate them and provide tools for using them effectively.

Right now, only PLC blocks, tag tables, and data types are supported by the VCI. If you are using version control, you will still need to archive and back up your entire TIA Portal project to preserve changes to things like your hardware configuration or any HMIs.

The ability to see a detailed history of changes made to a project can be very beneficial for managing a project over its lifetime. Additionally, being able to easily import and export files enables multiple developers to quickly share parts of their project with each other, without having to export the entire thing.

Since it is a relatively new feature, keep an eye out for future improvements and additional functionality to be added in later releases.

Learn more about DMC’s TIA Portal development expertise and contact us for your next project.

The post Using the Version Control Interface (VCI) in TIA Portal V16 appeared first on DMC, Inc..

We joined the conference as a Siemens Solution Partner and joined Siemens at their booth – which displayed Siemens’ multi-discipline/multi-step demo and showed off a variety of different technologies, including their metal 3D printing, an additive manufacturing process to generate a lighter, stronger component of an electronic vehicle. We also brought one of our major California Siemens clients, Anaergia, to join in the conference and experience.

Our engineers arrived in Germany on Sunday and joined Siemens as they hosted a dinner at the Governor’s Mansion with great food. Throughout the trip, we joined Siemens for meals, excursions, and experiences.

The conference began Monday, May 30 and finished Friday, June 3. On Monday and Tuesday, we had a full day checking out the expansive Siemens booth and exploring the enormous conference.

Wednesday, we drove to Heidelberg, where we stayed for the second half of the trip. Along the way, we stopped at the Porsche museum (foreshadowing!) getting a chance to check out a slice of Porsche history. Following the day of travel, we joined Siemens for the White Ship Fleet Dinner Cruise.

Thursday, we started our day by visiting the Heidelberg castle via a tour of the old city.

Also on our busy Thursday, we did a tour of the Stuttgart facility where they make the Taycan, the first all-electric Porsche. We had a chance to participate in the Porsche Driving Experience, where they put us on a track and let us test the cars out ourselves. We started by putting the Taycan electric vehicles through a stunt course which included drifting and slaloming. For the finale, we got into 9-11s and got to do a Grand Prix (safely!) around the track.

After a week at the HANNOVER MESSE, we want to thank Siemens for hosting us and our clients. The event was insightful, and it was a pleasure joining them as a Siemens Solutions Partner. We look forward to joining them for this event and others in the future.

Learn more about DMC’s Siemens Partnership and Siemens S7 PLC Programming expertise, and contact us today for your next project!  

The post DMC Attends the HANNOVER MESSE 2022 appeared first on DMC, Inc..

We’ll continue where we left off in the previous blog. We’ve instantiated a Vlv_1Ctrl CM and added the 2Ctrl, Interlock, and Permit variants to the CM instance. I’d like to make the appropriate interconnections to my valve’s chart, so let’s look at the various options available.

The most obvious method is to open the CFC editor and make interconnections by selecting block IOs. This should be no surprise, it is a completely valid method of addressing IO or interconnecting blocks.

I’ll interconnect my valve’s open feedback limit switch using this method. Navigate to sheet B, page 1 where you’ll find the GSH block. Right-click on PV_In and select ‘Interconnection to Address.’ I’ll search for the device symbol that I previously created in the Symbol Table: ZSO-0101. Selecting the symbol will automatically address the correct memory location for this input: I70.2.

The technological IOs above the chart can save you a bit of time navigating between sheets. It summarizes all the pertinent information for the technological type in one convenient location. For example, if we wanted to use the technological IOs to make the closed feedback limit switch interconnection, we could simply open the appropriate object in the technological tree (GSL in this case), click on the signal we want to interconnect (PV_In), and select New Signal Interconnection. This brings up the same symbol navigator as before, where I’ll select ZSC-0101, the symbol for my valve’s closed limit switch.

The summary view provided by the technological IO editor is a convenient way to make interconnections — although it does not lend itself to bulk engineering. For example, Imagine I had multiple valves to configure. I could open each chart and make these interconnections. I could also leverage the Technological View in Simatic Manager to streamline this process.

In the Technological View, browse to the project hierarchy folder that contains your CM instance. In this case, there is only one CM; however, if you find the interface cluttered, you can apply filters (Filter by Column) to selectively view only the objects you care about. Head to the Signals tab to view the chart IOs. Here, you can quickly assign a symbol to the Signal property for each of the available chart signals.

In addition to addressing IO points, you can make interconnections to Parameters (such as the Interlock and Protect block inputs on the Parameters tab) or modify the default Event texts on the Messages tab.

There are multiple ways to make interconnections on PCS7, and each of them has its place. The Siemens BPCM Library lends itself to bulk engineering via the Technological View. If you’re considering PCS7 for your next process automation project, reach out to us at DMC!

Learn more about DMC’s Siemens Solutions Partnership and contact us for your next project. 

Read part one of this series: Introduction to Siemens Best Practice Control Modules

The post Bulk Engineering with Siemens BPCM in PCS7 appeared first on DMC, Inc..

What is the BPCM?

The Siemens BPCM takes its cue from the S-88 batch model. It aims to give developers a predeveloped and tested library of control modules, the lowest level of the S-88 model. Control modules may reference actual hardware, like valves or motors, or they may consist of a controller and an actuator such as a PID temperature controller and modulating globe valve. The BPCM contains fully developed control modules to address all of the routine equipment and controllers throughout your plant.

Valve Example

Not every valve is identical. Whereas one may be a normally closed air-over-spring valve with no feedback, an adjacent valve may be air-over-air with position feedback on either end of its stroke. The BPCM recognizes there is no one-size-fits-all valve prototype and it also eases a developer’s pain by providing variants on the control module to account for these differences.

Drag a Vlv_1Ctrl object from the library into your project hierarchy to create an instance of the control module type and give the object a unique and meaningful name. In this case, the valve I’ve created corresponds to YZ-0101 on my P&ID, so I’ll run with that. By right clicking on the object, you’ll see the option to define CM Variants:

Variants are optional ways you can modify the behavior of the CM type. Below, you can see I’ve selected the 2Ctrl, Interlock, and Permit variants. These variants will create additional blocks on this instance of the Vlv_1Ctrl object – namely, it will create Pcs7DiOu blocks to control the valve in either direction (open vs. close) as well as provide Intlk08 blocks that I can use for my valve interlocks and permissive.

With just a few clicks, we’ve created all of the required blocks to configure our valve. From here, we can configure the connections for our CM with either the Technology view (great for bulk engineering) or on the CM’s chart in the Continuous Function Chart editor.

It’s always better to let the tools do the work for you — in this case, the Siemens BPCM Library is an essential tool to developing consistent, manageable code in Siemens PCS7. If you’re considering PCS7 for your next process automation project, reach out to us at DMC!

Learn more about DMC’s Siemens Solutions Partnership and contact us for your next project. 

Read part two of this series: Bulk Engineering with Siemens BCPM in PCS7

The post Introduction to Siemens Best Practice Control Modules appeared first on DMC, Inc..