No Copy


No Right Click

Selamat Datang di Situs Belajar PLC dan SCADA

Blog gratis yang menyajikan berita seputar PLC dan SCADA.

Microsoft Windows 10

Berita seputar Microsoft Windows 10. Membahas berbagai informasi mengenai Microsoft windows terbaru.

Apple OSX

Artikel yang membahas tentang OSX terbaru dari Apple tentu sangat menarik untuk dibaca. Tak kalah serunya jika kita paham mengenai tips dan trik yang ada didalamnya.

Photography

Photography asik dan menarik jika kita mengetahuinya lebih dalam. Disini kita bisa melihat berbagai hal dari sudut pandang photo. Menarik untuk dipahami.

Tuesday, October 14, 2008

Case Study: Bronco Wine Company

Courtesy of: Inductive Automation

Weaving it all together with Web Technology

Bronco Wine Company, Ceres, CA (the producer of “Two-buck Chuck”) uses FactoryPMI for enterprisewide process monitoring, control, and troubleshooting. It was a business decision to use this technology, and is paying off handsomely for the Franzia family-owned business.

Bronco Winery — Who are they?

“Bronco Winery is passionate about producing its wines with a consistent color, flavor, and ‘mouth-feel’”, says John Franzia, a co-owner in the California-based Bronco Wine Company. He is also a 60-something embracer of technology. He comments “Anytime, everywhere”—referring to his company’s adoption of Inductive Automation’s FactoryPMI Plant Management software solution to help his staff run their wine business.

The metrics are staggering. Their top brand—Charles Shaw— sells for $2 in California, and is known as “2-Buck-Chuck”. They produce and ship over 45 million liters or 12 million gallons of this brand annually.

Other wineries that use Bronco’s services require rigorous testing and process validation since it is THEIR reputations on the line. Bronco, with facilities in Ceres, Escalon, Napa, and Sonoma can manage this and all sides of their business because of the processes they have put into place.

“FactoryPMI is an integral part of our success,” suggests Bob Stashak, winemaker at Bronco’s Domaine Napa winery. “Our reputation is at stake.”

Bronco Wine Company

Meet Paul Franzia, Engineering Manager

“We are growers, producers, blenders, bottlers, and exporters of wine.” This suggests that the complex processes and procedures of winemaking have to be right.

“We are growing all the time,” he says.

He is responsible for the move to FactoryPMI. “We were using a SCADA product for environmental controls, and interfacing it [HMI] with the PLCs that were doing the control,” says Franzia. “Communication was sporadic, and was frequently non-responsive,” he mentions.

As the need to bring more information to more people grew, it was obvious that Bronco had a problem.

“They wanted big dough to re-license each existing client,” lamented Franzia. “FactoryPMI doesn’t use this model.” It is estimated that Bronco saved over $300,000 on client licenses alone.

That wasn’t the only battle that Bronco was fighting. Their enterprise plant management and SCADA solution needed to integrate with the databases from other enterprise software applications (IFS Maintenance Management Software and ProPak). It needed to provide scalability for over 150 clients in their 4 locations, plus remote access for troubleshooting.

Project costs were important. The selected software had to be efficient in deployment of clients and development of applications due to the geography. When a new project came on-stream, everyone needed to have it—automatically. And when a new client was needed, or client access rights had to be modified, it needed to be done quickly. A web-deployed system using open standards would be desirable.

And with compliance issues of utmost importance, reporting in both real-time and historically was paramount!

With the multiple plants, Bronco also had a need for all people to see all things.

“We needed to upgrade.” Paul Franzia states.

Bronco chose FactoryPMI from Inductive Automation.

FactoryPMI is a database-centric enterprise-class plant management and SCADA software which is helping Bronco Winery streamline their business as well as helping them meet their production targets and the stringent compliance requirements of the wine industry.

FactoryPMI uses a web browser to launch its client interface. Any computer that can connect to the network and run a browser is a FactoryPMI client. All the user needs is a login ID, and they can access the system to the level which their login group allows them to go.

Administrators can add or delete users on the fly, in real-time— and from anywhere! The security model inherent in the software allows for administrators to fine tune the projects, set user policies and tracks the activities at every FactoryPMI client.

FactoryPMI uses an SQL database as its engine. Interacting and sharing information with different databases is one of the main design features behind FactoryPMI.

