show the entry list
ES - SIMATIC Manager -- Creating programs -- CFC - Using block libraries
What are the system requirements for using SIMATIC PCS 7 Industry Library?
What should you watch out for when changing the symbolic addresses of input/output modules?
Why are the inputs of the driver block in the CFC chart no longer interconnected after replacing a HART analog module?
How do you parameterize the PCS 7 APL channel driver so that the output process value is inverted?
How do you configure a Modbus slave using the "RCV_341" (FB 121) PCS 7 block?
Why do I get the signal "QBAD" on my "CH_AI" driver block?
How do you configure the "Sample_T" input?
Why is the module INT_P issuing invalid values at the output?
Why isn’t the CH_AI block not interconnected automatically with the option "Create module driver"?
How can I change the preset message class in standard blocks?
Can blocks from the CFC library for the S7-300 CPUs also be used in a program for an S7-400 CPU?
What is the meaning of the block input VALUE_QC of the CH_DI block?
Why is the simulated value not output on the CH_AI driver block and how can a value still be simulated?
When do you speak of a "self-regulating process" and when of a "non-self-regulating process"?
How do you do perform controller optimization with the PCS 7 PID tuner?
What is the meaning of the parameters "GAIN", "TN" and "TV" with the CTRL_PID block?
Why is there only half the expected current output from each of the analog output modules in the case of redundant modules?
How much memory is used by the SIMATIC PCS 7 V6.0 library blocks and templates in the PLC?
What do I have to take into account to avoid that the actual value overshoots when switching over from hand/track operation to automatic operation of the "CTRL_PID" with activated setpoint ramp?
How can additional message texts - only as event and OS range - be edited in a block that supports messages in SIMATIC PCS 7 V5.x?
When generating the module drivers, how can you clear the message "Necessary files are missing for block CH_AI. Please note that you must install exactly that version of the library from which this block was imported"?
Why does the CH_AI driver report the slave still to be defective (QBAD=1) after failure and return of a PROFIBUS DP slave (e.g. ET 200M)?
How do you interconnect an FM350-2 in PCS 7?
How can you clear the error message "Value BITVAL is not defined in file AL_CHN.xml / CH_DI." in the module driver log?
FM 350-1, 350-2, 450, SM338 -- Setting up and parameterizing hardware -- Initializing and parameterizing modules
How do you cyclically read out the 8 channels of the FM 350-2 counter module as quickly as possible?
How can the counter values of compact CPUs and of the FM 350/FM450 counter module be made available again after a power failure?
How do you commission the FM350-2 counter module (6ES7350-2AH01-0AE0) in STEP 7 Professional V11 and higher?
How do you commission the FM350-1 counter module (6ES7350-1AH03-0AB0) in STEP 7 Professional V11 and higher?
Why with module FM350-1 does the internal gate STS_GATE remain open in single count mode although the software gate SW_GATE closes?
Which function modules (FM) can be used remotely in an ET 200M?
How do you interconnect an FM350-2 in PCS 7?
How can you retain the counter value of counter modules (6ES7350-1AH03-0AE0, 6ES7350-2AH00-0AE0, 6ES7450-1AP00-0AE0) after a STOP to RUN transition of the CPU?
How can you fast load an initial value in the counter group FM350-1 or FM450-1?
How can you generate a process alarm with the latch function on the "FM350-1" module?
Images mixed up in the FM450-1¿s configuration package for displaying the hardware gate controller 
Specifying direct I/O access to the FM 350-2, 2 channels
SM 338: how do you handle disconnected channels?
How do you interconnect an FM350-2 in PCS 7?
Part number:

This entry describes how to configure an FM350-2 in PCS 7 using the PCS 7 Standard Library. If you use the PCS 7 Advance Process Library (APL) in your project, information about configuring in this case is available in this entry: 83146298

This is how you configure the FM350-2 Counter in PCS 7

Changes from PCS 7 V7.x onwards

Configuration with the FCs from the FM350 library - all 8 channels can be evaluated
Using this method you configure a block sleeve to incorporate the relevant FCs from the FM350 library. More information is available in the manual "FM350-2 Counter Function Module Installation and Parameter Assignment" in Entry ID 1105178.

Configuration with the CH_CNT (FB127) block of the PCS 7 library V6.x - permits access to only 4 channels
The blocks that are supplied with the module are not necessary for the PCS 7 because the PCS 7 only requires the blocks that are already in the PCS 7 V6.x library (from PCS 7 V6.0 SP3).

