we published yesterday this new node for communication between node-red and Allen Bradley PLCs by using the "EtherNet/IP" protocol:
Could you please index it into the node palette?
This node is similar to our famous https://www.npmjs.com/package/node-red-contrib-s7 node
I will add it to the index, although I would suggest the name could be improved. "Ethernet" and "IP" are very generic terms and there's no suggestion it has anything to do with a particular brand of PLCs.
Actually it's not specifically for Allen Bradley PLCs. It is a generic implementation of the industrial EtherNet/IP Protocol (https://en.wikipedia.org/wiki/EtherNet/IP ) which is commonly used by AllenBradley and Rockwell PLCs, I mean, this was just an example.
I think Nick was suggesting you use something more than ethernet/IP - like node-red-contrib-cip-to-ethernet-ip.
I got your point, but since the node was based on the https://github.com/cmseaton42/node-ethernet-ip we wanted to keep the name to make it easier to find.
In what way does
node-red-contrib-cip-to-ethernet-ip not 'keep the name' any more or less than the name you have chosen? It still has
ethernet-ip in it, but it has a tiny bit more context to help users understand.
Do you expect your primary users of the node to be already experienced enough with node.js to be aware of the
Thanks for the naming suggestion, I agree the name can be improved. But as CIP is technically a super-set protocol of EtherNet/IP, I'd say it may look grammatically strange to name it
...cip-to-ethernet-ip. Instead, what do you think about
node-red-contrib-cip-ethernet-ip or then simply
node-red-contrib-ethernet-ip-client doesn't tell you anything it's relationship to cip where
Someone who searches for 'cip' will find
node-red-contrib-cip-ethernet-ip and have a good idea that it might be useful. I'd vote for that one.
I guess it depends how much time you have to field all the "it's not working" issues from people who won't read the readme and have a Pi with ethernet and an IP...
Putting cip in the name of the node should stop that
Indeed. Not everybody knows that EtherNet/IP is a protocol and not just one's internet cable that has an IP. I'll rename everything then to 'node-red-contrib-cip-ethernet-ip', then I'll come back so it can be indexed in the flows library.
Whoever thought of calling the protocol that in the first place needs to be publicly shamed.
Guilherme if you edit your first post, you can change the title
This node is awesome! Any way to get it to work for string data?
Hello @gfcittolin the cip node works great. Are there any plans to have is support string data types or am I missing something obvious...sorry newbie here...
Hi @jewendt, great that you liked it!
String support is something that we also want Currently, the underlying
node-ethernet-ip library doesn't support it, there's even an issue regarding this lack of support.
Thery're open for pull requests there. As soon as we have a bit more time here, if nobody does that first, we'll try to create a pull request for them with the support for strings.
Looks they are working on the library. @gfcittolin are you keeping up with what the are doing? Will the node red automatically inherit the underlying functionality or is there something that you need to do get Node Red node to work. Sorry for the newbie question...
I'm watching it, that's a starred GitHub repo of mine
Due to npm's
package-lock.json it probably won't pick up automatically, as it is locked down to the current version. But as soon as they release a new version we'll test it and release a new version with the improvements.
Hi all, I am new to this, i have installed node-red-contrib-cip-ethernet-ip, but i dont have anything showing in my nodes within node-red, any ideas ?
the node is visable from the pallet, but looks like it is disabled