Search the Community

Showing results for tags 'guardlogix safety controllers'.

  • Search By Tags

    Type tags separated by commas.

  • Search By Author

Content Type

Find results in...

Find results that...


Date Created

Last Updated

Filter by number of...

Found 37 results

  1. Mitsubishi Safety PLC

    Nurlan_B posted a topic in Mitsubishi

    Hi everyone.  Is it possible use mitsubishi safety plc as logic solver for fire and gas detection system  on the plant ? 
  2. Hi Guys, I have an application where i am trying to interface between a 1756-L61s GuardLogix CPU (via an EN2TR ethernet module) and CitectSCADA v7.2. Which driver in citect will work in this situation ? - i have tried ABCLX with no success. Have interfaced to a ControlLogix CPU without issue, not sure what i am missing - any ideas?
  3. Good day, We are using Guardlogix 1756-72s controllers for our ESD system. We created safety add-on instruction in RSLogix5000 v20 and wanted to test it using RSLogix Emulate 5000, however we are getting an error that safety add-on instructions are not supported in standard controllers. Is there a way to test safety code using Emualate or Softlogix?

  4. Writing access to Safety CPU

    Nizami_225 posted a topic in Mitsubishi

    Hello. I tried to read/write from/to safety cpu (QS001) over MC protocol. I managed to read from cpu devices but i couldn't write to any safety cpu device. It was possible to write data to Q series plc (Q02HCPU in my example) with MC protocol. I am searching any method of writing to safety cpu (QS001). If anyone could this before? And are there any settings in GX Developer (GX works) for access to writing to QSCPU? P.S: As known it's possible to read/write from/to Q series PLC with MX Component. It's also available reading from QSCPU with MX component. But cannot write to safety cpu with MX component (written in Mx component manual). Thanks.
  5. PAROCK1 for HMI/SCADA View File Now a software solution is available for your Modbus (MB) needs in Rockwell/Allen-Bradley Control Logix or Compact Logix (Clgx) family processors, instead of a traditional 3rd party hardware like Prosoft MVI-56, Molex SST-SR4-CLX-RLL etc.  It is an Add-on instruction (AOI) for PLC/PAC firmware v16 or later, (other solutions are available for pre v16 systems).  For hardware interface, use PLC’s channel 0 (serial) or TCP/IP Interface module(s) to have as many MB TCP/IP devices or serial devices.  (Some limits apply based on system configurations, Comm. settings depending on HW used.) Connect any MB Client/Master or Server/Slave device(s) to your CLgx PLC, including flow computers, analyzers, VFDs, Power Monitors, Level gauges, Smart I/O, etc.  All the MB public/native function codes are supported.  32-Bit integers/floats as single entity are supported with byte and word level swapping. A separate utility automates the data mapping to your PLC logic.  Features -Serial Master (BASIC required Option); TCP; Slave; Redundancy; More than 5000 accumulative registers; MB CFC (Custom/Private Function Code) Support; Data mapping too – Between PAROCK1 & your PLC logic; Packaged with Rockwell; TCP/IP Interface Module; Volume Discounts; Annual Support Requirements -Rockwell/AB-CLgx processor with v16 or later.  Contact PCI for earlier versions. -If using CPU’s Chan0, you cannot use Chan0 for any other user mode activity. You can use it for non-user mode activities -TCP/IP Interface Modules from Rockwell/AB supported, are: -1756-EN2xx ControlLogix® Ethernet/IP communication modules, firmware revision 5.007 or later -1756-EWEB ControlLogix Ethernet/IP web server module, firmware revision 4.006 or later -1768-EWEB CompactLogix Ethernet/IP web server module, firmware revision 1.002 or later -1769-L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, and 1769-L36ERM CompactLogix controllers, firmware revision 20.011 or later -1769-L24ER-QB1B, 1769-L24ER-QBFC1B, 1769-L27ERM-QBFC1B CompactLogix controllers, firmware revision 20.011 or later -1769-L16ER, 1769-L18ER, 1769-L18ERM CompactLogix controllers, firmware revision 20.011 or later Other Related Services/Items -Custom PLC Add-on instructions building -PLC upgrades, troubleshooting, applications -PC Windows, iOS5, Linux, Mobile devices Comm. Drivers -Custom development, Technology Transfer Services  -Other Non-AB communication drivers for serial or TCP  -Full control system integration, training, architecture design This driver can be conviniently used with Visual Studio in development of complete large scale complex HMI/SCADA Systems. It can be used to perform advanced reporting MES, analytics, IoT, Big data type apps. One example is available to download here For More Info Overview of Parijat Drivers: Click here  Additional supporting Info about Parijat Drivers:Click here Complete Related Driver options: Click here     Submitter Scadadoctor Submitted 03/10/16 Category Other PLC Demo Software
  6. Hello All, I have a guardlogix processor that I just safety locked with a known password. When I tried to unlock, that password didn't work. Upon reading a bit I realized that the lock and unlock passwords are separate. I never set the unlock password but blank doesn't work. Could it be a leftover due to program copy paste or is there a way to find/reset this unlock password.    
  7. Hello, I am new-bie for using Modicon. this is what we have and i was wonderting if these are controllers. if they are, why do we have 2 of them? I am trying to get PLC program for back up. Can someone help me out? Thanks for reading
  8. Hello. I searched for an answer for this but it is still not very clear to me. I have a new Guardlogix 1756-L72S. I would like to create a project to work with it with firmware version 20.13. I have RSlogix5000 v20.01(CPR 9 SR 5) which should be compatible with it (in fact I can open projects with another guardlogix that have that firmware version) BUT when I create my new porject, the firmware version RSLogix5000 puts is v20.11 1. How could I create a project with the firmware version 20.13 for my guardlogix? (Didn't find an AOP for this) 2. If I update the guardlogix to firmware 20.13 with the CONTROLFLASH, could I still be able to go online and work with it, even though my project has a different firmware version? Thanks!
  9. Several years ago before I arrived at my company, an integrator came in to do the automation on our system. They used a Controllogix 1756-L61S for the safety portion of the project. Apparently, when they completed the job they did not provide the source code with comments, safety password, etc. for anything and it got ugly between our company and theirs. In other words, they would not provide it if we went back to ask them. Allen Bradley has told us that we can not make any alterations now to the safety logic because we do not have the password that was used to create it. And they said there is no longer a master password that you could use like in previous controllers. Does anybody know of any workarounds for this? Or have heard of anything that might possibly work?
  10. Hello everybody, I'm designing a safety system for a HV power supply. The idea is to use a series of 2 contactors to supply power to the system controlled by a safety PLC. So, it is a typical application. The problem is that the power supply and the contactors are are installed on HV platform, isolated from ground, where the PLC is installed. I think the only possibility is to use an optic fiber link. Does any body know is there is any way to connect a contactor to a PLC output using an optic fiber link, without compromise the cyclical checking performed by the safety module (as I understand, the outputs are continuously check in order to detect wire breaking). The alternative that I have is to use a distributed IO system installed on the platform, connected with a Ethernet Optic Fiber to the PLC: for example using a simens S7-400 PCL with a IM467FO modules (on ground) and a ET200M system with a IM153-2FO module on the platform. But I wonder if there is something more simple and cheaper. Thanks!

  11. Version 3.11.5.0

    2804 downloads

    .NET class library for use in Visual Studio.NET to create HMI/SCADA apps that communicate with A-B ControlLogix, CompactLogix, Micro800 Series, PLC5, SLC500, and MicroLogix PLCs via Ethernet.   For .NET Framework 2.0 - 4.8 projects. Does not require OPC, RSLinx, or 3rd party drivers. x86, x64, and Any CPU compatible. Visual Studio.NET 2010, 2012, 2013, 2015, 2017, 2019, and 2022 compatible Supports unsolicited messages. Most .NET Framework targets are supported, including Web, Windows, console, and service apps. Can be configured programmatically or visually Visually design your entire communications configuration without writing a single line of code Extremely high performance - 5~10 mSec typical transaction time Supports ControlLogix family native tag names Supports reading and writing entire ControlLogix family UDTs and PDTs Supports block transfers of up to 250 words per transaction Tag database can be configured via code or visual designer Abstract base classes allow you to write generic code that works with all drivers Synchronous and asynchronous read/write methods Data change notifications Provides common user interface across all driver classes No limit on number of devices or data points Multi-threaded for high data throughput Includes extensive help system Example applications with VB and C# source code included. Easily connect office systems to factory floor. Runtime-free for qualified applications  
  12. File Name: A-B Ethernet Driver for .NET File Submitter: Automated Solutions File Submitted: 13 Dec 2007 File Category: Demo Software .NET Component for use in Visual Studio.NET to create HMI/SCADA apps that communicate with A-B ControlLogix, CompactLogix, Micro800 Series, PLC5, SLC500, and MicroLogix PLCs via Ethernet. Supports unsolicited messages Does not require OPC, RSLinx, or 3rd party drivers. x86, x64, and Any CPU compatible Visual Studio.NET 2005, 2008, 2010, 2012, and 2013 Compatible Most .NET targets are supported, including Web, Windows, console, and service apps. Can be configured programmatically or visually Visually design your entire communications configuration without writing a single line of code Extremely high performance - 5~10 mSec typical transaction time Supports ControlLogix family native tag names Supports reading and writing entire ControlLogix family UDTs and PDTs Supports block transfers of up to 250 words per transaction Tag database can be configured via code or visual designer Abstract base classes allow you to write generic code that works with all drivers Synchronous and asynchronous read/write methods Data change notifications Provides common user interface across all driver classes No limit on number of devices or data points Multi-threaded for high data throughput Includes extensive help system Example applications with VB and C# source code included. Easily connect office systems to factory floor. Runtime-free for qualified applications Click here to download this file