<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Industrial Monitoring on AltSql.com</title>
    <link>https://altsql.com/tags/industrial-monitoring/</link>
    <description>Recent content in Industrial Monitoring on AltSql.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 28 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://altsql.com/tags/industrial-monitoring/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Machine Monitoring Case Study: Overheat Alarm Handled on the Sensor While Wi-Fi Was Down</title>
      <link>https://altsql.com/machine-monitoring-case-study-overheat-alarm-handled-on-the-sensor-while-wi-fi-was-down/</link>
      <pubDate>Mon, 28 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://altsql.com/machine-monitoring-case-study-overheat-alarm-handled-on-the-sensor-while-wi-fi-was-down/</guid>
      <description>&lt;p&gt;A temperature sensor on a machine takes one reading a second. When the machine runs hot, the fan has to come on right away, whether or not the plant&amp;rsquo;s Wi-Fi is working. In the Alpha demo this device runs the AltSql engine on 64 KB of flash with 1,048 bytes of engine RAM, and it makes that call by itself.&lt;/p&gt;&#xA;&lt;p&gt;The run covers one simulated hour. Wi-Fi drops out from minute 20 to minute 35. Two gateways listen: gateway A receives every record, and gateway B, which stands in for a constrained link, receives only the minute summaries and the fan state.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
