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.

Timestamps
0:00 The plant with a NAT device in every machine
3:10 What network address translation actually is
4:10 Why machine builders hand you an addressing problem
6:40 Option one: readdress every device in the panel
9:00 What readdressing really costs in licences and hours
10:00 The warranty exposure nobody budgets for
10:40 Which devices actually belong on the plant network
12:22 Option two: how NAT sits between the panel and the plant
14:30 The laptop problem: plant side versus equipment side
16:45 When an IT provisioned laptop cannot reach the drive
17:25 The temporary translation entry workaround
18:30 What NAT costs to buy and to keep running
20:50 How to make the call

More from Joltek:
Website: https://www.joltek.com
Book a modernization consultation: https://www.joltek.com/book-a-modernization-consultation

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.

Timestamps
0:00 Intro
1:00 Siemens ET 200SP and Odot remote I/O: a yarn machine conversion update
3:30 Panel review: I/O density, wire tray sizing, and heat
6:00 Why run two flavors of I/O in one panel
7:10 Water inside a VFD: what washdown really does to enclosures
11:10 Structured text vs ladder logic: where ladder actually came from
13:40 Why "the right tool for the job" is the wrong framing
16:00 Platform documentation decides the language more than preference does
17:10 A customer demanded 18 AWG on every input: is the customer always right
21:20 Laid off after four years, and how not to be first on the list
28:40 A strange mix of skills, and which layers command a premium
31:40 Hiring junior engineers: what a degree does not tell you
33:40 The DHCP interview question, and better questions to ask instead
40:00 Lateness, moonlighting, and the habits that end a junior career
48:20 Wrap up

Connect:
LinkedIn: https://www.linkedin.com/in/vladromanov
Joltek: https://www.joltek.com
SolisPLC: https://www.solisplc.com

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.

Timestamps
0:00 Intro
0:20 First control panel build: any advice?
1:45 The S7-200 Smart is obsolete
4:25 Lost three weeks into a new PLC programming job
8:15 Why going back to school is the wrong move
8:50 How to ask your manager for training and get a yes
10:20 Is there a lack of PLC tutorials on YouTube?
14:45 The worst motion control workaround I have seen
15:45 MC_JOG, JOG_LXM32 and the velocity that will not change
18:50 Dynamic gearing as the Rockwell alternative
20:45 PanelView 7 Plus download and communication errors
23:20 Why the RSLinx Enterprise path is the real suspect
25:00 Wrap up

Connect:
LinkedIn: https://www.linkedin.com/in/vladromanov
Joltek: https://www.joltek.com
SolisPLC: https://www.solisplc.com

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.

Timestamps
0:00 What this video is and is not
1:10 Which model, and why software engineers converge on one
2:10 Two workflows: a desktop context store and the phone in the field
4:20 What the subscription actually costs
5:20 Where it helps first: defining a vague problem
9:00 The palletizer example: decompose before you prompt
11:50 A real request: an hourly productivity screen
12:50 Carrying context across Rockwell, Siemens, Omron and Opto 22
15:10 Where it breaks: less common platforms and firmware revisions
17:15 Why structured text works better than ladder logic
18:40 Troubleshooting: turning a vague complaint into a direction
22:40 The PowerFlex problem: fault codes differ across drive families
24:40 Reading code you have never seen, in a language you do not speak
27:00 Why you are still the last line of defence
28:30 The learning curve nobody wants to pay

Connect:
LinkedIn: https://www.linkedin.com/in/vladromanov
Joltek: https://www.joltek.com
SolisPLC: https://www.solisplc.com

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.

Timestamps
0:00 On site commissioning across Rockwell, Omron, and Ignition
0:50 Can you power a Point I/O over PoE?
5:10 Why running 24 volts is usually the simpler answer
7:00 The Opto 22 groov RIO as native PoE I/O
8:20 Trade school PLC courses vs the electrician route
11:50 Master the fundamentals before sequencers and motion
14:25 Pick the employer and the mentor, not the title
15:00 Why PLC programming gets classed as a maintenance skill
17:10 Reliable, maintainable, expandable: the real difficulty
19:40 The technical debt a plant takes on
21:20 If you had to build a factory tomorrow
24:45 Ignition and CODESYS for a small plant you own
26:00 Choosing hardware on local support, not spec sheets
28:40 What changes when you advise a C suite
31:30 Is a two year controls associate degree worth it?
35:00 What iOS app design taught me about HMI design
37:20 Native HMI graphics vs importing from other software
39:50 ISA 101 on standalone machines: adopt it selectively

Connect:
LinkedIn: https://www.linkedin.com/in/vladromanov
Joltek: https://www.joltek.com
SolisPLC: https://www.solisplc.com

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-data
Rockwell 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.

Timestamps
0:00 Ignition Community Conference and the Opto 22 groov RIO build
1:20 A Siemens S7-1500 and Danfoss FC 302 commissioning panel
5:25 First month as a control engineer and knowing nothing
6:10 Procter and Gamble, 2014, and a Schubert case packer
9:00 Commissioning sequence: voltages, grounding, dry run
12:25 Vendor support, OEMs and integrators as real resources
13:40 A home test rig with Siemens, Schneider Electric and WAGO
17:45 Why PLC programmers use ladder logic instead of C++
20:15 Boolean logic and state conditions, the real answer
26:20 An AutomationDirect CLICK pump station reviewed
30:30 HMI critique: button sizing, colour and label hierarchy
33:35 Allen-Bradley PLC-2, PLC-5 and CRT programming terminals

