Bobby5184 (Customer) asked a question.
P1-540 & Keyence NU-EP1
Hello,
I have not had to set up a Ethernet IP device with the Productivity PLC.
I have a P1-540 PLC and Keyence fiber optic sensors with a NU-EP1 Ethernet IP Buss.
I have IP address set in both and they are both plugged into a stride switch.
Under hardware configuration/ethernet IP tab I try to import EDS file and get the following.
I did manually configure a generic client but still no luck.
Can anyone off pointers to get me headed in the right direction?
Thanks.
Hi @Bobby5184 (Customer)
I have not connected a Keyence Fibre Optic Sensor NU-EP1 but here are a couple of posts showing the process of connecting Ethernet IP with the Productivity.
Productivity to Click PLC Ethernet IP
https://accautomation.ca/productivity-1000-plc-click-ethernetip-remote-io/
Productivity to BRX Do-More PLC Ethernet IP
https://accautomation.ca/productivity-1000-series-plc-brx-do-more-ethernetip-remote-io/
This may help you out.
Regards,
Garry
https://accautomation.ca/
Thanks Garry,
Yes todays plan was to look up your video's. I have link several of them in the past to friends and co-workers who where having issues with certain things. I will check out the ones you have pertaining to this and see if I can come up with something.
Thanks again for the time and effort you put forth to do these.
Making a little progress today. As you can see from attached image I have connection and it knows what it's connected to.
I'm enabled and connected but it has a status description of my message as "Invalid Segment in path"
We've had many calls pertaining to problems when using Keyence EDS files.
If the Keyence adapter device returns an "Invalid Segment" error, it means that the Keyence device doesn't understand the path that Keyence has specified in the EDS file. This points back to possible mistakes in the EDS file.
Found another customer that was getting same error but it was a Keyence bar code scanner. You might be able to apply some or all of their setup to see if it will get yours up and running.
This customer noticed that resolved his issue was enabling a CFG file with zero(0) elements (even though EDS files did NOT have the CFG file available). They implemented this a part of their generic device setup and was able to successfully establish ethernet communications.
Thanks for the reply and the PDF file.
I started over following this advice and have gotten rid of the "Invalid Segment" error. Now seeing the following error. OX109.
I have an email into my local Keyence office waiting for further information.
Reference help file topic P260 for all EtherNet/IP error codes.
Based on the EDS file I found online for the NU-EP1, the 'Monitor Data and External Input' connection is:
T->O
O->T
Configuration Data
The file types that can be attached here do not include EDS files. So, I've saved the one I found as a TXT file and attached it here. If this is not the file for which you are referring, please attach your file to the post using the same approach.
Sorry for the delayed response, been out sick the last couple of days.
I have been about to successfully connect and its talking back and forth. I just need to get my IO messaging correct with data type and size and the assembly instance. Catching up on some things today so hopefully tomorrow.
Thanks
Thanks for all the help. I have finally established communications and can see the status of each of the 8 fiber optic sensors. I will follow up with exact details of my settings so if it may help someone in the future.
Hi Bobby, I'm trying to do exactly same thing like you. Could you post your settings and if possible couple of rungs of your program that show how to get the reading from the Keyence sensor?