kaiser_will
MrPLC Member-
Content count
918 -
Joined
-
Last visited
Posts posted by kaiser_will
-
-
The old 6200-series project must be pushed out with, ASCII Export, with descriptions turned ON. http://control.com/thread/1005348876#1005348876
Then on the Logix import, make sure all (3) elements are turned ON (Symbols, Descriptions, Titles). http://literature.rockwellautomation.com/idc/groups/literature/documents/rm/1756-rm085_-en-p.pdf
-
There was a funky issue with some SLC processors reloading the program from EEPROM. If you pull the CPU, disconnect the battery (that is probably depleted -> this is probably where your problem first started...depleted battery), short the solder pads on the back to clear memory (I know looking at the CPU, but cannot remember the board location names), slide the CPU back in, connect a fresh battery, then try to reload from EEPROM again. http://www.plctalk.net/qanda/showthread.php?t=44851
3 people like this -
We are a machine builder. Old customer requests programmed drives to replace failed Altivar 61 drives. Latest model is Altivar 630. Past engineers did not fully document all the parameter changes. I have read through all of the Schneider literature I could find, but have not found explanation of how the parameters all work together.
Somewhat of a simple application, with the two VFDs running an AC fan motor. Not networked. (2) logic inputs, (2) analog inputs.
I believe LI1 ON will put into RUN mode, loss of LI1 puts into STOP mode. RUN mode uses analog AI1 value for scaling speed command.
The tricky part...analog AI2 is to overcome speed command of AI1 depending on voltage level. The command switching I have not figured out.
-
The home sensor, in your case a dynamic safety switch, is wired into the K5500 Home/Reg input?
Document how you desire for this process to function.
-
Since the motor is being controlled by contactors and not a VFD, the encoder feedback from the motor to the PLC may cause you a lot of grief. The problem you may encounter is position control repeatability.
Depending on the dynamics of the load being moved and the precision required for placement of the load, you may wind up spending a lot of time tweaking the PLC program to be in control and capable.
To answer your question, the MicroLogix 1400 with its (6) high-speed counter inputs, each counter input has a register in the PLC. Refer to the user manual, wire the encoder into a PLC HSC channel, add logic to reset or clear the register, have operator run the system and take note of the register value when in-position, store the register value, conduct repeatability tests.
Refer to page 96 http://literature.rockwellautomation.com/idc/groups/literature/documents/rm/1766-rm001_-en-p.pdf
-
Please post screenshots of some of the PLC code with the HMI button control. It appears your issue is how you are coding your PLC logic and the HMI buttons/status bits.
In a case like this, where you are programming your first PanelView and CompactLogix application, it is very possible your HMI and PLC communicate properly, but you may not be structuring your HMI objects or the code in your PLC properly.
There are many ways that engineers can code the HMI and PLC applications.
Suggestion...create test CompactLogix tags (HMI_Command, HMI_Status), structured DINT. Add simple PLC rung for a HMI_Command.0 (Start_CMD), normally-open contact, with one-shot, add a test to make sure the output coil is not ON, then latch the output coil HMI_Status.0 (Start_Coil). Add a branch around the output coil with one-shot and unlatch the start bit HMI_Command.0. In this fashion, if the output is not already latched ON and the operator starts, the HMI start bit is only ON for one PLC scan cycle, it is used to latch the output coil, then the HMI start bit is forced OFF.
Follow this up with a rung to turn the output coil off. Simple PLC rung for HMI_Command.1 (Stop_CMD), normally-open contact, with one-shot, add a test to make sure the output coil is ON, then UNLATCH the output coil HMI_Status.1 (Start_Coil) with coil branch and one-shot with unlatch stop bit HMI_Command.1.
Finish your test by adding (2) new HMI test buttons...Start and Stop (HMI_Command.0 & .1, respectively). Add a multi-state indicator, 2-states, 0 = Off = Green (safe mode, no motion) = HMI_Status.0; state 1 = On = Red (in motion).
If all works properly...output is OFF (multi-state indicator = GREEN), PLC tag HMI_Command.0 = OFF & HMI_Status.0 = OFF. User presses START, output tag is turned ON, multi-state indicator = RED, PLC tags HMI_Command.0 = OFF & HMI_Status.0 = ON.
-
Can you correctly start and stop from the PLC code only? If you cannot toggle or latch HMI input bits to start and stop in the PLC, you are wasting time. Get the PLC code to behave properly then move onto the HMI. The key is to structure the HMI application so that the buttons accurately tell you what is happening (the HMI should not display you wanted to start a device, but should display that the device is actually started).
-
Which A-B PLC platform are you using?
When you say "move induction motor", do you mean as an indexer (i.e., moving the AC motor to a physical position)?
What is controlling the AC induction motor (i.e, VFD)?
-
Not a silly question, in my opinion. Many of us have been in the same situation before.
Category: There are 2 categories of Safety Circuits...Stopping Category and Functional Category. Depending on your industry, when someone is talking about "CAT 3" safety, they are probably referring to Functional Safety.
CAT or SIL or PL: Depending on your industry, you may be required to design to CAT (Safety Category) or SIL (Safety Integrity Level). These categories are being replaced by ISO 13849-1:2006, which will combine them into a new safety rating PL (Performance Level).
My understanding is that the base safety standards drive equipment manufacturers to follow mandatory rules, then disseminate the outcomes into manufacturer safety design guides. The base safety standards are from standards organizations and typically require paid subscription for copies. I believe that is why equipment manufacturers have developed safety design guides. These are the main players that I know of.
TUV Accreditation https://www.tuv-sud.co.uk/uploads/images/1397220093835586640369/plr-determination-matrix.pdf https://www.tuv-sud-america.com/uploads/images/1437679765593848991447/uk-mkg-practical-guide-lr-en-gb.pdf
Rockwell/Allen-Bradley http://www.ab.com/en/epub/catalogs/3377539/5866177/3378076/7565826/Performance-Level-PL.html http://www.rumsey.com/files/upload/ISO13849.pdf
Keyence http://www.keyence.com/ss/products/safetyknowledge/performance/level/
Pilz https://www.pilz.com/en-US/knowhow/law-standards-norms/functional-safety/en-iso-13849-1
Schneider/Telemechanique http://www2.schneider-electric.com/documents/original-equipment-manufacturers/pdf/Machine-safety-guide.pdf
-
This is an OLD topic. You are encouraged to start new topics to get the best responses possible.
You need help with FactoryTalk View 8 for "global parameters and parameters passing". Your question is vague. Can you specify what your task or issue is?
Specifically are you needing help with FTView Machine Edition (ME - for A-B HMI applications) or FTView Site Edition (SE - for PC-based applications)? They are different software packages, thus features and functions may be different.
http://literature.rockwellautomation.com/idc/groups/literature/documents/um/viewme-um004_-en-e.pdf
http://literature.rockwellautomation.com/idc/groups/literature/documents/um/viewse-um006_-en-e.pdf
-
Many current-technology platforms are utilizing software E-stop circuits. I was against the concept, but have been swayed by the robustness of the solutions. Allen-Bradley's STO (Safe-Torque Off) emergency stop circuit simplifies machine design and build, and gives many programming features to work with; extremely well suited for servo motor control.
http://literature.rockwellautomation.com/idc/groups/literature/documents/rm/gmc-rm002_-en-p.pdf
-
There are (2) components to Logix5000 for version control and compatibility...Logix5000 version and Firmware version. You should install Logix 20.04 and all of the firmware versions you will need to support.
After Ver 20.04, Logix5000 became Studio5000.
-
Much of your answer can be determined if the outside engineer can remotely connect through your company WAN and ping the PLC? There are many levels of system architecture that can affect this situation.
A popular method today, but requires a PC with the Allen-Bradley programming and communication software already on it...you at the shop floor connect your PC or laptop to the machine, your PC or laptop must be connected to your company WAN, then utilize something like TeamViewer (remote desktop access through internet).
-
The PowerFlex 525 is an Ethernet/IP drive that integrates well with tag-based PLCs. The MicroLogix 1100 is the older-generation data table-based PLC. For adapting the PF525 with a Micro1100, you are probably using a MSG CIP messaging protocol?
I did find this document; Appendix A references Fault Code for the Instance declaration. http://literature.rockwellautomation.com/idc/groups/literature/documents/at/750com-at001_-en-p.pdf
-
Which versions of FTView & Logix5000 are you utilizing?
In FTView ME Studio, are you browsing for your Logix5000 project (on your development PC) and reading all of the tags so that they are visible? In FTView ME, one must configure the communications link (of your Development PC to the PLC).
Posting screenshots should provide quicker or more thorough responses from the forum.
Refer to page 32 in this lab example. http://www.wernermn.com/assets/files/PDF/Solution%20Expo/Presentations/VI/VI02.IntrotoFTViewME8.0LabManual.pdf
-
-
Your question is if 1756-HSC in a ControlLogix system would replace a 1746-HSCE in a SLC-500 system, for "analog output to control a VFD". Analog output to control a VFD is independent of the high-speed counter module; the counter module is used by the PLC to create the analog output signal, but the counter module is not directly responsible for the analog output command.
The SLC-500 1746-HSCE is capable of X1-X2-X4 quadrature modes, up/down pulses, and direction. The ControlLogix 1756-HSC is capable of X1-X4 quadrature modes, counter mode.
You will need to delve in further, into the SLC program, to identify how this counter module is used.
http://literature.rockwellautomation.com/idc/groups/literature/documents/um/1746-um002_-en-p.pdf
http://literature.rockwellautomation.com/idc/groups/literature/documents/um/1756-um007_-en-p.pdf
-
CompactLogix L32E processors have an internal battery backup (#1769-BA); Chapter 10. The processor has an indicator light for the battery health; the battery can support retaining processor memory as long as the BAT light is energized (when the processor is de-energized). The user manual identifies how the expected battery life is de-rated based on panel temperature. You could be experiencing a failed battery if the processor is powered down and the battery is disconnected (or depleted).
Predictive Maintenance schedule, spare battery, having communication cables & programming software (or local resource to support you) and current program backups. These steps may save your bacon.
http://literature.rockwellautomation.com/idc/groups/literature/documents/um/1769-um011_-en-p.pdf
-
CompactLogix L32E...Page 86, CompactLogix does not support removal and insertion under power. http://literature.rockwellautomation.com/idc/groups/literature/documents/um/1769-um011_-en-p.pdf
How does one look for CompactLogix PLC faults? Page 131 of the User Manual displays how to diagnose faults with the built-in status lights.
If the user manual does not identify the fault, one will have to go online with Logix/Studio 5000 and refer to the Logix5000 programming manual (which has in-depth fault code lists). http://literature.rockwellautomation.com/idc/groups/literature/documents/pm/1756-pm014_-en-p.pdf
-
Thank you for the input, ControlsGirl
-
What process did you follow for "moving to a remote SQL server"? I believe the key is to edit the ODBC Connection to the NEW SQL Server. The SQL Server Authentication credentials are very critical for this to work.
-
Does anyone know of an alternative to Turck for fieldbus cordsets? I like their quality, but the typical 2-3 week lead time for any length fieldbus cordset is a big challenge to work around.
-
It appears that your HMI application is not properly communicating with the PLC, none of the tags are being updated (which is why they are in an ERROR state).
Was this a working system or is this a new startup?
The bottom-pane of the FTView SE runtime console has diagnostic messages. Stretch this box open wider and post a screenshot. This box will display the status, working or not-working, and guide you to what the root problem is.
-
Had this FTView SE Ver. 8 system been setup for SQL data storage, already? Modifying applications to add system-level features can be a big chore.
If you message me, I can share a big Word work instruction I developed for building a FTView SE PC from scratch. The 70-page document is too large to upload.
Program Wont Download to PLC
in Allen Bradley / Rockwell Automation
Posted
Reminder: With control systems, the development PC (typically considered Level 1) is always higher-level than the PLC (Level 0). Thusly, download sends to the PLC; upload sends from PLC.