Node-red-contrib-cip-st-ethernet-ip cycle time not respected

I have been using node-red-contrib-s7 to read tags from Siemens PLCs and I define a reading cycle time. Each cycle generates an object with the tags and enters in the flows correctly. However, when using the equivalent node node-red-contrib-cip-st-ethernet-ip to read tags from a Rockwell PLC, I notice that the cycle time is not respected, and the reading is done without a predicted time.

Thanks,

Roberto

It's been done time since I used that node but I suspect it does one of 2 things...

  1. Make implicit messaging & so only send data upon PLC changes (i.e. truly event based)
  2. Uses explicit messaging (polling for values) but only Enid when it notices a value change (pseudo event based)

In other words I think you only get values upon change (not at every poll)

I may be misremembering.