ElectronGuru

Since the PowerFlex 755 has Ethernet embedded in the MCB (port 13) why do you have and Ethernet card installed at port 5? I'd remove that card from your drive. I assume you already have the PF755 AOP downloaded to the laptop that the Studio 5000 project is on. Also, delete any previously attempted drive install from the I/O tree. The easiest way to add a drive to the I/O configuration of a controller is to use the module discovery feature. Make sure the controller and drive are powered up and connected to the network. Go online with the controller with Studio 5000. Right-click on the I/O tree Ethernet icon and click Discover Modules, which opens the Select Module box. Add the PowerFlex drive. You'll have to give it a name. Click upload. Choose the drive from RSLinx and upload the drive with all DPI ports. When the progress bar has completed, click OK. From the New Module box click Create. Close the Select Module box. The drive is added and you'll find that a few dozen of its status and command parameters have been added to the controller's tag list.

In FTME you could possibly you use the recipe function, which writes values to tags. You have a "data set" (values) that you write to a "tag set" (controller tags). Up to ten data sets can be paired with a single tag set. A "unit" is the data set(s) paired to a tag set. If you have more than ten test conditions, create more units. Once you set it up, simply pushing an HMI button on the recipe display writes the pre-defined values to the controller tags for the specific test you're running. You can also set it up to be editable at run time, or lock out run time edits if needed.

Like most software producers, Rockwell divides its firmware into major and minor revisions. So FW Rev 32. 003 would be spoken as "32 dot 3", where 32 is the major rev and 3 is the minor. Major revs are usually adding or changing functionality, such as adding program parameters in V28. Minor revs are usually fixing known anomalies. Newer major firmware usually has more functionality but yes, you may discover a new bug here and there. However, Rockwell is pretty good about documenting known problems in the release notes. Always read the release notes when you want to know what something will or won't do.

Check your initial graphics setting and FTLinx communications again, and try the Test Application again. Unfortunately, both ME and SE can be pretty touchy and you just have to stay at it until you get what you're looking for out of the ME runtime application.

@VFD Guy thanks for the feedback. I had been been fighting with the darn thing and had figured it out, but then a colleague found a KB article that clearly defined what I learned in the school or hard knocks. In CCW V22... Download is an all or nothing event. It downloads to all ports and does not prompt to go online. Synch allows you to download to specific DPI ports but does not prompt you to go online. Connect; Will allow you to connect directly if all ports & parameters match. If there's difference, it asks you if you want to use the project or device parameter values. Downloads / uploads in accordance with your selection (which allows for DPI specific downloads). Then connects to the drive. They define Connect as the preferred method. Here's a link to the KB article but login is required. https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/1092740

Not a double post! Just upgraded from V10 to V22 of Connected Components Workbench. In V10 you can go to an Advanced window and upload/download to a single DPI port within a drive. For example, if you loose an output on an extended I/O module, you can replace the module and download to only that module. Have they taken that away, or is it just hidden somewhere? CCW will not let me download to the drive unless I manually put the Safe Speed Monitor module in program mode. I tried removing the module from the Device Definition and it still hangs up on the safety card. Also trying to get my head wrapped around the whole "Synchronize" thing. Any pointers would be appreciated but it seems the only purpose it serves is to upload current drive values into the offline file.

I did that and I'm having better luck at getting something to show up in the desired folder. However, I started a brand new project with a brand new drive and when I clicked Save, it saved the project to the folder and they gave an error box that says, "Unable to save the project located at: path to the default folder". Well, no kidding. I didn't want to save at the default folder. However, the main problem is that if I edit an existing file, it will not save the changes. Edit; After another hour of messing around with it, I've found that the issue only occurs on projects that were save in the previous version on the laptop. (I upgrade from V10). If I create a new project from scratch, everything works as you'd expect. But any pre-existing V10 projects I open, I can't make and save edits or I get the above described problems. Nothing on this in Rockwell Knowledgebase.

Anyone have any experience with CCW V22. Every time I open a project, it prompts me to save to the original location. Fine, that's not really a problem. When I make an edit and click Save, it tries to save to OneDrive no matter where I point it on the local laptop. If I click OK on the OneDrive location, it says the file and destination names are too long. I disabled OneDrive, created a dummy folder on my desktop, and when I try to Save As two things happen: After saving in the dummy file, a second save dialog box appears prompting me to save to the original OneDrive file location. When I open the newly save project in the dummy folder, none of the edits were saved. Unfortunately, the CCW Help contains no information on drives and the section on saving gives directions as though you're trying to save a Word document. And as I've described above, that does not work. Searched Rockwell KB and so far have come up with nothing.

