Hello everyone! I'm currently engaged in a project that involves a Micro 820 PLC and an Ethernet/IP-compatible distance sensor (link provided below). My main objective is to retrieve the sensor data and display it on a Human-Machine Interface (HMI). The documentation from the sensor manufacturer offers clear guidance for setup with Logix 5000, which seems straightforward. However, I've encountered challenges while searching for resources related to the Micro 800 series controllers. Unfortunately, Connected Components Workbench (CCW) does not provide support for EDS files, leading me to implement CIP Generic Messaging as per Rockwell's support instructions. While I received a reference document with examples, it mainly focuses on PLC-to-PLC communication and doesn’t seem applicable to my situation. Has anyone in this community tackled a similar challenge or know of any relevant literature I can consult? You can find the sensor here: [Wenglor Distance Sensor](https://www.wenglor.com/product-world/products/) and the Rockwell document here: [Rockwell Automation Guide](http://literature.rockwellautomation.com/idc/groups/literature/documents/qs/2080-qs002_-en-e.pdf). Your insights would be greatly appreciated!
Welcome to the PLCTalk forum community! To get started, we recommend you follow our Quick Start guide. Use the "CIP Generic" configuration as demonstrated to access the Identity Object of your sensor. If this initial step is successful and you can retrieve information such as the Device Code (Class 1, Instance 1, Attribute 3), you can advance to more complex operations like reading specific parameters. If you could provide a link to the specific sensor model and its documentation, that would greatly assist us; the link shared previously directed us to a general product overview. It's important to note that the sensor in question might not support this type of connection and may only function with an I/O scanner such as ControlLogix or CompactLogix. We will have a clearer understanding once we review the datasheet and user manual.
Thank you for your response! Unfortunately, I'm unable to provide a direct link to the product page. I missed it earlier, so I apologize for the inconvenience. You can easily find the item by following the link and entering the part number provided below into the search bar, located to the right of the shopping cart. Once you locate the product, scroll down to the "Downloads" section, where you'll find a variety of documents available for you. I can't upload the documents directly because their size exceeds the limits. Part Number: OY2TA104P0150E If you encounter any issues accessing the part listing, please feel free to reach out. UPDATE: Here is the direct link to the product listing. I was able to share it by selecting "Share Product" on the page: [Product Link](https://www.wenglor.com/product/OY2TA104P0150E)
Thank you for your help! I've located the Electronic Data Sheet for the device, which provides detailed information about Parameter 1, known as the Measured Value. The specifications are as follows: - **Param1**: 0 - **Reserved**: Will equal 06 - **Link Path**: "20 64 24 01 30 01" - **Link Path Size**: 0x0000 - **Descriptor**: 0xC4 - **Data Type**: DINT4 - **Data Size (in bytes)**: "Measured value" - **Name**: "mm" - **Units**: "" - **Help String**: 100, 10100, 100 - **Minimum, Maximum, Default Values**: , , , - **Scaling Factors**: mult, div, base, offset - **Links**: mult, div, base, offset - **Decimal Places**: 1 The Parameter Path is crucial as it encodes the Class, Instance, and Attribute of the parameter, specifically "20 64 24 01 30 01". This indicates that the Distance falls under Class 0x64, Instance 1, Attribute 0x01. Ensure that the data size is set to 4 bytes. Once you’ve successfully configured your Micro 820 program with Class 1, Instance 1, Attribute 1 set to 1211 (Wenglor Vendor ID), be sure to test this implementation.
Hey! It sounds like a challenging project you've got there. I’ve worked with similar setups where I had to integrate Ethernet/IP devices with a Micro 800 PLC. While the absence of EDS support in CCW can be a pain, I found that digging into CIP Generic Messaging with examples can actually be quite effective, even if they focus on PLC-to-PLC communication. One tip is to carefully structure your message format according to the sensor’s specifications, as this can help in pulling the data correctly. I also recommend checking out forums dedicated to Automation and Rockwell products; sometimes users share their own EDS workarounds or specific experiences that could be really helpful. Good luck, and keep us posted on your progress!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: 1. Determine the sensor’s Ethernet/IP communication parameters such as IP address and data structure. 2. Use the reference document provided by Rockwell Automation to understand the required messaging format and commands. 3. Implement the necessary messaging configuration in CCW by setting up message instructions to request and interpret
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.