Changes to the configuration options of block CH_CNT (FB127): From V7.x with 8 possible channels
In order to be able to use the 4 additional channels (4-7), you set the USE_CNT and USE_MSRV inputs (Fig. 04) to TRUE for these channels in the CH_CNT blocks. You must not that these 4 channels are read cyclically as a data record from the module. They are read cyclically because these counter and measured values are not in the process image of the FM350-2 Counter. For the sake of performance, you should only set these two inputs to TRUE only if you need the function.
In the 4 channels of the FM350-2 Counter that are in the process image (channels 0-3) you can use the cyclic reading option by setting the two inputs USE_CNT and USE_MSRV likewise for channel concerned. Here, however, you must note that this is also at the cost of performance.

Install the FM 350-2 Counter software before proceeding as follows.
No. Procedure
1 Add an FM350-2 Counter module to your HW Config and select the module (Fig. 01).
Double-click the FM module to open the parameterization window for the FM350-2 Counter.

Fig. 01: Hardware Configuration

2 In the parameterization window of the FM350-2 Counter, you execute the menu command "Edit > Specify channels" in order to set the channels (Fig. 02).

Fig. 02: Configuration of the counter module

3 Define the settings for the channels in this window.

Fig. 03: Specifying channels

During parameter assignment, it is important to note which data type has been selected for the count values (user_type1 and user_type2) which have been read in.
In this example, user_type 1 has been configured with WORD and user_type 2 has been configured with DWORD.

Configuration of block CH_CNT (FB127) in CFC
No. Procedure
1 Insert the CH_CNT block (FB127) into your CFC plan.

Fig. 04: CFC block for the counter module

2 Create symbols in the symbol table for the start addresses for the FM350-2 module.

Fig. 05: Settings in the symbol table

Note the following here:

  • Depending on which data type has been selected during the parameter assignment for FM350-2 with HW Config for user_type1 or user_type2, you select either EW for WORD or ED for DWORD.
    The address for user_type1 commences from the base address of the module + 8 bytes (base address = 512; ED520 or EW520, for example).
  • The start address for the module in this example is 512.
    The first channel has been set to WORD; therefore, enter EW520 in the symbol table.
  • The address for user_type2 commences from the base address of the module +12 bytes (e.g. base address = 512; ED524 or EW524).
    In our example, enter ED 524 in the symbol table.

In the case of the WORD data type, you can also assign symbols for the following addresses: "base address" + 10 and "base address" + 14. In terms of channels, the count and measured values must lie flush in the process image. The sequence can be count or measured value and vice versa. However, only one symbol may be defined as the start address of the count or measured values for a channel.

3 Connect the LATCH input parameter to the appropriate channel.

Fig. 06: Manual interconnection of the CFC block

4 Start compilation of the CFC charts.

Fig. 07: Compiling the charts with the "Create module driver" option

5 Block after CFC compilation

Fig. 08: Ready-connected and configured block in CFC

The following are performed automatically during compilation using the "Create module driver" function:

  • Parameter assignment of the block
  • Interconnection of the LADDR and CHANNEL inputs
  • Connection of the MODE input to the OMODEx output of the FM_CNT block
  • Connecting the FM_DATA structure to the identically-named structure of the FM_CNT block 

Example of addressing the channels of the block CH_CNT (FB127)
If you use the "WORD" data format to display values, then the values of channels 0 to 3 are in the process image. The values for channels 4 to 7 are not in the process image and have to be read using "Read data record".

The channels in the process image are addressed as described in the Online Help. The base address 512 will be used in this example.

Channels in the process image:
Channel 0: Base address + 8 bytes = EW 520
Channel 1: Base address + 10 bytes = EW 522
Channel 2: Base address + 12 bytes = EW 524
Channel 3: Base address + 14 bytes = EW 526

Only 2 channels are available in the process image with the DWORD data format. 

Channels outside the process image (these are read using "Read data record"):
Channel 4: Base address + 4 bytes = EW 516
Channel 5: Base address + 5 bytes = EW 517
Channel 6: Base address + 6 bytes = EW 518
Channel 7: Base address + 7 bytes = EW 519

The following holds for addressing these channels (4 to 7): Base address of the module + channel number. 

There is further information available on the configuration of the module and of the block in the Online Help for the "CH_CNT" block (FB127).

 Entry ID:19734436   Date:2014-01-10 
I regard this helpfulas not helpful                                 
My Documentation Manager 
Support Request
To this entry
Create PDF 
Send to a friend
Compatibility tool 
Online Help
Guided Tour