Search the Community

Showing results for tags 'plc5'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Found 29 results

  1. Hello All, I want to read data from a Control Logix PLC, into a PLC5/60, using Ethernet and a MSG instruction in the PLC5. When verifying the MSG instruction in the PLC5, I get an error message. "Target Address in invalid". Once I figure out how to do this I need to replicate it in another PLC5. Scope is to read the status of 4 paint pumps controlled by the CLX. If any of the 4 stop, the PLC5 needs to know, because it is controlling the paint application equipment. Source data resides in a Control Logix 1756-L63. The tag is INT type, 4 elements long, and the name is PUMP_STS_B2. The IP address of the CLX is 4.2.6.230. There are 2 ENBT cards, one in slot 1, and the other in slot 3. 4.2.6.230 is slot 3. PLC2,5 / SLC Mapping has been created in the CLX. File=421 Name PUMP_STS_B1 and File=422 Name Pump_STS_B2. The file mappings represent a binary file created in each of the PLC5's B421:0~4 in Booth 1, and B422:0~4 in Booth 2. The PLC5/60 is Enhanced series E model using the Ethernet side card. The IP address of the PLC5 is 3.26.5.61. I also created MG file types in each of the PLC5/60. MG420:0~19 in each processor. This was necessary to use the MSG instruction in the PLC5. I have searched the forums for examples of how to do this with no solid results. I am trying to follow the best practices of reading the data into my PLC so anyone who follows can tell where it is coming from. While the IP addresses are not closely related they should be able to communicate. I say this because all of our PC's are on the 4.2.6.XXX network on a 255.255.252.0 sub net and we have no issue communicating with the 3.26.5.61 IP address. Any help and advice would be greatly appreciated. Regards, Mike Carter
  2. Any one have an idea how to convert this from PLC5 to CLX Thanks
  3. 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  
  4. 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