I’m so happy that I can present some exciting news about innovations from the world of WAGO. I also get to introduce the new format for our WAGO webcasts. In this webcast, we’re going to be focus on “control technology”. My colleagues, Jens Krake and Cord Rombach, and myself, Christian Bartelheimer, will provide you with more in-depth information about the subject. If you have questions during the webcast, feel free to ask them in the chat window, and we will answer them as they come in. If you’re watching this afterwards, then feel free to contact our support people. So, on to the topic. So, on to the topic. Like we said, we’re focusing on control technology. First, I’d like to provide some additional context about the subject. Although we’re currently talking about control technology, there are some other webcasts about similar topics that have a strong connection to this. These include, for example, touch panels, which also ultimately integrate PFC technology, that is, the software features. This means that the second part of our webcast will also interest people who deal with displays. Then we have our new WAGO I/O System Advanced, which we have integrated into our PFC technology. So, the second part will interest those working with our PFCs. I would now like to look at control technology in a bit more depth. In addition to our ETHERNET controllers, which we have offered for 20 years and are currently in their fourth generation, we also have the Controller PFC. We have an incredibly broad portfolio of PFCs, with numerous variants to precisely satisfy your requirements. You can always find the right device in our portfolio to match your specific application and needs. What these devices have in common is their Linux® operating system, which provides diverse security features directly on board. The special thing about this controller platform is that we can use these devices as automation controllers. This means that you can use e!COCKPIT, our inhouse engineering software, to its full potential. The diverse fieldbuses, all of the configurators, everything that we offer and you are familiar with, can be used with this platform. you are familiar with, can be used with this platform. You can use open standards and languages that are already well established. This would be a good point to mention Docker, a container technology that has gained importance over the last few years, because it makes it very easy to integrate new functionalities. Our platform also has this potential. We should also mention, that when we discuss container technology, we are not just talking about the PFCs from the 750 Series, but also the new WAGO I/O System Advanced, and our displays, as mentioned before. These also have this technology. Now, we’d like to turn to our innovations. We have added two new devices to our portfolio: one with a cellular modem, and the other has four ETHERNET ports. We also have new software features to introduce, and we now have the technical ability to add a BACnet stack to the devices, and onto WAGO’s own OPC-UA server. In principle, the hardware is designed similarly to another one of our favorite devices. On the left, you can see a serial interface and two ETHERNET sockets. On the right is a modem, like the previous unit, but which is marketed for 3G technology. It is easy to recognize, due to the four large ventilation slots. Here is the antenna connection, but otherwise, it functions like a conventional PFC. We also have LEDs for signaling. So, that’s it for the hardware. PFC already implies many of the advantages that I have just mentioned. The multiple possibilities included on this platform are naturally also available on this device. The actual feature distinguishing it from other PFCs is precisely this LTE modem. This means that I can use new cellular standards, can implement LTE easily on the device, and thus on the PFC platform as well. The particular innovation in our device is that it provides an especially compact solution in comparison to others. You can save a lot of space because the modem is integrated into the module. And because the connection cannot be separated on the hardware side, it also provides a high level of security. I can answer that with a definitive no. And I would also like to explain why. The cool thing about the 5G infrastructure, which is currently under construction (all of the frequencies will be allocated, but not all of them have been allocated yet), is that the 5G infrastructure also supports 4G, or, to be strictly accurate, LTE. Therefore, I can also in corporate this device in a 5G infrastructure, and remain quite future-proof. However, you must also consider that industrial products, and that also includes the modems incorporated in this device or other devices, in this device or other devices, often become available at a later point in time than consumer products. Therefore, it could be some time until industrial 5G products can be purchased. OPC UA is a topic that is generally on everyone’s mind. There are currently many different standards on the market and the goal of OPC UA is to establish itself, in principle, as THE standard. Because we recognize that OPC UA has succeeded at many points and continues to forge ahead, it is also, naturally, important for WAGO. So that is what we are focusing on now! We want to take some initiative with regard to this technology. It is quite important to work with this topic, and we wanted to do that. Therefore, we decided to create our own solution, so that we can also advance the most important features. The subject of “security” is often mentioned in concert with OPC UA; this is quite important from our point of view, and is currently gaining increasing attention on the market. and is currently gaining increasing attention on the market. This is an area, in which we can offer an excellent range of services with our own server, and we plan to push ahead with this. The 3S server is already used by our current firmware. This will remain the case, because we want to support our clients in the best possible way as they move from an older solution to a newer one. For this reason, there will be an installation packet, available from our support people and also from the website, which you can then install. This deactivates the old server and brings the new one on line for your use. Hello, My name is Jens Krake, and I’m the product manager for the range of products that includes controllers and HMI, and I would like to introduce our new 750-8210 Controller. It adds to the successful PFC200 generation 2 series and has, in addition to the technical features common to the series, four RJ-45 ETHERNET ports and a transmission speed of 100 megabits. The innovation in the 750-8210 and its variants is that all four ports can be freely separated. This means that I can communicate in one network using all four ports, or I can also use the four ports to communicate in four separate networks. Any combination is conceivable, so that two ETHERNET ports can communicate in one network and two ETHERNET ports can communicate in another. It’s really easy, and I would like to show you the configuration, using the new Web-Based Management. First, I have to log in on the login screen. The controller recognizes that I have logged in using the default password, and password, and indicates that I should probably change that. I can reset that under the “Users” setting under the “Configuration” tab. Afterwards, I click on the “Networking” menu to reset the ETHERNET configuration. As you can see, the device currently has the default settings, and all four ports are assigned to bridge 1; that means that all four ports are switched to one network. So now, I am going to separate the device, so that two ports communicate in one network, and two ports communicate in another. I enter the IP address for the new network in the “TCP/IP Configuration” field. Any possible network is available at this point: in my case, I select a static IP address. However, DHCP or BOOTP would also be possible. What is important is that the subnet template separates the networks. The controller also indicates to me that the interface features have been changed, so that if this is a mistake, I can now correct it. The “Information” tab now shows that the settings have been accepted and the two ETHERNET ports can now communicate using the IP address. I can find the firewall settings under the “Security” tab, which has now been expanded by a new bridge, so that I can have different firewall settings for each separate network. The configuration for two times two ports is now complete. By way of example, I’m now going to add a third bridge, so that you can see how easy it is for the device to communicate in three different networks. To do this, I assign port X12 to bridge 3 so that I can enter a new IP address in the TCP/IP configuration menu. I select a static IP address for this as well, which naturally has to be located in another network. And here, you can see that I can carry out independent firewall settings for the third network. The third IP address has also been accepted, and you can see how easy the whole thing is. Hello, my name is Cord Rombach, and I’m a product manager for HMI controllers, I am going to discuss BACnet IP in today’s webcast. In 2019, we developed our first BACnet IP controller based on the PFC200. This controller satisfies revision 14, is listed with BTL, and has the AMEV attestation, which is important for Germany. In comparison withh our previous controllers, the new controller has a higher number of BACnet objects and can display BACnet objects in tables, using Web-Visu, and even change them, which I find to be a particular highlight. In addition, we went a step farther: we are now at firmware version 16 and have the opportunity to import BACnet IP into the controller using certificates. For us, that affects the PFC200 controllers and the WAGO touch panels. We have, in total, developed two distinct licenses: with a lower number of BACnet objects, with a higher number; and, in combination with the devices and the BACnet licenses, it is possible to differentiate up to 26 BACnet IP devices. Furthermore, we also have the potential to retrofit BACnet for existing systems. It’s quite simple: the devices have to undergo an update to firmware 16, and then I can upload the licenses into the devices using proven tools, for us that means e!COCKPIT or the WAGO Upload, and I can already execute the BACnet IP on this device through the licensing allocation alone. We have a total of three noteworthy innovations. The first is an add-on for e!COCKPIT. By using the BACnet add-on, I can easily configure BACnet objects from I/O data points. In addition, you have the potential in e!COCKPIT to enter data into the controller configuration: by using a call interface, I can get into the WAGO BACnet configurator and implement further changes. When I synchronize everything back again, I have my data in e!COCKPIT and thus, I have an easy path for setting up BACnet-I/O data points using e!COCKPIT. This is a very easy and efficient possibility! The second innovation is the alarm handling. BACnet itself offers mechanisms for detecting and evaluating alarms. These are sent to clients via event notifications. In the new firmware, the PFC200 and the WAGO Touch Panel can also read out alarms and display them in an alarm table. This makes it possible to detect alarms, and likewise to configure and/or acknowledge them. Thus, I have the ability, locally on site, to acknowledge corresponding alarms, e.g., in a ventilation station. Now, we come to trend data. We have a datalogger that we have been using for quite some time at WAGO. This is a web tool, which can be called up in the web browser, and you can use it to show data in a graphic display. The tool offers several convenient functions: for example, zooming and scaling are possible, and we can now use this tool to display BACnet trend data. This allows me to appropriately read the BACnet trend data: I can display information, data, and curves, and I can also process them. This provides me with the capability, for example, to be able to directly display temperature profiles in a system on site, for example, a ventilation system. In 2019, we overhauled the entire WAGO BACnet-IP product portfolio, and we want to emphasize the new features in 2020. To demonstrate this to those outside the company, we decided to become Gold Members in BACnet International. We want to reflect the reliability and consistency to others, and we want to be an integral component for our customers when they search for new solutions for new tasks and projects in the BACnet area. And now we have arrived at the end of our “Control Technology” webcast. I hope that you have received a lot of interesting information. Please feel free to use our “Meet the Speaker” function, which will allow you to exchange thoughts with our colleagues and obtain additional information. You can also request additional information from our support people. Thank you for your interest, and stay healthy!