How does modernizing from serial-based protocols like DH45 to Ethernet-based communication improve factory infrastructure?
Answered at 24:50 in Built for the Operator: Julio Velasco on Design, Education, and a Career Shaped by Ignition · Ignited: Striking Industrial Automation Conversations
How does modernizing from serial-based protocols like DH45 to Ethernet-based communication improve factory infrastructure?
Moving from RS-485 serial communication (DH45) to Ethernet requires adding network infrastructure like switches and IDFs, involving electricians and network specialists to run Ethernet drops to edge devices. This is expensive and provides no immediate gratification, but it establishes the foundation needed to connect previously isolated devices, maintain system functionality during the migration, and enable future smart factory capabilities beyond just adding screens.
Full answer and detailsRead the whole answer, key facts and every other question from this episode
In short
Moving from RS-485 serial communication (DH45) to Ethernet requires adding network infrastructure like switches and IDFs, involving electricians and network specialists to run Ethernet drops to edge devices.
Julio Velasco, Founder at IOScada · Built for the Operator: Julio Velasco on Design, Education, and a Career Shaped by Ignition · Ignited: Striking Industrial Automation Conversations · answer at 24:50
Key takeaways
- Moving from RS-485 serial communication (DH45) to Ethernet requires adding network infrastructure like switches and IDFs, involving electricians and network specialists to run Ethernet drops to edge devices.
Quote to remember
“It's a gradual thing where you're basically getting all the devices that are edge devices or not even part of a network and then bringing them up to a point where now you communicate with them, which that's a huge feat.”
— Julio Velasco
The full answer · about 2 min
Moving from RS-485 serial communication (DH45) to Ethernet requires adding network infrastructure like switches and IDFs, involving electricians and network specialists to run Ethernet drops to edge devices. This is expensive and provides no immediate gratification, but it establishes the foundation needed to connect previously isolated devices, maintain system functionality during the migration, and enable future smart factory capabilities beyond just adding screens.
Key facts
- 2008-2009: Financial crisis period when Julio joined Inductive Automation / Calmetrics after being laid off
- 80 percent: Software licensing costs as portion of integrator project costs that frustrated Steve Heckman
- 20-30 percent: Remaining profit margin for integrators after software licensing fees
- Nearly 2 decades: Duration of Julio Velasco's involvement with Inductive Automation ecosystem starting around 2008
- Hundreds of plants: Number Julio has visited where operators don't know what firmware versions run on their PLCs
People, companies and topics mentioned
More answers from this episode
- 4:00Why is automation considered recession-proof in manufacturing?
- 8:00Why did Steve Heckman create Inductive Automation and Ignition instead of building another SCADA tool?
- 12:15What is the difference between brownfield and greenfield in industrial manufacturing modernization?
- 19:50What is the problem with Industry 4.0 implementations that only add sensors and screens to legacy machines?
- 24:00What is the first step Julio Velasco takes when assessing a manufacturing facility for digital transformation?