Fluke Connect tools are very handy connectable tools that can share measurement data between various test and measurement tools and your smartphone. It’s an evolving system, and I believe Fluke has been heading in the right direction.
Earlier today I received an email introducing Fluke Condition Monitoring tools, which looks to be a side branch from the Tool Connect system.
The tools look to do much of the same things, but are more designed as left-in-place sensors.
This makes a lot of sense, from both functionality and cost standpoints. While there isn’t much technical or sales data available, I’m going to guess that the new sensors, which don’t look to have any built-in displays, will cost less than comparable multimeters.
Plus, you can use Fluke tech and sensors that you already own – such as iFlex current clamps, other current clamp leads, and probes.
This diagram shows the intent differences between Fluke Connect and Fluke Condition Monitoring tools.
Whereas Fluke Connect tools can communicate with your smartphone, it looks like a gateway is needed to connect the monitoring sensors to the “Fluke Cloud.”
Here’s what you can measure:
- AC and DC voltage
- AC and DC current
Measurements can be taken and recorded as frequently as once per second, for “over a month at a time.”
You can receive real-time alerts via text messages or emails when readings go beyond pre-set parameters.
For example, let’s say you have a motor that optimally runs at 85°. Having temperature, voltage, and current sensors, or a combination of sensors, can give you a picture of what’s going on.
Fluke Connect tools are useful for diagnosing problems as they arise, and for gathering routine measurements to establish a baseline, but it seems like the monitoring sensors could tell you when a problem occurs. To my understanding, it can also provide you with a short history of measurements, which might help to paint a clearer story.
This is how I’m understanding the system, forgive me if I’m wrong. I’m pairing together limited information with how I understand the current Fluke Connect system works.
You could potentially use Fluke Connect tools in a similar manner, to log measurements over time, but I don’t think that’s how they’re meant to be used.
Fluke also says:
Best of all, it installs in a matter of minutes so you can place the sensors, diagnose an issue, and move on to the next piece of equipment.
That part confuses me, as the purpose of pre-set parameters and alarms is more congruent with leave-in sensors, and not test-and-go sensors. Diagnose-and-move-on seems to be better suited for the Fluke Connect tools.
This part of their product discussion makes more sense to me:
Each wireless sensor sends measurements every second, giving you a history of equipment performance before, during and after an event, allowing you to make preventive maintenance decisions.
That’s exactly what I imagined Fluke Condition Monitoring was meant for when I first opened the announcement email.
Several sensors are launching with the new line, all being aimed towards industrial applications.
As an aside, wouldn’t it be interesting if Fluke followed Flir, one of their competitors, and entered the consumer equipment market? There is a lot of potential there, for various sensors around the home. I’d love to see Fluke water, temperature, voltage, and current sensors that could be placed around the home and set to ping my smartphone if conditions went outside normal limits.
Fluke Condition Monitoring Products:
- AC voltage sensor, 3510 FC
- DC voltage sensor, 3511 FC
- AC current iFLex sensor, 3520 FC
- DC 2000A current sensor, 3521 FC
- K-Type temperature sensor, 3530 FC
- Gateway, 3501 FC
The gateway can stream data from up to 10 Fluke 3500-series sensors to the Fluke Cloud, via a wired or wireless network connection. It can store up to 3 months of measurement data, for disconnected applications.
The gateway also has a WiFi interface and can communicate with Android and iOS devices via the Fluke Connect app.
It has a Li-ion battery backup, in case of power disruptions.
More Info(via Fluke)