Library manual XBTGC Expert I/O High speed counting | 3 MB

EIO0000000644.04 

Magelis XBT GC HMI Controller 

04/2012 

Magelis XBT GC HMI 

Controller 

High Speed Counting 

XBT GC HSC Library Guide 

04/2012 

www.schneider-electric.com

The information provided in this documentation contains general descriptions and/or 

technical characteristics of the performance of the products contained herein. This 

documentation is not intended as a substitute for and is not to be used for 

determining suitability or reliability of these products for specific user applications. It 

is the duty of any such user or integrator to perform the appropriate and complete 

risk analysis, evaluation and testing of the products with respect to the relevant 

specific application or use thereof. Neither Schneider Electric nor any of its affiliates 

or subsidiaries shall be responsible or liable for misuse of the information contained 

herein. If you have any suggestions for improvements or amendments or have found 

errors in this publication, please notify us. 

No part of this document may be reproduced in any form or by any means, electronic 

or mechanical, including photocopying, without express written permission of 

Schneider Electric. 

All pertinent state, regional, and local safety regulations must be observed when 

installing and using this product. For reasons of safety and to help ensure 

compliance with documented system data, only the manufacturer should perform 

repairs to components. 

When devices are used for applications with technical safety requirements, the 

relevant instructions must be followed. 

Failure to use Schneider Electric software or approved software with our hardware 

products may result in injury, harm, or improper operating results. 

Failure to observe this information can result in injury or equipment damage. 

© 2012 Schneider Electric. All rights reserved. 

2 04/2012

Table of Contents 

Safety Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 

About the Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 

Part I I/O Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 

Chapter 1 Special I/O Configuration. . . . . . . . . . . . . . . . . . . . . . . . . 13 

Local and Special I/O Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 

Special I/O Configuration Possibilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 

I/O Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 

Part II HSC Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 

Chapter 2 HSC General Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . 25 

HSC Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 

HSC General Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 

Chapter 3 1-Phase HSC Counter. . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 

Up/Rising Edge Counter Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 

Down/Rising Edge Counter Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 

Up/Falling Edge Counter Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 

Down/Falling Edge Counter Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 

Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 

Chapter 4 2-Phase HSC Counter. . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 

Mode 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 

Mode 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 

Mode 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 

Mode 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 

Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 

Chapter 5 HSC Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 

HSC Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 

Part III HSC Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 

Chapter 6 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 

Dedicated Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 

04/2012 3

Chapter 7 Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 

HMI_HSCStart: Start the HSC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 

HMI_HSCStop: Stop the HSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 

HMI_HSCGetCurrentValue: Get the HSC Current Value . . . . . . . . . . . . 56 

HMI_HSCGetCapturedValue: Get the HSC Value . . . . . . . . . . . . . . . . . 57 

HMI_GetSynchronizedOutput: Get Synchronized Output Status . . . . . . 58 

HMI_ClearSynchronizedOutput: Clear Synchronized Output Status. . . . 59 

HMI_SetCounterValue: Set the HSC Value. . . . . . . . . . . . . . . . . . . . . . . 60 

HMI_ClearCounterValue: Clear the HSC Value . . . . . . . . . . . . . . . . . . . 61 

HMI_GetPreLoadStatus: Detect Preload Input Signal. . . . . . . . . . . . . . . 62 

HMI_ClearPreLoadStatus: Clear PreLoad Status . . . . . . . . . . . . . . . . . . 63 

HMI_GetPreStrobeStatus: Get PreStrobe Status . . . . . . . . . . . . . . . . . . 64 

HMI_ClearPreStrobeStatus: Clear PreStrobe Status . . . . . . . . . . . . . . . 65 

HMI_GetMarkerStatus: Detect Hardware Marker Input Signal . . . . . . . . 66 

HMI_ClearMarkerStatus: Clear the Marker Status . . . . . . . . . . . . . . . . . 67 

Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 

Appendix A Function and Function Block Representation . . . . . . . . 71 

Differences Between a Function and a Function Block . . . . . . . . . . . . . . 72 

How to Use a Function or a Function Block in IL Language . . . . . . . . . . 73 

How to Use a Function or a Function Block in ST Language . . . . . . . . . 76 

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 

4 04/2012

Important Information 

NOTICE 

Safety Information 

Read these instructions carefully, and look at the equipment to become familiar with 

the device before trying to install, operate, or maintain it. The following special 

messages may appear throughout this documentation or on the equipment to warn 

of potential hazards or to call attention to information that clarifies or simplifies a 

procedure. 

04/2012 5 

§

PLEASE NOTE 

Electrical equipment should be installed, operated, serviced, and maintained only by 

qualified personnel. No responsibility is assumed by Schneider Electric for any 

consequences arising out of the use of this material. 

A qualified person is one who has skills and knowledge related to the construction 

and operation of electrical equipment and its installation, and has received safety 

training to recognize and avoid the hazards involved. 

6 04/2012

At a Glance 

Document Scope 

Validity Note 

Related Documents 

About the Book 

This documentation provides information on the High Speed Counter (HSC); 

functions available with the XBT GC HMI Controller. 

This documentation describes the data types and functions of the XBT GC HMI 

Controller HSC library. 

The following basic knowledge is required: 

Basic information on functionality, structure and configuration of the XBT GC HMI 

Controller 

Programming knowledge of FBD, LD, ST, IL or CFC language 

This document has been updated with the release of SoMachine V3.1. 

Title of Documentation Reference Number 

Magelis XBT GC HMI Controller, Pulse Train Output, Pulse 

Width Modulation, XBT GC PTOPWM LibraryGuide 

EIO0000000650 (ENG); 

EIO0000000651 (FRE); 

EIO0000000652 (GER); 

EIO0000000653 (SPA); 

EIO0000000654 (ITA); 

EIO0000000655 (CHS); 

Magelis XBT GC HMI Controller Programming Guide EIO0000000632 (ENG); 

EIO0000000633 (FRE); 

EIO0000000634 (GER); 

EIO0000000635 (SPA); 

EIO0000000636 (ITA); 

EIO0000000637 (CHS); 

04/2012 7

Product Related Information 

SoMachine Programming Guide EIO0000000067 (ENG); 

EIO0000000069 (FRE); 

EIO0000000068 (GER); 

EIO0000000071 (SPA); 

EIO0000000070 (ITA); 

EIO0000000072 (CHS); 

You can download these technical publications and other technical information from 

our website at www.schneider-electric.com. 

LOSS OF CONTROL 

WARNING 

