Back to all FAQs

question

What's the most frustrating 'legacy system integration' horror story you've encountered when trying to connect a 1990s Mitsubishi PLC to modern IIoT platforms, and what workarounds actually worked in production environments?

answer

Oh man, where do I even start? One of the worst horror stories I've heard involved trying to connect a 1990s Mitsubishi A-Series PLC to a modern cloud-based IIoT platform. The PLC was still running perfectly fine on the factory floor, but it spoke a proprietary protocol that modern systems just couldn't understand natively.

The real nightmare began when we discovered the PLC's communication ports were RS-232 only - no Ethernet, no TCP/IP, nothing modern. We tried using protocol converters, but the Mitsubishi's proprietary protocol kept dropping data packets randomly. The worst part? The PLC would occasionally just stop responding for hours, then mysteriously start working again without any intervention.

What actually worked in production? We ended up using a multi-layered approach:

1. A dedicated industrial protocol converter that could handle the Mitsubishi's legacy protocol and convert it to Modbus TCP
2. A small industrial PC running OPC-UA server software to act as a bridge
3. Implementing heartbeat monitoring and automatic reconnection logic
4. Adding local data buffering so we wouldn't lose data during communication drops

The key was accepting that we couldn't make the old PLC 'modern' - we had to build a robust translation layer around it. It wasn't pretty, but it kept production running while we planned the eventual PLC replacement.

Recent Q&A

Quickly browse the latest questions and answers

Contact form