A full reporting tool for real-time and historical data was attractive to Bronco—especially the ‘Click-to-Graph’ component.

FactoryPMI is a solution for operations as well as the business, connecting the enterprise from the plant floor to the back office. Based on standard software platforms such as Java and OPC, FactoryPMI allows Bronco to implement Paul Franzia’s dream of having real-time insight into the operations for himself and his supervisors, and John Franzia’s desire to stay successful.

How FactoryPMI is Working for Bronco

Real-time? No problem. In the past, many of the operations were based on paper and telephone conversations. “I can be in Napa, and see what’s going on in Ceres right now. Sometimes, I tell the supervisor that there is a problem before he even knows. FactoryPMI has given us insight into our business,” Franzia states.

Phone calls from supervisors can come to Paul Franzia’s phone at any time. Regardless of where he is (even in his truck he can use his laptop and air card), he can log into the system, and onto the screen that his supervisor is looking at and provide instant ‘managerial’ feedback and help.

Management efficiency is bettered greatly.

“Manual operations are where the mistakes happen. We are removing those opportunities so they (the operators) can’t make mistakes.”

Supervisors need access to their area of responsibility from wherever they are. Ken Cullum, Maintenance Manager at the Ceres Winery says, “Our refrigeration guys would have to record the same data in four different places. Now they enter it at any FactoryPMI station.”

Inductive Automation Panel

Benefits to the Winemaking Process

The locations, although miles apart, need to appear on— screen as if they were under the same roof. FactoryPMI’s project redirection feature allows that to happen. There are presently six servers running FactoryPMI—four in Ceres, one in Escalon, and one in Napa. Each server has certain projects running on them. When a user needs to view a different part of the operation, the software redirects the client to the required project even if it’s on a different server.

Server clustering allows the FactoryPMI servers to be redundant. These servers can run the same projects, and in future state, the servers will be configured in a clustered environment which will provide redundancy.

Bronco blends wine for that consistent ‘mouth-feel’ that John Franzia talked about. The winemakers need historical data such as temperatures, and analytical data to determine which tank of wine to use for their current schedule.

Tank management is a huge part of a winemakers’ daily and weekly job description. FactoryPMI serves up the data to allow them to make the business decisions necessary to properly manage their raw assets.

If a tank temperature went too high, they will know, and will be able to adjust their procedures accordingly. Bronco is moving towards wireless tank gauging, which will be monitored by FactoryPMI. Reports and real-time alerts will be pushed to the managers and the winemakers automatically.

During crush [a 24/7 grape harvest season], the weather is king. Everything is subject to change, and when it does everyone needs to know now. When a winemaker changes the plan, the process has to be agile and react. Cross-shift information exchange is no longer a challenge for Bronco.

FactoryPMI interfaces with the ProPak ‘grower relations’ database. Trucks carrying grapes arrive at the winery, and the load is analyzed and data entered into ProPak. When the same truck arrives at the dump pit some time later, FactoryPMI interrogates the ProPak database, and compares the information with its own database, which has been manipulated by a winemaker.

During crush, there is no time for mistakes. “Our seasonal employees are not wine-wise,” says John Franzia. “They don’t know the difference between a zinfandel grape and a chardonnay, and these are the employees that are dumping the trucks.”

The right truck HAS to be dumped into the right pit, at the right time. If the wrong load gets dumped into the wrong pit, it could mean the loss of hundreds of thousands of dollars to Bronco for each occurrence.

Without manual intervention, the truck is only dumped if everything matches.

Benefits to the Bottling Operations

In all locations everyone knows ‘how you’re doing’ because of FactoryPMI. As Dino Rossini, Operations Manager suggests, “We produce a minimum of 20,000 cases a day here. This is our only KPI [Key Performance Indicator]. That’s the only thing that matters, and no one can fool the system.”

“The downtime analysis from FactoryPMI gives me the ability to ‘predict’ failures based on my knowledge,” he says. “The login and security gives the operator ownership of the ’ whatever it is that he is about to do’.”

“The trending and relational data logging of PMI helps me out in a big way. The historical rear view mirror is especially helpful when we are trying to figure out a problem.”

“They can look at it, and they can do something about it!” exclaims John Franzia.

