Podcasts about Modbus

This week Shawn Tierney meets up with Maria Santella and Robert Murao of ICP DAS USA to learn about their new Modbus RTU, TCP, and other products in this episode of #TheAutomationPodcast. For any links related to this episode, check out the “Show Notes” located below the video. Watch The Automation Podcast from The Automation Blog: Listen to The Automation Podcast from The Automation Blog: The Automation Podcast, Episode 274 Show Notes: Special thanks to Maria and Robert for coming on the show, and to ICP DAS USA for sponsoring this episode. To learn more about these products, please see the below links: Modbus Gateways  Modbus Touch Screen Controllers   Modbus RTU DAQ Serial Port Sharing Devices  Modbus over Cellular Until next time, Peace ✌️ If you enjoyed this content, please give it a Like, and consider Sharing a link to it as that is the best way for us to grow our audience, which in turn allows us to produce more content

Alejandro Cabrera Muñoz, co-founder and CEO of Green Eagle Solutions, returns to discuss automating 70 GW of renewable assets and why operators are self-operating their fleets. Reach out to sales@greeneaglesolutions.com to learn more! Sign up now for Uptime Tech News, our weekly newsletter on all things wind technology. This episode is sponsored by Weather Guard Lightning Tech. Learn more about Weather Guard’s StrikeTape Wind Turbine LPS retrofit. Follow the show on YouTube, Linkedin and visit Weather Guard on the web. And subscribe to Rosemary’s “Engineering with Rosie” YouTube channel here. Have a question we can answer on the show? Email us! Welcome to Uptime Spotlight, shining light on wind energy’s brightest innovators. This is the progress powering tomorrow Allen Hall: Alejandro, welcome back to the program.  Alejandro Cabrera Muños: Thank you so much, Allen. It’s a pleasure to be here.  Allen Hall: Well, so last time we talked, you had so much happening at Green Eagle, and it is, uh, amazing to watch the progress there. You’ve been around for quite a while now. You started, what, in 2011 working on SCADA systems. Uh, uh, there’s been a lot of evolution since then. Walk me through, like, the process where you thought, “Hey, there’s a business here.”  Alejandro Cabrera Muños: Of course. Uh, we actually started officially back in 2012. It’s been a, quite a, of a long journey to, to get here. Uh, yeah, we started, uh, back, back then. We say it’s a whole new world, right? If we look backwards, like, almost 15 years. Makes me, makes me feel, like, extremely [00:01:00] old. Uh, but ne- nevertheless, um, yeah, back then we were trying to, to cover, like, a lot of issues that were based on OEM SCADAs, which by the way, we still are dealing with. But, but that, that was starting point. It was, um- It was, uh, based on understanding that the, the renewable energy industry is so complex. Every wind farm, every solar plant has different issues, different systems. Even, even the same models from the same manufacturer sometimes have complete different systems, which complicates everything. So it was very exciting to, to start our careers in a, in an industry where nothing is standard and where everyone is looking for something that is standard. So that’s, that’s where we fit in. Um, yeah, and in these years, we, we started basically creating the f- the foundations, uh, uh, on top of, uh, SCADA systems. [00:02:00] But as soon as we had that, those foundations, we realized that this sector is not gonna evolve, uh, it’s gonna cope up with the complexity, uh, of the technical complexity, market volatility, regulatory compliance. That’s not gonna be solved by just having more SCADAs. So we created a layer of automation in place, which is basically what we’ve been, um, evolving in the last 10 years now, um, with the, with the mindset and with the goal that every wind turbine should be running autonomously without having to have people behind it, uh, supervising and taking control of it. Allen Hall: Yeah, and that’s a great founding idea, but that has grown from an idea to you’re automating, what, 40 gigawatts of renewable assets right now?  Alejandro Cabrera Muños: Oh, we’re actually now connected to over 70 gigawatts.  Allen Hall: That’s amazing. Alejandro, that’s incredible.  Alejandro Cabrera Muños: And all of them are different.  Allen Hall: Sure. So that, that’s a combination– 70 gigawatts is a combination of wind and solar and anything else? Alejandro Cabrera Muños: Yes. [00:03:00] Well, actually, one of the, one of the main, um, needs that we try to cover from day one is to be able to connect to all, um, asset classes. So we understand that, um, the challenge of operating a large portfolio for our customers, um, can only be solved if we have the ability to connect to all type of asset classes. So we can have to connect to wind turbines, inverters, trackers, substations, um, energy meters, you name it. You– we have to connect to every single asset class, um, because what’s important is how you manage that data on top of that and how you react on the anomalies.  Allen Hall: Right. Because I think a lot of operators are now considering taking your model, the Green Eagle model of s-self-operating, but they need that help, they need that insight into the operation of a solar farm or a wind farm or, or any of those assets, renewable assets, ensure those inverter-driven assets. You’re, you’re seeing– I, I think we’re seeing the same thing, which is a lot of operators decide to [00:04:00] leave full service agreements globally, and what do you think is driving that now? Uh, is it a financial decision? Is it a performance decision, or is it both?  Alejandro Cabrera Muños: I think there are many factors, but I think the main driver is the financial aspects of it. I think when you, when you delegate the operations to a third-party, uh, entity They are gonna optimize their services to whatever service level agreement or availability they are committed to. And for that reason, you’re never gonna get– effectively, you’re never gonna get the extra mile. You’re never gonna get any extra from there. Um, and that’s okay when the market is– has great conditions and everything w- is going well. But we are seeing how in the last years we have, uh, a lot of market volatility, negative pricing. Everything is becoming more and more complex, so many projects are actually under stake financially. And I think that’s, um, that’s pressuring everyone to look for opportunities to squeeze their assets a little bit more or a little bit better, I would say.[00:05:00] Um, and part of that is to take operations in-house so you at least you have the opportunity to, to do, um, a better job, uh, let’s say.  Allen Hall: Yeah, and part of what we’re seeing is, at least in the United States and, and globally now, I think it’s, there’s more action globally than there has been on mergers and acquisitions. So an operator that has historically had a particular OEM in wind, you know, say it’s Vestas or Siemens or GE, whoever, Nordex, it could be any of them. Uh, when they acquire another competitor or another farm, they’re bringing in a f- a wind turbine they probably don’t know much about. And, and that’s a huge problem. And, and there’s not a lot of resources for them to grab hold of. Uh, that’s one of the marketplaces you’re trying to fill right now, right?  Alejandro Cabrera Muños: Of course. Uh, as I mentioned before, if something describes our sector is that nothing is standard, despite everyone is seeking standardization of everything, right? Uh, but nothing is standard for, [00:06:00] for– and that, that’s the reality. So the first thing when, when you have a portfolio and you are incorporating new assets into it, you need, um, a solution that is able to connect to all type of assets, right? Um, w-we call our solution a three-in-one solution because first of all, it acts as a second level SCADA, so you can connect everything there, uh, everything there, and you have access to all the data across all your assets. Then we have the SCADA automation layer, and then we have the data analysis layer on top of that. Okay. But let’s focus on the operations, which was, uh, your question, right? So you have a new bunch of assets. Sometimes you don’t have any documentation whatsoever, but these are Gamesas, Nordex, a bunch of them from different years. Um, the first thing that we provide is a second level SCADA, so you can connect to all of those. But We have, uh, something that we believe is very unique. So what we provide to our [00:07:00] customers is ability to automate all these assets autonomously. And what that gives you, it’s, um, set of data that can be analyzed, and we can learn from what’s working, what’s not working, beyond what the manufacturer’s gonna tell you to do, right? So we have thousands of General Electric turbines connected to our software, for instance. Um, we know what works, what doesn’t works, uh, what are the faults that can be resetted remotely, what are the ones that are not, what is the success ratio of those resets, ’cause that’s a metric that nobody else has unless you have automation in place. Uh, but we can actually understand, is it working? Is it not working? Is it creating fatigue for no reason to these turbines? So what– we have all this, this, uh, un- this knowledge and this, um, knowhow, uh, for all these models. Um- I believe one of the main, um, value that we provide to our customers is, is not only the, the solution itself, but it’s also the [00:08:00] ability to be somehow prescriptive. It’s, it’s not that we’re gonna know more about how to operate the assets than our customers, but, uh, we have a sense of what’s the benchmark, right? So I, I– And that benchmark is very, very useful for them as well.  Allen Hall: So th- that’s part of getting to scale, and 70 gigawatts is a, a lot of scale, where you have seen a number of turbines in different places operating in different environments and performing at different levels. That’s unique, right? That gives you insight into really what’s happening to a turbine or a solar asset globally and also locally. For a lot of operators that just happen to acquire or, or, or take on a- an older wind farm, uh, they tend to get stuck, right? They, they, they, they don’t tend to be able to, to find their way through those little nuances. That’s a huge financial impact to them eventually, right?  Alejandro Cabrera Muños: It is. And I, and I believe that for many years this was something that in a way got, um– [00:09:00] didn’t get a lot of visibility. I think people were not fully aware of how much revenue, how much production they were losing just because they were not operating their assets at the best capacity. Um, now we have the data to prove what, what better can look like. W- uh, we have data to prove that if you follow the OEM’s, uh, protocols, you may be creating fatigue for no reason. Um, and there are improv- there are ways to improve that thing. So I think it’s, um– We are, we are opening the door for a new, complete new way to operate your, your portfolio and get more benefit from it. Allen Hall: I think that’s a very interesting aspect of the sort of the structural aspects of how a, a wind turbine performs, and a lot of that is driven by software. And you, you realize if you’re paying close attention to the OEMs that some of the software updates are not necessarily performance enhancements. They’re more of protecting the turbine because they realize they may have a problem. So it may be a slight derate, it may be a, a different sort of power curve that happens. [00:10:00] But a lot of operators don’t really sense that that is happening up close because they’re not into the details of that. That’s where Green Eagle separates itself. You are into all those details. And do you have a lot of operators just reach out for help immediately saying, “Hey, I have this Siemens Gamesa or Gamesa wind farm,” think about an older wind farm, a Gamesa wind farm Help. Just please help. Uh, whatever you can do, just show us you can do it. Do you, do you start to run a little test campaign on that site, or do you, or do you go pull back from the 70 gigawatts and 15 years of history to, to show this is what you can do with that particular asset to, to get them involved in a thinking about the problem a little bit differently? Alejandro Cabrera Muños: Well, I wish, I wish it was that way. Um, but what, what– It, it was that transparent, but what happens is that we’re working with the largest, uh, some of the largest utilities and IPPs in the world. So what happens is that they, they will never come to us saying, [00:11:00] “We don’t know how to operate this turbine,” or, “We don’t have enough information.” Um, the way they ask for it is like, “Are you compatible with this?” And, “Do you know… Do you have some protocols? Do you know the standard protocols to run these turbines?” Um, and that’s the way we, we start the conversation, and then they, uh, they, they get confident that we can actually help them with that. We only know about how, how much or how little they know about a specific model once we start working with them. And it’s not all or nothing. I- Ev-Even the largest manufacturer, e-even the largest utilities, their portfolio is constantly evolving. They’re incorporating new sites almost every month. So there’s always one site that they don’t, they don’t have expertise in the, in the house, so it’s, it’s normal. Like, basically not many people have expertise in some of the models from old Nordex or Gamesas or you name it. It, it’s impossible basically to have to understand all models in the world. So I think we [00:12:00] have the, the data, the benchmarks, and experience, and on top of that, the of course, the, the tools, so you can actually operate better those, those assets.  Allen Hall: So the name of your system is called ARSOS, A-R-S-O-S, and for anybody listening to this podcast, you can just Google it, and it’s gonna take you to Green Eagle. What is that product? How would, how would you define or describe that product?  Alejandro Cabrera Muños: Well, ARSOS is a suite. Um, what– The way I like to think about it is a, is a three-in-one solution, right? So it’s first of all, it acts, it, it, it fits in between the SCADA world and the REMs, uh, the REMs, uh, solutions. Okay? And they’re complete different worlds even though you see dashboards and they look the same thing. But SCADAs must be, um, must be able to be installed on premises. They require OT enterprise cybersecurity level. They can be, they should be installed on air-gapped infrastructure, so no access to internet whatsoever. [00:13:00]Um, and that they tend to be extremely complex to configure and, and, uh, adapt to every, uh, every different site. So that’s one world. Um, on the other hand, we have the, the REM solutions that are like more like a SaaS platform, like a Power- it could be Power BI, it could be like the, the normal use cases that you need it. You need something, some tools to create the reports at the end of the month to understand the performance of your assets, right? So you have these two, two worlds. So what we are proposing here is a solution that has been built for the past 15 years, but it fits right in the middle. So it covers Almost everything that you need from a SCADA and second level SCADA solution. It puts automation in place, and then it also gives you all the data so you can consume it in the best way, uh, possible, which by the way, now with, uh, artificial intelligence, it’s incredible what you can do with it. So this is basically what we have built, um, right [00:14:00] now. And the main differentiation here is that since we are in the middle, we are trying to solve all this complexity from a SCADA world with a product that is already pre-configured. So you can basically connect to your sites in a completely easy way, um, doing clicks and not a lot of complexity because it’s already pre-made for your needs. Um, because of that, the time to market is extremely much, uh, faster compared to a SCADA solution, so you can have a solution in thing, in hours and not in months. It’s, it’s not a project anymore, right? Which is, which it sounds like normal when you, when you talk about applications, it sounds like a normal thing to do, that you have a, a system running in hours or minutes. But when you’re talking about SCADAs, that’s like sci- uh, sci-fiction, right? Um, that’s what we’re bringing to, into, onto the table. It’s, it’s, uh, something that you can connect to all your assets in a seamless way, painless, and, uh, and, uh, off the [00:15:00] shelf.  Allen Hall: Well, that’s a very interesting way of framing, uh, the product because, uh, you do see both ends of the spectrum here, where y- there’s a number of companies that are offering a c- completely SaaS product, which is a very pretty dashboard, and it still relies on a human to watch this dashboard and, and to make sense of it, and it provides some insight. And then you get to the other side, which is almost a completely mechanical system, where it’s just SCADA data and, and you’re just picking up data for datas, uh, to have, basically. So you, you f- you sort of find that middle ground. The, the, the amount of software and technology that it’s in that space, though, must be huge, and what is the effect of AI bring to you? Does that help you more with just on the, on the, on the model side or just the, the statistical analysis of all the data that you have access to now?  Alejandro Cabrera Muños: Let me make a, um, clarification. Because since, uh, we are, we are providing automation [00:16:00] in a world that is mission critical, right? So there’s no, a lot of, there’s no room for creativity or probabilistic approach. It all has to be the deterministic, right? Uh, so when we talk about automation, we’ve always been focused on deterministic automation, so rule-based, uh, automation, and that’s what we have implemented on top of the level of the SCADAs, right? So that’s, that’s the part where you know how to deal with an asset. You have the protocols. You want to understand how they work, but you want to have certainty of what happens if the turbine is on fault and the fault is related to the gearbox temperature and so on. So you wanna make sure that there’s a reset automatically executed only if the temperature of the gearbox is under X threshold. So this very deterministic approach. Uh, but we have, uh, something, um, very unique when we go on the, on the other side, when we go on the side of the REMs. Because we not only have the data of, of the assets, we [00:17:00] not only have statuses, performance, availability, uh, production. We also have the data of how these assets, assets have been operated, right? So we know how much fatigue they have received, how they’ve been operated, um, have they received curtailments or not? How many curtailments? What were the reasons? So we can actually have a 360, uh, degree of all the data, including all the control, not only how they’re performing, but also how we are operating those assets. And we believe that this is very unique because only if you have all these 360 data, then you can actually enhance what you have on top of that. And that is where AI come, comes in, right? So AI, AI is great in, um, helping our customers in doing root cause analysis, um, dealing with anomalies are not well, um, uh, procedure. Uh, there’s no course of action that is clear, that you don’t know. It’s, they’re not like too [00:18:00] frequent to, to have one. Uh, mixing different type of data. Like I mentioned before, you have, uh, market data, you have curtailments, you have, uh, commands to stop or start a turbine. You have a lot of information there, and you can put all together. Uh, also along with the CMMS information. Um- Lastly, they get– they can pull that together to do whatever they need, right? Uh, they can build with AI. You, you can now do your own dashboards. You can create your own APMs if you wanted to. Um, and I like to think about it, like, with these new tools that you can create disposable dashboards. And, uh, the concept is that it doesn’t matter how many different dashboards you have in an APM, but tomorrow you have a, a specific case. And I think it’s amazing that now with AI and the right, uh, data structure, you can now create a dashboard, and maybe it’s just for one use case, you know? And you just build it today, look at the data. You have [00:19:00] a, um, a case study, and that’s it. May– you never use it that again. The trick for being able to, to, to create this ecosystem where you analyze the data in a completely different way is that we have been working on how to structure the data so the AI is gonna be able to understand the data itself. So once that, that layer is structured in the right way, then you can actually create your own APMs or your own dashboards as you need to.  Allen Hall: That’s fascinating. So instead of just thinking of a turbine or a, a solar field as a asset where you’re trying to maximize performance necessarily, you’re looking at it from the marketplace, the, the, uh, the shutdowns, all the, the things that are contr- overriding the performance and trying to optimize performance in this market environment, which may be very turbulent, and I think for a lot of wind operators is very turbulent, uh, at, at the minute just [00:20:00] because of the nature of the electricity grid. So you’re, you’re then thinking about Having an AI tool to help you do investigative work on the particulars, not just the global data set of how this turbine globally operates, but the specifics, that’s fascinating because that allows you then to treat each turbine as its own separate power plant, in a sense, but also to, to think about lifetime issues and how to maintain that piece of equipment in a much more efficient way. That’s remarkable.  Alejandro Cabrera Muños: And you have the– With AI, you also have the capabilities to automate all these type of analysis. So once you have a specific, uh, case to be analyzed, then you can automate that case to be analyzed in a daily basis, in a weekly basis. But that’s, uh, that, that’s, uh, that’s, uh, the world that we are moving to. Allen Hall: So a lot of what’s happening at Green Eagle at the moment is being automated and, and making it easy for, for customers to get [00:21:00]onboarded to the RSO system. What does that look like today? Uh, how do, how do I get onboarded? I have an asset of I got 1,000 turbines and a couple of solar fields. What does it look like to get me started in the RSO system with Green Eagle? Alejandro Cabrera Muños: Well, if you’re using our cloud, it’s, it’s gonna be a process of If you have a, a portfolio of 500 gigawatts, you can connect to our, to our cloud in a matter of like one month to two months So that’s something that you can do by yourself. So, um, you can create the assets, you can create the connectivity. The connectivity is done through IP filtering or VPN tunnels. All that is from the, from the dashboards, from, from the cloud. Um, then you can, based on the model directory, you can choose which is the, the assets that you want to connect to and through what channels, whether you have Modbus, OPC, and so on. Um, but that’s a- as complex as, as it gets. Really? It’s n- it’s not easy either, because [00:22:00] you need to understand what is a Modbus, what is a OPC, but that’s what it is. It, it’s not a matter of, like, installing something on site and doing tons of, uh, complex, uh, um, configurations. You don’t need, uh, SCADA engineers to be, like, building these dashboards tailor-made for your sites and, and all that is, is something from the past in o- in our opinion. Allen Hall: So you’re not on the telephone, or you’re not on a, a online chat with the Green Eagle team, because it’s, it’s, it’s– you’ve, you’ve done enough capacity now that you’ve automated this.  Alejandro Cabrera Muños: You don’t have to.  Allen Hall: That’s amazing, because I think that’s the first worry for any operator that is gonna make that leap saying, “Hey, I need a little bit of help with this wind farm or this solar site,” is that, “Oh, I gotta be on the phone. I gotta– There’s a lot of im- of onboarding that has to happen,” and you’ve eliminated that.  Alejandro Cabrera Muños: Well, first, w- I, I totally understand this hesitation. Um, many of our customers are living in, in the, in the SCADA world, right? Uh, and which w- it was probably once a pain [00:23:00] to be configured to begin with, and I think half the sector is traumatized by these processes. So I, I tot- I totally understand that that pain is, is still there, right? I understand that. But what we’re trying to do is to, to move forward and say like, “Yeah, that, that’s gone. That was the past. Now we have a different way to do it.” And if you have, uh, either new assets that you need to connect or you even consider, like, moving to something more modern, something with more capabilities, something that comes with automation in place, uh, well, we have a solution that is painless. Allen Hall: Can I discuss, or can we go back and forth about the, the use of inverter-based resources, the solar and the wind sites, in terms of the, the move from grid following to grid forming and stabilizing the grid? I think there’s gonna be a lot of changes in the way that we operate these assets over the next year. Mostly, uh, I see action in the United States from the Iberian blackout about a year ago. They’re changing the thought process of how they want to run the grid so that the wind [00:24:00] and solar can keep the grid operating. Is– Are you involved in, are you involved in that aspect of how you operate those assets and how those inverters perform and, and configuring them to, to do more of the, of the grid forming and keeping the grid stable? Alejandro Cabrera Muños: I believe, to be honest, this is more related to power plant controllers and hybrid plants. So we have, we have made several projects with, um- With a mix, uh, of, uh, wind, solar, um, and storage. And wh- but what we’re doing here, uh, to be completely honest, we are not involved in the power plant controllers. Uh, we believe that that’s an electrical device and has, uh, uh, particularities that are out of us- our scope. But what we do is to, again, we connect to all asset classes, right? So we also w- connect to the PPCs, and we can monitor the PPC, the performance of the PPC, and we integrate that into everything else, right? So [00:25:00] that’s, for us, that’s another asset that we are connecting to, and that it make– it completes the view of, um, of sites that are now, like, almost like mini portfolios at, at the same place, right? ‘Cause you have, uh, different technologies, service stations. You have so many things that you need to orchestrate as well. So we’re, we’re w- moving into, into that area as well, uh, f- with the same concepts.  Allen Hall: B- so in a, in a sense, you’re able to monitor the health or status of the grid. Because you’re connected to so many of these assets, you have a pretty good understanding of how the grid is doing at any particular moment then. Alejandro Cabrera Muños: That’s right, yeah, especially in, in Spain, of course, ’cause we’re connected to, um, over 25 gigawatts at the, uh, at, in Spain, so.  Allen Hall: Alejandro, that’s amazing.  Alejandro Cabrera Muños: Over 25 gigawatts at the, uh, at, in Spain. So, so that’s s- it’s almost a third of the, of the installed capacity in Spain.  Allen Hall: Is there a movement in Spain to, to use technology like yours [00:26:00] to better monitor, regulate, control the, uh, wind and solar assets so- such that they stay engaged when, when the, the grid starts to, to vary a little bit? Has anybody asked you to, to be involved with that? Because it seems like you’re the right– you’re in the right place at the right time.  Alejandro Cabrera Muños: The challenge of all these grid codes, uh, in, in most of cases is just that There are tons of curtailments that are coming from many different reasons, technical restrictions, market, uh, dispatch, um, other type of compliance. Um, the, the first challenge is to just execute on them, right? So they’re coming, you need to apply on the, on the sites. Um, that was the first, the first phase. But now that we have so many gigawatts connected, and that we’re also participating in balance mechanis- balance mechanisms and ancillary services, what we are seeing is that depending on how your assets perform and how quickly they are in regulating, um, you are gonna [00:27:00] have penalties or more, uh, profitability in the participation of the markets. So that’s, that’s extremely important as well ’cause it’s, it’s quite difficult to, to measure. But we have all the– Since everything is automated, you can always track, and you can statistically understand which of the sites are performing better or worse, in what cases, and therefore you have opportunities to improve the regulation and get more revenue from it. Allen Hall: Okay. So Green Eagle then is, because of the scale that it has at the minute, can look at the grid and is involved in, in the, the grid requirements, so to speak, of, of, uh, curtailments and what assets are operating when, and also the voltage control aspects and frequency control, which is the other part of it. You, because you’re, because you have so many assets in Spain and globally, you, it’s amazing the number of assets you have. You, you then can actually, one, see health of the grid, two, [00:28:00] provide insights to operators on what that looks like. I mean, real time you could, you can do that. And then are, are, are the regulators then coming to, to you asking advice on how these assets should perform? Because it does seem like you would be a tremendous resource on how the grid is actually doing on a larger scale from a renewables standpoint.  Alejandro Cabrera Muños: Yeah. Well, fortunately, the, the regulator has its own also, uh, system, so it’s, uh, redundant, right? So as far as we, we are working to, to have, uh, the best system in the world, but, but it will be a lot of, uh, responsibility for us to just have the whole grid depending on us. That would be a lot of weight. Uh, but in a, in a way, in, in a, in a way, it already depends on us, uh, effectively. So, so the pressure is, is there. We have, we have talked to them, um, since we have so many customers, um, in the, in the– at this level, uh, we have to be very quick in implementing new grid codes and new [00:29:00] regulatory, uh, compliance issues and, and so on. So that’s, that’s, um… It’s a challenge, but at the same time, it’s, it’s very exciting that we are always ahead in, in this regard.  Allen Hall: Right. If, if I was an operator and I had Green Eagle as one of my, uh, helpers in a sense, uh, assistants in a sense, that helps with the, the grid code i-in terms of, one, understanding it, and two, being able to implement the changes that are coming down all the time. You have a resource there that understands it from a larger perspective because you see it from multiple operators in multiple places trying to do the same thing. That’s a huge advantage instead of you trying to na-navigate or try to understand all those grid code changes and why they’re happening and what it means to you and how do you operate your assets. So you can provide a little bit of guidance there for the operators.  Alejandro Cabrera Muños: Of, of course. Um, uh, the main, the main value proposition that we can have here for anyone that wants to participate or be part of the Spanish market is that we already have all this figured out. So if you wanna start from the scratch [00:30:00] with, uh, with a SCADA, industrial SCADA, well, let’s, let’s go with, let’s go with that. You’re gonna be probably traumatized in the future, right? Uh, but with us you have an off-the-shelf product that is already compliance. It, uh, h- we have already set, uh, the system certified by the TSO in Spain. So we have already gone through this process so many times, and it’s off the shelf, so you don’t have to worry about any of this. And on top of that, you have the Peace of mind that if tomorrow there’s gonna be a, a, a new change in the, in the, in a new grid code, well, which most likely is gonna happen, um, soon, uh, we have to, we have to do it. Because we have already, uh, a lot of customers that, that, that need it. So for us, it’s actually also, uh, strategic to, to be ahead and be fast in implementing these grid codes. Allen Hall: That’s amazing. That’s such a huge resource for Spain and the rest of the world. Yeah, that’s amazing. Well, I, I know people who are listening to this podcast right now are thinking, “Okay, I haven’t heard of Green [00:31:00]Eagle, but now I’m interested, and I need to f- find out more.” How do they contact you? Where do they go first? What’s the best first step?  Alejandro Cabrera Muños: Well, they can connect, uh, directly to me through LinkedIn, or they can just write to sales@greeneaglesolutions.com.  Allen Hall: Great, yeah, and Alejandro’s available on LinkedIn, so you can f- find him there. And we’ll put his contact information in the show notes to, so you have quick access. Alejandro, you gotta come back more often because the, the things that you’re doing with Green Eagle are amazing, and, uh, the, the scale is incredible. Congratulations on that. Uh, and, and I, I, I need you to come back and tell us what the next generation looks like because I know when you guys get ahold of AI and start thinking through some of these real challenging problems, Green Eagle will have solutions. So you’re welcome back anytime.  Alejandro Cabrera Muños: Super exciting to come back, uh, when you invite me. Thank you so [00:32:00] much.

Downtime does not care who your vendor is, but your recovery time absolutely does. We sit down with Bruce Burton, an electrical reliability engineer at Trinity Manufacturing in North Carolina, to hear a candid customer story about modernization, trust, and what it takes to keep a chemical plant running when the stakes are high.Bruce walks us through major electrical upgrades including motor control centers, transformer planning, and the kind of engineering decisions that make future expansions and retrofits less painful. We also get specific about support in the real world: troubleshooting variable frequency drives, getting parts turned around fast, and building a virtual inventory system with barcodes and routine counts so critical spares are there before a failure hits.Then we go deep on smart motor control centers and industrial data. Bruce explains how Ethernet/IP and Modbus connectivity unlock three-phase visibility, historical trending, faster root cause analysis, and more confident decisions during faults. We also talk power quality monitoring, harmonic distortion, and how custom communications drivers can pull useful data from a mixed fleet of devices without disrupting an operating plant. If you care about plant reliability, industrial automation, and practical digital transformation, this conversation is packed with field-tested insight.Subscribe, share this with someone in manufacturing, and leave a rating and review so more reliability-focused teams can find the show.Keep Asking Why...Read our latest article on Industrial Manufacturing herehttps://eeconline.com/inspire/EECO100_trinityOnline Account Registration:Video Explanation of Registering for an AccountRegister for an AccountOther Resources to help with your journey:Installed Asset Analysis SupportSystem Planning SupportSchedule your Visit to a Lab in North or South CarolinaSchedule your Visit to a Lab in VirginiaSubmit your questions and feedback to: podcast@eecoaskwhy.comFollow EECO on LinkedInHost: Chris Grainger

