Search the Community
Showing results for tags '1754-en2t/d'.
Found 4 results
Tapas Thakker posted a topic in Allen BradleyHello Guys, I am very new to CIP messaging and in our project, we are trying to Controllogix to SCADA server using CIP messaging: What I understand from the process right now is : 1. SCADA Opens a connection for Large forward Open ( Connection size set at 2500 bytes) 2. PLC responds and establishes a connection 3. SCADA send an MSP request to access tags from PLC 4. PLC responds to this request The problem we are facing is the PLC doesn't send out a response of more than 240 bytes, Have any of you guys have faced a similar issue or can help me with troubleshooting? Thanks in advance Attached screen captures from wire
Issue suddenly began about 3 weeks ago...or I noticed it anyway. I opened devicenet to change a parameter in a drive but all nodes have a question mark on them and RSNetworks will not register them no matter what I do. I checked RSLinx and I see question marks on The DNB/E modules and on the EN2T/D modules. I made sure I had the eds files and AOI's for these modules but nothing changes. I have uninstalled Networx and changed versions several times but it comes up the same way. I am using RSLinx version 4.10 and now have RSNetworx version 28. Any ideas? Thanks in advance.
Good afternoon fellow members,I once again ask for your help to know if any of you have struggled with similar issues. For the past year and a half, Every 1-2 months we seem to be losing communication with one of our PLC's/racks. We have in the rack a 1756-EN2T card (revision 3.006) that will flash as if it is communicating and status OK (green LED), yet we will be unable to ping it and our operator interfaces go into error. We could also not open the web browser page of the EN2T card, nor connect to the PLC/rack through RSLogix5000. As this happened over the weekend, the local electrician was called and he tried cycling power to the rack and there was no change after it came back on (not sure how long he left power off to the rack though). The problem seemed to be fixed after we told him to pull the EN2T card out of its slot and then re-insert it.We verified the CIP cinnections for this card and it is around 98 to 101 CIP connections out of a max of 248, so not too high. the card's CPU usage is 24-29%, so no indication of problems there. EN2T Card is set to auto-negociate, just like all the other cards we use at all of our plants. Has anyone ever experienced a similar problem?Thank you in advance for all your help and knowledge-sharing!
TigerLily posted a topic in Allen BradleyI have an application I am currently working on where I have a single AB ControlLogix PLC that needs to read data from 12+ Omron CJ2M PLCs. The Omron PLCs don't need to read any data from the AB. I have tried several things including the generic .eds file from Omron and the instructions in the document I found on this site: Omron CJ2 to Rockwell ControlLogix Ethernet/IP Datalink. The generic .eds file gave me a D6 error on the Omron side and after talking to support it does not seem like the correct path. When I tried following the instructions for the datalink I ran into several issues. The first issue was that after configuring my network in the Omron software upon trying to load it I got a unit mismatch message for the 1756-EN2T, the .eds file I have is for a 1765-EN2T but the card shows as a 1756-EN2T/D, so I am concerned that could cause an issue...that being said I can't find any .eds file specifically for the /D revision. The next thing I noticed was that there doesn't seem to be be a way to link the produced data from the Omron to the AB, the Omron configuration software with the AB .eds files loaded only gave me the option to send data to the Omron which we do not need to do. I created a generic Ethernet module in my RSLogix program for the Omron PLC and then created a consumed tag and linked that to the module but I do not see where I set up the link on the Omron side for that, so how does it know what addresses to read?? Any help would be greatly appreciated!!!! Thank you!