Factory Field Notes

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.

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

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-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

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-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

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-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

Wireless PLC Access during commissioning lets you program and troubleshoot a controller from a laptop without running an Ethernet cable across the plant floor. This video shows the field method and the disciplined alternative.

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.

In-House vs Contractor is the call every engineering manager eventually faces on aging control systems, and this field Q&A works through when to keep the work internal and when to bring in outside help.

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

Industrial automation Q&A on the skills shift every controls team is feeling, plus a cautionary Rockwell quality story, a TIA Portal version trap, and honest career advice. This episode answers five of the most upvoted questions from the r/PLC community.

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.

Industrial automation careers reward the people who treat skill building like a capital investment, not a hobby. This Q&A breaks down how to grow in controls, SCADA, and MES, how to break into the field without an engineering degree, and how to think about which skills actually pay.

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.

This obsolete ControlLogix has been running a whole production line for over a decade, the power supply just failed, and nobody will approve the modernization. In this Q&A I work through five real questions from the community, and the one that hits hardest is the nightmare cabinet: a dusty, ten foot high enclosure built around a controller that ended support years ago.

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.

Allen-Bradley vs Siemens is rarely a pure technology decision, and this field Q&A breaks down why region, hiring, support networks, and vendor lock-in usually decide your PLC standard long before specs do. If you own a platform decision, this gives you the real reasoning to defend it upward.

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.