The designer of any control scheme must consider the potential failure modes 

of control paths and, for certain critical control functions, provide a means to 

achieve a safe state during and after a path failure. Examples of critical control 

functions are emergency stop and overtravel stop, power outage and restart. 

Separate or redundant control paths must be provided for critical control 

functions. 

System control paths may include communication links. Consideration must be 

given to the implications of unanticipated transmission delays or failures of the 

link. 

Observe all accident prevention regulations and local safety guidelines. 1 

Each implementation of this equipment must be individually and thoroughly 

tested for proper operation before being placed into service. 

Failure to follow these instructions can result in death, serious injury, or 

equipment damage. 

1 For additional information, refer to NEMA ICS 1.1 (latest edition), "Safety 

Guidelines for the Application, Installation, and Maintenance of Solid State Control" 

and to NEMA ICS 7.1 (latest edition), "Safety Standards for Construction and Guide 

for Selection, Installation and Operation of Adjustable-Speed Drive Systems" or their 

equivalent governing your particular location. 

8 04/2012

User Comments 

UNINTENDED EQUIPMENT OPERATION 

WARNING 

Only use software approved by Schneider Electric for use with this equipment. 

Update your application program every time you change the physical hardware 

configuration. 



We welcome your comments about this document. You can reach us by e-mail at 

techcomm@schneider-electric.com. 

04/2012 9

10 04/2012


I/O Configuration 

04/2012 


04/2012 11 

I


12 04/2012

Introduction 


Special I/O 

04/2012 

Special I/O Configuration 

This chapter describes how local I/Os can be configured as special I/Os. 

What’s in this Chapter? 

This chapter contains the following topics: 

04/2012 13 

1 

Topic Page 

Local and Special I/O Overview 14 

Special I/O Configuration Possibilities 16 

I/O Summary 19

Special I/O 

Local and Special I/O Overview 

Introduction 

Special I/O Types 

The XBT GC HMI Controller supports Local I/Os (see Magelis XBTGC HMI 

Controller, Programming Guide). There are: 

12 hardware inputs and 6 hardware outputs for the local I/Os of the 

XBT GC 1100 HMI Controller 

16 hardware inputs and 16 hardware outputs for the local I/Os of the 

XBT GC 2120 HMI Controller and the XBT GC 2230 HMI Controller 

The local I/O can be configured as special I/O. Special I/Os include: 

High Speed Counter (HSC) (see page 26) 

Pulse Train Output (PTO) (see Magelis XBTGC HMI Controller , Pulse Train 

Output, Pulse Width Modulation, XBTGC Library Guide), 

Pulse Width Modulation (PWM) (see Magelis XBTGC HMI Controller , Pulse 

Train Output, Pulse Width Modulation, XBTGC Library Guide) output 

Pulse Latch Input (PLI) (see Magelis XBTGC HMI Controller , Pulse Train Output, 

Pulse Width Modulation, XBTGC Library Guide) 


Special I/Os are configured in four Groups. Each Group has two inputs (In and In+1 of Group n) and one output (Qn of Group n), as shown in the diagram below: 

NOTE: Any remaining I/Os can be configured as normal I/O. (see page 15). 

14 04/2012

Local I/Os and Special I/Os Configuration 

The following diagram provides the local and special I/Os configuration: 

Special I/O 

Legend 

1 The local I/Os for the XBT GC 1100 HMI Controller are from I8 to I11 and from 

Q4 to Q5. 

2 The local I/O for the XBT GC 2120 HMI Controller and the 

XBT GC 2230 HMI Controller are from I8 to I15 and from Q4 to Q15. 

Special I/Os Configuration Order 

When configuring special I/Os, follow the order shown in the diagram below: 

The special I/Os configuration depends on the number and type of HSC required. 

There are 3 cases: 

Case 1: (see page 16) No HSC is required, or only 1-Phase HSC is required (also 

referred to No 2-Phase HSC) 

Case 2: (see page 17) One 2-Phase HSC is required 

Case 3: (see page 18) Two 2-Phase HSC are required 

See more specific information in the HSC Configuration chapter (see page 45). 

04/2012 15

Special I/O 

Special I/O Configuration Possibilities 

Case 1: No 2-Phase HSC Combination 

All Groups can be configured independently as HSC, PLI or PTO/PWM: 

These Groups can provide the combinations shown in the following table: 

Main Functions I (2n) I (2n+1) Q (n) 

1-Phase HSC Input 1-Phase HSC Input Normal Input or 

Preload or 

Prestrobe 

Normal I/O, PWM or 

PTO 

Normal Output or 

Synchronized Output 

Normal Input Normal Input Normal Output or 

PWM or 

PTO 

PLI Pulse Latch Input Normal Input Normal Output 

NOTE: n is the Group number starting from 0 to 3 (HSC0n/PTO0n/Latch0n) where 

I( 2n ), I( 2n+1 ) and Q( n ) are the inputs and ouput respectively of the Group n. 

16 04/2012

Special I/O 

Case 2: One 2-Phase HSC Combination 

Group 0 and Group 1 form a 2-Phase HSC, the others can be configured as HSC, 

PLI or PTO/PWM: 

For this combination, Group 0 (HSC00) and Group 1 (HSC01) are combined to form 

a 2-Phase HSC. The following tables show the combinations available: 

I0 I1 Q0 

Counter 1A Normal Input or 

Preload or 

Prestrobe 

I2 I3 Q1 

Counter 1B Marker Input or 

Normal Input 




PWM or 

PTO 

NOTE: Group 2 and Group 3 (HSC0n/PTO0n/Latch0n) follow the rules of the No 2- 

Phase HSC. 

One 2-Phase HSC Combinations Summary: 

The PLI function is not available on any input of the Group 

The PWM and PTO functions are available on the second output of the second 

HSC in the Group 

The Synchronized Output is available on the output of the first HSC in the Group 

04/2012 17

Special I/O 

Case 3: Two 2-Phase HSC Combination 

The following diagram shows the Two 2-Phase HSC Combination: 

For this combination, Group 0 (HSC00) and Group 1 (HSC01) are combined to form 

a 2-Phase HSC. Group 2 (HSC02) and Group 3 (HSC03) form another 2-Phase 

HSC. The following tables show the functions available: 

I0 or I4 I1 or I5 Q0 or Q2 

Counter 1A Normal Input or 

Preload or 

Prestrobe 

I2 or I6 I3 or I7 Q1 or Q3 