Parce que… c'est l'épisode 0x301! Shameless plug 3 au 5 juin 2026 - SSTIC 2026 24 et 25 juin 2026 - Troopers 26 et 27 juin 2026 - leHACK 19 septembre 2026 - Bsides Montréal 1 au 3 décembre 2026 - Forum INCYBER - Canada 2026 24 et 25 février 2027 - SéQCure 2027 Description Dans cet épisode, Georges Badro, consultant chez Mandiant à Paris spécialisé dans les infrastructures critiques et les systèmes industriels, explique le fonctionnement et la sécurisation des sous-stations électriques. Architecture du réseau électrique Le réseau électrique se décompose en trois zones : la génération (centrales hydrauliques, nucléaires, thermiques, renouvelables), le transport et la distribution. Le réseau de transmission permet de limiter les pertes d'énergie et surtout d'équilibrer production et consommation afin de maintenir une fréquence stable. Contrairement à un réseau d'eau, un réseau électrique exige un équilibre permanent entre ce qui est produit et ce qui est consommé, sous peine de l'endommager. Les sous-stations sont les nœuds névralgiques de ce réseau de transmission : ces grands parcs clôturés que l'on aperçoit au bord des routes centralisent et redistribuent l'électricité. On y trouve des transformateurs et des disjoncteurs, ces derniers permettant d'ouvrir ou de fermer le courant. Aujourd'hui, ces équipements ne sont plus opérés manuellement mais via du contrôle numérique : interfaces homme-machine (IHM), contrôle à distance, RTU (Remote Terminal Units servant de passerelle vers le centre de contrôle), relais de protection et de contrôle (qui lisent tension, intensité et fréquence pour automatiser des décisions), postes d'ingénierie et équipements réseau. Interconnexion croissante et surface d'attaque Badro insiste sur la disparition de l'« air gap » d'autrefois. Les sous-stations sont désormais interconnectées avec les centres de contrôle, des tiers, des partenaires, parfois directement à internet, voire avec le cloud pour la maintenance prédictive. L'architecture type comprend un réseau IT, une DMZ séparant l'IT des systèmes industriels (OT), un centre de contrôle régional ou national (avec historians, serveurs SCADA, bases de données) relié aux sous-stations via VPN ou MPLS. Chaque sous-station est configurée différemment. Certaines connexions exploitent le Powerline Communication (PLC), qui utilise les câbles électriques existants pour transmettre des paquets TCP/IP. Cette multiplication des accès distants, justifiée par la difficulté d'intervenir physiquement dans des zones rurales, augmente considérablement le risque. Les protocoles courants incluent IEC 104, DNP3 et GOOSE. Scénario d'attaque en Red Team Badro détaille l'approche Red Team de Mandiant, précisant qu'un véritable attaquant ne prendrait pas les mêmes précautions. L'attaque commence généralement par un accès initial à l'IT via phishing ou exploitation de vulnérabilités. Suit une phase de reconnaissance : énumération du domaine, recherche de documentation sur les partages réseau et wikis, fichiers de configuration aux extensions spécifiques, mots de passe en clair (notamment de VPN) et schémas d'architecture. L'accès au réseau OT s'obtient ensuite via un VPN, l'exploitation de flux autorisés au firewall, ou la compromission d'hyperviseurs hébergeant des VM IT et OT. Plutôt qu'un scan NMAP destructeur, l'équipe privilégie une reconnaissance furtive : écoute passive du trafic, analyse des adresses IP et MAC, utilisation de logiciels légitimes d'opérateurs et de scripts spécialisés (Modbus, DNP3). Les vulnérabilités exploitées sont souvent basiques : mots de passe par défaut sur interfaces web, SSH ou Telnet, parfois sur des fonctionnalités cachées utilisées par les fournisseurs et inconnues des équipes. À partir d'une IHM, l'attaquant remonte vers les relais de protection, cibles plus insidieuses permettant des dégâts coûteux. Compromissions réelles Badro compare deux attaques réelles. En Ukraine en 2015, l'attaque a démarré sur l'IT par phishing (malware Black Energy via macro), récupéré des mots de passe VPN, accédé aux IHM, RTU et switchs Moxa, puis ouvert les disjoncteurs et déployé des firmwares corrompus pour empêcher la reprise de contrôle. En Pologne en décembre 2025, l'attaque a ciblé directement l'OT en exploitant une CVE connue mais non corrigée pendant plusieurs semaines sur des firewalls exposés à internet. L'attaquant s'est étendu aux RTU, relais, IHM et convertisseurs série-Ethernet via des comptes par défaut, a lancé des scans locaux, uploadé des firmwares corrompus, supprimé des fichiers système des relais et déployé des wipers sur les IHM. Le constat marquant : malgré dix ans d'écart, les mêmes vulnérabilités basiques persistent. Si l'entrée dans les réseaux IT s'est durcie, le côté OT reste comme l'IT « d'il y a très longtemps » — peu de mots de passe robustes, peu de contrôles — par préjugé d'isolement et par des pratiques de maintenance figées. Attaques avancées et défense Au-delà de la simple ouverture d'un disjoncteur, des attaques plus subtiles ciblent la logique des relais : modifier des valeurs de déclenchement, fausser une LED, ou altérer la fonction de réenclenchement automatique. Ces manipulations restent invisibles jusqu'à une condition rare (un arbre tombant sur une ligne) et sont très difficiles à diagnostiquer sans journalisation. Côté défense, Badro recommande : changer les mots de passe par défaut (et alerter si l'ancien est réutilisé), maintenir à jour les systèmes exposés à internet, restreindre les accès SSH/HTTP à des points spécifiques, contrôler les flux PLC venant des centrales, et surtout établir une visibilité réseau et événementielle à tous les niveaux. La prévisibilité des réseaux OT facilite la définition d'une baseline et la détection d'anomalies. L'approche consiste à décomposer chaque système, comprendre les fonctions et leurs interfaces internes/externes (par exemple le GPS spoofing), puis concevoir protections et détections adaptées — en protégeant avant tout le disjoncteur, élément le plus critique. Collaborateurs Nicolas-Loïc Fortin Georges Badro Crédits Montage par Intrasecure inc Locaux réels par Google Paris

In this episode of The Electropages Podcast, host Robin Mitchell interviews Rodney Dowdall, VP of R&D at TeleCANesis. Rodney explains how TeleCANesis helps engineers connect CAN, Modbus, ISOBUS, EtherCAT, MQTT, JSON, and other protocols through a configurable middleware stack designed to reduce repetitive code changes and simplify embedded data handling. The conversation covers how TeleCANesis was built around a real engineering problem: data formats, CAN messages, DBC files, and sensor interfaces keep changing, forcing developers to rewrite and revalidate code. Rodney explains how a configuration-led approach can help engineers update message handling without changing core software, reducing the risk, time, and certification burden that often comes with embedded development. Engineers will also hear a wider discussion on AI-assisted coding, deterministic software, safety certification, human-in-the-loop development, and why "vibe coding" may suit some applications but not safety-critical embedded systems. This episode provides a practical look at how middleware, tooling, and protocol abstraction can make connected devices easier to build, maintain, and scale.

We mogen 80 kilowatt gebruiken. We hebben 25 elektrische auto's. En toch is iedere auto vol als-ie weg moet. Hoe? In deze aflevering twee gastnerds die vorige week ook al aan tafel zaten: Femme Taken (oprichter Tweakers, mede-eigenaar Loqio) en Jesper Weiland (oprichter Exonet). Femme bouwt energiemanagementsoftware en Jesper heeft sinds 2018 een all-electric kantoorpand in Zevenaar dat als proeftuin dient. Samen leggen ze uit waarom een aansluiting van 80 kW genoeg is voor 25 Tesla's, waarom 14 laadpalen elkaar netjes laten meedoen, en waarom Liander Jesper twee ingebrekestellingen stuurde toen het script in het weekend even niet meewerkte. Onderweg: dynamische energietarieven, time-of-use nettarieven, het einde van de saldering, Chinese omvormers die remote nieuwe firmware krijgen, thuisaccu's met een terugverdientijd van tien jaar, en de vraag of we de energietransitie wel bij de eindgebruiker moeten leggen. Een aflevering over netcongestie als papieren probleem, en over wat je daadwerkelijk kunt doen. Over Femme Taken Femme Taken is in 1998 op zijn achttiende Tweakers begonnen, toen nog Tweakers.net. Hij is sinds 2008 architect bij Tweakers en daarnaast mede-eigenaar van Loqio, dat zich richt op slim energiemanagement en domotica. Zijn eigen 17e-eeuwse boerderij in de Achterhoek staat bekend als “het slimste huis van de Achterhoek”. LinkedIn: https://www.linkedin.com/in/femme/ Loqio: https://loqio.nl Over Jesper Weiland Jesper Weiland is mede-eigenaar van Exonet, een onafhankelijke managed hosting provider in Zevenaar die hij sinds 2002 samen met compagnon Robin runt. Exonet is begin 2026 de nieuwe hostingsponsor van Tweakers geworden. Zelf is Jesper sinds 2000 op Tweakers actief, met meer dan 15.000 forumposts in de boeken. LinkedIn: https://www.linkedin.com/in/jesper-weiland-1551705/ Website: https://www.exonet.nl In deze aflevering 0:00:00 Intro: 80 kW, koppel-uitdagingen en waarom 120 niet altijd nodig is0:01:09 Hoe Femme’s smart home hobby een side hustle werd0:07:10 Energiemonitoring 101: van koffiezetapparaat tot WTW-installatie0:10:23 Vijf jaar luchtkwaliteitsproblemen, opgelost met Grafana-dashboards0:13:40 Twaalf laadpalen, 25 auto’s: het puzzelstuk dat alles oplost0:19:11 Geknepen door Liander: 80 kW terwijl de meterkast 250 ampère aankan0:23:14 Slimme laadpalen, domme laadpalen en alles ertussenin0:27:00 Dynamische tarieven, time-of-use en het einde van de saldering0:38:25 Chinese omvormers en de cloud die altijd wil meekijken0:46:10 De papieren werkelijkheid van het stroomnet0:53:00 Thuisaccu’s, balansmarkt en waarom tien jaar terugverdientijd niet werkt1:03:58 Security: wat als iemand alle zonnepanelen tegelijk uitschakelt1:06:45 De volgende stap: een industriële batterij voor het pand1:14:00 Afsluiting en plug Genoemd in deze aflevering Loqio, Femmes bedrijf voor energiemonitoring en smart charging Exonet, managed hosting met all-electric kantoorpand Home Assistant, open-source smart home platform Grafana, dashboardtool voor monitoring en visualisatie Aardehuizen Olst, ecologische wijk met Loqio-energiemanagement Modbus, industrieel communicatieprotocol Matter, nieuwe standaard voor smart home interoperabiliteit Loqio over Exonet, het projectverslag van het kantoorpand Vorige aflevering: Tweakers en Exonet, waarin de bromance begon Tips van de tafel Femme: Als je serieus aan de slag gaat met energiemanagement, zorg dat alles lokaal blijft draaien. Een Raspberry Pi heeft inmiddels meer dan genoeg performance, en je systeem werkt door als de internetverbinding eruit ligt. Jesper: Begin niet met techniek, begin met inzicht. Meet eerst wat er gebeurt in je verdeelkast voordat je ook maar iets gaat optimaliseren. De rest volgt vanzelf zodra je de cijfers in een dashboard ziet. Randal: Vraag bij je netbeheerder na of je gecontracteerde vermogen wel klopt met wat je daadwerkelijk gebruikt. Verlagen scheelt soms tientjes per maand, maar weet dat je er met geen mogelijkheid weer makkelijk vanaf komt als je het later weer nodig hebt.See omnystudio.com/listener for privacy information.

פרק מספר 514 של רברס עם פלטפורמה - Attack Analytics. בפרק זה רן ואורי מארחים את ד"ר גיא וייזל, Tech Evangelist בחברת Cato Networks, לשיחה מרתקת על האופן שבו בינה מלאכותית משנה את חוקי המשחק בעולם הסייבר. דיברנו על מודלי AI מתקדמים, כיצד הם מאיצים מתקפות של האקרים אך גם משפרים את יכולות ההגנה, ואיך פרוטוקולים עתיקים יכולים להוות נקודת תורפה מסוכנת לתשתיות פיזיות. [00:00] ל"ג בעומר, כנס רברסים ופתיחת הפרק חג שמח! מקליטים על הדרך למדורה של רבי שמעון. עדכונים לגבי כנס רברסים 2026: אנחנו כבר עובדים במרץ ומגייסים ספונסרים לכנס הקהילתי. אם הארגון שלכם מעוניין לתמוך, מוזמנים לשלוח לנו מייל ל-team@reversim.com (או כל וריאציה אחרת שעובדת לכם). קול קורא (CFP) להגשת הרצאות לכנס ייפתח ממש בקרוב. [01:05] הכירו את ד"ר גיא וייזל ואת חברת Cato Networks גיא משמש כ-Tech Evangelist ב-Cato Networks, תפקיד היושב בתפר שבין קבוצות ה-R&D והמוצר לבין עולם השיווק, החדשנות, ועבודת השטח בעולמות הסייבר וה-AI. קצת על קייטו נטוורקס: החברה, המונה כ-1,800 עובדים (עם מרכז פיתוח גדול בתל אביב), חלוצה בקטגוריית ה-SASE (Secure Access Service Edge). הפלטפורמה מספקת איחוד של רשת ואבטחה כשירות בענן - מעין "כיפת ברזל" לסניפים ומשתמשים של ארגונים ברחבי העולם. במקום להסתמך על ריבוי מוצרי נקודה (Point Solutions), הארגון מקבל תמונה מלאה וקונטקסט רחב על הכל תחת פלטפורמה אחת (הכוללת SD-WAN, DLP, CASB, Zero Trust ועוד). [06:07] עידן ה-"Mytus Moment" והשפעת ה-AI על מתקפות סייבר רן מזכיר מודל מיתולוגי ומתקדם ממשפחת Claude של Anthropic שמסוגל לאתר ולנצל פרצות אבטחה ביעילות מפחידה. גיא מתאר את המצב כ-"The Mytus Moment" – סמן לתעשייה על כניסתם של מודלים מתקדמים (מבית אנתרופיק, OpenAI ואחרים) שמייצרים קפיצת מדרגה בעולם התקיפה (ראו גם: Cato joins OpenAI's Trusted Access for Cyber TAC). מה בעצם משתנה בפועל? מתודולוגיות התקיפה עצמן (Reconnaissance, Lateral Movement) נותרו דומות, אך ה-Scale והמהירות צמחו משמעותית. ה-AI מצמצם את זמן התגובה מגילוי ה-Zero-day ועד לניצול בפועל – משבועות וחודשים לשעות או דקות. במקום סריקות גנריות (כמו של Script Kiddies), סוכני AI יודעים כעת לתפור וקטורי תקיפה מותאמים אישית למטרה ספציפית, ולשרשר חולשות (Vulnerability Chaining) כדי להתקדם ברשת בצורה עצמאית וחכמה. [16:04] כשה-Agents חובשים כובע לבן: איך משנים את תפיסת ההגנה בדיוק כפי שתוקפים נעזרים ב-AI, ארגוני הסייבר חייבים לאמץ Agents הגנתיים כדי להתמודד עם קצב האיומים החדש. מעבר ממנגנונים מבוססי חתימות (Signatures) לזיהוי אנומליות ופעילות דינאמית מבוססת קונטקסט מלא של המשתמש והרשת. שינוי דרמטי במדדי ההצלחה (SLA) של צוותי אבטחה: המיקוד עובר מ-Time to Patch (זמן תיקון החולשה). להתמקדות ב-Time to Protect (זמן ההגנה הרציפה בסביבת הריצה). יש חשיבות גוברת ל-Shift Right (הגנה על ה-Production בזמן אמת) ולא רק ל-Shift Left. מלכודות לסוכני AI: מחקר של קייטו חשף את WebPromptTrap – פרצת Indirect Prompt Injection חדשה שמדגימה כיצד תוקפים יכולים לחטוף סוכני AI דרך תוכן זדוני המוטמע באתרים. [18:04] מתקפות על תשתיות פיזיות: הבעיה עם פרוטוקול Modbus Modbus הוא פרוטוקול תקשורת ותיק (משנת 1979) המשמש לבקרי תעשייה (PLC ו-SCADA), המפעילים תשתיות פיזיות כמו סכרים, מערכות אנרגיה סולארית, משאבות וצנטריפוגות. הפרוטוקול נעדר אבטחה בסיסית או הצפנה, ולמרות זאת, בשל תהליכי מודרניזציה או טעויות אנוש, הוא נחשף לעיתים ישירות לאינטרנט. מחקר של קייטו שבוצע לאורך 3 חודשים חשף שרכיבי Modbus ב-70 מדינות (ביניהן ארה"ב, צרפת ויפן) נמצאים תחת מתקפות אמיתיות. אילו סוגי מתקפות נצפו על ידי המערכות? איסוף מידע (Reconnaissance). מתקפות מניעת שירות (DoS) שנועדו למנוע מהמפעילים לשלוט בבקר. זיהוי סוג המערכת (Fingerprinting). ניסיונות אקטיביים של כתיבה ל-Registers (זיהו מתקפות מתשתית סינית) במטרה לשנות פיזית פעולות של חיישנים ומנועים. שילוב של יכולות ה-Agentic AI – שיודעות לזהות בקר פתוח ולשגר אקספלויט תוך שניות – יחד עם המצב הגיאופוליטי המתוח, הופכים את האיום על תשתיות לאומיות לממשי ומהיר יותר מאי פעם. האזנה נעימה!

Podcast: Nexus: A Claroty Podcast (LS 32 · TOP 5% what is this?)Episode: Samir Boussarhane on New MITRE Caldera for OT Attack SimulatorsPub date: 2026-04-26Get Podcast Transcript →powered by Listen411 - fast audio-to-text and summarizationSamir Boussarhane, senior cybersecurity engineer at MITRE, joins the Nexus Podcast to discuss some new simulator plug-ins added to Caldera for OT. Caldera for OT is an open-source adversary emulation platform that automates security assessments for operational technology (OT) systems. Samir provides context on a new simulator called the Aloha Water Treatment plant, which emulates a water utility and serves as a training platform for students, engineers, and IT security teams alike. Caldera for OT now also supports protocols such as BACnet, Modbus, and includes an HVAC simulator.Subscribe and listen to the Nexus Podcast here. Access the Aloha Water Treatment simulator.  Medium article on the Aloha Water Treatment simulator.The podcast and artwork embedded on this page are from Claroty, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.

Samir Boussarhane, senior cybersecurity engineer at MITRE, joins the Nexus Podcast to discuss some new simulator plug-ins added to Caldera for OT. Caldera for OT is an open-source adversary emulation platform that automates security assessments for operational technology (OT) systems. Samir provides context on a new simulator called the Aloha Water Treatment plant, which emulates a water utility and serves as a training platform for students, engineers, and IT security teams alike. Caldera for OT now also supports protocols such as BACnet, Modbus, and includes an HVAC simulator.Subscribe and listen to the Nexus Podcast here. Access the Aloha Water Treatment simulator.  Medium article on the Aloha Water Treatment simulator.

An airhacks.fm conversation with Christofer Dutz (@christofer-dutz) about: discussion about Apache PLC4X as the JDBC of industrial automation, the API and SPI architecture with Java service loader for driver discovery, Modbus protocol for HVAC systems and heating devices, PLC4X core API operations including discovery and browsing and reading and writing and subscribing and publishing, multi-language support with PLC4J for Java and PLC4Go for Go and PLC4Py for python and C#, code generation from protocol definitions using language-specific templates, XML-based cross-language unit tests, OPC UA as the Esperanto of industrial protocols versus PLC4X speaking native device protocols, OPC UA overhead causing PLC strain and network congestion, comparison of OPC UA to CORBA and grpc, CORBA IIOP protocol on devices, bidirectional communication for reading sensor data and writing control flags, subscription-based event-driven data collection to reduce PLC polling load, founding ToddySoft to provide commercially supported open source industrial products, the gap between open source libraries and industrial consumption, ToddySoft Connect as bubble-wrapped PLC4X drivers for platforms like Inductive Automation Ignition, eliminating edge gateway boxes on shop floors, native protocol communication reducing network load on 100 Mbit industrial networks, unified namespace concept as JMS for industrial automation, Apache IoTDB as time series database with push queries and callback features, Apache TsFile storage format for writing time series data directly on PLCs, shifting from polling to pushing in industrial data collection, ToddySoft File as C libraries compiled for PLCs, ToddySoft DB as embedded stripped-down IoTDB for edge devices, ToddySoft Edge as the combined platform resembling an application server for industrial automation, Industry 4.0 definition and evolution from manual labor through steam power through PLC automation to connected production, compressed air as a service business model, early failure detection in multi-step production lines, OSGi runtime driver loading, Eclipse Tycho build system difficulties, Kafka Connect PLC connectors, SPS fair in Nuremberg as one of the largest industrial automation fairs, signal theory and Nyquist sampling rate in PLC polling Christofer Dutz on twitter: @christofer-dutz

E3 Tile Chaos to Clean Startup Screens: Organizing CO₂ Racks, Layouts, and a Firmware ‘Oops'Brett Wetzel and Kevin Compass kick off this rowdy Advanced Refrigeration Podcast episode with travel talk and a quick rant about getting an E3 to communicate after an IP change, then jump into turning a messy CO₂ rack tile setup into something actually usable. They walk through creating and reorganizing tile groups (receiver, gas cooler, suction groups, oil separator, cases, etc.), explain why breaking menus down makes troubleshooting faster, and show how to build custom layout/startup screens with the key points techs actually need (pressures, temps, valve %, superheat). Along the way they discover icon management, debate the “misc/other” junk-drawer tabs, fumble through the lack of search, and even start a firmware/display update while joking about what might slam shut if it goes sideways. They finish with a quick Modbus address tip and plans for future E3 training videos.

Copeland E3 Tiles, Layout Stuff, Firmware & Atlanta Hood Rat Sh$t Episode-- 514 E3 Tile Chaos to Clean Startup Screens: Organizing CO₂ Racks, Layouts, and a Firmware ‘Oops'Brett Wetzel and Kevin Compass kick off this rowdy Advanced Refrigeration Podcast episode with travel talk and a quick rant about getting an E3 to communicate after an IP change, then jump into turning a messy CO₂ rack tile setup into something actually usable. They walk through creating and reorganizing tile groups (receiver, gas cooler, suction groups, oil separator, cases, etc.), explain why breaking menus down makes troubleshooting faster, and show how to build custom layout/startup screens with the key points techs actually need (pressures, temps, valve %, superheat). Along the way they discover icon management, debate the “misc/other” junk-drawer tabs, fumble through the lack of search, and even start a firmware/display update while joking about what might slam shut if it goes sideways. They finish with a quick Modbus address tip and plans for future E3 training videos.

www.iotusecase.com#IIoT #Shopfloor #LowCode In dieser Episode des IoT Use Case Podcasts spricht Gastgeber Dr. Peter Schopf mit Thilo Brosinsky, Entwicklungsleiter bei der Peakboard GmbH, und Björn Mutschler, Produktionsleiter bei der Johannes Giesser Messerfabrik GmbH. Thema: Wie eine dezentrale IoT-Low-Code-Plattform Shopfloor-Apps von der Maschinenintegration bis zum Energie- und Produktionsmanagement schrittweise skaliert. Folge 205 auf einen Blick (und Klick):(05:59) Herausforderungen, Potenziale und Status quo – So sieht der Use Case in der Praxis ausPodcast ZusammenfassungGIESSER Messer startete mit einer einfachen Shopfloor-Visualisierung, um Produktionskennzahlen erstmals tagesaktuell und direkt an der Maschine sichtbar zu machen. Die zentrale Herausforderung: geringe Akzeptanz, heterogene Datenquellen (ERP, Maschinen, Energie), fehlende Standards bei Maschinenschnittstellen und die Notwendigkeit, produktionskritische Anzeigen ausfallsicher zu betreiben – ohne Großprojekt oder Cloud-Zwang. Umgesetzt wurde dies mit einer dezentralen IoT-/Low-Code-Architektur: Anwendungen werden im Peakboard Designer per Drag-and-drop (bei Bedarf mit Scripting) erstellt, Daten über OPC UA, Modbus, SQL/ERP angebunden und auf lokale Peakboard Boxen verteilt; der Peakboard Hub dient optional zur zentralen Verwaltung, ohne dass bei Ausfall der Zentrale die Shopfloor-Logik stoppt. Eingesetzt werden u. a. MDE/BDE, Downtime-Tracking, papierarme Auftragssteuerung (ziehende Fertigung) sowie Energiemonitoring bis hin zu Lastmanagement. Für IT/OT-Entscheider zeigt der Use Case: iteratives Skalieren mit geringem Startaufwand, schnelle Integration bestehender OT/IT-Systeme, höhere Transparenz und robuste Betriebsfähigkeit im Werk.-----Relevante Folgenlinks:Peter (https://www.linkedin.com/in/peter-schopf/)Thilo (https://www.linkedin.com/in/thilo-brosinsky-39870766/)Jetzt IoT Use Case auf LinkedIn folgen1x monatlich IoT Use Case Update erhaltenJetzt IoT Use Case auf LinkedIn folgen1x monatlich IoT Use Case Update erhalten

Dive into the latest updates of the SM 800A with version 4.2.4. This episode covers the new communication features for LON devices, the addition of Comm Stats tab, and the importance of strong passwords for compliance. Discover tips and tricks for troubleshooting Ethernet connections and explore the new Modbus options for connecting to HGM-MZ and CO2-MZ.************The Controller Talk Podcast, presented by Danfoss North America, is hosted by Food Retail Tech Support experts Dave Yoder and Chris Brown, highlighting best practices for utilizing Danfoss controls in the supermarket and warehouse industries that you won't find in any manual.Drop us an email with suggestions for topics to cover, questions to answer, or comments to discuss on future episodes!ControllerTalkNorthAmerica@Danfoss.com.For more information and additional episodes of the Controller Talk podcast, visit https://controllertalk.captivate.fm/ Subscribe on Apple Podcasts (https://podcasts.apple.com/us/podcast/controller-talk/id1617965227), Spotify (https://controllertalk.captivate.fm/spotify) and Google Podcasts (https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5jYXB0aXZhdGUuZm0vY29udHJvbGxlcnRhbGs?ep=14).

www.iotusecase.com#OTMonitoring #OTCybersecurity #Anomalieerkennung In Episode 197 des IoT Use Case Podcasts spricht Co-Host Dr. Peter Schopf mit Jan Fischer, Head of Sales bei Rhebo aus Leipzig. Im Mittelpunkt stehen OT-Cybersecurity und der Schutz industrieller Netze in kritischen Infrastrukturen, der Fertigung und der Logistik. Jan erklärt, wie Rhebo Brownfield-Umgebungen passiv überwacht, Anomalien sichtbar macht und warum IT/OT-Konvergenz nicht automatisch bedeutet, beide Welten vollständig zu verheiraten. Es geht um reale Vorfälle aus der Praxis, Social Engineering über LinkedIn, vergessene Assets im Netz und die Frage, welche Rolle KI heute tatsächlich in der OT-Security spielt.Folge 197 auf einen Blick (und Klick):(04:26) Herausforderungen, Potenziale und Status quo – So sieht der Use Case in der Praxis aus(10:01) Lösungen, Angebote und Services – Ein Blick auf die eingesetzten Technologien(27:46) Übertragbarkeit, Skalierung und nächste Schritte – So könnt ihr diesen Use Case nutzenPodcast ZusammenfassungOT-Cybersecurity im Brownfield. Wie Rhebo industrielle Netze passiv absichertIn dieser Folge zeigt Jan Fischer, wie Unternehmen ihre OT-Security pragmatisch auf ein neues Niveau heben, ohne Produktionsnetze oder kritische Infrastrukturen zu gefährden. Die Ausgangslage sind historisch gewachsene Brownfield-Netzwerke mit alten Protokollen wie Profibus oder Modbus, unverschlüsselter HTTP-Kommunikation, vergessenen Druckern oder Raspberry Pis im Netz und verschleppten Updates auf Security-Komponenten.Die Lösung von Rhebo basiert auf passivem Monitoring. Die Software schneidet den OT-Netzwerkverkehr mit, trennt typische von atypischen Musterbildern und meldet Anomalien frühzeitig. Im Rahmen eines Assessments wird die bestehende Infrastruktur durchleuchtet. Auffällig sind etwa ungeplante DHCP-Server, neue Protokolle, Datenströme ins Ausland oder kompromittierte Systeme nach Social-Engineering-Angriffen. Ein Forensik- und Diagnose-Team bewertet die Funde und leitet konkrete Maßnahmen ab, vom Schließen von Einfallstoren bis zum gezielten Nachrüsten von Security.Jan ordnet außerdem aktuelle Entwicklungen wie NIS2, den Cyber Resilience Act und den Wunsch nach europäischen On-Prem-Lösungen ein und erklärt die Grenzen von KI in der OT-Security. Die Episode richtet sich an Betreiber kritischer Infrastrukturen, Fertigungs- und Logistikunternehmen sowie OT-Verantwortliche, die ihre Netze härten und reale Angriffe früh erkennen möchten.-----Relevante Folgenlinks:Peter (https://www.linkedin.com/in/peter-schopf/)Jan (https://www.linkedin.com/in/jan-fischer-a4552b103/)Rhebo Homepage (https://rhebo.com/de/)Jetzt IoT Use Case auf LinkedIn folgen1x monatlich IoT Use Case Update erhalten

