ElectronGuru
MrPLC Member-
Content count
363 -
Joined
-
Last visited
Posts posted by ElectronGuru
-
-
You'll need to go to the PanelView's Configuration mode to get the configuration settings. Start here on page 59:
https://literature.rockwellautomation.com/idc/groups/literature/documents/um/2711p-um001_-en-p.pdf
As for the HMI and direct reference tags, those are in the PanelView's code, which the programmer would've written in FactoryTalk ME. The runtime (.MER) file would have to be uploaded from the PanelView to the laptop, restored to a .MED file, and then you'd have access to the tags.
-
As a drives guy, when I think of PWM I tend to think in terms of both positive and negative pulse polarity (as opposed to only true and false), and those pulses are almost always in gigahertz. When I've needed pulse control for SCRs I've always used an external piece of hardware, as I described above. So... this particular thread is opening a new door for me.
-
-
I assume we're using the same acronyms and by "PWM" you mean Pulsed Width Modulation. Off the top of my head I don't know of any Allen Bradley output cards or instructions that create PWM. There may be a process card out there that does that but I'm not familiar with it, and a quick glance at the ControlLogix Analog I/O Modules User Manual didn't turn anything up.
When I was doing IR welding we installed solid state SCR device that were like a very dumbed-down DC drive. A voltage signal directly from a PLC analog output card went to the input of the SCR driver, which then pulsed an output to the IR bulbs to control the temperature of the weld. Is this similar to what you're trying to accomplish? If you're in a closed loop system providing the actual temperature back to the PLC, you can certainly use the PID instruction to get tighter control of that temperature. I just don't think you're going to be able to PWM out directly from the PLC to a field device.
-
@TimWilborne has a lot of great videos on YouTube.
If you check with your local AB distributor you can find training delivered there by a Rockwell instructor. Based on your experience and current job, I'd recommend CCP299, description below:
https://literature.rockwellautomation.com/idc/groups/literature/documents/pp/gmst10-pp335_-en-e.pdf
It's offered as a level 1 class so it goes over a lot of fundamentals, but graduates at level 2.
-
The controller you have can only be upgraded to v20, and is not compatible with anything above that.
When the firmware is updated in any controller, that controller's project is deleted and must be downloaded in the new version. This means you must have that version of Studio installed on your laptop, and the project must be saved in that version.
Hope this helps.
-
My understanding is that 64 bit data types can only be used in the L8 controllers, V28 and above.
1 person likes this -
-
Several things come to mind, starting with the huge mismatch between the motor and drive HP. This could be the biggest part of your problem. The drive is sensitive to that, as well as whether the motor is inductive of permanent magnet.
When a PowerFlex drive is in V/Hz or SV (Volts-per-Hertz or Sensorless Vector) modes, the RPM displayed when running is essentially an estimate of speed based on the drive's output. However, you said that you're not getting any voltage output at R,S & T, correct? I've seen this on 755 drives in FV (FluxVector) mode when the encoder is wired incorrectly. The drive is trying to accelerate the motor but the encoder pulses are the wrong polarity. Is the motor using an encoder (other device) for speed feedback?
If you have Connected Components Workbench, can you post a copy of the drive file here? There are just too many scenarios to go through and a look at the configuration would be a big help.
-
I'm not overly familiar with PV800 but my first thought is that if the problem is related to cycling the power, is there a PV powerup (or other) macro running that sets your initial values to zero?
Assuming the 800 has powerup macros available, a problem with this theory is that you said the problem progressed through drives, rather than simultaneously affecting them all on powerup. Just spit balling here...
-
I talked to an integrator today who told me that on upgrades, his customers are now demanding change-over to Allen Bradley. Apparently lead time on Siemens controllers & components are 18+ months.
-
I'm assuming this will be wired to a Micro- or CompactLogix encoder input?
-
-
@Twigums in FactoryTalk Studio, open a display, right-click on any white space within that display, and select "Display Settings" from the pop-up dialog box. In the lower left corner of the Settings box you'll see "Maximum Tag Update Rate".
When the display is open in a running HMI project, this field value sets the rate at which the display must attempt to update the tag(s) value(s) from the controller. Depending on the process, 1 second is usually sufficient.
The quicker the update rate, the more often the HMI will request the data be retrieved across the network, which can cause communication issues in other devices on that network.
1 person likes this -
I created a project with that card and it doesn't show a raw low and high. What I'm seeing is a Current Range, Digital Filter, and Low/High Engineering. Check the attachment to see that I have the correct card. If so, I'd set the following:
- Range to 4-20 mA
- Low Engineering to 10
- The High Engineering to 212.
-
In the 5-series there are the 523, 525, and 527 drives. The differences are mostly in embedded communications and safety options, but I believe they are all limited to a max of 30HP. Wouldn't hurt to get a price quote and do some comparing to see if it's worth the while to change over as your current drives age out and fail.
Looking forward to hearing what failed on your 4M, and hopefully they'll be able to tell you why it failed, as well.
-
Re-seating means physically removing a circuit board, I/O module, controller card, etc, and reinstalling it. It's a bit of a placebo but surprisingly, solves a lot of problems.
Cycling the power means turning the power completely off, waiting the minimum amount of safe time, then turning power back on. If there is no safe time specified in the manual, one minute with power off is usually sufficient.
-
Your status light is red in both pics, so I'm assuming it's solid red. Page 103 of the manual says that's a non-recoverable hardware failure and advises to replace the terminal. Sorry it's not better news.
https://literature.rockwellautomation.com/idc/groups/literature/documents/um/2711r-um001_-en-e.pdf
-
@BobLfoot OUCH! I bet the distributor and Allen Bradley both hated hearing that!
These days, anything 30HP or less I'd grab a PF525. It's a newer (current) generation drive and was designed to be a drop-in replacement for the Bulletin 160s, PF4s, and PF40s.
1 person likes this -
It sounds like the Compare Tool is not installed on the VM. Try downloading the Compare Tool from, and then installing it on your VM.
-
It does sound as though a control or power board has died. When a control board goes out they're not usually as dramatic as the power parts, like the IGBTs or incoming power diodes.
If it's relatively new, hopefully you can get it warrantied and maybe a failure analysis to find out why it died.
-
A quick glance at the book didn't reveal anything. My gut says you have a brick and need to replace the drive. Check the obvious things (like all three phases of incoming power, loose internal connections, etc) first, but I think this drive is done.
2 people like this -
@Joe E. is 100% correct. There are just too many variables when adding a drive to a CLX project. Drive model, frame size, HP, volts, firmware, etc, just to name a few, and it's such a pain to get all those matched manually.
In addition to Joe's method, when online with the CLX project I've been able to right-click on the network and select "Discover Module". That should pick up your PowerFlex drives and add them to the project just as if they were IO cards in a remote controller chassis, except of course you don't have to add the chassis.
1 person likes this -
CLX controllers are 32 bit processors and as such, they like to process 32 bit data. It just works better. Look at this way; if you were moving and everything you owned fit into boxes that were exactly X-by-Y-by-Z, wouldn't that be an easier move than playing Tetris with your furniture in the moving truck? Sure, some of the boxes may not be full but if they're all the same size, it's an easier move. Boxes that are the same size stack and move easier than boxes that are different sizes, even if some boxes are only partially filled. If all your data is the same size (DINT) that's easier to process than different size data packs (SINT, INT, LINT, etc), even if half the DINT data (bits 16 and above) are not used. This is why the default data type in CLX controllers, as well as most IO cards, is DINT. Same size data equals easier and quicker processing of said data in a CLX controller.
View PanelView Plus Configuration
in Allen Bradley / Rockwell Automation
Posted
If you're wanting upload, convert to MED and peek inside the code, yes, you'll need FactoryTalk ME Studio.
If it's 5.0 or lower you're going to need to call Tech Connect.
Also, whoever created and transferred the MER had the option to not allow conversion back to MED, or to allow conversion with password only. If that's the case, you'll never be able to recover the MED. I don't know of any way to determine that other than attempting to restore the MED and seeing if it restores, prompts you for a password, or says it can't be restored.
If you're able to restore the MED, you'll find the HMI tags in an easy to access HMI tag file. You'll have to sus out the direct reference tags individually by going to the connections tab in the properties dialog box of every interactive object (like push buttons and gages) on every display.