More from Joltek: https://www.joltek.com
Book a modernization consultation: https://www.joltek.com/book-a-modernization-consultation

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-strategy
Rockwell PLC Lifecycle Migration Guide: https://www.joltek.com/blog/rockwell-plc-lifecycle-migration-guide
Connecting 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.

Timestamps
0:00 The S7-1500 display meme explained
2:20 A large enterprise ControlLogix panel reviewed
4:10 The PanelView, the missing switch, and no cooling
6:20 A gutted Festo servo drive cabinet
8:00 How those drive terminals should have come apart
9:40 Why cut cables tell you who did the teardown
10:50 A first PLC project: house lighting on a Productivity controller
13:20 DIN rail length, and Home Assistant as the next step
14:10 PLC-5 trainer units and the software problem underneath
18:10 What should a beginner actually learn first
19:20 Reading the board: CompactLogix L38ERM and Micro850
21:10 Studio 5000 over CCW, and why
21:50 Ladder logic, FactoryTalk View ME, then Ignition

More from Joltek: https://www.joltek.com
Book a modernization consultation: https://www.joltek.com/book-a-modernization-consultation

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-strategy
Industrial Unmanaged Switches and Cybersecurity: https://www.joltek.com/blog/industrial-unmanaged-switches-cybersecurity
Plant 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.

Timestamps
0:00 Messy Control Panel Teardown Begins
2:40 Why Panels End Up In This State
3:40 No Room To Expand And A Switch On The Side
5:32 Obsolete Delta VFD And Panasonic PLC
6:10 Retrofit The Panel Or Run It Out
6:36 SLC 500 And A Trolley For A Desk
9:16 S7-1500 Will Not See The ET 200SP
10:16 How To Ask For Help Properly
12:26 Process Of Elimination On PROFINET
16:56 Festo Trainer And The Siemens LOGO
20:00 Corporate IT Is Taking Over OT
25:56 Three Things To Do Right Now

More from Joltek: https://www.joltek.com
Book a modernization consultation: https://www.joltek.com/book-a-modernization-consultation

Most PLCs do not connect wirelessly out of the box, so field teams reach for an inexpensive travel router to close the gap. Subscribe for more field grounded guidance on OT networking, commissioning, and industrial modernization from Joltek.

Learn more at Joltek:
- OT Networking Fundamentals: https://www.joltek.com/education/ot-networking-fundamentals
- IT and OT Architecture Integration: https://www.joltek.com/services/service-details-it-ot-architecture-integration
- Industrial Cybersecurity for ICS: https://www.joltek.com/blog/industrial-cybersecurity-ics

An Allen-Bradley CompactLogix 5069, a Siemens S7-1200 G2, a Siemens S7-1500, and an AutomationDirect Productivity PLC all share one limitation. They give you Ethernet and USB, and nothing more, and the same is true across most field hardware, including Phoenix Contact and Opto 22. When the electrical panel sits far from remote I/O, which is common in oil and gas, food and beverage, and chemical plants, that wired constraint becomes a productivity problem, because the panel may be a long walk or a tall climb from where you need to stand.

Vladimir Romanov, founder of Joltek and SolisPLC, frames this from experience. Sent to commission equipment at a peanut butter plant, he lost the electrician promised to help run the FAT, who was pulled to operations mid checkout. The panel was not on the plant network yet, and IT had not assigned IP addresses. To keep making progress on the I/O, some of it on 40 foot tanks reached by a vertical ladder, he had to carry the laptop up while holding the connection to the PLC. That is when a small wireless bridge stops being a convenience and starts protecting the commissioning schedule.

The tool shown is a TP-Link Nano WR802N, bought for about $30 roughly eight years ago and now discontinued. A current equivalent runs closer to $50 or $60, while enterprise wireless hardware climbs into the hundreds and thousands of dollars. For field work the cheap unit is often the smart pick. It packs easily for air travel and is easy to replace when a harsh environment destroys it. The honest constraints are size, price, and range. Distance, multiple users, and speed are where a larger radio earns its cost, which is why the video also configures a TP-Link AC1200 Wi-Fi router with external antennas for longer reach.

The demonstration is deliberately complete. It covers a factory reset with a SIM pin, wiring the router to the CompactLogix at 192.168.0.231, and configuring the unit in access point mode. It changes the default admin and admin credentials, because an open wireless node on an OT network is an exposure, not a footnote. It confirms DHCP, pings the PLC, and sets up Ethernet and IP drivers in RSLinx Classic, both by entering a specific IP and by browsing a remote subnet, then uploads the program in Studio 5000. One clarification helps in the field: older RSLogix 5000 relied on RSLinx Classic, while newer Studio 5000 uses FactoryTalk Linx.

For managers, the point is not only that this works. Field wireless is a genuine commissioning productivity fix, but it is also an OT remote access decision with a security dimension, and standards such as IEC 62443 shape that posture. That is why the video closes on the disciplined alternative. A cheap mini PC jump box with a 512 GB SSD and 16 GB of RAM sits physically wired to the PLC and is reached over Remote Desktop, so the session survives even if the wireless link drops while a user runs Studio 5000, RSLogix 5000, TIA Portal, or CODESYS. The proper long term answer is real OT and IT architecture with servers, jump boxes, and IT supported remote access, which is the work Joltek helps manufacturers plan and build.