Shawn Tierney meets up with Henrik Pedersen and Jacob Abel to learn about OTee Virtual PLCs in this episode of The Automation Podcast. For any links related to this episode, check out the “Show Notes” located below the video. Watch The Automation Podcast from The Automation Blog: Listen to The Automation Podcast from The Automation Blog: The Automation Podcast, Episode 252 Show Notes: Special thanks to Henrik Pedersen and Jacob Abel for coming on the show, and to OTee for sponsoring this episode so we could release it “ad free!” To learn about the topics discussed in this episode, checkout the below links: OTee Virtual PLCs website Schedule an OTee demo Connect with Henrik Pedersen Connect with Jacob Abel Read the transcript on The Automation Blog: (automatically generated) Shawn Tierney (Host): Thank you for tuning back into the automation podcast. Shawn Tierney here from Insights. And this week on the show, I meet up with Henrik Pedersen and Jacob Abel to learn all about virtual PLCs from OTee. That’s o t e e. And, I just thought it was very interesting. So if you guys have ever thought about maybe running virtual PLCs to test some processes out, I think you’ll really enjoy this. With that said, I wanna welcome to the show for the very first time, Hendrik and Jacob. Guys, before we jump into your presentation and learn more about what you do, could you first introduce yourself to our audience? Henrik Pedersen (OTee): Yeah. Sweetly. So my name is Hendrik. I am the cofounder, COO, OT, a new industrial automation company, that, we’re really glad to present here today. I have a background from ABB. I worked eleven years at ABB. In terms of education, I have an engineering degree and a master degree in industrial economics. And, yeah, I’m I’m excited to be here. Thanks, Rom. And I’ll pass it over to Jake. Jacob Abel (Edgenaut): I’m, Jacob Abel. I’m the principal automation engineer at Edgnot. EdgeNaught is a systems integrator focusing on edge computing and virtual PLCs. My background is in mechanical engineering, and I’m a professional control systems engineer, and I have thirteen years experience in the machine building side of industrial automation, specifically in oil and gas making flow separators. And I’ll hand it back to Henrik here. Henrik Pedersen (OTee): K. Great. So OT, we are a a new industrial automation company, the new kid on the block, if you will. We’re a start up. So, we only started, about three years ago now. And, we focus solely on virtual PLCs and and the data architectures allow you to integrate virtual PLCs in in operations. And, you know, some of the listeners will be very familiar with this first, thing I’m gonna say, but I think it’s valuable to just take a take a little bit step back and and remember what has happened in in history when when it comes to to IT and OT and, and and what really what really happened with that split. Right? So it was probably around the ‘9 you know, around nineteen nineties where the the the domain computer science were really split into these two domains here, the IT and OT. And, and that, that was, that was kind of natural that that happened because we got on the, on the IT side of things, we got Internet, we got open protocols and, you know, we had the personal computers and innovation could truly flourish on the IT side. But whereas on the OT side, we were we were kind of stuck still in the proprietary, hardware software lock in situation. And and that has that has really not been solved. Right? That that that is still kind of the the situation today. And it this is what this is obviously what also, brought me personally to to really got really super motivated to solve this problem and and really dive deep into it. And I experienced this firsthand with with my role in NAD and, how how extremely locked we are at creating new solutions and new innovation on the OT side. So so we’re basically a company that wants to to truly open up the the the innovation in this space and and make it possible to adopt anything new and new solutions, that that sits above the PLC and and, you know, that integrate effectively to to the controller. So I I have this this, you know, this slide that kind of illustrates this point with with some some, you know, historical events or or at least some some some big shifts that has happened. And, Aurene mentioned a shift in nineteen nineties. And it wasn’t actually until ’20, 2006 that Gartner coined this term OT, to explain the difference really what what has happened. And and, you know, as we know, IT has just boomed with innovation since since the nineties and OT is, is, is slowly, slowly incrementally getting better, but it’s still, it’s still the innovation pace is really not, not fast. So, this is also, of course, illustrated with all the new developments in in GenAI and AgenTic AI, MCP, and things like that that is kinda booming on on the IT side of things. And and and yeah. So, but we do believe that there is actually something happening right now. And and we have data that they’re gonna show for for that. Like, the the large incumbents are now working on this as well, like virtual PLCs, software defined automation and all kinds of exciting things going on on the OT side. So we do believe that that we will see, we will see a shift, a true big shift on the OT side in terms of innovation, really the speed in which we can, we can improve and adopt new solutions on the OT side. And this is kind of exemplified by, like, what what is the endgame here? Like, you could say that the endgame could be that IT and OT once once again becomes the same high paced innovation domain. Right. But then we need to solve those underlying problems, the infrastructural problems that are still so persistent on the OT side of things. The fine point of this slide is to just illustrate what’s happening right now. It’s like cloud solutions for control is actually happening. Virtual PLC, software based automation, AI is happening all at once. And we see it with the big suppliers and and also the exciting startups that’s coming into this space. So I think there’s there’s lots of great excitement now that we can we can expect from the OT side, in in next few years. Shawn Tierney (Host): Yeah. You know, I wanna just, just for those listening, add a little, context here. If we look at 1980, why was that so important? Why is this on the chart? And if you think about it, right, we got networks like Modbus and, Data Highway in nineteen seventy eight, seventy nine, eighty. We also got Ethernet at that time as well. And so we had on the plant floor field buses for our controls, but in the offices, people were going to Ethernet. And then when we started seeing the birth of the public Internet, right, we’re talking about in the nineties, people who are working on the plant floor, they were like, no. Don’t let the whole world access by plant floor network. And so I think that’s where we saw the initial the the divide, you know, was 1980. It was a physical divide, just physically different topologies. Right? Different needs. Right? And then and and as the Internet came out in the early nineties, it was it was now like, hey. We need to keep us safe. We know there’s something called hackers on the Internet. And and I think that’s why, as you’re saying in 2006, when Gartner, you know, coined OT, we were seeing that there was this hesitant to bring the two together because of the different viewpoints and the the different needs of both systems. So I think it’s very interesting. I know you listeners, you can’t see this, but I kinda want to go back through that and kinda give some context to those early years. And and, you know, like Henrik says, you know, now that we’re past all that, now that we’re using Ethernet on the plant floor everywhere, right, almost everywhere, on all new systems, definitely, that that becomes the right now on this on the today on the, on the chart. And I’ll turn it back to you, Henrik. Henrik Pedersen (OTee): Yeah. I’ll search that. I just wanna echo that as I think that there are really good reasons for why this has happened. Like, the there has you could argue that innovation could flourish on the IT side because there was less critical systems, right, less, more, you know, you can do to fail fast and you can do, you can test out things on a different level. And so so there’s really lots of good reasons for why this has happened. We do believe that right now there is some really excitement around innovation, the OT side of things and and this pent up kind of, I wouldn’t call it frustration, but this pent up potential, I think is the right word, is is can be kind of unleashed in our industry for for the next, next decade. So so we are like this is really one of the key motivators for me personally. It’s, like, I truly believe there’s something truly big going on right now. And and I I do I do encourage everyone, everyone listening, like, get in get in on this. Like, this is happening. And, you know, be an entrepreneur as well. Like, build your company, build and, you know, create something new and exciting in this space. I think I think this is this is a time that there hasn’t been a better time to create a new new technology company or a new service company in this space. So this this, this is something at least that motivates me personally a lot. So let me move over to kind of what we do. I mentioned I mentioned that we focus solely on the virtual PLC. This this is now presented in the slide for those that are listening as a as a box inside a open hardware. We can deploy a virtual PLC on any, ARM thirty two thirty two and and sixty four bit processor and x eighty six sixty four bit with the Linux kernel. So so there are lots of great, options to choose from on the hardware side. And and, and yeah. So you can obviously when you have a Virtual PLC you can think of it new in terms of your system architecture. You could for instance, you know deploy multiple Virtual PLCs on this on the same hardware and you can also, think about it like you can use a virtual PLC in combination with your existing PLCs and could work as a master PLC or some kind of optimization deterministic controller. So it’s it’s really just opening up that, you know, that architectural aspect of things. Like you can think new in terms of your system architecture, and you have a wide range of hardware to choose from. And, and yeah, So the the flexibility is really the key here, flexibility in how you architect your system. That CPU that you deploy on will will obviously be need to be connected to to the field somehow, and that’s that’s true, classical remote IO, connections. So we currently support, Modbus TCP and Ethernet IP, which is kind of deployed to to, our production environment, as it’s called. So moving on to the next slide. Like, this is kind of the summary of our solution. We have built a cloud native IDE. So meaning anyone can can basically go to our website and log in to into the solution and and give it a spin. And, we’ll show you that afterwards with with Jake. And the system interacts through a PubSub data framework. We use a specific technology called NUTS, for the PubSub communication bus. And you can add MQTT or OPC UA to the PubSub framework, according to your needs. So, and from that, you can integrate with, whatever whatever other, software you might have, in your system. So we have these value points that we always like to bring up. Like, this obviously breaks some kind of vendor lock in in terms of the hardware and the software. But it’s also, our virtual PLC is based on on the six eleven thirty one. So it’s not a lock in to any kind of proprietary programming language or anything like that. There is, there’s obviously the cost, element to this that you can potentially save a lot of cost. We have, we have verified with with with some of our customers that they estimate to save up to 60% in total cost of ownership. This is there is obviously one part is the capex side and the other part is is the opex. And and is this data framework, as I mentioned, is in in in which itself is is future proof to some extent. You can you can integrate whatever comes comes in in a year or or in a few years down the line. And, there’s environmental footprint argument for this as you can save a lot on the on the infrastructure side. We have one specific customer that estimates to save a lot on and this this particular point is really important for them. And then final two points is essentially that we have built in a zero trust based security, principle into this solution. So we have role based access control. Everything is encrypted end to end, automatic certification, and things like that. The final point is, is that this is the infrastructure that allows you to bring AI and the classical, DevOps, the the thing that we’re very used to in the IT side of things. Like, you you commit and merge and release, instead of, instead of the traditional, way of working with your automation systems. So I know this is like, this is pro pretty much, like, the boring, sales pitch slide, but, but, yeah, I just wanted to throw this this out there for for the guys that there is some there is some, intrinsic values underneath here. The way the system works, you will you will see this very soon, through the demo, but it’s basically you just go to a website, you log in, you create a project. In there, you would create your your PLC program, test, you code, you simulate. You would onboard a device. So onboard that Linux device that you you want to deploy on. This can be as simple as a Raspberry Pi, or it can be something much more industrial grade. This depends on on on the use case. And then you would deploy services like, as I mentioned, MQTT and OPC UA, and then you would manage your your your system from from the interface. And, I have this nice quote that we got to use from one of the customers we had. This is a global, automotive manufacturer that, basically tells us that it’s, they they highlighted the speed in which you can set this up, as as one of the biggest values for them, saving them a lot of hours and setting setting up the system. So I also wanted to show you a real you know, this is a actual real deployment. It was it was deployed about a year ago, and this is a pump station, or a water and wastewater operator with around 200 pump stations. They had a mix of of Rockwell and Schneider PLCs, and they had a very high upkeep, and they were losing a lot of data from these stations because they were connected over four g. When the Internet was a bit poor, they lost a bit of data in their SCADA systems, so they had these data gaps and things like that. So pretty pretty, you know, standard legacy setup to be to be honest. Quite outdated PLCs as well. So what they what they did for the first, pump station was they they, you know, removed the PLC. They put in a Raspberry Pi for for, like, €60 or, like, $70, connected it to to a to a remote IO Ethernet IP module they had, in in the storage, and deploy this data framework as I’m showing on the screen now. So so they that was that was the first station they put online, and they they chose a Raspberry Pi because they thought, okay, this is interesting, but will it work? And then they chose a pump station, which was was really just poor from before. So they had very little to to to lose to to deploy on this station. So so, yeah, this has been running for a year now without any any problems on a Raspberry Pi. We have obviously advised against using a Raspberry Pi in a critical environment, but they just insisted that that what that’s what they wanted to do for this first case. Shawn Tierney (Host): And I’ll back that up too. Your generic off the shelf Raspberry Pi is just like a generic off the shelf computer. It’s not rated for these type of environments. Not that all pump houses are really bad, but they’re not air conditioned. And I think we’ve all had that situation when it’s a 120, 130 out that, you know, off the shelf computer components can act wonky as well as when they get below freezing. So just wanted to chime in there and agree with you on that. For testing, it’s great. But if you’re gonna leave it in there, if you were in my town and you say you’re gonna leave that in there permanently, I would ask to have you, assigned somewhere else for the town. Henrik Pedersen (OTee): Yeah. Yeah. Exactly. No. So and and that point is also illustrated with the second station they brought online. So there they chose a much more industrial grade CPU, that, that, was much, you know, cost cost a bit more, but it’s more suited for the environment. And, and yeah. So this was, I can disclose it was a Bayer Electronics, CPU. So so yeah. And, and they reported, some good, good metrics in terms of, like, the results. They they said around 50 on the hardware, 75% on the management of the PLC system. So this relates more to that they have very a lot of, you know, driving out with the car to these stations and doing changes to their systems and, and updates. They no longer have any, any data loss. It’s local buffer on the data framework. They’ve increased tag capacity with 15 x, resulting in in four fifty five x better data resolution and a faster scan frequency. And this is actually on the Raspberry Pi. So so just just think of it as as the the even the even the, kind of the lowest quality IT off the shelf, computers, are are able to to, to execute really fast in in in, or fast enough for for, for these cases. So, Shawn, that was actually what I wanted to say. And, and also, you know, yeah, we are we are a start up, but we do have, fifth users now in 57 different countries across the world. And it’s it’s really cool to see our our our, our technology being deployed around the world. And, and yeah. I’m really, really excited to to, to get more, users in and and hear what they what they, think of the solution. So so yeah. I’ll I’ll with that, I don’t know if, Shawn, you wanna you shoot any questions or if we should hand it over to Jake for for for a demo. Shawn Tierney (Host): Yeah. Just before we go to Jake, if somebody who’s listening is interested, this might be a good time. It said that, you already talked about being cloud based. It’s, o t e e. So Oscar Tom, Edward Edward for the the name of the company. Where would they go if if they like what Jake’s gonna show us next? Where will they go to find out more? Henrik Pedersen (OTee): Yeah. So I would honestly propose that they just, reach out to to me or Jake, on on one of the QR codes that we have on the presentation. But they can also obviously go to our website, 0t.io,0tee.io, and just, either just, log in and test the product, or they could reach out to us, through our website, through the contact form. So yeah. Shawn Tierney (Host): Perfect. Perfect. Alright, Jake. I’ll turn it over to you. Jacob Abel (Edgenaut): Thanks, Shawn. Fantastic stuff, Henrik. I wanna take a second too to kinda emphasize some of the technical points that you, presented on. Now first, the the fact that you have the built in zero trust cybersecurity is so huge. So, I mean, the OT cybersecurity is blowing up right now. So many certifications, you know, lots of, consulting and buzz on LinkedIn. I mean, it’s a very real concern. It’s for a good reason. Right? But with this, zero trust built in to the system, I I mean, you can completely close-up the firewall except for one outgoing port. And you have all the virtual PLCs connected together and it’s all done. You know, there’s no incoming ports to open up on the firewall to worry about, you know, that security concern. You know, it’s basically like, you know, you’ve already set up a VPN server, if you will. It’s it’s not the same, but similar and, you know, taking care of that connection already. So there’s an immense value in that, I think. Shawn Tierney (Host): And I wanted to add to the zero trust. We’ve covered it on the show. And just for people, maybe you’ve missed it. You know, with zero trust is you’re not trusting anyone. You authorize connections. Okay? So by default, nobody’s laptop or cell phone or tablet can talk to anything. You authorize, hey. I want this SCADA system to talk to this PLC. I want this PLC to talk to this IO. I want this historian to talk to this PLC. Every connection has to be implicitly I’m sorry. Explicitly, enabled and trusted. And so by default, you know, an an integrator comes into the plant, he can’t do anything because in a zero trust system, somebody has to give him and his laptop access and access to specific things. Maybe he only gets access to the PLC, and that makes sense. Think about it. Who knows whether his laptop has been? I mean, we’ve heard about people plug in to the USB ports of the airport and getting viruses. So it’s important that person’s device or a SCADA system or a historian only has access to exactly what it needs access to. Just like you don’t let the secretary walk on the plant floor and start running the machine. Right? So it’s a it’s an important concept. We’ve covered it a lot. And and, Jake, I really appreciate you bringing that up because zero trust is so huge, and I think it’s huge for OT to have it built into their system. Henrik Pedersen (OTee): Yeah. Absolutely. Absolutely. Jacob Abel (Edgenaut): I wanted to highlight too the Henrik mentioned that the the backbone of the system is running on a technology called NATS. That’s spelled n a t s. And why that’s important is this is a a lightweight messaging, service, and it’s designed to send millions of messages per second. You know, that’s opposed to, you know, probably the best Modbus TCP device that you can find. You might get a couple 100 messages through per second. It’s millions of messages per second. It’s, you know, especially with, you know, we’re dealing with AI machine learning, you know, training models. I mean, we’re data hungry. Right? So this gives you the backbone too. You know, it’s like it can push an immense amount of tag data, you know, with ease. I think that’s another really important point. With that, though, I’ll I’ll get on to the demo. Henrik Pedersen (OTee): Oh, that’s great. We do we do see that, Jay, that most of our customers report on that, you know, 400 or 700 x better data resolution. And so it’s it’s a step change for for for the data resolution there. Yeah. Jacob Abel (Edgenaut): Excellent. So one of the things that I personally love about OT is how quickly you can get into the PLC once everything’s set up. So this is OT’s website, obviously, ot.io. So once you’re here, you just go to log in. And that brings in the login screen. Now I’m are I’m using my Google account for single sign on, so I can just click continue with Google. And this brings me into the main interface. And another thing that I love is that, you know, it is very simple and straightforward, you know, and simple is not a bad thing. Simple is a good thing. I mean, the way that things should be is that it should be, it should be easy and the finer details are taken care of for you. So right here, we have our main project list. I just have this one benchmarking program that I’ve imported in here. And you also have device lists, just a a test device that I’ve installed the runtime on. Just real quick. You know, you have a Martha, the AI assistant in the corner here. And, the documentation guides is up here. So you can get help or look into reference material very easily. It’s all right there for you. So I’m gonna open up this program here. So just a quick tour here. Right up here in the top left is basically where where most everything’s done. So if you click on this little down arrow, you can choose what virtual PLC runtime to attach it to. I’ve already attached it to the device. I installed the runtime on. You can add, you know, a new program, driver, function blocks, custom data types real quick here. Compile your program, download it to the device. Check the release history, which is really, really great. As you can, you can go into release history and you can revert to a prior version very easily. We got built in, version control, which is another, great feature. Henrik Pedersen (OTee): I can also just comment on that, Jake, that we do have we do have, in the quite short term roadmap to also expand on that with Git integration, that, a lot of our customers are are asking for. So yeah. Jacob Abel (Edgenaut): Awesome. Yeah. I mean, that’s that’s another, very hot topic right now. It’s, you know, getting getting the revision control systems, as part of, you know, at least the textual, programming languages. See, so, you know, we have a few, like, housekeeping things here. I mean, you can delete the program, export it. It’s a good good point here is that, OT complies with the PLC open, XML specification. So you can import or export programs, in this XML format, and it should work with solid majority of other automation software out there. You know, if you need to, you want to transition over to OT, you know, you can export it from your other software and import it rather easily. Got your program list here and, you know, just the basic configuration of, you know, you can add global variables that you wanna share between the different programs and POUs or, you know, change the, cycle rate of the periodic tasks, add more tasks. Let’s just get jump into this program here. Both the system uses the IEC sixty one one thirty one dash three standard structured text. So here’s just a little, quick benchmark program that I’ve been using to do some performance testing. Like you, you have the, the code right here, obviously. And on our, our right, the variable list, very easy to add a new variable and pick out the type. You can set a set of default value, add some notes to it. Super easy. So let’s go online. So if you have these little glasses up here in the top, right, you display live tag values. And so it’s grabbing from the runtime that’s running and plopping it right in here in the editor, which I I love the way it’s displayed. It makes it. And, you know, it’s one of the question marks is if you’re doing structured text instead of letter logic, like how it’s gonna show up and how readable is it gonna be. I think the, the text, like the color contrast here helps a lot. It’s very, very readable and intuitive. And we also have the tag browser on the right hand side. Everything is, organized into, you know, different groups. There’s the the resources and instances that you’ve set up in the configuration tab. So the by default, the tag the tags are all listed under there. And here too, you know, you can set tag values doing some performance testing, as I said. So this is, recording some some jitter and task time metrics. And that’s that’s really it. That’s the that’s the cloud IV in a nutshell. Super easy, very intuitive. I mean, it’s there there’s zero learning curve here. Shawn Tierney (Host): For the, audio audience, just a little comment here. First of all, structured text to me seems to be, like, the most compatible between all PLCs. So, you know, everybody does ladder a little bit differently. Everybody does function blocks a little bit differently. But structured text and, again, I could be wrong if you guys think out there in the in listening, think I’m wrong about that. But when I’ve seen structured text and compared it between multiple different vendors, it always seems to be the closest from vendor to vendor to vendor. So I can see this makes a great a great place to start for OT to have a virtual PLC that supports that because you’re gonna be able to import or export to your maybe your physical PLCs. The other thing is I wanted to comment on what we’re seeing here. So, many of you who are familiar with structured text, you know, you may have an if then else, or an if then. And and you may have, like, tag x, equals, you know, either some kind of calculation, you know, maybe, you know, z times y or just maybe a a constant. But what we’re seeing here is as we’re running, they have inserted at a in a different color the actual value of, let’s say, tag x. So in between you know, right next to tag x, we see the actual value changing and updating a few times a second. And so it makes it very easy to kinda monitor this thing while it’s running and see how everything’s working, and I know that’s that’s huge. And I know a lot of vendors also do this as well, but I love the integration here, how it’s so easy to see what the current values are for each of these variables. And, I’ll turn it over to you, Hendrick. I think I interrupted you. Go ahead. Henrik Pedersen (OTee): Yeah. No. I was just gonna comment on that. Jake said, like, this is the this is the POC editor, and the next the next big feature that we’re releasing very soon is essentially the service, manager, which is the, which is the feature that will allow our users to deploy any kind of service very efficiently, like another runtime or OPC UA server or an entity server or or or whatever other, software components that that, you want to deploy, like a Knox server or things like that. So and that’s that’s, we were really excited about that because, that will kind of allow for a step change in how you kind of orchestrate and manage your system and your, your system and your, your, you have a very good overview of what’s going on with versions of, of the different software components running in your, your infrastructure and your devices and things like that. So we’re really excited about that, that it’s coming out. And it might be that actually when when this, episode airs, who knows if it’s if it’s done or or not, but we’re very close to release the first version of that. So excited about that. Shawn Tierney (Host): Now I have a question for you guys, and maybe this is off topic a little bit. So let’s say I’m up here in the cloud. I’m working on a program, and I have some IO on my desk I wanna connect it to. Is that something I can do? Is there a connector I can download and install my PC to allow the cloud to talk to my IO? Or is that something where I have to get a a, you know, a local, you know, like we talked about those industrial Linux boxes and and test it here with that? Henrik Pedersen (OTee): Yeah. So I think you what you what you’re you’re after is, like, the IO configuration of, if you wanna deploy a driver, right, or, like, a modbus driver and how you figure out the system. Right? Shawn Tierney (Host): Yeah. Because this is in the cloud. It’s not on my desk. The IO is on my desk. So how would I connect the two of them? How would I is is that something that can be done? Henrik Pedersen (OTee): Yep. Yeah. Exactly. That’s that’s actually the you know, I I think, Jake, you might just wanna show why you deploy a driver. Right? Jacob Abel (Edgenaut): Sure. Sure. And I just wanna take a second to, clarify. You know, it’s something that kinda comes up often, and I I don’t I don’t think it gets it’s it’s cleared up enough is that so, you know, we have this cloud ID here. So, you know, you can open this from anywhere in the world. But the virtual PLC run times get installed on computers preferably very locally, you know, on the machine, on the factory floor, something like that. I I’ve got, an edge computer right here. Just as an example. I mean, this is something you would just pop in the control panel and you can install OT on this. So to answer your question better, Shawn, you know, to get to, you know, the remote IO that you need essentially, or actually in the, in the case of this, this has onboard IO. You know, you’re looking at connecting with MOBAs, PCP, Ethernet IP. I I know that a lot more protocols are coming. Profinet. So how you would do that is that you have that plus sign up here and add a driver config. We’re just gonna do, Modbus real quick. Henrik Pedersen (OTee): Mhmm. Jacob Abel (Edgenaut): And we wanna add a TCP client. So you can name the client, tell it how fast to pull, you know, any delays, put in the IP address. Just an example. Do the port number if you need and then add your requests. You know, you have support for, all the main function codes and mod bus right here, you know, read holding, read input, you know, write multiple coils, all that good stuff, you know, tell address how many registers you wanna do, timeouts, slave ID. And then, you know, once you’ve done that, so let’s say, you know, I’m gonna read, and holding registers here, the table on the right auto updates. You can do aliases for each one of these. You can just do register one Mhmm. As an example Shawn Tierney (Host): It’s showing just for the audio audience, it’s showing the absolute address for all these modbus, variables and then, has the symbols, and he’s putting in his own symbol name. It has a default symbol name of symbol dash something, and he’s putting his own in, like, register one, which makes it easier. Yeah. Jacob Abel (Edgenaut): Good point. Yeah. Good point. Thanks, Shawn. So, yeah, once once you put in your request and you can throw in some aliases, for the different registers, you know, you can go back to your program and here’s this, sample variable that I just added from earlier. You know, you can the registers are 16 bits. I’m gonna select, an int. And what you can do here now is select those modbus requests that you just set up. So it automatically maps these to those variables for you. So that that way you don’t have to do anything anything manual, like have a separate program to say, you know, this tag equals, you know, register 40,001. You know, it’s already mapped for you. So that’s that’s essentially how you would connect to remote IO is, just add a client in the driver configs and, fill in all your info and be off and running. Shawn Tierney (Host): That’s excellent. I really liked how you were able to easily map the register to the modbus value you’re reading in or writing to to your, variable so you can use that in your program. That was very easy to do. Jacob Abel (Edgenaut): Oh, yeah. Yeah. It’s that it’s like I said, that’s one of the things that I love about this interface is that everything is just very straightforward. You know, it’s it’s super easy to just stumble upon whatever it is you need and figure it out. Henrik Pedersen (OTee): And just just, to add to to kinda your your processors, like, once you have created that connection between the IO and and and the program, you basically just, compile it and download it to the to the runtime again, and and it executes locally the based on the yeah. Nice. Jacob Abel (Edgenaut): Oh, right. Good point. Yeah. Of of course, after we add something, we do have to redownload. So Shawn Tierney (Host): Very interesting. Well, that answers my question. Jacob Abel (Edgenaut): I think that’s that’s about it for the the demo. I mean, unless, Shawn, you have any more questions about the interface here. Shawn Tierney (Host): No. It looked pretty straightforward to me, Hendrik. I don’t know. Did you have anything else you wanted to discuss while we have the demo up? Henrik Pedersen (OTee): Nope. Not nothing related to this except for that, you know, this is probably something that’s quite new in the OT space is that this is a software service, meaning that there are continuous development going on and releases, and improvements to the software all the time. Like literally every week we deploy new improvements. And, and what, I typically say is that like, the, you know, if you if you if you sign up with OT, what you what you will experience is that the actual software keeps on becoming better over time and not is not going to become outdated. It’s going to be just better over time. And I think that’s part of what I really loved about the innovation space, innovation happening around IT is that that, that has become the new de facto standard in how you develop software and great software. And I think we in, in, in the OT space, we need to adopt that same methodology of developing software, something that continuously becomes better over time. Shawn Tierney (Host): Yeah. And I would just say, you know, if you’re if you’re on the OT side of things, you wanna be in six eleven thirty one dash three languages, because these are things that your staff, you know, what you know, your electricians and technicians and even engineers, you know, should know, should be getting up to speed. I don’t know. We’re at the automation school. We’re teaching, structured text. And so, easier. I look at this, and I’m like, this is a lot easier than trying to learn c plus or or JavaScript. So in any case, I think, you know, if it’s an OT side real IO control, real control system or data collection, you know, you know, very important, you know, mission critical data collection, then, you know, I’d rather have this than somebody trying to write some custom code for me and, you know, use some kind of computer language who doesn’t understand, you know, the OT side of things. So, I could definitely see the advantage of your system, Henrik. Henrik Pedersen (OTee): Yep. I I I also wanted to say to that, Stike, the I I do not believe the EIC standards in general will disappear. They exist for a very good reason. Right. Exists to standardise to to ensure safety and determinists, determinism in this. So I don’t think they will disappear. But there are obviously advances now with AI and things like that that can can help us create these things much faster and much more efficient and things like that. So, so but, but the EIC standards, I think, will be there for a very long time. Obviously, the 06/4099 standard is is really exciting, and and we believe that that can be, yeah, that that can clearly be there, but it’s still a new EIC standard. So, Shawn Tierney (Host): it’s not think what we’re gonna see is we’re gonna see a lot more libraries fleshed out. There’ll be a lot less writing from scratch. We’ve interviewed on the History of Automation podcast. We’ve interviewed some big integrators, and they’re at a point now, you know, twenty, thirty years on that they have libraries for everything. And I think that’s where we’ll see, you know, much like the DCS, I think, vendors went two years ago. But I still think that the there’s a reason for these languages. There’s a reason to be able to edit things while they run. There’s a reason for different languages for different applications and different, people maintaining them. So I agree with you on that. I don’t I don’t think we’re we’re gonna see the end of these, these standard languages that have done us very well since the, you know, nineteen seventies. Jacob Abel (Edgenaut): I just wanna add a bit on there about, Shawn, you mentioned, you know, doing less code. I I did show earlier in the bottom right hand corner here, we have our our little AI assistant, Martha. I don’t believe the feature, it has been released yet. You know, Henrik, correct me if I’m wrong, but I know one of the things that’s coming is, AI code generation, you know, similar to that of cloud or chat GPT. So it’s going to, you know, you can open this guy up here. You know, right right now, I think it’s just for, help topics, but you’ll be able to talk to Martha and she’s gonna generate code for you in your program there all built in. Henrik Pedersen (OTee): Yeah. Yeah. That’s that’s coming really fast now. So, it’s it’s not been implemented yet, but it’s, it’s right around the corner. Shawn Tierney (Host): Yeah. And it’s it’s not gonna be able to it’s you’re not gonna be able to hook a camera up to it and, like, take pictures of your machine and say, okay. Write the control code for this. But, you know, if you had a, you know, process that had 12 steps in it, the AI could definitely help you generate that code and and other code. And we’ll have to have Henrik and Jake back on to talk about that when it comes out, but, you know, it’s gonna be able to save you, reduce the tedious part of the the coding. You know, if you need an array of so many tags and so many dimensions or, you know, the stuff that, you know, it would just be the typing intensive, it’s gonna be able to help you with that, and then you can actually put the context in there. Just like, you can pull up a template in Word for a letter, and then you can fill in the blanks. You know? And and, of course, AI is helping make that easier too. But, in any case, Henrik, maybe you can come back on when that feature launches. Henrik Pedersen (OTee): Yeah. Absolutely. And I’m also excited about just a simple a use case of of translating something. Right? Translating your existing let’s say if it’s a proprietary code or something like that, like, getting it getting it standardized and translating it to the ESE six eleven thirty one standard, for instance, or, so so the obviously AI is, like, perfect for this space. It’s there is no doubt, And and it’s, like, that’s also why I’m so excited about, like, what’s going on at the moment. It’s like there’s so much innovation potential, in the on the OT side now that, they are with all these new technologies. Shawn Tierney (Host): Yeah. Absolutely. Absolutely. Well, gentlemen, was there anything else you wanted to cover? Henrik Pedersen (OTee): I think just just one final thing from from me is, like, we thought a lot about it, like, before this this episode, and we thought, like, let’s offer let’s offer the listeners something something of of true value. So so we thought, the, you know, after this after this episode launched, we want to want to offer anyone out there that’s listening a free, completely hands on trial of our technology, in their in their in their environment or on their Raspberry Pi or whatever. So just just reach out to us if you wanna do that. And, and I yeah. We’ll get you set up for for for testing this, and it’s not gonna cost you anything. Shawn Tierney (Host): Well, that’s great. And, guys, if you’re listening, if you do take advantage of that free trial, please let me know what you thought about it. But, Henrik, thank you so much for, that offer to our listening audience. Guys, don’t be bashful. Reach out to him. Reach out to Jake. Jake, thank you for doing the demo as well. Really appreciate it. My pleasure. Any final words, Henrik, before we close out? Henrik Pedersen (OTee): No. It’s been great. Great, being here, Shawn, and thanks for for helping us. Shawn Tierney (Host): Well, I hope you enjoyed that episode. I wanna thank Hendrik and Jacob for coming on the show, telling us all about OT virtual PLCs, and then giving us a demo. I thought it was really cool. Now if any of you guys take them up on their free trial, please let me know what you think. I’d love to hear from you. And, with that, I do wanna thank OT for sponsoring this episode so we could release it completely ad free. And I also wanna thank you for tuning back in this week. We have another podcast coming out next week. It’ll be early because I will be traveling and doing an event with a vendor. And so expect that instead of coming out on Wednesday to come out on Monday if all goes as planned. And then we will be skipping the Thanksgiving, week, and then we’ll be back in the in the, in December, and then we have shows lined up for the new year already as well. So thank you for being a listener, a viewer, and, please, wherever you’re consuming the show, whether it’s on YouTube or on the automation blog or at iTunes or Spotify or Google Podcasts or anywhere, please give us a thumbs up and a like or a five star review because that really helps us expand our audience and find new vendors to come on the show. And with that, I’m gonna end by wishing you good health and happiness. And until next time, my friends, peace. Until next time, Peace ✌️  If you enjoyed this content, please give it a Like, and consider Sharing a link to it as that is the best way for us to grow our audience, which in turn allows us to produce more content

