Search results

Frequently with a Mark VIe turbine control system the plant DCS isn't from GE (though obviously GE would love to sell you the plant DCS as well, they most typically do that with new plants) so this isn't an unusual situation, so I'm surprised you're not getting good answers. It probably has to...

You can't directly use files written in a later version of ToolboxST in an older version, unfortunately. Depending on what you want to do, however, there is one loophole that may help--copy paste. If you have both versions of ToolboxST installed, you can copy-paste from the newer version into...

OK, you're right, that is weird. So, two questions. What Mark VIe runtime version is this, and is that TTXSPV4 block the original TTXSPV4 from turblib or is it possibly a User Block with modified behavior? The icon for it in the treeview will be different if it is a user block.

I'd still like to get the values for the input TTXD2 array and the outputs TTXSP1, TTXSP2, and TTXSP3 from the exact same frame. I've got a TTXSPV4 block right here in front of me (Mark VIe runtime V04.07.06C on a UCSA controller), calculating TTXSP1 correctly (highest-lowest).

To see if the block is working, you need the inputs (TTXD2 array) and TTXSPV4 block outputs from the exact same controller frame. You've got sreenshots of both, but probably from different points in time, so they don't match. As CSA pointed out you can't go by the HMI screens (even though both...

The message text you posted isn't the actual diagnostic, it is ToolboxST saying it can't get a list of diagnostics from the pack. A lot of things could cause this, but most of them have more specific diagnostics or error messages. When you connect to the device in Toolbox, are there any errors...

Ah, if your Mark VIeS version is V03.02.07C and the Virtual Mark VIeS version is V04.03.00C or later, that might explains things. Between the two versions two pins were added to the COMPARE block (HYST and SENS), and given the serialization failure was in a user block called BLOCK_COMPARE_R...

Interesting; the best possibility I can think of is that the Mark VIeS virtual controller version doesn't match the runtime version used to configure the device in ToolboxST. The block libraries are built into the simulator rather than accepting a download from ToolboxST like the real runtime...

It isn't that simple. Depending heavily on what programming language, processor, OS, and libraries are involved, malformed data can certainly be used as an attack vector. For example, passing an address out of range in a write register command could easily attack a modbus driver running on...

Is this a hypothetical question? If you've got an infected powermeter I'd love to know more details. There's a prior discussion on this subject already (use search), but it boils down to whether you're talking about a general threat or specific threat. No general malware is going to be able...

I'd submit this to GE's product services, but if you're in a hurry: First a question, what version of ControlST are you using? CMS was switched from CVS to SVN on the backend and a lot of improvements made in V6 and later. This is for my own curiosity, as I think the below workaround should...

I should probably add the Cimplicity side of this; open your screen and the smart object cim file (by convention, these are .cim files that start with tp_) and drag the object type you want onto your screen. A popup window will let you choose options, including the Device and "Ctrlr", which...

There really isn't anything special to do; so long as the variable names on your Cimplicity object match the globals defined by logic it will just work. The blocks in the Standard and DCS block libraries that have HMI faceplates follow a naming convention. Pins that are used by an HMI...

All of the mapping between the HMI objects and controller logic is by variable name; usually the variable name is a combination of a device's tag name and sub variables. Usually there is a single block in the controller representing the device that has a corresponding tag name and variables. You...

Cybersecurity is all about defense in depth--layers of protection rather than assuming one defense is foolproof protection. Poor engineering has often compromised what should have been easy layers--hardcoded passwords on embedded systems for example. You also have to know what your level of...

Normally you'd let ToolboxST do that, rather than trying to use a terminal and do it manually. Look at the "Controller Setup" section of GEH-6700, which should be installed with ControlST. If you really want to connect over serial, which I don't recommend unless you are an expert, there are...

What you're describing is called a supply chain attack, and is a grave concern across the industrial controls industry. Probably the best known example is Stuxnet, where PLCs were apparently tampered with before even making it to Iran. Counterfeit devices are possible, especially for...

The newer licenses for ControlST (V5 and later) have the raw capability for one-year licenses, but I'm not sure GE sells them that way to external customers. It isn't an option on the part number flowchart (google search for GHT-200060), but maybe something has been added recently. I'd call GE...

In Toolbox, you can set a password for Privilege Level 1 and above (change online values). Open your M6B file for a controller, and use the Options->Passwords menu option. Don't forget your password, I'd make a backup of your unprotected M6B in a safe place.

I'd take exception to the statement that PLCs don't get viruses; no reason they can't. Most are just industrial PCs running a RTOS like Vxworks, realtime linux, or QNX. While general purpose viruses probably won't touch those platforms, the "advanced persistent threats" out there certainly do...