Timestamps
0:00 Intro
1:05 Why PLCs Do Not Connect Wirelessly
3:00 The Travel Router Approach with the TP-Link Nano
4:05 Why You Need It: Commissioning With No Network
5:15 A Peanut Butter Plant FAT Story
8:05 Tradeoffs: Size, Price, and Range
9:55 Demo: Factory Reset and Wiring
12:30 Who Is Joltek
13:05 Configuring the Router as an Access Point
20:00 RSLinx: Drivers and Browsing the Subnet
23:35 A Larger AC1200 Router and Studio 5000 Upload
32:25 The Jump Box and Mini PC Alternative
34:50 Closing

Website: https://www.joltek.com
Book a modernization consultation: https://www.joltek.com/book-a-modernization-consultation
Reach Vladimir Romanov on LinkedIn. Questions are welcome in the comments.

Vladimir Romanov answers six real questions from the field, from a Siemens ET 200SP retrofit to buggy PLC software, HMI design, and hiring for automation roles.

If you lead an automation or engineering team, subscribe to Factory Field Notes for weekly lessons that connect the technical call to the business case.

Learn more at Joltek:

- Control System Modernization Strategy: https://www.joltek.com/blog/control-system-modernization-strategy

- Rockwell PLC Lifecycle and Migration Guide: https://www.joltek.com/blog/rockwell-plc-lifecycle-migration-guide

- When to Use a System Integrator: https://www.joltek.com/blog/system-integrators

- Recruiting and Building Automation Talent: https://www.joltek.com/blog/recruiting-robotics-automation-small-manufacturers

The most valuable thread here is not a piece of hardware. It is the decision a team faces when a machine breaks and everyone wants to fix it in-house. That instinct is understandable, because internal staff already know the process and the payroll is already committed. The mistake is treating that labor as free. Assign people to a retrofit they are not equipped to finish and you spend capital and months on a problem that may need a specialist, and those months rarely show up on a budget line. The honest business case is total cost, not headline rate: how long it takes, whether the skill exists internally, and what the delay costs in downtime. There is a matching lesson for integrators and consultants. It is often easier to let a customer try and fail than to convince them up front, because the same customer who shrugs off a recommendation today will call once the in-house attempt stalls.

The technical questions carry the same subtext. The episode opens with a legacy textile machine converted to Siemens ET 200SP remote I/O, most likely tied back to the controller over PROFINET, with Odot digital I/O modules chosen to save cost. The savings on commodity I/O are usually modest and the integration and support burden can erase them, so that choice belongs in the business case, not left to the panel builder. Obsolescence upgrades like this are where a modernization roadmap pays off.

Two questions land on the workforce problem every plant is living through. An electrician asked how to learn PLCs affordably, and the practical answer is to train on the hardware you actually run: a discontinued Rockwell MicroLogix 1100 with the free RSLogix 500 edition, an AutomationDirect CLICK, or a borrowed trainer of your own platform teaches far more than another photo sensor. This matters to managers because the pipeline is thin. Industry data shows 94% of executives acknowledge the manufacturing skills gap, roughly 2.7 million baby boomers are expected to retire from manufacturing by 2025, and only about 9% of workers aged 19 to 24 are entering the skilled trades. A real training path costs less than the tribal knowledge you lose when a senior technician retires.

Another question asked why programming software from Siemens, Schneider Electric, and Mitsubishi feels slow and buggy next to consumer apps. The answer is structural: these are low-volume engineering tools that carry drivers for USB, Ethernet, RS232, RS485, and Data Highway Plus, compile to several controller architectures at once, and still support hardware from the previous century. That backward compatibility is both a feature you rely on and the source of the friction. On visualization, the guidance is to resist elaborate 3D HMI graphics and follow the ISA 101 standard toward clean, readable screens, then invest the saved time in usability so operators ramp faster and make fewer errors.

The last question came from a data science graduate interviewing for a role that touches PLCs. What a good interviewer screens for is not PLC trivia. It is curiosity, real respect for plant-floor safety, and smart questions about how the company collects and uses its data. If you hire for automation-adjacent roles, interview for judgment and coachability over a checklist of acronyms.

Timestamps

0:00 Intro: This Week's Field Questions

0:18 Siemens ET 200SP and Odot Remote I/O Retrofit

5:45 In-House vs Contractor: When to Fix It Yourself

9:30 Building the Automation Business Case

12:12 About Joltek and Factory Field Notes

12:45 Teaching Yourself PLCs on the Right Hardware

19:10 Why PLC Software Is Buggy and Bloated

22:48 HMI Design: 3D Visuals vs ISA 101

26:32 Impressing in a PLC and Data Interview

Connect with Joltek:

Website: https://www.joltek.com

Book a modernization consultation: https://www.joltek.com/book-a-modernization-consultation

Vladimir Romanov, founder of Joltek, answers each one as someone who has hired, mentored, and built automation teams. If you manage engineers or you are growing your own career, subscribe for breakdowns that connect the technical work to the business decisions behind it.

The lead question is the one most managers are quietly navigating: have PLC programmers become accidental network engineers? The answer is yes, and it is worth understanding why. Over the last decade the field migrated off contained fieldbuses like DeviceNet, ControlNet, and SERCOS onto Ethernet based protocols, EtherNet/IP on the Rockwell side and PROFINET on the Siemens side, with OPC UA carrying data up to other systems. The push to make plants ready for AI only accelerates it, because every AI ambition starts with collecting more plant floor data. The practical result is that your controls people now spend real time on managed switches, IP addressing, VLANs, and duplicate IP troubleshooting, usually alongside the IT department. For a manager, that is a training and hiring signal, not a footnote. Joltek publishes a full OT networking fundamentals course for free, which is a low cost way to close that gap on your team.

