The advent of good remote monitoring is a big plus in this area. My question would be what can be done to automate the response to any events that show up in the monitoring? If the lubricant is monitored for particulates such as metals then any rapid rise in particulate count would indicate a problem. In this case, it would seem there is not much possibility for an automated solution other than to reduce the likelihood of further damage by shutting down the system until the damage to metal parts can be repaired.
In the event the lubricant becomes contaminated it would seem to be a good idea to include a conditioning system to remove contaminates like water if possible. Perhaps this conditioning system operates continuously anyway and then any out of acceptable condition must be addressed with some kind of on-site visit.
Temperature of the lubricant under load is another factor and any system like this presumably has some automatic controls in place to maintain the correct temperatures. It might be possible to monitor this system so that any increase in coolant flow over time can be detected. This would help in predicting deterioration or some other adverse effect in the temperature monitoring and controls. If the amount of cooling is steadily increasing the automatic system is adjusting to the condition correctly. However it would be good to know in advance when the ability to increase cooling was about to reach a limit.
I recall a proposed system design using Helium as the working fluid and as the bearing lubricant. Since it was a sealed system the claim was made that this could theoretically operate for 30 years without much attention as long as the correct operating conditions were maintained.
Festo's BionicKangaroo combines pneumatic and electrical drive technology, plus very precise controls and condition monitoring. Like a real kangaroo, the BionicKangaroo robot harvests the kinetic energy of each takeoff and immediately uses it to power the next jump.
Design News and Digi-Key presents: Creating & Testing Your First RTOS Application Using MQX, a crash course that will look at defining a project, selecting a target processor, blocking code, defining tasks, completing code, and debugging.
Focus on Fundamentals consists of 45-minute on-line classes that cover a host of technologies. You learn without leaving the comfort of your desk. All classes are taught by subject-matter experts and all are archived. So if you can't attend live, attend at your convenience.