# Pulsing outputs

**URL:** <https://forum.inductiveautomation.com/t/pulsing-outputs/92044>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [June 18, 2024, 6:22pm UTC](https://forum.inductiveautomation.com/t/pulsing-outputs/92044 "2024-06-18T18:22:44Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Felipe\_CRM](https://avatars.discourse-cdn.com/v4/letter/f/dfb087/32.png) [@Felipe\_CRM](https://forum.inductiveautomation.com/u/Felipe_CRM)\
**Post date:** [June 18, 2024, 6:30pm UTC](https://forum.inductiveautomation.com/t/pulsing-outputs/92044/2 "2024-06-18T18:30:24Z")

</div>

The cleanest way would probably be to create a flashing CSS style like in this post:

> [@How to run a script continuously to update tags](https://forum.inductiveautomation.com/t/how-to-run-a-script-continuously-to-update-tags/92018/6):
>
> You'll just have to add a little map transformation that acts like a NOT gate. This can still be done without scripting. For the flashing, you can make an animated style like in the below example. Simply enable this style when either of those alarms are active. It really, really sounds like you can get rid of any startup scripts that drive this behavior and replace them with a tag binding combined with a transformation.

That would automatically loop as long as 'infinite' is checked.

Then, you put an expression binding on `props.style.classes`:

```python
if({mytag}, 'flashing', '')

```

assuming your CSS style class is called `flashing` and your tag is `mytag`. Adjust the names to fit your situation.

---

_[View the full topic](https://forum.inductiveautomation.com/t/pulsing-outputs/92044)._