The second question is a useful reminder that incoming inspection still matters, even on premium hardware. A practitioner received a Rockwell ControlLogix L915 safety controller, a roughly $20,000 piece of equipment for use with PlantPAx, with a misaligned and improperly seated RJ45 port and missing faceplate markings. It is heading back on an RMA. Lower volume safety processors get produced in smaller runs, which is exactly where a defect can slip through, so it is worth checking expensive hardware before it goes into a chassis.

The third question is a version standardization trap. A new machine arrived with a Siemens S7-1200 G2, and older TIA Portal versions 14 and 17 cannot go online with it. You need version 20, ideally version 21, and the Gen2 I/O is not backward compatible without a PROFINET bridge. The broader lesson for a plant is to standardize your engineering software versions before a mix of V14, V17, V20, and V21 turns every service call into a licensing scramble.

The episode closes with two human questions: whether controls people are genuinely into broader technology, and whether you can get into automation without an engineering degree. On the degree question the honest answer is that it is possible but harder, because large employers often filter by degree, and the no degree path can take far longer than the four year shortcut.

Learn more at Joltek:
- Free OT Networking Fundamentals course: https://www.joltek.com/education/ot-networking-fundamentals
- IT and OT Architecture Integration: https://www.joltek.com/services/service-details-it-ot-architecture-integration
- Modern Plant Network Requirements in Manufacturing: https://www.joltek.com/blog/modern-plant-network-requirements-manufacturing
- Workforce Development and Education: https://www.joltek.com/services/service-details-workforce-development-education

Timestamps
0:00 Intro and How This Q&A Works
1:00 Have PLC Programmers Become Accidental Network Engineers
4:45 Who Is Joltek
5:20 A Defective $20,000 ControlLogix L915 Safety Controller
11:20 Which TIA Portal Version You Need for the S7-1200 G2
15:35 Are Controls Engineers Actually Into Tech
21:25 Getting Into Automation Without an Engineering Degree
28:50 Closing and How to Reach Out

If you are weighing a skills investment, a hire, or a hardware standard, send a note on LinkedIn or leave a comment. Vladimir reads and responds.

Vladimir Romanov, founder of Joltek, answers real questions from the community as someone who has hired, mentored, and built automation teams. If you manage engineers or you are trying to grow into a more valuable role yourself, subscribe for breakdowns that connect the technical work to the business decisions behind it.

The throughline of this episode is simple and uncomfortable: interest alone does not set your market value. The people who pull ahead pair what they enjoy with what the industry will actually pay for. An engineer who can consult on the architecture of a SCADA and MES platform commands a premium over one who only produces AutoCAD or EPLAN drawings, not because one role matters more on a given day, but because the harder skill takes more years to master and carries more uncertainty and communication load. Treating your own learning like a portfolio, weighting it toward marketable and in demand skills, is the single most useful habit discussed here.

That same lens reframes a career change. One viewer asked about moving into automation in his 40s from law enforcement and a Salesforce administrator role, with no engineering degree. The honest answer is that the most direct path for someone fluent in business IT, CRMs, and ERPs is SCADA and MES, not the electrician route, because the work feels familiar and the transition story writes itself in an interview. Inductive University from Inductive Automation is free and will take you a long way on the SCADA side before you ever pay for formal training.

For managers, the rest of the episode is just as relevant. There is a detailed answer on when to deliberately limit a system's scope rather than over deliver, including how time and materials contracts shift risk to the customer while fixed bids shift it to the integrator, and why every extra mile should be a conversation with the customer before it becomes free work. The final question walks through a real OT network fault where two Rockwell devices ended up sharing an IP address behind NAT modules, and why DHCP in a production environment, aging battery backed controllers, and a single moved cable are the usual suspects.

Learn more at Joltek:

- Workforce Development and Education: https://www.joltek.com/services/service-details-workforce-development-education

- Recruiting for Robotics and Automation at Small Manufacturers: https://www.joltek.com/blog/recruiting-robotics-automation-small-manufacturers

- IP Addresses in Industrial Automation and OT Networks: https://www.joltek.com/blog/ip-addresses-industrial-automation-ot-networks

- Manufacturing Execution Systems and Business Strategy: https://www.joltek.com/blog/manufacturing-execution-systems-business-strategy

Timestamps

0:00 Heading to Automate 2026 and What This Q&A Covers

0:55 How Do You Actually Get Better at Your Controls Job

8:18 How to Learn PLC Programming on Your Own

13:50 Who Is Joltek

14:25 Career Change Into Automation Without an Engineering Degree

24:05 When to Limit Scope on Purpose: T&M vs Fixed Bid

33:45 OT Network Fault: Two Rockwell Devices, One IP Address

39:40 Closing and How to Reach Out

If you are weighing a skill investment, a hire, or a career move in automation, send a note on LinkedIn or leave a comment. Vladimir reads and responds.

Come find the team at Automate 2026 in Chicago.

If you program, wire, commission, or maintain industrial systems, this episode is built for you. I go past the surface and into why this specific failure mode is so expensive. The controller in that chassis predates Studio 5000, which means you cannot flash it forward and the program carries no stored comments, so the next person to walk up uploads logic with zero documentation. Support ended around 2017, so if the processor cooks itself in that heat you cannot simply buy a replacement, and the same controller that runs a multimillion dollar line is worth maybe fifty dollars on the used market. Add an unsupported Data Highway Plus network that tops out at 57.6 kbps next to gigabit EtherNet/IP, and the real risk is not the one hour power supply swap. It is the four week outage when a peripheral fails and there is no spare and no migration plan. Unplanned downtime now averages around $260,000 per hour across manufacturing and closer to $400,000 per hour for US plants, which is exactly why the do nothing answer is the most expensive one.

