This part 2 of 2 How-To video will show you how easy it is to power up and connect up the Productivity3000. The easy setup and configuration of the Productivity3000 will help you be more productive. With no power budget restrictions and no module location restrictions, the Productivity3000 stands out from other programmable controllers.
Legacy Video Sequence Number: L-PC-P3K-003
Okay, in part one we powered up the system. Now, we’ve connected the communications cable between our PC and our Productivity3000 Programmable Automation Controller. We’re now ready to use the programming software which we already downloaded and installed on this PC. Now, in this video we’ll connect up the CPU, auto-discover all the hardware, and create a couple simple programs. I should mention, that all of our devices – the P3000, the C-more, and the GS-drive e-drive module all require some minor Ethernet configuration that needs to be completed in order to get them all talking to each other. We’ll cover this in more detail in future videos. Here, we’re connected to our P3000 system. You can see by opening the hardware configuration dialog under the set up>> application tools>> and clicking on the reconfiguration after a few seconds all of the attached I/O modules in any other hardware is recognized. Now, keep in mind that the CPU needs to be in the stop mode when reading the hardware configuration. Here, we see the GS2 AC drive that we’ve attached via the Ethernet Remote I/O connection is also recognized. In our real world connections I've got a limit switch that detects if the assembly machines safety guard is on. In most cases, we want to shut down the machine, and if this happens, we want to turn on an indicator light that alerts the operator of the machines condition. We’ll call this limit switch our safety guard open signal. I use the limit switches normally closed contact prior to our first DC input module. I've chosen the normally closed contacts so the circuit is complete when the switch is not being actuated by the guard. Think of it as what we want to have happen if the switch were accidentally removed from the machine. I've also wired a stacklight that will give a visual warning of the machine error. I’ve wired the stacklight to our first DC output module. Now, watch how simple it is to program the code for these I/O points and create a working ladder example. I start a new task and insert a normally open contact on my first rung. I need to assign an address so I use the browse icon and the normally open contact dialog box to scroll down to input DI zero one one one. This is the address for the first input on the 16-ND3 input module. Next, I'll drag and drop an output coil on the far-right of the same rung. I’ll use the dialog’s browse icon to scroll down and locate output DO zero one three one. This is the address for the first output on the 16-TD1 output module. From the tag database utility I'll rename our input to read safety guard open. I’ll also rename our output to read guard open warning. Using a tag name to describe our signals will make it so much easier to later understand and troubleshoot the program. Let's see if it works? Success, it works. Next, we’ll program the P3000 to control the GS2 AC motor drive from our C-more touch panel. The P3000 software has a large number of built-in instructions. One group contains the communications instructions and in this group are the instructions that allow us to read and write data directly to our attached GS Drive. In our situation, we want to control the AC motor from our C-more touch panel which requires the ability to write information to the drive. Here, we insert a GS Drives write instruction into our program from the communications instructions group. Next, we select the GS drive node number that is setup on the GS e-drive modules dip switches. Keep in mind that we are able to auto-discover the GS Drive when we did our hardware configuration. So, it should be available in the pull down list. Watch as I create tag names for the various parameters within the instructions box. I can keep this as simple as creating frequency reference tag names for both the run and the jog commands within the auto write section and a few other tag names. I’ll use the tag names run freq and jog freq for our drive running and jogging frequencies. For our example we’ll keep the default polling times as shown. Although, the status bits shown here are optional we’ll go ahead and add them for our demonstration. The status bits are very useful if troubleshooting is required. We also have an entire section of parameters in the manual writes section in the GS Drives write instruction that we can control both when the drive is running and also when it is stopped. We will show the uses of controlling these parameters in future videos. Now, click okay to insert the GS Drives write instruction. A define tags dialog box will appear showing the various tag names that we've just created. At this point, we could change some of the data types, but for our example we’ll just click okay to accept them as is. Next, we need to add contact signals in order to control auto run and auto jog inputs to the GS Drives’ write instruction. We’ll use the tags named auto run and jog run to keep our example simple. Again, as we insert each contact you see the defined tags dialog box come up. So, just click okay to accept. Since we won’t be changing any of the drives parameters we won't need to do anything with the run mode data or stop mode data inputs to the instruction box. Once we’ve completed our program we’ll export the tag name database as a CSV file. Make sure to check the include I/O tags box in the dialog box so that our I/O tag name database is included. We're creating this file that will allow us to import all the tag names into the C-more programming software. Which will save us from having to retype all the tag names again in the C-more program. We’ll now compile our project to check for errors, then transfer our completed project to the P3000 CPU. We now open the C-more programming software and start a new project. Make sure you’ve selected the AutomationDirect Productivity3000 Ethernet PLC protocol. Import the tag name database file that was created and create a numeric entry object that will allow us to change the GS2 drives’ frequency. We’ll select the imported tag name rung freq. Next, add a maintained pushbutton that will allow us to start and stop the drive. Use the imported auto run tag name for the pushbutton. We could have also added objects for the auto jog and frequency functions at this time but we’ll try to keep our demonstration simple. We’ve now completed programming P3000 so we can control the GS2 AC Drive from our C-more touch panel. We first enter the frequency that we want the drive to run at using the C-more’s numeric entry object with a tag name rung freq. Next, we press the auto run pushbutton that we created on the C-more touch panel that will enable the GS Drive to run in the auto mode. As you can see the AC motor connected to the drive ramps up to the frequency we’ve set. We’ll also cover how we did this simple example in more detail with later videos. This is the conclusion to our out of the box experience. We have our Productivity3000 system assembled, wired to a few real world I/O points, configured in the software, and a simple program created, and finally we showed you how quick communications can be set up with the GS AC motor drive and our C-more touch panel. Please follow some more Productivity3000 videos here at learn.automationdirect.com Thanks for watching. See you soon.