Today is...
Wednesday, June 20, 2018
Welcome to, the global online
community of automation professionals.
Featured Video...
Featured Video
A demonstration of EtherCAT control of linear motors using the CTC EtherCAT master.
Our Advertisers
Help keep our servers running...
Patronize our advertisers!
Visit our Post Archive
Mark-VIe Servers
Functions of Servers provided with Mark-VIe

Dear All,

We have one number of Mark-VIe control panel for Gas Turbine, Frame-6.

There are 02 nos of servers provided with Mark-VIe. I found both have similar functions for engineers & operators. Name of the server are GT1_SVR & CRM1_SVR.

I would like to know what is the difference in terms of functionality of these two servers. Are they redundant?


1 out of 1 members thought this post was helpful...

Dear MJ,

The PRIMARY difference between the two HMIs is that the Mark VIe ToolboxST files that are used for configuration and troubleshooting are stored on CRM1_SVR, and are (or usually are) accessed by ToolboxST when it's opened on GT1_SVR. That's the PRIMARY difference between the two. Other than that, the two are basically redundant (from the CIMPLCITY standpoint--operation, alarm management, commands, etc.).

Some CRM1_SVRs run the GE CMS (Configuration Management Server) program and keep track of changes to files and that information is primarily stored on the CRM1_SVR.

Sometimes if there is a communication link to a DCS or other control system are data archival and -retrieval system in the plant that may--or may not--be done through CRM1_SVR.

A LOT of the differences between the HMIs can be seen by looking at the ML 4108 drawing, the "control system arrangement" drawing (I just realized the initial/acronym for 'control system arrangement matches my long-in psuedonym!). That shows which HMIs are connected to what other systems, if any.

But, any other distinction ("Engineering Workstation" or "Operator Workstation") is simply a matter of choice by site personnel. Both HMIs can be used to issue commands to the Mark VIe; both HMIs can be used to monitor the operation of the Mark VIe; ToolboxST on both HMIs can be used to configure, troubleshoot and monitor operation of the Mar VI--with the exception that if CRM1_SVR is not operational then GT1_SVR cannot access the "master" ToolboxST files on CRM1_SVR.

Hope this helps! Do try to locate the 4108 drawing, because it's very useful for troubleshooting network problems, and understanding which HMIs are connected to any other control systems, if present and applicable.

Again, this only describes the primary differences between the two HMIs, which are important--but from a strictly operational point of view, there is no difference between the two (starting, stopping, changing load, etc.).

Dear CSA,

As you mentioned if Server is down we cant access TooboxST. If it needs to be accessed, whats the way out?


2 out of 2 members thought this post was helpful...

What is it that you need ToolboxST for? How many turbines and HMIs are on the full ToolboxST project file?

SOME HMIs have ToolboxST installed on them but if the "Master" ToolboxST project file can't be accessed then the local HMI could be used to upload the ToolboxST configuration from the turbine control panel in order to be able to view live data/values.

But, that would not be the complete ToolboxST project file, only the information for that one device.

What is the problem with the main ToolboxST server?

There are some configuration servers and databases that are only available on the main server. Some sites have a back-up server that can "take over" for the main server--IF configured properly. Unfortunately, few are properly configured, and there really are no written procedures for doing so. It generally requires GE assistance and a good deal of that to properly configure the back-up server to correctly assume all the functions of the main server in the event of a problem with the main server.

Some HMIs were configured to be local back-up storage locations for the entire ToolboxST project file. You would have to look on the hard-drive of the local hmi(s) to see if that was done at your site, and if there was a batch or script file on either HMI or perform periodic back-ups to be local hmi(s). This is a case of "the standard is there is no standard " as it was never done consistently, and now with so many different GE providers, all with their own ideas about how HMIs should be configured, it's even more of a conundrum about how any sit's HMIs might be configured.