From there I review a first automation project, a farm control panel built on an AutomationDirect CLICK PLC, and get specific on HMI design. Too much bright green and red, motor status that should show more than running or stopped, and a navigation scheme that changes position from screen to screen. I also critique a Siemens S7-313C and KTP 700 training kit, explain why I would add real networking gear and industrial buttons, and why an elevator is a better portfolio project than an obscure oil and gas spec. Then I share the most exciting project I have worked on, a full peanut butter plant modernization with Stratix switches, batch handling, and FactoryTalk View, and I close with a beginner deep dive on program structure, alarm management, and why HMI design is more important than most builders treat it.

If this kind of field level breakdown is useful, subscribe so you catch every Q&A.

Learn more at Joltek:
- Rockwell PLC Lifecycle Migration Guide: https://www.joltek.com/blog/rockwell-plc-lifecycle-migration-guide
- Control System Modernization Strategy: https://www.joltek.com/blog/control-system-modernization-strategy
- Root Causes of Downtime in Industrial Automation: https://www.joltek.com/blog/root-causes-downtime-industrial-automation
- Systems Modernization and Risk Management: https://www.joltek.com/services/service-details-systems-modernization-risk-management

Timestamps
0:00 Intro and how this Q&A works
0:50 HMI and UX review of a first automation project
9:50 The nightmare cabinet: an obsolete ControlLogix nobody will modernize
17:40 PLC training kit feedback: Siemens S7-313C and KTP 700
26:30 My most exciting PLC project: a peanut butter plant
32:30 Program structure, alarm management, and HMI design

More from Joltek:
Website: https://www.joltek.com
Connect on LinkedIn and leave your questions for the next Q&A in the comments.

Most managers inherit a control system standard rather than choose one from a clean sheet. A plant accumulates machines from different builders, each arriving with its own controller, and over time the cost and difficulty of supporting many vendors pushes the organization toward harmonizing on one platform. The honest answer to "why Allen-Bradley and not Siemens" starts there. Allen-Bradley and Rockwell Automation dominate North American plants because the surrounding ecosystem dominates: the integrators, the distributors, the training centers, and the engineers who can be on site during a midnight shift all cluster around the regionally entrenched brand. Siemens carries that same weight across most of Europe, while Omron and Mitsubishi hold strong positions across much of Asia. Standardizing on a platform your region cannot easily staff or source is a real operational risk, not a spec sheet footnote.

There is a genuine technical contrast worth understanding too. In this episode the comparison is framed as Rockwell being easier to use but more prescriptive, similar to a closed and guided ecosystem, while Siemens offers more flexibility and customization at the cost of engineering complexity. North American teams tend to lean heavily on ladder logic and external integration resources, whereas European teams more often carry deeper in-house engineering capability and reach for structured text. Once a platform is embedded, the surrounding products follow it: the HMIs, the VFDs, the servo drives, the managed switches, and the energy monitors all integrate more cleanly inside Studio 5000 or TIA Portal, which is exactly how vendor lock-in compounds and why switching platforms after you scale almost never pencils out.

This Q&A also tackles the questions that fill a maintenance manager's week. We cover whether to suspect PLC logic or field hardware first when a conveyor stops intermittently, using a real example of a Siemens S7 line where an intermittent proximity sensor tripped the stop logic without ever holding an alarm long enough to be obvious. We get into building latches and trending the exact stop bits so an intermittent fault can be captured instead of chased for hours. We look at a vandalized PanelView Plus terminal, what a screen replacement actually involves, and why a full terminal can run $2,000 to $5,000 depending on features and source. And we close on whether every control system inevitably becomes harder to modify over time, why software segmentation per line keeps that complexity contained, and where SCADA and MES layers genuinely do raise the risk.

If you are serious about manufacturing, automation, and making technical decisions you can defend to leadership, subscribe and join the community.

Learn more at Joltek:

- Control System Modernization Strategy: https://www.joltek.com/blog/control-system-modernization-strategy

- Rockwell PLC Lifecycle Migration Guide: https://www.joltek.com/blog/rockwell-plc-lifecycle-migration-guide

- Root Causes of Downtime in Industrial Automation: https://www.joltek.com/blog/root-causes-downtime-industrial-automation

- System Integrators in Manufacturing: https://www.joltek.com/blog/system-integrators

Timestamps

0:00 Intro to Factory Field Notes

0:38 On the road at a client site

1:08 New apprentice: how long until you feel competent

5:05 Why Allen-Bradley and not Siemens

6:00 Standardizing a plant on one PLC platform

9:00 How region decides Rockwell, Siemens, Omron, Mitsubishi

9:55 Rockwell vs Siemens: ease of use vs flexibility

11:20 How vendor lock-in compounds across the ecosystem

13:28 Troubleshooting: do you check logic or hardware first

15:50 Reading the HMI fault and working backwards

17:00 Latches and trending to catch intermittent faults

18:45 A vandalized PanelView Plus and what repair costs

20:55 Do PLC systems get harder to modify over time

24:30 Where SCADA and MES layers add real complexity

Find more from Joltek and Vladimir Romanov:

Website: https://www.joltek.com

Book a modernization consultation: https://www.joltek.com/book-a-modernization-consultation

New episodes of Factory Field Notes drop regularly. Subscribe so you do not miss the next one.

Every question maps to a decision an engineering manager is already navigating: retention, training, IT and OT scope, and how to hire and evaluate junior talent.