The Click-to-Graph function has been especially useful. “Click it and up it comes,” smiles Paul Franzia.

Robert Hall, Production Manager at the Ceres Winery adds, “We use FactoryPMI to track our efficiencies, and chart our downtime. It helps with line setups as well.”

Once the wine is bottled, the finished product is trucked to a climate controlled warehouse. Based on real-time and anticipated data from the weather service, FactoryPMI tells the PLC what to do. “This is where using Java makes things like this easy,” says Paul Fallgren, the chief integrator of the Bronco technology solution at Calmetrics. “We could not have done what Paul (Franzia) wanted to do with conventional software. FactoryPMI uses industry standard methods and practices which allows me to integrate our solution with all of the other technology that Bronco uses. The owner’s demands are high, and we can respond. Their needs can be easily met with FactoryPMI development timelines.”

Downtime Analysis Screen Press Run Screen

Reporting, Troubleshooting and Tech Support

“I’m the eye in the sky with FactoryPMI and all of the managers know it,” grins Paul Franzia. Using the graph trending, data logging tables and Click-to-Graph, Franzia can easily track and pin-point operational issues to solve problems in real time. The downtime reporting tools within FactoryPMI are really what he likes. “That’s the best,” he states very deliberately. The information that is gleaned from these reports has justified capital expenditure, and “made us better.” He was referring to hitting the production targets on a shift by shift basis. They rarely miss.

Rossini was very complimentary of Inductive Automation when it came to tech support. “We know who we’re dealing with, and can put a face on the company. They fix it.” This response was to the question of ‘What do you do when things don’t work as planned?’

Paul Franzia concurs. “We talk to the people who know, not a call center.”

John Franzia wraps up our conversation by saying, “We have a hell of a lot of stuff on it. It’s pretty impressive what the software can do.”

Paul Franzia is very matter of fact when he says that he can be in five places at once. “It makes me a better manager. Efficiencies have improved upwards of 30%, productivity targets are hit everyday, and I can be more responsive to the business and to my managers.”

Steve Hechtman, President of Inductive Automation has often said, “I am always looking for something that’s too good to be true.”

Bronco Winery has found it!

Connecting IFIX SCADA to Siemens S7 using TCP/IP

Setting up an S7 connection using TCP/IP

The TCP/IP method of communication to the S7-300 and S7-400 PLC's via TCP/IP communication module uses the S7WIN, S7WINSP, S7NT, or S7NTSP protocol.

Software requirements

  • Siemens SIMATIC NET software v6.1 SOFTNET-S7 Industrial Ethernet
  • IFIXSCADA v5.x or above
  • Windows XP + SP1

Hardware requirements

  • Standard network card
  • S7-300 with CPU315-2 DP
  • Siemens power supply PS30/5A
  • Siemens CP343-1 TCP

The hardware modules occupy the following slots in the Siemens PLC:

  1. Siemens power supply
  2. S7-300 CPU 315-2 DP
  3. Ethernet CP343-1 TCP

Example configuration

All wiring should be installed according to Siemens documentation.

Installing the SIMATIC NET software

You must log in as an Administrator to install the SIMATIC NET software. Close all other running applications, including any antivirus software you may be running.

  1. On the SIMATIC NET flash screen, start the installation by clicking Install SIMATIC NET Software.
  2. The PC configuration screen appears. Click Next.
  3. Select the English language option, then click Next. Click Next again.
  4. Click yes to the licensing agreement screen.
  5. Enter your Name and Company on the User Registration screen.
  6. If you already have SIMATIC NET software installed, this will be the drive selected by default. Clear the Run automatic authorization option, and then click next. The Setup: Configuration screen appears.
  7. Select all application options to be installed. (This is necessary if you do not already have STEP7 installed on your machine. If STEP7 v5.2 or higher is already installed, you do not have to select the NCM PC/S7 v5.2 application.) Click Next.
  8. The applications you selected are installed. At the prompt, click OK to restart your system. The system restarts and installs the selected applications. Click Finish to restart your system again.

The SIMATIC NET software is now installed.

Configuring the SIMATIC NET software

This step involves using the Commissioning Wizard to configure the software you installed in the previous step.

Configuring the module