Counter 1B Normal Input or 

Preload or 

Prestrobe 





18 04/2012

I/O Summary 

Overview 

Special I/O 

The I/O summary shows the current I/O pin configuration for I/O nodes as HSC, 

PTO/PWM and PLI. 

To access the I/O summary, click the IO Summarize... button available on the 

configuration screen of each function. 

The following picture shows, as an example, the HSC IO Summary: 

NOTE: The IO Summarize... button is common to all functions and can be 

accessed from the configuration screen of each function: HSC, PTO/PWM and PLI. 

04/2012 19

Special I/O 

I/O Summary Window 

Click the IO Summarize button to display the following window: 

I/O Summary Messages 

If an I/O setting inconsistency is detected, the Configuration column from the IO 

Summary provides two types of messages: 

Error: Conflict happened on HSC and IO settings 

Error: Conflict happened on HSC and PTO/PWM settings 

20 04/2012

Special I/O 

Example of I/O Summary 

The following example shows the IO Summary window when I/O is configured as a 

standard input, with a Prestrobe input including a detected error message: 

04/2012 21

Special I/O 

22 04/2012

Introduction 


HSC Principles 

04/2012 


04/2012 23 

II 

This part describes the HSC principles used with the XBT GC HMI Controller. 

What’s in this Part? 

This part contains the following chapters: 

Chapter Chapter Name Page 

2 HSC General Overview 25 

3 1-Phase HSC Counter 29 

4 2-Phase HSC Counter 37 

5 HSC Configuration 45


24 04/2012


HSC Overview 

04/2012 

HSC General Overview 



04/2012 25 

2 

Topic Page 

HSC Overview 26 

HSC General Characteristics 28

HSC Overview 

HSC Overview 

Concept 

The HSC function executes the counting of fast pulses from electronic sensors, 

encoders, switches, etc. The HSC function is independent from the XBT GC HMI 

Controller scan time. 

Two HSC types are available: 

1-Phase HSC (see page 29) 

2-Phase HSC (see page 37) 

For information on the XBT GC HMI Controller general I/O configuration, refer to I/O 

Configuration (see page 11). 

Maximum Number of Channels and Operating Frequency 

For information on the maximum number of HSC channels and their operating 

frequency, refer to HSC General Characteristics (see page 28). 

Use Case 

The following graph shows a typical use case. The synchronized output changes 

only when the counter value crosses the ON or OFF preset threshold values: 

NOTE: The 1-Phase HSC up-counting or down-counting depends of the Mode 

(see page 30) set from the HSC I/O configuration (see page 45) screen. Upcounting/Down-counting 

is available with the 2-Phase HSC only. The 1-Phase HSC 

offers up-counting or down-counting depending upon your selected mode from the 

HSC configuration screen. 

26 04/2012

HSC Overview 

Once the HSC is configured, it works independently from the application. Each event 

that occurs in the graph above is described in the table below: 

Event Number Description 

1 The counter crosses the ON preset upward 

Result: The synchronized output is set to a high level 

2 The counter crosses the OFF preset upward 

Result: The synchronized output is set to a low level 

3 The counter crosses the maximum count and resets to 0 

4 The counter crosses the OFF preset downward 

Result: The synchronized output is set to a high level 

5 The counter crosses the ON preset downward 

Result: The synchronized output is set to a low level 

6 The counter decreases to 0 and wraps back to the maximum count 

7 The direction of counting changes from up to down 

04/2012 27

HSC Overview 

HSC General Characteristics 

HSC Characteristics 

The following table shows the maximum frequency per HSC: 

HSC type Number of HSC Max. frequency (kHz) per 

HSC 

1-Phase HSC 4 4*25 100 

3 2*25 + 1*50 

2 2*50 

1 1*100 

2-Phase HSC 2 2*25 50 

1 1*50 

Total Max. 

frequency (kHz) 

28 04/2012

General 


1-Phase HSC Counter 

04/2012 


04/2012 29 

3 

This chapter describes the 1-Phase HSC Counter for the XBT GC HMI Controller. 



Topic Page 

Overview 30 

Up/Rising Edge Counter Mode 31 

Down/Rising Edge Counter Mode 32 

Up/Falling Edge Counter Mode 33 

Down/Falling Edge Counter Mode 34 

Specifications 35


Overview 

Introduction 

The 1-Phase HSC uses one hardware input as a counter input. When there is a 

pulse signal on the input, it can be a: 

count-up counter, or, 

count-down counter 

Configure the 1-Phase HSC using the modes available via the HSC Configuration 

screen (see page 45). 

1-Phase HSC Modes Overview 

Up/Rising edge Counter (see page 31)Mode: 

The counter counts up at each rising edge of the input. 

Down/Rising edge Counter (see page 32) Mode: 

The counter counts down at each rising edge of the input. 

Up/Falling edge Counter (see page 33) Mode: 

The counter counts up at each falling edge of the input. 

Down/Falling edge Counter (see page 34) Mode: 

The counter counts down at each the falling edge of the input. 

1-Phase HSC Specification 

Specification of this counter is described in the 1-Phase HSC Specification 

(see page 35). 

30 04/2012

Up/Rising Edge Counter Mode 


Up/Rising Edge Counter Mode Description 

The following diagram shows the behavior of the 1-Phase HSC using the Up/Rising 

mode: 

On each rising edge of input 1A, the counter counts up. 

04/2012 31


Down/Rising Edge Counter Mode 

Down/Rising Counter Mode Description 

The following diagram shows the behavior of the 1-Phase HSC using the 

Down/Rising mode: 

On each rising edge of input 1A, the counter counts down. 

32 04/2012

Up/Falling Edge Counter Mode 


Up/Falling Counter Mode Description 

The following diagram shows the behavior of the 1-Phase HSC using the Up/Falling 

mode: 

On each falling edge of input 1A, the counter counts up. 

04/2012 33


Down/Falling Edge Counter Mode 

Down/Falling Counter Mode Description 

The following diagram shows the behavior of the 1-Phase HSC using the mode 

Down/Falling: 

On each falling edge of input 1A, the counter counts down. 

34 04/2012

Specifications 


The following table describes the 1-Phase HSC Specification: 


Synchronized Output Specification 

The following table describes the synchronized output specification with the 1- 

Phase HSC: 

Preload Input 

Items Specification 

Low limit 0, see 1 and 2 below 

High limit 4,294,967,295 dec (FFFFFFFF hex) 

Start Counter Counter starts from the IEC application via the counter library 

