ElectronGuru

Is that code on the flow meter or the controller's input card? It's been a minute since I've worked with Rosemount transmitters but I seem to recall they give their errors in whole words, such as, "out of range" or "coil overcurrent". But like I said, I'm a bit rusty there.  If the error code you're talking about is on the input card, it should probably read something like "16#0009". If that is the code you're getting on the input card, you have an invalid card or channel configuration, and you'll have to fix that through Studio5000.  Any more details you can provide will be helpful in getting this fixed.

While @BobLfoot is right, here's an over-generalized stab at it. I downloaded and tested on a 1756-5573, using V32. It works to count and record the parts over five-minute intervals.     Five Minute Part Counter.pdf

OLE is Object Linking and Embedding, which is used to link embedded objects from multiple applications. OPC is OLE for process control, so kind of like an acronym within an acronym. Core components of OPC are necessary for all classic OPC applications. It's a pain in the butt, but you need one (the correct OPC) installed for the other (CCW or other OPC dependent applications) to work so you can access all your graphics and such within the application. This is an over-simplified explanation, but hopefully it has given you an idea of why you're getting this install error.  Your error code says you're using V0, which I've never heard of and makes me wonder if you have OPC core components installed at all. The attached release notes for CCW V13 (like your error code) says you need V3.0. (Page 6): https://literature.rockwellautomation.com/idc/groups/literature/documents/rn/cc-rn001_-en-p.pdf The link below should allow you to download what you need. You will have to become an OPC Foundation member, which usually only requires a valid email address. https://opcfoundation.org/developer-tools/samples-and-tools-classic/core-components/ I believe there are other places on the web you can download this, as well, if you prefer. Once the OPC is downloaded and installed, CCW should start working for you. 

@Michael Lloydout of curiosity I looked up and read the book description on MVM and I don't think the description is wrong, so much as poorly written. It specifically states that the picture shows the instruction before execution. To my way of thinking, they should show a before and after, but that's why it kind of misleads a person about where the 1s and 0s should be.

@chelton that's an excellent point. Thanks for bringing it up and showing a great example. Since the mask value 0 filters out source data from getting to the destination, the masked destination bits would remain unchanged after the MVM execution because the 0s are blocking any source data (0 or 1) from being written to those destination bits. This is just one more reason the MVM instruction isn't used that often.  @JesusRCh I believe I miss-spoke myself regarding filtering out decimal places using MVM. When I worked in a power plant we used a lot of 16 bit transmitters to monitor things like oxygen levels, airflow, differential pressure, etc. Eight bits were the value of what was being measured (% of O-2, cubic feet of airflow per minute, etc) and eight bits were the status of the instrument, itself (run mode, calibration mode, alarm, etc). When moving something like the airflow data to an operator's view (like a DAQ station or LED display), we would use MVM to mask out the status bits. This would keep the display from showing extraneous data or outright gibberish. I had incorrectly remembered this as filtering out decimal places and spoke without thinking. Sorry 'bout that.  At any rate, with the addition of Chelton's example above and the fact that we've both shown MVM is pretty limited, it's not likely an instruction you're going to run across often. 

MVM is rarely used but it does not work the way @Michael Lloyd described. Quite irritating when the book is wrong. Here's what's happening: Source is the original data Destination is where you want it to go Mask is like a coffee filter that the original, raw data passes through to remove what you don't want it gets to the Destination. To be clear, in the Mask, 1s are true and allow data to pass; 0s are false and do not allow data to pass. In the example mentioned above, if the original word value of 01010101 (170 decimal) is passing through a mask of 11110000 (15 decimal), then the data at the Destination would be 01010000 (10 decimal).This works whether moving data from one array to another, or moving data around in real-world IO. I've attached three screen shots showing the tag monitor that proves this out on 1756-L7 controller using V32. I'm using Copy_Dummy[8] as the Source, Copy_Dummy[9] as the Mask, and Destination_dummy[0] as the Destination.  As for the OP's question, you can use this instruction to conditionally ignore certain digital data, like inputs on a, IO card, or to filter out unwanted decimal places in analog data, etc. However, there are a hundred other ways this can be done so like I mentioned above, you won't see this instruction very often. Hope this helps.   MVM Example.pdf