In this episode of the Lighting Controls Podcast, Webster and Ron welcome back Umesh Baheti, SVP of Product and Engineering at MaxLite, to dive deep into the evolving world of lighting controls and smart building integration. Here's what you'll discover: 

Zastanawiałeś się, jak przeszliśmy od fabryk tonących w kablach (80% kosztów projektu!) do nowoczesnych sieci Profinet? W tym odcinku śledzimy ewolucję magistral polowych (Fieldbus).

Totex co-founder Berlin Raj joins Eric and “Overkill Bill” to unpack a single-box, hydronic monoblock system that combines space conditioning, domestic hot water, pool heating, thermal + lithium storage, EV charging integration, and backup power. Born from Berlin's lifelong tinkering (and many shocks), the idea: stop wasting condenser heat—capture it for hot water while cooling. The system keeps all refrigerant sealed in the outdoor unit and runs PEX supply/return to indoor air handlers (ducted or ductless), avoiding field flares and refrigerant line runs. Install looks familiar—set the pad, pipe PEX, fill a glycol loop, wire power/control—yet it adds clever tricks: load matching from ~1.5–6 tons, dynamic load limiting for small panels (even ~20–30A circuits), modular thermal storage (~100 kWh cooling / ~55 kWh heating), a ~10.5 kWh lithium pack, and app/10" touchscreen controls over Modbus with hooks for BMS and home automation. In cooling-plus-hot-water mode, field tests show very high effective COP (Berlin cites “9+”) because the unit harvests both sides of the cycle. Engineered for residential and light commercial (think houses, small offices, QSRs), the unit can supply hot water up to ~165°F, support radiant/underfloor at lower temps, operate down to about -7.6°F, and be manifolded for capacity and redundancy. Texas is the target U.S. beachhead (long cooling seasons = months of “free” hot water), with pilots in Australia and U.S. pilots planned; broader availability is aimed for mid to late next year. Berlin's closing note? “People, people, people”—comfort and outcomes start with humans. Notable Quotes: “Why dump condenser heat when you can use it? Cool the house and make hot water at the same time.” — Berlin Raj “Dynamic load balancing means a heat pump that plays nice with a 100-amp panel.” — Eric Kaiser (paraphrased) “People, people, people. Comfort is ultimately about humans first.” — Berlin Raj   Berlin on LinkedIn:https://www.linkedin.com/in/berlinrajm/ Totex website: https://www.totexenergy.com/ Come visit with Berin in person at the www.USHeatPumpSummit.com     This episode was recorded in September 2025.  

www.iotusecase.com#Retrofit #EUDataAct #SinglePairEthernet In Episode 190 des IoT Use Case Podcasts spricht Gastgeberin Ing. Madeleine Mickeleit mit Dr.-Ing. Karsten Walther, Geschäftsführer von Perinet. Thema der Folge ist die praktische Umsetzung des EU Data Act in der Industrie. Es geht um sichere Datennutzung direkt an Anlagen und Geräten, um Brownfield Nachrüstungen mit Modbus und RS485, um Single Pair Ethernet als Brücke in die IP Welt und um realistische Schritte von der sicheren Leitungsverschlüsselung bis zur cloudfähigen Architektur.Folge 190 auf einen Blick (und Klick):(08:44) Herausforderungen, Potenziale und Status quo – So sieht der Use Case in der Praxis aus(27:04) Übertragbarkeit, Skalierung und nächste Schritte – So könnt ihr diesen Use Case nutzenPodcast ZusammenfassungEU Data Act in der Praxis. Wie Hersteller und Betreiber Bestandsanlagen sicher nachrüsten und Gerätedaten nutzbar machen.Die Herausforderung beginnt oft im Feld. Viele Steuerungen sind aus den achtziger Jahren gedacht, sprechen Modbus oder RS485 und haben keine Netzwerkschnittstelle. Datenzugriff ist dennoch gefordert, Transparenz und Sicherheit ebenso.Gleichzeitig dürfen Prozesse nicht stillstehen und Investitionen müssen planbar bleiben. Die Lösung ist ein schrittweiser Retrofit mit klarer Priorität.Zuerst wird die Kommunikation über die bestehende Leitung abgesichert. Adapter vor Feldgerät und Controller übersetzen Modbus in die IP Welt, ermöglichen Verschlüsselung und sauberes Gerätemanagement. Netzwerk Security wird so gestaltet, dass auch Installateure im Feld sicher arbeiten können.Im nächsten Schritt werden einzelne Geräte zu eigenständigen Netzwerkteilnehmern, perspektivisch bis hin zu virtuellen Steuerungen und zentralem Software Rollout. Perinet liefert hierfür passende IoT Hardware wie smarte Adapter und bringt Beratungsleistung für Integration und Security ein.Ergebnis sind sichere, wirtschaftliche und EU Data Act konforme Lösungen mit klarer Roadmap für Brownfield Anlagen. Besonders relevant für Hersteller, Betreiber und Systemintegratoren, die Datenhoheit, Skalierbarkeit und Investitionssicherheit verbinden wollen. Jetzt reinhören und konkrete Schritte für die eigene Nachrüststrategie mitnehmen.-----Relevant links from this episode:Madeleine (https://www.linkedin.com/in/madeleine-mickeleit/)Karsten (https://www.linkedin.com/in/karsten-walther-395822365/)periNODE Smart Adapter (https://www.perinet.io/de/produkte/smart-components/perinode-modbus)IoT-Community (https://iotusecase.com/de/community/)Eu Data Act (https://digital-strategy.ec.europa.eu/de/policies/data-act)Perinet bei der SPS: Halle 5, Stand 332Jetzt IoT Use Case auf LinkedIn folgen1x monatlich IoT Use Case Update erhalten

Shawn Tierney meets up with Lauton Rushford of Endress+Hauser to learn about new innovations in Coriolis Flowmeter Technology in this episode of The Automation Podcast. For any links related to this episode, check out the “Show Notes” located below the video. Watch The Automation Podcast from The Automation Blog: Listen to The Automation Podcast from The Automation Blog: The Automation Podcast, Episode 247 Show Notes: Special thanks to Endress+Hauser for sponsoring this episode so we could release it “ad free!” To learn about Endress+Hauser, and Coriolis Flowmeters, checkout the below links: Learn more about Endress+Hauser Learn more about flowmeter products Read the transcript on The Automation Blog: (automatically generated) Shawn Tierney (Host): Welcome back to the automation podcast. Shawn Tierney here from Insights and Automation, and I wanna thank you for tuning back in. This week on the show, I meet up with Lawton Rushford from Endress and Hauser to learn all about the latest innovations in Coriolis flow meters. And I also wanna thank Endress and Hauser for sponsoring this episode so I could bring it to you completely ad free. With that said, if you’re interested in learning about what’s the latest in technology used in Coriolis flow meters, I think you’ll enjoy this episode. I know I did. And with that, let’s go ahead and jump right into this week’s show. I wanna welcome to the show, Lawton from Endress and Hauser. Lawton, it’s great to have you on. This is the first time you’re on the show. We plus, we’ve had your company on before. But, Lawton, if you don’t mind, could you, before we jump into Coriolis flow meters, which is an extremely important technology in our industry, could you first introduce yourself to our audience? Lauton Rushford (E+H): Yeah. Absolutely. Thank you. My name is Lawton Rushford. I am the flow product marketing manager here at Anderson Hauser, based in Greenwood, Indiana, which is about twenty minutes south of Indianapolis, Indiana at our, national headquarters, for Anderson Hauser. I’ve been with Anderson Hauser for seven years now, a whole bunch of different roles, but, for the last three years, I’ve been in this role, a flow marketing manager. Today, I I really wanted to highlight a couple of awesome innovations that we’ve had in Coriolis flow technology, over the last, we’ll see, about year or so, because I think there’s a lot of, use cases and a lot of awesome, insights we can get from from our Coriolis flow meters. And, yeah. So I guess we can we can kick it off. I did wanna highlight Anderson Hauser as the the manufacturer that I work for, and we have a history, a long history of, of innovation. And so I’m gonna kinda highlight that, initially, talk about what sort of portfolio we have currently with our Coriolis flow meters, and then talk about a couple of new cool things that that we have released over the last couple of couple of months. And then finish off with, what we call heartbeat technology. It’s our advanced diagnostic system in all of our flow meters and all of our products across the board. It started with flow. So I think there’s a lot of you cool use cases, and I’ll I’ll highlight a couple of those as well. And then, of course, Shawn is the the audience here. Anytime there’s questions or anything, please feel free to to let me know, and I can I can try and address them as they come up? Shawn Tierney (Host): Sounds good. Yeah. Lauton Rushford (E+H): Awesome. Great. So I guess our first Coriolis meter that we introduced into the market was back in, 1986. So it’s been some time. As you can tell by the the slide here, there’s a lot of different designs of Coriolis flowmeters. There isn’t one right way to do it, but I think that the way that Anderson Houser has approached innovation is is pretty pretty awesome and pretty impressive. Everything from a single tube, design to a dual tube design, dual straight tube design versus a dual bent tube design. There are a lot of different types of Coriolis meters out on the market, and we’ll talk about a couple of, differentiators that we that, Anderson Hauser has on, on some products that we’ve recently released. Shawn Tierney (Host): You know, just by looking at the, the slide here, the one that, like, really attracts my eye is the ProMASS. That’s the one that I I think I’ve seen the most in the field. Lauton Rushford (E+H): Yep. Yep. Shawn Tierney (Host): You know, walking around the different plants, and, that was launched in 1998. So that’s been out for quite some time. So just wanted to throw that out there for those listening. That may be the one you’ve seen the most of as in your in your travels. Lauton Rushford (E+H): Yeah. Yeah. Definitely. There’s a lot of a lot of ProMasses out there. Our endpoint was the first one, but, shortly after that, we released our ProMasses. And we’ve just been you know, we’ve we’ve had a lot of iterations, which I think is also part of the impressive thing in terms of innovation that Anderson Hauser continues to to to, do in terms of research and development on that. And the one that I always think about is is the the one that kinda looks like a UFO. That is our ProMASS X. It’s a high capacity, large diameter, Coriolis meter with four tubes in there. So it’s kind of bent two separate sys systems and then put together in one, large device, and I always I always think that one’s cool because it kinda looks like a like something out of Star Wars or something. Yep. Yep. So, yep, so I I think that’s that’s really, really cool. There’s a lot of new things that we’ve released, and this is, I mean, this is a short timeline of of some of the innovations that we have. But, you know, over the last year or so, we’ve we’ve definitely invested a little bit more, into specific applications, and that kind of leads us into our entire portfolio of Coriolis flow meters. We have 17 different sensors. So that is not a normal thing in the industry. I I think that to some people, it it can be confusing if you’re looking at them all at the same time, a little overwhelming. But I I think it’s really important that I that I kind of talk about this in terms of every application that we look at. We’re not trying to put one flow meter into that application. We’re taking the application and the requirements of that application and designing a device that’s meant for it. So, in certain applications, you may not have to choose between 17 different sensors. You really have probably two or three that you’re trying to to decide between and weigh, both pressure drop, accuracy, density specifications, things like that that that will ultimately give you the the best meter for that application. But we we don’t wanna take a an approach of trying to, cram a a sensor into an application. We would prefer to design the sensor in and meant for certain applications. So it does I guess there’s two questions on here. Why so many sensors? Well, because we wanna design our our sensors for specific applications. There’s a lot of different applications out there. Doesn’t that make it confusing? Well, of course, it makes it a little confusing if you’re looking at it from from the high level 17 different sensors. But, every application that we look at, we’re we’re trying to, there’s a lot of different requirements of of applications in oil and gas versus life sciences, and we wanted to design sensors that fit the market and fit the application that they’re supposed to go into. And in general, all of them work the exact same way. As a as a general rule of thumb, your Coriolis flow meter measurements are mass flow, density, and temperature as a as a starting point. We’ll talk about a couple of features that we’ve started adding to some of our flow meters that that, create more of a multivariable device. Instead of just measuring those three things, we can add viscosity or, we can do other things or concentration, things like that, with the meters. But in general, the mass flow is is using, the phase shift between your inlet and outlet pickup coils and taking that into account to relate it directly to the amount of mass that’s within those tubes. And then similarly, as the tubes are oscillating, a more dense fluid is going to have a lower resonant frequency. And based around resonant frequencies, we can understand how dense the fluid is inside of the, inside of those flow tubes. And then we also have on every single one of our Coriolis flow meters, PT 1,000, temperature probe that’s attached directly to the inside of the, the outside of the tube within the secondary containment, for additional values, additional multivariable, use uses. I mean, for for example, on a on a concentration measurement, really what you’re using is density and temperature in conjunction, to relate that to a concentration. So that’s something that that we would that that would add to the use cases for for a a Coriolis flow meter. And one of the the current biggest innovations that we’ve had recently is with our our ProMaths queue. The ProMaths queue is a a little bit of a different design than some of the other ProMasses that you may have seen on on some previous slides. We actually, have a little bit, longer tube that’s, has a more harsher bend in it. Mhmm. The reason for that is because what we’re trying to do is we’re trying to oscillate these two sensors or these two flow tubes at two at the same frequency, but in two different modes. So in multiple frequencies, at the same time. So, essentially, what we’re doing is our our historic use of a a pro mass meter is kind of in that that top visual where we’re oscillating in one frequency, and one one specific frequency depending on the fluid that’s going through it. And then on the at the bottom, we show an additional mode of oscillation, so an additional frequency that we’re oscillating at that gives us additional information for, specifically challenging applications. So in in in a lot of these cases, what we what we see in most of these applications is, a lot of whipped products, purposeful entrainment of of air into into, applications. So cement in general, let’s say, as an example, we can start there. Well cement, you’re it’s aerated all the time. So as you are are moving that cement around, air pockets can be filled in inside of that cement and can cause challenges as most things with air cause challenges, especially as as you’re moving into a multiphase fluid. Anytime you have one or more than one fluid phase within the the the meter, the meter can is it’s it’s almost like, the meter is kind of confused. It it’s not really sure what it’s supposed to be reading and what it is reading and why it’s reading that. So with with multi frequency technology, we can actually compensate internally compensate because we’re oscillating in two modes. We can compensate for the air that’s present and give a, a corrected mass flow and a corrected, density. So Right. A lot of milk milk applications, cream cheese, well cement, anything like that. Shawn Tierney (Host): That’s awesome. Could you back up one slide for a second? Sure. Lauton Rushford (E+H): Sure. Shawn Tierney (Host): I just I find this so interesting, but I I know that the audience, not everybody’s on the same page. So I think this would be a great slide. Could you just, like, vary what the basic the basic operation of a Coriolis flow meter is? Okay. We know we’re trying to measure typically the flow rate, the flow rate. Right? And, you know, there’s all these variables that go into it. But could you really just, you know, give us the the introductory, you know, how does this thing work? Lauton Rushford (E+H): Sure. So there are exciters, if if you will, or vibrating electronics that’s going to oscillate those flow tubes. Shawn Tierney (Host): Okay. Lauton Rushford (E+H): And they’re gonna if there’s no flow in it, the oscillation is going to basically be, very in line, in sync. Your tubes are going to move out and then move in. And, again, it’s these are a little exaggerated in terms of videos, but the actual tubes will will start vibrating, almost like a tuning fork or you hit a wine glass on the side of a table and you get the vibration out of the wine glass. That’s kind of the same vibration that’s happening. And now as we start flowing product through those flow tubes, we get these these waves that are created. And the inlet and outlet pickup coil are now not in sync, meaning that we’re using the Coriolis force or we’re essentially looking at a phase shift as those tubes start to create those waves, where where there’s a time difference between the inlet and the outlet pickup coil. And that time difference is ultimately what’s related to phase shift, which is ultimately what’s related to that mass flow that’s inside the tubes. Similarly, as we’re oscillating those tubes, if we have water going through that, those tubes, well, we know what the resonant frequency should be of water. We also know what the resonant frequency is of a more dense or a lighter, less dense fluid. So now we can start understanding what the density is specifically as well. So that’s where kind of the multivariable, measurements happen within the flow tube. But, essentially, all of it’s based around a time measurement. It’s all based around when does this, this pickup coil pick up this tube, and when does this pickup, outlet pickup coil pick up the the tube coming back. Yep. Shawn Tierney (Host): Yeah. And so we talked about the ProMASQ having two modes because when the liquids or, you know, like, the substance, like cement or dairy, you know, cream or whatnot, have a lot of ear in it, that could be a challenge. So you have this other mode. We also talked about having a, the temperature sensor thermocouple built in. Mhmm. Is is temperature always and I know I’m asking a lot of crazy questions here, but is temperature always a factor? Because I can see definitely products operate very differently than based on the temperature. Is temperature always a factor in, coming up with the calculation? Lauton Rushford (E+H): So, typically, temperature is going to affect not only the fluid. It’s also going to affect the properties of the tubes themselves. So that’s something that’s often overlooked. And and when when we’re when we’re looking at applications, yes, we care about what the the the temperature of the fluid is because, the density of that fluid may change. There may be more or less mass flow depending, on, how close a pump is. There’s a lot of installation effects as well. But, ultimately, the the as those tubes are oscillating, if you’re if the temperature is low enough or the temperature is high enough, those tubes are have the potential to move more or less Yeah. As you’re oscillating them. So that’s where temperature plays a really big factor, not only in in measuring temperature, that’s a great added value, but also in the, the thermal, properties of the actual tube’s material themselves. Shawn Tierney (Host): Thank you for taking my questions. I just find this interesting. Lauton Rushford (E+H): Yeah. Oh, that’s that’s great. That’s a great question. That is something that that isn’t really thought about, but, we always we always have to take that into account. And and that’s part of, ensuring that the the stated accuracy, their specifications of the device are met throughout the entire, temperature range of the meter’s specification. So if we know that we’re gonna be operating, this meter is rated for negative 40 degrees f to 300 degrees f, well, we have to make sure that we understand how the tubes will react throughout that entire range. And that’s that again goes back to that innovation that goes back to the research and development that goes into the design of these sensors. So, a lot of important things there. So with that, I guess there’s there’s another added value that that comes into play when, we talk about oscillating that Pro Mask Q at a, at two modes. There’s actually an additional effect that happens to the tubes, And as those tubes because of how long those tubes are, as the tubes start oscillating, at the end of their oscillation, at their maximum amplitude of oscillation, you get a slight twisting motion in the tubes themselves. And so we have a device that is called our ProMass I that directly measures, viscosity directly out of the meter. And that is using a similar, a similar technology in a torsional oscillation mode. Whereas the ProMAS Q, just by nature of design, actually has some slight twisting motions. So, you know, our our r and d g experts and geniuses over, over over overseas, they they came up with this idea. Well, why couldn’t we do a similar thing with our ProMask Q? Why couldn’t we look at how much shear we’re placing on the fluid or how much twisting we’re placing on the on the fluid and understand maybe a little bit more about the individual properties of that fluid that’s going through the meter? And that’s where the oscillation the the torsional oscillation or the rotational oscillation, of that that flow tube can give us a little bit more insight into the viscosity of the fluid itself. And so this is where kind of another innovation, which is on the ProMascue, the hydrocarbon viscosity monitoring. We do what’s called we stated it’s for hydrocarbon viscosity, and the reason for that is because hydrocarbons have a very known, viscosity profile across all different pressures and and temperatures. And so we can we can verify on water and ensure that the meter is going to react properly, and and maintain the accuracy that we stated it’s going to have. And, again, this is a monitoring point. It’s not necessarily a calibrated point. It is plus or minus 10% accuracy, which isn’t very high, but it’s it’s enough to where you can start seeing when you have the difference between a very heavy crude oil and water or a very light crude oil or, like, light hydrocarbon. And the repeatability is ultimately where where the the use case comes in. So this is one of the highlights that I wanted to to point out because I think not only on the monitoring side, it gives us more values, it gives us more information on on what’s happening inside the meter, without us having to open up the meter, and and or open up the the pipe and and look at it. So a couple of applications, typically you’re gonna see them both, in all parts of oil and gas, which is upstream, midstream, and downstream, all the way into, refining products. A lot of these applications, in in midstream, especially in pipelines, is going to be the addition of some sort of drag reducing agent. So we can understand as adding that as we start adding that drag reducing agent into pipelines, how much effect is it actually having? Are we changing the properties enough of the product, or is it, are we not changing it? Are we changing it too much? It gives us, more of a, a qualitative understanding of the product that’s going through the meter. So and, you know, I’d I’d mentioned earlier, you know, we do, a lot of industries, but, you know, I guess the two completely opposite industries would be something like oil and gas and, life sciences or pharmaceutical, And that kind of plays into this transition here into our, ProMASS U. This is our, is a relatively new product, that we’ve had out for less than a year at this point. But our ProMASS U is our single use Coriolis technology. In a lot of pharmaceutical applications, there’s a lot of challenges in terms of cleaning, in terms of making sure that there’s no risk of cross contamination. And the biggest thing with that is, the introduction of single use production. So taking cells, biology, all the way through to a, a marketed medicine or a product, but using all single use products. And that saves on risk for cross contamination, especially in large factories. And, it also actually does save some money because of the amount of chemicals and and cleaning that has to go on in a lot of these pharmaceutical companies. A single use technology kinda fits the need in in that industry very, very well. Shawn Tierney (Host): So what I’m looking at here is it looks like a a lab tabletop type device Yep. And the the u, right, the the the pipes is replaceable. So Yes. It looks like a cartridge where you would, like, you know, turn a lever. You could let’s say you ran product one and you ran that for a while and then you’re done. You would turn this lever, release the cartridge, pull it out, and those pipes don’t have to be cleaned. They can be disposed of. And now you put in your new one, and you can run a different product. And we all know, like, a few years ago, we all heard the horror stories of a pharmaceutical that makes two different batches of medicine, and it was like nightmares. Thank god. That never get out into the real world because only only god knows what would happen. So that’s that’s I like you can’t we can’t exclude that type of cross contamination just can’t happen in Yeah. The twenty first cent in the twenty first century. So but this this is so interesting. Is this c is this something that would be in a I’m just looking at such a nice looking desktop device. Would this be something that was only used in a lab or could it actually be used in a production line? Lauton Rushford (E+H): Yeah. So there’s there’s two versions. Okay. There is a tabletop, which is what you can kinda see on the screen where we have this chassis built around, the the there’s really three components in this. There’s a a transmitter that’s kind of sitting at the top there. There is a base unit, which is where the sensor goes into, that has all the electronics, and then you have your disposable sensor. So the sensor is where all your fluid is gonna be flowing through. Shawn Tierney (Host): Mhmm. Lauton Rushford (E+H): The base unit is doing all of the, manipulation on the tubes themselves. So we talked about how a Coriolis meter works or oscillating those tubes. The base unit is actually doing that, and then the transmitter is taking all of that raw data, understanding it all jumbled up, and giving it out a flow rate, a very accurate flow rate. And there’s two different versions of this. There is a test desktop version and a panel mount version. So the panel mount version would be, you know, in a skid of some sort. Mhmm. That would be permanent, but then the the single use cartridge would be pulled out, disposed of, and then a a new one would be replaced there. And and that’s kind of kind of what we’re gonna get to too in a little bit once we start seeing some of the challenges in this industry. So this industry really is is it’s not new, but it is in terms of process instrumentation. There’s not a lot of manufacturers out there who who have single use flow technologies. So there’s a challenge from our perspective as as the the manufacturer to try and meet all of the requirements of the industry, while providing a robust, accurate, reliable sensor for these applications. And so that’s where our r and d kind of, hit a hit a snag at at one point almost because they’re they’re so used to making robust products that last ten, twenty, thirty years in process. Now we have to look at a product that we want to also do all of those things, but also be disposed of. And so there’s there’s some challenges there. Similarly, there’s a challenge of of calibration in a lot of pharmaceutical plants because certain products require calibration before they’re even installed. Certain products require calibration before they’re installed and while on-site. And then, if there’s ever a replacement that goes in, there’s an additional calibration that might have to happen. And so what we wanted to do was take all of those constraints, all of those challenges, and try and check the boxes of all of them. And I think that’s kinda where our single use landed. There are still some, you know, some certain applications that are challenged, but they’re always gonna be a challenge, until there’s some innovation that comes out that that truly meets that need. But, I guess, in general, really, if if you look at a high level, it’s a half a percent accurate device. We have four different sizes of of sensors that can go into the same base unit. We have an eighth inch, a quarter inch, a half inch, and a one inch sensor that will go into this base unit. They all fit into the same base unit. So as we talked about it with an example, using product A, maybe you’re only flowing at 10 liters per minute, but then product b, you’re flowing at 75 liters per minute. Well, technically, those should probably be two different flow meters, but we can just change the different cartridges out, and and there’s no risk of of contamination, and there’s no need to change anything other than the sensor itself. It is gamma sterilizable, especially in pharmaceutical. That’s really important to make sure that there’s no contamination at all from anything in production, from any anybody’s hands getting on it or anything like that. We don’t do it as a manufacturer. We would kind of rely on our OEMs, on our, tube set manufacturers to actually put these skids together, and part of that package would be to gamma sterilize all of the fittings, all of the tubing, as well as as well as the the flow sensors. And then we also talked about the different the different designs that we have. It is stainless steel tubes, which is different, and it’s polycarbonate flow splitter. So if you see that purple part on the screen, where our tubing would come into, that is a plastic or a polycarbonate product. And then the tubes themselves where we’re actually performing the measurements is a stainless steel, three sixteen l, material, which is different because at when you think about single use, you think about plastic. You think about, bags that are plastic, bioreactors that are plastic, because they’re easy to throw away and they they’re inexpensive. But we felt like in order to meet all of those challenges and all of those, constraints in terms of, current, sensor designs, we felt like the most robust way to do that would be to use stainless steel. And we have a long history of of manufacturing stainless steel devices, and so this is just, another way that we could, show our our expertise in in in products and in especially in Coriolis meters. So there are, as I mentioned, three components. You have your base unit or your single, single use disposable sensor. Down at the bottom there, you have your base unit, which is again where all your electronics are, and then you have your, and then you have your transmitter. And there’s a cable going from the the transmitter to the the base unit. There’s a couple of things I want to highlight on the inside of what the meter is and how it what it looks like. The first thing and probably the most important is that barcode scanner. So every single one of these disposable flow tubes gets calibrated at our factory and then gets imprinted a QR code on the inside of the flow meter. And that QR code, that two d barcode scanner actually scans that information. So it can it can accurately pull in the calibration information. It can pull in the serial number of the tubes. It can pull in the line size of the tubes. It can pull in a lot of information related to those tubes. And then it can relay that back to the transmitter, and the transmitter can check to make sure everything seems functional. And that kind of falls into where our heartbeat technology, conversation may come in in in just a little bit. And then again, all the electronics are our sensor electronics boards, our, ISCM or our sensor electronics module, all is based inside that base unit, inside this very large not not very large, but a a very heavy bodied base unit to ensure stability, across the board. And so here’s an example of what that QR code kinda looks like on the on the backside of that that flow tube, and then another, look into kind of what the the the inside of the base unit looks like. You see coil inlet one, coil inlet two, or coil outlet two. Similarly to kind of what we talked about before, we really care about what’s hap what’s going on in between those tubes, in between those those two coils. And so we’re magnetically oscillating the, the Coriolis flow tubes inside at that back piece, that back, what is that? It’s like a gray type ceramic piece in the back, and that’s ultimately giving us giving us that oscillation that we’re looking for. And then our inlet and outlet, pickup coils are also magnetically coupled to to the sensors, and, we can detect very small changes in those at that oscillations those oscillations. So very very cool, very innovative. It’s a product that we’ve had out for a while in, a while, less than less than a year, but long enough. And there’s been a lot of interest in in the pharmaceutical space, especially as people are trying to save costs, go closer to maybe a personalized medicine approach, where there’s gonna be smaller, amounts of product going through, more expensive amount of product going through. Accuracy is gonna be the most important there. And so this is where, we kinda talk about a little bit more about how to maintain that data trail, that automated data trail from the cal the calibration in the factory all the way into production. And so in this case, what we what we’re looking at is, here’s the process of what would happen in in in a in a system. We would calibrate the tubes at our factory. The tubes would go to a tube set manufacturer. The tube set manufacturer puts all of these pieces together. They double bag them in a class seven ISO, ISO class seven environment. Super clean area, no risk of contamination there. And then just to be even more safe, they’re going to gamma sterilize it there. Then they’re going to bring it on-site where they have their skid created, and they’re gonna plug everything in. And then once they plug everything in and turn the entire skid on, they’re gonna, they’re gonna notice that on the flow meter, it says, hey, we’re doing a function check right now. What does that mean? That’s ultimately what we call heartbeat technology, and that’s doing some advanced diagnostics behind the scenes. And it’s checking information like electronics in the bit in the base unit. It’s checking, tubes, making sure the tubes are aligned and weren’t damaged in shipping, and ensuring that the the factory calibration is still valid on the current device. So all of that is happening kind of behind the scenes before you, even start running product through it, to ensure that we are fully CGMP or, current good manufacturing practice and operation, on a production side. And that kind of maybe leans leads a little bit into, another product that we’ve recently released, which is our Anderson Hauser ProMASS k 10. It’s the first Coriolis meter, in the world that has IO Link as an output. And now IO Link, I I think it’s really important to start with a really good basis about what IO Link is, and IO Link is something I call it the three wire digital communication, but it it’s not a 100% accurate. So we’ll maybe dive into that a little bit and talk about what IO Link can do, and how it is, is being accepted in industries, specifically in farms, in in food and beverage and pharmaceutical industries. As a general rule of thumb, most large smart factories are using Ethernet based protocols. So that means that their their the devices that they have, the control system that they have is all digital, which means you can get a lot more data and get a lot of data. You can get so much data you have no idea what to do with. There’s also, these Ethernet switches that are typically either remote Ethernet switches or switches that are out in the plant that, that are pulling in a lot of this data and then sending it up to whether it’s their asset management system or a control system, and ultimately can give us the most amount of information about the health of the device, any sort of multivariable, values that we have coming out of the device. And then similarly, on the op on the right side here of this screen, you see an IO Link system. IO Link also does a very similar thing where you have a remote, what’s called an IO Link master. It’s connected to a flow meter or connected to a level switch or connected to, a temperature probe, and it pulls all that information in, and then it outputs that information back to their control system. And so historically, we’ve had a lot of Ethernet four wire devices, whether that’s Ethernet IP, PROFINET, Modbus, any sort of digital heart as a as an option as well. That’s historically been where our Ethernet four wire and two wire devices come from. Now IO Link hasn’t really been a focus for us, but because of our our diversity in different industries, we’ve had to look at IO Link as a feasible, cost efficient choice for basic process needs in under in in flow meters, in pressure transmitters, in a lot of devices, and a lot of a lot of different applications. And so there’s some benefits and pros and cons to both. Ethernet, you have a lot of process devices versus simple simple measurement points. The, the IO Link, you have a specific range in terms of distances. That’s only about 60 feet, which means it’s really, really good for those skid solutions, that are put out in into many, many factories and especially especially in food and beverage. The IO Link masters are really where the integration happens. And then the data that’s recorded and aggregated is happening inside that IO Link master where typically on a, Ethernet based system, you all have full transparency from, device level all the way up to your your control system, DCS system, throughout and anywhere throughout that system as well. There is uses for both even in the same plants. There’s uses for both in in similar applications, but I I think one of the benefits is being the first, Coriolis manufacturer to have a IO Link device. What does that mean? Really, what it means is we can get some very good data, not all the data, but in many cases, we don’t need all of the data, and we can be super accurate, extremely fast in terms of data data transmission, and, make things a little easier in terms of of integration and installation of the devices. So typically what a a system or a subsystem might look like with IO Link, you have your IO Link master, that’s where power is is brought to, and it’s also where our connection to that overarching enterprise system or DCS system is. So that IO Link master is a must. You have to have that. You also have to have a flow meter that is or any device that is capable of outputting in an IO Link protocol, in an IO Link communication method. And then there’s a specific three wire cable that goes from the device to the master. And there this is the often overlooked thing, but it’s an IODD. Essentially what that means is it’s an IO Link device driver. So that device driver is gonna tell the IO link master what and how is this device sending information to me. So it’s almost like a little roadmap for the IO Link master to understand what’s happening on the on the base the base level of, of that IO Link device. Ultimately, these are the four things to have that you have to have for, basic subsystem components. And then, as you start integrating it to into an overarching system, there’s a little bit more that would be needed as well, but this will at least get you started, and understanding kind of why there’s IO Link masters, and why there’s IO Link protocols and technology in the first place. So again, this is our Coriolis k 10, with our IO Link master. It’s a line size three eighths of an inch all the way up to three inch. It also has what we call heartbeat technology. It has, three a. It has all of our, approvals for hygienic applications, for food and beverage applications, for pharmaceutical applications as well, and gives us a little bit more flexibility in terms of what we can offer our customers that will meet the need of where they’re at, but also prepare them for for future, expansions and, and and large scale DCS turnarounds and things like that. So, there is a couple of things here, mass flow as a standard with density, temperature, and you get a standard totalizer one as an output. There is, again, food contact materials, eHedge three a, all hygienic process connections as well as standard process connections, available with this device. And then one other key factor here is when we’re in actually interacting with this device, there’s a couple of ways we can interact with it. We can, of course, use a a touch screen. We can push the device and and be right in front of it. There’s also a method for using a free app that we have on on the Android store and the Apple Apple Store. That’s called SmartBlue. That’s available for a lot of different devices, but it is using a Bluetooth technology to, tap into the device and configure, everything. And then the other option is using a, a device manager, with a CDI port that’s built inside the transmitter as well. So all different ways to to interact with the same device, even, interacting with it using IO Link is possible as well. So a lot of different functionalities, a lot of different, options, so we can meet the needs where meet the customers where their needs are, and then also where their they wanna get get to. So that kind of takes us into what heartbeat technology is. And we actually we talk about heartbeat technology as a story because I think if we start talking about what it is before we talk about the story, it’s, it’s it’s it’s hard to to wrap your head around. There’s a lot going into it. And part of that that discussion really starts with a a marketing phrase, which is called taking the pulse of your measurement. And what that really does is is it’s trying to understand how the device is operating currently, and how the device may be operating in the future based on current conditions. And so all all of that is is started with what our customers expect out of a flow meter, expect out of a pressure transmitter, expect out of a pH probe. All of our customers’ needs and our users’ needs are expanding. So not only do they need excellent measurement performance from a device, they also need a reliable device. I I need to know when something’s going wrong. They also wanna be available. If the device itself isn’t always available, they can’t trust it. We want our customers to not only trust our device, but trust the measurement performance that they’re getting out of the device. And they also want it easy to easy to use. As we’ve seen in a lot of industries, the, the operations teams, the operators that are on on the plant floor are getting less and less, and maybe they’re moving more towards engineering. But there are a lot of plants that are running extremely lean. And so running lean means they have to run efficiently and they have to run effectively. And if our devices are not easy to use and easy to understand, we’re we’re kind of failing at at that point. So we also wanna make sure our devices are safe. We wanna make sure our devices are predictive, and we wanna make sure our devices potentially can be connected in the future. And so all of those together is now now we’ve got a difficult puzzle we’ve gotta try and solve, with any one of our measurement devices. And that’s where we think kinda heartbeat technology meets a lot of those needs and bridges the gap between, the excellent measurement performance and and all of these, needs that we have. So we split heartbeat technology into kind of three categories. We have diagnostics, which is, current, current status, current device diagnostics, advanced diagnostics. That’s the basis of everything. So if we don’t have a good basis of diagnostics, we can’t do verification. We can’t do monitoring. We can’t provide in, improved process insights, very effectively if we don’t have a good base unit. So that happens from that happens from the the design of our devices all the way down to the raw components that go into all of the devices as well. And then verification is kind of a what’s happening to my device right now, and can you give me a PDF printout of what that looks like. So that’s that’s part of the verification. And then again, monitoring how we look at certain values over time trended over time, so we can start understanding, predictively when certain process conditions or process upsets may happen or could happen, and how will they affect our measurements. So all of that together is really bridged on the diagnostic coverage. It’s based around how we can detect our, any alarms, alerts, failures, things that happen inside the device that weren’t expected. All of that needs to be, really, really important. And so our IO modules, our sensor electronic modules, our sensor, inlet and outlet pickup coils, and our divi our ex the entire excitation system that’s happening inside of a of a Coriolis meter, all are really, really important to understand the health of the device. If we can understand the health of individual components of the device, we can try and better understand the health of the entire device as a whole. Kind of the sum of, sum of equal parts or the sum of parts is is greater than the than the sum of the the system. So, that’s ultimately what we’re trying to do here. And what that means is that this value, the heartbeat sensor integrity parameter is always generated and can be used as a direct value for, understanding process related concerns as well as meter concerns. So in a similar way, we talked about, oscillation modes with our PROMAS Q, with our PROMAS I, and other flow meters as well. The frequency or the oscillation frequency that we’re actually doing for this HBSI value is a fixed diff distance from that frequency. And so at any one time, we’re we’re oscillating these tubes at one, two, almost, three every, three different frequencies every time. And so the part of this this parameter is ultimately giving us a little bit more information related to the health of the sensors, related to, even the health of the process as well. And we’ll talk about a couple of use cases on on how that, and what that means, and and can ultimately mean for you. So as a general rule of thumb, when we calibrate and design a new sensor, our HBSI value, is 0% at reference conditions, and that may fluctuate depending on if you’re operating at reference conditions or not. But right around zero, it could be negative point one to positive point one, percent, but there’s no no cause kind of for concern there. We do have kind of a stated bandwidth in which we expect the flow meter to operate well within its its factory calibration and well within its specification. But if that value shows very, very low, or values, like, right around zero as a reference condition, your HBSI value is related directly to sensor components that aren’t affected. So if our exciter current, if our pickup coils, if our, sensor tubes are not damaged, likely that HBSI value is going to remain at zero or right around zero. Now when we do have something like a wear mechanism, something like corrosion or erosion or abrasion inside the tubes, ultimately, there’s things that are going to be affected by that. Now how do we actually detect that? Well, that’s where using this HBSI value, we can actually understand individual components of the the flow meter, individual, components like the sensor tubes. For example, if we were to have a corrosion instance, your wall thickness of the tubes would change. And so what what would happen there is as we start oscillating these tubes, you would start to see that value increase because your tubes are moving moving more and more and more because we’re oscillating at the same frequency or at the at the same frequency, but the tubes is not our tubes are not as heavy. Right? So, that’s where that that HBSI value can give us information related to, kind of the health of all of our devices or all of our our components within the device. So there’s multiple ways to observe that HBSI value, and this is where trending comes into play, looking at something and trying to be predictive and preventative, in the long term. There’s no process interruption. This this entire thing happens. This entire, HBSI value is generated, automatically by the device itself. It remained the measurement remains completely available, continuously available, and it happens in situ behind the scenes, if you will, of a of your measurement. And then you’re gonna improve efficiency, obviously, and and reduce risk if you understand what’s happening and what’s going on inside the flow meter without you actually visually seeing what’s happening to the device. So, all of that to say, there’s a lot of ways to observe it, but there is also important ways, that we can use it. So, yes, knowing that the HVSI value is zero is just that’s great. That’s awesome. But what does that ultimately mean? And here’s a couple of examples. Here’s a couple of use cases. So we’ve had an application, in the past where, it was an abrasive fine slurry. And so anytime you have abrasive fine slurries, you have to be extra cautious of using bent tubes, and also the velocities in which you’re flowing those those those processes through there. So the initial one, they had was a dual bent tube that failed six months in the service, and they replaced it with a single straight tube. So they expected to see some abrasion, but because of the design of the flow meter, that HBSI parameter was taken over time, and it’s been installed for for four years now and shows a relatively flat line behavior for the the HBSI value, meaning there’s no wear mechanism going on inside that device, be because of the process. So that’s a that’s a use case there. Another use case that that we talk about a lot is is the presence of abrasion in general. We know that in some applications, there is going to be abrasion. And that’s on us as the manufacturer, that’s also on, the customer to understand what their levels and limits are, and are capable of handling. And if they don’t know, that’s that’s where we we should probably step back and say, hey, let’s let’s talk about this as a as a at a high level. What happens when something goes wrong? Do you just automatically remove the device? Is it are you down in terms of, not being able to produce properly? Things like that. And that’s where in this case we used, kind of predictive maintenance every ten, twelve, fifteen, eighteen months. We know we have to replace this device because of the abrasion, or we have to decrease our velocity, through the meter. So either way, that’s ultimately this use case and showing showing that there is a wear mechanism happening, and we need to understand at what point do we need to start replacing these devices. And lastly, here’s one that was an unexpected wear mechanism. So customer used a Coriolis flow meter, and for five days, everything was great. No worries. Everything was totally fine. Customer didn’t expect anything to be wrong, which is exactly what was shown. And then once they did a cleaning cycle with a new product a new cleaning product, they noticed that this value increased. And so over time, I mean, think about twenty five days, you’re increasing your HBSI value because you’re performing your regular scheduled cleaning. Well, that wasn’t understood, and that wasn’t, that didn’t the the customer didn’t know that was going to affect things. We didn’t know that was going to affect things, but this ultimately shined light on, here’s what’s happening. Now can we change cleaners, or can we use a material that’s more compatible with that cleaner, or can we just live with the the, the risk that the the values will last long enough for us to get really, really good good data, and then we can, and look at replacing it, things like that. So this was another, application where we weren’t expecting to see any sort of drift, but we did because of, the the wear mechanism that that wasn’t, very well known or or present at at the time. So, ultimately, I think, you know, using, something like heartbeat technology as a, a confidence boots booster in your measurement is is really the the key there. Because I think the more that we can increase confidence in our measurements, the more that our customers, will continue to want to to work with us and collaborate with us on on applications and and talk, about, different, industry applications and things like that. As as the working for a manufacturer is currently my my first my first job, I think I think, out of college, I think there’s a there’s a really cool benefit of of a privately owned company that continues to invest in research and development for the products that we have. And, I think that, you know, Anderson Hauser has has done a great job of, showing some innovations that we can within our Coriolis flow flow meter technologies. That’s all I got. Shawn Tierney (Host): Well, I thought that was very interesting, especially the HBSI, how you guys have in included that in your product so you can see that everything’s good, or if something is starting to go out of out of, you know, out of I don’t wanna say out of whack. You know, something’s starting to go out of alignment, you know, with Yeah. What you were expecting. And that example of cleaning, you know, nobody would have thought, you know, this, you know, this product is designed to run this fluid through it, but the cleaner, they’ll finding out that the cleaner was the problem. That’s priceless. Right? That’s priceless. And you can you like you said, there’s different options you can take to address that issue, but now that you know what the problem is. If you didn’t know there was a problem, then your values would be off over time, and that wouldn’t be good at all. Right. So Right. Just such an interesting topic to talk through. And I I appreciate you not only to take us through your products, but also taking us through some of the technologies that are built in the products and that make them work. And I you know, there’s a lot there between the, field bus, the PROFINET, and the Ethernet IP on your really high end, high accuracy, you know, type of installations versus maybe a smaller installation where you can use IO Link because it’s slower cost. We just had the IO Link folks on the podcast. If you guys missed that, just, check back, a podcast or two ago. We had the IO link guys on talking about what they do and how they do it, and I think you summarized it very well in this presentation. And so I think that makes a lot of people happy because in many cases, that’s a lower cost. Yeah. I mean, you’re not gonna get the same performance as you’re gonna get over Ethernet, but you’re it’s a lower cost, and it’s, you know, maybe enough information for your application. So it’s good to see that option there, especially for those skid manufacturers who can utilize those products. You know, with that, I I don’t have any other questions. Was there anything else you wanted to say before we close out the show? Lauton Rushford (E+H): No. All I have to say is thank you. I appreciate the the time and the the the platform. I think this is, awesome, and thank you for asking all the questions you did. I think there was a lot of a lot of really good information that you mentioned, as well there too. So, thank you. That’s all I have to say. Shawn Tierney (Host): Well, Lon, thank you for coming on. I, I just like the first time we had Anderson Hauser on, it was just really just so intellectually interesting. So it’s our pleasure to have you on, and we really appreciate you guys. Lauton Rushford (E+H): Thank you. Appreciate it. Shawn Tierney (Host): Well, I hope you enjoyed that episode, and I wanna thank Lawton for for coming on the show, not only to bring us up to speed on Coriolis flow meters, but also answering my questions because I know I interrupted there, especially at the beginning with a lot of questions. So really appreciate him, taking my questions and also bringing us up to speed on the technology. Now Now I also wanna thank E and H for sponsoring this episode so I could bring it to you ad free on all platforms. I don’t like ads, but, you know, you gotta pay the bills. And when a vendor comes in and they sponsor the show, it really underwrites our cost to edit it and publish it. So I’m super appreciative to them and to all our sponsors who do that. And please let them know if you see E and H anywhere out there, if you’re talking to one of their reps or you’re talking to, somebody from E and H, please let them know how much I appreciate and maybe you appreciate that they sponsored this episode. I also wanna mention that you may not know this, but I brought my other podcast back, the automation news podcast. I renamed the automation tech talk. And anytime I have an episode that is, one of my shorter episodes that I think will do good on audio, be a good listen. Right? I am publishing it on that automation tech talk podcast. And on this podcast, you probably notice every once in a while, I’m releasing an episode of the automation show. Some episodes of the automation show, there’s so much hands on that I don’t think they’d make a good audio addition, but some of them are like presentations and discussions. And I think those would make a good episode of the automation podcast. So I’m releasing them on this podcast channel, but I’m keeping the name, the automation show. So you know, hey. This is, originally was a video that was turned into a podcast. So give me feedback. If you don’t like those, I’ll stop doing it. But I thought because, some weeks we can’t always bring you a new episode, we may have an episode of automation show that I think would make a good listen. So I wanted to bring those to you on this platform as well. And, again, I always love your feedback, and I wanna thank everybody who’s given a five stars or thumbs up. You guys are great. I you know, last time I checked on it, you had so many people, had given us five stars. And that you know, that’s really how we find new vendors come out, like E and H and other vendors. Right? They specifically said you guys were such had such great feedback on the previous podcast that they wanted to come back on. So please take a moment. I know a lot of you listen while you’re driving. But when you get home or get to some place where you can look at your phone, please give us a thumbs up or a five star rating because that really helps us grow the audience and find new vendors to come on the show. And with that, I’m gonna end the show right there. I wanna wish you all good health and happiness. And until next time, my friends, peace. Until next time, Peace ✌️  If you enjoyed this content, please give it a Like, and consider Sharing a link to it as that is the best way for us to grow our audience, which in turn allows us to produce more content