Stop Counter Counter stops from the IEC application via the counter library 

Counting Up/Rising edge 

Modes Down/Rising edge 

Up/Falling edge 

Down/Rising edge 

NOTE: Refer to 1-Phase HSC Modes Overview (see page 30) and 1-Phase 

HSC Configuration Screen (see page 45) for more information. 

Counter clear Clears the counter value to 0 from the IEC application via the counter library 

Legend 

1 After the counter value reaches the low limit of 0 hex, the counter value is 

FFFFFFFF hex for the next input. 

2 After the counter value reaches the high limit of FFFFFFFF hex, the counter 

value is 0 hex for the next input. 

Items Specification 

Counting up The synchronized output when counting up is set to: 

ON when the value of the ON preset +1 is detected 

OFF when the value of the OFF preset +1 is detected 

Counting down The synchronized output when counting down is set to: 

OFF when the value of the ON preset -1 is detected 

ON when the value of the OFF preset -1 is detected 

Clear Clears synchronized output from the IEC application via the counter library 

The counter value is set to a pre-configured value when the Preload input pulse is 

detected. The pre-configured value is set via the user interface of the HSC. 

04/2012 35


Prestrobe Input 

HSC Value Settings 

The counter value is written into an internal memory area. The value is retrieved 

from the IEC application via the counter library, using the function 

HMI_HSCGetCapturedValue (see page 57). 

Value Setting Specification 

ON preset From 0 to 4,294,967,295 dec (FFFFFFFF hex) 

OFF preset From 0 to 4,294,967,295 dec (FFFFFFFF hex) 

36 04/2012

General 



04/2012 


04/2012 37 

4 

This chapter describes the 2-Phase HSC Counter for the XBT GC HMI Controller. 



Topic Page 

Overview 38 

Mode 0 39 

Mode 1 40 

Mode 2 41 

Mode 3 42 

Specifications 43


Overview 

Introduction 

2-Phase HSC Modes Overview 

The 2-Phase HSC uses the phase difference between two counter signals to 

perform count-up or count-down. There are four modes of phase difference: 

Mode 0: 2-Phase*4 (see page 39) 

Mode 1: Count + Direction (see page 40) 

Mode 2: Up + Down (see page 41) 

Mode 3: Two Phases*2 (see page 42) 

Mode 0 (2-Phase*4): 

The counter counts up or down depending on the order of the inputs. 

Mode 1 (Count + Direction): 

The counter counts up or down depending on the rising edge of one input and the 

value of the other input. 

Mode 2 (Up + Down): 

The counter counts up or down depending on the rising edge of one input and the 

value of the other input. 

Mode 3 (2-Phase*2): 

The counter counts up or down depending on the rising/falling edge of one input 

and depending on the order of the inputs. 


Specification of this counter is described in the 2-Phase HSC Specification 

(see page 43). 

38 04/2012

Mode 0 


Mode 0 Description 

The following diagram shows the behavior of the 2-Phase HSC using mode 0 (2- 

Phase*4): 

Input 1A 

Input 1B 

Counter 

Value 

Off Preset 

ON Preset 

Synchronized 

ouput 

If the rising edge of input 1A is enabled before the rising edge of input 1B, then the 

counter counts up. If the falling edge of input 1A is enabled after the falling edge of 

Input 1B, then the counter counts down. 

The following table provides the 2-Phase HSC behavior for inputs 1A and 1B: 

Input 1A Input 1B Counter Behavior 

1 (High) Rising edge Counts up 

0 (Low) Falling edge 

Falling edge 1 (High) 

Rising edge 0 (Low) 

1 (High) Falling edge Counts down 

0 (Low) Rising edge 

Rising edge 1 (High) 

Falling edge 0 (Low) 

04/2012 39


Mode 1 


The following diagram shows the behavior of the 2-Phase HSC using mode 1 (Count 

+ Direction): 

The HSC counts up on the rising edge of input 1A when 1B is 0 (low). The HSC 

counts down in the rising edge of input 1A when 1B is 1 (high). 



Rising edge 0 (Low) Counts up 

1 (High) Counts-down 

All other combinations All other combinations Does not count 

40 04/2012

Mode 2 



The following diagram shows the behavior of the 2-Phase HSC using mode 2 (Up + 

Down): 

Input 1A 

Input 

Counter 

Value 

1B 

On Preset 

Synchronized 

Output 

The HSC counts up in the rising edge of input 1A when 1B is 0 (low). The HSC 

counts down in the rising edge of 1B when 1A is 0 (low). 



Rising edge 0 (Low) Counts up 

0 (Low) Rising edge Counts down 


04/2012 41


Mode 3 


The following diagram shows the behavior of the 2-Phase HSC using mode 3 (2- 

Phase*2): 

Input 1A 

Input 1B 

Counter 

Value 

Off Preset 

ON Preset 

Synchronized 

ouput 

The HSC counts up in the rising and falling edge when input 1A comes before input 

1B. The HSC counts down in the rising and falling edge when input 1A comes after 

input 1B. 



1 (High) Rising edge Counts up 

0 (Low) Falling edge 

0 (Low) Rising edge Counts down 

1 (High) Falling edge 


42 04/2012

Specifications 


The following table describes the 2-Phase HSC Specification: 


Synchronized Output Specifications 

The following table describes the synchronized output specification with the 2- 

Phase HSC: 

Marker Input 

Preload Input 

Prestrobe Input 

Item Specification 

Low limit 0 

High limit 4,294,967,295 dec (FFFFFFFF hex) 

Start Counter Counter starts from the IEC application via the counter library 

Stop Counter Counter stops from the IEC application via the counter library 

Counting 

edge 

Rising edge or falling edge 

Counter clear Clears the counter value to 0 from the IEC application via the counter library 

Item Specification 

Counting up The synchronized output when counting up is set to: 

ON when the value of the ON preset +1 is detected 

OFF when the value of the OFF preset +1 is detected 

Counting down The synchronized output when counting down is set to: 

OFF when the value of the ON preset -1 is detected 

ON when the value of the OFF preset -1 is detected 

Clear Clear synchronized output from the IEC application via the counter library 

A hardware input sets the HSC value to 0. This is only available on the 2-Phase 

counters. 

The counter value is set to a pre-configured value when the Preload input pulse is 

detected. The pre-configured value is set via the user interface of the HSC. 

The counter value is written into an internal memory area. The value is retrieved 

from the IEC application via the counter library, using the function 

