Ethernet communication to NU-EP1 laser sensor controller

[dcx]

We are starting development of a new ATE. I already have a Keyence NU-EP1 controller (http://www.keyence.com/products/sensor/network-communication/nu/models/nu-ep1/index.jsp) for 2 laser sensors. It communicates to the PC via Ethernet. I am wondering if I would be able to communicate to this device via a LabVIEW program using VISA functions, since this device does not come with a LabVIEW driver. Or would I have to get the Ethernet/IP Driver, or is this driver included in my LabVIEW full development package? Thank you for the information.

[DollaBrillz]

To communicate with LabVIEW, you will need a driver for your third party device. Below is a link where you can find and download the third party drivers supported by our ADE for this device if there is one supported.

http://www.ni.com/downloads/drivers/

I hope this helps!

[dcx]

Hi, 

I am trying to communicate with the device over ethernet though. There is no third party driver for the device over ethernet/IP that I know or saw from your link. I believe the Ethernet driver here (http: //sine.ni.com/nips/cds/view/p/lang/en/nid/209676) should be able to communicate to the device with cyclic messaging over this network protocol.  I don't believe the NI driver requires a 3rd party driver, from the examples I have seen it should be able to directly communicate over the network. I downloaded the trial of the Ethernet/IP driver and will try it in the next couple days. Hopefully the driver works and we can purchase that, otherwise we will need a new solution.

Thanks.

[Jesse_D]

There seems to be some confusion over Ethernet communication from LV and Ethernet/IP. 

Your device is Ethernet/IP compatable and needs the LV ethernet/IP driver. 

LV does ship a general ethernet communication API (two, actually). But raw TCP communication is different from Ethernet/IP communication. Ethernet/IP is another protocol built on TCP/Ethernet. 

[dcx]

Sorry to take so long to reply, but I noticed when I tried the Ethernet/IP examples (I am trying the ethernet/IP trial for the driver first) it appeared data was successfully being sent to the device. The sensor controller (NU-EP1) has 4 LED lights as indicators for what is going on with the unit. One of the LED's indicated that data was being seen at the devices end, but then there was an LED to show an error that the EDS file for the ethernet/IP communication to PC was not on the PC. 

Is there a way to import an EDS file for the controller device, to the PC through LabVIEW (maybe in MAX?) so that the PC can recognize the device? I was playing around with EtherCAT and noticed you can upload an XML in a project for that type of communication. Is there something similiar for an EDS file for ethernet/IP in this instance?

Thanks!

Kelsi

[DollaBrillz]

Which driver are you currently using, and which version of LabVIEW are you working in? Additionally, is there a specific reason you are using EDS?

Thank you for the update!

[dcx]

I am using the Ethernet/IP driver 1.3 and LabVIEW 2013 sp 1. I have the EDS file for the controller, because that is what was provided with the device by the company.

Thanks!

[DollaBrillz]

Are there any specific errors that you are running into? Have you been able to verify that the device is recognized by the PC? Also, what operating system are you using?

[dcx]

I am running Windows XP still, transitioning to Windows 7 shortly. Currently I see an error in the labVIEW example "TagReadWrite.vi", while the NU-EP1 controller is showing the error of no EDS file. After pressing stop reading, then stop writing I get this error:

Error -251723760 occurred at EthernetIP Tag Write STRING.vi;
Details: CIP Error - Extended status may be available
CIP Status: 0x5 (Invalid destination/class/instance/structure)

Possible reason(s):

Ethernet/IP Industrial Protocol: (Hex 0xF0FF0010) CIP Error - Extended status may be available

Which I don't know if it is related to the EDS file or maybe I have my configuration set up wrong. I know I have the correct IP address.

Kelsi 

[RyanPoPo]

Hey Kelsi,

That error generally means you are trying to send too much data in a single write. The phrase "CIP Error - Extended status may be available" is referring to the byte limitation of most PLCs, which is 504 bytes of data including the data headers. You are most likely hitting or exceeding this limit, so what you need to do is break up your data and use multiple writes to avoid runnin ginto this error.

Regards,

Ryan