Read 100+ kepware tags in machine trigger

We have to read more than 100 Kepware tags (fault codes) in a machine trigger to identify the right fault code. Looking for what is the best way to implement this in Tulip.

Writing if/else logic in machine trigger is a painful task but that is the only option we have now and finally we are not getting expected result.

We don’t know how much time it will take to execute the trigger but by the time the execution completes, machine status may be back to RUNNING state and ends up adding the fault code to RUNNING activity record instead of STOPPED activity record. This is one issue.

So, the question here is, Is it good to read these many tags from Kepware (data transfer over network to cloud) and implement the logic in Tulip vs implement the logic at kepware/plc and get the fault code via one tag.

Another question is, these many tags gives any performance issue on tulip instance? We are seeing some lags after implementing this.

Can someone help us to understand what is wrong we are doing here and any alternative approaches you can suggest for this?

Appreciate your help.

1 Like

I would go the plc route that you are thinking about. We have tried to do similar things with having tulip do the logic and for instances where we have status/tag changes in split seconds we found that the machine tags in tulip did not always keep up and sometimes would have a lag. For these cases we either moved the logic to plc or Node-Red. I think the fewer tags you have the better to send through.

1 Like