When your system restarts after the software has been installed, your system's hardware configuration is scanned. The Commissioning Wizard appears automatically. (You can also access the Commissioning Wizard at Start/Simatic/SIMATIC NET/Settings/Commissioning Wizard.)

The number of steps required depends on the number of PC Ethernet cards (or modules) detected in your PC. The more modules you operate in the computer, the more steps are required.

  1. Click Next.

    An Ethernet Network Card with with the IP addresses settings shown above was found. This is the network card that will be configured for communication with the Siemens PLC. This is put on index 5.

    Note: The index of the network card can be set with the NCM PC Configuration (hardware configuration). The station index defaults to 5 if you use the Commissioning Wizard.

  2. Select the Use the module for productive operation in configured PC station option, and then click next.
  3. Clear the SIMATIC NET OPC Server in configured PC Station option and select the Configure more applications option. Then click next.
  4. Register the names for your user application: enter VFD1 in the Name text box. This user application is put on index 1. Click Next.

    Note: The name of the application is the VFD name. This comes later in the IFIX Project Editor under Communication | Ports in the Special options text box.
  5. Click Next. This screen appears, confirming you have completed configuring the module:
  6. The configuration is saved and the PC station is reconfigured. Your existing configuration data is overwritten. Click OK to confirm at the prompt.

This completes the module configuration.

Configuring the project with the PC Station Wizard

The next step to configure the project using the PC Station Wizard.

  1. Start the PC Station Wizard.
  2. Choose Create a new project and configuration. A new project is created. Click Next.
  3. Define a new Project name; this example uses IFIXS7. Specify where the copy of the local PC station settings resides, and then click Next.
  4. Select the Edit network and connection configuration option, and then click Finish. NetPro automatically starts, displaying the network configuration.
  5. Click the Application box in the PC station, and then choose Insert | New Connection. The Insert New Connection dialog box appears.
  6. Choose the Unspecified item in the tree. From the Type menu in the Connection area, choose S7 connection. Then click Apply, and then click OK.
  7. In the Properties -S7-Connection dialog box, the local IP Address should be the address of the Ethernet card in the PC. This example uses 192.168.0.190. The partner IP Address should be that of the Ethernet CP343 module in the PLC, in this case 192.168.0.148. The Local ID is the connection identifier of this connection (here it is S7-Connection_1). It will be used later on as the address of the IFIX I/O device. Click Address Details.

    Note: The Local ID S7-Connection_1 is used later in the IFIX Project Editor under Communication | I/O Devices in the I/O Device Address text box. This name is case-sensitive and cannot not contain any spaces.

  8. In the Address Details dialog box, enter the card location of the CPU that the SIMATIC S7 communicates with. Here the card location is 2. Click OK.

    Note: Some power supplies might occupy 2 slots. If so, the card location of the CPU is one higher at 3.

  9. In the NetPro window the new S7-Connection_1 connection appears. Choose Network | Save and Compile. The Save and Compile dialog box appears.
  10. Select the Compile and check everything option, and then click OK.
  11. After completing the save and compile operation, a message appears in the NetPro window. This indicates the warnings and errors present in the configuration. If warnings occur here, then this is to be handled as information only. But if errors occur, the project configuration cannot be loaded. To view errors, choose View |Outputs.
  12. Highlight by clicking on the PC Station (TESTXP). Afterwards the connection table disappears in the message window. From the NetPro menu choose PLC | Download | Selected Stations to transfer the project configuration to the PC. Alternatively, right-click the PC Station and choose Download | Selected Stations.
  13. To confirm the overwrite of configuration data and to proceed with the download, click Yes.
  14. To confirm stopping the Target Module (Network interface Card), click OK.
  15. The configuration should now be successfully loaded. Exit NetPro and click next, and next again to finish the Commissioning Wizard. If you have errors, see for details.

Defining an access point for the application

The next step is to define an access point for the application.

  1. The Configuration Console should appear after terminating the Commissioning Wizard. If it doesn't, open the Configuration Console by selecting START / SIMATIC / Simatic Net / Settings / Configuration Console.
  2. In the Configuration Console dialog box, right-click the Access Point object, and choose New | New access point.

    Note: You can choose any name for the Access point, but it cannot contain spaces and be longer than 32 characters.

  3. In the New access point dialog box, enter your access point name (this example uses IFIXS7). Select the hardware component that will be associated with this access point (TCP/IP -> ASUSTeK/Broadcom 440x in the example).

    Note: The access point name is used later in IFIXSCADA in the Project Editor under Communication | Boards in the Special Options text box. The access point name is case-sensitive.

    After creating the access point the Configuration Console should look like this:
  4. Close the Configuration Console.