HMI_HSCGetCapturedValue (see page 57). 

04/2012 43


HSC Value Settings 

The following table shows the value settings of the HSC: 

Value Setting Specification 

ON preset From 0 to 4,294,967,295 dec (FFFFFFFF hex) 

OFF preset From 0 to 4,294,967,295 dec (FFFFFFFF hex) 

44 04/2012


HSC Configuration 

04/2012 

HSC Configuration Screen 


04/2012 45 

5 

Accessing the HSC Configuration Screen 

You can access the HSC configuration screen from the Devices window, as 

explained in the procedure below: 

Step Action 

1 Access the Devices window 

2 Click Embedded Functions → HSC (HSC) 

Result: The HSC I/O Configuration window appears


HSC Configuration Screen 

The following screenshot shows the entire HSC configuration screen: 

Properties of the HSC Configuration Screen 

The following table describes the properties of the HSC Configuration screen: 

Parameters Initial Value Range Description 

Phase Type Not used Not Used Select the HSC counter 

1-Phase 

2-Phase 1 HSC 

2-Phase 2 HSC 

type 

46 04/2012

I/O Summary 


Parameters Initial Value Range Description 

IN (2n+1) Not used Not Used 

Normal Input 

Preload 

Prestrobe 

Select the input pin type 

Out(n) Not used Normal Ouput 


Select the ouput pin type 

Mode (1-Phase) Up/Rising Up/Rising edge Counter Select the 1-Phase HSC 

Edge 

Down/Rising edge Counter 

Up/Falling edge Counter 

Down/Falling edge Counter 

counter mode 

Mode (2-Phase) Mode 0 Mode 0 Select the 2-Phase HSC 

Mode 1 

Mode 2 

Mode 3 

counter mode 

On Preload 1000 0 - 4,294,967,295 Set the On Preload 

value 

On Preset 2000 0 - 4,294,967,295 Set the On Preset value 

Off Preset 2000 0 - 4,294,967,295 Set the Off Preset value 

When selecting HSC → Counter Type → Phase Type as 1-Phase HSC counter 

from the I/O Configuration window, you can configure: 

Each of the four HSC groups as 1-Phase HSC counter 

When selecting HSC → Counter Type → Phase Type as a 2-Phase 1 HSC from 

the I/O Configuration window: 

Group 0 (HSC00) and 1 (HSC01) form a 2-Phase HSC counter 

Group 2 (HSC02) and 3 (HSC03) can be configured as 1-Phase HSC counter 

When selecting HSC → Counter Type → Phase Type as a 2-Phase 2 HSC from 

the I/O Configuration window: 

Group 0 (HSC00) and 1 (HSC01) form a 2-Phase HSC counter 

Group 2 (HSC02) and 3 (HSC03) form another 2-Phase HSC counter 

The I/O Summarize... button is described in the I/O Summary (see page 19) 

section. 

04/2012 47


48 04/2012

Introduction 


HSC Library 

04/2012 


III 

This part describes the data types and functions of the XBT GC HMI Controller. 

What’s in this Part? 

This part contains the following chapters: 

Chapter Chapter Name Page 

6 General Information 51 

7 Functions 53 

04/2012 49


50 04/2012


General Information 

04/2012 

Dedicated Functions 


Using Dedicated Functions 

Once dedicated functions such as HSC, PLI and PTO/PWM outputs are configured, 

certain inputs and outputs are dedicated to the function or function blocks that 

control them. 

WARNING 

04/2012 51 

6 

UNINTENDED EQUIPMENT OPERATION 

Do not modify a function, function block references or parameter values while the 

function or the function block is active (executing). 



The function block instance name must match the name defined by configuration. 

Hardware related information managed by this function block is synchronized with 

the MAST task cycle. 

UNINTENDED OUTPUT VALUES 

WARNING 

Only use the Function Block instance in the MAST task. 

Do not use the same Function Block instance in a different task. 



NOTE: Forcing the logical output values of the FB is allowed by SoMachine but it 

will have no impact on hardware related outputs if the function is active (executing).


52 04/2012

Overview 


Functions 

04/2012 

Functions 

This chapter describes the functions of the HSC Library. 



04/2012 53 

7 

Topic Page 

HMI_HSCStart: Start the HSC 54 

HMI_HSCStop: Stop the HSC 55 

HMI_HSCGetCurrentValue: Get the HSC Current Value 56 

HMI_HSCGetCapturedValue: Get the HSC Value 57 

HMI_GetSynchronizedOutput: Get Synchronized Output Status 58 

HMI_ClearSynchronizedOutput: Clear Synchronized Output Status 59 

HMI_SetCounterValue: Set the HSC Value 60 

HMI_ClearCounterValue: Clear the HSC Value 61 

HMI_GetPreLoadStatus: Detect Preload Input Signal 62 

HMI_ClearPreLoadStatus: Clear PreLoad Status 63 

HMI_GetPreStrobeStatus: Get PreStrobe Status 64 

HMI_ClearPreStrobeStatus: Clear PreStrobe Status 65 

HMI_GetMarkerStatus: Detect Hardware Marker Input Signal 66 

HMI_ClearMarkerStatus: Clear the Marker Status 67

Functions 

HMI_HSCStart: Start the HSC 

Function Description 

This function is used to start the HSC function. The couting is enabled and any 

pulses present before the start of the HSC counter are ignored. 

Graphical Representation (LD/FBD) 

IL and ST Representation 

To see the general representation in IL or ST language, please refer to the chapter 

How to Use IL and ST Representation (see page 71). 

Parameter Description 

The following table describes the input parameters: 

Parameter Type Comment 

Enable VAR_INPUT Enable if true 

CH VAR_INPUT Channel number of the HSC 1 

Legend 

1 An out of range CH value sets the FB output to a false state. The CH values 

can be: 

For a 1-Phase HSC: from 0 to 3 

For a one 2-Phase HSC: 0 

For a two 2-Phase HSC: 0 or 2 

The following table describes the output parameter: 


HMI_HSCStart VAR_OUTPUT HSC started successfully 

54 04/2012

HMI_HSCStop: Stop the HSC 


This function is used to stop the HSC function. 


Functions 








CH VAR_INPUT Channel number of the HSC1 Legend 

1 An out of range CH value sets the FB output to a false state. 

The CH values can be: 






HMI_HSCStop VAR_OUTPUT HSC stopped successfully 

04/2012 55

Functions 

HMI_HSCGetCurrentValue: Get the HSC Current Value 


