Hi,

Well, it looks the faceplate is custom made by someone? Normally a SFC chart/instance only has a SFC faceplate.

Are you using SFC types to create SFC instances? or are you using SFC charts?

With SFC types, you can easily create additional texts in the characteristic section under: "POSINO". This can create a note text for the operator which you can assign each step.

There is also the option to use OPTIPNO, which is basically an operator prompt-> Filled tank with water?  you can then acknowledge this text to continue with the next step.

However, if you do not have SFC types, but charts....this is not possible.

The best thing you can do probably is to create a custom block with an input and output of type STRING and with OCM capability (allows this input/output to be send to the OS during compile). This way, you can set in each step the input value, like: "Filling tank with water" and in the code you transfer this to your output. You then create a IO field or something where you display the value of the output of type STRING.

I hope I made this understandable?

Hi,

I already posted once the differences...here it comes:

The main difference is that SFC types are mainly used by the PCS7 Add on: Batch. This is a higher level system which controls the system by executing recipes. Batch works according to ISA88, where there is a process cell->unit->equipment->control module.

A SFC type can represent an equipmentmodule like an agitator.

However, using SFC type is not limited to Batch only. The main difference is that a SFC type is setup once, and multiple instances can be inserted in CFC charts. For an SFC chart, there is only one. You can setup a SFC type uniform, which means you cannot address objects directly. You can configure so called characteristics like block contacts, setpoint, parameters etc. which you use in the SFC type. When you have your SFC type complete, you can distribute instances of that SFC type. With a SFC type, you can also create control sequencers like CS1: Stir, CS2: Heat, CS3: Cool.

When you have 10 tanks which have the same functionality, you can create one SFC type and use 10 instances. A SFC type is expandable with IO's, which you define in the "Characteristic" overview. You can define parameters, setpoints, block contacts, operator text etc. For the so called block contacts, you can define objects of type valve, motor, PID etc. When you insert the instance, you can connect your process tag to the objects you defined and a connection is made.

A SFC chart is a basic SFC which cannot be expanded. In a SFC chart, you can address objects directly. You cannot use characteristics.

A SFC chart works in the same way like a SFC type-instance. You can set it to run, stop, abort etc. according to the so called: SOL logic. A SFC chart has no CFC block. It only has an SFC editor with an external view. A SFC type has a CFC block which you can drag in a chart.

What differs more is that a SFC type can have 64 sequencers, where a SFC chart can only have 8.

So basically:

When you have multiple units with the same functionality, it's better to create an SFC type. When something has to be changed, a SFC has to be changed once and can be updated throughout the project all at once.

When you have unique functionality or easy functionality, you can use a SFC chart. Usually, a SFC type needs more engineering time.

I prefer to use SFC types always, because I'm used to them because of the Batch knowledge.

Please see the attachment for a visual schematic of the SFC type