04-08-2009 10:41 AM - edited 04-08-2009 10:41 AM
Unfortunately I am not sure what might be the issue. It seems like the presence of EtherNet/IP support (not just Ethernet) varies based on which version PLC5 you have and while it seems like yours should support it based on Rockwell's app notes, I cannot say for certain. I also am not 100% certain if the PLC5 supports the type of message we are using (Rockwell's documentation is somewhat lacking in this regard). Since I do not have a PLC5 here to play with I can't really examine it to see what the problem may be. Perhaps if there are any other users with PLC5s here that may be able to test it out and comment on whether it works for them it may help out.
04-14-2009 05:21 PM
04-14-2009 06:33 PM
There should be no issues building this into an EXE. The only requirement should be getting the driver's DLL onto the remote system. If you are running into other errors it may be due to not building all the LabVIEW support VIs you need into the EXE. You may want to verify that all the VIs from vi.lib that you are using are included and such.
As you said, one way to get the DLL installed is by running the installer on the system. I have to admit that I have not tested running the installer on a machine with only the LabVIEW runtime installed so it is possible that the installer ends up finding nothing to install since there are no supported versions of LabVIEW (though you may be able to force it by manually selecting some version of LabVIEW to install support for). You can confirm this by checking for
Another option you could try is to place the
04-23-2009 12:09 PM
I was just checking in to report this build issue. I have the same issue. The ethernerIPInterface.dll is in the build but does not get installed to the system32 folder. Tried several build configs but no luck. I manually had to install the dll.
04-23-2009 01:51 PM
Where are you getting the DLL to install manually? Is it possible that it is not in System32 because you are running on a 64-bit OS? If so, the installer will put it into the SysWoW64 directory.
04-24-2009 09:08 AM
04-24-2009 09:27 AM
04-24-2009 09:32 AM
Hi JF3M and dazach,
It doesn't look like LabVIEW will automatically pull SystemRoot-based DLLs into an installer. However, as you found out, you can tell it to do so manually and put it alongside the EXE and it will work.