SIGNL4

Mobile Alerting and Anywhere Incident Response

SIGNL4
  • Product
    • Feature Overview
    • On-Call Management
    • Mobile Alerting App
    • Why SIGNL4
    • First Steps
    • Security, Data Privacy & GDPR
    • Online Help & FAQ
    • Blog and what’s new
    • System Status
  • Use Cases
    • IT Alerting
    • SIEM & SecOps Alerting
    • IoT Service Alerting
    • Industry 4.0 Maintenance Calls
    • After-Hours Service Desk
    • Field Service Dispatching
    • Emergency Alerting
  • Integrations
  • Pricing
  • Company
    • About
    • Partner Program
    • Podcast
    • Media
    • Contact us
    • Newsletter
  • Free Trial
  • My Account
  • Deutsch

Inspiration

  • Home
  • Inspiration
  • Integrations
  • Real-time mobile alerts for monitoring of dry contacts with Web-IO from Wiesemann & Theis

Real-time mobile alerts for monitoring of dry contacts with Web-IO from Wiesemann & Theis

  • By Ronald
  • October 5, 2018
  • IntegrationsManufacturingOT & IoT
Real-time mobile alerts for monitoring of dry contacts with Web-IO from Wiesemann & Theis

Machines, pumps, valves, fire alert systems, temperature sensors, smoke detectors, etc. often do not offer IT integration. Instead, they provide simple analog cables to interface with dry contacts. Monitoring these I/O states and detecting abnormal behavior or malfunctions a common scenario in industrial IoT.

Operations teams in charge of business and operational continuity need to know any abnormal behavior in order to take immediate action. Having information available on a dashboard is often not sufficient and they might roam the shop floor or are away from the operations control room fixing machines and systems. Any critical information or alert needs to reach responsible staff  immediately no matter where they are.

This is where SIGNL4 comes in. The app-based alerting solution ensures that the right people get actionable and enriched information at the right time and wherever they are.

Here, we describe how to use a hardware device to detect analog I/O states and then to use SIGNL4 for mobile real-time alerting.

Device overview

