Question: is it possible to use without PLC about node-ethernet-ip HOT 6 CLOSED

The primary purpose of this API is to be used with a Rockwell PLC. That said, you may be able to use some of the lower level classes within the library (CIP, ENIP) as a base for getting something working.

from node-ethernet-ip.

Not sure if I understand correctly, but I assume the vision system supports CIP explicit communication? If so, there must be some sort of datasheet, where the Object model is specified, hopefully including support for Get_Attribute_Single?
If the answer is still yes, I implemented a small patch that should be able to read every CIP Object (Class,Instance,Attr) via Get_Attribute_Single Service.
Can be found in the branch "generic-support".

from node-ethernet-ip.

@bmhgit I believe the vision system supports CIP communication, I'll poke around with your suggestion and see what I get. Did you possibly mean branch "port-support"? I only see 3 branches, master, port-support, and v2.0.0. Didn't see that it was on your fork. Sorry.

from node-ethernet-ip.

@bmhgit So the problem is that the vision system does not recognize my computer as a PLC, and therefore refuses to send any data. When configuring the EtherNet/IP on the vision system, the user manual says it should say communication status: Connected, whereas now it reads Disconnected. When I try to connect using node-ethernet-ip tools, it just hangs on the PLC.connect("xxx.xxx.xxx.xxx", 0).then(async () =>

from node-ethernet-ip.

@emielke12, It will not work out of the box with a vision system. The problem lies in multiple places. First the Controller class is written to accommodate specific objects within Rockwell Controllers thus it does not generalize to other platforms easily. Second, the Enip class that the Controller class is built on utilizes explicit messaging by default.

If you can get access to the Vision System's CIP object references then you may be able to use the underlying generic ethernet/ip API to read/write data to the system in a similar fashion to how the Controller works.

Currently, the underlying API supports Unconnected Explicit messaging, though @bmhgit submitted a PR a while back that adds connected messaging (hopefully Ill be able to get around to pulling it someday 😬)

from node-ethernet-ip.

Closing this issue, though feel free to continue the discussion :)

from node-ethernet-ip.