This completes the Simatic NET software configuration.

Configuring the S7 driver

The IFIX S7 driver needs three names (settings) from the SIMATIC NET software
configuration. The following points are needed:

SIMATIC NET Configuration
example
IFIX Info
Access point of the application IFIXS7 Boards, Special options
Field
VFD/Application Name VFD1 Ports, Special options Field
Name of the connection (or Local
ID)
S7-Connection_1 IODevices, Address Field

Using the Express Wizard

You use the Express Wizard to configure your communications.

  1. In IFIX Explorer, create a new (empty) test project.
  2. In the IFIXSCADA Project Editor, choose Communication | Express Wizard.
  3. In the wizard:
    • Create a new I/O Servers e.g. IOServer.
    • Create a new I/O Device e.g. IODev.
    • Select external as the type of the I/O Device (PLC): Select the Siemens | S7-300 or S7-400| TCPIP using NE2000 network CARD for Windows NT for NT/W2K/XP/2003, or the TCPIP using NE2000 network CARD for Windows 95/98 for 95/98/ME option.
  4. Define the name of the connection. In this example it is S7-Connection_1.

    Note: Do not select the Link I/O Device to an external tag Database option.

This completes this section.

Setting the Access Point

The next step in the process is to set the access point of the application.

  1. Open the Boards dialog box by choosing Communication | Boards.
  2. In the Special Opt text box, enter the access point of the application. This example uses IFIXS7.

Setting the VFD name

The next step is to set the VFD name.

  1. Open the Ports dialog box by choosing Communication | Ports.
  2. In the Special Opt text box enter the VFD Name. In this case VFD1.

Checking the name of the S7 connection

The next step is to check the name of the S7 connection.

  1. Open the I/O Device dialog box by choosing Communication | I/O Devices.
  2. In the Address field enter the name of the connection to the PLC. This example uses S7-Connection_1.

Variable declaration

The next step is to declare the variables.

  1. Open the Tags Form by choosing Tags | Variable Tags.
  2. Create a variable with the following information:
    • Variable Tag Name: TestInteger
    • I/O Device Name: IODev
    • Type: INT
    • Address: DB190,0

Troubleshooting your S7 connection

Question: I receive the following error message when downloading the PC station in the SIMATIC NCM PC manager:

  • "The module "station manager" cannot be contacted. Change the on-line interface."
  • "For On-line connections via the PC internal interface a station name must be assigned in the component configurator. This name must be identical to the name of the PC station, as configured in the STEP7 (or Simatic Net) project."
  • "Online: No connection could be made. The participant does not announce itself."

Solution

  1. Check in SIMATIC NCM PC Manager under the Menu option Options | Set PG/PC Interface, whether the point of entrance S7ONLINE is linked with the PC internal (local) interface.
  2. The Station Configuration Editor tells you whether your module is Online. You can start the Station Configuration Editor by double-clicking the icon. This should not be OFFLINE, so to change its mode of operation, click Change Mode. The mode of operation should now change to ONLINE.
  3. Check the station name in the Station Configuration Editor. This must match with the name in SIMATIC NCM PC Manager. You can change the station name in the Station Configuration Editor by clicking Station Name.
  4. Open the Station Configuration Editor and the SIMATIC NCM PC Manager. Check the order and the number of configured components and the indexes that are used. These should match.

The Logix5000 Essential Manuals

The Allen Bradley Logix5000 family (ControlLogix, CompactLogix, FlexLogix, SoftLogix) has some very good manuals. If you are just starting out or need a refresher here are the key manuals and the order I would read them. If you have RSLogix 50000 installed then you will find some of these in the Help > Online Books menu. Revision 16 also has some great videos in the Learning Center.

The Basics

For starters there is the Quick Start manual.
manual Logix5000 Controllers Quick Start

If you don't deal with the PLCs or RSLogix 5000 too much and just need a quick reminder about the hardware or programming then the System Reference is perfect.
manual Logix5000 Controllers System Reference

