I am seeking assistance in establishing a connection between an Allen Bradley Micrologix 1200 using DF1 protocol and a WinCC Advanced project on a PC station (not HMI). Currently, I am able to run the project using WinCC RT at Windows startup, but I am using WinCC Professional, which does not have a driver for connecting with the Micrologix 1200 via serial port. If I switch to WinCC Advanced to create a project for the PC station, I can find a driver for serial communication with DF1. However, I am unsure how to save the project in a way that allows it to be run by WinCC RT. Therefore, I am exploring two solutions: 1) Is there a method to integrate a DF1 serial driver into WinCC Professional? 2) How can I save a WinCC Advanced project to enable it to be run by WinCC RT at a later time? Any suggestions or advice on this matter would be greatly appreciated.
bigplik asked if it is possible to integrate the DF1 serial driver into WinCC Professional. While I may not have direct experience with WinCC Professional, I believe it can function as an OPC DA Client for RSLinx, which serves as an OPC DA Server. Additionally, bigplik inquired about how to save a WinCC Advanced project in order to later run it with WinCC RT (runtime). To achieve this, ensure that the target PC and configuration PC are connected to the same LAN. Then, launch the WinCC RT Loader program on the target PC and initiate a transfer via Ethernet from the configuration PC.
My Micrologix 1200 PLC does not have an ETH port, only a serial port available. Hey @JesperMP, are you familiar with any AllenBradley alternatives for WinCC Runtime? I want to create a basic SCADA screen to operate on a PC and link it to my AB Micrologix 1200 using DF1. Can you suggest any compatible solutions for this setup?
Both the configuration PC and the target PC are equipped with Ethernet connectivity, even if the connection to the PLC is serial. To initiate a test of WinCC Advanced RT on the configuration PC within TIA, simply click on the 'Start Runtime' button. WinCC Advanced is a suitable option for a SCADA Lite system, featuring an integrated DF1 driver. In contrast, WinCC Professional may be excessive for a project involving an AB ML1200 PLC.
I have a single PC and I need to remotely start it in order to run my PC station project using WinCC Advanced. This project requires a connection to an AB ML1200 PLC via a serial port, as no other ports are available on the AB ML1200 and there is no additional PC for use.
The WinCC Advanced programming software should be installed on the same PC designated for operation. In this scenario, simply follow the instructions for initiating the transfer process and enter the PC's unique IP address.
While I can't speak to integrating a DF1 serial driver into WinCC Professional, I can shed some light on running a WinCC Advanced project with WinCC RT. You just have to follow a few steps: 1) Create your project in WinCC Advanced as usual. 2) Then, you'll use "Compile (rebuild all)" from the menu. 3) After the compilation, you'll need to back it up via the "Backup Project" menu item. 4) Finally, restore this backup on your WinCC RT instance. This exported backup should include everything you need to execute it with WinCC RT. Always remember to stop the runtime before restoring a backup.
✅ 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: - No, WinCC Professional does not have a built-in driver for connecting with the Micrologix 1200 via serial port. You may need to consider using WinCC Advanced, which offers a driver for serial communication with DF1.
Answer: - To enable a WinCC Advanced project to be run by WinCC RT, you can save the project in a compatible format that WinCC RT can access. Make sure to follow the appropriate steps for saving and transferring the project files for seamless execution.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.