plcpeople
commented
7 years ago You will not be able to use this package unless you map a tag as an old-style "register". Say air_pressure is a floating point, then you would go to Communications menu, Map PLC5/SLC messaging, and map air_pressure to file 20. Then request F20:0 using nodepccc and it should work. For a lot of tags you would want to map them to an array.
I realize this is not ideal but I have not had a customer willing to subsidize the work to implement the CIP protocol yet. I was able to request a few tags from a ControlLogix as a "proof of concept" but did not get any farther, unfortunately. But if this is implemented, it will be separate from NodePCCC.
aguilared
Regards, I have reviewed the code JS and I noticed that only make reference to the PLC SLC and SLC TAGS are written format. I have a 5000 ControlLogix L62, as NodePCCC use the library. As it gives me error with the name of the TAGS.
Run logs: [26342,640543399] Initiate Called - Connecting to PLC with address and parameters: [26342,642161528] { port: 44818, host: '192.168.0.27', routing: [ 1, 0, 1, 0 ] } [26342,645670629] Connection cleanup is happening [26342,647648806 192.168.0.27] Attempting to connect to host... [26342,650936363 192.168.0.27] TCP Connection Established to 192.168.0.27 on port 44818 - Will attempt EIP Connection [26342,655129009 192.168.0.27] EIP Register Session Response Received - connection confirmed [26342,655552538 192.168.0.27] Session Handle is 0x13023F00 [26342,655843654] Translation OK [26342,656546115 192.168.0.27] Adding air_pressure [26342,657363676] Error - String Couldn't Split Properly. For SLC Addressing it needs a : to be valid. [26342,657497371] Dropping an undefined request item. PS C:\node\nodepccc>