With the recent release of Node-RED on the edge gateways, it would be very helpful if we could have a node that would act as an input and/or output to and from Tulip (some kind of trigger node).
Great suggestion and we have a few related ideas in the works. Very soon (a few releases) there will be a new API endpoint in Tulip to allow you to send data to Tulip Machines. This can then be used from Node-RED or any other programming language. After that we will have specific Tulip nodes that make this even easier. Data coming through this endpoint will be available as Machine Attributes and can be used to drive machine state or trigger events from within Apps.
Currently, you can use Connectors to trigger Node-RED flows. If your NR flow has ‘HTTP In’ as a node, you can then create a Connector Function in Tulip to kick things off from an App. To enable this, use the EdgeMC as the ‘Connector Host (Running On)’ when setting up the Connector. We don’t have immediate plans for creating a Tulip Node here, but will certainly consider it!
Are these options in line with what you are thinking?
What you have described is in line with my initial thoughts. Look forward to seeing what’s possible with the use of Node-RED!
Just a me too, but having the NodeRED nodes available outside of the Edge MC or upcoming device would be very welcomed.
Here’s a specific use case:
We are evaluating the Opto 22 groov Rio for use as a TPM device by collecting data from equipment. It has a highly configurable I/O capability, NodeRED built in, and even PoE in a very small package.
I can open up a CNC Mill cabinet, grab the Ethernet going to the controller, plug it in to the Rio’s PoE port, and then add a patch cable from the Rio’s second port (2 port switch) back to the Mill. Then I only need to hook up the sensors (current draw, vibration, temperature, etc) and configure the inputs in NodeRED, and if I had the Tulip API node, easily get all then information logged into Tulip.