The Essentials

If you are getting into programming and designing a system then you'll want to start off with the Common Procedure Manual. It has a lot of helpful examples dealing with all aspects of the system.
manual Logix5000 Controllers Common Procedures Programming Manual

Next comes the nitty gritty of each instruction. It's a good idea to at least peruse all the instructions so you have an idea of what is available.
manual Logix5000 Controllers General Instructions Reference Manual
manual Logix5000 Process Control and Drives Instructions Reference Manual
manual Logix5000 Controllers Motion Instructions
manual GuardLogix Safety Application Instruction Set Reference Manual

An often overlooked manual but filled with great information for getting the most out your designs is the Design Considerations Reference Manual. Certainly a must read if you are knee deep in the development and programming of Allen Bradley PLCs.
manual Logix5000 Controllers Design Considerations Reference Manual

Hardware Specifics

Specifics for the hardware can be found in the User Manuals and Installation Instructions for the PLC.

ControlLogix
manual ControlLogix System User Manual
manual ControlLogix Installation Instructions
manual ControlLogix Controller and Memory Board Installation Instructions

CompactLogix
manual CompactLogix System User Manual
manual CompactLogix 1769-L31 Installation Instructions
manual CompactLogix 1769-L32E, 1769-L35E Installation Instructions
manual CompactLogix 1769-L32E, 1769-L35E Installation Instructions
manual CompactLogix 1769-L32C, 1769-L35CR Installation Instructions

FlexLogix
manual FlexLogix System User Manual
manual FlexLogix Controllers Installation Instructions

SoftLogix
manual SoftLogix System User Manual
manual SoftLogix Controllers Installation Instructions

GuardLogix
manual GuardLogix Controllers User Manual
manual GuardLogix Controllers Installation Instructions

Networking

If you are deciding on which network to use then see the Design Considerations manual and the section "Determine the Appropriate Network". Otherwise, for existing networks the following are helpful.

Ethernet/IP
manual Ethernet Design Considerations for Control System Networks
manual EtherNet/IP Modules in Logix5000 Control Systems User Manual
manual Guard I/O EtherNet/IP Safety Modules User Manual

ControlNet
manual ControlNet Modules in Logix5000 Control Systems

DeviceNet
manual DeviceNet Modules in Logix5000 Control Systems User Manual
manual Guard I/O DeviceNet Safety Modules

The links are from the AB site so they are the latest and greatest manuals. Let me know if any of them are broken or if I forgot one you think is essential.

A Quick Tutorial on RSLogix Emulator 5000

RSLogix Emulator 5000 is a software simulator for the Allen Bradley line of Logix 5000 controllers (ControlLogix®, CompactLogix®, FlexLogix®, SoftLogix5800® and DriveLogix®). The goal is to mimic the function of a PLC without the actual hardware and thus do advanced debugging. More information can be found in the AB publication LGEM5K-GR015A-EN-P.

As a quick introduction we’ll go through a simple example of setting up a simulation. This involves three major steps.

  1. Setting up the chassis monitor.
  2. Creating a connection in RSLinx.
  3. Creating a project with associated emulation hardware.

Setting up the Chassis Monitor

To start the Chassis Monitor, click Start > Programs > Rockwell Software > RSLogixEmulate 5000 > RSLogix Emulate 5000 Chassis Monitor.

RSEmulator 00 Open
When the emulator opens up you’re confronted with what looks like an empty chassis. In slot 0 is an RSLinx module which has to be there for the emulator communications to work. Your slot 1 might have another irremovable RSLinx module depending if you are running RSLogix Enterprise.
RSEmulator 01 - Empty Chassis Monitor

From here we set up our hardware configuration for simulation. Our first step will be to add the CPU. In this case it is a special one called an Emulation Controller.

  1. Click Slot > Create Module.
  2. Choose the Emulator RSLogix Emulate 5000 Controller.
  3. Chose slot 2 for the controller
  4. Click OK to add it to the chassis monitor.
    RSEmulator 02 Select Emulator Controller
  5. At this point you may be accosted with a message about previous configurations. Just select Reset the Configuration to Default Values and click NEXT.
  6. The next two dialog screens are for setting up the controller details. Click NEXT and FINISH to accept all the defaults.
    RSEmulator 03 Emulator Controller Setup 1
    RSEmulator 04 Emulator Controller Setup 2

