How to setup and use RS Emulate, S2 E40.And to see a video version of the above, check out the below episode of The Automation Minute: If you've found this article helpful and would like learn more about RSLogix, RSLinx, RS Emulate, and A-B PLCs, I recommend you check out my affordable PLC video training course at PLC Basics Second Edition. At this point you can use the free copy of RSLogix I showed you how to get last week, and the RSLogix tip from earlier this week to go online with your emulated PLC.
If you see your emulated PLC show up under the”EMU500-1 driver” as shown above in the red box, then your emulated PLC has been loaded and the RSLinx driver is communicating to it.
I typically leave it at the default of zero, and just click on OK: With the Emulated driver added, we can now close the Configure Drivers window: To check it's working, click the “plus sign” on the left side of the “EMU500-1 driver” in the RSWho window to expand it, and the select the”EMU500-1 driver” to insure it starts browsing: (if an RSWho window is not already open, use the menu, “Communications – RSWho,” to open one): You can open “Configure Drivers” by either selecting it from the “Communications” menu, or by clicking on the “Cable” icon on the toolbar: When “Configure Drivers” is open, select the “SLC 500 (DH485) Emulator driver” from the “Available Driver Types” drop down list: Then click on “Add New”: I recommend leaving the default name unchanged, and then clicking on OK: Next, provide a network address (aka Station Number) on the emulated network for RSLinx. The first step is to launch RSLogix Emulate 500 and open an RSLogix Micro or RSLogix 500 file using either the “File – Open” menu, or the open file toolbar icon as shown below: In this example, I'm going to open program P14 from my PLC Basics course: Once you select a file, the next step is to give it a virtual network address (aka Station #) on the emulated network, and press OK: This last step in RS Emulate is optional – you can put your emulated PLC into the run mode by clicking the “Run” button on the toolbar: Now that we have an emulated PLC running, our next step is to open the “configure drivers” window in RSLinx Classic Lite. At this point, it should only show your workstation in location 00.Last week I walked through how to get a free copy of RSLogix Emulate 500, and in today's article I'll show you how to set it up. Now that the driver is in place, you can check that it’s working correctly by expanding it within the main view.
This number represents the location of your PC the default number should be fine. Give your driver a unique name and set the number of your station to 0. Once you click on “Add New…”, a pop-up will appear and require you to make a few selections. If you haven’t make sure to follow the tutorial link below.ĭownload RSLogix 500, RSLogix 500 Emulate & RSLinx. Keep in mind that this driver will only be visible if you’ve properly installed the tools we’ve talked about in the download section. Once here & while the computer has RSLogix 500 Emulate installed, you should be able to select a driver which is called “SLC 500 (DH485) Emulator driver”. Just as before, we navigate into the RSLinx Classic interface and enter into the “Configure Drivers” menu. However, this process is slightly different due to the fact that we have a “virtual” driver which will point to our PC. We’ve looked at how to set up drivers in our previous tutorial on Connecting to MicroLogix 1100 PLC.
It is therefore recommended to check them out before jumping into this topic. This tutorial builds upon the last few pieces of content which we’ve released.
In this tutorial, we will be exploring how to get started in RSLogix 500, RSLinx & RSLogix 500 Emulate in order to bring a full program online within our computer. However, it’s somewhat tricky to get this going for the first time. Working in RSLogix 500 Emulate is straight forward once everything is working & talking properly. RSLogix 500 Emulator brings a lot of capability & accessibility to those who don’t have access to hardware or simply want to test certain logic before deployment.