Shawn Tierney meets up with Tom Weingartner of PI (Profibus Profinet International) to learn about PROFINET and System Redundancy in this episode of The Automation Podcast. For any links related to this episode, check out the “Show Notes” located below the video. Watch The Automation Podcast from The Automation Blog: Listen to The Automation Podcast from The Automation Blog: The Automation Podcast, Episode 244 Show Notes: Special thanks to Tom Weingartner for coming on the show, and to Siemens for sponsoring this episode so we could release it ad free on all platforms! To learn more PROFINET, see the below links: PROFINET One-Day Training Slide Deck PROFINET One-Day Training Class Dates IO-Link Workshop Dates PROFINET University Certified Network Engineer Course Read the transcript on The Automation Blog: (automatically generated) Shawn Tierney (Host): Welcome back to the automation podcast. My name is Shawn Tierney from Insights and Automation, and I wanna thank you for tuning back in this week. Now on this show, I actually had the opportunity to sit down with Thomas Weingoner from PI to learn all about PROFINET. I actually reached out to him because I had some product vendors who wanted me to cover their s two features in their products, and I thought it would be first it’d be better to actually sit down and get a refresh on what s two is. It’s been five years since we’ve had a PROFINET expert on, so I figured now would be a good time before we start getting into how those features are used in different products. So with that said, I also wanna mention that Siemens has sponsored the episode, so it will be completely ad free. I love it when vendor sponsor the shows. Not only do we get the breakeven on the show itself, we also get to release it ad free and make the video free as well. So thank you, Siemens. If you see anybody from Siemens, thank them for sponsoring the Automation Podcast. As a matter of fact, thank any vendor who’s ever sponsored any of our shows. We really appreciate them. One final PSA that I wanna throw out there is that, speaking like I talked about this yesterday on my show, Automation Tech Talk, As we’ve seen with the Ethernet POCs we’re talking about, a lot of micro POCs that were $250 ten years ago are now $400. Right? That’s a lot of inflation, right, for various reasons. Right? And so one of the things I did this summer is I took a look at my P and L, my pros profit and loss statements, and I just can’t hold my prices where they are and be profitable. Right? So if I’m not breaking even, the company goes out of business, and we’ll have no more episodes of the show. So how does this affect you? If you are a student over at the automation school, you have until mid September to do any upgrades or purchase any, courses at the 2020 prices. Alright? So I I don’t wanna raise the prices. I’ve tried as long as I can, but at some point, you have to give in to what the prices are that your vendors are charging you, and you have to raise the prices. So, all my courses are buy one, sell them forever, so this does not affect anybody who’s enrolled in a course. Actually, all of you folks rolled in my PLC courses, I see it updates every week now. So and those who get the ultimate bundles, you’re seeing new lessons added to the new courses because you get that preorder access plus some additional stuff. So in any case but, again, I wanna reiterate, if you’re a vendor who has an old balance or if you are a student who wants to buy a new course, please, make your plans in the next couple of weeks because in mid September, I do have to raise the prices. So I just wanna throw that PSA out there. I know a lot of people don’t get to the end of the show. That’s what I wanted to do at the beginning. So with that said, let’s jump right into this week’s podcast and learn all about Profinet. I wanna welcome to the show, Tom from Profibus, Profinet North America. Tom, I really wanna just thank you for coming on the show. I reached out to you to ask about ask you to come on to to talk to us about this topic. But before we jump in, could you, first tell the audience a little bit about yourself? Tom Weingartner (PI): Yeah. Sure. Absolutely, Shawn. I’m gonna jump to the next slide then and and let everyone know. As Shawn said, my name is Tom, Tom Weingartner, and I am the technical marketing director at PI North America. I have a fairly broad set of experiences ranging from ASIC hardware and software design, and and then I’ve moved into things like, avionic systems design. But it seemed like no no matter what I was working on, it it always centered around communication and control. That’s actually how I got into industrial Ethernet, and I branched out into, you know, from protocols like MIL standard fifteen fifty three and and airing four twenty nine to other serial based protocols like PROFIBUS and MODBUS. And, of course, that naturally led to PROFINET and the other Ethernet based protocols. I I also spent quite a few years developing time sensitive networking solutions. But now I focus specifically on PROFINET and its related technologies. And so with that, I will jump into the the presentation here. And and, now that you know a little bit about me, let let me tell you a little bit about our organization. We are PROFIBUS and PROFINET International or PI for short. We are the global organization that created PROFIBUS and PROFINET, and we continue to maintain and promote these open communication standards. The organization started back in 1989 with PROFIBUS, followed by PROFINET in the early two thousands. Next came IO Link, a communication technology for the last meter, and that was followed by OmLux, a communication technology for wireless location tracking. And now, most recently, MTP or module type package. And this is a communication technology for easier, more flexible integration of process automation equipment. Now we have grown worldwide to 24 regional PI associations, 57 competent centers, eight test labs, and 31 training centers. It’s important to remember that we are a global organization because if you’re a global manufacturer, chances are there’s PROFINET support in the country in which you’re located, and you can get that support in the country’s native language. In the, lower right part of the slide here, we are showing our technologies under the PI umbrella. And I really wanted to point out that these, these technologies all the technologies within PI umbrella are supported by a set of working groups. And these working groups are made up of participants from member companies, and they are the ones that actually create and update the various standards and specifications. Also, any of these working groups are open to any member company. So, PI North America is one of the 24 regional PI associations, and we were founded in 1994. We are a nonprofit member supported organization where we think globally and act locally. So here in North America, we are supported by our local competence centers, training centers, and test labs. And and competence centers, provide technical support for things like protocol, interoperability, and installation type questions. Training centers provide educational services for things like training courses and hands on lab work. And test labs are, well, just that. They are labs that provide testing services and device certification. So any member company can be any combination of these three. You can see here if you’re looking at the slide, that the Profi interface center is all three, where we have JCOM Automation is both a competent center and a training center. And here in North in North America, we are pleased to have HMS as a training center and Phoenix Contact also as a competent center. Now one thing I would like to point out to everyone is that what you should be aware of is that every PROFINET, device must be certified. So if you make a PROFINET device, you need to go to a test lab to get it certified. And here in North America, you certify devices at the PROFINETERFACE center. So I think it’s important to begin our discussion today by talking about the impact digital transformation has had on factory networks. There has been an explosion of devices in manufacturing facilities, and it’s not uncommon for car manufacturers to have over 50,000 Ethernet nodes in just one of their factories. Large production cells can have over a thousand Ethernet nodes in them. But the point is is that all of these nodes increase the amount of traffic automation devices must handle. It’s not unrealistic for a device to have to deal with over 2,000 messages while it’s operating, while it’s trying to do its job. And emerging technologies like automated guided vehicles add a level of dynamics to the network architecture because they’re constantly entering and leaving various production cells located in different areas of the factory. And, of course, as these factories become more and more flexible, networks must support adding and removing devices while the factory is operating. And so in response to this digital transformation, we have gone from rigid hierarchical systems using field buses to industrial Ethernet based networks where any device can be connected to any other device. This means devices at the field level can be connected to devices at the process control level, the production level, even even the operations level and above. But this doesn’t mean that the requirements for determinism, redundancy, safety, and security are any less on a converged network. It means you need to have a network technology that supports these requirements, and this is where PROFINET comes in. So to understand PROFINET, I I think it’s instructive here to start with the OSI model since the OSI model defines networking. And, of course, PROFINET is a networking technology. The OSI model is divided into seven layers as I’m sure we are all familiar with by now, starting with the physical layer. And this is where we get access to the wire, internal electrical signals into bits. Layer two is the data link layer, and this is where we turn bits into bytes that make up an Ethernet frame. Layer three is the network layer, and this is where we turn Ethernet frames into IP packets. So I like to think about Ethernet frames being switched around a local area network, and IP packets being routed around a wide area network like the Internet. And so the next layer up is the transport layer, and this is where we turn IP packets into TCP or UDP datagrams. These datagrams are used based on the type of connection needed to route IP packets. TCP datagrams are connection based, and UDP datagrams are connectionless. But, really, regardless of the type of connection, we typically go straight up to layer seven, the application layer. And this is where PROFINET lives, along with all the other Ethernet based protocols you may be familiar with, like HTTP, FTP, SNMP, and and so on. So then what exactly is PROFINET, and and what challenges is it trying to overcome? The most obvious challenge is environmental. We need to operate in a wide range of harsh environments, and, obviously, we need to be deterministic, meaning we need to guarantee data delivery. But we have to do this in the presence of IT traffic or non real time applications like web servers. We also can’t operate in a vacuum. We need to operate in a local area network and support getting data to wide area networks and up into the cloud. And so to overcome these challenges, PROFINET uses communication channels for speed and determinism. It uses standard unmodified Ethernet, so multiple protocols can coexist on the same wire. We didn’t have this with field buses. Right? It was one protocol, one wire. But most importantly, PROFINET is an OT protocol running at the application layer so that it can maintain real time data exchange, provide alarms and diagnostics to keep automation equipment running, and support topologies for reliable communication. So we can think of PROFINET as separating traffic into a real time channel and a non real time channel. That mess messages with a particular ether type that’s actually eighty eight ninety two, and the number doesn’t matter. But the point here is that the the the real time channel, is is where all PROFINET messages with that ether type go into. And any other ether type, they go into the non real time channel. So we use the non real time channel for acyclic data exchange, and we use the real time channel for cyclic data exchange. So cyclic data exchange with synchronization, we we classify this as time critical. And without synchronization, it is classified as real time. But, really, the point here is that this is how we can use the same standard unmodified Ethernet for PROFINET as we can for any other IT protocol. All messages living together, coexisting on the same wire. So we take this a step further here and and look at the real time channel and and the non real time channel, and and these are combined together into a concept that we call an application relation. So think of an application relation as a network connection for doing both acyclic and cyclic data exchange, and we do this between controllers and devices. This network connection consists of three different types of information to be exchanged, and we call these types of information communication relations. So on the lower left part of the slide, you can see here that we have something called a a record data communication relation, and it’s essentially the non real time channel for acyclic data exchange to pass information like configuration, security, and diagnostics. The IO data communication relation is part of the real time channel for doing this cyclic data exchange that we need to do to periodically update controller and device IO data. And finally, we have the alarm communication relation. So this is also part of the real time channel, because, what we need to do here is it it’s used for alerting the controller to device false as soon as they occur or when they get resolved. Now on the right part of the slide, is we can see some use cases for, application relations, and and these use cases are are either a single application relations for controller to device communication, and we have an optional application relation here for doing dynamic reconfiguration. We also use an application relation for something we call shared device, and, of course, why we are here today and talking about applications relations is actually because of system redundancy. And so we’ll get, into these use cases in more detail here in a moment. But first, I wanted to point out that when we talk about messages being non real time, real time, or time critical, what we’re really doing is specifying a level of network performance. Non real time performance has cycle times above one hundred milliseconds, but we also use this term to indicate that a message may have no cycle time at all. In other words, acyclic data exchange. Real time performance has cycle times in the one to ten millisecond range, but really that range can extend up to one hundred milliseconds. So time critical performance has cycle times less than a millisecond, and it’s not uncommon to have cycle times around two hundred and fifty microseconds or less. Most applications are either real time or non real time, while high performance applications are considered time critical. These applications use time synchronization to guarantee data arrives exactly when needed, but we also must ensure that the network is open to any Ethernet traffic. So in order to achieve time critical performance here, and we do this for the most demanding applications like high speed motion control. And so what we did is we added four features to basic PROFINET here, and and we call this PROFINET ISOCRANESS real time or PROFINET IRT. These added features are synchronization, node arrival time, scheduling, and time critical domains. Now IRT has been around since 02/2004, but in the future, PROFINET will move to a new set of I triple e Ethernet standards called time sensitive networking or TSN. PROFINET over TSN will actually have the same functionality and performance as PROFINET IRT, but we’ll be able to scale to faster and faster, networks and and as bandwidth is is increasing. So this chart shows the differences between PROFINET, RT, IRT, and TSN. And the main difference is, obviously, synchronization. And these other features that, guarantee data arrives exactly when needed. Notice in in the under the, PROFINET IRT column here that that, the bandwidth for PROFINET IRT is a 100 mil a 100 megabits per second. And the bandwidth for PROFINET RT and TSN are scalable. Also, for those device manufacturers out there looking to add PROFINET IRT to their products, there are lots of ASICs and other solutions available in the market with IRT capability. Alright. So let’s take a minute here to summarize all of this. We have a a single infrastructure for doing real time data exchange along with non real time information exchange. PROFINET uses the same infrastructure as any Ethernet network. Machines that speak PROFINET do so, using network connections called application relations, and these messages coexist with all other messages so information can pass from devices to machines, to factories, to the cloud, and back. And so if you take away nothing else from this podcast today, it is the word coexistence. PROFINET coexists with all other protocols on the wire. So let’s start talking a little bit here about the main topic, system redundancy and and and why we got into talking about PROFINET at all. Right? I mean, what why do we need system redundancy and things like like, application relations and dynamic reconfiguration? Well, it’s because one of the things we’re pretty proud of with PROFINET is not only the depth of its capabilities, but also the breadth of its capabilities. And with the lines blurring between what’s factory automation, what’s process automation, and what’s motion control, we are seeing all three types of automation appearing in a single installation. So we wanna make sure PROFINET meets requirements across the entire range of industrial automation. So let’s start out here by looking at the differences between process automation versus factory automation, and then we’ll get into the details. First off, process signals typically change slower on the order of hundreds of milliseconds versus tens of milliseconds in factory automation. And process signals often need to travel longer distances and potentially into hazardous or explosive areas. Now with process plants operating twenty four seven, three sixty five, system must systems must provide high availability and support changes while the plant is in production. This is where system redundancy and dynamic reconfiguration come in. We’ll discuss these again here in in just a minute. I just wanted to finish off this slide with saying that an estop is usually not possible because while you can turn off the automation, that’s not necessarily gonna stop the chemical reaction or whatever from proceeding. Sensors and actuators and process automation are also more complex. Typically, we call them field instruments. And process plants have many, many, many more IO, tens of thousands of IO, usually controlled by a DCS. And so when we talk about system redundancy, I actually like to call it scalable system redundancy because it isn’t just one thing. This is where we add components to the network for increasing the level of system availability. So there are four possibilities, s one, s two, and r one, r two. The letter indicates if there are single or redundant network access points, and the number indicates how many application relations are supported by each network access point. So think of the network access point as a physical interface to the network. And from our earlier discussion, think of an application relation as a network connection between a controller and a device. So you have s one has, single network access points. Right? So each device has single network access points with one application relation connected to one controller. S two is where we also have single network access points, but with two application relations now connected to different controllers. R one is where we have redundant network access points, but each one of these redundant network access points only has one application relation, but those are connected to different controllers. And finally, we could kinda go over the top here with r two, and and here’s where we have redundant network access points with two application relations connected to different controllers. Shawn Tierney (Host): You know, I wanna just stop here and talk about s two. And for the people who are listening, which I know is about a quarter of you guys out there, think of s two is you have a primary controller and a secondary controller. If you’re seeing the screen, you can see I’m reading the the slide. But you have your two primary and secondary controllers. Right? So you have one of each, and, primary controller has the, application one, and secondary has application resource number two. And each device that’s connected on the Ethernet has both the one and two. So you went maybe you have a rack of IO out there. It needs to talk to both the primary controller and the secondary controller. And so to me, that is kinda like your classic redundant PLC system where you have two PLCs and you have a bunch of IO, and each piece of IO has to talk to both the primary and the secondary. So if the primary goes down, the secondary can take over. And so I think that’s why there’s so much interest in s two because that kinda is that that that classic example. Now, Tom, let me turn it back to you. Would you say I’m right on that? Or Tom Weingartner (PI): Spot on. I mean, I think it’s great, and and and really kinda emphasizing the point that there’s that one physical connection on the network access point, but now we have two connections in that physical, access point there. Right? So so you can then have one of those connections go to the primary controller and the other one to the secondary controller. And in case one of those controllers fails, the device still can get the information it needs. So, yep, that that’s how we do that. And and, just a little bit finer point on r one, if you think about it, it’s s two, but now all we’ve done is we’ve split the physical interface. So one of the physical interfaces has has, one of the connections, and the other physical interface has a has the other connection. So you really kinda have, the same level of redundant functionality here, backup functionality with the secondary controller, but here you’re using, multiple physical interfaces. Shawn Tierney (Host): Now let me ask you about that. So as I look at our one, right, it seems like they connect to port let’s I’ll just call it port one on each device to switch number one, which in this case would be the green switch, and port number two of each device to the switch number two, which is the blue switch. Would that be typical to have separate switches, one a different switch for each port? Tom Weingartner (PI): It it it doesn’t have to. Right? I I I think we chose to show it like this for simplicity kinda to Shawn Tierney (Host): Oh, I don’t care. Tom Weingartner (PI): Emphasize the point that, okay. Here’s the second port going to the secondary controller. Here’s the first port going to the primary controller. And we just wanted to emphasize that point. Because sometimes these these, diagrams can be, a bit confusing. And you Shawn Tierney (Host): may have an application that doesn’t require redundant switches depending on the maybe the MTBF of the of the switch itself or your failure mode on your IO. Okay. I’m with you. Go ahead. Tom Weingartner (PI): Yep. Yep. Good. Good. Good. Alright. So, I think that’s some excellent detail on that. And so, if you wouldn’t mind or don’t have any other questions, let’s let’s move on to the the, the the next slide. So you can see in that previous slide how system redundancy supports high availability by increasing system availability using these network access points and application relations. But we can also support high availability by using network redundancy. And the way PROFINET supports network redundancy is through the use of ring topologies, and we call this media redundancy. The reason we use rings is because if a cable breaks or the physical connection, somehow breaks as well or or even a device fails, the network can revert back to a line topology keeping the system operational. However, supporting network redundancy with rings means we can’t use protocols typically used in IT networks like, STP and RSTP. And this is because, STP and RSTP actually prevent network redundancy by blocking redundant paths in order to keep frames from circulating forever in the network. And so in order for PROFINET to support rings, we need a way to prevent frames from circulating forever in the network. And to do this, we use a protocol called the media redundancy protocol or MRP. MRP uses one media redundancy manager for each ring, and the rest, of the devices are called media redundancy clients. Managers are typically controllers or PROFINET switches, and clients are typically the devices in the network. So the way it works is this. A manager periodically sends test frames, around the network here to check the integrity of the ring. If the manager doesn’t get the test frame back, there’s a failure somewhere in the ring. And so the manager then notifies the clients about this failure, and then the manager sets the network to operate as a line topology until, the failure is repaired. Right? And so that’s how we can get, network redundancy with our media redundancy protocol. Alright. So now you you can see how system redundancy and media redundancy both support high availability. System redundancy does this by increasing system availability, Walmart. Media redundancy does this by increasing network availability. Obviously, you can use one without the other, but by combining system redundancy and media redundancy, we can increase the overall system reliability. For example, here we are showing different topologies for s one and s two, and these are similar to the the the topologies that were on the previous slide. So, if you notice here that, for s one, we can only have media redundancy because there isn’t a secondary controller to provide system redundancy. S two is where we combine system redundancy and media redundancy by adding an MRP ring. But I wanted to point out here that that even though we’re showing this MRP ring as as as a possible topology, there really are other topologies possible. It really depends on the level of of system reliability you’re trying to achieve. And so, likewise, on on this next slide here, we are showing two topologies for adding media redundancy to r one and r two. And so for r one, we’ve chosen, again, probably for simplistic, simplicity’s sake, we we add an MRP ring for each redundant network access point. With for r two, we do the same thing here. We also have an MRP ring for each redundant network access point, but we also add a third MRP ring for the controllers. Now this is really just to try to emphasize the point that you can, you you can really, come up with just about any topology possible, but it because it really depends on the number of ports on each device and the number of switches in the network and, again, your overall system reliability requirements. So in order to keep process plants operating twenty four seven three sixty five, dynamic reconfiguration is another use case for application relations. And so this is where we can add or remove devices on the fly while the plant is in production. Because if you think about it, typically, when there is a new configuration for the PLC, the PLC first has to go into stop mode. It needs to then re receive the configuration, and then it can go back into run mode. Well, this doesn’t work in process automation because we’re trying to operate twenty four seven three sixty five. So with dynamic reconfiguration, the controller continues operating with its current application relation while it sets up a new application relation. Right? I mean, again, it’s it’s really trying to get this a a new network connection established. So then the the the controller then switches over to the new application relation after the new configuration is validated. Once we have this validation and the configuration’s good, the controller removes the old application relations and continues operating all while staying in run mode. Pretty handy pretty handy stuff here for for supporting high availability. Now one last topic regarding system redundancy and dynamic reconfiguration, because these two PROFINET capabilities are compatible with a new technology called single pair Ethernet, and this provides power and data over just two wires. This version of Ethernet is now part of the I triple e eight zero two dot three standard referred to as 10 base t one l. So 10 base t one l is the non intrinsically saved version of two wire Ethernet. To support intrinsic safety, 10 base t one l was enhanced by an additional standard called Ethernet APL or advanced physical layer. So when we combine PROFINET with this Ethernet APL version of 10 base t one l, we simply call it PROFINET over APL. It not only provides power and data over the same two wires, but also supports long cable runs up to a kilometer, 10 megabit per second communication speeds, and can be used in all hazardous areas. So intrinsic safety is achieved by ensuring both the Ethernet signals and power on the wire are within explosion safe levels. And even with all this, system redundancy and dynamic reconfiguration work seamlessly with this new technology we call PROFINET over APL. Now one thing I’d like to close with here is a is a final thought regarding a new technology I think I think everyone should become aware of here. I mean, it’s emerging in the market. It’s it’s quite new, and it’s a technology called MTP or module type package. And so this is a technology being applied first here to, use cases considered to be a hybrid of both process automation and factory automation. So what MTP does is it applies OPC UA information models to create standardized, non proprietary application level descriptions for automation equipment. And so what these descriptions do is they simplify the communication, between equipment and the control system, and it does this by modularizing the process into more manageable pieces. So really, the point is to construct a factory with modular equipment to simplify integration and allow for better flexibility should changes be required. Now with the help of the process orchestration layer and this OPC UA connectivity, MTP enabled equipment can plug and operate, reducing the time to commission a process or make changes to that process. This is pretty cutting edge stuff. I think you’re gonna find and hear a lot more about NTP in the near future. Alright. So it’s time to wrap things up with a summary of all the resources you can use to learn even more about PROFINET. One of the things you can do here is you can get access to the PROFINET one day training class slide deck by going to profinet2025.com, entering your email, and downloading the slides in PDF format. And what’s really handy is that all of the links in the PDF are live, so information is just a click away. We also have our website, us.profinet.com. It has white papers, application stories, webinars, and documentation, including access to all of the standards and specifications. This is truly your one stop shop for locating everything about PROFINET. Now we do our PROFINET one day training classes and IO link workshops all over The US and parts of Canada. So if you are interested in attending one of these, you can always find the next city we are going to by clicking on the training links at the bottom of the slide. Shawn Tierney (Host): Hey, guys. Shawn here. I just wanted to jump in for a minute for the audio audience to give you that website. It’s us.profinet.com/0dtc or oscardeltatangocharlie. So that’s the website. And I also went and pulled up the website, which if you’re watching, you can see here. But for those listening, these one day PROFINET courses are coming to Phoenix, Arizona, August 26, Minneapolis, Minnesota, September 10, Newark and New York City, September 25, Greenville, South Carolina, October 7, Detroit, Michigan, October 23, Portland, Oregon, November 4, and Houston, Texas, November 18. So with that said, let’s jump back into the show. Tom Weingartner (PI): Alan, one of our most popular resources is Profinet University. This website structures information into little courses, and you can proceed through them at your own pace. You can go lesson by lesson, or you can jump around. You can even decide which course to take based on a difficulty tag. Definitely make sure to check out this resource. We do have lots of great, webinars on on the, on on the website, and they’re archived on the website. Now some of these webinars, they they rehash what we covered today, but in other cases, they expand on what we covered today. But in either case, make sure you share these webinars with your colleagues, especially if they’re interested in any one of the topics that we have listed on the slide. And finally, the certified network engineer course is the next logical step if you would like to dive deeper into the technical details of PROFINET. It is a week long in Johnson City, Tennessee, and it features hands on lab work. And if you would like us to provide training to eight or more students, we can even come to your site. If you would like more details about any of this, please head to the website to learn more. And with that, Chai, I think that is, my last slide and, covered the topics that I think we wanted some to cover today. Shawn Tierney (Host): Yeah. And I just wanna point out that to you guys, this, training goes out through all around The US. I definitely recommend getting up there. If you’re using PROFINET and you wanna get some training, they usually fill the room, like, you know, 50 to a 100 people. And, it’s you know, they do this every year. So check those dates out. If you need to get some hands on with PROFINET, I would definitely check out those. And, of course, we’ll have all the links in the description. I also wanna thank Tom for that slide. Really defining s one versus s two versus r one and r two. You know, a lot of people say we have s two compatibility. A matter of fact, we’re gonna be looking at some products that have s two compatibility here in the future. And, you know, just trying to understand what that means. Right? You know, when somebody just says s two, it’s like, what does that mean? So I really if that slide really doesn’t for you guys listening, I thought that slide really kinda lays it out, kinda gives you, like, alright. This is what it means. And, so in in in my from my perspective, that’s like it’s you’re supporting redundant controllers. Right? And so if you have an s two setup of redundant, seamless controllers that or CPUs, then you’ll be that product will support that. And that’s important. Right? Because if you had a product that didn’t support it, it’s not gonna work with your application. So I thought that and the the Ethernet APL is such a big deal in process because I you know, the the distance, right, and the fact that it’s it’s, intrinsically safe and supports all those zones and and areas and whatnot, that is, and everybody everybody all the instrumentation people are all over. Right? The, the, the Rosemonts, the fishes, the, the endless houses, everybody is is on that working group. We’ve covered that on the news show many times, and, just very interesting to see where that goes, but I think it’s gonna take over that part of the industry. So, but, Tom, was there anything else you want to cover in today’s show? Tom Weingartner (PI): No. I I think that that really, puts puts a a fine finale on on on this here. I I do wanted to maybe emphasize that, you you know, that point about network redundancy being compatible with, system redundancy. So, you know, you can really hone in on what your system reliability requirements are. And and also with with this this, PROFINET over APL piece of it, completely compatible with with PROFINET, in in of itself. And and, also, you don’t have to worry about it not supporting, system redundancy or or anything of of the like, whether, you know, you you wanted to get, redundant even redundant devices out there. So, that’s that’s, I think that’s that’s about it. Shawn Tierney (Host): Alright. Well, I again, thank you so much for coming on. We look forward to trying out some of these s two profanet devices in the near future. But with that, I I really wanted to have you on first to kinda lay the groundwork for us, and, really appreciate it. Tom Weingartner (PI): No problem. Thank you for having me. Shawn Tierney (Host): Well, I hope you guys enjoyed that episode. I did. I enjoyed sitting down with Tom, getting up to date on all those different products, and it’s great to know they have all these free hands on training days coming across United States. And, you know, what a great refresher from the original 2020 presentation that we had somebody from Siemens do. So I really appreciate Tom coming on. And speaking of Siemens, so thankful they sponsored this episode so we could release it ad free and make the video free to everybody. Please, if you see Siemens or any of the vendors who sponsor our episodes, please tell them to thank you from us. It really helps us keep the show going. Speaking of keeping the show going, just a reminder, if you’re a student or a vendor, price increases will hit mid September. So if you’re a student, you wanna buy another course, now is the time to do it. If you’re a vendor and you have a existing balance, you will want to schedule those podcasts before mid September or else you’ll be subject to the price increase. So with that said, I also wanna remind you I have a new podcast, automation tech talk. I’m reusing the old automation new news headlines podcast. So if you already subscribed to that, you’re just gonna get in the new the new show for free. It’s also on the automation blog, on YouTube, on LinkedIn. So I’m doing it as a live stream every lunchtime, just talking about what I learned, in that last week, you know, little tidbits here and there. And I wanna hear from you guys too. A matter of fact, I already had Giovanni come on and do an interview with me. So at one point, I’ll schedule that as a lunchtime podcast for automation tech talk. Again, it still shows up as automation news headlines, I think. So at some point, I’ll have to find time to edit that to change the name. But in any case, with that, I think I’ve covered everything. I wanna thank you guys for tuning in. Really appreciate you. You’re the best audience in the podcast world or the video world, you know, whatever you wanna look at it as, but I really appreciate you all. Please feel free to send me emails, write to me, leave comments. I love to hear from you guys, and I just wanna wish you all good health and happiness. And until next time, my friends, peace. Until next time, Peace ✌️  If you enjoyed this content, please give it a Like, and consider Sharing a link to it as that is the best way for us to grow our audience, which in turn allows us to produce more content

