ElectronGuru

MrPLC Member
  • Content count

    358
  • Joined

  • Last visited

Everything posted by ElectronGuru

  1. FactoryTalk Studio Crashing

    @Joe E.That's what I'm running into. There's a knowledge base topic that covers this but it's for V6. And I'm in a situation where the company manages the VMs on my company-owned laptop, so your fix is somewhere between impractical and impossible. (Damned IT people, lol).  Out of frustration I decided to re-install V12. ME is fine but SE refuses to open any project that I haven't created brand new. All existing SE projects or those newly restored from .apa files opens FT SE Studio, but the project explorer window is blank. No server, no display files, no FactoryTalk Linx, no nothin'! I'm out of answers and have just started clicking and right-clicking any and every random thing trying to find ANYthing that will at least get me back to where I started.  I've reached out to a couple Rockwell developers (Rockwell employees who (among other things) write training curriculum) and waiting to see if they have a solution. If someone else has any ideas, please!, let's hear them. If I find the solution I'll be sure to post it.
  2. Panelview Panel + 7 900W Unable to connect

    There are some rare occasions when an old PV6 wont be able to interact with an L8 running V32 or V33. This is why I suggested double-checking product compatibility earlier.  Since you upgraded your firmware (and if you haven't already) you might try deleting are re-configuring your Design and Runtime shortcut paths in the communications setup. Also, I always like to test at least one or two displays from the FT Studio to make sure that the path is valid before I create the .mer.  If you've done all that, the next time you open the transfer tool, click on the Ethernet network icon and let the three boxes blink for at least ten or fifteen seconds. This will give Linx time to eliminate anything that it previously detected that it might not actually see at the moment. Many times I've clicked on the node too fast after opening the tool, only to find the node isn't actually where Linx can see it. This can be caused by anything from bad configurations to, an unplugged network cable, or (most embarrassingly) the power to the node being turned off.
  3. Panelview Panel + 7 900W Unable to connect

    From the image you posted it does look like you have selected a controller network port as the path, rather than the controller. Have you tried testing the application or individual displays from the laptop to ensure the Design path works? It is possible the PanelView is not compatible with that controller.
  4. Panelview Panel + 7 900W Unable to connect

    Did you copy the Design shortcut to the Runtime shortcut before creating the .mer?
  5. Powerflex 400 25HP wird amp behavior

    You were informed correctly; the PF400 is primarily designed for pumps and fans. There is no PF725 that I'm aware of. I think you might have meant to type 755. There is a PF525 but it is only rated up to 30HP. You mentioned that you were looking for torque options. The PF755 does have almost 20 torque parameters, while the PF400 only has one; Parameter 13 "Torque Current", which is a read-only parameter which displays the torque portion of the output current. It is important to note that with any AC motor there is an inverse relationship between torque and speed. Whether or not your system is set up as a torque (rather than speed) follower, it makes sense that you'd see amp fluctuations with changes in speed or load demand. This might be worse in the 400, which was designed to run best on a modified V/Hz curve for pumps and fans. 
  6. @Joe E. that's good work, man! I'd bet money that solves his issue!
  7. The first thing that jumped off the page at me is when I verified the project, all of the errors are due to the value "x.x.x" being in a BOOL datatype within the AOI parameters. I'm not sure what's causing this or what to do about it, but will continue to look around. Anyone else see anything like this somewhere and have a solution?
  8. Powerflex fault 315

    Not sure what drive you have but in the PF750 manual, 315 means "The absolute maximum Position Error value has been exceeded". This is a configurable alarm, which means the programmer gets to choose what happens when the condition occurs. The programmer felt that "fault" was the best option for your process. This is configured in the motion instructions in Logix, so it can't be addressed in the drive, itself. You'll have to look at controller's logic to determine what the max position is programmed to be, and why the drive is exceeding it.
  9. @Joe E. I'll have to ask my friend what version of Studio he was using and what controller. The e's may or may not be just an annoyance but the real question is, why the invalid expression error? My guess has always been that the AOI was modified off-line and then downloaded. If the problem is with the AOIs. it's almost certainly related to AOI tags or parameters because code errors are not allowed to be downloaded and as you said, AOIs can't be modified online.
  10. The  5069-L306ER will only go down to V29. The 1769-L16ER is compatible with V20 through V32. Flash the 1769 to match the 5069, then download your project.
  11. Ramp program for rslogix500

    @VFD Guy has asked a pretty valid question, which @BobLfoot eluded to; different drives treat accel ramp rate differently. If accel is set to ten seconds, some drives will take ten seconds for all speed changes, from current speed to new setpoint, while others assume a zero to setpoint, and scale the difference if the drive is already running.  Let us know how the RMP instruction works out for you.
  12. @Joe E. The first article you posted is dated Feb 2020 and is for RSLogix5000 (pre-V21). The OP's project is clearly written in Studio5000 V28 or earlier, so the article may be a valid resource for this. However, the E, e, I, i, R,r, and D designations have gone through many changes over the various Studio iterations, and as Rockwell instructor I know firsthand how challenging keeping at all straight can be. In my personal experience, on pre-V21 versions of Studio (and as I recall), as soon as you enter the online editing mode, the top line (the one that's being edited) automatically gets an "e' regardless of whether there are errors. The lower, duplicated line gets an "r". They change to upper case once the edits are accepted but not yet compiled/assembled. They changed the e and E to i and I in later versions. Pain in the butt. Regardless, I've always been trained by Rockwell that "e" means editing, which flies in the face of the article you posted. Go figure, lol.  For the OP's problem we're really down to two questions: Why are the "e"s there when he's clearly not in the online editing mode, and why has he got the invalid expression errors. I've bounced the first question off a couple of colleagues who both offered the same explanation; someone began an online edit to the controller and then logged off mid-edit without exiting the edit mode. The e's are now permanently in the code. My super-nerd friend who has a demo at home tested this replicated it exactly. The e's were ever-present after the mid-edit disconnect, and showed up on all subsequent re-connects and uploads. The only way he could get rid of them was to download the original project, overwriting the e's. To sum it up, the OP's code will likely have to be uploaded, corrected offline, saved, and downloaded to get rid of those non-online editing mode e's. Based on the above responses, I thing we're all on the same page about the expression errors. Something is wrong with his AOIs. I'm thinking it's tag related and he's just going to have to pour over it until he finds the issue. I hate how much of a non-answer that is but I/we don't have the code in front of us.  @Dimitry Stepanoffare you able/allowed to post the .acd here? 
  13. I agree and said in my first response that I think the AOI tags have been modified or deleted. Still waiting to hear back from the OP.  Very keen of you to catch the PC time stamps in the pics. Still doesn’t explain how he’s online and appears to be scanning code that’s also in edit mode. That’s the Big Mystery to me right now. 
  14. Exactly. So what are those “e”s doing there. Something is clearly amiss. 
  15. The lowercase “e”s mean that that line of code is being edited. Lower case “i”s mean the edits have been accepted (no errors) and are ready to be inserted. A bright green power rail does mean the controller is in the run mode. However, it does not mean that particular routine is being scanned, because it would have to be called by a JSR.  All that to say, yes, seeing the e’s next to a green power rail is definitely not the norm. I really wish I could be there in person to drive around in this one myself. 
  16. Just to review: An invalid expression error means there's an error in the syntax of the written expression. For example, if I were attempting get the mean average of three tag values using the CPT instruction I would write the following expression: "(Tag1 + Tag2 + Tag3) / 3". But what if I screwed it up and added an extra operand, like a multiply right next to an add: "(Tag1 +* Tag2 + Tag3) / 3". This expression now has an error, and the error description will be "invalid expression or tag". The same error would occur if I entered a tag that didn't exist, whether it's a tag that hasn't been created or one that has been deleted. As you know, errors can not be downloaded to the controller so this will have to be remedied. To try to begin to answer your questions: You uploaded the project from the controller, and are now finding these errors in the uploaded project? Or did the errors show up after modifications were made to the code? Seems to me like it would have to be the latter because offline errors don't download and online edited errors will not be allowed to be tested or replace existing code in the run mode.  If any instruction is missing its tag the error will be "Instruction has no arguments specified". If an instruction is missing other vital info (ie, no value written in the "Preset" field of a TON) the error will be "Missing operand or argument". My experience is this rule applies to AOIs, as well, but if anyone has more or different information on this I'd love to hear it. In the screenshot showing the AOI with zeros in the "External_Req", that line of code appears to be in the edit mode (lower case "e"s on the rung numbers) and I believe the 0s and ?s are the controllers way of telling you there's an error here. Any time you see a "?" in Rockwell code there's a problem. Due to the multiple decimal points, I'm wondering if that field is expecting to see data from a multi-dimension array. Or it could just be that's the default filler for missing tags/values in an AOI. I'd like to see the code for the AOI and play with before I said anything more specific. Since the AOIs seem to be the source of your issues, I would open their profiles to examine their tags, parameters, and logic. Chances are that tags not created in the AOI(s) profile were added to the code as part of the edit, or tags the AOI(s) depend upon were deleted during editing. Hopefully the original programmer left some descriptions in there for you to help understand how and why the AOIs are used, which will help a lot in rebuilding what's missing or corrupted. Hope this helps.
  17. Question About AB 2080-LC50-48AWB

    I don't think so but take a thorough read of the user manual to be sure. https://literature.rockwellautomation.com/idc/groups/literature/documents/um/2080-um002_-en-e.pdf
  18. @pcmccartney1 if an IGBT was blown he'd almost certainly be getting faults. Not impossible to not have faults in that condition, but extremely unlikely, particularly with a PF753. The suggestions made above would lead the OP to that, if that's the condition causing his problems.
  19. First off, get rid of that antiquated Drive Explorer tool and install Rockwell's free Connected Components Workbench (CCW). It's a far better and more user friendly drives tool, with many more features. And did I mention it's FREE? It sounds like you're using a hard-wired 0-10VDC analog signal in for speed reference, and that you've at least put meter leads on the terminal blocks to verify it's not the wires. I will further assume that you've checked the for the obvious things like loose connections at the terminal blocks, particularly with any feedback devices, such as an encoder (if used). @alan_505 has set you down the right path to start with and the results you get from that check will determine what to do next. If parameter 2 shows an incoming speed reference at or very close to 0 regardless of the voltage on the terminal block, check parameter 545 (Speed Ref A Sel) to make sure the drive is looking at the correct analog input. If it's not, fix it. If it is correct, remember that voltage on the terminal block doesn't automatically mean the drive can see that signal. Go to the analog input parameter (255 for the main control board, 54 & 64 for the 24v extended I/O card analog inputs) to view the raw data coming into the drive. If that's not changing to match what the multimeter says, your analog input channel is likely bad. If parameter 2 shows an incoming speed reference that closely matches the actual input at the terminal blocks, check parameters 935 and 936, Drive Status 1 & 2. These are bit parameters that tell you at a glance what the drive thinks it's doing. All of the bits in these parameters are important but when I'm having symptoms you've described, I always look at P935 bits 4 (Accelerating), 5 (Decelerating), and 8 (At Speed), 26 (At Limit), and 27 (Cur Limit) first. For instance, assuming a correct and good input speed signal, if bit 8 is set and the motor is not moving, you'll want to check your motor's encoder (other feedback device) if you're using one. If it's damaged or has loose wires, the drive isn't getting the feedback it needs to let the motor draw more current. I once found bits 4 and 27 were simultaneously set because someone accidentally changed the current limit parameter to the minimum of 1. The drive was trying to run but no significant current was leaving the drive because the limit had been hit. No faults, no alarms, and no motion.  I know you said you believe no parameters have been changed from their known good values, but these are all things that should be checked and positively eliminated as possible reasons for the failure.  Keep us posted on your progress and I hope this helps. 
  20. Is this happening on all I/O addresses/tags, or just the N7 data tables? If all, follow @alan_505's advice above. If only on the data tables., we'll have to dig deeper.
  21. 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.
  22. OEE line speed

    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
  23. CCW V13.0

    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. 
  24. Masked moved instruction

    @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.
  25. Masked moved instruction

    @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.