This function is used to get the current value of the HSC. 

















HMI_HSCGetCurrentValue VAR_OUTPUT HSC current value 

56 04/2012

HMI_HSCGetCapturedValue: Get the HSC Value 

Functions 


This function is used to get the HSC value when the PreStrobe input is triggered. 

















HMI_HSCGetCapturedValue VAR_OUTPUT HSC value on PreStrobe input 

trigger 

04/2012 57

Functions 

HMI_GetSynchronizedOutput: Get Synchronized Output Status 


This function is used to get the status of the synchronized output. 

















HMI_GetSynchronizedOutput VAR_OUTPUT The function returns a true 

state on a synchronized output 

detection, and a false state 

otherwise. 

58 04/2012

HMI_ClearSynchronizedOutput: Clear Synchronized Output Status 


This function is used to clear the status of synchronized ouput. 


Functions 

After the operation is completed, synchronized outputs are managed according to: 

the counter evolution 

the ON and OFF preset values 







Enable VAR_INPUT Clear Status if true 









HMI_ClearSynchronizedOutput VAR_OUTPUT The function returns a 

true state if successful 

and a false state 

otherwise. 

04/2012 59

Functions 

HMI_SetCounterValue: Set the HSC Value 


This function is used to set the HSC value. 








Enable VAR_INPUT Set if true 

CH VAR_INPUT Channel number of the HSC1 NewValue 

Legend 

VAR_INPUT Value to set 








HMI_SetCounterValue VAR_OUTPUT The function returns a true state if 

successful and a false state 

otherwise. 

60 04/2012

HMI_ClearCounterValue: Clear the HSC Value 


This function is used to clear the HSC value (set to 0). 


Functions 







Enable VAR_INPUT Clear if true 


Legend 








HMI_ClearCounterValue VAR_OUTPUT The function returns a true state if 


otherwise. 

04/2012 61

Functions 

HMI_GetPreLoadStatus: Detect Preload Input Signal 


This function is used to detect a hardware Preload input signal. The Preload status 

must be cleared prior the next Preload status detection. 








Enable VAR_INPUT Get Status if true 









HMI_GetPreLoadStatus VAR_OUTPUT The function returns a true state if 


otherwise. 

62 04/2012

HMI_ClearPreLoadStatus: Clear PreLoad Status 

Functions 


This function is used to clear the PreLoad status in order to detect the next PreLoad 

hardware input trigger. 








Enable VAR_INPUT Clear PreLoad status if true 









HMI_ClearPreLoadStatus VAR_OUTPUT The function returns a true state if 


otherwise. 

04/2012 63

Functions 

HMI_GetPreStrobeStatus: Get PreStrobe Status 


This function is used to detect a hardware PreStrobe input signal. The PreStrobe 

status must be cleared prior the next PreStrobe status detection. 








Enable VAR_INPUT Get PreLoad Status if true 









HMI_GetPreStrobeStatus VAR_OUTPUT The function returns a true state if 

the PreStrobe input signal is 

detected and a false state 

otherwise. 

64 04/2012

HMI_ClearPreStrobeStatus: Clear PreStrobe Status 


This function is used to clear the PreStrobe status in order to detect the next 

PreStrobe hardware input trigger. 


Functions 
















HMI_ClearPreStrobeStatus VAR_OUTPUT The function returns a true 

state if successful and a false 

state otherwise. 

04/2012 65

Functions 

HMI_GetMarkerStatus: Detect Hardware Marker Input Signal 


This function is used to detect a hardware marker input signal. The marker status 

must be cleared before the next marker status detection. 










Legend 








HMI_GetMarkerStatus VAR_OUTPUT The function returns a true state if 

there is a marker signal and a false 

state otherwise. 

66 04/2012

HMI_ClearMarkerStatus: Clear the Marker Status 

Functions 


This function is used to clear the marker status in order to detect the next marker 

input trigger (rising edge). 



To see the general representation in IL or ST language, please refer to the How to 

Use IL and ST Representation (see page 71) chapter. 













HMI_ClearMarkerStatus VAR_OUTPUT The function returns a true state if 


otherwise. 

04/2012 67

Functions 

68 04/2012


04/2012 

Appendices 

04/2012 69

70 04/2012

Overview 


Function and Function Block Representation 

04/2012 

Function and Function Block 

Representation 

Each function can be represented in the following languages: 

IL: Instruction List 

ST: Structured Text 

LD: Ladder Diagram 

FBD: Function Block Diagram 

CFC: Continuous Function Chart 

A 

This chapter provides functions and function blocks representation examples and 

explains how to use them for IL and ST languages. 



Topic Page 

Differences Between a Function and a Function Block 72 

How to Use a Function or a Function Block in IL Language 73 

How to Use a Function or a Function Block in ST Language 76 

04/2012 71


Differences Between a Function and a Function Block 

Function 

Function Block 

A function: 

is a POU (Program Organization Unit) that returns one immediate result 

is directly called with its name (not through an Instance) 

has no persistent state from one call to the other 

can be used as an operand in other expressions 

Examples: boolean operators (AND), calculations, conversion (BYTE_TO_INT) 

A function block: 

is a POU (Program Organization Unit) that returns one or more outputs 

is always called through an Instance (function block copy with dedicated name 

and variables) 

each Instance has a persistent state (outputs and internal variables) from one 

call to the other 

Examples: timers, counters 

In the example below, Timer_ON is an instance of the Function Block TON: 

72 04/2012

How to Use a Function or a Function Block in IL Language 



This part explains how to implement a Function and a Function Block in IL language. 

Functions IsFirstMastCycle and SetRTCDrift and Function Block TON are 

used as examples to show implementations. 

Using a Function in IL Language 

The following procedure describes how to insert a function in IL language: 

Step Action 

1 Open or create a new POU in Instruction List language. 

NOTE: The procedure to create a POU is not detailed here. For more information, refer to the SoMachine 

global help. 

2 Create the variables that the function requires. 

3 If the function has 1 or more inputs, start loading the first input using LD instruction. 

4 Insert a new line below and: 

type the name of the function in the operator column (left field), or 

use the Input Assistant to select the function (select Insert Box in context menu). 

5 If the function has more than 1 input and when Input Assistant is used, the necessary number of lines is 

automatically created with ??? in the fields on the right. Replace the ??? with the appropriate value or 

variable that corresponds to the order of inputs. 

6 Insert a new line to store the result of the function into the appropriate variable: type ST instruction in the 

