<?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 Precomputing.com</title>
    <link>https://precomputing.com/tags/industrial-monitoring/</link>
    <description>Recent content in Industrial Monitoring on Precomputing.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 01 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://precomputing.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://precomputing.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://precomputing.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>
    <item>
      <title>AltSql Vector Teaches a Device What a Healthy Motor Sounds Like, in 32-Byte Fingerprints</title>
      <link>https://precomputing.com/altsql-vector-teaches-a-device-what-a-healthy-motor-sounds-like-in-32-byte-fingerprints/</link>
      <pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://precomputing.com/altsql-vector-teaches-a-device-what-a-healthy-motor-sounds-like-in-32-byte-fingerprints/</guid>
      <description>&lt;p&gt;A vibration sensor on a motor hears a lot. Most of it is the motor doing its job. The useful part is the moment the sound changes into something new, like a bearing starting to wear. Sending every sample to a server to find that moment costs bandwidth the device often does not have.&lt;/p&gt;&#xA;&lt;p&gt;AltSql Vector lets the device do the listening. Every 1.6 seconds it splits what it hears into 32 frequency bands and turns that into a fingerprint of 256 bits, which is 32 bytes. It keeps fingerprints of the states it has been taught, such as idle, running and loaded. For each new fingerprint it finds the closest one it knows and names the state. When nothing it knows is close enough, it flags the pattern as one it was never taught.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AltSql Wave Keeps Raw Vibration Bursts on the Device, Lossless, and Sends Only Their Features</title>
      <link>https://precomputing.com/altsql-wave-keeps-raw-vibration-bursts-on-the-device-lossless-and-sends-only-their-features/</link>
      <pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://precomputing.com/altsql-wave-keeps-raw-vibration-bursts-on-the-device-lossless-and-sends-only-their-features/</guid>
      <description>&lt;p&gt;When a pump&amp;rsquo;s bearing starts to fail, an analyst wants two things. A quick figure to spot it, and the raw signal to understand it. Devices usually keep one or the other. They send summary figures and throw the signal away, or they send the signal and pay for every byte of it.&lt;/p&gt;&#xA;&lt;p&gt;AltSql Wave keeps both. A sensor records a short burst of vibration, compresses it without losing a bit and stores it on the device, where the bursts stay for as long as its flash holds them. While the samples arrive, it works out the figures an analyst looks at first, such as RMS, peak and kurtosis, and the level in a few frequency bands. Only those figures go to the gateway, where SQL can search them. When a row looks interesting, the gateway fetches the raw burst behind it, checked against its CRC-32.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