Next we’ll add some input/output simulation.

  1. Click Slot > Create Module.
  2. Choose the 1789-SIM 32 Point Input/Output Simulator.
  3. Chose slot 3 for the simulator and click OK.
    RSEmulator 05 Select Input Simulator
  4. Accept the defaults for the setup by clicking NEXT and FINISH.
    RSEmulator 06 Input Simulator Setup 1
    RSEmulator 07 Input Simulator Setup 2

The chassis monitor will now have two emulation modules in it ready to go.

RSEmulator 08 Full Chassis


Creating a connection in RSLinx

  1. Start RSLinx under Start > Programs > Rockwell Software > RSLinx > RSLinx Classic
  2. Click Communications > Configure Drivers.
  3. Select the Virtual Backplane (SoftLogix 58xx) driver from the Available Driver Types list.
  4. Click Add New. The Add New RSLinx Driver dialog box appears. Click OK.
  5. The new driver appears in the Configured Drivers list. Click Close.
RSEmulator 09 Create Driver

Using RSLogix Emulator in a Project

To use the emulator in a project you must setup the hardware correctly.

  1. Start the RSLogix 5000 software and create a new project.
  2. Under the New Controller window type select an Emulator – RSLogix Emulator 5000 Controller. Give it a name and assign it to the same slot as the one you put in the Chassis Monitor which in our example is slot 2. Click OK.
    RSEmulator 10 Setup Processor
  3. In RSLogix 5000's Controller Organizer, right click on the I/O Configuration folder, and then click New Module. The software displays the Select Module window.
  4. Open the Other folder. Select the 1756-MODULE from the modules list and then click OK.
    RSEmulator 11 Setup Simulator Card
  5. The software displays the New Module window.
    a. Add a Name for the card.
    b. In the Slot field put the number that corresponds with the Chassis Monitor.
    c. For the Connection Parameters put in the following and click OK
    Assembly Instance Size
    Input 1 2
    Output 2 1
    Configuration 16 0
    RSEmulator 12 Setup Simulator Card Setup 1
  6. On the next Module Properties screen make sure to change the Requested Packet Interval to 50.0 ms.
    RSEmulator 13 Setup Simulator Card Setup 2

Ready, Set, Go

You are now ready to use the emulator just like you would any other PLC. Open Who Active and set the path to the RSLogix 5000 Emulator.
RSEmulator 14 Connecting
The inputs can be simulated in the emulator’s Chassis Monitor by right clicking on the module and selecting Properties. Under the I/O Data tab is the ability to toggle each of the inputs on or off.
RSEmulator 15 Simulating

Note:
RSLogix Emulator is sometimes erroneously called RSEmulator.

Factory Tours

I love factory tours especially if they're personal ones. There's just something about seeing automation in action that's just cool.

Lego Factory Tour

I got started on a little factory tour information internet romp after watching this cool flash video about the Lego factory. I love Legos so seeing it in automation is a bit of double your pleasure. If you're a Lego fanatic and in Denmark then you might actually get an inside tour. I have no plans so you'll have to tell me about it.

There's a book called Watch It Made in the USA which is a guide to visit nearly 300 factories and company museums across the U.S.A. So you could plan your whole family vacation around factory tours. Yeah right, if you could just get the kids to agree to that. Tongue out The book is very well done but if you just want a quick run down of some local factories you can try the Factory Tours USA website.

Here's a list of one's that sound fun and interesting to me.

  • Boeing (Everett, WA) - I've actually been on this tour and would love to go again. Absolutely worth it.
  • Jelly Belly (Fairfield, CA) - Oh these jelly beans have amazing different flavors. It'd be great to be up to your armpits in them.
  • Ben and Jerrys (Waterbury, VT) - Another one of my favorites: Ice Cream!
  • Taylor Guitars (El Cajon, CA) - I play guitar so this would be awesome.
  • Toyota (Georgetown, KY) - Any automobile manufacturing is cool.
  • Crayola (Easton, PA) - Now here's one the kids could get into especially if they are Sesame Street age.
  • Celestial Seasonings (Boulder, CO) - I dunno, it just sounds so comforting.

I'm sure there's a lot more. If you have any suggestions then add a new comment.

#