operator column (left field) and the variable name in the field on the right. 

To illustrate the procedure, consider the Functions IsFirstMastCycle (without 

input parameter) and SetRTCDrift (with input parameters) graphically presented 

below: 

Function Graphical Representation 

without input parameter: 

IsFirstMastCycle 

with input parameters: 

SetRTCDrift 

04/2012 73


In IL language, the function name is used directly in the Operator Column: 

Function Representation in SoMachine POU IL Editor 

IL example of a function 

without input parameter: 

IsFirstMastCycle 

IL example of a function 

with input parameters: 

SetRTCDrift 

Using a Function Block in IL language 

The following procedure describes how to insert a function block in IL language: 

Step Action 

1 Open or create a new POU in Instruction List language. 


global help. 

2 Create the variables that the function block requires, including the instance name. 

74 04/2012

Step Action 


3 Function Blocks are called using a CAL instruction: 

Use the Input Assistant to select the FB (right-click and select Insert Box in context menu). 

Automatically, the CAL instruction and the necessary I/O are created. 

Each parameter (I/O) is an instruction: 

Value to inputs are set by ":=". 

Values to outputs are set by "=>". 

4 In the CAL right-side field, replace ??? with the instance name. 

5 Replace other ??? with an appropriate variable or immediate value. 

To illustrate the procedure, consider this example with the TON Function Block 

graphically presented below: 

Function Block Graphical Representation 

TON 

In IL language, the function block name is used directly in the Operator Column: 

Function Block Representation in SoMachine POU IL Editor 

TON 

04/2012 75


How to Use a Function or a Function Block in ST Language 


This part explains how to implement a Function and a Function Block in ST 

language. 

Function SetRTCDrift and Function Block TON are used as examples to show 

implementations. 

Using a Function in ST Language 

The following procedure describes how to insert a function in ST language: 

Step Action 

1 Open or create a new POU in Structured Text language. 


global help. 

2 Create the variables that the function requires. 

3 Use the general syntax in the POU ST Editor for the ST language of a function. The general syntax is: 

FunctionResult:= FunctionName(VarInput1, VarInput2,.. VarInputx); 

To illustrate the procedure, consider the function SetRTCDrift graphically 

presented below: 

Function Graphical Representation 

SetRTCDrift 

The ST language of this function is the following: 

Function Representation in SoMachine POU ST Editor 

SetRTCDrift PROGRAM MyProgram_ST 

VAR myDrift: SINT(-29..29) := 5; 

myDay: DAY_OF_WEEK := SUNDAY; 

myHour: HOUR := 12; 

myMinute: MINUTE; 

myRTCAdjust: RTCDRIFT_ERROR; 

END_VAR 

myRTCAdjust:= SetRTCDrift(myDrift, myDay, myHour, myMinute); 

76 04/2012


Using a Function Block in ST Language 

The following procedure describes how to insert a function block in ST language: 

Step Action 

1 Open or create a new POU in Structured Text language. 


global help. 

2 Create the input and output variables and the instance required for the function block: 

Input variables are the input parameters required by the function block 

Output variables receive the value returned by the function block 

3 Use the general syntax in the POU ST Editor for the ST language of a Function Block. The general syntax 

is: 

FunctionBlock_InstanceName(Input1:=VarInput1, Input2:=VarInput2,... 

Ouput1=>VarOutput1, Ouput2=>VarOutput2,...); 

To illustrate the procedure, consider this example with the TON function block 

graphically presented below: 

Function Block Graphical Representation 

TON 

The following table shows examples of a function block call in ST language: 

Function Block Representation in SoMachine POU ST Editor 

TON 

04/2012 77


78 04/2012

1-phase counter 

2-phase counter 

BOOL 

Boot application 


Glossary 

04/2012 

Glossary 

0-9 

A 1-phase counter uses 1 hardware input as counter input. It usually counts up or 

counts down when there is pulse signal in the input. 

A 2-phase counter uses the phase difference between 2 input counter signals to 

count up or count down. 

B 

A Boolean type is the basic data type in computing. A BOOL variable can have one 

of these values: 0 (FALSE), 1 (TRUE). A bit that is extracted from a word is of type 

BOOL, for example: %MW10.4 is a fifth bit a memory word number 10. 

Files that contain machine dependent parameters: 

machine name 

device name or IP address 

Modbus Serial Line address 

Routing table 

04/2012 79

Glossary 

BOOTP 

BYTE 

CAN 

CANopen 

CFC 

controller 

The Bootstrap Protocol is a UDP network protocol that can be used by a network 

client to automatically obtain an IP address (and possibly other data) from a server. 

The client identifies itself to the server using the client’s MAC address. The server— 

which maintains a pre-configured table of client device MAC addresses and 

associated IP addresses—sends the client its pre-configured IP address. BOOTP 

was originally used as a method that enabled diskless hosts to be remotely booted 

over a network. The BOOTP process assigns an infinite lease of an IP address. The 

BOOTP service utilizes UDP ports 67 and 68. 

When 8 bits are grouped together, they are called a BYTE. You can enter a BYTE 

either in binary mode or in base 8. The BYTE type is encoded in an 8-bit format that 

ranges from 16#00 to 16#FF (in hexadecimal format). 

C 

The Controller Area Network protocol (ISO 11898) for serial bus networks is 

designed for the interconnection of smart devices (from multiple manufacturers) in 

smart systems for real-time industrial applications. CAN multi-master systems 

ensure high data integrity through the implementation of broadcast messaging and 

advanced diagnostic mechanisms. Originally developed for use in automobiles, 

CAN is now used in a variety of industrial automation control environments. 

CANopen is an open industry-standard communication protocol and device profile 

specification. 

The Continuous Function Chart (an extension of the IEC61131-3 standard) is a 

graphical programming language that works like a flowchart. By adding simple 

logicals blocks (AND, OR, etc.), each function or function block in the program is 

represented in this graphical format. For each block, the inputs are on the left and 

the outputs on the right. Block outputs can be linked to inputs of other blocks in order 

to create complex expressions. 

A controller (or “programmable logic controller,” or “programmable controller”) is 

used to automate industrial processes. 

80 04/2012

expansion bus 

E 

Glossary 

The expansion bus is an electronic communication bus between expansion modules 

and a CPU. 

expansion I/O module 

An expansion input or output module is either a digital or analog module that adds 

additional I/O to the base controller. 

FBD 

firmware 

Function Block 

