# Help to modify rbe "node-red-contrib-cip-st-ethernet-ip" **URL:** \ **Category:** Node-RED\ **Created:** [October 17, 2024, 6:13pm UTC](https://www.wago.community/t/help-to-modify-rbe-node-red-contrib-cip-st-ethernet-ip/1258 "2024-10-17T18:13:02Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Hector\_Edge](https://avatars.discourse-cdn.com/v4/letter/h/8dc957/32.png) [@Hector\_Edge](https://www.wago.community/u/Hector_Edge)\ **Post date:** [October 17, 2024, 6:13pm UTC](https://www.wago.community/t/help-to-modify-rbe-node-red-contrib-cip-st-ethernet-ip/1258/1 "2024-10-17T18:13:02Z")
I tried to modifying the **“node-red-contrib-cip-st-ethernet-ip”** node **to get “ALL TAGS” every cycle time** , but I have not been successful. Currently the node works only rbe (Report By Excpetion) The node blocks unless the incoming value changes, and this is not good when you want to reconstruct the complete history of a variable (Tag). I have tried to modify the .js file but when I think I have done it after a couple of hours node red crashes in different ways. Has anyone already worked on this modification? ---
**Author:** ![WagoKurt](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/wagokurt/32/11_2.png) [@WagoKurt](https://www.wago.community/u/WagoKurt)\ **Post date:** [December 6, 2024, 1:01am UTC](https://www.wago.community/t/help-to-modify-rbe-node-red-contrib-cip-st-ethernet-ip/1258/2 "2024-12-06T01:01:01Z")
Hello, you can use a state machine to read the list of desired tags. If you pass a message to the eth-ip-in node, the topic can request a tag by name. So, just create a global list of the variable names, and then write a state machine that requests each variable one at a time. This will read the values quite fast in practice. Setting the node to ALL doesnt work very well in my experience, it times out due to too many connections being made to the Rockwell PLC (i think).