Subscribe for analysis of engineering team dynamics, capital planning, and the operational realities of running an industrial automation function.

Learn more at Joltek:

- IT and OT Architecture Integration: https://www.joltek.com/services/service-details-it-ot-architecture-integration

- Workforce Development and Education: https://www.joltek.com/services/service-details-workforce-development-education

- Automation Leadership: https://www.joltek.com/blog/automation-leadership

- Recruiting Robotics and Automation in Small Manufacturers: https://www.joltek.com/blog/recruiting-robotics-automation-small-manufacturers

The first question is a familiar one. Controls engineers used to spend most of their time inside PLC logic, and now the harder problem is everything around the PLC: HMI servers, edge devices, OPC UA, MQTT, historians, and the IT side consuming plant floor data. At larger sites this still gets handled by dedicated controls teams who never touch a switch or a domain controller. At smaller sites the same engineer is expected to do both, and the gap between job description and actual workload is widening fast.

The second question is the one engineering managers should pay closest attention to. A practitioner asked whether people are generally miserable in this field after two and a half years across two jobs. The pattern in the post is structural, not personal: zero training, no mentorship, hostile reception to mistakes, operators escalating against engineers, and a previous occupant of the seat who left in under a year. Schneider Electric's 2024 workforce survey reports 59 percent of frontline skilled workers over 55 plan to retire within five years, and only 9 percent of workers ages 19 to 24 are entering skilled trades. The retention play is unglamorous: structured onboarding, named mentors, and shielding junior engineers from blame culture during the first 12 to 18 months on the floor.

The third question was technical. A practitioner asked why Studio 5000 logic was applying a bitwise AND with 65,535 to a Local:2:I.Data array. That mask preserves the lower 16 bits of the 32 bit input register and discards the upper 16, a common pattern when an analog card packs two values into a double integer or when the upper bits hold status flags the application should not act on. For managers approving training spend, this is the type of question every junior engineer carries into their first commissioning, and a short internal documentation library of these patterns saves hours per project.

The fourth and fifth questions both connect to skill development. One practitioner posted a wall of secondhand PLCs including SLC 500, ControlLogix L71, CompactLogix, Micro800, MicroLogix 1000 through 1400, Point I/O, GE Fanuc, ABB, and Mitsubishi units, most sourced for a fraction of new pricing. Another engineer with 15 years in the field admitted feeling behind on virtualization, domain controllers, and firewall rules. The structured path is Cisco CCNA fundamentals, then VLAN configuration on Rockwell Stratix or equivalent managed switches, then IP planning, OT segmentation, and the IT and OT DMZ patterns common to modern plant networks. Sponsoring a shared lab and protecting dedicated learning time are the two interventions engineering managers control most directly, and both compound.

The sixth question was the entry level PLC market in Germany. The honest read is that Germany has a real shortage of automation engineers and a soft labor market for new graduates at the same time. Plant closures driven by pressure from Chinese electric vehicle manufacturers, rising energy costs, and broader economic conditions are pushing experienced engineers into open roles before junior candidates compete. The platform expectation in most German plants is Siemens TIA Portal and WinCC, with Beckhoff and Phoenix Contact present in specific verticals. The consistent hiring filter regardless of region is the same: can the candidate operate safely on a live plant floor, and will they put in legwork before escalating.

Timestamps

0:00 Intro and How to Submit Questions

0:30 Q1: Is Automation Now Software Infrastructure

4:00 Q2: Why Controls Engineers Burn Out

10:30 About Vladimir and Joltek

11:00 Q3: Bitwise AND in Studio 5000 Explained

14:50 Q4: Building a Personal PLC Training Bench

18:20 Q5: The IT and OT Skills Gap

23:00 Q6: PLC and Automation Job Market in Germany

28:30 What Senior Engineers Look For in Junior Hires

31:30 Closing Thoughts

Connect with Vladimir and Joltek:

Website: https://www.joltek.com

Book a modernization consultation: https://www.joltek.com/book-a-modernization-consultation

About Joltek: https://www.joltek.com/about

Rockwell Automation surveyed 1,560 decision makers across 17 countries for the eleventh annual edition, with 62 percent holding spend authority.

Subscribe for executive analysis of industry research, capital allocation, and the operational reality behind digital transformation.

Learn more at Joltek:

- Digital Transformation in Manufacturing: https://www.joltek.com/blog/digital-transformation-in-manufacturing

- Industry 4.0 and Smart Manufacturing: https://www.joltek.com/blog/industry-4-0-smart-manufacturing

- Industrial Cybersecurity (ICS): https://www.joltek.com/blog/industrial-cybersecurity-ics

- Unlocking Industrial Data in Manufacturing: https://www.joltek.com/blog/unlocking-industrial-data-in-manufacturing

The report frames 2026 as the start of an execution era, with smart manufacturing moving from pilot to production. The directional read is right. The specific numbers behind it deserve closer scrutiny from anyone carrying P&L responsibility for a plant or a portfolio of plants.

The most generous figure in the report is the claim that 43 percent of collected manufacturing data is now used effectively. In dozens of plant walks across food and beverage, CPG, life sciences, and pharmaceuticals, the realistic number looks closer to 5 to 7 percent once "effectively" is defined as data that is captured, contextualized, and actively moving OEE, quality, yield, or cost. Most production data still dies at the PLC and DCS layer, never reaching a historian, never landing in a database, and never informing a decision. The companion claim that 34 percent of operations are AI augmented today is similarly soft. Microsoft Copilot helping a quality engineer write a better email is not the same as a machine learning model closing a vision loop on a packaging line, and the survey does not separate the two.

