If you like automation, then JUMO is the right place for you. Here is Michael again and now we are going to start with a topic from the area of promotion. Today we will take a closer look at the second part of our JUMO variTRON Visu template. Today we're going to cover the configuration of our controller modules, let's go. Ok then we'll start again together, today I brought reinforcements with me again , for the second part of our Visu template, and Felix is there again today . Good morning Felix, hello Michael. Yes, as you can see, we are already back on our Visu template, we are live here in the system and Felix has already selected controller 1, controller 1 and we can see that a controller module is now installed in our project , yes, now there are perhaps many applications of yours where you need several controller modules, but you still want to use our variTRON Visu template, so we will now show you together how you can add more controller modules and which configuration options you can use yes then you have or what settings you still have to make so that it appears so great here in the Visu.
Yes Felix then show us what the first steps look like. Yes, first we go to the setup, here I have expanded the existing burst with a controller module, now you can make adjustments in CODESYS, for this I go to the PLC application tab and start CODESYS. After opening CODESYS, the following tree structure can be seen on the left-hand side, we have the CPU here, as well as two controller modules, under the CPU you can open the PLC-Logic, here is the application and this is each with the structure OEM, Bootapplication to see, under OEM and the program PLC_PRG you can design your visualizations, as well as create your own program, under the boot application the complete menu structure has been created, this is initially irrelevant for you. In order to integrate the added controller module into the visualization, the following steps are now necessary, you can now open it under the OEM folder, here I have defined the global variable list gvlConfigurationController, this can be opened and here you can see the number of the previous modules under iNumberOfControllerModules configure, we now have two controller modules, so we expand that or adapt this to two.
Furthermore, we have the respective module labels here, these are important so that the controller or the CODESYS can communicate with our firmware, we now have the module label here under the hardware configuration, you can now see the module label under Settings, this must now also be integrated into CODESYS, that is Here we have the ModuleLabel ControllerModule2, we now have to change this to CTR04_5 and save it, in the next step the variables in CODESYS must be linked with the controller module 2, this is done via the I / O image, here we already have the I / O under the first controller module -Image filled, this can now be used as a template to also do this in the second controller module, it is structured in such a way that we take an array for each controller module here, i.e. in controller module 1 we have the index 0, in the second controller module it would be this now index 1, otherwise everything is the same, in order to avoid the copy-and-paste errors now, there is a certain trick that you can do here by taking our template and right-clicking on controller module 1 to do an export mappings to CSV, that is, we export the EA image as CSV in Excel, I have already prepared the Excel file, I open it and now you can go through replace, you can now quickly change the respective variables, that means we still have the indices 0 here , you can now change all of them in index 1, that means we copy the text, go to search and replace, add the index here and change the to index 1 and can now replace everything, so all indexes are defined on 1, furthermore the DeviceName is no longer CTR04_2 as it is now in controller module 1, but it is now controller module 2 with CTR04_5, this is also adapted, we copy this text, go back to search and replace, paste the text and replace with 5, replace all.
So we have now changed the CSV file and we can now import it into CODESYS, now we go to controller module 2, right-click and can now select the CSV file via Import mappings from CSV , I have already renamed it to CTR04_5 and open. Now all I / O images are integrated, all variables are integrated and there is no copy-and-paste error, so the controller configuration in CODESYS is complete. Ok then many thanks Felix for the explanation, execution up to here. Of course, now we would like to see whether what Felix has built for us really worked, so the question now would be whether we can already see the changes in the JUMO variTRON Visu template or are there any steps required Felix, please show us again.
Yes, of course , you must first download these changes to the CPU. To do this, you go to the CPU and can now download the file or the project to the CPU. Login wirh download and off we go, now you have to start the CPU after loading . Ok wonderful, then the test will come to see if the whole thing worked, then I would ask you Felix, go to the browser and then let's see if we can now find a second controller in our visu, see right here We're back to the surface again – controller okay and now you can already see, before there was only controller 1, now we have two controllers and if we now go on it, on the second controller, we can see exactly the same picture as we do we were already used to it from our first controller, here of course still without current values, because we have not yet connected any sensors and have not yet made any configuration here, i.e.
We have not specified any setpoints, yes, very good then we thank Felix, great job, I think some information is still there, namely the link between the programmer and the controller modules, so I would also hand over to you that you would just show us this briefly. Exactly if you … if you now have both a programmer and a controller module, you also want to link the programmer setpoints with the controller module, this is done in such a way that we are now in the structure – in the PLC_PRG there is a structure that stOemType means that on the one hand it naturally contains these controller modules, where I said and the programmer, the programmer consists of, at least this type, inputs and outputs and in the programmer, in the output we now have both the setpoints and the control contacts that can now be linked to the outputs or could also be used as setpoints for the controller module , I'll show now: we simply link control circuit 1 from controller module 2 and here in detail the setpoint from programmer 1 to the setpoint of control circuit 1, for this purpose We have already predefined the outputs here under the I / O images and so far the setpoint that is used in the visualization has been linked here t is no longer needed because we now want to use the programmer, this is always a REAL variable, shown here, we can now link them by going to this point Point Point, under Application – PLC_PRG is the Structure stOem can be seen, here there is the structure of the programmer, here you can click again, here always the stOUT that I just showed, here we can now take the setpoint, this consists of an array of 30 REAL values, you can Now say here, we now have programmer 1 and take the first setpoint, so we have linked the programmer or the setpoint of programmer 1 with control circuit 1.
Ok then thank you so much Felix, as we can see the Felix has now transferred our changes to the control again, we are in RUN, then the question about the test again, did the whole thing work, therefore I would ask you to show briefly in our Visu what the changes are now looking like, I am just moderating it, that means we go back together now first to the programmer – programmer 1 and here is already program 2 or program name 2 selected accordingly, right now Felix starts the program here accordingly and now we look at the setpoint from our controller, yes we can see the ramp is going up, so it worked, was successful and so many love thanks to Felix, yes me think that brings us to the end of this video, I hope everything has been brought across in an understandable manner, otherwise if there are any questions, feel free to ask in the comments, we b They'll be happy to answer, yes in this sense, if you liked the video, please leave your thumbs up there, we'll see you again for the next part, it's mainly about process images, that will then be part 3 of the variTRON Visu template , Have a great day with you and do it well – bye.