I can't find the ESD version in the Rockwell PCDC but if you're seeing it as an option, try downloading the release note for both editions. Any differences should be clear when comparing the release notes side-by-side. Also, you could just ask the distributor. Is there a price difference?

Use an XIC instruction with the pushbutton tag. Use a CTU instruction to count the number of times the button is pushed. Use a TON with XIO to set the 5 minute intervals. The counter is retentive and therefore will need something to reset it at some point. You may also want to put something on the rung between the pushbutton and counter to prevent false counts if the operator pushes the button during the timing interval.  I've attached a Word doc with a template that should help you get started. Hope this helps.   Try this.docx

You'll likely have to create a subroutine in the controller that MOVs the recipe being run into a tag with data type STRING, then read that tag in the HMI on a String Display. I once tried to do this with an HMI tag, but couldn't figure out how to make it work. 

Typing the AB device's IP address into the address field of any browser should pull up the AB device's web page. Some devices will require that the web pages feature be enabled. When you do this, you'll only get the details (firmware, configuration, diagnostics, etc) for that IP device. So you'd get the info for a ethernet card in a ControlLogix chassis, but not the controller card, itself. From the web page of the device with the IP address, you should then be able to browse the chassis and get the same info for each individual device. 

If you're using version 28 or higher of Studio5000, you can use parameters instead of tags. While you would still have to copy and paste them from one program to another, they are editable online in the run mode, and therefore much more flexible. Instead of scoping a local tag with an alias to an output, I create an output parameter of the data-type BOOL, and give a "connection" to the I/O point. If I ever need to, I can change that connection while online and in the run mode. 

V21 is when they changed from RSLogix 5000 to Studio 5000. I believe that all ControlLogix L6 and below controllers are hard-stopped at V20, and there are only a handful of L7s that will dip down to V19. Use Rockwell's Product Compatibility & Download Center (PCDC, link is below) to determine what you can flash your controller to, but make sure you have that version of Logix or Studio available on your laptop. You'll need it to upgrade the existing stored project to the same level as the newly flashed controller, and then download to that controller. https://compatibility.rockwellautomation.com/Pages/MultiProductSelector.aspx?crumb=111

I just now quickly glanced at V17, 18 and 19 release notes and didn't see anything that jumped off the page as the filter being a new feature. I currently only have V28 through 32 installed on my laptop, so I can't dig around and find where to activate that feature. In the versions I have, it doesn't appear that the search filter can be toggled on or off. If it could be, I would expect it to be under Tools, Options, which is where you should start looking if you haven't already. You might also check under the View tab. It's kind of a silly placebo, but have you tried closing and re-opening the project to see if it shows back up?  Anyone else have any thoughts or solutions on this?

Is V16 the one that's not showing the search filter? Have you seen that search filter in that project before?

You appear to have different versions in the two images. The one appears to be V28-ish; the bottom one is definitely an older version. I looked around in my V28 and V32 and can't find anything to toggle that filter on and off. Check the versions and their release notes to see when they added that filter. I'd be curious myself to know if that can be turned on and off.

Program Mode is used to download projects to the controller or to have easier time of making online edits. The controller is in Program when the controller's is key/toggle switch is place in PROG, or when placed in Program from the online tool bar in Studio if the key/toggle is in Rem.  Many output cards have the feature you've shown that allows analog cards to go to zero, hold last state according to code scan, or go to a user-defined value, and for digital outputs to turn outputs on, off, or hold last state. 

Have you auto-tuned the drive? If not, try doing a speed tune (parameter 1027) and see if that helps. I have seen loose motor or encoder wires, damaged or misaligned encoder couplings, etc. cause issues with responses to changes in speed reference. Also, incorrect values on encoder and motor nameplate parameters can cause speed control problems. Do you get the problem on decel commands, as well? You have relatively long accel/decel times (50/45 secs) but your S-curves are on the default settings. If you're driving a high-inertia load, overshooting the commanded speed reference might be expected without some S-curve added.

