Attention everyone, I am currently assisting a client who is still using an old ABB Advant/MOD300 system (v14.4) from the y2k era. Back then, I set up the ABB Industrial IT MOD300 OPC Server 1.1/2 (v1.01.035), which operates on OPC DA 1.0. This software must be installed on the same PC as the Interface Board, also known as the RTAB in ABB MOD terms. The RTAB emulates a Multibus1 system on a PCI board to allow data retrieval over the MOD300 DCN in a masterless token ring topology. As you can tell, upgrade options for the PC and its operating system are limited, currently stuck on Windows XP. Despite attempts to run it on Windows 7, it was unsuccessful. I have incorporated some Matrikon Middle Ware (their OPC-ODBC Client) to extract real-time data from the ABB MOD system and store it in a SQL Database. Everything has been running smoothly, although challenges have arisen as SQL is continuously updated. However, a new obstacle has emerged as the customer's Corporate IT department mandates the use of Windows Server 2019 with SQL Server 2019, rendering the old SQL Drivers on Windows XP unusable due to the requirement of TLS 1.2. Previous compatibility with TLS 1.0 has been disrupted by this change. Despite my efforts to resolve this issue with Corporate IT, including exploring patches and workarounds, the solutions provided by Microsoft have not been effective. The client is transitioning to Inductive Automation's Ignition system on multiple machines, moving away from the ABB Advant/MOD300 platform to ControlLogix/Ignition setup. However, two machines with specialized equipment cannot be migrated immediately, prompting me to consider integrating visualization and data archiving into Ignition for basic functionalities. This would entail establishing communication with the ABB MOD300 OPC Server and potentially archiving data to SQL within Ignition. Nevertheless, my attempts to connect OPC Clients like Kepware, Matrikon, and OPC-Expert to the MOD300 server located on another machine have been unsuccessful so far. Adjusting DCOM settings in the software has not yielded the desired results. The complexity is further compounded by the customer's deployment of Ignition Servers on Linux for running multiple machines, necessitating caution to prevent any disruptions. I am seeking advice from anyone who has successfully accessed data remotely from the ABB MOD300 OPC Server. I plan to collaborate with their IT team to investigate any potential obstacles, considering that Port 135 is open and no VLAN crossing is involved at the moment. Although experience in this area may be scarce, I am hopeful that someone may possess the necessary expertise, even if it means reaching out to individuals in Rochester, NY or Columbus, OH.
I will provide further details. Recently, the corporate IT department of the customer prohibited the direct connection of OPC DA 1.0 Servers to Ignition due to security reasons. Therefore, the new goal is to locate a suitable OPC UA Tunneller or Wrapper that is compatible with Windows XP. This software will serve as a bridge between the MOD Advant OPC DA 1.0 Server and the Ignition Gateway, enhancing data transfer and security.
Hey! I do sympathize with your predicaments; systems from that era can be quite troublesome to interface with today's tech landscape. However, I had a similar challenge with an old system a few years back and what worked for me was inserting a "data diode" of sorts in the form of a separate server running on an OS that could communicate with both systems. This server machine linked the old data source, then updated to a newer database on a modern system. It does add another layer of complexity and potential failure points, but it could bridge the gap without needing to run outdated systems on unsecured OS versions. It may be worth looking into these type of solutions if you haven't already.
I can see you're dealing with quite an obscure yet intriguing challenge! While I don't have specific experience with the ABB MOD300 system, I've had similar experiences working with outdated systems and OPC servers. From your description, it seems like the Hardware - Software interface is the main issue, complicated by requirement of TLS 1.2. My suggestion would be to first look into legacy hardware support options, especially software bridge tools that can 'translate' between modern and legacy hardware. Secondly, regarding OPC connections, you mentioned you're adjusting DCOM settings in the software, have you also tried tweaking the Configurations in OPC Client (like ProgID, Security)? These can also play a pivotal role in successful remote communication. Lastly, transitioning to a more open-source OPC server like OpenOPC might be beneficial given the flexibility it provides in tailoring to specific applications. Hope this helps!
It sounds like you're facing quite the challenge with that legacy system! Given the complexities involved, especially with DCOM settings and the push towards newer technologies, I can see how it could be tricky to establish that OPC connection. Have you considered using a VPN or a direct point-to-point connection as a workaround? Sometimes, experimenting with the firewall configurations on both the server and client machines can make a big difference too. Also, reaching out to those with experience in the field may reveal some hidden gems of solutions! Good luck navigating through this; I’m sure there are people who've tackled similar hurdles.
It sounds like you’re navigating a tricky situation with that legacy system! Have you looked into setting up a virtual machine with Windows XP on a more modern hardware while bridging it to your network? This way, you might keep the old software environment intact while still complying with your IT department's new security guidelines. Also, sometimes playing with the DCOM settings can be a pain, but ensure that the firewall on both the client and server-side allows traffic for the relevant ports beyond just Port 135. I wish you the best of luck; transitioning to Ignition should yield great benefits in the long run!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: - Challenges include compatibility issues with newer operating systems like Windows Server 2019, the need for TLS 1.2 which disrupts previous compatibility with TLS 1.0, difficulties in connecting OPC Clients to the MOD300 server located on another machine, and complexities arising from deploying Ignition Servers on Linux.
Answer: - Despite attempts to resolve this issue with Corporate IT through patches and workarounds, finding effective solutions has been challenging. Upgrading to newer SQL Drivers compatible with TLS 1.2 may be necessary.
Answer: - Yes, it is possible to establish communication with the ABB MOD300 OPC Server and potentially archive data to SQL within Ignition to enable basic functionalities, especially for machines where immediate migration is not feasible.
Answer: - Troubleshooting steps may
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.