--- title: Setup registration of unit state using a pulse signal description: "A signal that toggles its value like a pulse, is referred to as blinking:   Go to the Configuration->Data source page: Select the unit you wish to setup the registration for(The units here are exampl" --- [Skip to content](https://kb.dataintel.dk/setup-registration-of-unit-state-using-a-pulse-signal#main-content) English Show submenu for translations [Submit a request](https://kb.dataintel.dk/kb-tickets/new?hsLang=en) ![DIAP-1.png\]](https://kb.dataintel.dk/hs-fs/hubfs/DIAP-1.png?height=41&name=DIAP-1.png) - [Default HubSpot Blog](https://diap-6547305.hs-sites.com/blog) Open main navigation Close main navigation - [Default HubSpot Blog](https://diap-6547305.hs-sites.com/blog) - English Show submenu for translations - [Submit a request](https://kb.dataintel.dk/kb-tickets/new) - Go to Data Intelligence A/S Go to Data Intelligence A/S Hello. How can we help you? - There are no suggestions because the search field is empty. 1. [Help Center](https://kb.dataintel.dk/?hsLang=en) 2. [OEE site](https://kb.dataintel.dk/oee-site?hsLang=en) 3. [Configuration](https://kb.dataintel.dk/oee-site?hsLang=en#configuration) # Setup registration of unit state using a pulse signal ### Introduction - This guide describes how to setup the registration of a unit's state using a signal that toggles it's value like a pulse. ### Blinking A signal that toggles its value like a pulse, is referred to as **blinking:**   ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360021514859mceclip1.png) ### Setup Go to the **Configuration-\>Data source** page: ![](https://kb.dataintel.dk/hubfs/image-png-Jul-02-2021-11-43-17-23-AM.png) Select the unit you wish to setup the registration for(The units here are examples and are different from yours): ![](https://kb.dataintel.dk/hubfs/image-png-Jul-02-2021-11-44-01-88-AM.png) Click the **Add** button: ![](https://kb.dataintel.dk/hubfs/image-png-Jul-02-2021-11-20-09-41-AM.png) Select **Stop bit with blinking**: ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360021507379mceclip0.png) ### Configuration of Stop bit with blinking - **Name:** The name of the event server, that is collecting the data. - **Small stop time**: This is how long a small stop can last in seconds. A stop is consisted a small stop as long as it hasn't lasted longer than this period. - **Small Stop Reason**: This is the stop reason that is used with small stops. - **DIAP Tag**: The DIAP tag is where the unit state data is collected. The structure of the name is  \[DIAP\]-\[PLC\]-\[Tag\] - **Collection old data on startup**: This tells the event server, to start with a months old data from the first read(**Don't active this, because it could lead to data being processed more than once, this is meant for support**). - **Blink interval**: This is how many seconds that may pass before the next changed value should occur to say that the value is blinking(a pulse change) - **Stop reason**: This is the stop reason that is used, when the stop has lasted longer than **Small stop time**. - **Blink type**: This is used to set a unit's state when the data is blinking. The state options are: - **Run**(Blink when running) - **Stop**(Blink when stop) ### DIAP tag data type - **Type:** Double The expected data type is decimal numbers like : 0.0, 0.1,1.0, 1.2 ### Example - Blinking on run: A unit is consisted running as long as its state signal changes value within 20 seconds. This means that the event server's **Blink type** = **Blink when running** and the **Blink interval** = **20**: ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360021513720mceclip2.png)![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360021513740mceclip3.png)   ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360021529819mceclip5.png) ### Example - Blinking on run and with stop causes: With the same setup as the previous example, we now consider stop causes. Let's say, that as long as the stop doesn't last longer than 60 seconds, then it is a small stop, with stop cause **Small stop** after that the stop is no longer a small stop and it will have stop cause **Machine stopped**. This means that the event server's **Small stop time = 60**, **Small Stop Reason = Small Stop** and **Stop reason = Machine stopped**: ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360021530239mceclip8.png)![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360021530059mceclip7.png)![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360021528020mceclip11.png)   ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360021528180mceclip13.png) ### Example - Configure stop bit with blinking  Select a name for the event server, that is collecting the data. Here we called it "Run pulse": ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360021528520mceclip14.png) Set how long a small may last in seconds. Stops that last to this period and not longer, are consisted small stops. Here we sat it to 60 seconds: ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360021528600mceclip15.png) Select a small stop reason, when a small stop is created, it uses this stop reason. Here we used "Small Stop": ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360021530819mceclip16.png) Select the DIAP tag, where the data comes from. Here we selected "dev00225 - Demo - Tag 1" ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360021528680mceclip17.png) Skip Collect old data on Startup, it should be turn off: ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360021528720mceclip18.png) Set how many seconds may pass before the next changed value should occur for considering the signal to be blinking. Here we set it to 20 seconds: ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360021531059mceclip19.png) Select the stop reason, that will be used, when the stop has lasted longer than **Small stop time**. Here we selected "Machine stopped": ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360021531119mceclip20.png) Set state for when the signal is blinking **Run** or **Stopped**. Here we set it to **Run**(**Blink when running**): ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360021528900mceclip21.png) When you are done, the configuration should look something like this(But with your values): ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360021531419mceclip22.png) Click **Save** to save the configuration: ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360037673894mceclip11-Feb-23-2021-12-28-34-22-PM.png) Now you have a configuration for setting the state on a unit with a pulse signal. ### Start collecting data When you have made your configurations in the **Data source**, then you need to start the event server for the configuration, so the data get collected. Go to the **Configuration-\>Data source status** page: ![](https://kb.dataintel.dk/hubfs/image-png-Jul-02-2021-11-47-27-99-AM.png) Select your unit: ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360038505433mceclip13-Feb-23-2021-12-28-35-71-PM.png) Click the switch for the event server with the configuration: ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360021531699mceclip23.png) Then the light turns green and the Last run timestamp is updated, when your event server has run your configuration for the first time: ![](https://kb.dataintel.dk/hubfs/Knowledge%20Base%20Import/eltronic.zendesk.comhcarticle_attachments360038507553mceclip14-Feb-23-2021-12-28-37-29-PM.png) That it. Now your configuration are done and you are collecting data. - [DIAP Gateway](https://kb.dataintel.dk/diap-gateway?hsLang=en#main-content) - [Getting Started](https://kb.dataintel.dk/diap-gateway?hsLang=en#getting-started) - [Troubleshooting](https://kb.dataintel.dk/diap-gateway?hsLang=en#troubleshooting) - [Known issues/limitations](https://kb.dataintel.dk/diap-gateway?hsLang=en#known-issues-limitations) - [General](https://kb.dataintel.dk/general?hsLang=en#main-content) - [FAQ](https://kb.dataintel.dk/general?hsLang=en#faq) - [Configuration](https://kb.dataintel.dk/configuration?hsLang=en#main-content) - [FAQ](https://kb.dataintel.dk/configuration?hsLang=en#faq) - [Troubleshooting](https://kb.dataintel.dk/configuration?hsLang=en#troubleshooting) - [Guides](https://kb.dataintel.dk/configuration?hsLang=en#guides) - [Protocols](https://kb.dataintel.dk/configuration?hsLang=en#protocols) - [Live/Real time site](https://kb.dataintel.dk/live-real-time-site?hsLang=en#main-content) - [Getting Started](https://kb.dataintel.dk/live-real-time-site?hsLang=en#getting-started) - [FAQ](https://kb.dataintel.dk/live-real-time-site?hsLang=en#faq) - [Guide](https://kb.dataintel.dk/live-real-time-site?hsLang=en#guide) - [Features](https://kb.dataintel.dk/live-real-time-site?hsLang=en#features) - [OEE site](https://kb.dataintel.dk/oee-site?hsLang=en#main-content) - [Getting Started](https://kb.dataintel.dk/oee-site?hsLang=en#getting-started) - [FAQ](https://kb.dataintel.dk/oee-site?hsLang=en#faq) - [Guides](https://kb.dataintel.dk/oee-site?hsLang=en#guides) - [Configuration](https://kb.dataintel.dk/oee-site?hsLang=en#configuration) - [Remote Access](https://kb.dataintel.dk/remote-access?hsLang=en#main-content) - [Getting Started](https://kb.dataintel.dk/remote-access?hsLang=en#getting-started) - [FAQ](https://kb.dataintel.dk/remote-access?hsLang=en#faq) - [Guides](https://kb.dataintel.dk/remote-access?hsLang=en#guides) - [API](https://kb.dataintel.dk/api?hsLang=en#main-content) - [API](https://kb.dataintel.dk/api?hsLang=en#api) - [Release information](https://kb.dataintel.dk/release-information?hsLang=en#main-content) - [DIAP Release Notes](https://kb.dataintel.dk/release-information?hsLang=en#diap-release-notes) - [Live/Real time site](https://kb.dataintel.dk/release-information?hsLang=en#live-real-time-site) - [OEE site](https://kb.dataintel.dk/release-information?hsLang=en#oee-site) - [Management site](https://kb.dataintel.dk/release-information?hsLang=en#management-site) - [DIAP Gateway](https://kb.dataintel.dk/release-information?hsLang=en#diap-gateway) - [Default HubSpot Blog](https://diap-6547305.hs-sites.com/blog) [![Chill listening crop-3](https://kb.dataintel.dk/hs-fs/hubfs/Sk%C3%A6rmbillede%202021-05-04%20kl.%2017.46.04.png?width=221&height=26&name=Sk%C3%A6rmbillede%202021-05-04%20kl.%2017.46.04.png "Chill listening crop-3")](https://diap.hubspotpagebuilder.com/-temporary-slug-5b226bcb-69c8-45c1-82ff-e060e2d4037d?hsLang=en) Copyright © 2026, Data Intelligence A/S