That's quite a tale and I can't wait to hear how (and if) you're able to get it solved.  Since this works on some drives and not others, my first inclination would be to run online compare tools in CCW or Drive Executive to see what differences there are in firmware, I/O configurations, and parameter settings. For me personally, I've found that encoders can cause a lot of issues when running test modes such as what you described above, especially if the encoders are set to quad check. Maybe start there from within the compare tool(s)?  

The alarm description you're getting " Fallada eix arrastr" according to Google Translate is "Drag Axis Failure", which I can't find in the Fault/Alarm Descriptions in the manual (Publication 20D-PM001D-EN-P - March 2019). @VFD Guy is correct that to better help you solve this, we could really use the exact numeric alarm code. Whether you're using an A3 or A6 HIM, you should be able to use the HIM to navigate to the Alarms section, follow @VFD Guy's suggestion of deleting the alarm que, and see what alarm then shows up. The yellow flashing STS light on the front of the drive indicates a Type 2 alarm, meaning you're not going to start that drive until you find and remove the condition causing the flashing light. Going back to your original post, you said that, " an alarm condition exist (run inhibit stat) bit 1 is true ( no enable)". I assume you're looking at parameter 156, "Start Inhibits". When bit 1 is true the book instructs us that there is "no enable" as seen by the drive. Sometimes inputs fail and the drive can't see that the 24 volts is present at a terminal block. If I were there in your facility, I would immediately look to see which digital input is programmed as Enable, then go look at the digital input status parameter to see if that bit is true when 24 volts is applied at the correct terminal block. There are cases where drive peripherals can cause an inhibit that manifests itself as a "drive not enabled" alarm condition. For example, if you have a Safe Speed Monitor card installed and someone placed that SSM in Program Mode, the drive would be disabled, you'd have a yellow light, and no other indication as to what's causing the start inhibit. Program Mode in an SSM card is logically in series with Drive Enable, but there's nothing in the HIM, drive parameters, or Alarm que that would indicate this is the issue. That said, I started a Connected Components Workbench project and added a PowerFlex 700S drive to it and I don't see that SSM is an available option for that drive, but I'm using V10 (V13 is the most current) so I might not have the latest available info. The other thing that concerns me is you said this is not a new installation, which leads me to believe that this was working for a period of time, then stopped. Which, in turn, always leads me to the same question; what changed? Did someone change a parameter setting? The easiest way to check this is to get on line with the drive using CCW and check the "Show Non-Defaults" to see what has changed from factory settings. (I can't remember if the A3 HIM has this feature but the A6 does. @VFD Guy, do you know if there's a changed parameters feature on the A3?) If used as a drive enable, did the digital input burn out? As mentioned above, find out where digin for enable is programmed, and check that the drive sees that bit go true when 24VDC is applied. Is there a peripheral somewhere that is holding the drive in "not enabled"? Is there a 20-COM card, or any other extras installed on the drive that might be causing the issue? Start with easiest stuff first, and work your way through it. 

@VFD GuyExactly. That’s for the hair splitting elaboration. 

My mistake; it appears to only be the PowerFlex 70 that requires digital input 6 to be the drive enable input. 

Is this a new installation, or one with recent changes made to it? Or is this something that was working and then stopped? Assuming it may be a new installation, some of the PowerFlex 7- series drives require the Enable to be wired to terminal 6. If your safety/enable circuit is wired to a different terminal, you could be inhibited even though the circuit is true.

Sounds like you found it. Each family of I/O cards have their own options, all with similarities and differences. The 1756 analog output diagnostic cards have a feature that lets you ramp to the user defined value in fault mode. The 1768 input cards have output files that aren't even described in the manuals. Sometimes we just have to muscle though it with trial and error to what works. 

@pcmccartney1 yeah, I misread the OP, as well. And unfortunately, I'm not well versed in View, either. I'm more of an ME guy and live primarily in FT Studio.

Gotchya, and sorry for the misunderstanding. @Joe E. and @pcmccartney1 have given good advice above. Be careful about getting too low on the display update rate because it can take up a lot bandwidth on your network.