I have motors and pumps we'd like to start gathering general vibration data on for use in predictive maintenance. in the ~ 1000rpm, 10kW class.
I'm looking for a digital-output vibration sensor that I can read from in "some documented way from" a ~ linux PC:
As an example, take the IFM VVB001. This meets all those requirements EXCEPT requires an IOLink master, adding about $200 to each sensor all-in and complicating the wiring/install and failure points. But it does provide access to the point values at ~100ms cadence or faster, as well as supporting dumping a couple seconds of waveform for deeper analysis over the same bus.
Our edge ~gateways are linux-based PC's, used to talking "open" protocols to devices over protocols that don't require "vendor gateways" to gather and interpret the results. On the simple end that's just modbus/rs485/various protocols over TCP/IP. On the slightly more complex end that's SAE protocols over CAN, or custom (but documented) protocols over Bluetooth.
I am not finding anything better than the IFM IOLink device above. Most seem to require a full proprietary path to the cloud, which doesn't fit for how we need to use & access the data in the future.
Thank you!
I'm looking for a digital-output vibration sensor that I can read from in "some documented way from" a ~ linux PC:
- Must:
- Fannout/connection: no proprietary edge "gateway" device required, eg a full PC or PLC in it's own right that would require a cloud connection for vendor updates or data access. Implies data format must be documented (any of open/standard, publicly documented, under NDA, etc)
- data: read at reasonable latency (1sec~10sec): the standard "point values" of velocity & acceleration peak & RMS in order to provide a "live view" dashboad
- Strongly preferred:
- fannout: no "bus masters" required beyond standard PC interfaces such as rs485, TCP/IP, Bluetooth, etc.
- data: ability to dump on-demand / infrequently the full waveform (pre FFT) or spectrum (either works) for more detailed analysis. This may interrupt sensor operation to perform the download; may take 10's of seconds to download.
As an example, take the IFM VVB001. This meets all those requirements EXCEPT requires an IOLink master, adding about $200 to each sensor all-in and complicating the wiring/install and failure points. But it does provide access to the point values at ~100ms cadence or faster, as well as supporting dumping a couple seconds of waveform for deeper analysis over the same bus.
Our edge ~gateways are linux-based PC's, used to talking "open" protocols to devices over protocols that don't require "vendor gateways" to gather and interpret the results. On the simple end that's just modbus/rs485/various protocols over TCP/IP. On the slightly more complex end that's SAE protocols over CAN, or custom (but documented) protocols over Bluetooth.
I am not finding anything better than the IFM IOLink device above. Most seem to require a full proprietary path to the cloud, which doesn't fit for how we need to use & access the data in the future.
Thank you!