Unlike SE, ME is made to run on a PanelView station, so there is no client that can be run at your programming terminal. In ME, creating a runtime file creates the .MER (Machine Edition Run file) that you're going to download to the PanelView. You create/program the project in a .MED (Machine Edition Design) file. From the open .MED, "Test Application" (the little running person icon on the tool bar" is the SE equivalent of launching a client on the programming terminal. It creates and launches a temporary .MER on your programming terminal that is fully interactive with the controller and itself. (The Test Display feature is only interactive with the controller. For instance, you can't navigate from one display to another in Test Display). @Joe E. is correct; it did launch and hitting the escape or typing an X on your keyboard will shut down the temporary .MED application. It's showing the display that is set to be the initial graphic, and following the above advice (System >Startup >Initial graphic displays) and switching to the display you want shown on powerup/launch should solve your problem.

I believe that any downloads or safety edits to a safety project/controller require it be unlocked. I've been so spoiled for so long with Professional & Developer editions, I'm really not sure of specific limitations on Standard. However, I'm pretty sure you'll have to obtain a GuardLogix add-on license to lock and unlock the controller.

I assume the new module you've added is not part of the safety system. If you're able to access, add, and modify non-safety features of a safety project with a Standard license, the safety features in that project should remain in tact after your download. That said, certified safety controllers must be safety locked and have a safety signature to be SIL/PL rated. Be sure that while you're editing offline that you do not delete the project's safety signature, or edit/delete the safety network number (SNN). The controller will have to be safety unlocked prior to download, and the safety signatures of the controller and the offline project must match or you will not be allowed to download. Once you've completed the download, safety lock the controller to preserve the SIL/PL rating. Hope this helps.

While I have no direct experience with using S:5/11, I do have a lot of experience using data table bits in code. Sometimes controllers act goofy when they're in a non-normal state, like the battery being removed. The flickering bit could be a result of that. I'd experiment with monitoring the bit (perhaps even using a histogram, if possible) with a known good battery, no battery, and a battery you know to be well below acceptable voltage. Once you have compiled that data you'll know better how to use the bit in logic. After that, it's just matter of putting the bit on an XIC or XIO, latching in an OTL, and deciding if you need a time delay between the two.

Output objects in FT have a "hold time" feature that allows any given button on a display to send a signal to the PLC continuously for the hold period. I don't think that feature exists for VBA code and if it does, someone who knows a lot more about VBA than me will have help us. In the property panel for your numeric display there is a "Expose to VBA" box with two options: "Type Info Extension", where the properties of the object are displayed and accessible, but the events are not, and "VBA Control" where the properties and events of the object are displayed and accessible. While I don't see that you're using an event in your VB code, you could try changing the Expose setting to see if it helps. Based on what you've said, I think it's sending the signal successfully but for one scan only. If this is the case, you're like going to have to write code in the PLC to latch in the receipt of that signal for three seconds. Hope this helps.

Way back in the SCL500 days, a math overflow status flag would cause a major recoverable fault in the controller. This was in a rubber mill where fork trucks would back up into sensors and no matter how much you beefed up the guard, they'd just back up harder. The damaged sensor would put some bad data to the input module, the scaling instruction looking at the input channel would produce an overflow, the overflow flag would be set, and the controller would fault out in the middle of a mix. Then we'd spend the next 8 hours cleaning out the machine. One of the tricks we used to avoid this was to put the status flag S:V on an unconditional OTU instruction directly below the rung that was prone to causing the overflow. We'd also have to write some code to catch and annunciate the problem, let the current batch finish mixing, but inhibit the next batch from starting. I hadn't thought about this in years until it came up this weekend. I tried to use S:V/OTU to unlatch the overflow bit in an L7 controller using V32 and you guessed it (or already knew) it doesn't do that any more, lol. It appears the only way in 5000 is to interlace some buffer code to detect the overflow and move a non-zero number to the math instruction destination before the status flag sets. My question is; Is it now impossible to unlatch a math/system status flag through logic like in the the 500s, or is that option completely off the table in Studio 5000?

In SLC, the source is multiplied by the rate you specify. The result is added to the offset and sent to the destination. To try to solve you're first one; SCL1 Rate 25,000/10,000=2.5 (Rate)2.5X(Zero)4 = 10 +(offset)-2,500 = -2490 (Rate)2.5X(Span)20=50 +(offset)-2500 =-2450 It appears your range is 4-20 = -2490 to -2450 But it's nearly 2am, I'm falling asleep at my desk, and I probably screwed up something. Probably best you open the project and click on instruction help. That said, these are some typical calculations used for figuring out a linear relationship: Scaled value = (input value x rate) + offset Rate = (scaled max. - scaled min.) / (input max. - input min.) Offset = scaled minimum - (input minimum x rate)