F 

A Function Block Diagram is a graphically oriented programming language, 

compliant with IEC 61131-3. It works with a list of networks whereby each network 

contains a graphical structure of boxes and connection lines which represents either 

a logical or arithmetic expression, the call of a function block, a jump, or a return 

instruction. 

The firmware represents the operating system on a controller. 

(FB) A Program unit of inputs and variables organized to calculate values for outputs 

based on a defined function such as a timer or a counter. 

Function Block Diagram language 

(FBD) A function block diagram describes a function between input variables and 

output variables. A function is described as a set of elementary blocks. Input and 

output variables are connected to blocks by connection lines. An output of a block 

may also be connected to an input of another block. 

GVL 

G 

The Global Variable List manages global variables that are available in every 

application POU. 

04/2012 81

Glossary 

HMI 

HSC 

IEC 61131-3 

IL 

LD 

located variable 

H 

A human-machine interface is an operator interface (usually graphical) for industrial 

equipment. 

high-speed counter 

I 

The IEC 61131-3 is an international electrotechnical commission standard for 

industrial automation equipment (like controllers). IEC 61131-3 deals with controller 

programming languages and defines 2 graphical and 2 textual programming 

language standards: 

graphical: ladder diagram, function block diagram 

textual: structured text, instruction list 

A program written in the Instruction List language is composed of a series of 

instructions executed sequentially by the controller. Each instruction includes a line 

number, an instruction code, and an operand. (IL is IEC 61131-3 compliant.) 

L 

A program in the Ladder Diagram language includes a graphical representation of 

instructions of a controller program with symbols for contacts, coils, and blocks in a 

series of rungs executed sequentially by a controller. IEC 61131-3 compliant. 

A located variable has an address. (See unlocated variable.) 

82 04/2012

Modbus 

NEMA 

PLC 

PLI 

POU 

PTO 

M 

The Modbus communication protocol allows communications between many 

devices connected to the same network. 

N 

Glossary 

The National Electrical Manufacturers Association publishes standards for the 

performance of various classes of electrical enclosures. The NEMA standards cover 

corrosion resistance, ability to protect from rain and submersion, etc. For IEC 

member countries, the IEC 60529 standard classifies the ingress protection rating 

for enclosures. 

P 

The Programmable Logic Controller is the “brain” of an industrial manufacturing 

process. It automates a process, used instead of relay control systems. PLCs are 

computers suited to survive the harsh conditions of the industrial environment. 

Pulse Latch Input 

A Program Organization Unit includes a variable declaration in source code and the 

corresponding instruction set. POUs facilitate the modular reuse of software 

programs, functions, and function blocks. Once declared, POUs are available to one 

another. SoMachine programming requires the utilization of POUs. 

Pulse Train Outputs are used to control for instance stepper motors in open loop. 

04/2012 83

Glossary 

PWM 

reflex output 

retained data 

RTC 

SFC 

Structured Text 

system variable 

Pulse Width Modulation is used for regulation processes (e.g. actuators for 

temperature control) where a pulse signal is modulated in its length. For these kind 

of signals, transistor outputs are used. 

R 

In a counting mode, the high speed counter’s current value is measured against its 

configured thresholds to determine the state of these dedicated outputs. 

A retained data value is used in the next power-on or warm start. The value is 

retained even after an uncontrolled shutdown of the controller or a normal switch-off 

of the controller. 

The real-time clock option keeps the time for a limited amount of time even when the 

controller is not powered. 

S 

A program written in the Sequential Function Chart language can be used for 

processes that can be split into steps. SFC is composed of steps with associated 

actions, transitions with associated logic condition, and directed links between steps 

and transitions. (The SFC standard is defined in IEC 848. It is IEC 61131-3 

compliant.) 

A program written in the structured text (ST) language includes complex statements 

and nested instructions (such as iteration loops, conditional executions, or 

functions). ST is compliant with IEC 61131-3. 

A system variable structure provides controller data and diagnostic information and 

allows sending commands to the controller. 

84 04/2012

U 

unlocated variable 

An unlocated variable does not have an address. (See located variable.) 

Glossary 

04/2012 85

Glossary 

86 04/2012


Index 

04/2012 

Index 

0-9 

1-Phase Counter 

Down/Falling Mode, 34 

Down/Rising Mode, 32 

Overview, 30 

Up/Falling Edge Mode, 33 

Up/Rising Mode, 31 

2-Phase Counter 

Mode 0, 39 

Mode 1, 40 

Mode 2, 41 

Mode 3, 42 

Overview, 38 

Specifications, 43 

C 

ClearCounterValue, 61 

ClearMarkerStatus, 67 

ClearPreLoadStatus, 63 

ClearPreStrobeStatus, 65 

ClearSynchronizedOutput, 59 

Combination 

Special I/O, 16 

Configuration 

HSC, 45 

Special I/O, 13 

04/2012 87 

CBA 

F 

Functions 

Dedicated, 51 

Differences Between a Function and a 

Function Block, 72 

How to Use a Function or a Function 

Block in IL Language, 73 

How to Use a Function or a Function 

Block in ST Language, 76 

G 

GetMarkerStatus, 66 

GetPreLoadStatus, 62 

GetSynchronizedOutput, 58 

H 

HSC, 26 

1-Phase Counter, 30, 35 

2-Phase Counter, 38 

Characteristics, 28 

Configuration, 45 

Library, 49 

Number of channels, 26 

Operating Frequency, 26 

Overview, 25 

Use Case, 26

Index 


ClearCounterValue, 61 

ClearMarkerStatus, 67 

ClearPreStrobeStatus, 65 

ClearSynchronized, 59 

GetMarkerStatus, 66 

GetPreLoadStatus, 62 

GetSynchronizedOutput, 58 

HGetPreLoadStatus, 63 

HSCGetCapturedValue, 57 

HSCGetCurrentValue, 56 

HSCStart, 54, 64 

HSCStop, 55 

SetCounterValue, 60 

HSCGetCapturedValue, 57 

HSCGetCurrentValue, 56 

HSCStart, 54, 64 

HSCStop, 55 

I 

I/Os 

Summary, 19 

L 

Local and Special I/O 

Overview, 14 

O 

Overview 

Local and Special I/O, 14 

S 

SetCounterValue, 60 

Special I/O 

Combination, 16 


Configuration, 13 

Summary 

I/Os, 19 

88 04/2012

Library manual XBTGC Expert I/O High speed counting | 3 MB

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?