# Visibility of label component to blink **URL:** \ **Category:** Ignition\ **Tags:** vision\ **Created:** [August 6, 2020, 10:45pm UTC](https://forum.inductiveautomation.com/t/visibility-of-label-component-to-blink/37483 "2020-08-06T22:45:29Z")\ **Posts on this page:** 1\ **Showing post:** 9
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [August 7, 2020, 8:08pm UTC](https://forum.inductiveautomation.com/t/visibility-of-label-component-to-blink/37483/9 "2020-08-07T20:08:12Z")
I should mention, the reason I put into a client timer script is because I have various pulses defined, 125, 250,500,1000,2000ms I really only use the 500ms and it was easier to calculate these via script than expression. If you don't need pulses faster than a second, you can certainly do as @bpreston says. Fyi this is what I use: > [@Generate 0.5s and 0.25s pulse tag](http://forum.inductiveautomation.com/t/generate-0-5s-and-0-25s-pulse-tag/20391/4): > > Thanks for the replies. I ended up using client tags and a client script: # Set this to the script execution time period in ms timeInterval = 125 # Time to count up to in ms. This affects the times pulses that may be generated counterPeriod = 2000 tag = "[Client]System/Pulses/125ms Counter" counter = system.tag.read(tag).value # Increment the 125ms counter tag if the time is within the counterPeriod time, otherwise reset to 0 if counter \> (counterPeriod/timeInterval - 1): system.tag.write(t… --- _[View the full topic](https://forum.inductiveautomation.com/t/visibility-of-label-component-to-blink/37483)._