Shawn Tierney meets up with Eugenio Silva of Emerson to learn all about Dust Collection Systems, and Emerson’s Monitoring and Control Solution in this episode of The Automation Podcast. For any links related to this episode, check out the “Show Notes” located below the video. Watch The Automation Podcast from The Automation Blog: Note: This episode was not sponsored so the video edition is a “member only” perk. The below audio edition (also available on major podcasting platforms) is available to the public and supported by ads. To learn more about our membership/supporter options and benefits, click here. Listen to The Automation Podcast from The Automation Blog: Read the transcript on The Automation Blog: (automatically generated) Shawn Tierney (host): Welcome back to the automation podcast. My name is Shawn from Insights, and I wanna thank you for tuning back in. Now in this episode, I had the pleasure of meeting up with Eugene Silva from Emerson to learn all about the industrial control and monitoring system that comes with their industrial dust collectors. Now I thought it was very interesting. I hope you do as well. But before we jump into this episode, I do wanna thank our members who made the video edition possible. So So when a vendor does a sponsor of the episode, the video becomes a member only perk, and that is just $5 a month to get started. So thank you members for making the video edition possible. With that, I also wanna thank our sponsor for this week’s show, the automationschool.com and the automationblog.com. I have an update later in the show what’s going on on both sites, and I hope you’ll, stick around and listen to that, towards the end of the show. But with that said, let’s go ahead and jump into this week’s episode of the automation podcast. It is my pleasure to welcome Emerson back on the show and Eugene on the show to talk about dust collector monitoring. You guys can see the slide if you’re watching dust collector monitoring and control solutions. I’m excited about this because this is a solution versus, like, a discrete product. So with that said, Eugene, would you please introduce yourself to our audience? Eugenio Silva (Emerson): Yes. Shawn, thank you very much for this opportunity. Hello, everyone. Here’s Eugenio Silva. I’m a product manager, intelligence automation within Emerson, the discrete automation part of Emerson. I’m glad today gonna share some, some of our understanding and learnings with the dust collector monitoring control solution. And, when I talk about that, Emerson is also involved in in others, types of solutions that, our purpose is to drive innovation that makes the world healthier, safer, smart, and more sustainable. And I’m also responsible for continuous emission monitoring, pest collectors is one, utility, energy and compressed air management solutions. So for today, I prepared something that, we go a little bit, into why this type of, test collector solution is important, from understand of our customers and industry point of view. We’re going to look into the fundamentals of a dust collection, from the particle sensors to the dust collector systems, and then dive in into the dust collector solution where I’m going to provide you, some features, also explanation why they are there, and how this kind of capabilities deliver value to our end users and customers, and, hopefully, to have time as well to have a short, recorded demo that, brings us, full scope how the operators look into into that solution when they they use it. Shawn Tierney (host): But before we jump in, I wanna thank the automationschool.com for sponsoring this episode of the show. That’s where you’ll find all of my online courses on Allen Bradley and Siemens PLCs and HMIs. So if you know anybody who needs to get up to speed on those products, please mention the automationschool.com to them. And now let’s jump back into the show. Eugenio Silva (Emerson): In terms of key applications, industries use cases, dust collector is essential for many industries that produce dust, produce any kind of a pounder, any kind of a fume, and typically air pollution control, boundary processing, handling, industrial dust, fume ventilation are covered by one or another way by dust collectors. And, the industries that I put in both, these are the the dirty ones in the sense that they produce a lot of, particle, either in terms of gases or dust. Therefore, the regulations that are in these industries are quite strong. So cement, metals, chemical plus, carbon, black and toner, like lithium battery assembly, disassembly, metal foundry. And what is interesting is the either you produce a waste that you have to manage it properly, can be also recycled, for example, in the industries like plastics in food or wood. All the collected dust that you have, you can also reuse and sometimes recycle. But why? Why this is important? Why is it important to extract dust from these industries? Let’s start on the right side because this is what the the customer is looking for. Because the cost of our pollution, the hazards, this this safe safety accidents that can be caused by this kind of harmful airborne and particles and forms are so substantial, then of course, it’s very much regulated in all these industries. And if you calculate the costs on the public health, Sometimes big accidents in plants where even big fires or hazards to people operating the plant. We talk about billions per year, the cost of that. And one of the consequences of having such issues is that when the dust extraction system is not working properly or you have really a downtime. For example, I’m going to explain that this really depends on components that are very, they use so often that they wear down, like filters, like post files. And each time that we have a downtime is not the cost of the dust collector downtime that’s important. It’s the overall downtime costs that imposes to the operation of the plant because in order to be conformist, they have to stop operating until they fix the issue. And these downtimes, of course, arise in many ways in different aspects. How complex is this dust collector. But I’m I’m going to give you, some insights that, if a dust collector system does not have any solution to monitoring real time or control, the efficiency. Basically, the personnel is managing these assets without any sight, and everything can go wrong. That’s why the TCO and the maintenance aspects are quite important. Because if you’re not aware where is the problem, when you have to plan and this becomes a firefighting or reactive mode, then your costs are going to be quite high. And when you talk about the TCO, it’s about the cost of the equipment, the acquisition, the cost of operation, meaning not only the personnel, but in this case, we use a lot of compressed air. I’m going to explain why. The maintenance costs, as we explained, and the disposal costs. Disposal means, the filter bags that must be replaced and and changed, but also the the dust, the fume, all the elements that must be, properly managed and recycling sometimes. So this is the aspects why it’s important. Now let’s turn us about, the benefits and savings. So if you use the dust collector solutions, of any kind that can monitor in real time all the aspects, of the operation of a dust collector system and, also contributes turning maintenance from reactive to preventative and maybe predictive, then the best thing that you can do is to avoid huge penalties. As you can see on this graph, every decade, let’s say, the fines are getting steeper. And the reason for that is because of the the damage and the result of a big, like, say, issue on the plant regarding to this dust part is is quite heavy. So, therefore, we talk about 100 k’s or even plus in some industries like primary metal and chemical, where one single incident, it’s about a 100 k in average or more. And then, of course, to avoid that and to be completely compliance, you have to operate that systems, in many cases, 24 by seven. And, therefore, any way possible to reduce downtime and, as a plus, reduce the energy costs because for compressed air, you have to use electricity, then, it pays off because you’re going to be full time compliant. And the other thing is if you do properly, monitor and control your dust collector system, you also increase the filtration efficiency. So that means you are far from the high levels, where after that threshold, you would be penalized. You can operate under, conformist, under compliance, but can also expand the equipment life. For example, the life bags, the post valves, you don’t have it to replace as often, which is the case if you don’t do any real time monitoring diagnostics. On the left side, the way that we talk about improving maintenance is the total cost. When we talk about the filter life, at least one unit of a filter, It’s about 18 k, US dollars. And you see that, the tip of a iceberg is just the purchase price. The dust collector system, like, of course, has an acquisition cost. But below that, as a total cost of ownership, you have the energy that you expand utilizing the systems. You have the filter bags. You have to keep parts in your inventory. You have to dispose of that. And, of course, you have the downtime costs and also the labors labor costs. Now I’m going to just to give, a chance to say, okay. Tell me how a dust collector system works. Shawn Tierney (host): Before we get to that, we gotta pay the bills. So I wanna tell you about our sponsor, the automationschool.com. It’s actually the next room over. We have a huge training room. We have, some of the most unique products you’ll be able to work on. You know, I know everybody has a bunch of CompactLogix or s seven twelve hundreds or 15 hundreds and, you know, VFDs and HMIs. But some of the products we have here, you’re not gonna find in anybody else’s training room, not even the factory’s training room because we cover all different products. Right? So if you’re coming over to do training with us, you can actually learn Siemens and Allen Bradley at the same time. You can learn how to get Siemens and Allen Bradley to talk together. You guys know I’ve covered that on the show, but you could do it hands on. And some of the other things is like working with third party products. Right? So, you know, if you go to a vendor’s course, they’re not gonna have third party products. But we have as you remember from the wall in my studio, we have all kinds of third party products. And I’m gonna be taking some more pictures of all the different labs we have, the equipment we use, with these third party products. So if you know anybody looking for training and we can do custom things too. So if you wanna start training at noontime or 01:00 because you’re gonna drive in three or four hours away, I was recently just at a, large vendor’s customer doing some training on their behalf. And, yeah, that was a long drive. So if you want your, students to show up in person at twelve or one and then train and then at the on the last day, leave around twelve or one, we can do that as well. I don’t care. We could actually run into the night if you wanted to go, do evenings. Or, again, some people don’t learn very well in the evenings, but in any case, because I own the company, we can do whatever you want. As long as we have the equipment and the time to put it together, we’ll do it for you. So I just wanted to make you aware of that. We also if you’re, just wanna come yourself, if you go to the automationschool.com forward slash live, you will see a place where you can preregister for an upcoming class. And when I get enough people to sign up, I’ll reach out to you and tell you what date is gonna be held. And by preregistering like that, you will save $50 off the $500 price. And if you’re already a student, you will save the price of your online course off of the in person course. So maybe you bought my $200 Siemens or CompactLogix, ControlLogix cost. They’re gonna get that off of that $500. Right? And if you don’t own the online cost, don’t worry about it. If you come here for in person training, at the end of your training, we’re gonna enroll you, in one of those online courses completely free of charge so you can continue your learning. And you don’t have to worry about trying to blitz all the content while you’re here because whether you’re here for a day or five, it doesn’t matter. Whatever you have left to learn, you’ll be able to do it after hours at home, and there’s no additional charge for that. So with that said, let’s get back into this week’s episode of the automation podcast. Eugenio Silva (Emerson): And these are going to be general principles and basics. In general, a dust collector system looks like this. It’s a unit where the air is pulled in at the bottom of the compartment, and this could be forced or not. And then the air gets out, on the top, the outlet, and the dust is collected on the outside of the bag. So if you see this, in this picture, we have one full bag in kind of light brown color with a specific fabric, could be porosis fabric, a PVC, or some even paper in some cases. And then the cleaner exceeds at the top. And the what happens is that the dust cake builds up on the bags, on the outside part of the bag. And, if you see the number one on top, in that particular, entry point, we have two pulse valves with, compressed air in order to shake a little bit these, post bags, filter bags, and then knocks down the dust out of these bags, and then they are collected by a hopper at the bottom. Okay? So that’s basically, in general, how it works the principle. It’s a bit more complicated. Here is just to show that in order to automate a dust collector system including the filter bags, we use, a combination of, electrical and pneumatic, components. And these are from post valves, the ones that continuously blow air into these pipes, the compressed air tanks that hold the right pressure and the right compressed air capacity in order to keep the filtration efficiency very high. Then you have the filter regulators that, you have to bring, the pressure of this line to higher enough, to to be efficient, but not so high to spend too much compressed air. Then you can use controllers, black boxes that are able to do a time based sequencing, but these are not so so much sometimes efficient because it doesn’t take into consideration all the diagnostics that you can get out of it. And then, basically, the very important element is this, particle sensor that is on the outside of the clean air because that is gonna be your canary in the mind. Right? It’s gonna be the one that indicates if the filter, system is efficient efficient and if the the job is done right. And then the other things. But let’s go back to a very interesting view. You remember this picture here that, you you’re looking at, a cross session of the dust collector. Now you could imagine how it looks like from the top. From the top, it looks like that. There is a compressed air tank, that covers, certain portion of the filters units. For example, it’s very common that a filter, complete filter unit, might have different compartments. And in each of these compartments, you have a series of filter bags. And then imagine that you provide short but very powerful pulses of compressed air that are periodically injected on top of this columns. And below, there’s a filter bag. So, therefore, they are going to to receive to expand a little bit, and the dust cake then, outside of of their surface follows. And by inertial forces, of course, this dust is accumulated at the bottom, which is, extracted into a hopper. Of course, now depending of the number of the filters per line, per roll, these pulse valves needs to pulse a little bit faster or not. And the interval time, if you just follow time based approach, could be three to six minutes. Now if you calculate the average filter units, you may have 12 of these filter bags. You can have about seven to 10 pulse valves per unit. It’s very common that, one large installation would have about, like, 500 pulse valves and four, six times more filters, install it. And imagine that if each of them having boost every three minutes, 24 by seven, during seven days a week. So can you imagine the amount of compressed air that can be spent? That’s why these pulses must be very short and powerful, in hundred milliseconds to avoid it also big waste. I think that, picture on the left side, just to simply say that, it’s a lot of, interesting things to to get the dust removal, but basically is a jet of compressed air on top, that shakes the filter. And then by gravity, the dust cake is removed. Shawn Tierney (host): It’s not just a filter. You know, I think main main people may just think, well, a dust collector is just this bag that catches all the dust. You’re actually, you know, you’re you you do have the bags, but, you’re using compressed air to sequentially, depends depending on how many you have, shake those bags in a sense by blowing air into them, to shake off the dust so it falls into the hopper. And so I can you can definitely see, like you were mentioning, if you have lots of these cylinders or these bags, then the sequencing has to be, you know, pretty pretty precise and and pretty, repeatable to make sure you’re you’re cleaning all of the bags off. And I’m I’m assuming too, you need to know when the hopper is full because everything stops working if if if the hopper gets, over full. So very interesting. I think your diagrams do a great job of explaining it as well. Eugenio Silva (Emerson): Yeah. If I play a little bit when I mention that, it’s a a little bit the reverse, way of our vacuum cleaner. Right? Because Yeah. We suck the the dust inside of the bags. Mhmm. And when the bags are completely full clogged, the suction, power, it’s far reduced. Right? So then you have to to empty our, let’s say, filter bags. Here is the although the all the dust is accumulated on the outside, the outer surface of the fabric, but the effect is the same. If there’s so much dust on the surface or out of the surface, then, the air that is shown here, the intake, the air, and then the filter simply stops. That’s why affects completely the efficiency of, that, unit. And the post jet cleaning is a way to unclog or to clean, the filters in order to bring them to the more efficient operation. Shawn Tierney (host): Yeah. Especially if you have lots of dust, you need an automatic way to continue to clean it and get it off of the filter and into the bin. So yeah. No. That makes a lot of sense. Eugenio Silva (Emerson): Yeah. In in other cases, although you talk about, dust, of course, it could be any kind of a pounder. Like, for example, in the foods and beverage industry, you don’t want this for example, let’s say, a dry milk production. You don’t want that dust to be floating around because it can bring contamination. But believe it or not, it can ignite fire sometimes. So that’s why it’s important to to get that completely eliminated. So this is the part that very people would say, okay, on the outlet where the the air should be cleaner, as you can see on the right side, that this, particle sensor is located at the outlet, clean air side. It has a very interesting the way it works is quite interesting. We use a we have a sensor in our portfolio called p 152 that, we take advantage of this triboelectric effect. Basically, this sensor, is coated with PTFE or a Teflon layer, so it’s completely electronic, electric isolated from from, of course, the media. And then when the dust starts touching, that probe, a DC charge is transferred. But because of this, sensor probe is completely isolated, we set the flow layer, the resolution and the electric charge is in the order of a peak ramp. So 10 minus 12. And that the resolution is about point five picoamp. So, therefore, if you’re touching the particles, depends of their size, They are going to generate more or less electricity that’s going to be transferred. And the ones that are just surround, they are not touching. For example, imagine that this, duct air exhausting pipe is quite big. A bit half meter, maximum one meter around that sensor, the particle also generates, induced charge in AC. And by measuring that, we have an idea about how clean is, of course, there that’s getting out. But it’s a bit more tricky than you can imagine because it looks like this. Shawn Tierney (host): Hey, everyone. I hope you enjoy this week’s show. I know I really enjoyed it. And, of course, I wanna thank our members for making the video edition possible. So this vendor did not sponsor this episode. So the video edition is available for members, and there’s some great graphics in their presentation you guys may wanna check out. Now with that said, we do have some really exciting podcast episodes coming up. I’m sitting down with Inductive. I’m sitting down with Software Toolbox. I’m sitting down with Siemens and a bunch of other vendors. So we have plenty of new podcasts coming up in the coming weeks this summer. And I also wanted to give you an update of what’s going on over at the automation blog. We’ve had some new articles come out. Brandon Cooper, one of our freelancers, wrote a great article about emulating Allen Bradley e threes. We had a vendor, actually, submit an article and sponsor the site to submit an article about what makes a good automated palletizer. We also had an update about the automation museum. That’s a fundraiser we’re running. We’re trying to open a automation museum. I got a lot of legacy stuff I’d like to donate to it, and I’d love to have it so you can come in and actually walk through, not just see the stuff, but actually learn on it. Right? So maybe you have some old stuff in your plant. You come out to the automation museum, and you can learn how to use it. With that said, we’re also looking at possibly doing a podcast for automation museum to drive awareness of legacy automation. So any of you out there interested in that, contact me directly. And, you can do so over at the automationblog.com. Just click on the contact button. And, we also have an article two articles from Brandon Cooper about things he learned as he transitioned from working in a plant to traveling around and visiting other plants to help them with their processes and automation. So check those articles out over at the automation blog. And finally, over at the automation school, you know, we have the new factor IO courses. We also have I just added a new lesson to the logics version of that course. Somebody wanted to try to use bit shifts instead of counters, so I added a lesson on that. Plus, I’m now starting to update all of the courses, including the brand new ones I’m working on. So you’re gonna see a brand new start here lesson later in the week, and I’m working on some cool emulation, lateral logic for my PLC courses that if you don’t have any push buttons or limit switches, you can actually use this code I’m gonna give you for free to simulate the widget machine that I use as kind of the basis for my teaching. So in any case, check that out if you’re in one of my PLC courses over at the automationschool.com. And with that said, you know, I’m very thankful for all the vendors who come on, especially those who sponsor the episodes so I don’t have to do these commercials. I’m not a big commercial guy, but I do wanna thank you for hanging in there and listening through this update. And now we’ll get right back into this episode of the automation podcast. Eugenio Silva (Emerson): Every time you get, use the jet boost with the boost valves on top of the filter bags, it creates a peak. So that means the cleaning cycles that are happening in a duration of, just a 100 milliseconds. That’s why they are very, very thin. And they happening every two, three minutes, per roll. They have to they have in nature a little bit of noise because imagine that every time that, you clean, more dust gets into inside of the the filter back. So that means it’s like when you clean your vacuum cleaner, immediately when you turn on that, some of this dust is gonna get inside immediately, and that’s the peak. But now imagine that, you have a rupture in the filter or you have a big role because, unfortunately, these the things are wear out. And then these peaks starts getting higher and higher. So, therefore, what we do when we, put that solution in place for a little time, let’s say, couple of days, we needed to kind of, set up, these thresholds. We need to figure out the level of noise that could be because depends very much the capacity, the types of, of a test. But once you do that, in our solution, we set the thresholds like alarming, a warning alarm, which means that after that point, the maintenance crew, starts looking at, that could be a early indication that a filter bag is not okay until the maximum point that avoids any any nonconformist, issue, which is already a rupture. You really pass the time where this filter, must be replaced. Shawn Tierney (host): So we’re looking at this chart for those who are listening. And the particle sensor, you know, it’s measuring the particles as air flows normally. But during the pulse, right, we’re forcing a lot of air back in, back down. So we’re getting a lot more, you know, than the average air would have x amount of particles. But if we’re forcing a bunch of it back in, we’re gonna see a lot more particles per, let’s say, hundred millisecond pulse. Right? So we do expect a peak when we when we pulse it because we’re just forcing a lot of get back go into the reverse direction. So we can we catch the bag loose. But what you’re saying here on this chart, I find so in so much interesting. So you can quantify, like, the expected increase in, in dust that you’re gonna sense with the sensor when you go in the reverse, when you pulse pulse, blow the ear downwards to, to shake the bag free. But you’re saying if that if that extra increased amount of detected dust is either too high, above normal, or too low below normal, then that tells you that you you could either have a clogged bag or you could have a burst bag. Is that am I understanding that correctly? Eugenio Silva (Emerson): Yes. Is this correct? And then the interesting thing is that as soon as you’re getting closer to replace a filter back, this baseline starts raising a bit with a kind of, how can I say, there is a drift? Why? Exactly what you said. A filter is completely clogged. It’s not yet any rupture, but is the efficiency of the cleaning is not so okay. So therefore, this slightly changes needs to be analyzed. Why I’m showing row one to row 10? Exactly in the picture, if you remember, a compartment filter with several, let’s say, filter bags, they are under the row. So under the row one, you may have 10 filter bags, row two, row three, and so on. So that means you are able to indicate which row is the problem, but it might be that you still need to check further which of the filters in that particular row have the problems. The more quick this peak happens, more number of, filter bags can have a problem. Shawn Tierney (host): Mhmm. Eugenio Silva (Emerson): Okay? Shawn Tierney (host): So you have one sensor on the exhaust, and you’re sequencing through, you know, blowing out or shaking out, you know, pulsing each of the rows. So that’s why we see, you know, one reading across the, you know, across the horizontal, and we see your row, row one, row two, row three, row four, each of them with discrete values or pulses. And like you just said, if you have multiple issues on a row, then you’re going to see, you know, a higher or lower peak depending on what the issue is. I’m with you. Eugenio Silva (Emerson): Yes. That’s why I’m going to show the other diagnostic capabilities that we needed to associate with this, particle sensor. And just to remember that, this particle sensor, we simply use one unit on the outlet part. That’s why I needed to make the sequence in serialization of the post because then I need to to synchronize with the post jets of every role. Shawn Tierney (host): Mhmm. Eugenio Silva (Emerson): No? Row by row. Shawn Tierney (host): And I think too, if you tried to do them all at once, the the you would need a lot higher pressure. So it it kinda makes sense to do it row by row because it reduces your maximum pressure required. Eugenio Silva (Emerson): Yeah. In this practical sense, we’re not be able to Shawn Tierney (host): Differentiate. Eugenio Silva (Emerson): Identify which of the roles, would be the problem. That’s why we kind of still have to do that. But now let’s give in a solution overview, and I think that, some of the key capabilities and features are going to highlight even more, the other, diagnostic capabilities that we are able to to provide in order to identify correctly and early as possible such issues. So this is a typical dust collector system. And if you look at around, if this dust collector system is just, let’s say, automated with nomadic electric components and they don’t have real time monitoring, you’re not really know the emission level. If it also this is not real time monitoring with some diagnostics, then you are not able to identify when this particle sensor, for example, is completely taken by, the dust because the humidity entrance in that, in that pipe, or it might be that, it’s so dirty, your dust that, is already ingrained so much on the probe. Mhmm. So that’s why the poor, reliability or the low level sensitivity of that could be affected. And if you were not monitoring, these signals that I showed the these peaks synchronized with the post valve jets Mhmm. You don’t have any early warning. Okay? The post valves basically are coils. They are solenoid coils Shawn Tierney (host): Mhmm. Eugenio Silva (Emerson): With tag diaphragms that open and close at the speed of a hundred milliseconds. The point is that their life time is about a couple of millions of cycles. Mhmm. But imagine, in some cases, one, two years is already enough to to have end end of life. So a fault valve, has to be connected to a control system because you need to know if this is a short circuit or if the diaphragm is completely open. And you can only do that if every time that you cycle the valve, you also, check that. For example, the power that, you drive the coil gives you a feeling if that is a coil that is already gone. Okay? Now let’s talk about the compressed air. Right? If you have a a filter that is open, there’s a rupture. If you have, a diaphragm that’s completely gone open, you start consuming higher and higher the compressed air. The point is this is continuously increasing. You can just imagine that this is normal. But if you go into average and look at this in a historical way, you’re gonna see that this trend is caused because of the broken post valves, for example. So that’s why it’s also important aspect of the automation solution is to minimize the usage of the compressed air is to have a clearly operating under a baseline that is normal. The filter bags, independent of the materials, because if you talk about life sciences, foods, chemical, or metal, they have a different materials. They have a different, where else, lifetime span. The point is the costs might be the filter itself is not so expensive. But going up there, exchange stopping, moving things around, getting the dust out before you change, putting all the personal protection equipment may take hours. So, therefore, that is the cost of that. And if you’re not able to prevent or even have an early warning when that is going to occur, is gonna be a reactive, maintenance issue. Right? So that’s why just convincing that, it’s worth looking into different aspects. And that’s why, on the left side, when we talk about solutions, we talk about, the connectivity part that, we have to work with devices that are hard or four to 20 milliamps. Some of devices are modbus to CP. Newer actuators in post faults could be mu m q t t or even OPC UA. That’s the the PLC part that, we have. And we can work with pneumatic systems, for example, that they turn at AP, PROFINET, or any other, standards. Then, of course, we have the IOs, that, we have to look at to control the post jet systems, but also to monitor the differential pressures, to measure the compressed here in some cases, until the parts where at the top, we put HMI SCADA software platform that, we pre engineered, in order to to make it simpler the development, of that solution by our OABS or many cases directly to our end users. And all in the right are the elements that we offer in our portfolio. Some cases, OEMs of a dust collector systems just to take from us, and they might be that they have their own solution as well. Shawn Tierney (host): So just for the audio audience, I know we’ve covered these products a lot, especially on the news show. But, I mean, I’m just wanna kinda go through a couple of these things. You got the ASCO product line. Right? So remote piloted valves and, you know, all of those, that category, you know, the, pulse valves. But we also got the Advantex, which we’ve talked about, like figure filter regulators and, different cylinders. Topworks, which I think we’re all familiar with, proximity sensors and whatnot. And, some of the other products you guys, Rosemount, differential pressure transmitters. We also see, we have, the PAC systems. In this case, you could have edge analytics, and so you may have one of the PAC systems, edge IPCs. And we even see the, down in the corner there, the Emerson PLC and IOs, which I think we’re all familiar with as well. So that kinda shows you how, you know, this solution, you know, they’re taking all these different products they have in their catalog and putting it together in one solution, which is, you know, you kinda need all this stuff. You know, basically understanding how it works. We just went through it. And so it’s interesting. I don’t think I’ve seen a slide yet from Emerson where they kinda include in one application all, if not all, many of their their, different product lines. And then, the the skate on the top, it looks like, just some beautiful screens and charts and and, you know, dials showing the current status. So, and and I I didn’t mean to interrupt you, Gino, but nonetheless say that, especially since the people listening, they’ll be familiar with all those trade names because we’ve covered those in the past. But, in any case, let me turn it back to you. Eugenio Silva (Emerson): No. No. It’s thanks for highlighting. And I I say that, when I introduce myself that I’m from the discrete automation part of Emerson. Mhmm. Because most of, people would know Emerson by the Rosemont, for example, pressure, Fisher valves, and then the, you know, the delta v, DCS. Right? This is the discrete automation part, and that’s why probably something new, for everybody here. Thank you very much. So when I look at that in a nutshell, we, of course, have to put the sensory devices, the PLC on top, the HMI scanner. And, basically, what we provide is real time monitoring of this particulate, emissions. We detect but also locate where the leak is by compartments in rows. You can see on the picture that, on the top of this HMI screen, we have a filter unit with three compartments, compartment one, two, three. And each compartment has these rows on top, which is the number of rows, then the more a number of filter bags that, within each, compartment. So, therefore, just locating which compartment and which row, you have a problem, I can tell you it saves half day of the people, in the maintenance. We also optimize the push at cleaning. It’s an, patent based algorithm that is completely adaptive, and works not just with the post valves, but, we put, head pressure sensors. And this fluctuation and the differential pressure that we measure from the outlet and inlet allows us, of course, to, increase or decrease the frequency of these push heads, which allows not only to be more efficient, but also minimize compressed air. And then finally, when you talk about solidoids involved diaphragms, these ones we can indicate one by one where they have problems. So, therefore, if you look at down to the other HMI screen, there are two rows on top. The one that is a solenoid, the one that is a diaphragm, and these vertical bars are the filter bag health. If they are getting closer to red with the high levels, meaning that, their life span is already gone. And if you have, light indicators on the solenoid, the diaphragm depend of the color might be that you have a short circuit fail, open diaphragm. Therefore, you have also to replace. And, basically, when we install that solution, sometimes our customers, ask it to also integrate with their control systems. So, therefore, they compress their generation, the fan, the hoppers, the safety alarms, of the plant sometimes are fully integrated as well. Now let’s talk very much about few features features because these are the ones that probably you haven’t seen yet. Wanna talk about our HMI control system is based on Movicon, Movicon next platform. And, basically, it provides everything that you know from the Scott HMI. And that’s why to use this in general for applications like OIE, energy management, in some others, infrastructure monitoring, like, smart cities, wastewater facilities, solar, mega mega plants, etcetera. Of course, it provides data visualization, but, I like to highlight that, you could ask we provide connectivity to all major POCs that you can imagine, with communication drivers. Of course, the open standards like OPC UA, like, Modbus. And on the lower part, the the green, let’s say, the the gray part here is what we used for that solution. Sometimes we use a geo maps, to indicate where the filters are. Some geo references, let’s say geo fences as well. The people have to be, with a personal protection equipment to be there. So there are some, real time, data that, of course, we are collecting for the particle emissions and other elements like differential pressure, header pressure. And then you have the headlines. You can see some screens that are completely dedicated to alarms and alerts. And one of these, diagnostics that you see are related to the solenoid, to the filter bag, and to the diaphragm diagnostics. A lot of them are diagnostic get diagnosed in different ways. For example, the solenoids, we look into the power output of our IO cards to see if the valve post the solenoid is open or complete short circuit. The filter bag, I already explained it. We detect with some logic with the the particle sensors, And the diaphragm diagnostics is based on the header pressure because if it’s this diaphragm is completely open, the differential pressure within the chamber, it starts fluctuating, and then you know that there’s something wrong there. But all of them increases the filtration efficiency, changes from reactive to predictive maintenance, of course, keeps the site compliant, minimize dust emissions, and for sure increase equipment lifetime, like the filter units, and reduce the compressed air usage. If you sum up all of that, the return in investment is it might be quite fast, of course, for large big large installations might be within two years, but it’s still a very fast return in investment for that particular solution. That’s what it looks like. A little bit, let’s say, zoom in. You see that they’re not nice looking, but they indicate graphically where the issues are, the number of issues, on this screen about thresholds alerts. The second one on the right side, is like the number of cycles. Imagine that every pulse valve would have, about a couple of millions of cycles of lifetime. Here, you can at least predict when or how many spare parts that, you need to have in the next quarter. And then, the yellow or red signals means that, red gone, you have is a faulty. And the white ones or the red the yellow ones are the ones that, you need to watch because they’re getting closer to the lifetime dead of lifetime. The other aspect is, like I said, when thus collector systems, you acquire that without the solution, it comes with this sequence box, which basically is a time based posting. So it keeps posting three to six minutes, like I I said, hundred milliseconds, but it can change. It’s it’s fixed. And that means that leads to, an excessive use of the post valve. So you’re going to wear out quite sooner than it should, but also reduce the valve back life because stretching the the the back filters, of course, you’re gonna also wear out, and you waste much more compressed air than than probably you should. That’s why we implemented this other two types of a post jet cleaning methodologies. One is on demand. That really depends on the high differential pressure between the the chamber and, you can set, in the in the solution how these multiple filter lines are going to operate normally, And this differential pressure threshold can be, for example, when the efficiency is getting bad, the differential pressure gets lower. And then if that is within a certain band, you can estimate that, there is accumulation of the cascade. The other one is very, intelligent. It’s a function block, in our PLC that, does a dynamic change. So, therefore, you put the single set point and the adaptive algorithm based on the virtual pressure starts controlling the intervals between the posts. So the idea is that to optimize by eliminating unnecessary posts in the cycle of these valves and also minimizing the compressed air. Of course, when you install the solution and, you put the set point for the first time, the system needs a little bit time to learn, and it’s a learning algorithm that, starts adapting. And very soon, it starts performing optimally. Okay? Shawn Tierney (host): Hey, everybody. I just wanna jump in here one more time. Just thank our members, both on YouTube and at the automationblog.com. I got some really exciting stuff coming up for you guys, in the fall. I’m I just have this huge plan that I’m working on. And so, I really just thank you guys for being members. Don’t forget, you get access to Discord. Don’t forget, there’s a whole library of older episodes you get to watch. It’s such just what I’m doing this month for members. It’s, you get a whole library of stuff. We did so much member only content over the last couple of years that you have hundreds literally hundreds of hours of content that you and only you get access to as a member, whether you’re on YouTube or you’re at theautomationblog.com. And, of course, if you have any questions about your membership, reach out to me directly, please. And with that, let’s go ahead and jump back into this week’s show. Eugenio Silva (Emerson): And that looks like that. This is just another, possibility to see. You see that, on the left side, you see a particular rows, and each of these rows have the filter bags. Each filter bag has a vertical bar that indicates the healthy of that solenoid diaphragm is on the top. And then, each of these compartments can navigate from one to another. Then you have other additional elements like the header pressure, differential pressure, particle density, and you have a trained diagram that, you are able also to generate reports, but you also also to to monitor, in order to to type a little bit, the parameters in order to be more efficient. And then, completely right side, if you have more than one dust collector, you can create different screens if you want. But the idea here is that the C1, C2 means compartment one, two, three. Again, a diagnostics that leads to preventative predictive maintenance and avoids completely reactive maintenance. Interesting, if you don’t know, in order to replace a single filter, in order to check if a solenoid valve is completely short circuits, In order to see if, a diaphragm valve is open, you needed to get there in this personal protection equipment using mask, gloves. You need to go up. You need to kind of get to know where these things are. And imagine that if you could avoid and just look at the screen and say, hey. I know that this is the compartment one of the filter a, and I know where I needed to look at. And by the way, I have the spare part because I had early indications to fix it. So then we are not just talk about reduction time, but, I guess, reduction costs and avoid to put people every time in such a very interesting environment. Okay? I’m not going through the the right part because you can imagine that this is a description of how things are usually done. And if you turn this around into a proactive predictive maintenance, then you have less and maybe faster steps. And you can prevent and can plan in advance when you wanna go with these, units, and you have to wear this equipment for protection. So very quickly in the developer position. Of course, like any solution, customers are interested to know if, they can pay off payback very quickly. So the return investment of that. So that’s why we check, the size, the number of, units, what’s the minimum size the customer could start with, because the it’s a pre engineered solution, how fast it could be that we implement in the whole site. It could be also, of course, calculate how much their current expenditure in terms of maintenance, reactive maintenance, the cost of utilities like compressed air, how many times they have to or they have downtime issues. And from that, we can prove very quickly, very simply that, it’s worth investing in automation. 20 to 30% of our reduction is a lot if you consider that they use a huge amount of compressed air. And compressors, they use electricity. So, therefore, if you’re able to reduce compressed air, you also increase your operation efficiency because cost of utilities is one of the points. Downtime is everything. Maintenance, it’s about preventing that you need to do these manual inspections. Just go there, check, and come back, and you see that, okay, we could wait for another week. But because I’m here, I’m going to change anyhow the filter. And that, of course, you’re not, increasing the lifetime of our equipment. And interesting that some downstream equipment, like the blowers, like the vacu pumps, if they get a lot of dust or excessive dust, they also, damage them. So therefore, maximizing maintenance, optimizing every step pays off in that sense. And finally, of course, customers do that because they want the full compliance. Every possible issue can be tracked, can be report. The efficiency of the systems can be audit ready, reports. It can re really prove that you can you are reducing part commissions. You provide a lot of visibility what’s going on. So, therefore, the technical teams are in very high confidence to operate the system. Because if without, they are operating blindly, And that’s why they feel a bit concerned many times that, might be that the bad things are just going to happen. In a nutshell, we talk about savings, extending the filter life. We talk about savings, reduce the compressed air. We can avoid downtime. Each downtime is one event that costs not only in the maintenance part here, but also the whole production costs that are not calculate here. And half the penalties that, if you have a single issue, it’s gonna be a big one. So, therefore, it’s a good way to give customers an idea why they should invest the CapEx parts and how we can help with the OPEX to save, their budgets in the sense of operating dust collector systems. So, Shawn, if I have time three minutes, I’m going to run this HMI demo because then you can see on the screen how the different screens are operated, but it’s up to you if I if I if if I need to do that. Shawn Tierney (host): Yeah. Go ahead. Eugenio Silva (Emerson): Okay. So this is an HMI demo, of course, simulated here because imagine it’s not possible to connect to live or to have all this whole equipment. So then I’m going to click here. So, basically, you see how a operator would navigate the type of information that, is provided. I made this click through very quickly because then we don’t owe too too much time here. But you see that, you are able to trend the particle density, the air consumption. You can set the alarms. You can indicate which boost valve is not okay. How is the level of filter bags? And now the settings. The cleaning, these are the parameters that you can adjust. Like I said, we have an adaptive learning algorithm, but in many cases, you needed to steer at least set up, the sensors as well, how sensible sensitivity of that. There are many different thresholds. And then the diagnostic part, for the diaphragm and the rupture where you can detect. And once this is done, you can see that, you have, quite, interesting information. For example, if you change, you devolve, you reset the counter. These are the alarms that you can acknowledge, etcetera. Okay? And, that’s it. That was the case. Shawn Tierney (host): Yeah. That gives you a good idea of what you’re getting with as far as the HMI is concerned, and, it’s good to see a full screen. I mean, it looks it looks like a very well designed HMI. From my perspective, it looks like it’s really giving you it’s focusing in on any errors. So you have, like, just standard graphics, a very good looking graphics, and then if there’s an error, you see it in red or yellow, really calls the eye to it. But, Eugeno, I see that, there’s a QR code on the screen right now. Can you tell people where that goes? Eugenio Silva (Emerson): Yes. It goes to the product page on our Emerson.com site. And from there, you can request for demo. We can request for proposal. We can request for more information. So this is the entry point for you to go to know, how it how we provide that solution, which kind of, basic elements. And there, we have also the related product pages if you wanna get, get to know more. Shawn Tierney (host): And I think the important part here is a lot of times you you, you know, when when you have a dust collector system that is that is constantly needing care, right, to keep you in compliance and make sure your products are products are being made correctly and you’re keeping people safe and all of that, You know, these systems, you’re gonna they’re they’re gonna be expensive. And, you know, larger systems, of course, are gonna be expensive. And so that cost savings, it’s like energy savings we do with VFDs on pumps and fans. Right? Or energy savings we do when we’re doing lighting, the folks over at Emerson are gonna wanna help you kinda quantify that because, you know, they know that for you to be able to justify not only, hey. This has given us a lot of problems. We know it’s costing us money. You also wanna know your ROI. Right? And so they’re gonna work with you on that because that’s on these big projects, those are those are some of the things that we have to look at to be able to, you know, to budget correctly. Anybody who has ever been in the budgeting part of a company knows you just don’t spend money because it’s fun. You know, you have to have a reason beyond everything. So I would I would guess I’m right on that, Eugenio. Eugenio Silva (Emerson): Yes. And, Shawn, although I just covered the technical part, of course, without any commitment, we can talk to customers and consult them Yeah. To look it around and see, in terms of maturity, how they operate this dust collector systems. We can, of course, check the install base. We have a questionnaire, that can fill it in. We can understand the size. We can, for example, talk about the energy consumption, the number of, hours that they are spend or active maintenance. And based on that, we give them opportunity to analyze whether they want to invest in that solution, which is a CapEx investment, but, also improve how much reduction they could have on the OPEX part. Shawn Tierney (host): Yeah. Which is which is, yeah, how they’re gonna justify it. Well, Eugeno, I wanna thank you for going through that. I really enjoyed your presentation. I learned a lot more about about, this product line and actually this product category than I that I knew coming in, and you’re I think you did a great job of walking us through it all. So thank you very much for coming on the show. Eugenio Silva (Emerson): Shawn, on behalf of Emerson, we appreciate this opportunity. It’s my first one here, so I also enjoy it, and this was was great. A great conversation, great questions, and, thank you. Shawn Tierney (host): Well, I hope you enjoyed that episode. I wanna thank Eugene for coming on the show and bringing us up to speed on dust collector systems. I really didn’t know all of those technical details, and I really appreciate him going through that. And it’s cool to see how they integrated so many different Emerson products into that solution. I mean, it’s just not like a PLC into my o. The sensors, this I mean, you guys, sorry. I’m not gonna go through it again. But in any case, really appreciate that. And I also appreciate our members who made the video addition possible. Thank you, members. Your $5 a month not only locks this video, but so many other videos that we’ve done, hundreds of videos I’ve done over the last twelve years. So thank you for being a member and supporting my work. I also wanna thank the automationschool.com and the automationblog.com. I hope you guys listened to that update that I included in the show. So many good things happen at both places. I hope you guys would take a moment to check out both websites. And with that, I just wanna wish you all good health and happiness. And until next time, my friends, peace. The Automation Podcast, Episode 241 Show Notes: To learn about becoming a member and unlocking hundreds of our “member’s only” videos, click here. Until next time, Peace ✌️  If you enjoyed this content, please give it a Like, and consider Sharing a link to it as that is the best way for us to grow our audience, which in turn allows us to produce more content