The cybersecurity finding is more credible and more strategically important. 46 percent of respondents reported a cyber incident in the past year, and the report correctly identifies the IT and OT integration layer as the most vulnerable surface. The angle that the prose underweights is insurance. Cyber regulations already in force in the European Union under NIS2 are penalizing critical infrastructure manufacturers for extended downtime, and equivalent frameworks are expected to reach North America by 2027. Premiums for industrial cyber coverage are rising in advance of those frameworks, and underwriters increasingly demand evidence that legacy Windows XP machines, SLC 500 controllers, and PLC 5s are either retired, patched, or placed behind defensible firewall architecture. That is the dynamic shaping CapEx priorities right now, more so than the headline AI numbers.

The eight step path forward published in the report is recognizable to any operations leader who has run a transformation program. Two of the items deserve more weight than they typically receive. The first is communicating progress to build organizational momentum. A measurable share of transformation programs lose their best engineers to roadblocks, IT pushback, and approval friction long before the technical work is the bottleneck. The second is governance, because the data and decision rights questions only get harder as more systems become connected.

A useful framing for the data side of this work is connect, collect, store, visualize. Connect is mostly a protocol decision across OPC UA, MQTT, and EtherNet/IP in a mixed Rockwell, Siemens, Beckhoff, and Opto 22 estate. Collect introduces software on top of the control layer and pulls in OT to IT cybersecurity considerations directly. Store is a question of historian, time series database, and cloud strategy. Visualize is where the human in the loop decision discipline lives, and where most organizations still underinvest. PwC's 2024 Digital Trends in Operations finding that only 32 percent of industrial products companies say their operations technology investments delivered expected results sits honestly alongside the more optimistic figures Rockwell publishes. Deloitte and the Manufacturing Institute project 2 million unfilled manufacturing jobs in the United States by 2030, which reframes automation investment as a labor strategy as much as a productivity one.

The full report is free to download from Rockwell Automation and the link is provided in the description below.

Timestamps

0:00 Why Industry Reports Matter

1:30 Note From the Chairman and CEO

5:20 Demographics and Who Actually Responded

8:50 Executive Insights and Headline Stats

11:30 Energy, Workforce, and Cyber Pressures

13:40 Is 34 Percent of Operations Really AI Augmented

16:00 The 43 Percent Data Utilization Claim

22:00 Workforce Reskilling Reality Check

24:30 IT and OT Cybersecurity Incidents

30:20 Five Capabilities of the Execution Era

36:20 Connect, Collect, Store, Visualize

41:00 Cyber Insurance Premiums and EU NIS2

45:50 Workforce Empowerment

51:20 The Eight Step Path Forward

56:40 Closing Thoughts

Connect with Vladimir and Joltek:

Website: https://www.joltek.com

Book a modernization consultation: https://www.joltek.com/book-a-modernization-consultation

About Joltek: https://www.joltek.com/about

From legacy PLC migration to the polymath trap, this episode walks through the operating decisions quietly shaping plant floors across the country right now.

Subscribe for weekly conversations on industrial automation, manufacturing modernization, and the operational decisions that separate plants that scale from plants that stall.

Learn more at Joltek:
- Rockwell PLC Lifecycle and Migration Guide: https://www.joltek.com/blog/rockwell-plc-lifecycle-migration-guide
- Control System Modernization Strategy: https://www.joltek.com/blog/control-system-modernization-strategy
- Systems Modernization and Risk Management: https://www.joltek.com/services/service-details-systems-modernization-risk-management
- Recruiting Robotics and Automation Talent for Small Manufacturers: https://www.joltek.com/blog/recruiting-robotics-automation-small-manufacturers

This episode opens with a project that has been getting a lot of attention from controls engineers building interview portfolios. A candidate built a virtualized material handling system in Factory IO, controlled it almost entirely in structured text on CODESYS, used Inductive Automation Ignition for the SCADA layer with role based perspective sessions, and ran the architecture across a PC, an EtherNet/IP network, and a tablet client. From a hiring manager perspective, the project is impressive. The harder question is whether it converts in an interview. If the plant runs Allen-Bradley Studio 5000 or Siemens TIA Portal, the hiring engineer often does not give a CODESYS portfolio full credit even when the architecture is more advanced than what the role requires. The practical move is to bring the demo on a tablet, prepare to defend the design choices in plain operational terms, and ideally re implement a slice of the project on whatever platform the target company actually runs. That last step is what turns an interesting candidate into a hireable one.

The second question is the one every plant manager with aging infrastructure should be asking. A maintenance team spent a weekend cleaning up the wireway and reseating cards in an Allen-Bradley PLC 5 panel on a lumber sorter at a sawmill. The panel now looks excellent. The underlying business risk did not change. The Rockwell Automation PLC 5 line has been discontinued for years. Replacement I/O cards, specialty modules, Data Highway Plus interfaces, and ControlNet remnants now move through eBay, part auctions, and a shrinking pool of distributors at prices that increasingly exceed new CompactLogix or ControlLogix hardware. Spending engineering and skilled trades hours to revamp an obsolete asset without addressing the migration path is a capital allocation problem disguised as a maintenance project. For most plants running PLC 5 on a production critical line, the right next step is a migration plan to CompactLogix or ControlLogix, scoped honestly around the specialty modules and protocols still in use.

