1 00:00:00,799 --> 00:00:03,199 Welcome back to the Automation Podcast, the world's 2 00:00:03,199 --> 00:00:06,319 number one industrial automation product and technology show. 3 00:00:06,319 --> 00:00:07,299 Thanks to you, 4 00:00:07,679 --> 00:00:10,960 our audience of highly skilled automation professionals. Now 5 00:00:10,960 --> 00:00:12,080 if you're new to the show, my name 6 00:00:12,080 --> 00:00:14,304 is Sean Tierney from Insights and Automation, and 7 00:00:14,304 --> 00:00:16,225 I wanna thank you and our entire audience 8 00:00:16,225 --> 00:00:18,625 for tuning in this week. Now in this 9 00:00:18,625 --> 00:00:20,704 episode, I sit down with John Dattellum of 10 00:00:20,704 --> 00:00:21,204 Siemens 11 00:00:21,505 --> 00:00:23,204 to learn all about migrating 12 00:00:23,664 --> 00:00:24,725 from older versions 13 00:00:25,025 --> 00:00:26,484 of s seven PLCs 14 00:00:26,864 --> 00:00:28,804 and to a portal software 15 00:00:29,280 --> 00:00:30,960 to the newest versions. You know, we just 16 00:00:30,960 --> 00:00:33,600 covered version 21 with, John a few weeks 17 00:00:33,600 --> 00:00:36,000 ago, and now he walks through what you 18 00:00:36,000 --> 00:00:37,920 do to migrate. Maybe you have 19 or 19 00:00:37,920 --> 00:00:40,079 20 and you wanna go to 21, and 20 00:00:40,079 --> 00:00:41,760 he walks us through the steps to do 21 00:00:41,760 --> 00:00:43,784 that. And I found it really interesting that 22 00:00:43,784 --> 00:00:45,545 you don't have to flash the firmware of 23 00:00:45,545 --> 00:00:47,625 your controller right away, and you don't have 24 00:00:47,625 --> 00:00:48,204 to actually, 25 00:00:48,585 --> 00:00:50,504 upgrade your program right away to be able 26 00:00:50,504 --> 00:00:52,284 to use these. So there's some flexibility 27 00:00:52,585 --> 00:00:54,664 there to keep the PLC at the older 28 00:00:54,664 --> 00:00:57,929 firmware while you migrate your software or even 29 00:00:58,250 --> 00:01:00,250 download the software to a PLC that has 30 00:01:00,250 --> 00:01:02,250 a new firmware in it without upgrading your 31 00:01:02,250 --> 00:01:04,489 software. So really interesting stuff, and he goes 32 00:01:04,489 --> 00:01:05,930 through it all. But before we get to 33 00:01:05,930 --> 00:01:07,290 that, we got a couple of announcements. First, 34 00:01:07,290 --> 00:01:09,709 I wanna thank Siemens for sponsoring this episode. 35 00:01:10,025 --> 00:01:11,305 Not only did they take time out of 36 00:01:11,305 --> 00:01:12,745 their busy schedule to come on the show, 37 00:01:12,745 --> 00:01:14,745 but they also sponsor the show so we 38 00:01:14,745 --> 00:01:16,825 could release it to the broadest audience, the 39 00:01:16,825 --> 00:01:19,545 widest audience as possible. So we really appreciate 40 00:01:19,545 --> 00:01:20,284 their sponsorship. 41 00:01:20,745 --> 00:01:22,584 And the other announcement I have is from 42 00:01:22,584 --> 00:01:23,724 the Automation Museum. 43 00:01:24,049 --> 00:01:25,569 They wanted me to let you guys know 44 00:01:25,569 --> 00:01:27,829 that the first eight episodes are now out 45 00:01:28,049 --> 00:01:28,790 over at, 46 00:01:29,250 --> 00:01:30,049 youtube.com 47 00:01:30,049 --> 00:01:31,989 forward /@automationmuseum. 48 00:01:32,370 --> 00:01:34,049 And so the first eight episodes of the 49 00:01:34,049 --> 00:01:36,849 History of Automation podcast is out. We have 50 00:01:36,849 --> 00:01:39,349 four more in the queue that are coming. 51 00:01:39,605 --> 00:01:41,444 So please, go over and check out that 52 00:01:41,444 --> 00:01:43,064 channel and give us a subscription 53 00:01:43,525 --> 00:01:45,765 because, myself and the other host of that 54 00:01:45,765 --> 00:01:48,005 show are working very hard on the weekends 55 00:01:48,005 --> 00:01:50,825 to bring you more podcasts about legacy automation. 56 00:01:51,045 --> 00:01:54,119 Really interesting stuff. So with that said, let's 57 00:01:54,119 --> 00:01:55,959 go ahead now and jump into this week's 58 00:01:55,959 --> 00:01:58,519 episode and learn all about migrating from older 59 00:01:58,519 --> 00:02:01,899 versions of TIA Portal and s seven firmware 60 00:02:02,039 --> 00:02:04,359 to the latest and greatest. Hey, everybody. Welcome 61 00:02:04,359 --> 00:02:05,879 back to the show, and I wanna thank 62 00:02:05,879 --> 00:02:07,944 John for for coming back on. He's gonna 63 00:02:07,944 --> 00:02:09,944 walk us through something which I know if 64 00:02:09,944 --> 00:02:11,465 you haven't used it in a while can 65 00:02:11,465 --> 00:02:14,025 be a little confusing. So, John, thank you 66 00:02:14,025 --> 00:02:15,784 for coming back on the show. Appreciate you 67 00:02:15,784 --> 00:02:18,985 doing the recent v 21 update. And now 68 00:02:18,985 --> 00:02:20,590 you're going to give us a for some 69 00:02:20,590 --> 00:02:21,870 of us, it'll be a review. For some 70 00:02:21,870 --> 00:02:23,090 of us, it'll be new information. 71 00:02:23,709 --> 00:02:25,949 But, go ahead. Let me turn the floor 72 00:02:25,949 --> 00:02:26,769 over to you. 73 00:02:27,709 --> 00:02:28,530 Yeah. So 74 00:02:28,989 --> 00:02:30,829 the one thing that we we agreed to 75 00:02:30,829 --> 00:02:32,769 talk about was an understanding of, 76 00:02:33,629 --> 00:02:34,129 upgrading 77 00:02:34,430 --> 00:02:37,474 the project to the latest version, b 21, 78 00:02:37,694 --> 00:02:40,655 from the previous versions where the project might 79 00:02:40,655 --> 00:02:41,155 reside. 80 00:02:41,455 --> 00:02:42,834 And then secondarily 81 00:02:43,215 --> 00:02:44,094 to that is, 82 00:02:45,294 --> 00:02:45,794 updating 83 00:02:46,334 --> 00:02:48,034 the version or the image 84 00:02:48,814 --> 00:02:49,634 of the devices 85 00:02:50,229 --> 00:02:50,810 that exist. 86 00:02:51,990 --> 00:02:54,550 And the the the one key thing that 87 00:02:54,550 --> 00:02:56,150 I and I think this will make it 88 00:02:56,150 --> 00:02:58,090 easier to understand is that, 89 00:02:58,870 --> 00:03:00,550 if I'm working in an older version like 90 00:03:00,550 --> 00:03:02,490 a v 17 or a v 18 91 00:03:04,664 --> 00:03:06,444 TI portal on my machine, 92 00:03:07,784 --> 00:03:08,525 our intent 93 00:03:09,224 --> 00:03:11,784 is that the devices that come out with 94 00:03:11,784 --> 00:03:12,444 new firmware 95 00:03:13,305 --> 00:03:13,805 are 96 00:03:14,185 --> 00:03:15,960 compatible with the older versions. 97 00:03:17,080 --> 00:03:19,400 So if if my demo equipment that I'm 98 00:03:19,400 --> 00:03:20,860 running here in v 20, 99 00:03:21,240 --> 00:03:23,420 I put in a a brand new PLC 100 00:03:23,879 --> 00:03:26,219 or have to update the HMI, 101 00:03:26,760 --> 00:03:28,139 our objective, our intent 102 00:03:28,599 --> 00:03:29,260 is that 103 00:03:29,800 --> 00:03:30,780 the new device, 104 00:03:31,275 --> 00:03:32,474 even though it won't show up in my 105 00:03:32,474 --> 00:03:32,974 catalog 106 00:03:33,594 --> 00:03:35,215 with the part number and the firmware, 107 00:03:35,754 --> 00:03:38,094 it is backward compatible with the v 19. 108 00:03:40,634 --> 00:03:42,735 So that's the first thing that that, 109 00:03:43,995 --> 00:03:45,870 I I want people to think about is 110 00:03:46,030 --> 00:03:48,030 I'm I'm working with v 17 or v 111 00:03:48,030 --> 00:03:49,330 18 or v 19, 112 00:03:49,870 --> 00:03:52,129 and I get new a replacement PLC 113 00:03:53,389 --> 00:03:55,229 for something that might happen or I have 114 00:03:55,229 --> 00:03:57,150 a new machine, but I still wanna use 115 00:03:57,150 --> 00:03:58,129 that older version. 116 00:03:59,375 --> 00:04:01,314 I can use the new hardware 117 00:04:01,935 --> 00:04:03,715 or the new image, the new firmware, 118 00:04:04,495 --> 00:04:06,974 and it will be backward compatible with that 119 00:04:06,974 --> 00:04:08,974 old set. Yeah. And let's talk about that 120 00:04:08,974 --> 00:04:10,895 for a minute. So I I have an 121 00:04:10,895 --> 00:04:11,795 existing machine. 122 00:04:12,409 --> 00:04:14,330 I'm using v 17 on it. Let's say 123 00:04:14,330 --> 00:04:16,029 it's a 1,500, for example, 124 00:04:16,490 --> 00:04:18,009 and I don't know what the firmware would 125 00:04:18,009 --> 00:04:19,610 be. It could be three dot x, four 126 00:04:19,610 --> 00:04:21,069 dot x, whatever it is. 127 00:04:21,610 --> 00:04:22,110 Now 128 00:04:22,729 --> 00:04:24,569 I have I have to buy one for 129 00:04:24,569 --> 00:04:26,509 the spears for the shelf. Right? 130 00:04:27,495 --> 00:04:29,334 And that one could be newer because it's 131 00:04:29,334 --> 00:04:31,915 bought after the machine. What you're saying is 132 00:04:32,375 --> 00:04:34,555 that if we get a newer unit, 133 00:04:35,254 --> 00:04:36,555 you know, from the storeroom, 134 00:04:37,175 --> 00:04:39,495 that the intent Siemens' intent is that that 135 00:04:39,495 --> 00:04:41,250 newer unit will be able to plug right 136 00:04:41,250 --> 00:04:43,110 into the same spot as the older unit 137 00:04:44,209 --> 00:04:46,289 and, you know, assuming that everything else is 138 00:04:46,289 --> 00:04:47,649 the same. Right? It has the same number, 139 00:04:47,649 --> 00:04:49,329 Ethernet ports and all that stuff, or Ethernet 140 00:04:49,329 --> 00:04:50,769 ports and all that. It'll be able to 141 00:04:50,769 --> 00:04:52,289 plug into the same unit. You'll be able 142 00:04:52,289 --> 00:04:54,795 to download the same program to it so 143 00:04:54,795 --> 00:04:56,394 that you don't have to really worry that 144 00:04:56,394 --> 00:04:58,555 if the room the the replacement and the 145 00:04:58,555 --> 00:04:59,694 spear in the storeroom 146 00:05:00,074 --> 00:05:02,634 is newer, the attempt is that the newer 147 00:05:02,634 --> 00:05:04,154 unit will always be able to replace an 148 00:05:04,154 --> 00:05:05,915 older unit, and you won't have to buy 149 00:05:05,915 --> 00:05:08,175 a software upgrade. Am I understanding that correctly? 150 00:05:08,634 --> 00:05:09,089 Correct. 151 00:05:09,649 --> 00:05:10,149 Yep. 152 00:05:10,610 --> 00:05:12,870 And the other thing is you don't 153 00:05:13,490 --> 00:05:15,569 typically need to download. You just move the 154 00:05:15,569 --> 00:05:17,669 memory card. The memory card has the full, 155 00:05:19,569 --> 00:05:20,069 running, 156 00:05:21,410 --> 00:05:23,110 application in the 1,500. 157 00:05:23,345 --> 00:05:25,105 So the intent is you pull the memory 158 00:05:25,105 --> 00:05:27,125 card out of the PLC because you know 159 00:05:27,585 --> 00:05:28,965 that's what was running in the, 160 00:05:29,345 --> 00:05:29,845 predecessor 161 00:05:30,145 --> 00:05:30,645 version, 162 00:05:31,025 --> 00:05:32,625 if it's a replacement. If it's a new 163 00:05:32,625 --> 00:05:34,705 machine, then that's the other but the mem 164 00:05:34,785 --> 00:05:36,600 I've done it before where I just pulled 165 00:05:36,600 --> 00:05:38,060 the memory card out of the, 166 00:05:38,919 --> 00:05:40,680 older version of the hardware. It was a 167 00:05:40,680 --> 00:05:41,879 a zero two that you see here on 168 00:05:41,879 --> 00:05:42,540 the screen. 169 00:05:43,079 --> 00:05:45,000 And then I I put in a a 170 00:05:45,000 --> 00:05:46,839 new hardware, which is the zero three, the 171 00:05:46,839 --> 00:05:48,615 latest. These numbers go up. 172 00:05:49,574 --> 00:05:51,254 And in my case, it was probably a 173 00:05:51,254 --> 00:05:53,435 3.1 because it was a couple years ago. 174 00:05:53,495 --> 00:05:56,235 Put that memory card from the 2.9 firmware 175 00:05:56,454 --> 00:05:58,615 on this hardware into this one, put it 176 00:05:58,615 --> 00:06:00,774 in, run mode, and I was good. Because 177 00:06:00,774 --> 00:06:03,254 the device know. Yeah. Go ahead. Because the 178 00:06:03,254 --> 00:06:04,555 device is backward compatible. 179 00:06:05,230 --> 00:06:07,310 And that's important to know because the 15 180 00:06:07,310 --> 00:06:08,850 hundreds, they require that 181 00:06:09,230 --> 00:06:11,709 SIMATIC memory card. Right? So you're not gonna 182 00:06:11,709 --> 00:06:14,350 use a 1,500 without that official card. But 183 00:06:14,350 --> 00:06:17,149 the upside of that is that unlike a 184 00:06:17,149 --> 00:06:19,345 lot of other products on the market, if 185 00:06:19,345 --> 00:06:20,865 it goes down, you just put the card 186 00:06:20,865 --> 00:06:21,985 out, put it in the new one, and 187 00:06:21,985 --> 00:06:24,144 you're good to go. So that from a 188 00:06:24,144 --> 00:06:27,345 ease of replacement, that's just awesome. And the 189 00:06:27,345 --> 00:06:29,745 cards are like all these industrial cards. They're 190 00:06:29,745 --> 00:06:32,064 they're very reasonable and priced based on having 191 00:06:32,064 --> 00:06:32,884 to be industrial, 192 00:06:33,199 --> 00:06:35,040 But that's that's pretty awesome. So let me 193 00:06:35,040 --> 00:06:36,019 turn it back to you. 194 00:06:36,639 --> 00:06:38,720 Yep. So that's the first thing that people 195 00:06:38,720 --> 00:06:39,620 need to really 196 00:06:40,079 --> 00:06:41,459 grasp is that 197 00:06:41,759 --> 00:06:44,720 even though there's new version of Kia Porto 198 00:06:44,720 --> 00:06:45,615 v 21, 199 00:06:45,694 --> 00:06:47,794 even though there's new versions of the firmware 200 00:06:47,935 --> 00:06:49,074 4.1, 201 00:06:50,654 --> 00:06:53,074 I can still use the new hardware, 202 00:06:54,894 --> 00:06:56,115 that comes out 203 00:06:56,574 --> 00:06:58,495 in my systems if I'm not ready to 204 00:06:58,495 --> 00:06:59,454 upgrade to v 21 205 00:07:00,095 --> 00:07:01,314 v 21 yet. 206 00:07:02,129 --> 00:07:04,629 The other thing that's key to understand 207 00:07:05,089 --> 00:07:05,589 is 208 00:07:06,129 --> 00:07:07,430 you can see on my screen, 209 00:07:08,209 --> 00:07:09,430 I am working 210 00:07:09,810 --> 00:07:11,189 right now on a v 20 211 00:07:11,649 --> 00:07:13,350 online with my running demo. 212 00:07:14,290 --> 00:07:14,790 And, 213 00:07:15,644 --> 00:07:18,524 I've already updated this PLC firmware to a 214 00:07:18,524 --> 00:07:20,944 4.1, which is not shown. 215 00:07:21,564 --> 00:07:22,064 So 216 00:07:22,604 --> 00:07:24,305 even though v 20, 217 00:07:25,004 --> 00:07:27,644 the latest firmware and functionality it supports is 218 00:07:27,644 --> 00:07:28,784 a four point o, 219 00:07:29,930 --> 00:07:31,230 The actual device 220 00:07:31,770 --> 00:07:34,910 that exists in this running system 221 00:07:35,850 --> 00:07:36,350 is 222 00:07:36,650 --> 00:07:38,990 a 4.1 firmware because I've been doing 223 00:07:39,850 --> 00:07:41,850 things with v 21, so I upgraded the 224 00:07:41,850 --> 00:07:43,290 firmware so I could see it. So I 225 00:07:43,290 --> 00:07:45,545 can go here. I could connect to that 226 00:07:45,545 --> 00:07:46,045 PLC 227 00:07:46,504 --> 00:07:47,004 online, 228 00:07:47,944 --> 00:07:50,045 and you can see that it's a 4.1. 229 00:07:50,425 --> 00:07:51,805 So in your project, 230 00:07:52,504 --> 00:07:54,444 there's a version 20 project. 231 00:07:55,225 --> 00:07:57,884 You have told that the controller, the PLC 232 00:07:58,025 --> 00:07:59,965 is version four point o, 233 00:08:00,399 --> 00:08:03,439 And you downloaded that to the actual physical 234 00:08:03,439 --> 00:08:05,779 PLC, which is a 4.1. 235 00:08:06,160 --> 00:08:08,720 Correct. And I noticed you is that why 236 00:08:08,720 --> 00:08:11,279 you have there's an orange exclamation point at 237 00:08:11,279 --> 00:08:12,500 the top of the 238 00:08:13,120 --> 00:08:15,504 project tree. Is that what that is telling 239 00:08:15,504 --> 00:08:16,884 us, or is that something else? 240 00:08:17,345 --> 00:08:18,884 That's because I don't use passwords. 241 00:08:19,585 --> 00:08:21,285 Okay. That's fine. So 242 00:08:21,585 --> 00:08:23,745 would you when you go to download this 243 00:08:23,745 --> 00:08:25,824 and it sees, hey. The firmware is newer 244 00:08:25,824 --> 00:08:28,120 than what your project set to, Does it 245 00:08:28,120 --> 00:08:30,040 give you a complaint? Does does it say, 246 00:08:30,040 --> 00:08:31,879 hey. Are you are you sure you wanna 247 00:08:31,879 --> 00:08:32,459 do this? 248 00:08:34,200 --> 00:08:36,299 No. Normally, on that, it doesn't. 249 00:08:37,080 --> 00:08:39,340 Okay. On some of the other ones, like, 250 00:08:40,200 --> 00:08:40,544 the, 251 00:08:41,024 --> 00:08:41,684 the HMI 252 00:08:42,384 --> 00:08:42,884 will 253 00:08:43,424 --> 00:08:43,924 notice 254 00:08:44,384 --> 00:08:46,725 that it's a newer version of the image, 255 00:08:47,105 --> 00:08:49,605 and the HMI will queue more. 256 00:08:50,865 --> 00:08:51,684 It will 257 00:08:52,225 --> 00:08:52,964 queue me 258 00:08:53,345 --> 00:08:54,539 if the, 259 00:08:55,720 --> 00:08:56,379 if I'm 260 00:08:57,000 --> 00:08:57,500 downloading 261 00:08:57,879 --> 00:08:59,960 this v 20 project into the PLC and 262 00:08:59,960 --> 00:09:01,720 it's a v 21. I have a screenshot 263 00:09:01,720 --> 00:09:03,480 of that that I captured because I was 264 00:09:03,480 --> 00:09:06,615 downgrading it yesterday Yep. Over the spring. So 265 00:09:06,615 --> 00:09:07,835 it will say, 266 00:09:08,375 --> 00:09:09,115 for example, 267 00:09:10,134 --> 00:09:12,294 I've been working on this demo equipment the 268 00:09:12,294 --> 00:09:14,054 last week, and I've been doing a v 269 00:09:14,054 --> 00:09:16,054 21. This morning, I wanted to start of 270 00:09:16,054 --> 00:09:18,134 v 20. So when I went to download 271 00:09:18,134 --> 00:09:18,480 it, 272 00:09:19,039 --> 00:09:21,299 the download dialogue came up and said, hey. 273 00:09:21,839 --> 00:09:24,000 The device you're dialing downloading to is a 274 00:09:24,000 --> 00:09:25,779 v 21. Are you sure 275 00:09:26,320 --> 00:09:28,399 that you wanna download it to a v 276 00:09:28,399 --> 00:09:31,459 20? Because it knows it's degrading or downgrading 277 00:09:31,519 --> 00:09:32,179 the functionality. 278 00:09:33,014 --> 00:09:35,174 Got it. Great. Well, that's good. Well and 279 00:09:35,174 --> 00:09:37,334 it's good because you may not you know, 280 00:09:37,334 --> 00:09:39,014 you may get a unit in. It's been 281 00:09:39,014 --> 00:09:40,855 flashed to the newer firmware, but you need 282 00:09:40,855 --> 00:09:43,334 to keep the program in 20 for whatever 283 00:09:43,334 --> 00:09:45,254 reason so that we can use to continue 284 00:09:45,254 --> 00:09:47,190 to use that, which I think is so 285 00:09:47,190 --> 00:09:49,509 so pretty, you know, awesome. And, again, if 286 00:09:49,509 --> 00:09:51,589 you use an HMI, you may wanna keep 287 00:09:51,589 --> 00:09:53,190 it. That that's one reason why you may 288 00:09:53,190 --> 00:09:54,950 wanna not change it is because there may 289 00:09:54,950 --> 00:09:56,549 be other things connected to it, and you 290 00:09:56,549 --> 00:09:58,629 don't wanna change everything. Maybe you'll do that 291 00:09:58,629 --> 00:10:00,584 when things are down. But right now, you 292 00:10:00,704 --> 00:10:01,985 we just wanna keep the machine up and 293 00:10:01,985 --> 00:10:04,065 running, so we don't wanna be forced into 294 00:10:04,065 --> 00:10:06,485 migrating. So that's awesome. Okay. Good. 295 00:10:07,105 --> 00:10:09,184 Yeah. That's the one thing I I really 296 00:10:09,184 --> 00:10:11,284 try to drive home is that start somewhere 297 00:10:11,345 --> 00:10:12,659 where you know, 298 00:10:13,919 --> 00:10:14,740 that is, 299 00:10:16,000 --> 00:10:17,379 reachable like the PLC, 300 00:10:17,919 --> 00:10:19,440 where it's not gonna make an impact and 301 00:10:19,440 --> 00:10:21,279 I don't have to risk dealing with the 302 00:10:21,279 --> 00:10:22,960 HMI or the drive or the third party 303 00:10:22,960 --> 00:10:25,904 devices that might be connected or OPC UA, 304 00:10:25,904 --> 00:10:29,024 things that might get impacted by doing the 305 00:10:29,024 --> 00:10:33,024 upgrades, is start somewhere such as the firmware 306 00:10:33,024 --> 00:10:33,764 of the PLC, 307 00:10:34,384 --> 00:10:37,105 the project revision of the project, TF portal 308 00:10:37,105 --> 00:10:38,070 b 21. 309 00:10:38,230 --> 00:10:38,889 And then, 310 00:10:39,590 --> 00:10:42,730 you can after everything verifies it's communicating, 311 00:10:43,029 --> 00:10:43,769 like, HMI, 312 00:10:44,149 --> 00:10:45,830 then you can start to go, alright. Next 313 00:10:45,830 --> 00:10:47,350 week, I'll do the HMI. I'll do the 314 00:10:47,350 --> 00:10:48,889 drives and and then 315 00:10:49,990 --> 00:10:51,884 bridge it so that I I have a 316 00:10:51,884 --> 00:10:53,804 strategy. And the other thing I really try 317 00:10:53,804 --> 00:10:56,445 to bring home is if something does show 318 00:10:56,445 --> 00:10:58,865 us that is not necessarily, 319 00:10:59,884 --> 00:11:02,284 supporting the migration to the firmware or the, 320 00:11:03,085 --> 00:11:03,745 of the 321 00:11:04,519 --> 00:11:05,660 version of the project, 322 00:11:06,279 --> 00:11:07,720 realize that you can go back to v 323 00:11:07,720 --> 00:11:10,080 20 or v 19 and reload the pre 324 00:11:10,200 --> 00:11:11,100 previous project. 325 00:11:11,559 --> 00:11:13,240 So you can see that the demo project 326 00:11:13,240 --> 00:11:15,019 that I actually opened was a v 19 327 00:11:15,320 --> 00:11:16,940 with a 3.1 firmware, 328 00:11:17,879 --> 00:11:19,179 update two of the HMI. 329 00:11:19,754 --> 00:11:21,035 And as soon as I opened it in 330 00:11:21,035 --> 00:11:23,215 b 20, it's put an underscore b 20. 331 00:11:23,355 --> 00:11:25,514 So the v 19 project is still on 332 00:11:25,514 --> 00:11:26,254 my computer, 333 00:11:27,195 --> 00:11:28,735 and then I had this b 20. 334 00:11:29,035 --> 00:11:30,394 You know, I think we also have to 335 00:11:30,394 --> 00:11:31,375 be a little pragmatic 336 00:11:31,835 --> 00:11:32,894 about this too. 337 00:11:33,620 --> 00:11:35,940 I've, over the years, run into some, especially 338 00:11:35,940 --> 00:11:36,919 the younger engineers 339 00:11:37,299 --> 00:11:39,940 who or or technicians or electricians who 340 00:11:40,419 --> 00:11:42,179 they don't understand. Just because there's a new 341 00:11:42,179 --> 00:11:44,840 version doesn't mean you need to upgrade. Right? 342 00:11:45,235 --> 00:11:46,995 It's not like our phones and our TVs 343 00:11:46,995 --> 00:11:49,654 that are always forcing this upgrade. You know, 344 00:11:49,715 --> 00:11:52,355 production is king. Right? Uptime is king. Yeah. 345 00:11:52,355 --> 00:11:54,115 So if there's if there's not a reason 346 00:11:54,115 --> 00:11:56,274 upgrade, you don't need to. Now if you're 347 00:11:56,274 --> 00:11:58,115 building a new machine or putting in a 348 00:11:58,115 --> 00:11:59,254 new new system, 349 00:11:59,740 --> 00:12:01,180 it may make sense to use latest and 350 00:12:01,180 --> 00:12:02,700 greatest, or it may make sense to match 351 00:12:02,700 --> 00:12:04,700 it with what you already have installed. But 352 00:12:04,700 --> 00:12:06,059 I just, you know, I think all the 353 00:12:06,059 --> 00:12:07,820 listeners probably know this too. They'll agree with 354 00:12:07,820 --> 00:12:10,540 me. Prag be pragmatic about the upgrades. You 355 00:12:10,540 --> 00:12:11,899 know? If there's a new feature you have 356 00:12:11,899 --> 00:12:12,800 to have, great. 357 00:12:13,125 --> 00:12:14,804 But, you know, if the system's running and 358 00:12:14,804 --> 00:12:16,804 making money for the company and paying your 359 00:12:16,804 --> 00:12:19,365 paycheck, you know, think twice before upgrading it. 360 00:12:19,365 --> 00:12:20,884 You know, why are we doing this? What's 361 00:12:20,884 --> 00:12:23,125 the what's the practical reason for doing the 362 00:12:23,125 --> 00:12:23,625 upgrade? 363 00:12:24,004 --> 00:12:26,404 Right. The the other thing that I I 364 00:12:26,404 --> 00:12:28,004 had a conversation the other day is there's 365 00:12:28,004 --> 00:12:30,220 two types of people. I'm the type that 366 00:12:30,220 --> 00:12:31,120 will do it, 367 00:12:31,740 --> 00:12:34,700 through a process and and test one step 368 00:12:34,700 --> 00:12:37,200 at a time because I wanna know exactly 369 00:12:37,259 --> 00:12:39,740 where there's a problem. There's other the other 370 00:12:39,740 --> 00:12:41,980 guy, he's gonna have the attitude it should 371 00:12:41,980 --> 00:12:44,584 work. I'm gonna do it all. And if 372 00:12:44,584 --> 00:12:46,264 it doesn't work, then I'm gonna go complain 373 00:12:46,264 --> 00:12:47,004 to the vendor 374 00:12:48,345 --> 00:12:50,044 and go post things on Reddit, 375 00:12:50,664 --> 00:12:51,725 that it didn't work. 376 00:12:52,584 --> 00:12:55,429 And my attitude is that when I get 377 00:12:55,429 --> 00:12:57,610 that guide, then I try to back them, 378 00:12:57,830 --> 00:12:59,269 hey. You gotta go step by step so 379 00:12:59,269 --> 00:13:00,170 that we know 380 00:13:01,029 --> 00:13:03,110 where and what device is the problem, and 381 00:13:03,110 --> 00:13:05,190 and you gotta be reasonable about the concept 382 00:13:05,190 --> 00:13:06,889 of being, like you said, pragmatic 383 00:13:09,004 --> 00:13:09,076 about it. And you have to think about 384 00:13:09,085 --> 00:13:11,404 it's not just your computer. It's everybody else 385 00:13:11,404 --> 00:13:13,325 who's gonna be working on this machine as 386 00:13:13,325 --> 00:13:13,825 well. 387 00:13:14,205 --> 00:13:15,884 So, typically, you you know, some of the 388 00:13:15,884 --> 00:13:17,485 the listeners, they're in an island. They're the 389 00:13:17,485 --> 00:13:19,350 only one who's working on these systems. But 390 00:13:19,350 --> 00:13:20,089 some of them 391 00:13:20,629 --> 00:13:22,629 have colleagues who all their computers will also 392 00:13:22,629 --> 00:13:24,950 need to be updated as well. So you 393 00:13:24,950 --> 00:13:26,309 don't you don't wanna and I've seen that 394 00:13:26,309 --> 00:13:27,829 many times, and it causes a lot of, 395 00:13:28,070 --> 00:13:30,709 consternation in the plant when somebody doesn't upgrade 396 00:13:30,709 --> 00:13:32,789 it. Now everybody has to update their laptops 397 00:13:32,789 --> 00:13:34,804 because they don't have the right, you know, 398 00:13:34,804 --> 00:13:36,884 the software installed, the newest software installed. So 399 00:13:36,884 --> 00:13:38,904 let me turn it back to you. Exactly. 400 00:13:38,964 --> 00:13:39,464 Yep. 401 00:13:40,485 --> 00:13:40,964 So, 402 00:13:41,365 --> 00:13:42,725 what I'm gonna try to do, 403 00:13:43,205 --> 00:13:43,705 is, 404 00:13:44,404 --> 00:13:47,059 take this running system and just update it 405 00:13:47,059 --> 00:13:50,500 from, v 20 project to a v 21 406 00:13:50,500 --> 00:13:51,000 project 407 00:13:51,460 --> 00:13:52,019 and then, 408 00:13:53,059 --> 00:13:54,040 update the device 409 00:13:54,419 --> 00:13:56,899 of the PLC for now and then update 410 00:13:56,899 --> 00:13:59,620 the instruction set. So it'll be a multiple 411 00:13:59,620 --> 00:14:00,440 step project. 412 00:14:00,875 --> 00:14:03,214 But he you can see here's my simulation 413 00:14:03,995 --> 00:14:05,274 of my HMI that was 414 00:14:05,995 --> 00:14:08,714 this is actually a simulation of my v 415 00:14:08,714 --> 00:14:10,735 19 project running in v 20. 416 00:14:11,195 --> 00:14:13,195 I migrated it to v 20, but I 417 00:14:13,195 --> 00:14:14,575 didn't really change anything 418 00:14:14,955 --> 00:14:17,509 in it other than, you know, underscore v 419 00:14:17,509 --> 00:14:20,230 20. But it does run the drive and 420 00:14:20,230 --> 00:14:21,769 the little fake conveyor, 421 00:14:22,790 --> 00:14:25,190 simulation mode. So the drive is running in 422 00:14:25,190 --> 00:14:25,850 the background 423 00:14:26,389 --> 00:14:26,870 and, 424 00:14:27,269 --> 00:14:28,570 providing me that feedback. 425 00:14:28,875 --> 00:14:30,075 I don't know if you can hear that 426 00:14:30,075 --> 00:14:31,615 or not. Oh, yes. Yep. 427 00:14:32,394 --> 00:14:33,995 But the other day when I did this, 428 00:14:33,995 --> 00:14:36,554 the cool part was the HMI continued to 429 00:14:36,554 --> 00:14:37,054 function 430 00:14:37,754 --> 00:14:40,254 even after I had upgraded the PLC 431 00:14:40,634 --> 00:14:41,294 and the, 432 00:14:42,475 --> 00:14:45,549 project. So I'll I'll I'll close this project, 433 00:14:48,089 --> 00:14:49,149 save this project, 434 00:14:49,690 --> 00:14:51,850 because I wanna use this exact project that 435 00:14:51,850 --> 00:14:53,230 I had, all the green checkboxes. 436 00:14:54,409 --> 00:14:54,730 And, 437 00:14:55,615 --> 00:14:56,915 I'll close this because, 438 00:14:57,615 --> 00:14:59,615 I'm gonna migrate this one if I could 439 00:14:59,615 --> 00:15:01,235 find it. This will take a second. 440 00:15:05,695 --> 00:15:06,195 Cool. 441 00:15:07,470 --> 00:15:10,029 And then the cool thing is after my 442 00:15:10,029 --> 00:15:12,129 project is closed, I still just 443 00:15:12,589 --> 00:15:14,669 I can use the online accessible devices to 444 00:15:14,669 --> 00:15:16,189 see all the devices that I have on 445 00:15:16,189 --> 00:15:18,610 my network. I have three or four POCs, 446 00:15:18,829 --> 00:15:20,595 couple HMIs, a couple drives. 447 00:15:21,074 --> 00:15:22,115 So I can go in here and pick 448 00:15:22,115 --> 00:15:23,794 each one of these, and I can actually 449 00:15:23,794 --> 00:15:24,934 do the firmware update, 450 00:15:25,394 --> 00:15:26,134 through this 451 00:15:26,754 --> 00:15:29,875 online access with this tool right here, about 452 00:15:29,875 --> 00:15:30,934 a project open. 453 00:15:31,954 --> 00:15:33,574 But I do have my v 20 454 00:15:34,754 --> 00:15:35,850 project open. 455 00:15:36,389 --> 00:15:37,429 And here's, 456 00:15:39,830 --> 00:15:42,230 while we I was looking at it earlier 457 00:15:42,230 --> 00:15:44,730 today. This is my g two fifteen hundred, 458 00:15:45,190 --> 00:15:47,429 g two twelve hundred. I went in here 459 00:15:47,429 --> 00:15:49,975 just to get ready to upgrade the firmware. 460 00:15:49,975 --> 00:15:51,175 I'm not gonna do it right now because 461 00:15:51,175 --> 00:15:52,134 it takes a minute. 462 00:15:52,535 --> 00:15:53,915 But I downloaded 463 00:15:54,535 --> 00:15:56,235 from the support site, 464 00:15:56,615 --> 00:15:58,535 the four point o for this g two 465 00:15:58,535 --> 00:16:00,120 PLC. It was released this week. 466 00:16:00,919 --> 00:16:02,379 I browse to the file, 467 00:16:03,000 --> 00:16:04,679 so I could do the update, and then 468 00:16:04,679 --> 00:16:06,600 I click on this, and then it'll update 469 00:16:06,600 --> 00:16:07,259 the PLC. 470 00:16:08,200 --> 00:16:09,879 But I I I'm not gonna do an 471 00:16:09,879 --> 00:16:11,399 update today. I don't I don't think I 472 00:16:11,399 --> 00:16:12,679 don't think we need to do that because 473 00:16:12,679 --> 00:16:15,934 that's something that I think, we can deal 474 00:16:15,934 --> 00:16:18,334 with another time. But let's go ahead and 475 00:16:18,334 --> 00:16:19,934 I'll see if I can find that same 476 00:16:19,934 --> 00:16:21,774 project. Give me a moment. I might have 477 00:16:21,774 --> 00:16:23,475 to edit some of this stuff out 478 00:16:24,334 --> 00:16:25,740 while I search for that 479 00:16:26,379 --> 00:16:27,440 demo project. 480 00:16:28,459 --> 00:16:31,100 So here I I've found that v 20 481 00:16:31,100 --> 00:16:31,600 project. 482 00:16:32,620 --> 00:16:34,480 It's it says a p 20. 483 00:16:36,700 --> 00:16:37,200 It's 484 00:16:37,980 --> 00:16:39,440 a underscore v 20. 485 00:16:39,875 --> 00:16:41,394 And the cool part is, 486 00:16:42,195 --> 00:16:43,254 v 21 487 00:16:44,674 --> 00:16:47,955 will make an effort to read that file 488 00:16:47,955 --> 00:16:50,455 and search what's in it. And, basically, 489 00:16:50,835 --> 00:16:51,495 it will, 490 00:16:52,195 --> 00:16:52,695 check 491 00:16:53,070 --> 00:16:53,809 to make sure 492 00:16:54,110 --> 00:16:57,250 that my v 21 installation has the components 493 00:16:58,350 --> 00:17:00,990 required to upgrade the components that are in 494 00:17:00,990 --> 00:17:01,570 the project. 495 00:17:02,429 --> 00:17:05,470 So it recognizes that I've got some step 496 00:17:05,470 --> 00:17:05,970 seven 497 00:17:06,404 --> 00:17:07,384 with some safety, 498 00:17:09,684 --> 00:17:10,345 a few, 499 00:17:11,445 --> 00:17:11,945 WinCC 500 00:17:12,325 --> 00:17:13,865 devices that exist, 501 00:17:14,325 --> 00:17:15,545 and some drives. 502 00:17:16,484 --> 00:17:18,424 So it it goes through, and it agrees 503 00:17:18,484 --> 00:17:20,025 that it it's a good 504 00:17:21,910 --> 00:17:23,609 installation of v 21, 505 00:17:23,829 --> 00:17:26,789 and then it's gonna relabel it as v 506 00:17:26,789 --> 00:17:28,250 21. So I hit upgrade, 507 00:17:29,190 --> 00:17:31,049 and then it'll go through a process. 508 00:17:32,789 --> 00:17:34,410 In in these later versions, 509 00:17:35,365 --> 00:17:37,924 v 20, v 21, there's not as many 510 00:17:37,924 --> 00:17:39,224 changes to the core, 511 00:17:40,325 --> 00:17:40,825 database 512 00:17:41,365 --> 00:17:42,184 of the devices. 513 00:17:43,605 --> 00:17:45,625 So this is not as, 514 00:17:47,045 --> 00:17:49,470 significant as it was in b 11 or 515 00:17:49,470 --> 00:17:51,490 b 12 or b 13 or b 14. 516 00:17:52,990 --> 00:17:55,150 In in the, v 18, v 19, v 517 00:17:55,150 --> 00:17:55,650 20, 518 00:17:56,670 --> 00:17:59,330 fundamentally, the core of the PLCs and HMIs 519 00:18:00,109 --> 00:18:00,850 are are 520 00:18:01,309 --> 00:18:03,644 are are staying the same, and each version 521 00:18:03,644 --> 00:18:05,884 just adds a few new features like we 522 00:18:05,884 --> 00:18:08,285 talked about during the the update of v 523 00:18:08,285 --> 00:18:09,105 21, 524 00:18:09,965 --> 00:18:11,025 on the other podcast. 525 00:18:11,884 --> 00:18:13,644 Hey, guys. Just breaking in here really quick 526 00:18:13,644 --> 00:18:15,805 to thank Siemens for sponsoring this episode so 527 00:18:15,805 --> 00:18:17,345 we could release it on all platforms. 528 00:18:17,690 --> 00:18:19,849 Really appreciate when vendors do that. And I 529 00:18:19,849 --> 00:18:21,529 want to ask you, if you're enjoying this, 530 00:18:21,529 --> 00:18:22,970 if you're finding this helpful I know I 531 00:18:22,970 --> 00:18:24,809 did. It was a great refresher for me. 532 00:18:24,809 --> 00:18:26,730 But if you're finding this helpful, please let 533 00:18:26,730 --> 00:18:29,210 Siemens know. It helps them justify coming on 534 00:18:29,210 --> 00:18:30,429 the show more often, 535 00:18:30,805 --> 00:18:33,285 and, we really appreciate them sponsoring the shows 536 00:18:33,285 --> 00:18:35,125 too so we can, you know, cover some 537 00:18:35,125 --> 00:18:37,765 of our production costs. Now if you use 538 00:18:37,765 --> 00:18:40,244 other products besides Siemens, please reach out to 539 00:18:40,244 --> 00:18:42,085 them. Tell them to contact me directly. I'd 540 00:18:42,085 --> 00:18:43,769 love to have them on the show. I 541 00:18:43,769 --> 00:18:45,369 I mean, the only caveat is it has 542 00:18:45,369 --> 00:18:46,990 to be industrial automation related, 543 00:18:47,450 --> 00:18:50,750 typically focused on automation, you know, of manufacturing 544 00:18:50,890 --> 00:18:52,029 and process industries. 545 00:18:52,490 --> 00:18:53,930 But in any case, I do get a 546 00:18:53,930 --> 00:18:56,089 lot of people from outside the industry wanting 547 00:18:56,089 --> 00:18:58,330 to come on. But, in any case, you 548 00:18:58,330 --> 00:19:00,595 know, I know there's some vendors I reached 549 00:19:00,595 --> 00:19:02,835 out reach out to every month that are, 550 00:19:02,835 --> 00:19:04,755 like, favorites of you guys, the the people 551 00:19:04,755 --> 00:19:06,515 out there in the audience, and I just 552 00:19:06,515 --> 00:19:08,214 get crickets back. So please 553 00:19:08,674 --> 00:19:10,434 let your vendors know. Say, hey. You should 554 00:19:10,434 --> 00:19:12,755 go on the automation podcast. Sean is very 555 00:19:12,755 --> 00:19:14,400 easy to work with. Just reach out to 556 00:19:14,400 --> 00:19:16,000 him. My contact info is all over the 557 00:19:16,000 --> 00:19:18,640 place. But in any case, we'd love to 558 00:19:18,640 --> 00:19:21,759 cover every vendor that you're using. And, we've 559 00:19:21,759 --> 00:19:23,600 already covered, I mean, on over a 100 560 00:19:23,600 --> 00:19:25,840 different vendors, but we wanna keep expanding it 561 00:19:25,840 --> 00:19:27,794 and get some of the previous vendors to 562 00:19:27,794 --> 00:19:29,075 come back on so we could use your 563 00:19:29,075 --> 00:19:30,914 help with that. And, just let them know 564 00:19:30,914 --> 00:19:32,914 how much you appreciate the show and how 565 00:19:32,914 --> 00:19:34,835 valuable it is to you and the work 566 00:19:34,835 --> 00:19:36,515 you do. With that said, we're ready to 567 00:19:36,515 --> 00:19:38,674 jump back into this episode and learn more 568 00:19:38,674 --> 00:19:41,474 about migrating our s seven and TIA portal 569 00:19:41,474 --> 00:19:41,974 projects. 570 00:19:42,799 --> 00:19:45,359 So, the first thing that you'll notice up 571 00:19:45,359 --> 00:19:47,619 here is there's a underscore b 21. 572 00:19:48,559 --> 00:19:50,579 Yep. And, so basically, 573 00:19:51,279 --> 00:19:52,579 it's given the database, 574 00:19:52,880 --> 00:19:53,940 the project file, 575 00:19:55,085 --> 00:19:56,065 a different unique 576 00:19:56,525 --> 00:19:57,025 identifier, 577 00:19:58,125 --> 00:19:59,825 underscore v 21, 578 00:20:00,765 --> 00:20:01,505 so that 579 00:20:02,045 --> 00:20:03,105 it's not overriding 580 00:20:03,724 --> 00:20:04,224 our 581 00:20:04,525 --> 00:20:06,845 v 20 project or even my v 19 582 00:20:06,845 --> 00:20:07,345 project. 583 00:20:07,829 --> 00:20:09,769 And then, hopefully, theoretically, 584 00:20:10,390 --> 00:20:11,049 the PLC 585 00:20:11,669 --> 00:20:12,490 still is 586 00:20:15,190 --> 00:20:15,690 consistent 587 00:20:16,309 --> 00:20:18,390 with v 20 as it was with v 588 00:20:18,390 --> 00:20:19,210 21. 589 00:20:19,474 --> 00:20:20,674 So I should get, hopefully, 590 00:20:22,355 --> 00:20:23,575 good green statuses. 591 00:20:26,275 --> 00:20:28,434 Maybe a little bit of something going on 592 00:20:28,434 --> 00:20:30,134 with the difference here that I can, 593 00:20:30,994 --> 00:20:31,494 overcome 594 00:20:32,035 --> 00:20:32,369 with 595 00:20:33,250 --> 00:20:35,089 maybe something I didn't compile in the in 596 00:20:35,089 --> 00:20:36,950 the previous version or didn't migrate 597 00:20:37,569 --> 00:20:39,190 properly in b 20 '1. But, 598 00:20:39,730 --> 00:20:40,789 you can see that, 599 00:20:41,490 --> 00:20:43,250 usually, all I get is this little, 600 00:20:43,650 --> 00:20:45,829 version indicating that there's a difference, 601 00:20:46,275 --> 00:20:47,255 And I can go 602 00:20:47,555 --> 00:20:48,055 and, 603 00:20:49,075 --> 00:20:51,394 monitor everything except for this one that some 604 00:20:51,394 --> 00:20:52,295 reason decided 605 00:20:52,595 --> 00:20:54,275 that was gonna be different, and and I 606 00:20:54,275 --> 00:20:56,195 do get that occasion. But here, I can 607 00:20:56,195 --> 00:20:58,215 monitor what's going on in my machine 608 00:21:00,200 --> 00:21:01,660 even though the the PLC 609 00:21:02,119 --> 00:21:02,940 is still, 610 00:21:03,799 --> 00:21:05,019 a v 20 project. 611 00:21:06,840 --> 00:21:09,180 So now I'm using v 21, 612 00:21:09,320 --> 00:21:11,960 the v 21 project of the v 20 613 00:21:11,960 --> 00:21:14,299 project, and I'm monitoring the PLC. 614 00:21:14,914 --> 00:21:16,054 So I can monitor 615 00:21:16,595 --> 00:21:17,255 and troubleshoot. 616 00:21:18,275 --> 00:21:20,535 So what you've done here is you've offline. 617 00:21:21,234 --> 00:21:23,095 You've opened the v 20 project 618 00:21:23,634 --> 00:21:25,875 in v 21. It converted it to b 619 00:21:25,875 --> 00:21:27,335 v v 21, 620 00:21:27,529 --> 00:21:30,009 and you immediately went online with the with 621 00:21:30,009 --> 00:21:32,089 the POC that had the v 20 project 622 00:21:32,089 --> 00:21:32,750 in it. 623 00:21:33,289 --> 00:21:35,049 And you didn't have to switch back to 624 00:21:35,049 --> 00:21:37,309 v 20. You could stay in v 21, 625 00:21:37,529 --> 00:21:40,349 and we're online. We're monitoring. We can edit 626 00:21:40,774 --> 00:21:41,994 without having to, 627 00:21:43,734 --> 00:21:44,474 you know, 628 00:21:45,095 --> 00:21:47,654 redownload a v 21 version of this program 629 00:21:47,654 --> 00:21:50,315 to the PLC. And that's really cool. Now 630 00:21:50,774 --> 00:21:52,855 is the question. If I do make an 631 00:21:52,855 --> 00:21:53,914 edit using 632 00:21:54,730 --> 00:21:55,869 v 21, 633 00:21:56,250 --> 00:21:58,569 does that now stop v 20 from getting 634 00:21:58,809 --> 00:22:01,769 connecting again and looking at it? Correct. Yep. 635 00:22:01,769 --> 00:22:04,809 Okay. So now I would decide that I'm 636 00:22:04,809 --> 00:22:06,589 ready to I've I've validated, 637 00:22:07,474 --> 00:22:09,555 that the project seems to compile in in 638 00:22:09,555 --> 00:22:11,174 b 21. 639 00:22:11,955 --> 00:22:14,755 I'm gonna go ahead and download that to 640 00:22:14,755 --> 00:22:15,414 the PLC. 641 00:22:16,355 --> 00:22:18,215 So, you know, I might do some compiles 642 00:22:18,434 --> 00:22:20,434 to make sure, you know, that it it 643 00:22:20,515 --> 00:22:21,335 it's okay 644 00:22:21,799 --> 00:22:25,259 being a a a fifteen fifteen PLC 645 00:22:25,720 --> 00:22:27,259 in a v 21 environment. 646 00:22:27,960 --> 00:22:28,460 So 647 00:22:28,759 --> 00:22:29,900 I'll run the compile 648 00:22:31,799 --> 00:22:33,980 based on v 21, 649 00:22:34,039 --> 00:22:35,099 v 21, 650 00:22:35,144 --> 00:22:36,744 And then I'll download it to the PLC, 651 00:22:36,744 --> 00:22:38,825 which is gonna download the entire hardware and 652 00:22:38,825 --> 00:22:39,325 software. 653 00:22:40,424 --> 00:22:40,924 And 654 00:22:41,305 --> 00:22:41,805 then 655 00:22:42,345 --> 00:22:42,845 I'll, 656 00:22:44,585 --> 00:22:46,345 stop the PLC. In this case, it will 657 00:22:46,345 --> 00:22:48,500 stop the PLC. And then I'll, 658 00:22:49,920 --> 00:22:51,700 put it in remote and test it. 659 00:22:53,680 --> 00:22:56,180 And the key is one one thing is 660 00:22:56,480 --> 00:22:59,200 I haven't yet updated the PLC, so v 661 00:22:59,200 --> 00:23:00,420 21 is still 662 00:23:01,884 --> 00:23:02,384 using 663 00:23:02,924 --> 00:23:05,265 the PLC in a in a 664 00:23:05,805 --> 00:23:07,265 what do you wanna say? A 665 00:23:07,964 --> 00:23:09,984 backward compatible mode where it's 666 00:23:10,525 --> 00:23:12,365 still seeing it as an older version of 667 00:23:12,365 --> 00:23:14,730 the PLC. Okay. So that's important. The PLC 668 00:23:14,730 --> 00:23:16,650 is still at version 3.1. 669 00:23:16,650 --> 00:23:17,630 Got it. Yep. 670 00:23:18,410 --> 00:23:20,570 Now this might be a step that, you 671 00:23:20,570 --> 00:23:22,490 know, you just go right ahead and, 672 00:23:23,130 --> 00:23:24,110 change the firmware 673 00:23:24,650 --> 00:23:26,090 to one of the later versions, 674 00:23:27,424 --> 00:23:29,184 and just accept the fact that it is 675 00:23:29,184 --> 00:23:30,224 a 4.1, 676 00:23:30,224 --> 00:23:32,144 or you can download. What do you wanna 677 00:23:32,144 --> 00:23:32,644 do? 678 00:23:33,105 --> 00:23:34,744 No. Let's go ahead and download. So that 679 00:23:34,865 --> 00:23:37,585 that's the firmware version of the PLC in 680 00:23:37,585 --> 00:23:38,484 the project 681 00:23:39,025 --> 00:23:41,829 Right. Which doesn't have to match because the 682 00:23:41,829 --> 00:23:43,909 hardware is backward compatible. It doesn't have to 683 00:23:43,909 --> 00:23:45,049 match. Yep. 684 00:23:46,069 --> 00:23:48,549 So it gives a nice notice here. Yep. 685 00:23:48,549 --> 00:23:50,089 It's making you check the boxes 686 00:23:50,630 --> 00:23:52,549 to make sure you know that, hey. The 687 00:23:52,549 --> 00:23:53,849 project in this 20, 688 00:23:54,154 --> 00:23:55,774 you're downloading the 21. 689 00:23:55,835 --> 00:23:57,595 You sure you wanna do this? You're upgrading 690 00:23:57,595 --> 00:23:59,294 the project in the unit. Yep. 691 00:23:59,755 --> 00:24:01,054 Good. Yeah. Very helpful. 692 00:24:01,434 --> 00:24:02,875 Yeah. So that's a it's I mean, you 693 00:24:02,875 --> 00:24:05,034 gotta expand these things and read them. Now 694 00:24:05,034 --> 00:24:06,554 the one thing that's hanging up is the 695 00:24:06,554 --> 00:24:07,855 fact that I got a 696 00:24:08,474 --> 00:24:09,454 view of things. 697 00:24:10,019 --> 00:24:12,660 Okay. Dash of y. So it wants that 698 00:24:12,660 --> 00:24:13,880 to be compiled separately. 699 00:24:14,180 --> 00:24:14,680 So 700 00:24:16,019 --> 00:24:17,619 explicit con con, 701 00:24:18,100 --> 00:24:21,320 compile the view of things application as required, 702 00:24:22,345 --> 00:24:24,505 separately from the PLC because it's a kind 703 00:24:24,505 --> 00:24:26,044 of an HMI on the PLC. 704 00:24:26,424 --> 00:24:28,184 Yep. So if I go down here to 705 00:24:28,184 --> 00:24:29,164 the web application, 706 00:24:30,024 --> 00:24:32,825 view of things, just recompile that so that 707 00:24:32,825 --> 00:24:33,325 it's 708 00:24:33,704 --> 00:24:34,204 now, 709 00:24:35,384 --> 00:24:37,529 compiled in b 21. Then I can go 710 00:24:37,529 --> 00:24:38,590 back to the PLC, 711 00:24:39,289 --> 00:24:42,350 and I should have that same preview dialogue 712 00:24:43,049 --> 00:24:44,430 without that error. 713 00:24:44,970 --> 00:24:46,490 Yeah. We did cover that when that first 714 00:24:46,490 --> 00:24:48,430 came out. It was very, very cool feature. 715 00:24:49,130 --> 00:24:50,670 Yeah. It's a nice feature. 716 00:24:52,285 --> 00:24:54,525 So now I I that one's okay. It's 717 00:24:54,525 --> 00:24:56,144 gonna download it. Again, 718 00:24:56,765 --> 00:24:59,164 it's it's giving me clear notice that because 719 00:24:59,164 --> 00:25:01,345 it's gonna download some of the hardware, 720 00:25:03,019 --> 00:25:04,399 It's gonna stop it. 721 00:25:04,940 --> 00:25:06,079 It's going to, 722 00:25:07,659 --> 00:25:08,159 upgrade 723 00:25:08,539 --> 00:25:09,039 the 724 00:25:09,579 --> 00:25:10,079 PLC 725 00:25:10,619 --> 00:25:13,200 so that it's actually running a v 21 726 00:25:13,259 --> 00:25:13,759 project 727 00:25:14,460 --> 00:25:16,460 regardless of the firmware. And then I hit 728 00:25:16,460 --> 00:25:16,960 load, 729 00:25:17,394 --> 00:25:19,414 and I see my PLC stop 730 00:25:19,795 --> 00:25:20,615 and flash 731 00:25:20,914 --> 00:25:23,154 on the display. It's indicating a download in 732 00:25:23,154 --> 00:25:23,654 progress. 733 00:25:26,035 --> 00:25:27,875 Now if you were using some of the 734 00:25:27,875 --> 00:25:30,755 new v 21 features, you'd very likely have 735 00:25:30,755 --> 00:25:32,454 to update the firmware on the PLC. 736 00:25:32,819 --> 00:25:34,899 Or in this case, your PLC's firmware is 737 00:25:34,899 --> 00:25:36,579 already upgraded, but you'd have to tell to 738 00:25:36,579 --> 00:25:39,059 unlock those new features. You'd have to change 739 00:25:39,059 --> 00:25:41,079 the version of firmware in your project 740 00:25:41,380 --> 00:25:43,859 because, as we know, version 3.1 of the 741 00:25:43,859 --> 00:25:45,940 firmware doesn't have all the bells and whistles 742 00:25:45,940 --> 00:25:49,174 that version 4.1 has. Exactly. So, yeah. 743 00:25:50,755 --> 00:25:52,295 I I just went to the 744 00:25:52,835 --> 00:25:54,934 push buttons and reset my safety, 745 00:25:55,795 --> 00:25:56,295 and, 746 00:25:56,674 --> 00:25:57,894 the cool part is 747 00:25:58,434 --> 00:25:59,654 my machine is running. 748 00:26:01,554 --> 00:26:02,054 So 749 00:26:02,609 --> 00:26:05,109 I'm I'm I migrated the v 21, 750 00:26:05,329 --> 00:26:07,430 but I I I I can and maintained 751 00:26:07,650 --> 00:26:08,710 a safe threshold 752 00:26:09,089 --> 00:26:11,029 of not changing the PLC yet, 753 00:26:12,450 --> 00:26:13,589 just to make sure, 754 00:26:14,930 --> 00:26:15,404 that, 755 00:26:15,965 --> 00:26:18,365 the v 21 didn't upset the Apple card 756 00:26:18,365 --> 00:26:19,664 and and change anything. 757 00:26:20,684 --> 00:26:23,265 So then the next step is, okay, let's 758 00:26:23,325 --> 00:26:23,825 embrace 759 00:26:24,845 --> 00:26:26,945 changing the device to the new firmware. 760 00:26:31,500 --> 00:26:34,080 So now I can go here to, properties, 761 00:26:36,620 --> 00:26:38,080 change firmware revision, 762 00:26:39,980 --> 00:26:42,320 and it it right away recognizes 763 00:26:42,620 --> 00:26:43,484 what's the latest. 764 00:26:44,045 --> 00:26:44,545 Mhmm. 765 00:26:45,804 --> 00:26:47,884 So it when I do it down there, 766 00:26:47,884 --> 00:26:50,125 it basically comes up and it gives me 767 00:26:50,125 --> 00:26:52,545 an indication that, okay. This part number 768 00:26:53,005 --> 00:26:54,545 0303, 769 00:26:55,484 --> 00:26:58,045 does have a couple other options beyond the 770 00:26:58,045 --> 00:26:58,980 3.1. 771 00:26:59,220 --> 00:27:01,140 I mean, I could even if something was 772 00:27:01,140 --> 00:27:03,619 wrong, go back. But I I wanna go 773 00:27:03,619 --> 00:27:05,079 forward because I trust Siemens. 774 00:27:05,619 --> 00:27:07,400 Been here long enough that I know. 775 00:27:08,579 --> 00:27:10,500 So now this is the part where I 776 00:27:10,500 --> 00:27:12,019 say, okay. My now I'm gonna make my 777 00:27:12,019 --> 00:27:14,945 PLC a 4.1 778 00:27:14,945 --> 00:27:15,445 firmware. 779 00:27:15,745 --> 00:27:18,225 And, basically, now it's taking advantage of all 780 00:27:18,225 --> 00:27:20,884 the new features and functionalities and security 781 00:27:21,184 --> 00:27:22,404 benefits of the new, 782 00:27:22,705 --> 00:27:23,684 1,500. 783 00:27:23,985 --> 00:27:26,884 Again, you'll wanna you'll wanna select the PLC. 784 00:27:27,650 --> 00:27:29,730 If I select this and do compile, it's 785 00:27:29,730 --> 00:27:32,390 gonna compile a software part of the PLC. 786 00:27:32,690 --> 00:27:34,130 I like to go up here and set 787 00:27:34,130 --> 00:27:34,869 my context 788 00:27:35,409 --> 00:27:37,809 to the hardware and the software, and then 789 00:27:37,809 --> 00:27:39,029 I just hit this compile. 790 00:27:41,825 --> 00:27:43,845 Yep. Yeah. If you had a big project, 791 00:27:43,904 --> 00:27:45,904 it may make sense if you've only changed, 792 00:27:45,904 --> 00:27:48,244 like, let's say, a data block. Just recompile 793 00:27:48,304 --> 00:27:50,384 that data block. Right? But, you know, that 794 00:27:50,384 --> 00:27:51,765 may affect other other, 795 00:27:52,304 --> 00:27:54,144 you know, like the main OB or other 796 00:27:54,144 --> 00:27:56,440 blocks. So, you know, if you're if you 797 00:27:56,440 --> 00:27:57,099 just wanna 798 00:27:57,559 --> 00:27:59,579 download, just compile the whole thing. 799 00:28:00,359 --> 00:28:00,859 Yep. 800 00:28:03,000 --> 00:28:05,159 Honestly, when you do the download, it's doing 801 00:28:05,159 --> 00:28:06,380 a compile. Mhmm. 802 00:28:07,319 --> 00:28:07,819 But 803 00:28:08,565 --> 00:28:11,144 sometimes it's frustrating to get to this download 804 00:28:11,204 --> 00:28:12,085 dialogue and, 805 00:28:12,884 --> 00:28:15,605 get forward. Yep. Yeah. I think we I 806 00:28:15,605 --> 00:28:17,284 have to go back. So, again, it it's 807 00:28:17,284 --> 00:28:18,884 gonna come up and it's gonna say, hey. 808 00:28:18,884 --> 00:28:20,404 It's gonna reset it because, 809 00:28:21,605 --> 00:28:23,759 because we're making such a drastic change. 810 00:28:25,119 --> 00:28:27,279 I, it's gonna stop it. So in case 811 00:28:27,279 --> 00:28:29,119 I'm still running the machine, I would go 812 00:28:29,119 --> 00:28:29,859 to the HMI. 813 00:28:33,599 --> 00:28:35,759 It's gonna update some of the safety features 814 00:28:35,759 --> 00:28:38,964 because that changed in the web app. So 815 00:28:38,964 --> 00:28:42,025 I like this preview dialogue download. For me, 816 00:28:42,085 --> 00:28:44,644 it's it's like a little stethoscope that gives 817 00:28:44,644 --> 00:28:46,025 me all the details of, 818 00:28:46,805 --> 00:28:48,664 the health of my 819 00:28:49,289 --> 00:28:52,090 online device and what is gonna happen to 820 00:28:52,090 --> 00:28:53,070 it once, 821 00:28:53,850 --> 00:28:55,070 this download happens. 822 00:28:56,570 --> 00:28:58,009 Yeah. Back to what we were just talking 823 00:28:58,009 --> 00:28:59,529 about. If you've made a lot of changes 824 00:28:59,529 --> 00:29:00,269 to the program, 825 00:29:00,650 --> 00:29:02,410 do a compile. If you made some minor 826 00:29:02,410 --> 00:29:02,910 changes, 827 00:29:03,404 --> 00:29:05,725 likely the download's gonna do compile, and you're 828 00:29:05,725 --> 00:29:07,404 gonna be able to go forward. But, yeah, 829 00:29:07,404 --> 00:29:09,125 it does get frustrating to have it when 830 00:29:09,125 --> 00:29:10,445 you go to do a download, to have 831 00:29:10,445 --> 00:29:11,805 it bring up to the download window and 832 00:29:11,805 --> 00:29:14,205 say, oh, something didn't compile. For me, it's 833 00:29:14,205 --> 00:29:16,765 usually I forget to disable the password because 834 00:29:16,765 --> 00:29:18,900 I'm just working on the test bench, so 835 00:29:18,900 --> 00:29:20,820 I don't need the password. It's like, ugh. 836 00:29:20,820 --> 00:29:22,420 Now I gotta close that. I gotta go 837 00:29:22,420 --> 00:29:24,500 all the way down. So doing the compile 838 00:29:24,500 --> 00:29:26,440 first. And I think as people use it, 839 00:29:26,660 --> 00:29:28,660 they know, you know, what what when should 840 00:29:28,660 --> 00:29:30,820 I compile it before I download, or when 841 00:29:30,820 --> 00:29:32,259 can I just go right to download because 842 00:29:32,259 --> 00:29:34,279 there's a low risk of having any issues? 843 00:29:34,934 --> 00:29:35,434 Yep. 844 00:29:36,214 --> 00:29:38,934 So it's it's downloaded, and then now it's 845 00:29:38,934 --> 00:29:40,794 updated to the matching firmware. 846 00:29:41,654 --> 00:29:43,174 And I and I walk over here and 847 00:29:43,174 --> 00:29:44,315 hit my little safety 848 00:29:44,934 --> 00:29:45,434 reasimulate 849 00:29:46,214 --> 00:29:48,075 and validate the safety functions, 850 00:29:48,694 --> 00:29:49,230 and it's, 851 00:29:49,710 --> 00:29:50,849 back up and running. 852 00:29:51,630 --> 00:29:53,710 And, the cool part is my machine is 853 00:29:53,710 --> 00:29:54,529 up and running. 854 00:29:56,109 --> 00:29:57,549 And now you can take advantage of all 855 00:29:57,549 --> 00:29:59,809 the new features we talked about in the 856 00:30:00,029 --> 00:30:02,429 previous episode because you have everything updated to 857 00:30:02,429 --> 00:30:03,434 the latest and greatest. 858 00:30:06,154 --> 00:30:06,975 Yep. Yep. 859 00:30:08,075 --> 00:30:10,075 So for people used to working with other 860 00:30:10,075 --> 00:30:11,535 brands, this may be 861 00:30:12,075 --> 00:30:14,654 quite different. You know, there's no lockstep here. 862 00:30:14,715 --> 00:30:17,115 You have the independence like we did in 863 00:30:17,115 --> 00:30:18,495 in with with older, 864 00:30:18,980 --> 00:30:19,480 POCs. 865 00:30:20,180 --> 00:30:21,539 We still have that with the latest and 866 00:30:21,539 --> 00:30:24,820 greatest from Siemens, that independence between the firmware 867 00:30:24,820 --> 00:30:26,680 version, the version of the software, 868 00:30:27,220 --> 00:30:29,240 the version of the firmware in the software. 869 00:30:29,619 --> 00:30:31,299 Again, if you wanna use all the latest 870 00:30:31,299 --> 00:30:32,500 features, you're gonna have to go to the 871 00:30:32,500 --> 00:30:34,855 newest firmware and the newest software. But if 872 00:30:34,855 --> 00:30:36,855 you're just maintaining a system, then you have 873 00:30:36,855 --> 00:30:38,855 a lot of options here. You don't have 874 00:30:38,855 --> 00:30:41,414 to, you know, automatically upgrade the firmware or 875 00:30:41,414 --> 00:30:42,075 the software 876 00:30:42,534 --> 00:30:44,075 to continue to maintain it. 877 00:30:44,855 --> 00:30:47,640 Yeah. And and the one thing that that, 878 00:30:47,799 --> 00:30:49,640 you know, different from what I have in 879 00:30:49,640 --> 00:30:51,640 my little workshop here and you have there 880 00:30:51,640 --> 00:30:54,599 in the lab is our customers have huge 881 00:30:54,599 --> 00:30:56,039 systems. Way Oh, yeah. 882 00:30:56,519 --> 00:30:57,339 Third party 883 00:30:58,839 --> 00:30:59,339 devices 884 00:30:59,640 --> 00:31:01,740 and and robots and interfaces 885 00:31:02,039 --> 00:31:02,779 and drives. 886 00:31:04,965 --> 00:31:07,045 And you you have to take into the 887 00:31:07,045 --> 00:31:07,545 consideration 888 00:31:07,845 --> 00:31:08,345 that 889 00:31:08,965 --> 00:31:11,205 when you make this change to the the 890 00:31:11,205 --> 00:31:12,585 main device of the PLC, 891 00:31:13,125 --> 00:31:15,465 you're you're gonna have to validate that it 892 00:31:15,919 --> 00:31:18,559 maintains the communication and the connectivity to all 893 00:31:18,559 --> 00:31:20,720 the other components that are in there. So 894 00:31:20,720 --> 00:31:23,140 that's what's nice about this process, lockstep. 895 00:31:24,240 --> 00:31:26,960 If in this last step that the 4.1 896 00:31:26,960 --> 00:31:28,819 firmware in in the project 897 00:31:29,595 --> 00:31:30,815 of v 21 898 00:31:32,154 --> 00:31:34,335 created a situation with one of my interfaces, 899 00:31:34,394 --> 00:31:35,214 I could backtrack. 900 00:31:35,835 --> 00:31:36,335 Yep. 901 00:31:37,194 --> 00:31:39,035 You have to remain calm and you have 902 00:31:39,035 --> 00:31:40,894 to be be pragmatic 903 00:31:41,434 --> 00:31:43,539 about what steps would I go back to 904 00:31:43,539 --> 00:31:44,119 to determine, 905 00:31:44,899 --> 00:31:46,039 how do I get my 906 00:31:46,339 --> 00:31:48,819 confidence back to the because that ultimately, you 907 00:31:48,819 --> 00:31:50,339 know, what we want, we want the machine 908 00:31:50,339 --> 00:31:53,059 to be running for the management people there. 909 00:31:53,059 --> 00:31:54,434 So it's it's kinda creepy. 910 00:31:55,154 --> 00:31:56,914 Yeah. And and I I've done that too 911 00:31:56,914 --> 00:31:58,674 where I'll I'll be trying a new feature, 912 00:31:58,674 --> 00:32:00,115 you know, working with you and Lewis and 913 00:32:00,115 --> 00:32:01,975 the other team the people on your team, 914 00:32:02,035 --> 00:32:03,154 but then I have to go back and 915 00:32:03,154 --> 00:32:04,674 add a lesson to one of my courses 916 00:32:04,674 --> 00:32:07,255 that's using an existing, you know, previous version. 917 00:32:07,549 --> 00:32:10,450 And so I'll I'll downgrade the the controller. 918 00:32:10,589 --> 00:32:12,750 I'll, you know, open up the VM just 919 00:32:12,750 --> 00:32:14,190 for that class, and I'll use the older 920 00:32:14,190 --> 00:32:15,890 version. It's nice to have that independence 921 00:32:16,269 --> 00:32:17,970 to be able to go forward and backward 922 00:32:18,269 --> 00:32:20,109 and be able to use, you know, the 923 00:32:20,109 --> 00:32:21,789 newest software with the older firm was and 924 00:32:21,789 --> 00:32:23,009 vice versa. So, 925 00:32:23,585 --> 00:32:25,345 I think that's just it's so flexible, and 926 00:32:25,345 --> 00:32:27,904 it's kinda reminiscent of how other people used 927 00:32:27,904 --> 00:32:29,585 to do it years ago. But, you know, 928 00:32:29,585 --> 00:32:31,585 it's good that Siemens has, kept that. And 929 00:32:31,585 --> 00:32:33,045 I would like to know for the audience, 930 00:32:33,505 --> 00:32:35,424 what do you think? I mean, those of 931 00:32:35,424 --> 00:32:36,945 you using this in the field, have you 932 00:32:36,945 --> 00:32:39,210 found any or you have any questions that 933 00:32:39,210 --> 00:32:41,210 maybe John and I can answer? And for 934 00:32:41,210 --> 00:32:43,390 those of you using non Siemens products, 935 00:32:44,250 --> 00:32:46,029 what do you think? Is this more flexible 936 00:32:46,170 --> 00:32:47,849 or more confusing for you? I'd love to 937 00:32:47,849 --> 00:32:49,309 hear you guys' thoughts in the comments. 938 00:32:50,734 --> 00:32:52,654 So there's two more things that I I 939 00:32:52,654 --> 00:32:53,215 can do here. 940 00:32:54,015 --> 00:32:55,695 So I I just wanna, you know, give 941 00:32:55,695 --> 00:32:57,775 everybody a moment to, you know, digest all 942 00:32:57,775 --> 00:32:59,634 the things that we've kinda covered so far. 943 00:33:00,255 --> 00:33:02,654 But the the final thing is the actual 944 00:33:02,654 --> 00:33:03,715 instruction set 945 00:33:04,710 --> 00:33:07,529 also has a version on the instruction set 946 00:33:07,829 --> 00:33:09,529 that resides within the PLC. 947 00:33:10,390 --> 00:33:13,589 So these these instruction sets that are in 948 00:33:13,589 --> 00:33:14,250 in the 949 00:33:15,829 --> 00:33:17,769 configuration of the PLC also 950 00:33:18,494 --> 00:33:20,515 have a a version to them. 951 00:33:20,974 --> 00:33:21,474 And, 952 00:33:22,894 --> 00:33:25,055 some of them get updated with e with 953 00:33:25,055 --> 00:33:27,714 with each release for bug fixes or whatever. 954 00:33:27,855 --> 00:33:29,634 So there's one final step 955 00:33:30,109 --> 00:33:31,809 that a lot of people miss 956 00:33:32,509 --> 00:33:34,670 is, you know, and upgrade the program up 957 00:33:34,830 --> 00:33:37,009 upgrade the program in in star systems. 958 00:33:37,390 --> 00:33:39,250 So this will basically 959 00:33:39,710 --> 00:33:41,650 look through any counter 960 00:33:42,029 --> 00:33:43,650 or motion or move instructions 961 00:33:44,204 --> 00:33:45,825 that might have been fixed or 962 00:33:46,444 --> 00:33:48,845 or or updated in in the v 21. 963 00:33:48,845 --> 00:33:49,904 And it will basically, 964 00:33:51,644 --> 00:33:52,144 update 965 00:33:52,605 --> 00:33:53,345 the reference 966 00:33:53,964 --> 00:33:55,904 instructions that are used for the project 967 00:33:56,605 --> 00:33:57,105 and, 968 00:33:57,970 --> 00:33:59,990 fix any bugs that might have been identified 969 00:34:00,210 --> 00:34:02,610 from v 20 to v 21. 970 00:34:02,930 --> 00:34:05,110 So that so then that would be another 971 00:34:05,250 --> 00:34:07,430 step that is kind of required. 972 00:34:08,849 --> 00:34:10,289 And you can see, you know, it looks 973 00:34:10,289 --> 00:34:12,050 like there's some safety stuff and some other 974 00:34:12,050 --> 00:34:14,105 stuff that kinda got updated 975 00:34:14,804 --> 00:34:16,264 in the instruction sets. 976 00:34:17,204 --> 00:34:19,525 So that would be one more final little 977 00:34:19,525 --> 00:34:21,065 download to get myself 978 00:34:21,445 --> 00:34:24,485 completely up to and, again, you don't have 979 00:34:24,485 --> 00:34:26,664 to do that upgrade program if your instruction 980 00:34:26,724 --> 00:34:28,344 set works for the running machine. 981 00:34:29,030 --> 00:34:30,789 It's just I I I like people to 982 00:34:30,789 --> 00:34:32,469 understand that if you were to start a 983 00:34:32,469 --> 00:34:35,030 new project with this PLC and use the 984 00:34:35,030 --> 00:34:36,409 latest and greatest stuff, 985 00:34:36,949 --> 00:34:38,489 that's where we would be at. 986 00:34:38,789 --> 00:34:40,469 This time, I'll see if I can actually 987 00:34:40,469 --> 00:34:41,609 download that with 988 00:34:43,109 --> 00:34:43,769 the software 989 00:34:44,614 --> 00:34:47,014 since it didn't look like it showed up 990 00:34:47,014 --> 00:34:48,875 as, anything in the hardware. 991 00:34:50,295 --> 00:34:52,135 But it it is gonna because I think 992 00:34:52,135 --> 00:34:54,534 there's some motion stuff. But, basically, yeah, now 993 00:34:54,534 --> 00:34:57,094 it it it'll do a reload of some 994 00:34:57,094 --> 00:34:58,554 of the hard hardware configuration 995 00:34:58,980 --> 00:35:00,679 stuff that's related to the instructions, 996 00:35:01,300 --> 00:35:03,460 but that's the final little update for the 997 00:35:03,460 --> 00:35:03,960 PLC. 998 00:35:05,139 --> 00:35:05,639 Cool. 999 00:35:06,420 --> 00:35:08,340 Yeah. So that if you have an older 1000 00:35:08,340 --> 00:35:10,420 system and it operates a little differently, the 1001 00:35:10,420 --> 00:35:12,199 instruction operates a little differently 1002 00:35:12,575 --> 00:35:14,335 than the latest system, that's something to keep 1003 00:35:14,335 --> 00:35:16,175 in mind that, you know, we're not it's 1004 00:35:16,175 --> 00:35:18,755 not only firmware, it's the instructions as well. 1005 00:35:19,055 --> 00:35:21,375 And, so keep that in mind. That's part 1006 00:35:21,375 --> 00:35:24,015 of, you know, what all these industrial automation 1007 00:35:24,015 --> 00:35:26,015 vendors do is in testing their products as 1008 00:35:26,015 --> 00:35:27,315 they're updating that stuff. 1009 00:35:28,015 --> 00:35:28,349 Yep. 1010 00:35:29,710 --> 00:35:33,309 So I I think it's it's to me, 1011 00:35:33,309 --> 00:35:35,630 coming from the other vendor and doing things 1012 00:35:35,630 --> 00:35:37,390 the other ways and some of the other 1013 00:35:37,390 --> 00:35:39,170 stuff that I've struggled with the past, 1014 00:35:39,710 --> 00:35:41,410 I I really appreciate 1015 00:35:41,710 --> 00:35:43,890 the the the concept of this flexibility. 1016 00:35:44,804 --> 00:35:46,824 And, again, I haven't even updated the HMI. 1017 00:35:46,885 --> 00:35:48,184 My HMI is still 1018 00:35:48,804 --> 00:35:49,625 a image 1019 00:35:50,005 --> 00:35:51,065 that is a 1020 00:35:53,125 --> 00:35:54,824 v 19 update two, 1021 00:35:55,605 --> 00:35:57,684 in the project here. So this little HMI 1022 00:35:57,684 --> 00:35:58,440 device is, 1023 00:35:58,920 --> 00:35:59,420 still 1024 00:35:59,960 --> 00:36:02,920 the v 19 version. My actual HMI hardware 1025 00:36:02,920 --> 00:36:04,300 is a v 20 image, 1026 00:36:05,239 --> 00:36:07,639 and it's got a v 21 project that's 1027 00:36:07,639 --> 00:36:08,859 running in there. So, 1028 00:36:10,519 --> 00:36:12,199 to me, you know, I like the fact 1029 00:36:12,199 --> 00:36:13,800 that I can focus on one thing at 1030 00:36:13,800 --> 00:36:14,994 a time, like the PLC, 1031 00:36:15,855 --> 00:36:17,074 and the motion control. 1032 00:36:17,375 --> 00:36:18,035 And then 1033 00:36:18,494 --> 00:36:20,574 in a couple weeks, once I have all 1034 00:36:20,574 --> 00:36:22,015 the confidence in the world of this, then 1035 00:36:22,015 --> 00:36:23,235 I can tackle the HMO 1036 00:36:23,695 --> 00:36:24,675 as a whole part. 1037 00:36:25,454 --> 00:36:25,954 Absolutely. 1038 00:36:28,019 --> 00:36:29,380 So I think that was an excellent to 1039 00:36:29,380 --> 00:36:30,659 run through that. I mean, it was a 1040 00:36:30,659 --> 00:36:32,340 great refresher for me, and I hope everybody 1041 00:36:32,340 --> 00:36:33,940 who's watching, I thought thought it was a 1042 00:36:33,940 --> 00:36:35,940 good refresher, or maybe you learned something new 1043 00:36:35,940 --> 00:36:37,460 if you're not if you're not using Siemens 1044 00:36:37,460 --> 00:36:38,340 yet. But, 1045 00:36:38,980 --> 00:36:40,659 John, I really appreciate coming on and going 1046 00:36:40,659 --> 00:36:42,260 over that. Was there anything else you wanted 1047 00:36:42,260 --> 00:36:44,474 to cover before we end the show? No. 1048 00:36:44,474 --> 00:36:46,474 I I think that was the key is 1049 00:36:46,474 --> 00:36:48,174 is is the highlight of that. 1050 00:36:48,634 --> 00:36:50,714 There's there's some slides that are that explain 1051 00:36:50,714 --> 00:36:52,574 some of the stuff in the in the, 1052 00:36:53,114 --> 00:36:54,954 links to the other update that I'm gonna 1053 00:36:54,954 --> 00:36:56,714 give you. But I think this is the 1054 00:36:56,714 --> 00:36:58,750 most important part is to to have this 1055 00:36:58,750 --> 00:37:00,430 available as a little tech tip that you 1056 00:37:00,430 --> 00:37:01,090 can show. 1057 00:37:01,390 --> 00:37:03,470 Excellent. Well, I appreciate coming back on, John. 1058 00:37:03,470 --> 00:37:05,010 Really do. Absolutely. 1059 00:37:06,110 --> 00:37:07,789 I hope you guys enjoyed that episode. I 1060 00:37:07,789 --> 00:37:09,470 know I did. That was a great refresher 1061 00:37:09,470 --> 00:37:10,829 for me. I haven't touched some of that 1062 00:37:10,829 --> 00:37:12,855 stuff in a while, and I really appreciate 1063 00:37:12,914 --> 00:37:14,755 John coming on. He's actually coming back on 1064 00:37:14,755 --> 00:37:16,434 to show me how to upgrade my licenses, 1065 00:37:16,434 --> 00:37:17,715 which I'm gonna share to you as a 1066 00:37:17,715 --> 00:37:19,474 tech tip. So that'll be pretty cool to 1067 00:37:19,474 --> 00:37:21,795 do as well. But, I do wanna thank 1068 00:37:21,795 --> 00:37:22,755 Siemens for, 1069 00:37:23,075 --> 00:37:25,315 sponsoring this episode, coming on the show, bringing 1070 00:37:25,315 --> 00:37:27,210 us up to speed. I also wanna thank 1071 00:37:27,210 --> 00:37:29,369 you, the audience, for tuning in. There would 1072 00:37:29,369 --> 00:37:30,969 be no reason to have a show if 1073 00:37:30,969 --> 00:37:32,730 you guys weren't interested in this kind of 1074 00:37:32,730 --> 00:37:34,489 stuff. So thank you for tuning in. I 1075 00:37:34,489 --> 00:37:36,409 do wanna wish you all good health and 1076 00:37:36,409 --> 00:37:36,909 happiness. 1077 00:37:37,369 --> 00:37:38,989 And until next time, my friends, 1078 00:37:39,849 --> 00:37:40,349 peace.