www.iotusecase.com#SmartBuilding #WorkplaceExperience #FacilityManagementIn Episode 176 des IoT Use Case Podcasts spricht Gastgeberin Ing. Madeleine Mickeleit mit André Lange und Sebastian Creischer von ICONICS über smarte Arbeitsplatzlösungen in modernen wie bestehenden Gebäuden.Im Fokus: Wie sich heterogene Infrastrukturen mit IoT effizient vernetzen lassen – modular, kabellos und skalierbar. Praxisnah, aus erster Hand.Folge 176 auf einen Blick (und Klick):(14:30) Herausforderungen, Potenziale und Status quo – So sieht der Use Case in der Praxis aus(22:42) Lösungen, Angebote und Services – Ein Blick auf die eingesetzten Technologien(29:40) Übertragbarkeit, Skalierung und nächste Schritte – so könnt Ihr diesen Use Case nutzenPodcast ZusammenfassungSmarte Gebäude gibt's nicht nur im Neubau. In dieser Folge zeigen André Lange und Sebastian Creischer von ICONICS, wie sich selbst ältere Büro- und Industriegebäude mit IoT-Lösungen intelligent vernetzen lassen – ganz ohne aufwendige Umbauten.Im Fokus stehen zwei Ansätze:Building-Centric Anwendungen für Energie, Klima, Lüftung – und People-Centric Lösungen für Arbeitsplatzbuchung, Navigation und Raumauslastung. Beides lässt sich mit ICONICS Software modular integrieren, etwa über Genesis64 und den Intelligent Building Software Stack (IBSS).Die Gäste erklären, wie sich verschiedenste Systeme und Sensoren – ob BACnet, Modbus, OPC UA oder MQTT – über eine Integrationsplattform sicher verknüpfen lassen. Selbst Herausforderungen wie denkmalgeschützte Bestandsgebäude lassen sich damit smart meistern.Spannend sind Use Cases wie digitale Raumbuchung, ad-hoc Navigation per App oder Präsenz-Tracking fürs Flächenmanagement. Alles lässt sich kabellos, skalierbar und ohne Störung des laufenden Betriebs integrieren.Zum Ausblick wird's zukunftsweisend: KI-gestützte Anomalieerkennung, Kollegen-Finder per Bluetooth oder smarte Paketservices im Büro zeigen, wohin die Reise geht.

