Control.com team is commendable for providing and maintaining such platform that continually helping people globally. I register on control .com recently however I am scrolling the threads of my interest from past few months and I found them very informative.

Before putting the question let me explain the setup that We have; 4Nos 9E with Mark-V TMR. Redundant stage link <C> and <D>...Both stage links run through all units… 4Nos of HMIs (Windows-NT) each one located in LCR (local control room) of particular unit. Every HMI is connected to either <C> or <D> stage-link. One HMI from each Stage link i.e. HMI-1 from <C> and HMI-4 from <D> is communicating with Plant DCS (Ovation Emerson Westinghoue) and that through Ethernet… All HMIs are also connected to each other through (Ethernet).

Coming to problem that We are planning to add one HMI on either <C> or <D> staglink and want s to locate it in CCR (Central Control Room) where presently no HMI is available. New HMI is loaded with Windows 2000, TCI and Cimplicity. TCI version of new HMI is also updated one comparing running unit’s HMIs. (Running Units HMI TCI: V01.08.02C, New HMI:V02.00.08C)

Running unit project is loaded on this HMI and working fine OFF-LINE. Kindly advice on following;

What are the risks involve in connecting this HMI to stage link when units are in operation?

What should be considered prior to connecting this HMI to avoid setback if any?

Testing this HMI with standalone unit prior to connection with network. Can it make some difference in minimizing the risk?

Any other thoughts or better way to do it?

Regards,

 

Testing with an isolated Mark V would be the safest option.

 

CSA thanks for reply but can you put some light on first two question.

 

ASHGAR,

I purposely did not comment on the first two questions. It's not clear where you obtained the GE Mark V HMIs, nor if they are configured properly.

I don't know the permissible combinations of MS-Windows and TCI and CIMBRIDGE and CIMPLICITY and CIMPLICITY Service Packs. There are too many of them. If you've "mixed and matched", then the best advice is to try it on a "standalone" unit first.

There's a good chance everything will be okay--but, do you want to take a chance? Can your process stand the possible loss of one--or more--unit(s)?

Only you know the answers to the questions (except which versions of software are "certified" to work together, by GE, that is).

Which is why I purposely didn't comment on that aspect.

I'm a very conservative person when it comes to some things. Some would say too conservative, but, that's not going to make me change at this point in my career. "No guts; no glory," they also say. And, while I've enjoyed some successes I've managed to avoid a lot of failures with my philosophy.

Best of luck. Write back to let us know what you decide and what the results are.

 

CSA,

Good to hear from you. sorry for bit late to reply you.
My intention was not take you to "some things"...! I honor your belief... no demands to change yourself.

But basic question was on net working that if two different operating system (NT and 2000) can work together on ARCNET... and two different versions of TCI machines can hook on same stage-link simultaneously while assuming that configurations are OK. Please ignore the question if you feel that it’s still out of your circle.

Regards,

 

The HMIs don't communicate with each over the StageLink. They might communicate with each other over the PDH (via Ethernet) but they don't--and can't--communicate with each other over the ARCnet-based StageLink.

TCI is just the MW-Windows service that allows a PC to communicate with a Mark V (or multiple Mark Vs) using the ARCnet card. It also provides the Logic Forcing Display, the Prevote Data Display, the Control Constants Adjust Display, AutoCalibrate Display, etc. All the things which can't be done from CIMPLICITY.

When CIMPLICITY needs information it goes through CIMBRIDGE to TCI and TCI uses the ARCnet card to get it from the Mark V over the StageLink.

I have seen and used various versions of MS-Windows (Win95 running IDOS) and MW-Windows based HMIs (WinNT 4.0, Win2K, and WinXP) each running their own version of TCI, CIMBRIDGE and CIMPLICITY all on the same StageLink with no problem.

They just need to be configured properly on each HMI and configured to get data from the Mark V(s).

And remember: There is a "theoretical" limit of two (2) HMI Servers communicating with a Mark V. Because of the amount of data CIMPLICITY requests from a Mark V, if there are more than two GE Mark V HMI Servers connected to a Mark V, then it can really negatively affect the <C> processor's ability to provide data to any GE Mark V HMI.

And if any GE Mark V HMI is also using Logic Forcing Display or Prevote Data Display that adds immensely to the traffic and data requests.