The third question is the kind every operations leader recognizes. A family business inherited a three axis die casting robotic arm from 1991. The robot was acquired secondhand, never used, and someone stripped every wire from the cabinet for copper value before they took possession. The owner is asking whether to wire it back to the original terminal numbers or use the project as an excuse to modernize the PLC, the HMI, and the VFD. The honest answer from anyone who has lived through this kind of project: start by collecting part numbers from the largest components, retrieve the program backups if any exist, call the OEMs for the SEW Eurodrive, the legacy Siemens controller, and the robotic system, and price the migration before touching a wire. If the migration path is brutal and the business cannot afford the timeline, the better capital decision is often to retire the asset and source a functional secondhand unit rather than spend two years of part time effort getting a 35 year old machine back to a marginal state of operation.

Connect with Joltek:
Website: https://www.joltek.com
Book a Modernization Consultation: https://www.joltek.com/book-a-modernization-consultation
All Services: https://www.joltek.com/services

Timestamps
0:00 Intro
0:30 Home lab project in CODESYS and Ignition, interview worthiness
5:40 About Vladimir and Joltek
6:18 Allen-Bradley PLC 5 cleanup versus full migration on a lumber sorter
10:18 Rewiring a 1991 three axis robotic arm with no documentation
18:30 Polymath or specialist, the honest career conversation
29:00 PLC programming versus troubleshooting in real organizations
35:30 Essential skills to break in as a PLC technician

This first episode pulls the most discussed questions from r/PLC, PLCtalk, control.com, and automation subreddits, then answers each with the perspective a working controls engineer would give. Subscribe to follow the rest of the series.

Learn more at Joltek:

- PLC Scan Cycles, Polling, and SCADA Data: https://www.joltek.com/blog/plc-scan-cycles-polling-scada-systems-data

- Connecting an Allen Bradley PLC to Ignition: https://www.joltek.com/blog/connecting-allen-bradley-plc-ignition

- Modern Plant Network Requirements in Manufacturing: https://www.joltek.com/blog/modern-plant-network-requirements-manufacturing

- Rockwell PLC Lifecycle Migration Guide: https://www.joltek.com/blog/rockwell-plc-lifecycle-migration-guide

Question one is the RavSControls free browser based ladder logic simulator. I built a motor start and stop circuit: normally open start, normally closed stop, a coil for the motor, and a seal in branch on the motor running tag. Latching worked. The UI has a vibe coded feel familiar to anyone who has used Claude Code or Gemini, and it is useful for rung structure, contact and coil semantics, and the basic instruction set. It is not a substitute for Studio 5000, TIA Portal, or CODESYS when you need deterministic scan cycles or peripherals support, but for an introductory motor starter it is a clean free sandbox.

Question two is from a 40 year old switching out of retail and transit into automation through a community college program funded in part by the Pell Grant. Age is not the limiter, time is. Working 15 hours a day with two kids leaves very little room for the math, physics, and mental models automation work assumes. The market is real though. The 2025 workforce data lists the skilled worker shortage as a top business threat for 38 percent of manufacturers, and the average controls engineer salary sits at $119,682, up 4.3 percent year over year. The path takes longer than for a 20 year old in the same program, but it is absolutely possible.

Question three is whether physical PLC trainers with switches, BCD displays, and analog dials are still worth building. After the first hour of PLC wiring practice, the value of physical pushbuttons and LEDs drops fast. PID loops and sequence logic are better simulated in software. You can latch bits inside Studio 5000, RSLogix 5000, TIA Portal, or CODESYS, and use Inductive Automation Ignition or Node RED to emulate field devices and HMI screens. Physical trainers earn their keep for teaching wiring discipline; for logic instruction, virtualization wins on cost and flexibility.

Question four is from someone who built a fully browser based IEC 61131 part 3 environment with all five languages, OPC UA and Modbus, live tag monitoring, an HMI designer, multi user role based access, and version history. The build is real; the market problem is harder. Rockwell controllers run on Studio 5000. Siemens controllers run on TIA Portal. Interfaces, address structures, AOI tooling, and module configuration are tightly coupled to the vendor and firmware, and exporting cleanly into either stack is rarely smooth. The architecture also underestimates peripherals: VFDs, servo drives, smart sensors, third party load scales, and safety relays all need vendor specific configuration that OPC UA or Modbus alone does not erase.

Question five is whether modern PLC projects are actually getting more complex. They are. The PLC logic is often the easy part now. The full scope today usually includes HMI development, plant SCADA on top of local screens, OT networking with managed switches, VLAN segmentation, NAT for OEM cells, remote access for vendors and on call engineers, and a databases and analytics layer feeding plant KPIs like OEE, MTBF, and MTTR. Since 2020, remote access has shifted from a nice to have to a default expectation, and the pressure to measure with real time data has made historians and SCADA a baseline component, not an add on. The controls engineer role now extends well into IT territory.

Timestamps

0:00 Intro to the Q&A Series

0:50 Free PLC Ladder Logic Simulator (RavSControls)

5:33 Switching Into Automation at 40

8:23 Channel Intro: Vladimir Romanov and Joltek

8:55 Physical vs Virtual PLC Trainers

12:20 Browser Based IEC 61131 Part 3 PLC IDE

15:30 Are PLC Projects Getting More Complex?

19:30 Closing and Call for Questions

Visit Joltek: https://www.joltek.com

About Vladimir Romanov: https://www.joltek.com/team-members/vladimir-romanov

Book a modernization consultation: https://www.joltek.com/book-a-modernization-consultation

#PLCProgramming #IndustrialAutomation #LadderLogic #ControlsEngineering #OTNetworking