Facebook
Google
GitHub
Linkedin
H
can I communicate Speedtronic MK VI with rsview32 over OPC server and make HMI computer? if yes, what the software needed to make that?
If RSVIEW32 has OPC capability, it can be done, but it would have to be done through an OPC server on some computer. Some versions of CIMPLICITY on GE power generation HMIs have OPC capability. I believe a couple of the major OPC vendors (Matrikon and Kepware?) have done something similar and I don't know if it required the GE power generation HMI or could run on a separate PC, or even on the same PC that would be used as the new HMI.
I don't believe that GE "allows" anyone to communicate directly to the Mark VI controller processors over the UDH (Unit Data Highway) and that communication has to be done through a GE power generation HMI running the necessary software to allow communications with Mark VI controller processors.
But, the GE power generation HMI is still going to be required to use Toolbox to do any detailed troubleshooting or configuration changes (including LVDT calibration). So, that "box" will still be required no matter what HMI is used for monitoring and commands, or even trending.
Why increase the complexity of the communications and troubleshooting needlessly by adding another communications link and at least one more PC?
Reliability and availability should be the primary goal, and that includes keeping things simple without introducing more points of failure. There are perceived advantages to this type of communication, but every intermediate step (software and/or hardware) just adds to the potential for trouble and failure.
Granted, the GE power generation HMIs running CIMPLICITY aren't the greatest, but, there are some incredible implementations of CIMPLICITY in plant and process control applications other than power generation, and the operators and technicians rave about it. The issue with the power generation applications is that nobody ever takes the time to learn CIMPLICITY and it's inner workings and how to create more useful and informative displays, which is really why most people want to use a different HMI product: They don't like the graphics provided with the GE power generation HMIs.
But, each HMI comes with CIMEDIT and so one can create or modify any display. CIMPLICITY has a relatively rich feature set that is only 10-15% utilized on GE power generation HMIs, if that! (I do strongly suggest not modifying or deleting any original displays, because someone coming in from the packager might have real difficulty with new displays! And it makes debugging and troubleshooting that much easier to have something to refer to when implementing the new displays.)
And, let's not forget the cost of Rockwell products. We all think GE likes their stuff a lot (because they charge so much for it!). Rockwell adores their stuff--especially their software! CIMEDIT is included with the GE power generation HMIs "at no additional cost".
I don't believe that GE "allows" anyone to communicate directly to the Mark VI controller processors over the UDH (Unit Data Highway) and that communication has to be done through a GE power generation HMI running the necessary software to allow communications with Mark VI controller processors.
But, the GE power generation HMI is still going to be required to use Toolbox to do any detailed troubleshooting or configuration changes (including LVDT calibration). So, that "box" will still be required no matter what HMI is used for monitoring and commands, or even trending.
Why increase the complexity of the communications and troubleshooting needlessly by adding another communications link and at least one more PC?
Reliability and availability should be the primary goal, and that includes keeping things simple without introducing more points of failure. There are perceived advantages to this type of communication, but every intermediate step (software and/or hardware) just adds to the potential for trouble and failure.
Granted, the GE power generation HMIs running CIMPLICITY aren't the greatest, but, there are some incredible implementations of CIMPLICITY in plant and process control applications other than power generation, and the operators and technicians rave about it. The issue with the power generation applications is that nobody ever takes the time to learn CIMPLICITY and it's inner workings and how to create more useful and informative displays, which is really why most people want to use a different HMI product: They don't like the graphics provided with the GE power generation HMIs.
But, each HMI comes with CIMEDIT and so one can create or modify any display. CIMPLICITY has a relatively rich feature set that is only 10-15% utilized on GE power generation HMIs, if that! (I do strongly suggest not modifying or deleting any original displays, because someone coming in from the packager might have real difficulty with new displays! And it makes debugging and troubleshooting that much easier to have something to refer to when implementing the new displays.)
And, let's not forget the cost of Rockwell products. We all think GE likes their stuff a lot (because they charge so much for it!). Rockwell adores their stuff--especially their software! CIMEDIT is included with the GE power generation HMIs "at no additional cost".
F
Febri
I think this is not best way to make HMI using RSView32 rather than use Cimplicity and ToolBox as standard HMI/Tools for Operation/Engineering purpose.
But, you can do it using some OPC server and connect to Cimplicity OPC server (if ready install in one of your HMI), or using KEpware for GSM protocal (i have heard that Kepware have driver for this connection to MKVI)...please check on Kepware.
Better design than i have already implement is using serial modbus connection to HMI and send data to DCS for monitoring or connect Cimplicity OPC Server to Historian or other HMI using PDH network.
But, you can do it using some OPC server and connect to Cimplicity OPC server (if ready install in one of your HMI), or using KEpware for GSM protocal (i have heard that Kepware have driver for this connection to MKVI)...please check on Kepware.
Better design than i have already implement is using serial modbus connection to HMI and send data to DCS for monitoring or connect Cimplicity OPC Server to Historian or other HMI using PDH network.
W
wassim
You will need this opc server:
http://www.matrikonopc.com/opc-drivers/209/base-driver-details.aspx
This OPC Server is very easy to use. The RSView can act as an OPC client which you will connect it to the OPC server and transfer your data.
Let me know if you need any help
Wassim Daoud
Global Solutions Architect
www.MatrikonOPC.com
http://www.matrikonopc.com/opc-drivers/209/base-driver-details.aspx
This OPC Server is very easy to use. The RSView can act as an OPC client which you will connect it to the OPC server and transfer your data.
Let me know if you need any help
Wassim Daoud
Global Solutions Architect
www.MatrikonOPC.com