A robust device for industry usage is the “Web-IO 4.0 Digital, 2xIn, 2xOut” from Wiesemann & Theis GmbH in Wuppertal, Germany (https://www.wut.de/e-57737-ww-daus-000.php). Let’s have a look how to connect it to SIGNL4.

The device is only about 4 x 1 x 3 inch in size. It comes with a small screwdriver and a detailed and very helpful manual.

 

Setting up the device is simple and self-explanatory. For difficult network situations, the manufacturer provides helpful tips and tricks on how to finally reach the configuration interface of the device.

The small connector strip on the side of the device provides two inputs. If you want to monitor the state of a dry contact, you can connect a 24 Volt power supply. In our scenario we use the input labeled “Input 0”. The connection to the switch, which can interface with a machine interface, is connected to pin “+” and “Input 0”. The switch simple connects or disconnects the two pins.

Connecting Web-IO to SIGNL4

This condition (connected / disconnected) of the input channel is detected by the Web-IO and can lead to various types of actions. In our case we simply use the email channel to send the data to SIGNL4. To enable this action, you can configure the SIGNL4 SMTP server in the Web-IO device as shown below.

In the Actions section you can then configure to send the email to the SIGNL4 email address associated to your team in case the switch is connected, disconnected or in both cases.

You can freely configure the email text and subject line with placeholders so the signal in SIGNL4 appears like you need it.

In our case we use the following subject line:

<in0> switched to <i0> (count: <c0>) on <dn> (<$ y> – <$ m> – <$ d> <$ h>: <$ i>: <$ s>)

And the message text likes like this:

system: “sensor”
time: “<$ y> – <$ m> – <$ d> <$ h>: <$ i>: <$ s>”
device: “<dn>”
channel: “<in0>”
status: “<i0>”
count: <c0>

Using above format ensures that SIGNL4 discovers parameters in the email body and renders those as detail cards.

Placeholders are the following values:
<in0> = name of the first input channel
<i0> = switching state of the first input channel
<c0> = count of the first input channel
<dn> = device name
<$y> = year
<$m> = month
<$d> = day
<$h> = hour
<$i> = minute
<$s> = second

Those placeholders are replaced with the corresponding values ​​before the email is sent. If you now connect the switch or close the dry contact you will receive the signal in the SIGNL4 app.

About SIGNL4

SIGNL4 can notify via mobile push, text and voice calls. It tracks acknowledgements  and escalates automatically if required. Learn more about features of SIGNL4

 

Assemble your SIGNL4 team today!

*Sign up free, no Credit Card required

 

      

Tagged

dry contactsIndustrie 4.0IoT

Share

Related Posts

Remote Actions for IT Remediation, IoT Actions and more

July 25, 2022

Derdack SIGNL4 Joins Microsoft Intelligent Security Association (MISA)

May 17, 2022

Integration Options with SIGNL4

February 10, 2022

Building Automated Monitoring with Icinga and SIGNL4

October 19, 2021

Why SIGNL4?

SIGNL4® reliably notifies mobile operations teams and provides for a 10x faster response to critical alerts, major incidents and urgent service requests. Read more

 

Most Popular

  • Being a powerful ‘pager app’ SIGNL4 ca...
  • Microsoft Flow – send mobile Alert Notificat...
  • Geofencing Alerts with Automate or Tasker
  • Website Down Alert Notifications AWS CloudWatch Alarms to your mobile phone during...
  • Maintenance Call Machine Breakdown Maintenance Call using the AWS I...
  • Paging App Android settings for making SIGNL4 an even better...
  • Code Webhook CSharp C# C# code for the SIGNL4 webhook
  • Setting up the AWS IoT Button – and SIGNL4

FOLLOW US

  • Twitter
  • LinkedIn
  • Facebook
  • Vimeo

CATEGORIES

  • Communication (11)
  • Customer References (1)
  • Developer (11)
  • DevOps (12)
  • General (105)
  • Healthcare (1)
  • Integrations (24)
  • ITOM & ITSM (21)
  • Manufacturing (8)
  • OT & IoT (21)
  • Security (5)
  • Updates (32)

Tags

alert alert management alerts Android Application Insights Automate AWS IoT Button Azure B2B software c# Call Routing do not disturb Duty Scheduling emergency escalation Field Services geofencing handover Hotline ifttt Industrie 4.0 IoT IT Alerts IT Operations ITSM location Manufacturing Monitoring mute override on-call duty On-call Scheduling oncall duty Pager paging app press release SaaS splunk Tasker temperature voice voice recognition weather webhook Website zapier

ABOUT US

Derdack® is a long-standing innovator for enterprise-class mobile alerting and alert management solutions. Our global customer list includes The Boeing Company, Daimler, BMW, Porsche and many other leading brands. With SIGNL4® we have reinvented mobile alerting and alert management for operations teams in IT, IoT, Industry 4.0 and other areas where swift response to critical events matters.

SIGNL US

Phone +1 (202) 4 700 885
Intl +49 331 29878-20
CH +41 31 539 19 90
Email info (at ) signl4.com
Feedback online
Newsletter Sign-up

© 2023 - Derdack SIGNL4

  • Twitter
  • LinkedIn
  • Vimeo
  • GitHub
  • Feedback
  • About
  • Terms of Use
  • Privacy Policy (Website)
  • Cookie Policy (EU)
  • Product
    • Feature Overview
    • On-Call Management
    • Mobile Alerting App
    • Why SIGNL4
    • First Steps
    • Security, Data Privacy & GDPR
    • Online Help & FAQ
    • Blog and what’s new
    • System Status
  • Use Cases
    • IT Alerting
    • SIEM & SecOps Alerting
    • IoT Service Alerting
    • Industry 4.0 Maintenance Calls
    • After-Hours Service Desk
    • Field Service Dispatching
    • Emergency Alerting
  • Integrations
  • Pricing
  • Company
    • About
    • Partner Program
    • Podcast
    • Media
    • Contact us
    • Newsletter
  • Free Trial
  • My Account
  • Deutsch
Manage Cookie Consent
We use cookies to optimize our website and our service.
Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
Manage options Manage services Manage vendors Read more about these purposes
View preferences
{title} {title} {title}