# Catching short pulses (tripps) in Ignition

**URL:** <https://forum.inductiveautomation.com/t/catching-short-pulses-tripps-in-ignition/30426>\
**Category:** Ignition Early Access\
**Created:** [December 4, 2019, 6:42am UTC](https://forum.inductiveautomation.com/t/catching-short-pulses-tripps-in-ignition/30426 "2019-12-04T06:42:34Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mik977](https://avatars.discourse-cdn.com/v4/letter/m/5f8ce5/32.png) [@mik977](https://forum.inductiveautomation.com/u/mik977)\
**Post date:** [December 4, 2019, 6:42am UTC](https://forum.inductiveautomation.com/t/catching-short-pulses-tripps-in-ignition/30426/1 "2019-12-04T06:42:34Z")

</div>

Short question:

Is it even possible to catch 5-30ms pulses (Boolean going 0-\>1-\>0) coming from the OPC-UA Ignition server? Or from Kepware’s KepserverEx? Ping between IGW and KepserverEx is sub 1ms. Kepware’s OPC QuickClient gets all the pulses right. Ignition’s OPC client not.

I found lower than 100ms Tag Groups work unreliably.