Skip to main content

@ptitude Observer Master Slave solution

I would like to SKF release version of @ptitude Server where the software can be installed as Slave Client in addition to Master Server. This would serve end customer on site and remote monitoring solution simultaneously. Meaning that Slave Client would only passthrough data and settings to devices within the premises (factory, vessel, etc.) and allows end users to see data, measurements and process view. Master from remote location would serve the slave client by managing the settings etc... updates are first transmitted to slave client in remote destination and then to field acquisition devices. So Slave would be monitoring tool and proxy.

2 Votes

Comments

2 comments

Date Votes

    Interesting idea! Do you have any preferences regarding what tasks have to be done via Slave Client and data types you would like to observe on it?

    Slave Client would be running only for presenting data on premises for process supervisors or machine operators in dedicated computer or virtual machine. It should have limited access to more detailed information but basic wave forms, spectra, trends, etc. are available for monitoring machine condition. Altering monitoring/acquisition settings would not be plausible from Slave Client. Instead Slave Client would relay settings to acquisition devices when it receives updated configuration from Master Server. 

Please sign in to leave a comment.