Factory Field Notes

Vladimir Romanov
  • 0.0 (0)
  • Technology

Factory Field Notes is a practical podcast for manufacturing leaders, engineers, and technical managers who want real lessons from the plant floor. Hosted by Vladimir Romanov, the show breaks down automation, controls, SCADA, MES, OT networks, industrial data, downtime, reliability, project execution, and the messy work of modernizing factories without vendor fluff or empty transformation talk.

  1. 6d ago

    Ep. 18 | NAT or Readdress? The OT Network Decision That Shapes Your Plant for the Next Decade [Guide]

    NAT in industrial networks solves a real addressing problem and quietly creates three new ones. This is the buy or readdress decision, fully costed, from a live plant deployment. Most plants meet network address translation the same way. A new machine arrives, the builder has assigned an addressing scheme that has nothing to do with the plant, and somebody decides whether to renumber every device in that panel or put a NAT device in front of it. Subscribe for weekly breakdowns of the technical decisions that land on an engineering manager's desk. Learn more at Joltek:- IP Addresses in Industrial Automation and OT Networks: https://www.joltek.com/blog/ip-addresses-industrial-automation-ot-networks- Modern Plant Network Requirements for Manufacturing: https://www.joltek.com/blog/modern-plant-network-requirements-manufacturing- Plant Floor OT Networking: https://www.joltek.com/blog/plant-floor-ot-networking- IT and OT Architecture and Integration: https://www.joltek.com/services/service-details-it-ot-architecture-integration Readdressing looks cheapest on a quote and is not. Renumbering a panel needs connectivity to the PLC, the HMI, the drives and the servo drives, and in a Rockwell Automation environment that means a licensed copy of Studio 5000 or RSLogix, and very likely FactoryTalk View ME. Plenty of small and mid sized plants have nobody on staff who can do that and then verify every device still communicates. Then there is warranty, which rarely comes up in the engineering discussion and always comes up later. It sits with the original machine builder and is commonly void once the equipment is modified. If your team renumbers that panel and the builder can no longer reach it at the addresses in their own records, you own that conversation. The third problem catches technically strong teams. Putting everything on the plant network means deciding what traffic belongs there. A PLC and an HMI are usually fine. Hundreds of drives are a grey area. Vision systems publishing images to a server are not, and safety systems add their own polling load. NAT is the other route. It sits between the panel and the plant and translates one to one. The PLC at 192.168.1.10 inside the cabinet is published to the plant as 10.10.10.100, the HMI at .11 becomes .110, nothing inside the panel changes, and the builder's scheme survives. Rockwell Automation sells the 1783-NATR for this, higher tier Stratix switches can do it with the feature licensed, and vendors including Moxa build industrial switches with the capability. This is not a free translation layer. You only translate what you explicitly map, so a drive with no entry is genuinely unreachable from the plant side. An engineer at a desk running RSLinx can reach the PLC and cannot open that drive in Connected Components Workbench. Standing at the panel, they need a different address range on their laptop, and an IT provisioned machine may not let them change it. The workaround is that the NAT device usually holds an address on both networks, so you can add a temporary entry, do the work, and remove it afterwards. The hardware runs from roughly $1,000 to several thousand dollars per device. On top of that you pay engineering hours to build and document every entry, and you maintain two address schemes per machine for as long as that equipment runs. That spreadsheet becomes load bearing, and every contractor you bring in has to be told what they are walking into. Neither route is wrong, but neither is only about one panel. Once a plant starts down the NAT path it tends to spread into every machine that follows, so this is a standard you are setting, not a purchase you are making. Choose on purpose, write the choice down, and make sure the next person who opens that panel knows which one you picked. Timestamps0:00 The plant with a NAT device in every machine3:10 What network address translation actually is4:10 Why machine builders hand you an addressing problem6:40 Option one: readdress every device in the panel9:00 What readdressing really costs in licences and hours10:00 The warranty exposure nobody budgets for10:40 Which devices actually belong on the plant network12:22 Option two: how NAT sits between the panel and the plant14:30 The laptop problem: plant side versus equipment side16:45 When an IT provisioned laptop cannot reach the drive17:25 The temporary translation entry workaround18:30 What NAT costs to buy and to keep running20:50 How to make the call More from Joltek:Website: https://www.joltek.comBook a modernization consultation: https://www.joltek.com/book-a-modernization-consultation

  2. Sep 4

    Ep. 17 | Structured Text vs Ladder Logic: Why "The Right Tool for the Job" Is Lazy Advice [Full Q&A]

    Structured text vs ladder logic is the oldest argument in PLC programming, and this week a CODESYS convert changed sides and said so publicly. I agree with where he landed and not with how he got there. Subscribe for weekly industrial automation and manufacturing discussions. Learn more at Joltek:- IP Addresses in Industrial Automation and OT Networks: https://www.joltek.com/blog/ip-addresses-industrial-automation-ot-networks- Root Causes of Downtime in Industrial Automation: https://www.joltek.com/blog/root-causes-downtime-industrial-automation- Rockwell PLC Lifecycle and Migration Guide: https://www.joltek.com/blog/rockwell-plc-lifecycle-migration-guide- Workforce Development and Education: https://www.joltek.com/services/service-details-workforce-development-education The phrase I want to retire is "use the right tool for the job." It sounds like judgement and it is an evasion, because most IEC 61131-3 languages can accomplish ninety percent of what a control system needs. The same interlock builds in ladder, in structured text, or in a function block diagram, and all three run. That is exactly why the phrase settles nothing. Ladder still dominates discrete control for a historical reason that has not gone away. It mirrors the electrical schematics machines were already built from, and many of those schematics have not changed. A technician tracing a fault at two in the morning holds the print in one hand and the rung on screen in the other. That correspondence is worth more than elegance. Where continuous process is involved, function block diagrams win for the same reason: a P&ID reads as flow and so does a function block diagram. Structured text earns its place in data handling, recipe management, and anything algorithmic. It also dominates on CODESYS, and this is the part most people miss. It is not objectively better there. The documentation, the community answers and the examples all lean that way, so you get unstuck faster. Platform documentation quality decides language choice more often than anyone admits, which is why a Rockwell Automation shop and a Siemens shop reach different defaults without either being wrong. The question nobody asks is the one that matters: what happens to this program after you leave? A control system outlives the engineer who wrote it. If the next person needs a steeper learning curve to change one setpoint, you optimised for the wrong thing. Four more questions in this one. A spinning yarn machine conversion running Siemens ET 200SP alongside Odot remote I/O came back commissioned, one hundred and sixty eight stations of it, which raises a real point about wire tray sizing and heat in a dusty environment. A drive photographed with water under its bus bars leads into what sanitation does to enclosures in food and beverage. And a customer who demanded 0.75 millimetres squared on every input got a bulky panel, plus a fair question about whether that argument was worth having. Then the one that deserves a straight answer. A controls engineer laid off after four years, told the plant's control team cost too much, asks how to avoid being first on the list. Controls is badly understood by the people who approve budgets, and engineers here are poor at communicating the value they create. The average controls engineer earns $119,682, up 4.3 percent year over year, while 38 percent of manufacturers name the skilled worker shortage as a top business threat. Both are true at once, so the problem is visibility, not demand. The episode closes on hiring. A small integrator cannot find juniors who can explain what DHCP does. The degree has never been the signal. Extracurriculars are, and so is showing up on time. Timestamps0:00 Intro1:00 Siemens ET 200SP and Odot remote I/O: a yarn machine conversion update3:30 Panel review: I/O density, wire tray sizing, and heat6:00 Why run two flavors of I/O in one panel7:10 Water inside a VFD: what washdown really does to enclosures11:10 Structured text vs ladder logic: where ladder actually came from13:40 Why "the right tool for the job" is the wrong framing16:00 Platform documentation decides the language more than preference does17:10 A customer demanded 18 AWG on every input: is the customer always right21:20 Laid off after four years, and how not to be first on the list28:40 A strange mix of skills, and which layers command a premium31:40 Hiring junior engineers: what a degree does not tell you33:40 The DHCP interview question, and better questions to ask instead40:00 Lateness, moonlighting, and the habits that end a junior career48:20 Wrap up Connect:LinkedIn: https://www.linkedin.com/in/vladromanovJoltek: https://www.joltek.comSolisPLC: https://www.solisplc.com

  3. Aug 31

    Ep. 16 | PLC Programming Job With Zero Experience: Stay or Go Back to School? [Honest Answer]

    Three weeks into a new PLC programming job with zero PLC experience, no training and nobody nearby to ask. That question drives this episode, along with four more from the plant floor. Subscribe for weekly industrial automation and manufacturing discussions. Learn more at Joltek:- Unmanaged Switches and Cybersecurity: https://www.joltek.com/blog/industrial-unmanaged-switches-cybersecurity- PLC Lifecycle and Migration: https://www.joltek.com/blog/rockwell-plc-lifecycle-migration-guide- Industrial Ethernet Reliability: https://www.joltek.com/blog/industrial-ethernet-reliability The career question is the one worth sitting with. A computer science graduate takes a PLC programmer role, is promised training, gets one day of introduction, then is left alone while the rest of the team sits in another country. Three weeks in, they are asking whether an associate degree in industrial maintenance would have been smarter. My answer is no, and it is not close. Nobody hired that person believing they had ten years of ladder logic behind them. What is missing is not a degree, it is a request. Find the program, price it, say how long it takes and what it lets you do that you cannot do today, and hand your manager a decision that is easy to approve. I went through this at Procter and Gamble. By the time the company sent me to official Rockwell Automation training I knew more than the course covered, because I had been learning RSLogix 500 and Studio 5000 on live projects. The average controls engineer now earns $119,682, up 4.3 percent year over year, and 38 percent of manufacturers name the skilled worker shortage as a top business threat. Leverage sits with the person willing to learn on the job. The episode opens with a first control panel built by someone four years into filling and capping machines. The layout is good: breakers top left, a 24 volt supply feeding the switch and the controller, wire duct run so the wiring lands clean. Two things stand out. The controller is a Siemens SIMATIC S7-200 Smart, which is obsolete, so the toolchain question is real before a single rung gets written. A current S7-1200 G2 in TIA Portal is a better place to spend learning hours. The five port switch also looks unmanaged, fine on a bench and a problem once that habit reaches a production network. On why there are so few good PLC tutorials on YouTube, coverage is genuinely thin outside Rockwell Automation and Siemens, and it is not gatekeeping. It is cost. A used PLC or HMI runs a few hundred dollars. A bench that can demonstrate coordinated servo work on Kinetix, Sercos or Siemens drives runs into tens of thousands of dollars and past $100,000. The industry also moves slowly, so a ten year old RSLogix tutorial is still accurate. The technical highlight is a CANopen motion problem on a Schneider Electric Lexium LXM32 drive. The JOG_LXM32 block will not accept a velocity change while running. MC_MoveVelocity latches velocity only on the rising edge of execute. MC_JOG does accept a live change, but on restart the drive intermittently receives the velocity from the previous move, and synchronous PDO transmission did not fix it. The shipped workaround keeps rewriting the velocity variable with slightly different values so every scan forces a fresh write. Ugly, effective, and the customer accepted it. On the Rockwell side I have solved the same problem by leaving commanded velocity alone and dynamically changing the gear ratio to a virtual axis. Last is a PanelView 7 Plus that tests clean in FactoryTalk View Studio ME, then loses tags and throws communication errors once downloaded. The poster reports a controller firmware update fixed it. I doubt that is the mechanism. A PanelView 7 Plus talks to controllers as old as a PLC-5. Flashing the controller almost certainly invalidated the shortcut in RSLinx Enterprise, and rebuilding that path is what restored communication. When an HMI works on the desk and fails on the panel, start at the path, not the code. Timestamps0:00 Intro0:20 First control panel build: any advice?1:45 The S7-200 Smart is obsolete4:25 Lost three weeks into a new PLC programming job8:15 Why going back to school is the wrong move8:50 How to ask your manager for training and get a yes10:20 Is there a lack of PLC tutorials on YouTube?14:45 The worst motion control workaround I have seen15:45 MC_JOG, JOG_LXM32 and the velocity that will not change18:50 Dynamic gearing as the Rockwell alternative20:45 PanelView 7 Plus download and communication errors23:20 Why the RSLinx Enterprise path is the real suspect25:00 Wrap up Connect:LinkedIn: https://www.linkedin.com/in/vladromanovJoltek: https://www.joltek.comSolisPLC: https://www.solisplc.com

  4. Aug 28

    Ep. 15 | AI in Industrial Automation: Where It Actually Works and Where It Fails on the Plant Floor

    AI in industrial automation is producing real productivity gains and real risk at the same time. This is an honest account of where it helps and where it will confidently hand your team a wrong answer. Subscribe for industrial automation and manufacturing perspective from active project work. Learn more at Joltek:- Edge Computing, AI and Manufacturing Data: https://www.joltek.com/blog/edge-computing-ai-value-manufacturing-data- Root Causes of Downtime in Industrial Automation: https://www.joltek.com/blog/root-causes-downtime-industrial-automation- Workforce Development and Education: https://www.joltek.com/services/service-details-workforce-development-education- Operations and Performance Improvement: https://www.joltek.com/services/service-details-operations-performance-improvement Start with the economics, because it is the first question a manager asks. A basic subscription runs $20 per month and runs out of capacity within a few hours a day under heavy use. The higher tier is $200 per month. Against a loaded engineering rate that is not a meaningful line item. The real cost is the learning curve, paid up front by the people least able to spare the time. Anyone expecting a gain in week one will stop before getting one. Where the gains are genuine. Problem definition comes first and is underrated. A systems architect is usually handed a vague requirement already attached to a proposed solution. Putting that in front of a model and asking where the approach fails produces counterpoints worth raising before anybody commits. Second, carrying context across platforms. Experience spread over Rockwell Automation, Siemens, Omron, Mitsubishi Electric, Phoenix Contact PLCnext and Opto 22 cannot be held in working memory, and returning to one after months away is where scaffolding a known function saves hours. Third, and this is the strongest case, reading code somebody else wrote. A conveyor that will not start, logic written by a firm nobody can reach, is a normal Tuesday. Screenshotting routines into a model and describing the symptom narrows the search dramatically. Equipment arriving with German or Italian rung comments used to cost a day and now costs an hour. Now the failures, because these determine what you permit. Ask for a whole application in one prompt and you get something unusable. The palletizer example makes the point: infeed handling, staging and orientation, end of arm tooling, and recipe management are separate problems, and the architect decomposes them before prompting. The tool does not do that for you, and it is precisely the skill your senior people have and your junior people do not. Part number families are where confident wrong answers live. Give it a PowerFlex fault code without naming the exact drive family and it answers for a different one, with no hedging. Firmware revisions compound it, as do instruction sets deprecated years ago that it will still recommend. Structured text is handled noticeably better than ladder logic, which follows from how little advanced ladder material exists publicly. The organizational conclusion. These tools accelerate a competent engineer and do not replace judgment. On live equipment the person at the keyboard is the last line of defence, because a wrong rung is not a bad draft, it is a hazard to equipment and to people. With 94 percent of executives acknowledging the manufacturing skills gap, and 59 percent of frontline skilled workers over 55 planning to retire within five years according to a 2024 Schneider Electric survey, the pressure to make less experienced engineers productive faster is not going away. These tools help with that, and they also make it easier for someone without the experience to produce confident nonsense. Your review standards have to account for both. Timestamps0:00 What this video is and is not1:10 Which model, and why software engineers converge on one2:10 Two workflows: a desktop context store and the phone in the field4:20 What the subscription actually costs5:20 Where it helps first: defining a vague problem9:00 The palletizer example: decompose before you prompt11:50 A real request: an hourly productivity screen12:50 Carrying context across Rockwell, Siemens, Omron and Opto 2215:10 Where it breaks: less common platforms and firmware revisions17:15 Why structured text works better than ladder logic18:40 Troubleshooting: turning a vague complaint into a direction22:40 The PowerFlex problem: fault codes differ across drive families24:40 Reading code you have never seen, in a language you do not speak27:00 Why you are still the last line of defence28:30 The learning curve nobody wants to pay Connect:LinkedIn: https://www.linkedin.com/in/vladromanovJoltek: https://www.joltek.comSolisPLC: https://www.solisplc.com

  5. Aug 25

    Ep. 14 | PLC Brand Debate: Rockwell, Siemens, Schneider, or Something Cheaper? [Honest Answer]

    Choosing a PLC brand for a new plant has two very different answers depending on whether you own the factory or you are advising someone who does. This episode gives both, plus four more questions from the plant floor. Subscribe for weekly industrial automation and manufacturing discussions. Learn more at Joltek:- Connecting an Allen-Bradley PLC to Ignition: https://www.joltek.com/blog/connecting-allen-bradley-plc-ignition- Rockwell PLC Lifecycle and Migration Guide: https://www.joltek.com/blog/rockwell-plc-lifecycle-migration-guide- Edge Devices, PLCs, IPCs and Plant Architectures: https://www.joltek.com/blog/manufacturing-concepts-edge-devices-plcs-ipcs-industrial-automation-software-hardware-architectures- Root Causes of Downtime in Industrial Automation: https://www.joltek.com/blog/root-causes-downtime-industrial-automation The controller brand question is the one most people get backwards. The instinct is to compare spec sheets and price per point, and that is almost never what determines whether a platform works out over ten years. What actually matters is who supports it in your region, whether a local integrator has already deployed it, whether your existing people already know it, and how fast you can get a human on the phone when a line is down. For a small plant you own outright, that logic points somewhere unexpected. CODESYS as the development environment, because it is inexpensive, approachable, and hardware agnostic. Ignition from Inductive Automation as the SCADA layer, because it connects to a broad spectrum of devices and web deployment is cheap. Hardware agnosticism is not a philosophical position here. It is a supply chain hedge, and anyone who lived through recent lead time chaos understands why. The hardware vendor then gets chosen on local distributor and integrator support rather than on the datasheet, with WAGO, Opto 22, and PLCnext all viable underneath. For a manufacturer with multiple sites and a C suite making the call, the answer swings hard toward Rockwell Automation, Siemens, and Schneider Electric, for reasons that have very little to do with the controllers themselves. What is already installed, what the engineering staff already know, and the industry norm all outweigh the technical comparison. Pharmaceutical plants lean heavily on DeltaV. That is not an accident and it is not a spec sheet decision. This episode also takes on the question that gets the strongest reaction from working practitioners. Why does every PLC and SCADA job posting sit under a maintenance or electrician title? The argument here is that producing ladder logic which runs a machine is the easy part, and AI has made it easier still. The hard part is building a system that is reliable, maintainable, expandable, and connectable. Program scope tags leaking into global scope, messages passed between areas, rungs nobody documented: that is what a plant inherits when the skill is treated as a commodity, and the technical debt lands years later on somebody else. Also covered: whether you can power an Allen-Bradley Point I/O over PoE with a 90 watt splitter set to 24 volts, and why the Opto 22 groov RIO already solves that natively. Whether a trade school PLC track beats the electrician route, and why XIC, XIO, OTE, addressing, and scan cycle behaviour matter more than jumping ahead to motion and safety. Whether a two year controls associate degree is worth it with five years already in the field. And HMI design: why native graphics outperform imported assets, and how to apply ISA 101 selectively on standalone machines. Timestamps0:00 On site commissioning across Rockwell, Omron, and Ignition0:50 Can you power a Point I/O over PoE?5:10 Why running 24 volts is usually the simpler answer7:00 The Opto 22 groov RIO as native PoE I/O8:20 Trade school PLC courses vs the electrician route11:50 Master the fundamentals before sequencers and motion14:25 Pick the employer and the mentor, not the title15:00 Why PLC programming gets classed as a maintenance skill17:10 Reliable, maintainable, expandable: the real difficulty19:40 The technical debt a plant takes on21:20 If you had to build a factory tomorrow24:45 Ignition and CODESYS for a small plant you own26:00 Choosing hardware on local support, not spec sheets28:40 What changes when you advise a C suite31:30 Is a two year controls associate degree worth it?35:00 What iOS app design taught me about HMI design37:20 Native HMI graphics vs importing from other software39:50 ISA 101 on standalone machines: adopt it selectively Connect:LinkedIn: https://www.linkedin.com/in/vladromanovJoltek: https://www.joltek.comSolisPLC: https://www.solisplc.com

  6. Aug 8

    Ep. 13 | Ladder Logic vs C++: Why PLC Programmers Still Choose Ladder and Why They Are Right & P&G Stories

    Ladder logic is not a legacy habit. It is the right visual representation for the Boolean, state based logic that actually runs machines, and this week explains why that matters at 3 AM with a line down. Subscribe for weekly plant floor questions answered in full. Learn more at Joltek:PLC Scan Cycles, Polling and SCADA Data: https://www.joltek.com/blog/plc-scan-cycles-polling-scada-systems-dataRockwell PLC Lifecycle Migration Guide: https://www.joltek.com/blog/rockwell-plc-lifecycle-migration-guide The anchor question came from a computer science background: why do PLC programmers use ladder? The usual answer is cynical. Technicians cannot read C++, so write ladder or spend your nights driving to the plant. That is not the real reason, and I have met technicians who program better than most engineers. The real reason is what control logic actually is. IEC 61131-3 defines five languages for programmable controllers, and ladder is one of them because base machine control is overwhelmingly Boolean and state driven. A single valve permissive in a regulated plant can carry ten conditions gated through AND, OR and NAND relationships, and that reads far faster as rungs than as nested if and else if statements. Ladder came out of relay logic and reads like an electrical schematic, which is the document the people troubleshooting that machine were already trained on. Performance is not the argument people think it is. Ladder, structured text and C++ all end up as machine instructions on a controller, and if you need a for loop or reusable code, ladder gives you both through Add On Instructions and function blocks. The choice was never about capability. It is about which representation survives contact with the person diagnosing a fault two years from now, at night, with production stopped. MES layers, data applications and historian integrations belong in C++, Python or Rust. Base control does not. The other long segment answers someone one month into their first controls role who feels like they know nothing. I started at Procter and Gamble in April 2014 at a site in Maine, and my first week was commissioning a Schubert case packer shipped from Germany. It was the only significant Siemens asset on a floor otherwise running ControlLogix, so an S7-1500 machine had to exchange handshakes with the line, join the safety system, and get added to DeviceNet and ControlNet. The work was verifying voltages and grounding faults, powering up only after those checks passed, dry running motors, then validating component by component until product moved through. It was overwhelming and that was the point. The lesson that took me too long: use the OEM, the machine builder, the integrator and the vendor support contract you already pay for. Three real builds get reviewed. A commissioning panel running a Siemens S7-1500 with Danfoss FC 302 and IC7 drives daisy chained off a switch. A home test rig combining an S7-1500, an ET 200SP remote I/O drop, a Schneider Electric controller and a WAGO Compact Controller 100, with a Pilz safety relay sitting unwired. And a first design build: a pump station on an AutomationDirect CLICK controller, which runs about $120, driving three phase pumps through contactors. The wiring is good. The screen is where the work is. Start and stop are the most used controls on that station and the smallest targets on the display, while navigation buttons are large, and colour is doing work that labels should be doing. The episode closes on Allen-Bradley history: PLC-2 racks, a PLC-5 and CRT programming terminals shown at Vintage Computer Festival West. PLC-5 and SLC families still run production today, and their programming software goes end of life alongside the hardware. I am also building an Opto 22 groov RIO demo for the Ignition Community Conference in Sacramento in late September. Timestamps0:00 Ignition Community Conference and the Opto 22 groov RIO build1:20 A Siemens S7-1500 and Danfoss FC 302 commissioning panel5:25 First month as a control engineer and knowing nothing6:10 Procter and Gamble, 2014, and a Schubert case packer9:00 Commissioning sequence: voltages, grounding, dry run12:25 Vendor support, OEMs and integrators as real resources13:40 A home test rig with Siemens, Schneider Electric and WAGO17:45 Why PLC programmers use ladder logic instead of C++20:15 Boolean logic and state conditions, the real answer26:20 An AutomationDirect CLICK pump station reviewed30:30 HMI critique: button sizing, colour and label hierarchy33:35 Allen-Bradley PLC-2, PLC-5 and CRT programming terminals More from Joltek: https://www.joltek.comBook a modernization consultation: https://www.joltek.com/book-a-modernization-consultation

  7. Aug 3

    Ep. 12 | PLC Panel Builds Reviewed Plus the Exact Learning Path I Would Follow Today [Full Q&A 2026]

    PLC panel photos tell you almost everything about the person who built or dismantled them. This week reviews five real ones from the community, plus the honest answer to what a beginner should actually learn first. Subscribe for weekly plant floor questions answered in full. Learn more at Joltek:Control System Modernization Strategy: https://www.joltek.com/blog/control-system-modernization-strategyRockwell PLC Lifecycle Migration Guide: https://www.joltek.com/blog/rockwell-plc-lifecycle-migration-guideConnecting an Allen-Bradley PLC to Ignition: https://www.joltek.com/blog/connecting-allen-bradley-plc-ignition The best panel this week is a large enterprise Rockwell build: a ControlLogix rack with a second fixed chassis alongside it, digital and analog I/O broken out to the standard field terminals, a PanelView on the door that looks like a 7 Performance, and clean labeling throughout. Two notes on it. There is room in that enclosure to have scooted the chassis over and bought identical racks rather than mixing sizes. And there is no switch visible, which is unusual at that scale, though it works if the single controller runs one port to the remote rack over EtherNet/IP and the other to the plant network. No cooling either, which is defensible with no VFDs in the cabinet but is not what I would normally expect. The worst panel is the one that makes the point. Someone acquired a cabinet holding ten Festo servo drives with a Weidmuller ProTop supply feeding 24 volts at 40 amps, and every motor and feedback cable has been cut off at the drive. Those terminal blocks release with a small screwdriver into the blue notch. It takes seconds. Instead the whole harness was severed, so whoever bought that equipment now has to strip and re-terminate every conductor before anything runs. It is recoverable and it was unnecessary, and it tells you what kind of shop handled the teardown. If you are buying used industrial hardware, look at how it came out of the building. A first PLC project also came in: an AutomationDirect Productivity controller driving Finder relays for a low voltage house lighting retrofit, on a WAGO supply at 5 amps. It works. The main change would be a much shorter DIN rail, because everything on there fits in about a foot and the long runs to the relays make the wiring harder to read than it needs to be. If you want to push it further, Home Assistant running in Docker alongside the PLC gets you phone and browser control without touching the logic. Then a piece of history. Someone picked up the portable Allen-Bradley PLC-5 demonstration trainers, the units people were trained on, and they power up and boot clean. The parallel port is still on the side. The genuine problem underneath the nostalgia is software: when an OEM discontinues hardware they usually pull the ability to buy the programming software with it, and plenty of plants still run PLC-5 and SLC families today. The people maintaining those lines need RSLogix 5 and cannot simply purchase it. Distributors can sometimes route you to a license, but it is harder than it should be. The last question is the most useful one. Someone learning on a borrowed board with a CompactLogix L38ERM and a Micro850, using Connected Components Workbench and Studio 5000, asked what to focus on without disappearing down rabbit holes. Focus on Studio 5000, because it is the platform of choice across large enterprise while the Micro850 family has a much smaller install base. Learn ladder logic first, especially in North America. Then FactoryTalk View ME, which lets you build screens and simulate buttons and sensors against the controller from your laptop with no physical HMI. After that, Ignition, which is free to learn through Inductive University and runs on a laptop, and which pulls you naturally into Ethernet communication, MQTT and OPC UA. That progression is PLC, then HMI, then SCADA and data, and it is the order that actually builds on itself. Timestamps0:00 The S7-1500 display meme explained2:20 A large enterprise ControlLogix panel reviewed4:10 The PanelView, the missing switch, and no cooling6:20 A gutted Festo servo drive cabinet8:00 How those drive terminals should have come apart9:40 Why cut cables tell you who did the teardown10:50 A first PLC project: house lighting on a Productivity controller13:20 DIN rail length, and Home Assistant as the next step14:10 PLC-5 trainer units and the software problem underneath18:10 What should a beginner actually learn first19:20 Reading the board: CompactLogix L38ERM and Micro85021:10 Studio 5000 over CCW, and why21:50 Ladder logic, FactoryTalk View ME, then Ignition More from Joltek: https://www.joltek.comBook a modernization consultation: https://www.joltek.com/book-a-modernization-consultation

  8. Jul 29

    Ep. 11 | This Messy Control Panel Is One Fault Away From a Full Line Stop [Real Plant Panel Review]

    A messy control panel tells you almost everything about how a machine has been maintained. This episode reads five real plant photos and calls out what actually matters. The first submission is a panel worked on for years under time pressure, and every symptom of that is visible. I cover what I would flag first, why panels end up this way, and how to decide whether it gets retrofitted or runs until the machine retires. Subscribe for weekly plant floor questions answered in full. Learn more at Joltek:Control System Modernization Strategy: https://www.joltek.com/blog/control-system-modernization-strategyIndustrial Unmanaged Switches and Cybersecurity: https://www.joltek.com/blog/industrial-unmanaged-switches-cybersecurityPlant Floor OT Networking: https://www.joltek.com/blog/plant-floor-ot-networking Start with the panel. The disconnects and breakers up top are fine. What is not fine is labeling that tells you nothing, relays clearly added after the build because the label style does not match the original work, a safety relay lying loose on the panel floor, and a conductor terminated into nothing. There is a Delta VFD, a Panasonic PLC close to a MicroLogix in form factor, a Rockwell Automation power supply, Finder relays, and an unmanaged Stratix 2000 switch hanging off the enclosure instead of mounted. Once that door shuts, all of it shares the heat. Two things put panels here. Techs get squeezed on time, so the work gets done but the panel never gets put back. And a machine that faults often gets opened often, so covers come off and marginal labels stop meaning anything. The switch on the side is a third cause. That panel was built with no spare DIN rail, so when the plant wanted the asset on the network there was nowhere to put it. The real cost is mean time to repair. Somebody with ten years on that machine can still work on it, nobody else can, and the as built schematics are not current. That is the number to put in front of a plant manager, not the aesthetics. On the retrofit call, confirm whether the Delta VFD and Panasonic PLC are still sold, price a rebuild that includes current as built drawings, and weigh that against how long the machine stays in service. If it comes out in two years, running it out is defensible. If it runs another decade, every year you wait makes the downtime worse. The Siemens submission is the most useful lesson here. A fifteen year old S7-1500 will not talk to a new ET 200SP, two days are gone, and the post still does not contain enough for anyone to help. Nobody knows the CPU article number, its firmware, the firmware on the interface module, or what changing the firmware versions meant. Siemens support and any integrator will ask for that first. Then work by elimination. Connect to the CPU alone and confirm it is healthy. Add only the PROFINET interface module with no I/O behind it. Then add I/O one module at a time. Older CPUs cannot always be flashed to current firmware, which is why revisions matter across a gap this wide. The last question is closest to the work I do. A controls engineer of fifteen years watched their plant go from air gapped, to an OPC UA server pushing data out, to permanently internet connected, and the parent company moved in after the site IT person retired. The skilled worker shortage was named by 38% of manufacturers as a top business threat in 2025, and this is what it looks like on the ground. The root cause of IT led OT failures is a KPI mismatch, not incompetence. IT is measured on patch compliance. Operations is measured on whether the line ran. Those collide the first time a server hosting FactoryTalk View SE, Ignition, or Optix reboots during production. Ask what is being deployed and what the production impact is. Be in the room for anything touching a running line. Vet who they bring in. Learn IEC 62443 and the Purdue model by name so you share vocabulary with corporate IT. Timestamps0:00 Messy Control Panel Teardown Begins2:40 Why Panels End Up In This State3:40 No Room To Expand And A Switch On The Side5:32 Obsolete Delta VFD And Panasonic PLC6:10 Retrofit The Panel Or Run It Out6:36 SLC 500 And A Trolley For A Desk9:16 S7-1500 Will Not See The ET 200SP10:16 How To Ask For Help Properly12:26 Process Of Elimination On PROFINET16:56 Festo Trainer And The Siemens LOGO20:00 Corporate IT Is Taking Over OT25:56 Three Things To Do Right Now More from Joltek: https://www.joltek.comBook a modernization consultation: https://www.joltek.com/book-a-modernization-consultation

See All (18)

About

Factory Field Notes is a practical podcast for manufacturing leaders, engineers, and technical managers who want real lessons from the plant floor. Hosted by Vladimir Romanov, the show breaks down automation, controls, SCADA, MES, OT networks, industrial data, downtime, reliability, project execution, and the messy work of modernizing factories without vendor fluff or empty transformation talk.

Information

  • Creator
    Vladimir Romanov
  • Years Active
    2026
  • Episodes
    18
  • Rating
    Clean
  • Copyright
    © 2026 Vladimir Romanov
  • Show Website
    Factory Field Notes