4.0 Podcast listeners, listen up! If your plant floor still speaks in mystery Modbus and legacy PLC grunts while leadership wants shiny AI dashboards, the Edge Connectivity → UNS Workshop—live online June 17‑19, 2025—is your shortcut. In three hands‑on sessions we'll show you how to hook any asset, clean the data, and stream it straight into a Unified Namespace your MES, BI, and AI apps can actually use. Because you're part of the podcast crew, use code PODCAST40 at checkout for 40 % off, but only until May 31. Hit the link, claim your seat, and turn mystery data into real‑time insight—before your competition even knows what hit them.https://www.iiot.university/offers/jwyzWAMM?coupon_code=PODCAST40

In dieser Folge von „TechnikDiskutiert“ sprechen Thilo und Thorsten mit Andras Schmalenberg von der KOSTAL Solar Electric GmbH, Produktmanager für PV-Wechselrichter und Speichersysteme. Es werden die folgenden Punkte in der Folge besprochen:-    Was ist ein Hybrid-Wechselrichter?-    Wie kann man mit einem Energiemanagement-System die Leistungsregelung der PV-Anlage verhindert werden.-  Wie wird ein Batteriespeicher an den Wechselrichter angeschlossen.-  Welche Schnittstellen sind bei Wechselrichtern wichtig (Modbus und EEBus)?.-   Einfache Feature Freischaltung von Zusatzfunktionen beim Wechselrichter durch Aktivierungscodes.-  Leistungssteigerung durch Repowering von Bestandsanlagen.  Für Fragen, Anregungen, Themenvorschläge oder Kritik erreicht ihr uns wie immer unter: ⁠kontakt@technik-diskutiert.de⁠. Links: www.kostal-solar-electric.com Repowering Tool Repowering- Tool: https://repowering.kostal-solar-electric.com/ NEU: PLENTIOCRE MP (einphasig) für Repowering von einphasigen Anlagen: DB WR+Bat G3 MP https://www.kostal-solar-electric.com/g3_mp_bat_db_deDB WR+Bat G3 https://www.kostal-solar-electric.com/g3-bat_db_de Datenblattt PLENTICORE G3: https://www.kostal-solar-electric.com/db_plenticore-g3_de Listemit kompatiblen Partnern (z.B. Wärmepumpe, Wallbox, Energiemanagement):https://www.kostal-solar-electric.com/compatible-partner Dateblatt Wallbox ENECTOR: https://www.kostal-solar-electric.com/db_wallbox_enector-ac-3_7-11_deDatenblatt Projektwechselrichter PIko CI 100: https://www.kostal-solar-electric.com/piko-ci-100_db_de PLENTICORE plus / G3 Modbus TCP Spezifikation:https://www.kostal-solar-electric.com/plenticore-modbus-tcp-spezifikation

Welcome back to your favorite (and only!) Controller Talk Podcast for one final episode before the holidays - diving into the essentials of LON and Modbus communication wiring! What better way to spread some holiday cheer anyways?

In November 2024, the global spotlight turned to BIMworld Munich, where Marek Koźlak, PhD, Founder and CEO of SIMLAB, took the stage to present a groundbreaking vision for the future of property management and construction technology. With an audience of industry professionals spanning the Architecture, Engineering, and Construction (AEC) and Facility Management (FM) sectors, Koźlak's presentation illuminated the transformative potential of digital twin solutions like SIMLAB STAGES and SIMLAB SIM-ON. SIMLAB's mission, as Dr. Koźlak stated, is simple yet powerful: "Helping you feel more comfortable with your property." This vision resonates across all phases of a building's life-cycle, from design and construction to operation, maintenance, and even renovation. By bridging gaps in interoperability and offering intuitive tools for asset management, IoT control, and collaboration, SIMLAB is creating a unified digital ecosystem for the AEC industry. Addressing the Key Challenges in the AEC and Property Management Industries Dr. Koźlak identified a major challenge plaguing the industry: disconnected data systems. Building projects generate immense amounts of data—blueprints, BIM files, 3D scans, IoT sensor data, and maintenance records—but these datasets often exist in silos, preventing effective collaboration. SIMLAB's solutions, powered by cutting-edge Matterport integrations and IoT technologies, unify this data into a cohesive platform. SIMLAB's innovative platforms, STAGES and SIM-ON, leverage partnerships with industry-leading technology providers to deliver a seamless digital twin experience. These integrations ensure interoperability, efficiency, and advanced functionality across all phases of a building's life-cycle. Key integration partners include: Matterport: Providing high-quality 3D scans for immersive digital twin environments. KNX IoTech: Enabling seamless building automation and IoT integration. Schneider Electric: Supporting building automation through the Wiser for KNX logic controller. Procore: Enhancing construction management workflows and data exchange. NETxAutomation:: Facilitating advanced building system communication standards. NavVis: Delivering precise indoor mapping and spatial data solutions. FIBARO (a Nice company): Integrating IoT device control and automation. Helvar and DALI: Supporting lighting control and building automation. VingCard, Kaba, and Salto: Providing access control solutions for smart properties. Modbus, BACnet, and OPC: Ensuring interoperability with industrial communication protocols. M-Bus and DMX: Extending automation capabilities for HVAC and lighting systems. EnOcean: Enabling wireless and battery-free IoT device integration. Fidelio/Opera and Infor: Streamlining hotel management systems and real estate operations. SNMP and MQTT: Enhancing IoT communication and system monitoring. These partnerships empower SIMLAB's platforms to centralize diverse data streams into a unified, user-friendly digital twin solution. Here's a deeper dive into how his presentation and SIMLAB's solutions resonated with specific attendee groups at BIMworld Munich: For Facility Owners and Managers: Simplifying Operations with Digital Twins Facility owners and managers, tasked with overseeing the operation and maintenance of complex buildings, face daily challenges in tracking warranties, invoices, maintenance schedules, and IoT device performance.  Dr. Koźlak demonstrated how SIMLAB SIM-ON revolutionizes facility management by providing a spatial 3D interface powered by digital twin technology. From real-time IoT monitoring to task management and maintenance scheduling, SIM-ON consolidates all data into a single, user-friendly platform. Why This Matters: Facility managers can easily locate problem areas, manage assets, and monitor IoT systems in real-time, reducing the burden of juggling disparate tools. For building owners, this translates into lower operational costs, streamlined maintenance, and improved tenant satisfaction. For Architects and Interior Designers: Empowering Design Visualization For architects and designers, Koźlak highlighted how SIMLAB's STAGES platform serves as a powerful collaboration and visualization tool. By integrating Matterport scans with BIM data, architects can view side-by-side comparisons of design plans and as-built conditions.  The ability to track construction progress visually, annotate scans, and communicate issues with contractors fosters a collaborative workflow. Why This Matters: Designers gain unparalleled insight into project stages, from early blueprints to final finishes, ensuring that their creative visions are realized without costly deviations. The platform also simplifies client presentations by providing clear, visual documentation of progress. For Construction Companies and General Contractors: Enhancing Collaboration and Efficiency Construction professionals deal with tight deadlines, budget constraints, and complex coordination among teams. Dr. Koźlak showcased how STAGES addresses these pain points with its construction progress monitoring and issue tracking tools.  The platform's timeline feature enables contractors to review the status of a project at any given stage, compare scans over time, and resolve discrepancies quickly. Why This Matters: With all construction data centralized and easily accessible, contractors can eliminate communication gaps, reduce rework, and complete projects faster. STAGES empowers teams to collaborate seamlessly, whether they are onsite or remote. For Insurance Companies and Financial Institutions: Improving Risk Assessment Dr. Koźlak emphasized the value of digital twin technology for insurance and banking professionals. SIMLAB's platforms provide a comprehensive historical log of property documentation, including warranties, maintenance records, and IoT sensor data.  Insurers and banks can access accurate, up-to-date information about a property's condition, reducing risks during underwriting or claims processing. Why This Matters: With SIMLAB's solutions, financial institutions gain a transparent view of assets, enabling better decision-making and reducing liability risks. Insurers can also leverage visual documentation to speed up claims assessments and minimize fraud. For Real Estate Developers and Property Owners: Elevating Asset Value Real estate developers and property owners attending BIMworld Munich learned how SIMLAB's digital twin platforms can enhance the value and marketability of properties.  By providing a detailed visual record of a building's life-cycle, SIMLAB's tools help developers showcase the quality and sustainability of their projects to potential buyers or investors. Why This Matters: Developers can differentiate themselves in a competitive market by demonstrating transparency and a commitment to innovation. The ability to provide potential buyers with a complete digital history of the property adds immense value. A Call to Action: Embracing the Future of Digital Twin Technology Dr. Koźlak concluded his presentation with a bold vision for the future of digital twin technology. As SIMLAB prepares to expand its footprint in Europe and the United States, the company is actively seeking collaborations with AEC professionals, real estate developers, and technology integrators.  With their solutions already generating impressive traction — 2,000 customers and over €2 million in revenue—SIMLAB is poised to redefine how properties are designed, managed, and maintained. The potential of digital twin technology is limitless, and SIMLAB is leading the charge. As Dr. Koźlak aptly stated, "Coordination, communication, and collaboration are the keys to unlocking the full potential of the built environment." This transformative message from BIMworld Munich serves as a rallying cry for industry stakeholders to embrace innovation and join SIMLAB on their journey toward a smarter, more connected future. Next Steps: Discover How SIMLAB Can Transform Your Property Management Ready to revolutionize how you manage and operate your properties? Explore SIMLAB's cutting-edge solutions for digital twins, construction management, and IoT integration today. Here's how you can take the next step: Visit Our Website: Learn more about our platforms, STAGES and SIM-ON, and how they can benefit your projects at www.SIMLABinc.com. Set Up a Meeting: Have questions or want a personalized demo? Contact us to schedule a meeting and discuss your specific needs. Reach out via our Contact Us page. Let's work together to simplify your building's lifecycle management and unlock its full potential with SIMLAB's innovative technology.

Get on the Supermarket Academy waitlist now! New program to supercharge your supermarket refrigeration expertise. This episode of our “CO2 Experts” series features Rusty Walker, Training Director with the North American Sustainable Refrigeration Council (NASRC), leading an in-depth discussion on troubleshooting CO2 system electrical diagrams. The conversation is loaded with tips and examples aimed at helping refrigeration technicians troubleshoot service calls faster and get more confident with electrical principles. This “CO2 Experts Live” series is all about providing deep technical training so technicians and engineers in the field can get some quick tips on how to troubleshoot more efficiently and confidently. Links to more in this series below. In this conversation, we cover: -Basics of electrical symbols -Electrical relays and switches -Voltage and troubleshooting techniques -Electrical troubleshooting tips -Tools refrigeration technicians need to carry -Importance of understanding wiring diagrams -Understanding the electrical circuit -Using meters for  -Tips for reading wiring diagrams -Bipolar stepper valves -Modbus troubleshooting  Helpful Links & Resources: Connect with Rusty: rusty.walker@nasrc.org   Learn more about the NASRC: https://nasrc.org/  Episode 253. CO2 Experts: Designing an Oil Management System with Nabil Cook Episode 257. CO2 Experts Live: Case Controllers with Kevin Mullis Episode 246. CO2 Experts: Startup and Commissioning with Kevin Mullis BOOK A CALL with Trevor to learn more about refrigeration training programs. Upcoming Servicing Compressors, Supermarket and CO2 Trainings: Learn More Here Learn More About Refrigeration Mentor: https://refrigerationmentor.com/ Get your FREE Service & Compressor Troubleshooting Guide: Access Here Refrigeration Mentor Linktree Refrigeration Mentor on LinkedIn Refrigeration Mentor on Instagram Refrigeration Mentor YouTube Channel

Why did JPEmbedded, a member of the #STPartnerProgram, choose to use an STM32F7 in its APIS Box? See how this network protocol converter for Modbus and MQTT brings cloud connectivity and interoperability thanks to the #STM32 ecosystem.

Podcast: Emerson Automation Experts (LS 23 · TOP 10% what is this?)Episode: Building Cybersecurity Robustness in Pipeline Operations PodcastPub date: 2024-07-25Manufacturers and producers across all industries know the challenges in keeping their operations cyber-secure. Industries such as pipeline transportation and electrical & gas distribution networks face additional challenges in the wide geographic spread of their operations and the need for reliance on public communications networks. In this podcast, I'm joined by Emerson cybersecurity expert Steve Hill to discuss these additional challenges and ways the companies in these industries, suppliers, and federal regulators are collaborating to develop and implement best practices for strong cyber resiliency. Give the podcast a listen and visit the SCADA Solutions & Software for Energy Logistics on Emerson.com and the AspenTech Digital Grid Management page for methods and solutions to improve your cybersecurity defenses and ongoing programs. Transcript Jim: Hi, everyone. This is Jim Cahill with another “Emerson Automation Experts” podcast. Pipelines cover a wide geographic area and require continuous monitoring for safe, efficient, and reliable operations. Today, I’m joined by Steve Hill to discuss the challenges pipeline operators face in keeping their pipeline networks cybersecure. Welcome to the podcast, Steve. Steve: Thanks, Jim. Pleasure to be here. Jim: Well, it’s great to have you. I guess, let’s get started by asking you to share your background and path to your current role here with us at Emerson. Steve: Thanks, yeah. I’ve been in the automation and SCADA industry for about 40 years, started on the hardware design and communications that then moved over to software. And it’s nearly 20 years I’ve been with Emerson. I joined as part of the Bristol Babcock acquisition. My main focus now is working in wide-area SCADA as the director of SCADA Solutions for Emerson, and most of that’s working in the oil and gas industry, working with Emerson sales and the engineering teams and our customers as they design systems and products for the industry. And also, alongside that, for the last few years, I’ve been collaborating with CISA. That’s the U.S. government Cybersecurity and Infrastructure Security Agency as part of the Joint Cyber Defense Collaborative. Jim: Okay. That’s a nice, varied background. That’s really good for our discussion. So, what exactly do you mean by wide-area SCADA? Steve: That’s a great question. There’s a SCADA system where the software is monitoring equipment across a very wide area. It might be a very large geographic area, like a pipeline or gas, or water distribution network, or perhaps a well field. I mean, some of the systems, for example, I was speaking to a customer last week who is monitoring an entire pipeline across Peru, and yet, their control centers are actually in Mexico. So, to do that kind of thing, the equipment is usually connected via public networks. You know, private networks don’t extend that far, and even the control centers may be widely distributed. And as part of that, compared to in-plant control, there’s an assumption that your communications are clearly not gonna be 100% perfect. You’re gonna lose communications either momentarily, like with cellular networks, and when, for example, like we’ve got in Texas this week, with natural events like hurricanes can cut communications for hours. But because these systems are all critical infrastructure, such as pipelines or electrical distribution, the actual operations, the process, must never be interrupted. Today, we’re talking about cybersecurity, and that same sensitivity is why these systems are now the target to some of the most sophisticated cyberattacks. Jim: Okay, that gives a picture of the breadth of these types of SCADA systems, and you had mentioned you’d work with CISA, the cybersecurity infrastructure defense agency, and the Joint Cyber Defense Collaborative, which I’ll just call JCDC for short. Can you give some more examples on that work? Steve: Yeah. Really, I could give you a bit of background. Probably many of our listeners know that there’s been several successful cyberattacks against critical infrastructure over the last few years. Probably the most famous in the pipeline industry was an attack that’s referred to as the Colonial Pipeline attack. That was actually a criminal ransomware attack that resulted in gasoline and jet fuel shortage across the Eastern U.S. for several days, and that was criminals basically trying to get money. And it was almost a random attack, it wasn’t targeted. However, there have been actual state-sponsored attacks, and probably the one that was most successful was prior to the Russian military attack against Ukraine. They actually instituted several successful cyberattacks against the Ukrainian power grid. And very concerning is, in recent months, the U.S. infrastructure, including pipelines, have been successfully infiltrated by a group that are called Volt Typhoon, who are thought to be from the People’s Republic of China. So JCDC and CISA are working hard to really counter and protect against these threats. Jim: Wow. Well, that’s clearly a huge concern. What is the JCDC doing to address these challenges? Steve: Well, in 2023, so last year, JCDC facilitated the development of something called the Pipeline Reference Architecture. Basically, Emerson, alongside other industry vendors and also pipeline operators, participated in the development of this Pipeline Reference Architecture, which I’ll refer to as the PRA. It’s a fairly short document that outlines the design and operating principles for SCADA systems in the pipeline industry. And one thing the government is keen to point out, it’s not a regulatory document, but it does set out the best principles and is intended as guidance for the industry. Really, they want to work with the industry to come up with best practices. Jim: Well, it sounds like this PRA is another set of standards to address cybersecurity. Why is another document needed in the industry where a bunch of standards exist now? Steve: Yeah, that’s a question I and other members get asked quite a lot. The main reason is that wide-area SCADA represents a very different set of challenges to traditional SCADA, which we refer to as inside the wire. So for example, a refinery or a manufacturing plant, everything is in one location. But as I mentioned before, wide-area SCADA has got a very wide displacement, physically. It also actually has a lot of remote field workers. There may be folks working on that system hundreds of miles from base, and you’re also using communications networks that are not even owned or operated by the owners of the pipeline. Though this PRA is really intended for the pipeline industry, clearly, it’s applicable to almost any wide-area SCADA, that’s water or electrical industry as well. Jim: Okay, that makes sense. So those are definitely challenges that don’t exist for more automation systems, as you say, inside the wire. Tell us more about how the PRA addresses these. Steve: Well, the big thing is segmentation, basically, taking the network and splitting it into different levels that represent different areas of the operation. For example, the internet would be what’s referred to as level zero, and moving all the way down to the bottom of the network, that’s level nine. And the levels in between that represent different levels of trust. Now, those who are familiar with cybersecurity and SCADA are probably familiar with something that is called the Purdue model, which I think first came out in the late 1980s, and that also splits up SCADA and control networks and actually business networks into different levels. However, when that came out, the internet was in its infancy. No one would ever have used the internet or even really public IP networks for their connectivity. So it doesn’t really take into account many of the things we take for granted today in these systems. So the PRA is intended to expand and take into account the reality that, for example, some of this critical data will actually be transiting across a public network, right? And in order to achieve that with this segmentation, we’re using a concept called Defense in Depth, right? And as you go down the different levels of the network, the assumption is you can trust each item on that network better. So, for example, on the internet, you don’t trust anything, but when you get down, let’s say, to the communications between an RTU [remote terminal unit] and a gas chromatograph on a local serial link, you might completely trust that. Now, it’s interesting, although that’s part of the PRA model, that does actually conflict with a security concept called Zero Trust, which is something that Emerson has really based our products on. But both zero trust and defense in depth are valid. Jim: Now, you had mentioned a couple of concepts I’d like to explore a little bit more in there, and let’s start with zero trust. Can you explain that concept to us? Steve: Oh, yeah. Yeah. Zero trust is a concept where any piece of equipment or software should trust nothing. Don’t trust anything else on the network, don’t trust the network to be safe, and it should not rely on anything else for protection. And historically, SCADA was protected, for example, by firewalls. You would use insecure products that were known to not be secure because they were developed perhaps 20 or 30 years ago and hide them behind firewalls, and that’s really how we’ve handled security today. But there’s a realization you can’t do that. So we now need to design products so that they don’t trust anything. But the reality is many of our customers, Emerson’s customers and pipeline operators, have devices that were installed perhaps 30 years ago. That’s the typical lifespan of some RTUs and controllers in this industry. So as a result, when you get down to the lower levels of the network, zero trust doesn’t work. So you do have to have levels of additional protection. So for example, if you had a Modbus link, which is basically insecure almost by design, that should be protected by additional levels of firewalls and so on. But if you’re designing a modern product, it should be designed so it doesn’t rely on anything else. And that’s the concept of zero trust. Jim: Okay, got it. So don’t trust anything. Everything must be proven out. And the other concept you talked about was defense in depth. So, what does that mean? Steve: Well, the phrase is most commonly used where we’re talking about a network with multiple levels in. So when you come from, for example, the internet into your business network, you would have a set of firewalls and what’s called the demilitarized zone. And then when you go from your business network down to your controls network, you’d have another set of firewalls. So it’s multiple levels of protection. However, that same concept should be used actually within products as well. And, in fact, Emerson takes that very seriously with our secure development lifecycle certifications, IEC 62443, and how we design those products. Jim: Well, that’s good. As you get those two and as you put in more modern technology, that it complies and has that cybersecurity built into mind there. So, can you give us an example of how it’s built in? Steve: Yeah. That great one. If I take, for example, the Emerson FB3000 RTU, that’s a flow computer and a controller device that’s designed specifically for the oil and gas industry, especially for pipelines, an obvious concern is that that may be attacked externally to modify the firmware. Now, at the first level, the RTU itself has secure protocols. It uses something called DNP3, which would, in theory, provide access to the device. But then the firmware, when we issue new firmware, we put it on a website so we have protection of the website, we also publish a hash, which is basically a unique key that the customer downloading the firmware can check. It hasn’t been modified by anyone attacking the website. But then, when they actually put it into the RTU, so they’re updating firmware, the RTU will check that that firmware was developed by Emerson and was intended for that device. It does that by certifying certificates on the load. Now, once it’s in the device and it’s running in the field, you might say, “Well, the task is done,” but there’s an additional level of protection. It will continually and on boot, check that firmware, make sure the certificate still matches, it’s not being changed. And if it has been changed, it will actually revert to a known good factory firmware that’s basically embedded in the device. So you can see that there’s really five or six different things all checking and ensuring that firmware in that device was not compromised. So basically, multiple levels within the device, and in addition, there’s multiple levels on the network. So the bad guys have to get through a lot of different levels to damage or compromise the device. And we’re trying to do that with everything we design today. Jim: Yeah. And with modern cryptography and making any change completely will change that hash and everything and make it impossible to slip something in without it being noticed. So that’s really a nice thing. Steve: Yeah. And the fact that even if it detects it, it then goes back to factory firmware, which may be a slightly older version, but your operation will keep running. It will keep controlling, which is a very nice feature. Jim: Yeah, that’s a great example there. I guess, going back to the PRA, what else does it include other than the segmentation that you discussed? Steve: There’s about 10 high-level principles that cover aspects of the design and operation of the SCADA system. And for each of these, there’s various examples and guidance on how to actually follow the principle in a real-world system. So, for example, there was a whole section on how to manage third-party devices in the contractors, because on a pipeline system, you’re almost certainly gonna have, for example, engineers from Emerson coming in from third parties. So it gives examples on the real-world aspects of operating the system. Jim: Are there other examples from it you can share? Steve: Yeah. One important one is when you’re designing the system, you should identify and document all of the different data flows that occur. And that’s, when I say data flow, communications or conversation between different pieces of equipment. So, for example, this RTU may communicate with that SCADA platform on this particular machine and may communicate with a measurement system on another machine, document all of those data flows, and then deny all other data flows by default. Then, after the system is running, continually monitor it passively. And if you see an additional communication, say, between two pieces of equipment that normally never communicated or didn’t communicate on a particular IP socket, flag that immediately, because it may be something that’s going on that was unexpected. It certainly was outside the original design of the system. Jim: This has been very educational. Thank you so much, Steve. Where can our listeners go to learn more? Steve: Well, really a couple of places. If you go to the CISA blog, which is at www.cisa.gov/news-events, there’s details there. The actual PRA was published on March the 26th of this year. And also, if you want to discover more about Emerson’s involvement in wide-area SCADA and the cybersecurity associated with it, if you go to Emerson.com/SCADAforEnergy, you’ll find some information there. Jim: Okay, great. And I’ll add some links to that and to some of the other things we discussed in the transcript. Well, thank you so much for joining us today, Steve. Steve: Not a problem. It’s a pleasure. -End of transcript-The podcast and artwork embedded on this page are from Emerson Team, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.

Podcast: Nexus: A Claroty Podcast (LS 32 · TOP 5% what is this?)Episode: MITRE on Caldera for OTPub date: 2023-10-05Misha Belisle and Blaine Jeffries of MITRE join the Claroty Nexus podcast to discuss  Caldera for OT, a new set of operational technology plugins for the open source core Caldera adversary emulation platform. Caldera for OT supports the Modbus, BACnet, and dnp protocols, and Belisle and Jeffries hope to add future support for additional protocols. Red and purple teams may use Caldera for OT for adversary emulation in order to understand the exposure of these protocols to attacks. Caldera for OT is available here.The podcast and artwork embedded on this page are from Claroty, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.

Podcast: Nexus: A Claroty Podcast (LS 28 · TOP 10% what is this?)Episode: MITRE on Caldera for OTPub date: 2023-10-05Misha Belisle and Blaine Jeffries of MITRE join the Claroty Nexus podcast to discuss  Caldera for OT, a new set of operational technology plugins for the open source core Caldera adversary emulation platform. Caldera for OT supports the Modbus, BACnet, and dnp protocols, and Belisle and Jeffries hope to add future support for additional protocols. Red and purple teams may use Caldera for OT for adversary emulation in order to understand the exposure of these protocols to attacks. Caldera for OT is available here.The podcast and artwork embedded on this page are from Claroty, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.

Misha Belisle and Blaine Jeffries of MITRE join the Claroty Nexus podcast to discuss  Caldera for OT, a new set of operational technology plugins for the open source core Caldera adversary emulation platform. Caldera for OT supports the Modbus, BACnet, and dnp protocols, and Belisle and Jeffries hope to add future support for additional protocols. Red and purple teams may use Caldera for OT for adversary emulation in order to understand the exposure of these protocols to attacks. Caldera for OT is available here.

Today my guest is James Parsons of SCADAmatic who introduces us to their SimServe product in this episode of The Automation Podcast. For more information, check out the "Show Notes" located below the video. Watch the Podcast:  Listen via Apple, Google, Pandora, Spotify, iHeartRadio, Stitcher, TuneIn, YouTube, Rumble, Amazon Music, Podcast Index, Deezer, Podchaser, RSS, or below: The Automation Podcast, Episode 157 Show Notes: Special thanks to James Parsons of SCADAmatic for coming on the show to discussSimServe! You can now support our work and join our community at Automation.Locals.com! Thanks in advance for your support! Vendors: Would you like your product featured on the Podcast, Show or Blog? If you would, please contact me at: https://theautomationblog.com/contact Until next time, Peace ✌️  Shawn M TierneyTechnology Enthusiast & Content Creator Have a question? Join my community of automation professionals and take part in the discussion! You'll also find my PLC, HMI, and SCADA courses at TheAutomationSchool.com. (122 views)

Chris integrates full home power monitoring into Home Assistant, while Alex tames the AI and rushes to replace Dark Sky. Special Guest: Brent Gervais.

Vi har fått mange leserbrev i løpet av 2022 - Det som har vært gjengang har vært Protokoller, hva er BACnet, Modbus, KNX og hva er dette nye med API, Webhook og MQTT?For å hjelpe oss å demystifisere protokoller har vi fått med Eirik Bjørnstad fra Evotek for å bistå oss!Eirik har en lidenskap for bærekraft og drar full nytte av sin tekniske bakgrunn, bachelor i elektroteknikk og mastergrad i ledelse til å engasjere seg i spennende og innovative prosjekter, for å bygge en bedre morgendag.

CO2 Monday guest is James Darby from Resource Data Management.  James shares with us what RDM has to offers the industry for a solid refrigeration control platform.  Topics we discussed: Communication Protocols IP vs Modbus tcp/ip vs Modbus RTU RDMs CO2 superPAC controller The flexibility advantage of RDM controllers for new installs and retrofits RDM PLC controllers for customized system control design The advantage of the Data Manager that can log years of data They types of pictorial blocks to design a full customized control package. Examples like controlling parallel compressors or ejectors How RDM hubs can reduce installation cost and change setpoints in a click or two with the broadcast feature RDM Case Controllers which have many benefits like its ability to control all major manufactures EEVs.    Suction Float, Network Trim Control, Case Performance, Night Blind Detection, Defrost Warning and much more Learn more about RDM at resourcedm.com Get in touch with James on linkedin https://www.linkedin.com/in/james-darby-40756138/ or at James.d@resourcedm.co.nz ====================================== All Access to Refrigeration Mentor Content:  Learn More Upcoming Compressor Masterclass: Learn More Upcoming Supermarket Learning Program: Learn More Free System & Compressor Troubleshooting Guide Subscribe to the Refrigeration Mentors video newsletter and get your Free Compressor Guide Youtube Channel: https://www.youtube.com/c/refrigerationmentor Connect with the Refrigeration Mentor IG: @RefrigerationMentor

It's Season 4 Episode 1 of Industrial Automation - It Doesn't Have To.

Energy metering.  Is that EASILY accomplished?  Are there well suited applications for metering AND can a building owner be confident about energy consumption?  (YES!)  Greg and Dan, our Ask Caleffi gurus, talk about energy metering during this episode of the podcast.  They talk Modbus-to-BACnet (say what??) and what applications are perfect for calculating BTUs in a specific space.  Interested in a real-life example?  No problem!  Dan digs into an actual case study of successful tracking of energy usage with the 7504 Series CONTECA heat energy meter in action.Want to hear YOUR QUESTION on Ask Caleffi?  Take this quick 4 question survey for your chance to hear your question in a future episode.Survey:https://forms.gle/fRfnU8Px3B1Lq7K69