2 Visual Components Manuals

Introduction to Visual Components 2.3

Introduction to Visual Components 2.3 

Contents (3.9.2005) 

1 Welcome to Visual Components.......................................................................................................................1 

1.1 Visualization in B&R Automation Studio...............................................................................................1 

1.2 Visual Components..............................................................................................................................1 

2 Visual Components Manuals............................................................................................................................3 

3 Visual Components Reference Manual............................................................................................................5 

3.1 Editor (Operation) Reference...............................................................................................................5 

3.1.1 Shortcut Keys − Reference.........................................................................................................5 

3.1.1.1 Picture Editor.....................................................................................................................5 

3.1.1.2 Fonts.................................................................................................................................5 

3.1.1.3 Bitmaps.............................................................................................................................5 

3.1.1.4 Text groups.......................................................................................................................5 

3.1.2 Toolbars − Reference.................................................................................................................5 

3.1.2.1 Project...............................................................................................................................6 

3.1.2.2 Picture Editor.....................................................................................................................6 

3.1.2.3 Variables...........................................................................................................................6 

3.1.2.4 Fonts.................................................................................................................................6 

3.1.2.5 Bitmaps.............................................................................................................................7 

3.1.2.6 Text Groups.......................................................................................................................7 

3.1.2.7 Alarm System....................................................................................................................7 

3.1.2.8 Languages.........................................................................................................................7 

3.2 Screen Elements (Fields) − Reference................................................................................................7 

3.2.1 Static Picture Elements − Reference..........................................................................................8 

3.2.1.1 Static Text Picture Element − Reference..........................................................................9 

3.2.1.2 Static Picture Element Line − Reference.........................................................................14 

3.2.1.3 Static Picture Element Rectangle − Reference...............................................................17 

3.2.1.4 Static Picture Element Ellipse − Reference.....................................................................21 

3.2.1.5 Static Picture Element Background Bitmap − Reference................................................24 

3.2.2 Input Fields − Reference...........................................................................................................26 

3.2.2.1 Numeric Input Field − Reference.....................................................................................27 

3.2.2.2 String Input Field − Reference........................................................................................40 

3.2.2.3 Password Input Field − Reference..................................................................................52 

3.2.2.4 ListBox Input Field − Reference......................................................................................60 

3.2.3 Output Fields − Reference........................................................................................................67 

3.2.3.1 Numeric Output Field − Reference..................................................................................68 

3.2.3.2 String Output Field − Reference......................................................................................77 

3.2.3.3 Date/Time Output Field − Reference...............................................................................82 

3.2.3.4 Advanced Text Output Field − Reference.......................................................................87 

3.2.3.5 Bar Graph Output Field − Reference..............................................................................93 

3.2.3.6 ListBox Output Field − Reference.................................................................................100 

3.2.3.7 Bitmap Graphic Output Field − Reference....................................................................105 

3.2.4 Touch−Operated Fields − Reference.....................................................................................109 

3.2.4.1 Button Touch−Operated Field − Reference..................................................................109 

3.2.4.2 HotSpot Touch−Operated Field − Reference................................................................124 

3.3 Programming Interface for Controller Tasks − VISAPI.....................................................................134 

3.3.1 Requirements and Initializing.................................................................................................134 

3.3.2 Graphics and Text................................................................................................................134 

3.3.3 Setting Contrast and Brightness...........................................................................................134 

3.3.4 Reading the Key Matrix........................................................................................................135 

3.3.5 Touch Screen .......................................................................................................................135 

3.3.6 Manual Project Control.........................................................................................................135 

3.3.7 Reading Alarm Lists.............................................................................................................135 

3.3.8 Palettes..................................................................................................................................135 

3.3.8.1 Copying a Rectangular Screen Area − VA_CopyScreenRect.......................................136 

3.3.8.2 Displaying a Bitmap − VA_DrawBitmap........................................................................137 

3.3.8.3 Deleting the Alarm History − VA_DelAlarmHistory........................................................138 

3.3.8.4 Graphics and Text Output − VA_Ellipse........................................................................139 

3.3.8.5 VA_ExchangeFont........................................................................................................140 

3.3.8.6 Read Current Alarm List − VA_GetActAlarmList...........................................................140 

i



3 Visual Components Reference Manual 

3.3.8.7 Reading Alarm Lists − VA_GetAlarmList.......................................................................142 

3.3.8.8 Alarm Information at the Cursor Position − VA_GetAlCurPos.......................................143 

3.3.8.9 Touch Screen Calibration − VA_GetCalStatus..............................................................144 

3.3.8.10 Determining Contrast − VA_GetContrast....................................................................146 

3.3.8.11 Reading Display Information − VA_GetDisplayInfo.....................................................147 

3.3.8.12 Reading Alarm Lists − VA_GetExAlarmList................................................................148 

3.3.8.13 Reading the Key Matrix − VA_GetKeyMatrix..............................................................149 

3.3.8.14 Querying the Palette Color − VA_GetPaletteColor......................................................149 

3.3.8.15 Graphics and Text Output − VA_GetTextByTextGroup..............................................150 

3.3.8.16 User−Defined Touch Operation − VA_GetTouchAction..............................................151 

3.3.8.17 VA_Invblnk.................................................................................................................153 

3.3.8.18 Graphics and Text Output − VA_Line.........................................................................153 

3.3.8.19 Acknowledging Alarms from a Certain Group − VA_QuitAlarms.................................154 

3.3.8.20 Graphics and Text Output − VA_Rect.........................................................................155 

3.3.8.21 Graphics and Text Output − VA_Redraw....................................................................156 

3.3.8.22 Requirements and Initialization − VA_Saccess...........................................................157 

3.3.8.23 Saving Settings − VA_SaveSettings...........................................................................159 

3.3.8.24 Disable − enable backlight − VA_SetBacklight...........................................................160 

3.3.8.25 Setting Contrast and Brightness − VA_SetBrightness................................................160 

3.3.8.26 Setting Contrast and Brightness − VA_SetContrast....................................................161 

3.3.8.27 Setting the Palette Color − VA_SetPaletteColor.........................................................163 

3.3.8.28 Requirements and Initialization − VA_Setup...............................................................164 

3.3.8.29 Requirements and Initialization − VA_SetupX.............................................................165 

3.3.8.30 Manual Project Control − VA_SetUserParam.............................................................165 

3.3.8.31 Shutdown − VA_Shutdown.........................................................................................166 

3.3.8.32 Requirements and Initialization − VA_Srelease..........................................................166 

3.3.8.33 Manual Project Control − VA_StartProject..................................................................167 

3.3.8.34 Touch Screen Calibration − VA_StartTouchCal..........................................................169 

3.3.8.35 Manual Project Control − VA_StopProject..................................................................169 

3.3.8.36 Graphics and Text Output − VA_Textout....................................................................171 

3.3.9 Color Table − VISAPI..............................................................................................................172 

3.3.9.1 Color Palette for IPC Color Displays Reserved Colors: 255 − can be used for 

transparent effect........................................................................................................172 

3.3.9.2 Color Palette for SG3 Black/White DisplaysReserved Colors: none...........................174 

3.3.10 Error Codes − VISAPI...........................................................................................................174 

3.3.10.1 Error Codes.................................................................................................................174 

3.4 Supported Hardware − Reference...................................................................................................175 

3.4.1 Key Matrix...............................................................................................................................175 

3.4.1.1 Operator Panels for the CAN Controller C130..............................................................175 

3.4.1.2 PowerPanel Controllers.................................................................................................175 

3.4.1.3 Operator Panels for the IPC2001 Family......................................................................175 

3.4.1.4 Operator Panels for the IPC5000 Family......................................................................175 

3.4.2 Key Matrix − Panel 4B1270.00−490.......................................................................................175 

3.4.3 Key Matrix − Panel 4D1164.00−590.......................................................................................176 




3.4.7 Key Matrix − Panel 4P0420.00−490.......................................................................................179 

3.4.8 Key Matrix − Panel 4P3040.00−490.......................................................................................180 

3.4.9 Key Matrix − Panel 5D2000.02...............................................................................................181 

3.4.10 Key Matrix − Panel 5D2210.01.............................................................................................182 

3.4.11 Key Matrix − Panel 5D2210.01C (Compact IPC2001)..........................................................183 








ii






















3.5 Software Modules on the Controller.................................................................................................206 

3.5.1 Executable Visual Components Modules...............................................................................206 

3.5.1.1 Module Versions............................................................................................................207 

3.5.1.2 VC Project Management Module..................................................................................207 

3.5.1.3 VC Interpreter Module...................................................................................................207 

3.5.1.4 VC VGA Display Driver.................................................................................................207 

3.5.1.5 VC IPC Key Driver.........................................................................................................207 

3.5.1.6 VC IPC Touch Driver.....................................................................................................208 

3.5.1.7 VC CAN Panel Driver....................................................................................................208 

3.5.1.8 VC Power Panel Driver.................................................................................................208 

3.5.1.9 VC Printer Driver...........................................................................................................208 

3.5.1.10 VC AT Keyboard Driver...............................................................................................208 

3.5.1.11 VC Graphics Driver for PPxx.......................................................................................208 

3.5.1.12 VC Graphics Driver for PPxx.......................................................................................209 

3.5.1.13 Compact IPC2001 Modules (Example).......................................................................209 

3.5.1.14 CP360 Modules (Example).........................................................................................209 

3.5.1.15 CP476 Modules (Example).........................................................................................210 

3.5.2 Visual Components Data Modules.........................................................................................211 

3.5.3 Internal Details About Project Storage....................................................................................211 

3.5.3.1 Project Storage Example...............................................................................................211 

4 Visual Components User's Manual..............................................................................................................215 

4.1 Welcome to Visual Components......................................................................................................215 

4.1.1 New Functions in Visual Components 2.4..............................................................................215 

4.1.2 New Visapi Functions.............................................................................................................215 




4.2 Getting Started with Visual Components 2.4....................................................................................219 

4.2.1 CP476 with B127 CAN Display − Example.............................................................................219 

4.2.1.1 CAN − Step 1: Creating a New Automation Studio Project...........................................219 

4.2.1.2 CAN − Step 2: Inserting a Display.................................................................................220 

4.2.1.3 CAN − Step 3: Inserting PV Variables...........................................................................223 

4.2.1.4 CAN − Step 4: Applying Global Settings to Visual Components...................................227 

4.2.1.5 CAN − Step 5: Inserting an Input Field..........................................................................227 

4.2.1.6 CAN − Step 6: Inserting an Output Field.......................................................................229 

4.2.1.7 CAN − Step 7: Connecting an LED with a Process Variable.........................................231 

4.2.1.8 CAN − Step 8: Defining INC/DEC Keys........................................................................232 

4.2.1.9 CAN − Step 9: Compiling and Transferring the Project.................................................233 

4.2.1.10 CAN − Step 10: Test Operations.................................................................................234 

4.2.2 Compact IPC2002 − Example................................................................................................235 

iii



4 Visual Components User's Manual 

4.2.2.1 IPC − Step 1: Creating a New Automation Studio Project.............................................235 

4.2.2.2 IPC − Step 2: Inserting a Display..................................................................................236 

4.2.2.3 IPC − Step 3: Inserting PV Variables............................................................................239 

4.2.2.4 IPC − Step 4: Applying Global Settings to Visual Components.....................................242 

4.2.2.5 IPC − Step 5: Adding Pictures.......................................................................................243 

4.2.2.6 IPC − Step 6: Adding Bitmaps.......................................................................................244 

4.2.2.7 IPC − Step 7: Creating a Text Group............................................................................246 

4.2.2.8 IPC − Step 8: Creating HotSpots for Changing Pictures...............................................248 

4.2.2.9 IPC − Step 9: Page 1 (INIT_PIC) − Inserting a Dynamic Bitmap..................................251 

4.2.2.10 IPC − Step 10: Page 2 − Ellipse with a Dynamic, Changeable Fill Color....................256 

4.2.2.11 IPC − Step 11: Page 3 − Inserting a ListBox with Control Buttons..............................258 

4.2.2.12 IPC − Step 12: Compiling and Transferring the Project..............................................261 

4.2.2.13 IPC − Step 13: Test Operations..................................................................................262 

4.2.3 Getting Started with the VISAPI Programming Interface........................................................263 

4.2.3.1 Visapi − Tutorial − Inserting the Visapi Library..............................................................263 

4.2.3.2 Visapi − Tutorial − Inserting a Cyclic Task....................................................................265 

4.2.3.3 Visapi − Tutorial − Automation Basic Example.............................................................267 

4.2.3.4 Visapi − Tutorial − Preparing the C Example................................................................268 

4.2.3.5 Visapi − Tutorial − Finishing the C Example.................................................................270 

4.2.4 Sample Projects......................................................................................................................271 

4.2.4.1 Example: Step 1............................................................................................................271 

4.2.4.2 Example: Step 2............................................................................................................271 

4.2.4.3 Example: Step 3............................................................................................................271 

4.2.4.4 Example: Step 4............................................................................................................272 

4.2.4.5 Example: Step 5............................................................................................................272 

4.2.4.6 Example: Step 6............................................................................................................272 

4.2.4.7 Example: Step 7 − CAN ..............................................................................................272 

4.2.4.8 Example: Step 8 − VGA / CAN.....................................................................................272 

4.2.4.9 Example: VC_Demo......................................................................................................272 

4.2.4.10 Example: VC_WebDemo............................................................................................273 

4.2.4.11 Example: VC_Alarm....................................................................................................273 

4.3 Working with Visual Components.....................................................................................................273 

4.3.1 Resource Types......................................................................................................................274 

4.3.2 Creating a Visual Components Project...................................................................................274 

4.3.2.1 Creating a Visual Components Project.........................................................................274 

4.3.2.2 Inserting a Panel Object................................................................................................275 

4.3.3 Creating Advanced Visual Components Projects...................................................................276 

4.3.3.1 Several Software Objects and One Panel.....................................................................277 

4.3.3.2 Several Software Objects and Several Panels..............................................................277 

4.3.4 Editor Views............................................................................................................................278 

4.3.5 Picture Management...............................................................................................................278 

4.3.5.1 General Picture Management.......................................................................................278 

4.3.5.2 Adding a New Picture....................................................................................................279 

4.3.5.3 Deleting a Picture..........................................................................................................280 

4.3.5.4 Renaming a Picture.......................................................................................................280 

4.3.5.5 Changing the Picture Sequence....................................................................................280 

4.3.5.6 Changing Special Picture Properties.............................................................................280 

4.3.5.7 Defining the Start Picture..............................................................................................281 

4.3.5.8 Defining the Global Picture............................................................................................282 

4.3.6 Picture Editor..........................................................................................................................282 

4.3.6.1 General Picture Editor Operation..................................................................................282 

4.3.6.2 Grid and Snap−to−Grid Functions.................................................................................282 

4.3.6.3 Zoom Function..............................................................................................................283 

4.3.7 Variable Editor........................................................................................................................283 

4.3.7.1 Variable Editor...............................................................................................................283 

4.3.7.2 Variable View by Picture...............................................................................................284 

4.3.7.3 Variable Selection Dialog Box.......................................................................................285 

4.3.8 Text Group Editor...................................................................................................................285 

4.3.8.1 Text Group Editor (Overview)........................................................................................285 

iv




4.3.8.2 Inserting a New Text Group..........................................................................................286 

4.3.8.3 Inserting a Text into a Text Group.................................................................................286 

4.3.8.4 Changing Texts in a Text Group...................................................................................287 

4.3.8.5 Deleting Texts and Text Groups....................................................................................287 

4.3.8.6 Arranging Texts in a Group...........................................................................................287 

4.3.8.7 Variable Numbering of Text Groups..............................................................................287 

4.3.9 Bitmap Management...............................................................................................................288 

4.3.9.1 Bitmap Manager Overview............................................................................................288 

4.3.9.2 Inserting Bitmaps .........................................................................................................289 

4.3.9.3 Creating Bitmaps...........................................................................................................290 

4.3.9.4 Editing Bitmaps.............................................................................................................290 

4.3.9.5 Deleting Bitmaps...........................................................................................................290 

4.3.9.6 External Bitmap Editor..................................................................................................291 

4.3.9.7 Transparent Bitmaps.....................................................................................................291 

4.3.9.8 Color Table....................................................................................................................292 

4.3.10 Font Management.................................................................................................................293 

4.3.10.1 General Font Management.........................................................................................293 

4.3.10.2 Inserting Fonts.............................................................................................................294 

4.3.10.3 Changing Fonts...........................................................................................................295 

4.3.10.4 Deleting Fonts.............................................................................................................295 

4.3.10.5 B&R, Standard Fonts, and Windows..........................................................................295 

4.3.10.6 More Information About Fonts.....................................................................................295 

4.3.11 Language Management........................................................................................................296 

4.3.12 Color Configuration...............................................................................................................296 

4.3.12.1 Setting Standard Colors..............................................................................................296 

4.3.12.2 Dynamic Color Control................................................................................................298 

4.3.13 Importing / Exporting Resources..........................................................................................298 

4.3.13.1 Exporting Pictures.......................................................................................................299 

4.3.13.2 Importing Pictures.......................................................................................................300 

4.3.14 Project Options.....................................................................................................................301 

4.3.14.1 Project−Specific Configuration....................................................................................301 

4.3.15 Project Options.....................................................................................................................305 

4.3.15.1 Global Settings − General...........................................................................................305 

4.3.15.2 Global Settings − Project.............................................................................................306 

4.3.15.3 Global Settings − Picture.............................................................................................307 

4.3.15.4 Grid − Settings............................................................................................................307 

4.4 Visual Components User's Manual..................................................................................................308 

4.4.1 Touch Configuration...............................................................................................................308 

4.4.1.1 Change Settings............................................................................................................309 

4.5 Arranging Static Picture Components..............................................................................................310 

4.5.1 Texts.......................................................................................................................................310 

4.5.1.1 Inserting Text.................................................................................................................310 

4.5.1.2 Texts..............................................................................................................................311 

4.5.1.3 Texts..............................................................................................................................312 

4.5.1.4 Texts..............................................................................................................................314 

4.5.2 Lines.......................................................................................................................................314 

4.5.2.1 Drawing Lines................................................................................................................314 

4.5.3 Rectangle and Square............................................................................................................315 

4.5.3.1 Drawing Rectangles......................................................................................................315 

4.5.3.2 Rectangle and Square...................................................................................................316 

4.5.4 Ellipse and Circle....................................................................................................................317 

4.5.4.1 Drawing Circles and Ellipses.........................................................................................317 

4.5.4.2 Ellipse and Circle...........................................................................................................317 

4.5.5 Arranging Static Picture Components.....................................................................................318 

4.5.5.1 Overlapping Static Objects............................................................................................318 

4.5.6 Background Bitmaps...............................................................................................................320 

4.6 Configuring Output Fields for Data...................................................................................................321 

4.6.1 Recommendations..................................................................................................................321 

4.6.2 Displaying Texts and Numbers...............................................................................................322 

v




4.6.2.1 General..........................................................................................................................322 

4.6.2.2 Output Numeric.............................................................................................................325 

4.6.2.3 Output String.................................................................................................................327 

4.6.2.4 Output Date/Time..........................................................................................................327 

4.6.3 Displaying Analog Values.......................................................................................................328 

4.6.3.1 Bar Graph Output..........................................................................................................328 

4.6.4 Text and Graphics Output Using an Index..............................................................................331 

4.6.4.1 Advanced Text Output...................................................................................................332 

4.6.4.2 ListBox...........................................................................................................................334 

4.6.4.3 Bitmap Graphic..............................................................................................................335 

4.7 Configuring Input Fields for Data......................................................................................................337 

4.7.1 ListBox....................................................................................................................................337 

4.7.1.1 Text group .................................................................................................................337 

4.7.1.2 Option bytes.................................................................................................................338 

4.7.1.3 Cursor Character..........................................................................................................338 

4.7.1.4 Selected Item................................................................................................................338 

4.7.1.5 Status .................................................................................................................338 

4.7.1.6 Colors Foreground and background colors, as well color variables for the ListBox 

input control, can be specified for the selected item and the locked element in the 

Color dialog box..........................................................................................................338 

4.7.1.7 Completion Data Point..................................................................................................339 

4.7.1.8 Locking Input.................................................................................................................340 

4.7.1.9 Description...................................................................................................................340 

4.7.2 Numeric Input.........................................................................................................................341 

4.7.2.1 Formatting and Handling Input......................................................................................341 

4.7.2.2 Connecting Variables....................................................................................................344 

4.7.2.3 Additional Settings.........................................................................................................346 

4.7.3 Text Input................................................................................................................................347 

4.7.3.1 Formatting the Input......................................................................................................347 

4.7.3.2 Input Field Operation.....................................................................................................349 

4.7.3.3 Connecting Variables....................................................................................................350 

4.7.3.4 Additional Settings.........................................................................................................352 

4.7.4 Securing Input with Password Levels.....................................................................................352 

4.7.4.1 Configuring Locking for Input Fields..............................................................................353 

4.7.4.2 Entering Passwords......................................................................................................354 

4.7.5 Using Input Fields on Touch Screens.....................................................................................355 

4.7.5.1 Using Touch Keypads...................................................................................................355 

4.8 Advanced Control of Screen Elements............................................................................................358 

4.8.1 Recommendations for New Users..........................................................................................358 

4.8.2 Changing Colors Using Variables...........................................................................................358 

4.8.2.1 Connection....................................................................................................................359 

4.8.2.2 Color Variable Structure................................................................................................359 

4.8.2.3 Application Possibilities.................................................................................................360 

4.8.3 Controlling Fields with Status Variables.................................................................................361 

4.8.3.1 Connection....................................................................................................................361 

4.8.3.2 Assignment....................................................................................................................361 

4.8.3.3 Application Possibilities.................................................................................................363 

4.8.4 Advanced Text Group Options − Formatted Texts.................................................................363 

4.8.4.1 Connection....................................................................................................................364 

4.8.4.2 Format...........................................................................................................................364 

4.8.4.3 Data Point......................................................................................................................365 

4.9 VC Project Multilingual Capabilities..................................................................................................365 

4.9.1 Project Multilingual Capabilities..............................................................................................365 

4.9.1.1 Adding and Activating Text Layers................................................................................365 


4.9.2.1 Configuring Texts in Several Languages......................................................................366 


4.9.3.1 Switching Languages During the Design Phase...........................................................367 


vi




4.9.4.1 Text Groups in Several Languages...............................................................................368 

4.9.5 Multilingual Project Capabilities..............................................................................................368 

4.9.5.1 Switching Languages During Runtime..........................................................................368 

4.9.6 Multilingual Project Capabilities..............................................................................................369 

4.9.6.1 Importing and Exporting Texts......................................................................................369 

4.10 Keys, LED, and Touch Support......................................................................................................371 

4.10.1 Configuring Panel Keys........................................................................................................372 

4.10.2 Configuring Keys to Picture Levels.......................................................................................375 

4.10.2.1 Key Editor....................................................................................................................375 

4.10.2.2 Key List........................................................................................................................376 

4.10.2.3 Assigning Keys............................................................................................................376 

4.10.3 Creating Keys on the Touch Display....................................................................................378 

4.10.3.1 Inserting Touch−Operated Fields................................................................................378 

4.10.3.2 HotSpot.......................................................................................................................378 

4.10.3.3 Touch Button...............................................................................................................380 

4.10.4 Using Function Keys.............................................................................................................384 

4.10.4.1 Interaction with Control Variables................................................................................384 

4.10.4.2 Controlling Picture Changes........................................................................................387 

4.10.4.3 Navigating Input Fields................................................................................................388 

4.10.5 Configuring Several Key Levels............................................................................................389 

4.10.5.1 Setting the 'Switch Levels' Key....................................................................................389 

4.10.5.2 Configuring Additional Key Levels...............................................................................390 

4.10.5.3 Additional Settings.......................................................................................................391 

4.10.6 Configuring and Controlling LEDs........................................................................................391 

4.10.6.1 Configuration in the Editor...........................................................................................392 

4.10.6.2 Direct Operation from the Control Application.............................................................393 

4.10.7 Using the Key Matrix.............................................................................................................394 

4.10.7.1 Using the Key Matrix...................................................................................................394 

4.10.7.2 Key Matrix from Visual Components Version 2.0........................................................396 

4.11 Alarm System.................................................................................................................................396 

4.11.1 Notes for Visual Components Version 2.0 Users.................................................................397 

4.11.2 Preparations.........................................................................................................................397 

4.11.2.1 Defining the Alarm Bit Field.........................................................................................397 

4.11.2.2 Enabling the Alarm System.........................................................................................398 

4.11.3 Configuring the Alarm System..............................................................................................399 

4.11.3.1 Global Configuration....................................................................................................399 

4.11.4 Using Alarm Groups.............................................................................................................400 

4.11.4.1 Preset Alarms..............................................................................................................400 

4.11.4.2 Adding, Removing, and Editing Groups......................................................................401 

4.11.4.3 Alarm Group Parameters............................................................................................402 

4.11.5 Creating and Configuring Alarms..........................................................................................403 

4.11.5.1 Setting Up and Editing Alarms....................................................................................403 

4.11.5.2 Alarm Properties..........................................................................................................404 

4.11.6 Alarm Visualization...............................................................................................................406 

4.11.6.1 Alarm Line...................................................................................................................407 

4.11.6.2 Alarm List....................................................................................................................408 

4.11.6.3 Alarm Summary...........................................................................................................409 

4.11.6.4 Alarm History...............................................................................................................410 

4.11.7 Optimizing the Alarm Display................................................................................................411 

4.11.7.1 Adjusting the Display Format......................................................................................411 

4.11.7.2 Adjusting Status Abbreviations....................................................................................413 

4.11.7.3 Filtering the Displayed Alarm......................................................................................414 

4.11.8 Printing Alarms.....................................................................................................................416 

4.11.8.1 Activating the Alarm Printer.........................................................................................416 

4.11.8.2 Configuring the Printer................................................................................................416 

4.11.8.3 Configuring Status Texts.............................................................................................418 

4.11.8.4 Configuring the Print Format.......................................................................................418 

4.11.9 Group Alarms........................................................................................................................419 

4.11.9.1 Operation.....................................................................................................................419 

vii




4.11.9.2 Settings.......................................................................................................................420 

4.11.9.3 Choosing Alarms for the Group...................................................................................421 

4.11.10 Bypass and Acknowledgement Images..............................................................................422 

4.11.10.1 Usage........................................................................................................................422 

4.11.10.2 Setting Parameters....................................................................................................422 

4.11.11 General − VISAPI...............................................................................................................423 

4.11.11.1 General Information...................................................................................................423 

4.11.11.2 Requirements............................................................................................................424 

4.11.12 General/Drawing − VISAPI.................................................................................................425 

4.12 Tips and Tricks...............................................................................................................................425 

4.12.1 A Few Tips............................................................................................................................425 

4.12.2 Configuring a Help Picture....................................................................................................426 

4.12.2.1 Problem.......................................................................................................................426 

4.12.2.2 Solution.......................................................................................................................426 

4.12.3 Input Field Cursor Navigation..............................................................................................426 

4.12.3.1 Problem.......................................................................................................................426 

4.12.3.2 Solution.......................................................................................................................426 

4.12.4 Blinking Text (or Button)......................................................................................................427 

4.12.4.1 Problem.......................................................................................................................427 

4.12.4.2 Solution.......................................................................................................................427 

4.12.5 Adjusting the Touch Keypad.................................................................................................428 

4.12.6 Tips and Tricks.....................................................................................................................428 

4.12.6.1 Logging User Actions..................................................................................................428 

4.12.7 Tips and Tricks.....................................................................................................................429 

4.12.7.1 Creating Recipe Management.....................................................................................429 

4.12.7.2 Executing the Recipe Page.........................................................................................430 

4.12.7.3 Code in Automation Basic...........................................................................................431 

4.12.7.4 Code in ANSI C...........................................................................................................432 

4.12.8 VC System Tuning................................................................................................................432 

4.12.9 Tips and Tricks − Touch Pad................................................................................................433 

4.12.10 Importing / Exporting Panel Projects..................................................................................434 

4.12.10.1 Exporting Panel Objects............................................................................................434 

4.12.10.2 Importing Panel Objects............................................................................................436 

4.13 Frequently Asked Questions (FAQ)...............................................................................................438 

4.13.1 Frequently Asked Questions (FAQ) − Input Fields...............................................................438 

4.13.2 Frequently Asked Questions (FAQ) − Scaling......................................................................438 

4.13.2.1 General........................................................................................................................438 

4.13.2.2 Mathematics Reference..............................................................................................438 

4.13.2.3 Restrictions.................................................................................................................439 

4.13.2.4 Internal Performance..................................................................................................440 

4.13.2.5 Decimal Places..........................................................................................................440 

4.13.2.6 Scaling Output.............................................................................................................441 

4.13.2.7 Scaling Input................................................................................................................442 

4.13.3 Frequently Asked Questions (FAQ) − Keys..........................................................................443 

4.13.4 Frequently Asked Questions (FAQ) − VISAPI......................................................................443 

4.14 Upgrading Visual Components 2.0 Projects...................................................................................444 

4.14.1 Modification Notes................................................................................................................444 

4.14.1.1 Color Representation for IPC Projects........................................................................444 

4.14.1.2 Changing Pictures.......................................................................................................445 

4.14.1.3 API Functions from the VISAPI Library.......................................................................445 

4.14.1.4 Keys and Key Matrix for Touch Systems....................................................................445 

4.14.1.5 VCInfo Data Structure.................................................................................................446 

4.14.1.6 Character Set Representation.....................................................................................446 

4.14.1.7 Customer−Specific Panels..........................................................................................446 

4.14.2 Upgrading Visual Components 2.0 Projects.........................................................................446 

4.14.2.1 HotSpot Controls for the Key Matrix............................................................................446 

4.14.2.2 Calculating the Key Matrix...........................................................................................447 

viii

1 Welcome to Visual Components 

1.2 Visual Components 

1.1 Visualization in 

B&R Automation 

Studio 

In addition to supporting uniform 

configuration for control and 

positioning projects, B&R 

Automation Studio also provides 

the necessary platform used for 

structuring and integrating 

complete visualization 

applications. 

Visual Components can be used to configure visualization projects which use text and graphics. Possiblities for 

visualization applications are defined when the visualization hardware is selected in Automation Studio. Pictures 

can include input and output fields, as well as static or dynamic bitmaps. Using the common database interface, 

these are connected with control variables configured in the Automation Studio application. Static and dynamic 

texts can also be created for several languages. 

All parts of an automation application are saved together in a single project. The control program, motion objects 

(axis configuration and software), and the visualization application form a single functional unit which is 

controlled completely by Automation Studio. 

Once again, Version 2.4 has added many new functions. 

New users of Visual Components are recommended to start with the tutorials. Additional details can then be 

learned in the Working with Visual Components section. 

The User's Manual contains comprehensive introductions to all visualization elements. These are grouped 

according to their field of application. 

Details concerning Visual Components, its different fields, supported operator panels, and the runtime system 

are extensively covered in the Visual Components Reference Manual. 

Editing Visual Components projects which were created with Version 2.0 is described in the Upgrade Notes 

section. Projects which were created or edited with Visual Components Version 2.1 can immediately be opened 

and revised. Interfaces for touch−operated panels have to be reconfigured though. (See Touch Configuration) 

1 Welcome to Visual Components 1


2 1 Welcome to Visual Components

2 Visual Components Manuals 

Documentation for Visual Components consists of a User's Manual and a Reference Manual. 

Visual Components User's Manual 

The User's Manual describes all functions, operations, and processes involved in creating a Visual Components 

visualization application. FAQs and examples are also included so various tasks can be carried out. 

Visual Components Reference Manual 

The Reference Manual contains details about the various elements of a Visual Components visualization 

application, as well as its programing interface. 

2 Visual Components Manuals 3


4 2 Visual Components Manuals


This manual should be considered a reference tool for the following topics in Visual Components. 

3.1 Editor (Operation) Reference 

The Visual Components editor is outfitted with toolbars and shortcut keys for convenient use and to guarantee 

efficient work. Many Visual Components editor functions can therefore be reached comfortably and quickly. 

3.1.1 Shortcut Keys − Reference 

3.1.1.1 Picture Editor 

Shortcut Key Function 

Alt + Enter Picture properties 

Ins Insert new page 

Ctrl + Draw ellipse Draws a circle 

Ctrl + Draw rectangle Draws a square 

Ctrl + Draw line Draws horizontal or vertical line 

Ctrl When the Ctrl key is pressed, several objects can be selected 

Ctrl + C Copies selected object 

Ctrl + X Cuts selected object 

Ctrl + V Pastes selected object 

Ctrl + D Switches input field sequence on/off 

Del Clear 

Cursor keys Exact pixel positioning of selected object(s) 

Shift + Tab Switches the selected graphic element 

3.1.1.2 Fonts 


Alt +Enter Font properties 

Ins Inserts new font 

Ctrl + C Copies selected font 

Ctrl + H Cuts selected font 

Ctrl + V Inserts selected font 

Del Delete 

3.1.1.3 Bitmaps 


Del Delete 

Ins Insert bitmap 

3.1.1.4 Text groups 


Del Delete 

Ins Inserts text group 

3.1.2 Toolbars − Reference 

This section describes the icons in the toolbar. Depending on which editor is being used, icons in the toolbar will 

be either activated or deactivated. 

3 Visual Components Reference Manual 5

Icons are described from left to right. 

3.1.2.1 Project 

• Edit project comments 

• Open Visual Components settings dialog box 

3.1.2.2 Picture Editor 

• Insert new picture 

• Delete picture 

• Rename picture 

• Move picture up 

• Move picture down 

• Activate simulation mode 

• Select text layer (default) 

• Activate selection mode 

• Configure text input field 

• Draw line 

• Draw rectangle or square 

• Draw ellipse or circle 

• Select touch elements (button, hotspot) 

• Select input field (numeric, alphanumeric, or password) 

• Select output field (numeric, alphanumeric, bar graph, advanced text, date/time, dynamic bitmap, or 

ListBox) 

• Insert alarm field 

• Insert background bitmap 

• Zoom in 

• Zoom out 

• Show/Hide grid, grid settings 

3.1.2.3 Variables 

• Insert variable 

• Delete variable 

• Modify variable 

• Update the view 

• Name of the picture for the variable view (PIC3) 

3.1.2.4 Fonts 

• Insert font 

• Delete font 

• Rename font 


6 3.1.2.1 Project


3.1.2.5 Bitmaps 

• Insert bitmap 

• Delete bitmap 

• Rename bitmap 

• Edit bitmap 

• Zoom in on bitmap 

• Zoom out from bitmap 

3.1.2.6 Text Groups 

• Insert text group or text 

• Delete text group 

• Rename text group 

• Move text up 

• Move text down 

3.1.2.7 Alarm System 

• Insert new alarm group 

• Delete alarm group 

• Rename alarm group 

• Move alarm text up 

• Move alarm text down 

3.1.2.8 Languages 

• Insert new text layer 

• Delete text layer 

• Rename text layer 

• Compile text layer (activate) 

3.2 Screen Elements (Fields) − Reference 

Visual Components uses individual screen elements to create visualization applications. These elements are 

called fields in the following sections. A complete visualization project can be created by combining and 

configuring a series of these different fields in pictures. 

Every field in Visual Components is used, placed, edited, and configured in the same way. Details of these steps 

can be found in the User's Manual. 

Fields in a Visual Components application are classified into groups according to how they are used. Each one 

of these groups is described in its own section in this documentation. 

Fields Description 

Static Picture 

Elements 

Static picture elements are used to create the framework for a picture. As a rule, static 

elements do not represent any information, nor do they allow any input. Instead, they are 

usually used to label, group, and arrange active picture elements. 

Static picture elements are only drawn once when the picture is changed. After that, they are 

no longer updated. Because of this, they only load the system down the first time the picture 

3.1.2.5 Bitmaps 7

Input Fields 

Output Fields 

Touch−Operated 

Fields 

is changed. This isn't true, however, for elements which use status variables or variables for 

active color assignment. Details about controlling colors can be found in the Setting Color 

section of the User's Manual. 

Static picture elements can be placed on different layers with the editor. The layer displayed 

can be changed using ''Bring Forward'' and ''Send Backward'' in the object's shortcut menu 

(see Overlapping Objects). This overlap is then converted into a character sequence for the 

target system. 

Input fields allow information to be entered into process variables in various forms. The type 

of input field determines the different ways that this information is used. Most input fields 

accept the entry of numeric and alphanumeric characters. 

When numeric and alphanumeric characters are entered on systems with touch screen 

displays, Visual Components automatically adjusts the input fields on the touch screen to an 

appropriate display size. This happens automatically and does not have to be configured or 

programmed. 

When numeric and alphanumeric characters are entered using operator panel keys, the 

desired characters must first be configured on the panel keys depending on the needs of the 

application. There are several key levels provided as an option for doing so (max. 4). 

Visual Components provides input fields for all usual data types of process variables which 

can be entered into a visualization application. 

Output fields are used to represent information on the visualization device. Data shown 

comes from process variables from the control application. As a rule, output fields cannot be 

controlled or influenced by the user. 

Since no user interaction takes place, output fields function in the same way on touch screen 

systems as they do on other systems. 

Visual Components provides output fields for all usual data types of process variables used 

in a control application. Some data types can be displayed in different ways. Because of this, 

the user is able to choose the best suited representation for each application. 

Touch−operated fields either partially or completely replace operator panel key functions on 

systems with graphic touch screens. These include all touch screens with QVGA, VGA, or 

larger displays which are connected to the IPC2001 and IPC5000 families. 

Touch−operated fields are operated exclusively through the touch of correspondingly 

configured surfaces on the touch screen. Simultaneous operation using panel keys can be 

achieved by having a function key configured at the same time for the same action. 

3.2.1 Static Picture Elements − Reference 


Static picture elements are used to create the framework for a picture. As a rule, static elements do not 

represent any information, nor do they allow any input. Instead, they are usually used to label, group, and 

arrange active picture elements. 

Static picture elements are only drawn once when the picture is changed. After that, they are no longer updated. 

Because of this, they only load the system down the first time the picture is changed. This isn't true, however, for 

elements which use status variables or variables for active color assignment. Details about controlling colors can 

be found in the Setting Color section of the User's Manual. 

Static picture elements can be placed on different layers with the editor. The layer displayed can be changed 

using ''Bring Forward'' and ''Send Backward'' in the object's shortcut menu (see Overlapping Objects). This 

overlap is then converted into a character sequence for the target system. 

The number of static picture elements available depends on the type of panel used. The documentation for each 

individual picture element contains details about it's availability on various target systems. 

In general, static picture elements are reached using the toolbar in the Visual Components editor. They can also 

be found under the 'Tools' menu when the editor is active. 

8 3.2.1 Static Picture Elements − Reference


Static Picture 

Element 

Text 

Line 

Rectangle and 

Square 

Ellipse and 

Circle 

Background 

Bitmap 

Description 

This text element outputs a predefined text (from the editor) with a selectable font and size. 

Using language−switching (integrated in Visual Components), text can be configured for several 

langauges and switched at any time during runtime. 

Aside from language−switching, texts themselves can no longer be changed during runtime. If 

this is necessary, a suitable output field must be used instead. 

Using this picture element, lines can be created to optically organize the picture and to delineate 

and arrange the other fields in the picture. Lines can be created using any color supported by 

the display. 

Horizontal and vertical lines can be represented on all graphics−capable displays; diagonal lines 

can be represented on all graphics−capable displays except for CAN and serial controllers or 

operator panels. 

This picture element is used to draw rectangles in a picture. Rectangles can be output as either 

shaded ("filled") or unshaded. Any color can be selected for the border or "filling" and, if 

necessary, changed during runtime using a process variable. Rectangles may be used to group 

different fields together in the picture or for schematic representation. 

Rectangles can be output on all graphic displays (even semi−graphic displays on CAN and 

serial controllers). 

This picture element allows ellipses of any height and width to be displayed (they must be able 

to fit completely in the picture). Border and shading colors can be configured separately. 

Transparent (empty) shading for ellipses is also possible. Because of the possibility of 

connecting a variable to control ellipse color, they are very well suited as status indicators, for 

example. 

Ellipses can be output on all full−graphic displays, but not semi−graphic displays on CAN and 

serial controllers. 

This picture element allows a bitmap to be displayed as a background or picture arrangement 

element. The bitmap to be displayed must have already been inserted in the Visual Components 

Bitmap Manager. 

The bitmap cannot be changed during runtime. If this is necessary, then an output field bitmap 

can be used instead. 

3.2.1.1 Static Text Picture Element − Reference 

This text element outputs a predefined text (from the editor) with a selectable font and size. Using 

language−switching (integrated in Visual Components), text can be configured for several langauges and 

switched at any time during runtime. 

Aside from language−switching, texts themselves can no longer be changed during runtime. If this is necessary, 

a suitable output field must be used instead. 

General 

Summary of the basic properties of this static picture element. 

Function Displays texts. 

Availability This field can be used by all systems supported by Visual Components. 

Appearance 

Configured text is displayed with the defined font and size. 

Special functions: 

• Visible/Invisible switching using the Status process variable 

• Selectable foreground and background colors 

• Fully selectable fonts 

Individual Colors The following can be individually set for static text: 

3.2.1.1 Static Text Picture Element − Reference 9

• Foreground color (text color) 

• Background color 

All colors can either be set in the editor or during runtime using a process 

variable. 

Properties 

Static text properties are set under the various tabs of the Properties dialog box. The properties of the field can 

be displayed by double−clicking on the static text in the editor and are automatically shown after a new field is 

inserted. 

Available settings are described respectively on their own pages. The following list provides an outline of the 

possible settings (tabs), as well as references to detailed information. 

Text 

Parameter 

Colors 

Under this tab, text size, font, and content are defined for individual languages. The Text Input 

dialog box can also be opened for text entry. 

Basic parameters of static text such as its position and status are found under this tab. This page 

must be configured for all created static texts. 

Settings under this tab can be used to specify user−defined color settings and to connect process 

variables for controlling colors. This is very useful for color displays, but can also be used for 

black/white displays. 

3.2.1.1.1 Static Text Picture Element − Properties: Parameter 

Provides general settings for the static text picture element. 

3.2.1.1.1.1 Image 

Position 

Contains various settings for formatting the field on the screen. 

Left Specifies the position of the upper−left corner along the X axis (interval from the left display margin). 

Values for these parameters begin with 0 on the left margin and increase to the width of the display minus 

one pixel (on the right margin). 

Possible Settings for Full 

Graphic Displays 

Possible Settings for Text 

and Semi−Graphic Displays 


The field can be placed freely in the display, so that Left can be set from 0 

to the width of the display minus the width of the field in pixels. 

On text and semi−graphic displays, such as those which can be connected 

to the C130 CAN Controller, fields can only be placed evenly on every 

10 3.2.1.1 Static Text Picture Element − Reference


Top 

sixth X−coordinate ( Left = 0, 6, 12, 18, etc.). 

Specifies the position of the upper−left corner along the Y axis (interval from the upper display margin). 

Values for these parameters begin with 0 on the upper margin and increase to the height of the display 

minus one pixel (on the lower margin). 





The field can be placed freely in the display, so that Top can be set from 0 

to the height of the display minus the height of the field in pixels. 

On text and semi−graphic displays, such as those which can be connected 

to the CAN Controller C130, fields can only be placed evenly on every 

eighth Y−coordinate (Top = 0, 8, 16, 24, etc.). 

Status 


Source 

Assign... 

For the general operation of dialog boxes. 

OK 

Cancel 

Used to input or display the connected variable. 

Possible Settings Name of a UINT process variable 

Possible Values Bit 0 If 1, the field is invisible. 

All other bits are reserved. 

The Assign... button opens a dialog box to select a variable for the Source field. By 

default, only variables of suitable types are displayed. 

Buttons 

Applies settings and closes the dialog box. If settings cannot be applied because of an error, it is 

indicated and the dialog box is not closed. 

Note: 

All changes are applied, including those made under different (hidden) tabs. 

Closes the dialog box and discards any changes made. 

Warning: 

All changes will be discarded, including those made under different (hidden) tabs. 

Help Displays help for this tab. 

3.2.1.1.2 Static Text Picture Element − Properties: Text 

Under this tab, text size, font, and content are defined for individual languages. The Text Input dialog box can 

also be opened for text entry. 

3.2.1.1.2.1 Image 


Defines the text font on the screen. 

Logical Font 

Font 

Used to input or display desired fonts. 

Possible Settings Any font in the project can be selected. 

Text Table 

Contains the text to be displayed in the present languages. 

Language 

Column 

Text Column 

All languages defined in the project are listed in the Language column. Double−clicking on the 

desired language opens the Text Input dialog box for the text to be displayed for this language. 

Corresponding texts for the present languages are entered in this column. By default, the text 

entered in the first line ('default' language) will be applied automatically to all other text layers. By 

double−clicking on a text, it can be edited in the table. 


OK 

Cancel 

Buttons 



Note: 



Warning: 



3.2.1.1.3 Static Text Picture Element − Properties: Colors 

Allows colors to be set for static text. 

3.2.1.1.3.1 Image 


12 3.2.1.1 Static Text Picture Element − Reference


Allows colors to be set in the editor. 

Use Global 

Foreground 

Background 

Use 

Transparent 

Color 

Colors 

If this option is selected, then settings in the project options are applied to this element. 

Therefore, settings for foreground and background cannot be made. 

Selects the text color. This setting can only be activated if the Use Global option is not selected. 

Possible Settings for 

Full Graphic Displays 

Any desired color from a palette of 256 colors can be chosen. 

Standard palette colors are illustrated in the reference manual. 

Customer−specific operator panels can have their own color 

palettes. Correct colors are always indicated in the selection list. 

Possible Settings for Text and semi−graphic displays, such as those which can be 

Text and Semi−Graphic connected to the C130 CAN controller, support only black and white 

Displays 

colors. This is also true for the PP21 and PP41 Power Panels and 

their customer−specific varieties. 

Allows the choice of the static text background color. This setting is only activated if the Use 

Global and Use Transparent Color are not selected. 







Possible Settings for Text and semi−graphic displays, such as those which can be 

Text and Semi−Graphic connected to the C130 CAN controller, support only black and white 

Displays 

colors. This is also true for the PP21 and PP41 Power Panels and 

their customer−specific varieties. 

If Use Transparent Color is selected, only the foreground color can be changed. This applies 

both for fixed colors set using the dialog box and colors set using a process variable. 

Colors variable 

Allows color to be manipulated with a process variable during runtime. 

Source Used to input or display the connected variable. 


Possible Values Bits 0−7 The low byte contains the static text background 


Assign... 

color. 

Bits 8−15 The high byte contains the static text color. 

For both of these settings, the same colors which can be used for foreground and 

background in the editor are possible (see above). 

The Assign... button opens a dialog box to select a variable for the Source field. By default, only 

variables of suitable types are displayed. 


OK 

Buttons 



Note: 


Cancel Closes the dialog box and discards any changes made. 

3.2.1.2 Static Picture Element Line − Reference 

Using this picture element, lines can be created to optically organize the picture and to delineate and arrange 

the other fields in the picture. Lines can be created using any color supported by the display. 

Horizontal and vertical lines can be represented on all graphic displays. Diagonal lines can be represented on all 

graphic displays except for CAN and serial controllers or operator panels. 

General 


Function Displays lines. 

Availability 

Appearance 

Individual 

Colors 

Horizontal and vertical lines can be represented on all graphic displays (even semi−graphic on 

CAN and serial controllers) Diagonal lines can be be represented on all graphic displays except 

for CAN and serial controllers or panels. 

Lines will be displayed in the project exactly as they are configured in the editor. 



• Selectable line color 

The following can be individually set for lines: 

• Line color 

All colors can either be set in the editor or during runtime using a process variable. 

Properties 

Line properties are set under the various tabs of the Properties dialog box. Properties can be reached by 

double−clicking on the line in the editor. 



Parameter 

Colors 


Basic parameters of the line such as position and status are defined under this tab. This page must 

be configured for all created lines. 




14 3.2.1.2 Static Picture Element Line − Reference


3.2.1.2.1 Static Picture Element Line − Properties: Parameter 

Provides general settings for the static picture element line. 

3.2.1.2.1.1 Image 

Position 

Contains various settings for line formatting on the screen. 

Left 

Top 

Right 

Specifies the position of the upper−left corner along the X axis (interval from the left 

display margin). Values for these parameters begin with 0 on the left margin and 

increase to the width of the display minus one pixel (on the right margin). 





The line can be placed freely in the display, so that Left 

can be set from 0 to the width of the display minus the 

width of the field in pixels. 

Whether lines can be used and in which manner can be 

found in the hardware description of each display. 

Specifies the position of the upper−left corner along the Y axis (interval from the upper 

display margin). Values for these parameters begin with 0 on the upper margin and 

increase to the height of the display minus one pixel (on the lower margin). 





The line can be placed freely in the display, so that Top 

can be set from 0 to the height of the display minus the 

height of the field in pixels. 



Specifies the position of the lower−right corner along the X axis (distance from the left 

display margin). Values for these parameters begin with 0 on the left margin and 

increase to the width of the display minus one pixel (on the right margin). The value here 

must be larger than that in the Left field. 





The line can be placed freely in the display, so that 

Right can be set from 0 to width of the display minus the 




Bottom Specifies the position of the lower−right corner along the Y axis (distance from the upper 

display margin). Values for these parameters begin with 0 on the upper margin and 

increase to the height of the display minus one pixel (on the lower margin). The value 

here must be larger than that in the Top field. 

Possible Settings for Full The line can be placed freely in the display, so that 

3.2.1.2 Static Picture Element Line − Reference 15

Graphic Displays Bottom can be set from 0 to the height of display minus 

the height of the field in pixels. 





Status 

Contains various settings for line formatting on the screen. 

Source 

Assign... 


OK 

Cancel 



Possible Values Bit 0 If 1, the line is invisible. 




Buttons 



Note: 



Warning: 



3.2.1.2.2 Static Picture Element Line − Properties: Colors 

Allows colors to be set for the line. 

3.2.1.2.2.1 Image 


Use 

Global 

Line 

Color 

Colors 


If this option is selected, then settings in the project options are applied to this element. In addition, no 

setting for Line Color can be made. 

Selects the line color. This setting can only be activated if the Use Global option is not selected. 

16 3.2.1.2 Static Picture Element Line − Reference




Possible Settings for Text and 

Semi−Graphic Displays 





Text and semi−graphic displays, such as those which can be 

connected to the C130 CAN controller, support only black and 

white colors. This is also true for the PP21 and PP41 Power 

Panels and their customer−specific varieties. 



Source 

Assign... 


OK 



Possible Values Bits 0−7 In this case, the low byte has no effect on the display. 

Bits 8−15 The high byte contains the line color. 

The same colors are possible for this setting as for the setting Line 

Color in the editor (see above). 



Buttons 



Note: 



3.2.1.3 Static Picture Element Rectangle − Reference 

This picture element is used to draw rectangles in a picture. Rectangles can be output as either shaded ("filled") 

or unshaded. Any color can be selected for the border or "filling" and, if necessary, changed during runtime 

using a process variable. Rectangles may be used to group different fields together in the picture or for 

schematic representation. 

Rectangles can be output on all graphic displays (even semi−graphic displays on CAN and serial controllers). 

General 


Function Displays rectangles. 

Availability 

Appearance 

Individual 

Colors 

Rectangles can be output on all graphic displays (even semi−graphic displays on CAN and 

serial controllers). 

Rectangles will be displayed in the project exactly as they are configured in the editor. 



• Selectable border and filling colors 

The following can be individually set for rectangles: 

• Foreground color (border color) 

• Background color (filling color) 


3.2.1.3 Static Picture Element Rectangle − Reference 17

Properties 

Rectangle properties are set under the various tabs of the Properties dialog box. Properties can be reached by 

double−clicking on the rectangle in the editor. 



Parameter 

Colors 

Basic parameters of the rectangle such as its position and status are found under this tab. This page 

must be configured for all created rectangles. 




3.2.1.3.1 Static Picture Element Rectangle − Properties: Parameter 

Provides general settings for the rectangle static picture element. 

3.2.1.3.1.1 Image 

Position 

Contains various settings for formatting the rectangle on the screen. 

Left 

Top 

Specifies the position of the upper−left corner along the X axis (interval from the left display margin). 

Values for these parameters begin with 0 on the left margin and increase to the width of the display 

minus one pixel (on the right margin). 





The rectangle can be placed freely in the display, so that Left can 

be set from 0 to the width of the display minus the width of the field 

in pixels. 

Whether rectangles can be used and in which manner can be found 

in the hardware description of each display. 









The rectangle can be placed freely in the display, so that Top can be 

set from 0 to the height of the display minus the height of the field in 

pixels. 



Right Specifies the position of the lower−right corner along the X axis (distance from the left display margin). 


minus one pixel (on the right margin). The value here must be larger than that in the Left field. 

18 3.2.1.3 Static Picture Element Rectangle − Reference


Bottom 





The rectangle can be placed freely in the display, so that Right can 

be set from 0 to the width of the display minus the width of the field 

in pixels. 



Specifies the position of the lower−right corner along the Y axis (distance from the upper display 

margin). Values for these parameters begin with 0 on the upper margin and increase to the height of 

the display minus one pixel (on the lower margin). The value here must be larger than that in the Top 

field. 





The rectangle can be placed freely in the display, so that Bottom can 

be set from 0 to the height of the display minus the height of the field 

in pixels. 



Status 

Contains various settings for formatting the rectangle on the screen. 

Source 

Assign... 


OK 

Cancel 



Possible Values Bit 0 If 1, the rectangle is invisible. 




Buttons 



Note: 



Warning: 



3.2.1.3.2 Static Picture Element Rectangle − Properties: Colors 

Allows colors to be set for the rectangle. 

3.2.1.3.2.1 Image 

3.2.1.3 Static Picture Element Rectangle − Reference 19


Use Global 

Foreground 

Background 

Fill 

Colors 

If this option is selected, then settings in the project options are applied to this element. Therefore, 

settings for foreground and background cannot be made. 

Selects the color for the rectangle border. This setting can only be activated if the Use Global 

option is not selected. 




Text and Semi−Graphic 

Displays 

Any desired color from a palette of 256 colors can be chosen. Standard 

palette colors are illustrated in the reference manual. 

Customer−specific operator panels can have their own color palettes. 

Correct colors are always indicated in the selection list. 

Text and semi−graphic displays, such as those which can be connected 

to the C130 CAN controller, support only black and white colors. This is 

also true for the PP21 and PP41 Power Panels and their 

customer−specific varieties. 

Selects the color for rectangle shading. This setting is only active if the option Use Global is not 

selected and the box Fill is checked. 





Displays 









If Fill is selected, the rectangle will be filled in with the background color. If not, the inside of the 

rectangle will be transparent. 



Source 




Possible Values Bits 0−7 The low byte contains the rectangle background (filling) 

color. 

Bits 8−15 The high byte contains the rectangle foreground (border) 

color. 



20 3.2.1.3 Static Picture Element Rectangle − Reference



Assign... 



OK 

Buttons 



Note: 



3.2.1.4 Static Picture Element Ellipse − Reference 

This picture element allows ellipses of any height and width to be displayed (they must be able to fit completely 

in the picture). Border and shading colors can be configured separately. Transparent (empty) shading for 

ellipses is also possible. Because of the possibility of connecting a variable to control ellipse color, they are very 

well suited as status indicators, for example. 

Ellipses can be output on all full−graphic displays, but not semi−graphic displays on CAN and serial controllers. 

General 


Function Displays ellipses. 

Availability 

Appearance 

Individual Colors 

Ellipses can be output on all full−graphic displays, but not semi−graphic displays on 

CAN and serial controllers. 

Ellipses will be displayed in the project exactly as they are configured in the editor. 



• Selectable border and filling colors 

The following can be individually set for ellipses: 

• Foreground color (border color) 

• Background color (filling color) 


Properties 

Ellipse properties are set under the various tabs of the Properties dialog box. They can be reached by 

double−clicking on the ellipse in the editor. 



Parameter 

Colors 

Basic parameters of the ellipse such as its position and status are defined under this tab. This page 

must be configured for all created ellipses. 




3.2.1.4.1 Static Picture Element Ellipse − Properties: Parameter 

Provides general settings for the static picture element ellipse. 

3.2.1.4.1.1 Image 

3.2.1.4 Static Picture Element Ellipse − Reference 21

Position 

Contains various settings for ellipse formatting on the screen. 

Left 

Top 

Right 

Bottom 








The ellipse can be placed freely in the display, so that Left can be 

set from 0 to the width of the display minus the width of the field in 

pixels. 

Whether ellipses can be used and in which manner can be found in 

the hardware description of each display. 








The ellipse can be placed freely in the display, so that Top can be 

set from 0 to the height of the display minus the height of the field in 

pixels. 



Specifies the position of the lower−right corner along the X axis (distance from the left display margin). 


minus one pixel (on the right margin). The value here must be larger than that in the Left field. 





The ellipse can be placed freely in the display, so that Right can be 

set from 0 to width of the display minus the width of the field in 

pixels. 



Specifies the position of the lower−right corner along the Y axis (distance from the upper display 

margin). Values for these parameters begin with 0 on the upper margin and increase to the height of 

the display minus one pixel (on the lower margin). The value here must be larger than that in the Top 

field. 





The ellipse can be placed freely in the display, so that Bottom can 

be set from 0 to the height of display minus the height of the field in 

pixels. 

The respective display's hardware description will disclose whether 

ellipses can be used and in which manner. 

Status 


22 3.2.1.4 Static Picture Element Ellipse − Reference


Contains various settings for formatting the ellipse on the screen. 

Source 

Assign... 


OK 

Cancel 



Possible Values Bit 0 If 1, the ellipse is invisible. 




Buttons 



Note: 



Warning: 



3.2.1.4.2 Static Picture Element Ellipse − Properties: Colors 

Allows colors to be set for the ellipse. 

3.2.1.4.2.1 Image 


Use Global 

Colors 

If this option is selected, then settings in the project options are applied to this element. Therefore, 

settings for foreground and background cannot be made. 

Foreground Selects the color for the ellipse border. This setting can only be activated if the Use Global option 

is not selected. 







Possible Settings for Text and semi−graphic displays, such as those which can be connected 

3.2.1.4 Static Picture Element Ellipse − Reference 23

Background 

Fill 


Displays 




Selects the color for ellipse shading. This setting is only active if the option Use Global is not 

selected and the box Fill is checked. 





Displays 









If Fill is selected, the ellipse will be filled in with the background color. If not, the inside of the 

ellipse will be transparent. 



Source 

Assign... 



Possible Values Bits 0−7 The low byte contains the ellipse background (filling) 

color. 

Bits 8−15 The high byte contains the ellipse foreground (border) 

color. 






OK 

Buttons 



Note: 



3.2.1.5 Static Picture Element Background Bitmap − Reference 

This picture element allows a bitmap to be displayed as a background or picture arrangement element. The 

bitmap to be displayed must have already been inserted in the Visual Components Bitmap Manager. 

The bitmap cannot be changed during runtime. If this is necessary, then an output field bitmap can be used 

instead. 

General 


Function Displays bitmaps. 

Availability 

Full graphics panels with bitmap support 

• IPC2001 and IPC5000 families with 1/4 VGA, VGA, or larger 

display 

• Power Panel PP41 (only monochrome bitmaps) 


24 3.2.1.5 Static Picture Element Background Bitmap − Reference


The bitmap is shown on the display as it is in the editor. 

Appearance Special functions: 


Properties 

Background bitmap properties are set under the tabs of the Properties dialog box. Field properties can also be 

displayed by double−clicking on the bitmap in the editor and are automatically shown after a new bitmap is 

inserted. 

All available settings are found under one tab. 

3.2.1.5.1 Static Picture Element Background Bitmap − Properties 

Provides general settings for the background bitmap static picture element. 

3.2.1.5.1.1 Image 

Bitmap 

Specifies the bitmap to be displayed. 

Used to inputs or display the bitmap to be shown. 

Bitmap 

Possible Settings Any bitmaps inserted in the project tree. 

Position 

Contains various settings for positioning the bitmap on the screen. 

X 

Specifies the position of the upper−left corner along the X axis (interval from the left display margin). Values 

for these parameters begin with 0 on the left margin and increase to the width of the display minus one pixel 

(on the right margin). 



The bitmap can be placed freely in the display, so that X can be set from 0 to the 

width of the display minus the width of the field in pixels. However, the bitmap must 

be able to fit completely in the display. 

Y Specifies the position of the upper−left corner along the Y axis (interval from the upper display margin). 

Values for these parameters begin with 0 on the upper margin and increase to the height of the display minus 

one pixel (on the lower margin). 

3.2.1.5 Static Picture Element Background Bitmap − Reference 25



The bitmap can be placed freely in the display, so that Y can be set from 0 to 

the height of the display minus the height of the field in pixels. However, the 

bitmap must be able to fit completely in the display. 

Status 

Contains various settings for formatting the bitmap on the screen. 

Source 

Assign... 

Preview 

Displays the selected bitmap. 


OK 

Cancel 



Possible Values Bit 0 If 1, the bitmap is invisible. 




Buttons 



Note: 



Warning: 



3.2.2 Input Fields − Reference 

Input fields allow information to be entered into process variables in various forms. The type of input field 

determines the different ways that this information is used. Most input fields accept the entry of numeric and 

alphanumeric characters. 

When numeric and alphanumeric characters are entered on systems with touch screen displays, Visual 

Components automatically adjusts the input fields on the touch screen to an appropriate display size. This 

happens automatically and does not have to be configured or programmed. 

When numeric and alphanumeric characters are entered using operator panel keys, the desired characters must 

first be configured on the panel keys depending on the needs of the application. There are several key levels 

provided as an option for doing so (max. 4). 

Visual Components provides input fields for all usual data types of process variables which can be entered into 

a visualization application. 

Input Field Description 

Numeric 

Input Field 

String Input 

Field 

Password 

Input Field 


This type of input field allows numeric data to be entered. When the input field is inactive, the 

current state of the connected variable is displayed. Therefore, this type of input field is an output 

field at the same time. 

This type of input field allows text to be input into the visualization application. When the input 

field is inactive, the current state of the connected variable is displayed. Therefore, this type of 

input field is an output field at the same time. 

With this type of input field, a user level (password level) can be selected by entering a 

corresponding password. Entered text is only evaluated internally − the application itself contains 

26 3.2.2 Input Fields − Reference


ListBox 

Input Field 

the numeric information about which user level is currently set. 

Up to three password−protected user levels are supported and are determined by the last corretly 

entered password. Levels are defined numerically: 1 for the lowest authorization up to 3 for the 

highest. 

Fewer password levels can optionally be used, but additional levels are not supported with this 

type of field. Entering an incorrect password changes the password level to 0. 

Passwords are defined in the editor during the design phase and cannot be changed during 

runtime. If changing a password during runtime or more password levels are necessary, then an 

string input field can be used instead. Password evaluation must then be programmed into the 

control application. 

This type of input field can be used to select a text from a list of texts without having to change the 

control variable by scrolling. A desired entry can be selected with a separate selecting key. 

3.2.2.1 Numeric Input Field − Reference 

This type of input field allows numeric data to be entered. When the input field is inactive, the current state of the 

connected variable is displayed. Therefore, this type of input field is an output field at the same time. 

General 

Summary of the basic properties of these types of input fields. 

Function Display and input of numeric process variables in text form 

Data Types 

The following data types can be used for this field: 

USINT, SINT, UINT, INT, UDINT, DINT, and REAL 


Special 

Features 

Appearance 

Individual 

Colors 

Special Functions: 

• Value scaling for display and input 

• Input limiting to a selected value range 

• Input locking using numeric password levels (configurable) or the connected Status 

process variable for simple user management. 

• Notification during or after entry takes place using the Status and Completion Data Point 

process variables. This allows reactions to the input and synchronized data acquisition 

from external stations. 

The value is output as a sequence of digits on the display and is controlled using operator panel 

keys or the virtual keypad for touch screens. 




• Display of the decimal point in adjustable positions 

• Display of incorrect/missing variables (field filled in with hyphens '−') 

• Overflow display (field filled in with asterisks '*') 

• Optional display of preceding zeroes 


The following can be individually set for each input field of this type: 




Input Optional, using one or more of the following methods: 

• Numerically using panel keys 

• Numerically using the automatically displayed virtual keypad on panels with touch 

screens 

3.2.2.1 Numeric Input Field − Reference 27

• Using fully configurable Up/Down function keys (increases/decreases the value by 

degrees) 

Properties 

Input field properties are set under the various tabs of the Properties dialog box. Field properties can be 

displayed by double−clicking on the input field in the editor and are automatically shown after a new field is 

inserted. 



Parameter 

Colors 

Scaling 

Up/Down 

Completion 

Locking 

Simulation 

Basic parameters of input fields such as position, size, connected variable, and status are defined 

under this tab. Settings under this tab have to be adjusted for all input fields created. 




Scaling allows the value range on the PLC to be converted to another range of values on the 

visualization device. This means the user can select a suitable value range for calculation, editing, 

and display. 

No adjustments under this tab are necessary if the value of the variable should be displayed 1:1. 

The permitted input range can also be limited under this tab. 

Under this tab, the input field can be configured to use +/− keys. In this way, values can be 

increased or decreased more easily. This option is also useful for operator panel with very few 

keys. 

For normal numeric input, settings under this tab are not important. 

Notification setting using input in the field. This can be used to check the input value in the 

application or trigger other actions. 

These settings are optional. 

Using these settings, editing input fields can be restricted to certain user or password levels. 

If the field is not restricted, then these settings do not have to be adjusted. 

Allows the input of a display value for the editor's Simulation mode. In this mode, pictures for 

documentation can be created with the value set here displayed in the field. 

Inputting this information is optional. 

3.2.2.1.1 Numeric Input Field − Properties: Parameter 

Provides general settings for numeric input fields. 

3.2.2.1.1.1 Image 


28 3.2.2.1 Numeric Input Field − Reference


Format 


Number of Digits 

Digits after Decimal 

Point 

Font 

Display Leading 

Zeroes 

Specifies the amount of digits which should be displayed. If a decimal point is output, then 

the resulting field is one character wider than is specified here. 

Possible Settings 1 to 10 digits for DINT, UDINT, and FLOAT process variables 

1 to 5 digits for other data types. 

The field must be able to fit in the picture with its set size and font. 

Specifies how many digits (of those designated in Number of Digits) should be shown 

after the decimal point. 

Possible Settings There must be at least one position before the decimal point left 

open. Therefore, the setting can be a maximum of Number of Digits − 

1. 

Selects the font which should be used for the input field. 


If this option is selected, then open spaces before the first significant digit are filled with 

zeroes. Otherwise, blank spaces fill up the rest of the vacant area. 

Position 


X 

Specifies the position of the upper left corner along the X axis (interval from the left display 

margin). Values for these parameters begin with 0 on the left margin and increase to the 

width of the display minus one pixel (on the right margin). 




and Semi−Graphic 

Displays 

This field can be placed freely on the screen. Therefore, X can 

be set from 0 to the width of the display minus the width of the 

field in pixels. 

On text and semi−graphic displays, such as those which can be 

connected to the C130 CAN controller, fields can only be 

placed evenly on every sixth X−coordinate (X = 0, 6, 12, 18, 

etc.). 


Y 

Specifies the position of the upper left corner along the Y axis (interval from the upper display 

margin). Values for these parameters begin with 0 on the upper margin and increase to the 

height of the display minus one pixel (on the lower margin). 





Displays 

The field can be placed freely in the display. Therefore, Y can 

be set from 0 to the height of the display minus the height of the 



connected to the C130 CAN controller, fields can only be placed 

evenly on every eighth Y−coordinate (Y = 0, 8, 16, 24, etc.). 

Data Point 

Allows a variable to be connected which is displayed and operated with this input field. 

Source 

Assign... 


Possible Settings Name of a process variable with one of the following data types: 

USINT, SINT, UINT, INT, UDINT, DINT, or REAL. 



Status 


Source 

Assign... 

Preview 

Displays the field with the current settings. 


OK 

Cancel 



Possible Values Bit 0 If 1, the input field is invisible. 

Bit 1 If 1, then input is locked. 

Bit 14 Is set to 1 while the input field has the focus (is 

highlighted). The focus determines which input field is to 

accept input from the operator panel. 

If the input field loses the focus, then this bit is reset back 

to 0. 

Bit 15 Is set to 1 while the input field is activated (the value in the 

input field is being edited). It will be set back to 0 after the 

input has been completed or cancelled. 




Buttons 



Note: 



Warning: 






3.2.2.1.2 Numeric Input Field − Properties: Colors 

Allows colors to be set for the field's display. 

3.2.2.1.2.1 Image 


Use Global 

Foreground 

Background 

Colors 

If this option is selected, then settings in the project options are applied to this input field. 


Selects the text color used for this input field. This setting can only be activated if the Use Global 






Displays 









Selects the input field's background color. This setting can only be activated if the Use Global 






Displays 












Source 

Assign... 



Possible Values Bits 0−7 The low byte contains the input field background 

color. 

Bits 8−15 The high byte contains the input field text color. 






OK 

Cancel 

Buttons 



Note: 



Warning: 



3.2.2.1.3 Numeric Input Field − Properties: Scaling/Limits 

Enables flexible scaling of displayed or entered values. 

3.2.2.1.3.1 Image 

Enables scaling for this input field 

Scaling 

Active 

Scaling/Limits 


If this option is selected, the value in the input field is scaled, and input is then limited to the 

specified value range. 



Otherwise, the actual numeric value of the process variable is displayed, and input is limited only 

by the connected variable data type. 

The other fields under this tab are only enabled when this option is selected. 

PLC Value Range 

Specifies the allowed value range on the controller for the connected process variable. The range set here is 

scaled to the range set under Scaled Value Range for the display and input of the value in the input field. 

Parameters 

from PLC 

0% Value 

0% Source 

Assign... 

100% Value 

100% Source 

Assign... 

This field determines whether a 0% value and a 100% value are input in the editor (box 

unchecked) or if a process variable should be selected during runtime (box checked). 

The dialog box displays the necessary configuration fields which correspond to this setting. 

Specifies the lower limit of the permitted value range for the process variable on the PLC. This 

setting is only available if Parameters from PLC is not selected. 

Possible Settings Corresponds to the value range of the connected process variable. 

Defines the process variable which contains the lower limit of the value range for the variable 

processed with this input field on the PLC during runtime. This setting is only available if 

Parameters from PLC is selected. 

Possible Settings Name of a variable with the same data type as the variable connected to 

the input field. This variable can accept values like those defined under 

0% Value. 

The Assign... button opens a dialog box to select a variable for the 0% Source field. By default, 

only variables of suitable types are displayed. 

Specifies the upper limit of the permitted value range for the process variable on the PLC. This 



Defines the process variable which contains the upper limit of the value range for the variable 





100% Value. 

The Assign... button opens a dialog box to select a variable for the 100% Source field. By 


Scaled Value Range 

Specifies the permitted value range for the variable input and display in the visualization application. During 

input and display, this range is scaled to the process variable range set under PLC Value Range. 

Parameters 

from PLC 




0% Value Specifies the lower limit of the permitted value range for the process variable on the control 

panel. 

Possible Settings Possible settings are limited by the input field width in 

characters so that limits can be entered and represented in the 

input field. 

In addition, input is limited by the connected variable data type 

as follows. 

USINT SINT Value range from −99999 to 99999 (limited by 


0% Source 

Assign... 

100% Value 

INT UINT the maximum input field width of 5 characters). 

DINT Value range from −2147483648 to 2147483647 

UDINT Value range from 0 to 4294967295 

REAL Value range from −9999999999 to 9999999999 

These specifications apply when no decimal places are set. If 

decimal places are used, the specification refers to the units in 

the selected definition. 

Example: 

A SINT variable can be scaled from −999.99 to +999.99 when 2 

set decimal places are used. 

In this way, invalid input is automatically corrected to valid data. 


processed with this input field on the control panel during runtime. This setting is only available 

if Parameters from PLC is selected. 

Possible Settings Variables with the following data types can be connected to this property 

depending on the data type of the variable connected to the input field. 

USINT SINT Variables of data types USINT, SINT, INT, UINT, or DINT 

INT UINT DINT can be used independent of the data point of the 

connected variable. 

UDINT UDINT 

REAL REAL 

(The data type has to be able to accept the desired limits 

during runtime!) 

This variable can accept values like those defined under 0% Value. 



Specifies the upper limit of the allowed value range for the process variable on the control 

panel. 



input field. 


as follows. 

USINT SINT 

INT UINT 


Value range from −99999 to 99999 (limited by 

the maximum input field width to 5 characters). 







Example: 


decimal places are set. 




100% Source 

Assign... 

Determines the process variable which contains the upper limit of the value range for the 

variable processed with this input field on the control panel during runtime. This setting is only 

available if Parameters from PLC is selected. 

Possible Settings Depending on the data type of the variable connected to the input field, 

variables with the following data types can be connected: 




UDINT UDINT 

REAL REAL 






Shift Decimal Point 

Using this setting, the decimal point in the input field can be moved during runtime using a variable from the 


This setting is only available if Scaling Active is selected under this tab and at least 1 decimal place is specified 

in the Digits after Decimal Point field under the Parameter tab (otherwise, there is no space set aside for the 

decimal point). 

Warning! 

To guarantee that a field using dynamic decimal shifts acts the same way as a field with decimal places fixed 

when the same number of decimal places are used, decimal point shifting accesses the maximum value of the 

display scaling. The maximum value is multiplied by 10 for each addition decimal place which results. This can 

lead to problems recognizing the maximum allowed input value since it may be that the configuration input limit 

has to be shifted down by the additional decimal position to provide the automatic input standardization. 

Example: 

Configured: 0 − 10000 PLC value range; 0 − 1000 Display value range 

1 fixed decimal place. 

The field (UINT variable ) has a maximum of 7 places available (5 for the value range + 1 for the decimal + 1 for 

the sign). −−> 6 places available for numeric display. 

Input: 1000 becomes 1000.0. If one decimal place is now added, then inputting 1000 will lead to the correct 

value on the PLC (= 10000), but it wouldn't be able to displayed on the screen since it would be output as 

'1000.00', requiring 7 characters. 

Result: The Runtime evaluates it as an transgression but can't standardize the value since it cannot be 

displayed. 

Therefore, you should pay attention to the following during configuration: 

− What is the maximum amount of decimal places that I want to use? 

− If the most amount of decimal places is used with the maximum input value, can the value still be displayed? 

Source 

Determines the process variable which contains the number of additional decimal places to be 

displayed. If fewer decimal places should be displayed, then the value of the variable has to be 

negative. The resulting number of decimal places is determined by adding the value of this process 

variable with the value set in the Digits after Decimal Place field under the Parameter tab. This 

number must be able to fit in the selected field size. 

Possible Settings Name of a process variable of type USINT (default) or SINT. Data type SINT must 

be used if negative decimal point shifts are necessary (fewer decimal places). 

Assign... The Assign... button opens a dialog box to select a variable for the Source field. By default, only 



Note: 

The Type−Filter button must be unchecked in the dialog box to select a variable of type SINT. 


OK 

Cancel 

Buttons 



Note: 



Warning: 



3.2.2.1.4 Numeric Input Field − Properties: Up/Down 

Allows input using Up/Down keys in place of numeric input. If Up/Down input is enabled, then it is no longer 

possible to use the numeric keypad or the touch pad for input. Keys for Up/Down input are configured in the 

picture settings and apply for the entire page. 

3.2.2.1.4.1 Image 

Settings for changing the variable using Up/Down keys 

Up/Down 

Input 

UpDown 

Enables up/down input for this input field. The value in the input field can be increased or 

decreased via the keys displayed below if the input field is highlighted (is the active input field). 


Buttons 


OK Applies settings and closes the dialog box. If settings cannot be applied because of an error, it is 




Cancel 

Note: 



Warning: 



3.2.2.1.5 Numeric Input Field − Properties: Completion 

Allows notification about input in the input field. 

3.2.2.1.5.1 Image 

Completion Data Point 

Sets the connected variable to a fixed value each time the field is processed. 

Source 

Assign... 

Completion 

Value 


Possible Settings Name of a UINT process variable. The same variable can be 

connected to several input fields as a completion data point. 

Possible Values The variable is set to the value in Completion value after the input 

field is processed by the user of Visual Components Runtime. 

Visual Components does not further evaluate the connected 

variable. 



After the input field is processed, the value is written to the process variable specified under 

Source. 

Possible Settings Any acceptable value for variables of type UINT (0 to 65535) 


OK 

Buttons 


Cancel 



Note: 



Warning: 



3.2.2.1.6 Numeric Input Field − Properties: Locking 

Allows the input field to be locked depending on the current user or password entered. 

3.2.2.1.6.1 Image 

Enables input field locking 

Locking Active 

Locking 

If selected, this input field can be locked during runtime. A locked input field is displayed but 

cannot be highlighted or accept new input. 

Locking only affects the input field, not the connected variable. Another input field on the 

same page can allow a different value to be written to the process variable even if this field is 

locked. 

The other options under this tab can only be enabled when this option is selected. 

Password for Locking 

Defines the variable holding the current password level. Password levels are managed as numeric values. They 

can be provided either via the password input field or the application. 



Possible Settings Name of a USINT process variable. The same variable can be and usually is 

used as a password level for several input fields. 



Assign... 

Possible Values Visual Components supports up to 63 (0−63) password levels 



Input locked if... 

Determines which conditions must be met for input to be locked. 


Password Level 

Defines a logical condition under which the input is locked. Any of the following settings can be 

selected: 

Password level is 0 The field is locked when the connected Password process variable has 

the value 0. In every other case, the input is unlocked. 

Password value 

< Level 


>= Level 

The field is locked when the process variable connected to the 

Password has a smaller value than is shown in the Password Level 

field. If the value of the variable is larger or equal to the contents of the 

Password Level field, then the input field will be unlocked. 

The field is locked if the process variable connected to Password has a 

larger or equal value than the value shown in the Password Level field. 

If the contents of the variable are smaller than the value in the 


Defines the comparative value for the settings Password < Level and Password >= Level under 

Input Locked If.... 

Possible Settings 0 to 63 


OK 

Cancel 

Buttons 



Note: 



Warning: 



3.2.2.1.7 Numeric Input Field − Properties: Simulation 

Input of the displayed value in the editor's Simulation mode. 

3.2.2.1.7.1 Image 


Simulation Value 

Determines the value which should be shown in the input field during the editor's Simulation mode. Simulation 

mode can be used to create visualization pictures for product documentation. Visual Components does not use 

these settings in any other place. 

Simulation 

Value 

CharBox 

Desired display of the input field as a character string in Simulation mode. 

Possible Settings Any character string which can be displayed in the input field as a result of its 

set length. Visual Components does not check the format or the value of the 

input. 

The entire character set of the selected font can be displayed using this button. Characters can 

therefore be input that are not available with the current keyboard settings. A character can be 

inserted into the Simulation Value field by double clicking on it in the CharBox. 

It is displayed using the input field's set font. 

Possible Settings Settings 


OK 

Cancel 

Buttons 



Note: 



Warning: 



3.2.2.2 String Input Field − Reference 


This type of input field allows text to be input into the visualization application. When the input field is inactive, 

the current state of the connected variable is displayed. Therefore, this type of input field is an output field at the 

same time. 

40 3.2.2.2 String Input Field − Reference


General 


Function Displays and inputs text from and in process variables of type STRING[] 

Data Types 

Availability 

Special Features 

Appearance 


Input 


STRING[] 

This field can be used by all systems supported by Visual Components. 

Depending on the number of panel keys, it may not be possible to input all characters 

via the panel itself. However, this does not diminish the basic function of the input field. 


• Support of additional keys for cursor navigation and tabulator control for 

convenient input. 

• Editing of text longer than the field allows by scrolling field content. 

• Input locking using numeric password levels (configurable) or the connected 

Status process variable for simple user management. 

• Notification during or after entry takes place using the Status and Completion 

Data Point process variables. This allows reactions to the input and 

synchronized data acquisition from external stations. 

The value is output as a series of characters on the display and is controlled via 

operator panel keys or the virtual keypad on touch screens. 










Optional, using one or more of the following methods: 

• Character input using panel keys 

• Using the automatically displayed virtual keypad on panels with touch screens 

When panel keys are used to input, additional keys can be configured for convenient 

cursor navigation. The virtual keypad automatically displayed on touch screens provides 

these possibilities automatically (1/4 VGA system touch screens are limited by space 

and only provide a portion of the possible keys). 

Properties 



inserted. 



Parameter 

Colors 






Keys Allows additional keys to be configured for cursor navigation and tabulator control (TAB) for 

systems with operator panel keys. These settings make it easier to input but are not absolutely 

3.2.2.2 String Input Field − Reference 41

Completion 

Locking 

Simulation 

necessary. 

In addition, the input field's edit mode is set under this tab. This mode affects both the handling of 

panel keys and the keypad automatically displayed on touch systems. 


application or trigger other actions. 


Using these settings, editing input fields can be restricted to certain user or password levels. 

If the field is not restricted, then these settings do not have to be adjusted. 




3.2.2.2.1 String Input Field − Properties: Parameter 

Provides the settings for the string input field. 

3.2.2.2.1.1 Image 

Format 


Number of Characters 

Font 

Specifies the number of characters which should be displayed. The text may be longer 

than the width of the input field. During editing the text is scrolled so that the field is 

visible. 

Possible Settings The field must be able to fit in the picture with its set size and font. 

The entered and displayed text cannot be longer than the space 

provided for the connected variable (i.e. array elements of type 

STRING). 

Selects the font which should be used for this input field. 





Position 

Specifies the position of the input field in pixels on the screen. 

X 

Y 








Displays 







etc.). 








Displays 







Destination Data Point 

Allows a variable to be connected which is displayed and operated with this input field. 

Source 

Assign... 


Possible Settings Name of a process variable of data type STRING [] (array of variables of data 

type STRING, ANSI C programmers must use data type plcstring[]) 



It must be noted that the entire array is selected, not just one element from it. 

Status 


Source 

Assign... 









to 0. 








Preview 



OK 

Cancel 

Buttons 



Note: 



Warning: 



3.2.2.2.2 String Input Field − Properties: Colors 


3.2.2.2.2.1 Image 


Use Global 

Colors 



Foreground Selects the text color used for this input field. This setting can only be activated if the Use Global 






Displays 











Background 








Displays 











Source 

Assign... 




color. 







OK 

Cancel 

Buttons 



Note: 



Warning: 



3.2.2.2.3 String Input Field − Properties: Keys 

Allows additional keys to be set for conveniently editing string input. These settings only matter for the 

corresponding input field and only so long as it is highlighted (has the keyboard focus). 

In addition, the field's edit mode is set here. 

3.2.2.2.3.1 Image 


Keys 

Defines additional keys to conveniently edit strings on the visualization device. All settings are optional, and 

keys which have already been assigned a corresponding function are not available. 

Cursor Left 

key 

Cursor 

Right key 

Delete key 

Backspace 

key 

With this assigned function key, the cursor moves one character to the left without altering the 

input. If the cursor is already in the furthest leftmost position, pressing this key is ignored. 

This only applies to the input field for which this setting is active. 

Possible Settings Any unassigned function key on the operator panel can be configured for this 

action. The same function key can be used for several input fields as a cursor 

key or for other field−specific key functions. 

With this assigned function key, the cursor moves one character to the right without altering the 

input. If the cursor is already in the furthest rightmost position, pressing this key is ignored. The 

cursor can be inserted after the last input character so that new input can be added onto the end. 





The characters under the cursor are deleted using this assigned function key. The remaining 

characters to the right of the cursor are moved back accordingly. If the cursor is at the end of the 

input so that it is not under any characters, then pressing this key is ignored. 





With this assigned function key the characters left of the cursor are deleted. The cursor and the 

remaining characters are moved to the left accordingly. If the cursor is already in the leftmost 

position or the input field is empty, then pressing this key is ignored. 








Tabulator 

Allows a key to be assigned for tabulator (TAB) movement. Pressing this key moves the cursor several 

characters towards the end of the input (to the right). In doing so, the input in the field is not altered as would 

normally occur on a PC. 

Auto Tab Mode 

Tab key 

Tab Distance 

If this option is selected and the Tab key is pressed, the cursor will move to the position that 

follows the next non−alphabetic character. Generally, this will move the cursor to the next word. 

Punctuation and numbers are considered separators and are skipped over. 

If this option is selected, then the Tab Distance setting has no effect. 

The cursor can be moved several characters to the right using this assigned function key. The 

number of characters the cursor moves is set with AutoTab Mode or Tab Distance. If the cursor 

is already too far to the right to move the set tabulator distance, it moves to the end of the input. 

If the cursor is already at the end of the input, then pressing this button is ignored. 


Possible Settings Any unassigned function key on the operator panel can be configured for 

this action. The same function key can be used for several input fields as a 

cursor key or for other field−specific key functions. 

Using this setting, the distance of the cursor tabulator movement to the right can be set. This 

setting is only considered when the option Auto Tabulator is not enabled. 

Possible Settings Values from 1 to 9 can be set using the up and down buttons. Any 

value between 1 and one less than the width of the field is possible. 

Mode 

Sets the input field's edit mode. This determines whether the existing input is edited or replaced, and whether 

characters are displayed normally or hidden, as is the case with passwords. 

Edit Mode Specifies how the existing field contents should be edited or replaced. The 

following settings can be selected: 

Edit In this mode, an input field is edited normally. If the content 

should be changed, then the previous contents must first 

be deleted using the Delete and/or Backspace keys. 

Clear In this mode, the previously existing text is basically 

overwritten. Editing the old text is not possible since it is 

deleted when the first key is pressed to enter new input in 

the active field. 

Key−Dependent This mode combines the two previous modes depending 

on the first key used when editing the field. 

If the first key pressed is a cursor key, then the appropriate 

cursor movement occurs and the text is preserved. This 

behavior corresponds to Edit mode. 

In every other case, the text is completely replaced. This 

behavior corresponds then to Clear mode. 

Password This mode functions basically the same way as Clear 

mode except the characters entered (or the existing 

characters) are not displayed on the screen. Instead, a 

definable substitute character is displayed for each input 

character. 

In this way, password entry (and similar data) can be input 

without having to be displayed on the screen. 


Password Char 


OK 

Cancel 

The characters to be displayed in place of the actual 

characters can be set in Password Char. An asterisk (*) is 

used by default. 

This setting is important in Password mode and specifies the character that 

should be output in place of displaying characters which are input. The 

character checks that something was entered but does not supply any 

information about what it actually was. 

Possible Settings Any individual character which exists in the input 

field's font set can be chosen. The corresponding 

(chosen) character is input directly into the field. 

Default Setting * (asterisk) 

Buttons 



Note: 



Warning: 



3.2.2.2.4 String Input Field − Properties: Completion 


3.2.2.2.4.1 Image 






Source 

Assign... 

Completion 

Value 







variable. 




Source. 



OK 

Cancel 

Buttons 



Note: 



Warning: 



3.2.2.2.5 String Input Field − Properties: Locking 


3.2.2.2.5.1 Image 

Locking 



Locking Active 

If selected, this input field can be locked during runtime. A locked input field is displayed but 

cannot be highlighted or accept new input. 

Locking only affects the input field, not the connected variable. Another input field on the 

same page can allow a different value to be written to the process variable even if this field is 

locked. 





Source 

Assign... 












selected: 




< Level 


>= Level 













OK 

Cancel 

Buttons 



Note: 



Warning: 






3.2.2.2.6 String Input Field − Properties: Simulation 


3.2.2.2.6.1 Image 


Determines the value which should be shown in the input field during the editor's Simulation mode. Simulation 



Simulation 

Value 

CharBox 

Desired display of the input field as a character string in Simulation mode. 

Possible Settings Any character string which can be displayed in the input field as a result of its 


input. 



inserted into the Simulation Value field by double clicking on it in the CharBox. 


Possible Settings Settings 


OK 

Cancel 

Buttons 



Note: 



Warning: 




3.2.2.3 Password Input Field − Reference 

With this type of input field, a user level (password level) can be selected by entering a corresponding password. 

Entered text is only evaluated internally − the application itself contains the numeric information about which 

user level is currently set. 

Up to three password−protected user levels are supported and are determined by the last corretly entered 

password. Levels are defined numerically: 1 for the lowest authorization up to 3 for the highest. 

Fewer password levels can optionally be used, but additional levels are not supported with this type of field. 

Entering an incorrect password changes the password level to 0. 

Passwords are defined in the editor during the design phase and cannot be changed during runtime. If changing 

a password during runtime or more password levels are necessary, then an string input field can be used 

instead. 

General 


Function Selects password level by entering a password. 

Data Types 

Availability 


Appearance 


Input 


USINT process variable for outputting the current password level to the application 

Entering a password takes place by inputting characters (alphanumeric). 

This field can be used by all systems supported by Visual Components. 

Depending on the number of panel keys, it may not be possible to input all characters 

via the panel itself. However, this does not diminish the basic function of the input field. 

Passwords must be chosen in such a way that they can even be input from the operator 

panel. This is not checked by the Visual Components editor. 


• Up to 4 password levels, of which 3 are secured with passwords 

• Simple configuration of passwords in the Visual Components editor 

• Locking of input using the connected Status process variable 

• Notification during or after entry takes place using the Status and Completion 

Data Point process variables. This allows reactions to the input and 

synchronized data acquisition from external stations. 

Password are concealed when they are output so that they cannot be read. At the 

outset, the password appears blank after each picture change since only the current 

password level is stored, and not the last concluded input. 










Optional, using one or more of the following methods: 


• Character input using panel keys 

• Using the virtual keypad which is automatically displayed on panels with touch 

screens 

52 3.2.2.3 Password Input Field − Reference


Properties 



inserted. 



Parameter 

Colors 

Passwords 

Completion 






Sets the number of password levels as well as their accompanying passwords. These settings are 

usually adjusted for each created field. 


application or trigger other actions. For example, picture elements can be shown or hidden using 

their Status variables. 


3.2.2.3.1 Password Input Field − Properties: Parameter 

Provides the settings for the password input field. 

3.2.2.3.1.1 Image 

Format 


Number of characters Specifies the number of characters which should be displayed. 

Possible Settings 1 to 10 characters (passwords can be a maximum of 10 characters 

long) 


3.2.2.3 Password Input Field − Reference 53

Font 

Echo Character 

There cannot be more text than the width of the field allows. That 

means that passwords cannot be set to a length longer than the field 

itself. 

Selects the font which should be used for this input field. 


Chooses the character to be displayed in place of the character being entered. Actual 

input is not shown on the screen for security reasons. 

Possible Settings Any individual character which exists in the input field's font set can 

be chosen. The corresponding (chosen) character is input directly 

into the field. 

Default Setting * (asterisk) 

Position 

Specifies the position of the input field in pixels on the screen. 

X 

Y 








Displays 







etc.). 








Displays 







Destination (Password) Data Point 

Allows the connection of the variable which should be controlled with this input field. This variable is assigned to 

the password level corresponding to the last correctly entered password. If an incorrect password is entered, 

the password variable is reset to 0. 

Source 

Assign... 


Possible Settings Name of a process variable of data type UINT. 



Status 





Source 

Assign... 

Preview 



OK 

Cancel 









to 0. 







Buttons 



Note: 



Warning: 



3.2.2.3.2 Password Input Field − Properties: Colors 


3.2.2.3.2.1 Image 



Use Global 

Foreground 

Background 

Colors 









Displays 















Displays 














Source 

Assign... 




color. 







OK 

Cancel 

Buttons 



Note: 



Warning: 



3.2.2.3.3 Password Input Field − Properties: Passwords 

Provides settings for password levels as well as corresponding passwords. Passwords can be defined during 

the creation phase, but they may not be changed during runtime. If this is necessary, an input string can be used 

instead. 

3.2.2.3.3.1 Image 

Passwords 


Allows passwords to be defined for each individual password level (as well as the number of password levels 

themselves) during the creation phase. 

Number of 

Password Levels 

Password #1 

Password #2 

Password #3 

The number of password levels which manage the input field. Here, level 0 (no password) is 

also counted. 


Password for password level 1, the lowest password level (except level 0 which requires no 

password and is also the default for an incorrectly given password). 

Possible Settings A string of 1 to 6 characters. It should be noted that the corresponding 

characters have to be able to be input from the operator panel. 

Password for password level 2. 



Password for password level 3, the highest possible password level. 




OK 

Cancel 

Buttons 



Note: 



Warning: 



3.2.2.3.4 Password Input Field − Properties: Completion 


3.2.2.3.4.1 Image 






Source 

Assign... 

Completion 

Value 







variable. 




Source. 



OK 

Cancel 

Buttons 



Note: 



Warning: 




3.2.2.4 ListBox Input Field − Reference 

This input field can be used to display a list of texts from a text group on the screen underneath one another. A 

text can then be selected and highlighted using a process variable. 

If more texts are defined in the text group or the process variable than there is space set in the ListBox output 

field, then a corresponding excerpt is displayed. This ensures that the selected highlighted text is always visible. 

Text elements can be selected by the user with this type of input field. This is done using a cursor which can 

switch between individual texts without changing the connected process variable. The selection can be 

confirmed with a separately configured key. 

General 

Summary of the basic properties of these types of output fields. 

Function 

Data Types 

Displays vertically arranged lists of texts from a text group in a process variable with 

highlighting based on a numerical index from a process variable. 

The following data types can be displayed for this field: 

UINT − Chooses which text should be highlighted. 


Special 

Features 

Representation 

Individual 

Colors 


• Almost any number of texts can be defined during creation in the Visual Components 

editor and displayed during runtime (limited by the memory capacity of the target 

system). 

• Texts can be translated either conveniently in the editor or using external tools 

• Any desired operation can be implemented in the application using additional function 

keys or touch−operated fields. 

• Text groups can be used several times. 

• A cursor can be used inside the ListBox without the connected PV having to change. 

• A byte array can also be used to switch texts invisible or locked. 

• A cursor character even allows black/white displays to be used. 

Texts are output as a vertical list and are either extended to the set length with blank spaces or 

shortened if necessary. Because of this, the entire field always appears as a rectangle. 


• Automatic display of the correct text section so that the highlighted text is always 

visible in the picture. (as soon as the control is switched from input mode) 


• Selectable foreground and background colors as well as a separate color for 

highlighted text. 


• Configurable color for text locking state 


The following can be individually set for each output field of this type: 



• Foreground color (text color) for highlighted text 

• Background color for highlighted text 

• Foreground color for locked text 

• Background color for locked text 


Properties 




inserted. 

60 3.2.2.4 ListBox Input Field − Reference




Parameter 

Colors 

Keys 






The keys for navigating in the ListBox are defined with this setting. 

For each ListBox, individual keys can be defined for navigation. Additionally, keys that were defined 

in the global picture settings can be accepted. 


application or trigger other actions. For example, picture elements can be shown or hidden using 

their Status variables. 

Completion 


Locking 

Description 




Descriptive text about this input field can be entered under this tab. This text is saved in the Visual 

Components project but is not transferred to or processed on the target system. 

This text is optional but useful for project documentation. 

3.2.2.4.1 ListBox Input Field − Properties: Parameter 

Provides settings for the ListBox input field. 

3.2.2.4.1.1 Image 

Appearance 


X Specifies the position of the upper−left corner along the X axis (interval from the left display 



3.2.2.4 ListBox Input Field − Reference 61

Y 

Max. Text Length 

Rows 

Font 

Text Group 





This field can be placed freely on the screen. Therefore, 

X can be set from 0 to the width of the display minus the 


On text and semi−graphic displays, such as those which 

can be connected to the C130 CAN controller, fields can 

only be placed evenly on every sixth X−coordinate (X = 

0, 6, 12, 18, etc.). 

Specifies the position of the upper−left corner along the Y axis (interval from the upper 

display margin). Values for these parameters begin with 0 on the upper margin and increase 

to the height of the display minus one pixel (on the lower margin). 





Displays 







Specifies the maximum number of characters which can be displayed in a ListBox line. Texts 

longer than the allowed length will be truncated; blank spaces are used to "fill in" shorter 

texts. 

Possible Settings The field must be able to fit in the picture with its set size and 

font. 

Specifies the number of rows that will be displayed in the ListBox which also becomes the 

height of the output field. 


font. 

Chooses the output field font. 


Texts Sources and Options 

Selects the text group which should be output in this control at runtime. Its index must begin 

with 0 and rise consecutively. 

Option Bytes Byte array for controlling invisible/locked texts 

Cursor 

Character 

Displays an additional character for the text which has the focus (cursor) 

Variables 

Selected Item Variable which contains the index of the selected text 

Status Variable for switching the control invisible/locked 


OK 

Cancel 

Buttons 



Note: 



Attention: 






3.2.2.4.2 ListBox Input Field − Properties: Colors 


3.2.2.4.2.1 Image 

The 'Selected Item' area contains the selected element. This is the item which is linked with the PV. 

In the 'Disabled Item' section, color settings can be made for items which have been locked with the byte array. 


Use Global 

Foreground 

Background 

Colors 









Displays 















Displays 












Source 

Assign... 




color. 







OK 

Cancel 

Buttons 



Note: 



Attention: 



3.2.2.4.3 ListBox Input Field − Properties: Completion 


3.2.2.4.3.1 Image 






Source 

Assign... 

Completion 

Value 







variable. 




Source. 



OK 

Cancel 

Buttons 



Note: 



Attention: 



3.2.2.4.4 ListBox Input Field − Properties: Locking 


3.2.2.4.4.1 Image 



Locking 

Locking 

If selected, this input field can be locked during runtime. A locked input field is displayed but cannot be 

highlighted or accept new input. 

Locking only affects the input field, not the connected variable. Another input field on the same page 

can allow a different value to be written to the process variable even if this field is locked. 





Source 

Assign... 












selected: 




< Level 


>= Level 













OK 

Cancel 

Buttons 



Note: 



Attention: 






3.2.2.4.5 ListBox Input Field − Properties: Keys 

Allows keys to be configured for navigation in the ListBox. 

3.2.2.4.5.1 Image 

Use global tabs up/down 

settings 

Key Assignment 

If this option is selected, then the global tabs for up/down settings are used for 

navigation in the ListBox. 

Up key Control key for upward movement in the control 

Up key Control key for downward movement in the control 

Select key Control key for selecting the text item marked with the cursor 


OK 

Cancel 

Buttons 



Note: 



Attention: 



3.2.3 Output Fields − Reference 

Output fields are used to represent information on the visualization device. Data shown comes from process 

variables from the control application. As a rule, output fields cannot be controlled or influenced by the user. 

Since no user interaction takes place, output fields function in the same way on touch screen systems as they 

do on other systems. 

Visual Components provides output fields for all usual data types of process variables used in a control 

application. Some data types can be displayed in different ways. Because of this, the user is able to choose the 


est suited representation for each application. 

Output Fields Description 

Numeric Output Field This field allows data to be output in numeric form. 

String Output Field This field allows text to be output on the visualization unit. 

Date/Time Output Field 

Advanced Text Output 

Field 

Bar Graph Output Field 

ListBox Output Field 

Bitmap Output Field 

3.2.3.1 Numeric Output Field − Reference 

This field allows data to be output in numeric form. 

This output field allows the system date and time to be output. A series of fixed, 

predefined output formats are provided to do this. If these do not suffice, formatting 

can be configured in the control application and an output string can be used. This is 

also necessary to display other, different date and time information. 

This field allows text to be output based on a numeric index read from a process 

variable during visualization runtime. This provides a simple way to switch between 

a predefined number of texts. 

This output field allows numeric data to be output in the form of a movable bar 

graph. By default, bar graphs do not have any borders or other embellishments. 

These can be added easily as needed in the Visual Components project. 

Using this output field, a list of texts can be shown on the screen underneath one 

another. They can be used either from a text group or a process variable. A text can 

be highlighted and selected using a process variable. 

If more texts are defined in the text group or the process variable than there is 

space set in the ListBox output field, then a corresponding excerpt is displayed. This 

ensures that the selected highlighted text is always visible. 

The ListBox output field doesn't allow user interaction, either from panel keys or 

touch screen keypads. Thus, any necessary operations need to be implemented in 

the application. 

This field allows a bitmap graphic to be output depending on a numeric value read 

from a process variable during runtime. In this way, predefined bitmaps can be 

output depending on a process variable value. 

General 


Function Display of numeric process variables in text form 

Data Types 


USINT, SINT, UINT, INT, UDINT, DINT, and REAL 



Appearance 


• Scaling of the values for display 

The value is output as a series of numbers in the picture. 




• Display of the decimal point in adjustable positions 


• Overflow display (field filled in with asterisks '*') 

• Optional display of preceding zeroes 


Individual Colors The following can be individually set for each output field of this type: 



68 3.2.3.1 Numeric Output Field − Reference




variable. 

Properties 

Output field properties are set under the various tabs of the Properties dialog box. Field properties can be 

displayed by double−clicking on the output field in the editor and are automatically shown after a new field is 

inserted. 



Parameter 

Colors 

Scaling 

Simulation 

Description 

Basic parameters of the output field, such as position, size, connected variable, and status are 

defined under this tab. Settings under this tab have to be configured for all output fields created. 





visualization device. This means the user can select a suitable value range for calculation, editing, 

and display. 

No adjustments under this tab are necessary if the value of the variable should be displayed 1:1. 




Descriptive text about this output field can be entered under this tab. This text is saved in the Visual 



3.2.3.1.1 Numeric Output Field − Properties: Parameter 

Provides general settings for numeric output. 

3.2.3.1.1.1 Image 

3.2.3.1 Numeric Output Field − Reference 69

Format 


Number of Digits 

Digits after Decimal 

Point 

Font 

Display Leading 

Zeroes 

Specifies the amount of digits which should be displayed. If a decimal point is output, then 

the resulting field is one character wider than is specified here. 

Possible Settings 1 to 10 digits for DINT, UDINT, and FLOAT process variables 

1 to 5 digits for other data types. 


Specifies how many digits (of those designated in Number of Digits) should be shown 

after the decimal point. 

Possible Settings There must be at least one position before the decimal point left 

open. Therefore, the setting can be a maximum of Number of Digits − 

1. 



If this option is selected, then open spaces before the first significant digit are filled with 

zeroes. Otherwise, blank spaces fill up the rest of the vacant area. 

Position 


X 

Y 








Displays 







etc.). 








Displays 







Data Point 

Allows the connection of the variable which should be displayed with this output field. 

Source 

Assign... 


Possible Settings Name of a process variable with one of the following data types: 

USINT, SINT, UINT, INT, UDINT, DINT, or REAL. 



Status 





Source 

Assign... 

Preview 



OK 

Cancel 



Possible Values Bit 0 If 1, the output field is invisible. 




Buttons 



Note: 



Warning: 



3.2.3.1.2 Numeric Output Field − Properties: Colors 


3.2.3.1.2.1 Image 


Colors 

Use Global If this option is selected the settings in the project options are adopted for this output field. 


Foreground 

Background 


Allows the selection of color for the output field text. This setting can only be activated if the Use 

Global option is not selected. 





Displays 









Allows the selection of the output field's background color. This setting can only be activated if the 

Use Global option is not selected. 





Displays 











Source 

Assign... 



Possible Values Bits 0−7 The low byte contains the output field background 

color. 

Bits 8−15 The high byte contains the output field text color. 






OK 

Cancel 

Buttons 



Note: 



Warning: 



3.2.3.1.3 Numeric Output Field − Properties: Scaling/Limits 

Allows the flexible scaling of the displayed value. 




3.2.3.1.3.1 Image 

Enables scaling for this output field 

Scaling 

Active 

Scaling 

If this option is selected, the value in the output field is scaled. Otherwise, the actual numeric value 

of the process variable is shown. 



Displays the permissible value range of the PLC for the connected process variable. The range set here is 

scaled to the range set under Scaled Value Range for displaying the value in the output field. 

Parameters 

from PLC 

0% Value 

0% Source 

Assign... 

100% Value 




Specifies the lower limit of the permitted value range for the process variable on the PLC. This 








0% Value. 



Specifies the upper limit of the permitted value range for the process variable on the PLC. This 



100% Source Defines the process variable which contains the upper limit of the value range for the variable 


Assign... 





100% Value. 



Scaled Value Range 

Specifies the acceptable value range for the input and display in the visualization unit. During display, this 

range is scaled to the process variable range set under PLC Value Range. 

Parameters 

from PLC 

0% Value 




Specifies the lower limit of the permitted value range for the process variable on the control 

panel. 



input field. 


as follows. 

USINT SINT 

INT UINT 









Example: 




0% Source Defines the process variable which contains the lower limit of the value range for the variable 

processed with this input field on the control panel during runtime. This setting is only available 

if Parameters from PLC is selected. 






UDINT UDINT 

REAL REAL 






Assign... 

100% Value 

100% Source 

Assign... 




Specifies the upper limit of the allowed value range for the process variable on the control 

panel. 



input field. 


as follows. 

USINT SINT 

INT UINT 









Example: 




Determines the process variable which contains the upper limit of the value range for the 

variable processed with this input field on the control panel during runtime. This setting is only 

available if Parameters from PLC is selected. 






UDINT UDINT 

REAL REAL 






Shift Decimal Point 

Using this setting, the decimal point in the output field can be moved during runtime using a variable from the 


This setting is only available if Scaling Active is selected under this tab and at least 1 decimal place is specified 

in the Digits after Decimal Point field under the Parameter tab (otherwise, there is no space set aside for the 

decimal point). 

Source Determines the process variable which contains the number of additional decimal places to be 

displayed. If fewer decimal places should be displayed, then the value of the variable has to be 


Assign... 

negative. The resulting number of decimal places is determined by adding the value of this process 

variable with the value set in the Digits after Decimal Place field under the Parameter tab. This 

number must be able to fit in the selected field size. 

Possible Settings Name of a process variable of type USINT (default) or SINT. Data type SINT must 

be used if negative decimal point shifts are necessary (fewer decimal places). 



Note: The Type−Filter button must be unchecked in the dialog box to select a variable of type 

SINT. 


OK 

Cancel 

Buttons 



Note: 



Warning: 



3.2.3.1.4 Numeric Output Field − Properties: Simulation 


3.2.3.1.4.1 Image 



Specifies the output field value that should be displayed in the editor's Simulation mode. Simulation mode can 

be used to create visualization pictures for product documentation. Visual Components does not use these 

settings in any other place. 



Simulation 

Value 

CharBox 

Desired display of the output field in simulation mode as a character string. 

Possible Settings Any character string which can be displayed in the output field using the the 


input. 



inserted into the Simulation Value field by double−clicking on it in the CharBox. 



OK 

Cancel 

Buttons 



Note: 



Warning: 



3.2.3.2 String Output Field − Reference 

This field allows text to be output on the visualization unit. 

General 


Function Display of text of process variables of type STRING[] 

Data Types 


STRING[] 


Special Features None 

Appearance 


The value will be output as a series of characters in the display. 










variable. 

Properties 



inserted. 

3.2.3.2 String Output Field − Reference 77



Parameter 

Colors 

Simulation 

Description 












3.2.3.2.1 String Output Field − Properties: Parameter 

Provides general settings for the string output field. 

3.2.3.2.1.1 Image 

Format 



Font 

Specifies the number of characters which should be displayed. 


font. 



Position 

Specifies the position of the output field in pixels on the screen. 


X Specifies the position of the upper left corner along the X axis (interval from the left display 


78 3.2.3.2 String Output Field − Reference


Y 






Displays 







etc.). 








Displays 







Destination Data Point 


Source 

Assign... 


Possible Settings Name of a process variable of data type STRING [] (array of variables of data 

type STRING, ANSI C programmers must use data type plcstring[]) 



It must be noted that the entire array is selected, not just one element from it. 

Status 


Source 

Assign... 

Preview 



OK 

Cancel 







Buttons 



Note: 



Warning: 




3.2.3.2.2 String Output Field − Properties: Colors 


3.2.3.2.2.1 Image 


Use Global 

Foreground 

Background 

Colors 

If this option is selected the settings in the project options are adopted for this output field. 








Displays 















Displays 












80 3.2.3.2 String Output Field − Reference


Source 

Assign... 




color. 







OK 

Cancel 

Buttons 



Note: 



Warning: 



3.2.3.2.3 String Output Field − Properties: Simulation 


3.2.3.2.3.1 Image 







Simulation 

Value 

CharBox 



input. 






OK 

Cancel 

Buttons 



Note: 



Warning: 



3.2.3.3 Date/Time Output Field − Reference 

This output field is used to output the system date and time. A series of fixed, predefined output formats are 

provided to do this. If these do not suffice, formatting can be configured in the control application and an output 

string can be used. This is also necessary to display other, different date and time information. 

General 


Function Displays controller date and/or time information (system time). 

Data Types 


None (the system time is displayed) 


Special 

Features 

Appearance 

Individual 

Colors 

Uses predefined date and time formats. User−specific formats can only be implemented in the 

control application and displayed with output strings or a combination of several numeric output 

fields. 

The value will be output as a series of characters in the display. 


• Automatic formatting of date/time information 









Properties 




inserted. 

82 3.2.3.3 Date/Time Output Field − Reference




Parameter 

Colors 

Simulation 

Description 

Basic parameters for the output fields such as position, size, and status are defined under this tab. 

Settings under this tab have to be configured for all output fields created. 










3.2.3.3.1 Date/Time Output Field − Properties: Parameter 

Provides general settings for date/time output fields. 

3.2.3.3.1.1 Image 

Format 


Time Format Determines the format in which the date and/or time is displayed. 

Possible Settings Any of the formats out of the selection list: 

• DD.MM.YY HH:MM:SS 

• MM.DD.YY HH:MM:SSa 

• HH:MM:SS 

• HH:MM:SSa 

• HH:MM 

• HH:MMa 

Meanings of the abbreviations 

DD Day displayed with two digits 

MM Month displayed with two digits 

3.2.3.3 Date/Time Output Field − Reference 83

Font 

YY Year displayed with two digits 

HH Hour displayed with two digits 

MM Minutes 

SS Seconds 

a AM/PM display. In the other formats, a 24−hour display is 

used. AM/PM display is only represented by one 

character (a/p). 

Other characters (periods, colons, spaces) are output just as 

they appear in the format. 

The selected format determines the width of the field, so a 

separated display of the field size is not necessary or possible. 

The field must be able to fit in the picture with its set size and 

font. 

Chooses the font which should be used for the output field. 


Position 


X 

Y 








Displays 







etc.). 








Displays 







Status 


Source 

Assign... 

Preview 












OK 

Cancel 

Buttons 



Note: 



Warning: 



3.2.3.3.2 Date/Time Output Field − Properties: Colors 


3.2.3.3.2.1 Image 


Use Global 

Foreground 

Colors 









Displays 









Background Allows the selection of the output field's background color. This setting can only be activated if the 


Possible Settings for Any desired color from a palette of 256 colors can be chosen. Standard 

3.2.3.3 Date/Time Output Field − Reference 85

Full Graphic Displays palette colors are illustrated in the reference manual. 





Displays 







Source 

Assign... 




color. 







OK 

Cancel 

Buttons 



Note: 



Warning: 



3.2.3.3.3 Output Date/Time − Properties: Simulation 

Input of the displayed value in the editor simulation mode. 

3.2.3.3.3.1 Image 





Specifies the output field value that should be displayed in the simulation mode of the editor. The simulation 



Simulation 

Value 

CharBox 




input. 




It is displayed using the set font of the input field. 


OK 

Cancel 

Buttons 

Applies settings and closes the dialog box. If settings cannot be accepted because of a mistake, this is 

shown and the dialog box is not closed. 

Note: 

All changes are accepted, including those made under different (hidden) tabs. 


Warning: 



3.2.3.4 Advanced Text Output Field − Reference 

This field allows text to be output based on a numeric index read from a process variable during visualization 

runtime. This provides a simple way to switch between a predefined number of texts. 

General 


Function Display of text based on a numeric index from a process variable 

Data Types The following data types can be displayed for this field: 

3.2.3.4 Advanced Text Output Field − Reference 87

UINT 


Special 

Features 

Appearance 

Individual 

Colors 


• Almost any number of texts can be defined during creation in the Visual Components 

editor and displayed during runtime (limited by the memory capacity of the target 

system). 

• Texts can be translated either conveniently in the editor or using external tools 

• Easy highlighting of text with the Attribute Data Point variable 

• Text groups can be used several times 

The value is output in the picture as text from a text group using the text number which 

corresponds to the connected process variable. 





• Display of invalid values in the index variable (Field filled in with asterisks '*') 






Properties 



inserted. 



Parameter 

Colors 

Simulation 

Description 












3.2.3.4.1 Advanced Text Output Field − Properties: Parameter 

Provides general settings for advanced text output. 

3.2.3.4.1.1 Image 


88 3.2.3.4 Advanced Text Output Field − Reference


Format 



Font 

Text Group 

Specifies the number of characters which should be displayed. If the connected text 

group contains longer texts, then they are limited to this number of characters when 

displayed. 


font. 



Selects the text group and corresponding texts which should be displayed in the output 

field. 

Possible Settings Any existing text group in the project can be selected. 

Position 


X 








Displays 







etc.). 

Y Specifies the position of the upper left corner along the Y axis (interval from the upper display 








Displays 







Text Number Data Point 

Allows the connection of a variable which should select the text displayed in the output field. 

Source 

Assign... 


Possible Settings Name of a UINT process variable. 

Possible Values Corresponding to the number of texts in the connected text group, values 

from 0 to one less than the "Number of Texts" are allowed as long as the 

used text group numbers have not been changed. 

If the used text group numbers were changed, then only values can be set 

which have a text in the text group assigned. 

If the variable has a different value, this will be treated as an overflow 

situation, and a series of asterisks will be displayed. 



Allows the connection of a variable for display control. 

Source 

Assign... 

Attribute Data Point 



Possible Values Bit 0 If 1, the output field is highlighted. For pure text−displays (LCD and 

VFD Line Displays), text is displayed as blinking. On all other 

displays, text is inverted. 

Further options for color displays are available under the Colors tab 

under Properties. 




Status 


Source 

Assign... 

Preview 












OK 

Cancel 

Buttons 



Note: 



Warning: 



3.2.3.4.2 Advanced Text Output Field − Properties: Colors 


3.2.3.4.2.1 Image 


Use Global 

Colors 



Foreground Allows the selection of color for the output field text. This setting can only be activated if the Use 






Displays 









Background 








Displays 











Source 

Assign... 




color. 







OK 

Cancel 

Buttons 



Note: 



Warning: 



3.2.3.4.3 Advanced Text Output Field − Properties: Simulation 


3.2.3.4.3.1 Image 








Simulation 

Value 

CharBox 




input. 






OK 

Cancel 

Buttons 



Note: 



Warning: 



3.2.3.5 Bar Graph Output Field − Reference 

This output field allows numeric data to be output in the form of a movable bar graph. By default, bar graphs do 

not have any borders or other embellishments. These can be added easily as needed in the Visual Components 

3.2.3.5 Bar Graph Output Field − Reference 93

project. 

General 


Function Displays numeric process variables as moving bars. 

Data Types 

Availability 


Appearance 



USINT, UINT 

Graphic−capable operator panels 

• IPC2001 and IPC5000 families with 1/4 VGA, VGA, or larger display 

• Power Panel PP41 

• Semi−graphic displays on the C130 CAN controller (no pure text displays) 


• Selectable value scaling for display 

• Choice of horizontal or vertical extension, each in both directions (left/right, 

upward/downward) 

The value is output as a moving bar graph in the picture. 




• Horizontal or vertical extension possible in both directions 


• Foreground color (bar graph color) 



Properties 



inserted. 



Parameter 

Colors 

Scaling 

Active 

Description 







visualization device. This allows any desired range of values on the PLC to be automatically 

adapted to the length of the bars. 

If the variable value is specified to the length of the bar in pixels, then no settings are necessary 

under this tab. 

Descriptive text about this output field can be entered under this tab. This text is saved in the 

Visual Components project but is not transferred to or processed on the target system. 


3.2.3.5.1 Bar Graph Output Field − Properties: Parameter 

Provides general settings for bar graph output. 


94 3.2.3.5 Bar Graph Output Field − Reference


3.2.3.5.1.1 Image 

Format 


Width 

Length 

Determines the width of the displayed bar graph. The width of the bar corresponds to the extension 

direction set under Direction. For a horizontal bar (extension from left to right, or right to left), this 

parameter describes the height. For a vertical bar (extension from down to up, or up to down), this 

parameter describes the width. 

This setting is made with pixels. 

Possible Settings From 1 to the display size in the corresponding direction. 

The set size and position of the field must allow it to fit in the picture. 

Determines the length of the displayed bar graphic. The length of the bar corresponds to the 

extension direction set under Direction. For a horizontal bar (extension from left to right, or right to 

left), this parameter describes the width. For a vertical bar (extension from down to up, or up to down), 

this parameter describes the height. 

This setting is made with pixels. 

Possible Settings From 1 to the display size in the corresponding direction. 


Direction Determines the extension of the bar graph in one of the four main directions. The following settings 

can be chosen from the list. 


Position 


X 

Y 

Right Bar extends 

from left to 

right 

Upward Bar extends 

from down 

to up 

Links Bar extends 

from right to 

left 

Downward Bar extends 

from up to 

down 

Specifies the position of the upper left corner along the X axis (interval from the left display margin). Values 






Semi−graphic Displays 

This field can be placed freely on the screen. Therefore, X can be set from 

0 to the width of the display minus the width of the field in pixels. 

On semi−graphic displays, such as those which can be connected to the 

C130 CAN Controller, fields can only be placed evenly on every sixth 

X−coordinate (X = 0, 6, 12, 18, etc.). On pure text displays the display of 

bar graphics is not possible. 

Specifies the position of the upper left corner along the Y axis (interval from the upper display margin). 






Semi−graphic Displays 

The field can be placed freely in the display. Therefore, Y can be set from 0 to the 

height of the display minus the height of the field in pixels. 

On semi−graphic displays, such as those which can be connected to the CAN 

Controller C130, fields can only be placed evenly on every eighth Y−coordinate (Y 

= 0, 8, 16, 24, etc.). On pure text displays the display of bar graphics is not 

possible. 

Data Point 


Source 

Assign... 


Possible Settings Name of a process variable of data type USINT or UINT. 



Status 








Assign... 

Preview 



OK 

Cancel 




Buttons 



Note: 



Warning: 



3.2.3.5.2 Bar Graph Output Field − Properties: Colors 


3.2.3.5.2.1 Image 


Use Global 

Colors 

If this option is selected the settings in the project options are adopted for this 

output field. Therefore, settings for foreground and background cannot be made. 

Foreground Allows the selection of the color which represents the bar graph. This setting can 

only be activated if the Use Global option is not selected. 


Background 

Possible Settings 

for Full Graphic 

Displays 


for Semi−graphic 

Displays 

Any desired color from a palette of 256 colors can be 

chosen. Standard palette colors are illustrated in the 

reference manual. Customer−specific operator panels can 

have their own color palettes. Correct colors are always 

indicated in the selection list. 

Semi−graphic displays, such as those which can be 

connected to the C130 CAN controller, support only black 

and white colors. This is also true for the PP21 and PP41 

Power Panels and their customer−specific varieties. 

Allows the selection of the output field's background color. This setting can only 

be activated if the Use Global option is not selected. 


for Full Graphic 

Displays 


for Semi−graphic 

Displays 

Any desired color from a palette of 256 colors can be 

chosen. Standard palette colors are illustrated in the 

reference manual. Customer−specific operator panels can 

have their own color palettes. Correct colors are always 

indicated in the selection list. 

Semi−graphic displays, such as those which can be 

connected to the C130 CAN controller, support only black 

and white colors. This is also true for the PP21 and PP41 

Power Panels and their customer−specific varieties. 



Source 

Assign... 




color. 

Bits 8−15 The high byte contains the color of the bar. 






OK 

Cancel 

Buttons 



Note: 



Warning: 



3.2.3.5.3 Bar Graph Output Field − Properties: Scaling 

Allows the flexible scaling of the displayed value. 

3.2.3.5.3.1 Image 




Enables scaling for this output field 

Scaling Active 

Scaling 

If this option is selected, the value in the output field is scaled; otherwise, the actual numeric 

value of the process variable is shown as the extension of the bar in pixels. 



Specifies the allowed value range of the connected process variable on the PLC. The range set here is 

scaled to the length of the bar for the display of the value in the ouput field. If the connected variable 

has the value set under '0% Value,' then the bar will be displayed as empty. If the connected variable 

has the value set under '100% Value,' then the bar will appear filled−in. 

0% Value 

100% Value 

Specifies the lower limit of the permitted value range for the process variable on the PLC. 


Specifies the upper limit of the permitted value range for the process variable on the 

PLC. 



OK 

Cancel 

Buttons 



Note: 



Warning: 




3.2.3.6 ListBox Output Field − Reference 

Using this output field, a list of texts can be shown on the screen underneath one another. They can be used 

either from a text group or a process variable. A text can be highlighted and selected using a process variable. 

If more texts are defined in the text group or the process variable than there is space set in the ListBox output 

field, then a corresponding excerpt is displayed. This ensures that the selected highlighted text is always visible. 

The ListBox output field doesn't allow user interaction, either from panel keys or touch screen keypads. Thus, 

any necessary operations need to be implemented in the application. 

General 


Function 

Data Types 

Displays vertically−ordered lists of texts from a text group or from an array of string 

variables in a process variable. Highlighting is based on the number index from a 

process variable. 


STRING[][] − optional as the source of the text to be displayed 

UINT − Chooses which text should be highlighted. 



Appearance 



• Almost any number of texts can be defined during creation in the Visual 

Components editor and displayed during runtime (limited by the memory 

capacity of the target system). 

• Texts can be translated either conveniently in the editor or using external 

tools 

• Texts can also be provided using a process variable during runtime; in this 

case, language−switching must be prepared in the application. 

• Any desired operation can be implemented in the application using additional 

function keys or touch−operated fields. 

• Text groups can be used several times 

Texts are output as a vertical list and are either extended to the set length with blank 

spaces or shortened if necessary. Because of this, the entire field always appears as 

a rectangle. 


• Automatic display of the correct text section so that the highlighted text is 

always visible in the picture. 


• Selectable foreground and background colors as well as a separate color for 

highlighted text. 


• Display of invalid values in the index variable (Field filled in with asterisks '*') 





• Foreground color (text color) for highlighted text 

• Background color for highlighted text 


Properties 




100 3.2.3.6 ListBox Output Field − Reference


inserted. 



Parameter 

Colors 

Description 









3.2.3.6.1 ListBox Output Field − Properties: Parameter 

Provides general settings for ListBox output. 

3.2.3.6.1.1 Image 

Appearance 


X 








This field can be placed freely on the screen. Therefore, 

X can be set from 0 to the width of the display minus the 


On text and semi−graphic displays, such as those which 

can be connected to the C130 CAN controller, fields can 

only be placed evenly on every sixth X−coordinate (X = 

0, 6, 12, 18, etc.). 

Y Specifies the position of the upper left corner along the Y axis (interval from the upper display 



3.2.3.6 ListBox Output Field − Reference 101

Max. Text Length 

Rows 

Font 





Displays 







Specifies the maximum number of characters which can be displayed in a ListBox line. Texts 

longer than the allowed length will be truncated; blank spaces are used to "fill in" shorter 

texts. 


font. 

Specifies the number of rows that will be displayed in the ListBox which also becomes the 

height of the output field. 


font. 



Source of Texts 

Determines the source of the displayed texts. Only one of the two following options can be selected and used. 

Text Group 

String 

Array 

Assign... 

With this setting, a text group is used as the source for the text to be displayed. The text cannot be 

altered during runtime, but language switching can naturally be used. 

Possible Settings Text group with default text numbering (text groups with text numbering which 

has been changed by the user cannot be used). 

With this setting, an array of STRINGs is used as the source for the text. In this way, texts can be 

changed and expanded during runtime. However, language−switching must also be prepared in the 

application if it is to be used. 

Possible Settings Name of a process variable of data type STRING[][]. 

Example: 

In ANSI C, the variable must be declared as follows to define and connect 4 

texts with a maximum length of 80 characters to the ListBox. 

_GLOBAL plcstring texts[4][80]; 

Access is then possible with normal array indexing, with texts[0] designating 

the first string and texts[1][4] designating the fifth character in the second 

string. 

Possible Values The strings can contain any desired text, but only characters existing in the 

selected font will be displayed on the screen. 

The Assign... button opens a dialog box to select a variable for the String array input field. By 


It should be noted that the entire array is connected, not just parts of it. 

Variables 


Allows the connection of the variable which should select the text highlighted in the output field. In this way, 

texts in the ListBox are automatically advanced and the marked text is visible. The ListBox is an output field, 

which means that the operator cannot change the variable using the ListBox itself. However, this can be solved 

with additional input elements in the application. 



Source 

Assign... 

Status 



Possible Values Depending on the number of texts in the connected text group (or 

number of STRINGs in the connected process variable), values 

can range from 0 to one less than the "Number of Texts". If the 

variable has a different value, this will be treated as an overflow 

situation, and a series of asterisks will be displayed. 




Source 

Assign... 

Preview 



OK 

Cancel 







Buttons 



Note: 



Warning: 



3.2.3.6.2 ListBox Output Field − Properties: Colors 


3.2.3.6.2.1 Image 

3.2.3.6 ListBox Output Field − Reference 103

Colors 

Allows colors to be set for unhighlighted elements in the editor. Settings can also be adjusted during runtime 

using a process variable. 

Use Global 

Foreground 

Background 









Displays 















Displays 













color. 




Assign... 

For both of these settings, the same colors which can be used for foreground 

and background in the editor are possible (see above). 



Selected Item 

Allows colors to be set for highlighted elements (active lines) in the editor. Settings can also be adjusted during 

runtime using a process variable. 

Foreground 

Background 

Source 

Assign... 

Allows the selection of the color for the output field active line text. 





Displays 









Allows the selection of the color for the output field active line background. 





Displays 












color. 







OK 

Cancel 

Buttons 



Note: 



Warning: 



3.2.3.7 Bitmap Graphic Output Field − Reference 

This field allows a bitmap graphic to be output depending on a numeric value read from a process variable 

during runtime. In this way, various predefined bitmaps can be output depending on the value of a process 

3.2.3.7 Bitmap Graphic Output Field − Reference 105

variable. 

General 


Function Displays a bitmap based on a numeric index from a process variable 

Data Types 

Availability 

Special 

Features 

Appearance 

Individual 

Colors 


UINT 

Full graphics−capable panels with bitmap support 

• IPC2001 and IPC5000 families with 1/4 VGA, VGA, or larger display 

• Power Panel PP41 (only monochrome bitmaps) 


• Nearly any number of bitmaps can be set up in the Visual Components editor during the 

creation phase and represented during runtime (limited by the memory capacity of the 

target system). 

The value is selected as a bitmap from a list (corresponding to the connected process variable) 

which is defined during the creation phase. It is then output in the picture. 


None 


• Display of color and monochrome bitmaps 

Properties 



inserted. 



Parameter 

Description 






3.2.3.7.1 Bitmap Graphic Output Field − Properties: Parameter 

Provides the settings for the bitmap graphic output field. 

3.2.3.7.1.1 Image 


106 3.2.3.7 Bitmap Graphic Output Field − Reference


Position 


X 

Y 

Specifies the position of the upper left corner along the X axis (interval from the left display margin). Values 



The output field must be placed so that the largest (widest) bitmap in the bitmap list can be completely 

displayed on the screen. Output field width is not explicitly set. 

Possible Settings This field can be placed freely on the screen. Therefore, X can be set from 0 to the 

width of the display minus the width of the field in pixels. 

Specifies the position of the upper left corner along the Y axis (interval from the upper display margin). 



The output field must be places so that the largest (highest) bitmap in the bitmap list can be completely 

displayed on the screen. Output field height is not explicitly set. 

Possible Settings The field can be placed freely in the display. Therefore, Y can be set from 0 to the height 

of the display minus the height of the field in pixels. 

Data Point 

Allows the connection of the variable which should select the bitmap displayed in the output field. 



3.2.3.7 Bitmap Graphic Output Field − Reference 107

Assign... 

Possible Values Values from 0 to one less than the "Number of Bitmaps" are valid. If the variable 

has a different value, then the index is internally limited to this range. The value of 

the connected variable is not changed. 



Status 


Source 

Assign... 







Bitmaps 

Provides a table to select bitmaps for this output field. Bitmaps can be added, removed, or sorted in this list. 

Number 

Bitmap 

This column shows the number of the bitmap shown on the right. The connected process variable 

under Data Point must be assigned this value to display this particular bitmap. 

Possible Settings This column is only used to show that numbering bitmaps can only be altered 

by sorting. Numbering always begins with 0 and increases by 1 for each 

additional bitmap. 

Shows the currently selected bitmap for the corresponding number in the index on the left. Clicking 

on a bitmap name opens a selection list where another bitmap can be selected. 

Possible Settings Any bitmap in the project can be selected. 

Add Adds a new bitmap to the end of the list. 

Insert 

Remove 

Upward 

Downward 

In doing so, however, equal sized bitmaps should be used to obtain an 

optimal display of the output field. The background is not deleted when 

switching bitmaps for performance reasons and to avoid flickering on the 

screen. Therefore, the rest of an old bitmap can remain on the display 

when different sized bitmaps are used. 

Bitmaps are displayed in their actual size which means the widest or 

tallest bitmap in the list determines the size of the output field. Scaling 

bitmaps to the same size does not take place and must be carried out in 

a graphics program if necessary. 

Inserts a new bitmap into the currently highlighted field of the bitmap list. The remaining bitmaps will 

be moved one space down in the list (the bitmap numbers will be increased/decreased by one). 

Removes the currently selected bitmap from the list. The remaining bitmaps underneath will be 

advanced upwards and will receive a lower index number (by 1 per removed bitmap). 

Exchanges the position of the currently selected bitmap in the list with the one directly over it (the 

bitmap will be moved up one position). 

Exchanges the position of the currently selected bitmap in the list with the one directly below it (the 

bitmap will be moved down one position). 

Preview 

Shows the currently selected bitmap in the list so it can be checked. 


OK 

Buttons 


108 3.2.3.7 Bitmap Graphic Output Field − Reference


Cancel 



Note: 



Warning: 



3.2.4 Touch−Operated Fields − Reference 

Touch−operated fields either partially or completely replace operator panel key functions on systems with 

graphic touch screens. These include all touch screens with QVGA, VGA, or larger displays which are 

connected to the IPC2001 and IPC5000 families. 

Touch−operated fields are operated exclusively through the touch of correspondingly configured surfaces on the 

touch screen. Simultaneous operation using panel keys can be achieved by having a function key configured at 

the same time for the same action. 

There are several touch−operated fields available; these will be described in their own sections. 

Touch−Operated Field Description 

Button Touch Field 

HotSpot Touch Field 

3.2.4.1 Button Touch−Operated Field − Reference 

This touch−operated field allows surfaces to be configured in button form in the 

visualization picture. After it is set, the button functions like a conventional panel 

key. The available actions are applied to the area of operation on touch screen 

systems. 

Pressed and released states can be displayed for this button to show when it is 

being activated. 

The HotSpot touch−operated field allows invisible surfaces to be configured in a 

visualization picture. After it is set, the button functions like a conventional panel 

key. The available actions are applied to the area of operation on touch screen 

systems. 

The HotSpot does not possess its own image either in its pressed or released 

states. Therefore, other elements such as bitmaps, rectangles, or circles can 

brighten and enhance its touch function. 

This touch−operated field allows surfaces to be configured in button form in the visualization picture. After it is 

set, the button functions like a conventional panel key. The available actions are applied to the area of operation 

on touch screen systems. 

Pressed and released states can be displayed for this button to show when it is being activated. 

This touch−operated field is exclusively operated using the touch screen. 

General 

Summary of the basic properties of these types of touch fields. 

Function Operates the visualization application using touch buttons displayed on the touch screen. 

3.2.4 Touch−Operated Fields − Reference 109

Actions 

Availability 

Special 

Features 

Appearance 

Individual 

Colors 

The following actions can be triggered by activating a touch button: 

Change Picture Changes to another picture in the project. 

Next Picture Changes to the next picture. 

Previous Picture Changes to the previous picture. 

Set USINT Sets a USINT process variable to a defined value. 

Set UINT Sets a UINT process variable to a defined value. 

Toggle USINT Switches a USINT process variable between two values. 

Toggle UINT Switches a UINT process variable between two values. 

Momentary USINT Sets a USINT process variable when activated. 

Increment/Decrement Increases or decreases a process variable incrementally. 

Operator panels with a graphic touch screen (touch screens on QVGA, VGA and larger displays 

with the IPC2001 and IPC5000 families) 


• Keys can be evaluated in the control task using the key matrix. Jog key operation is 

possible by setting the priority of the key driver (touch driver). 

• Separate configurable appearance of pressed and released states. 

• Replaces function keys on operator panels with touch screens. 

• Input locking (using the touch−operated field) using the connected Status process 

variable for simple user management. 



from external stations (depending on the configured action). 

This field is shown as a button on the visualization unit. 



• Selectable foreground, background, and border colors 

• Optional 3D representation 

• Optional bitmap display on the button 

• Appearance for pressed and released states configured separately 


The following can be individually set for each touch field of this type: 

• Foreground color (text color) − separate for pressed and released states 

• Background color − separate for pressed and released states 

• Border color − upper and left−hand, as well as lower and right−hand sides configured 

separately (3D effect) 


Operation Touching buttons placed on the touch screen. 

Properties 

Touch−operated field properties are set under the various tabs of the Properties dialog box. Field properties 

can be displayed by double−clicking on the touch field in the editor and are automatically shown after a new 

field is inserted. 



Parameter 

Appearance 


Basic parameters of touch fields such as position, size, connected variable, and status are 

defined under this tab. Settings under this tab have to be adjusted for all touch fields 

created. 

Defines the button caption, border width, bitmaps to be displayed, and other display 

options. These must be configured for all touch−operated fields of this type. 

Colors Settings under this tab can be used to specify user−defined color settings and to connect 

110 3.2.4 Touch−Operated Fields − Reference


Action 

Description 

process variables for controlling colors. These possibilities are very useful for color 

displays, but can also be used for grayscale displays. 

Defines the action to be carried out with this button. This setting must be set for each 

touch−operated field of this type. 

Settings for the selected action are also defined under this tab. 

Descriptive text about this output field can be entered under this tab. This text is saved in 

the Visual Components project but is not transferred to or processed on the target system. 


3.2.4.1.1 Button Touch−Operated Field − Properties: Parameter 

Provides general settings for the touch button. 

3.2.4.1.1.1 Image 

Dimension 

Determines the touch field position and size on the screen. Different touch fields may not overlap in any place. 

Left 

Top 




Possible Settings The field can be placed freely in the display, so that Left can be set from 0 to the 





Possible Settings The field can be placed freely in the display, so that Top can be set from 0 to 

the height of the display minus the height of the field in pixels. 

Width Determines the touch field width in pixels. 

Possible Settings From 1 to the display width. 

3.2.4.1 Button Touch−Operated Field − Reference 111

Height 


Determines the touch field height in pixels. 

Possible Settings From 1 to the display height. 


Offset 

Determines the location of the touch−operated field in the key matrix. This setting is only required if the touch 

field should be queried using the key matrix. No setting is required here for the actions which can be configured 

for the touch field directly in the Visual Components editor. 

Key Matrix 

Offset 

Effective 

Index 

This option defines whether a user defined offset should be defined in the key matrix for this 

element. 

If this option is selected, the button offset must be defined in the input field. If applicable, the offset 

counts starting with the existing keys of the operator panel which is used. 

Example: 

Panel with 24 keys 

Offset set to 17 

The touch field is located at Index [41] of the key matrix. 

Possible Settings 0 to 255 minus the number of existing keys on the panel. 

(The resulting index may result in 255 at the most) 

Displays the resulting index in the key matrix for informational purposes. This information is only 

shown if Key Matrix Offset is selected. 

Status 


Source 

Assign... 


OK 

Cancel 



Possible Values Bit 0 If 1, the touch button is invisible. 

Bit 1 If 1, no operation of the touch field is permitted. (locked) 




Buttons 



Note: 



Warning: 




112 3.2.4.1 Button Touch−Operated Field − Reference


3.2.4.1.2 Button Touch−Operated Field − Properties: Appearance 

Defines the appearance of the touch button on the screen. 

3.2.4.1.2.1 Image 

Appearance 

Defines basic settings for both states of the touch button − pressed and released. 

Font 

Border Width 

Chooses the font which should be used for the touch button. If the button is only identified with a 

bitmap, then this setting has no effect. 


Sets the width of the touch button border in pixels. 

Possible Settings From 0 to the available surface of the button 

(The text and the bitmap on the button must be able to fit within the border) 

Released Button 

Defines specific settings for button appearance in its released state. 

Text Group 

Text 

Selects the text group which contains the text for the button. Texts cannot be input 

directly. Instead, they must be included and accessed from a text group. 

Possible Settings Any text group in the project can be selected. 

In addition, the first empty entry in the list is available for 

buttons which do not use a caption. 

Chooses the text to be displayed from the selected text group. 

Possible Settings Any text contained in the text group can be selected. 

Bitmap Selects the bitmap to be displayed on the touch button: either alone (centered) or 

with text (left on the button). 


Possible Settings Any bitmaps existing in the project can be selected as long as 

they can fit within it. 


buttons which do not use bitmaps. 

Pressed Button 

Defines specific settings for the appearance of the button in its pressed state. 

Text Group 

Text 

Bitmap 

Selects the text group which contains the text for the button. Texts cannot be input 

directly. Instead, they must be included and accessed from a text group. 

Possible Settings Any text group in the project can be selected. 


buttons which do not use a caption. 

Chooses the text to be displayed from the selected text group. 

Possible Settings Any text contained in the text group can be selected. 

Selects the bitmap to be displayed on the touch button: either alone (centered) or 

with text (left on the button). 

Possible Settings Any bitmaps existing in the project can be selected as long as 

they can fit within it. 


buttons which do not use bitmaps. 

Preview 

Shows the field with the currently selected settings. Can be toggled between pressed and released states. 


OK 

Cancel 

Buttons 



Note: 



Warning: 



3.2.4.1.3 Button Touch−Operated Field − Properties: Colors 

Allows colors to be set for button display. 

3.2.4.1.3.1 Image 




Dimensions 

Determines the colors for the buttons borders. 3D effects can be simulated with separately defined colors for 

the left and upper borders as well as the right and lower borders. Settings can also be adjusted during runtime 

using a process variable. 

Raised 

Sunken 

Source 

Sets the color of the upper and left borders of the button in its released state. To 

create a distinct button, this setting should be set to a light color. In its pressed 

state, the right and bottom borders will be shown with this color. 

Possible Settings Any desired color from a palette of 256 colors can 

be chosen. Standard palette colors are illustrated in 

the reference manual. Customer−specific operator 

panels can have their own color palettes. Correct 

colors are always indicated in the selection list. 

Sets the color of the lower and right borders of the button in its released state. To 

create a distinct button, this setting should be set to a dark color. In its pressed 

state the left and top borders will be shown with this color. 

Possible Settings Any desired color from a palette of 256 colors can 

be chosen. Standard palette colors are illustrated in 

the reference manual. Customer−specific operator 

panels can have their own color palettes. Correct 

colors are always indicated in the selection list. 



Possible Values Bits 0−7 The low byte contains the sunken color of the 

button. 

Bits 8−15 The high byte contains the raised color of the 

button. 

For both settings, the same colors as for the settings Sunken 

and Raised are possible in the editor (see above). 

Assign... The Assign... button opens a dialog box to select a variable for the Source field. 


By default, only variables of suitable types are displayed. 

Released Button 

Allows colors to be set for the button surface and text in its released state. Settings can also be adjusted during 


Foreground 

Background 

Source 

Assign... 

Allows the selection of the color of the button text. This setting can also be used for a possible 

monochrome bitmap placed on the button. 

Possible Settings Any desired color from a palette of 256 colors can be chosen. Standard palette 

colors are illustrated in the reference manual. Customer−specific operator 

panels can have their own color palettes. Correct colors are always indicated 

in the selection list. 

Allows the selection of the color for the button background. 








color. 






Pressed Button 

Allows colors to be set for the button surface and text in its pressed state. Settings can also be adjusted during 


Foreground 

Background 

Source 

Allows the selection of the color of the button text. This setting can also be used for a possible 

monochrome bitmap placed on the button. 





Allows the selection of the color for the button background. 









color. 




Assign... The Assign... button opens a dialog box to select a variable for the Source field. By default, only 





OK 

Cancel 

Buttons 



Note: 



Warning: 



3.2.4.1.4 Button Touch−Operated Field − Properties: Action 

Determines the action to occur when the touch button is pressed. 

3.2.4.1.4.1 Image 

Key Type 

Determines the action to occur when this touch button is activated. Depending on the selection in 

this list, the appropriate dialog fields are shown displaying possible settings for this action. 

In the following section, related actions are summarized into groups with references to the 

detailed descriptions of these group actions described further down the page. 

Change picture 

Next picture 

Previous picture 

Set USINT 

Set UINT 

Toggle USINT 

Toggle UINT 

Changes pictures when the touch field is activated. 

Detailed description See Change Picture 

Allows the simple, configurable control of an connected process variable 

with respect to its data type. 

Detailed description See Setting and Jogging Process Variables 


Momentary USINT 

Increment/Decrement 

Adjusts a connected process variable by increasing or decreasing the 

value by a preset amount. A process variable can conveniently be adjusted 

in both directions using two such touch fields. 

Detailed description See Increasing and Decreasing Process Variables 

Change Picture 

The actions in this group allow pictures to be changed by pressing the touch field. The following additional 

settings will appear in the dialog box: 

If the current picture is used at the target picture, then it switches to the previous picture during runtime. 

For example, if Pic3 has switched to Pic4 and a picture change to Pic4 is triggered in this same picture (Pic4), 

then it actually switches back to Pic3. This function is especially suitable for help pages since it always switches 

back to the picture where it started from. 

This picture history only stores one picture though. This means that a picture change from Pic3 to itself would 

switch back to Pic4 and not the picture which switched to Pic3 in the first place. 

Key Type 

Target 

Picture 

Defines the action to occur for the touch field. The following actions are described in this section: 

Change Picture Switches the picture to the one specified under Target Picture. Many 

independent touch fields can be configured with this action. 

Next Picture Changes to the next picture which can be set under Target Picture. This picture 

is understood as a global setting for the current picture. In other words, all touch 

fields and function keys of key type Next Picture will always change to the same 

'next picture'. 

Previous Picture Changes to the previous picture which can be set under Target Picture. This 

picture is understood as a global setting for the current picture. This means that 

all touch buttons and function keys of key type Previous Picture will always 

change to the same 'next picture'. 

Specifies the picture to be displayed when this touch field is activated. In the case of the Next Picture 

and Previous Picture settings under Key Type, the respective setting is made for this picture in the 

key list (see above). 





Any picture in the project can be chosen from the list with the exception of 

the current and global picture. 

Setting and Jogging Process Variables 

With the actions in this group, process variables can be set or jogged (only set while the touch field is being 

activated). The following additional settings are offered in the dialog box: 

Key Type Defines the action to occur for the touch field. The following actions are 

described in this section: 

Set USINT The USINT connected process variable is set to the value in field 

Value 1 when the touch field is activated. 

The field is set to the value in Value 1 each time the button is 

activated, but the process variable is not reset when the button 

is released. 

The Value 2 input field is not available for this key type. 

Set UINT The UINT connected process variable is set to the value in field 


Toggle 

USINT 



is released. 


The USINT connected process variable is set to the value in the 

Value 2 field, but only if the process variable currently contains 

the value in the Value 1 field. 

The process variable is set to the value in the Value 1 field in 

every other case. 

If the value is not otherwise changed, then each activation of the 

touch field toggles the value. 


Data Point 

Value 1 

Value 2 

No action occurs during the touch button's released state. 

Toggle UINT The UINT connected process variable is set to the value in the 



Momentary 

USINT 







Value 1 field when the touch field is touched. 

When the touch−operated field is released, the process variable 

is set to the value 0 (predefined). 


The process variable which should be manipulated with this touch field is located 

in the Source field. 

The Assign... button opens a dialog box to select a variable with a suitable data 

type. 

Possible Settings for: 

Set USINT 

Toggle USINT 


Set UINT 

Toggle UINT 

Name of a USINT process 

variable 

Name of a UINT process 

variable 

The value is written to the Data Point process variable using the requirements 

described under Key Type (see above). 


Set USINT 

Toggle USINT 


Set UINT 

Toggle UINT 

0 − 255 

0 − 65535 




Toggle USINT 0 − 255 

Toggle UINT 0 − 65535 

Set USINT 

Set UINT 


No settings possible or 

required. 


Completion Data Point After each operation of the touch field, a process variable of data type UINT can 

additionally be set to a predefined value. This makes requesting and evaluating 

input and operations easier to accomplish in the control application. 

The process variable which should be manipulated after this touch field is 

activated is located in the Source field. 


type. 



Completion Value 


This value is written to the Completion Data Point process variable after each 

operation of the touch field. 

Possible Settings 0 − 65535 

Increasing and Decreasing the Process Variable 

A process variable can be increased or decreased by a predefined amount using the actions described in this 

section. Convenient up/down control of a value can be accomplished using a combination of two such touch 

buttons. Up/Down control is internally limited by the INT16 data type. This means a maximum value of 32,768 

and a minimum value of −32,767 are used for the limits. 

The following additional settings are offered for this key type: 

Key Type 

Data Point 

Completion 

Data Point 

Defines the action to occur for the touch field. The following actions are described in this 

section: 

Increment/Decrement Depending on the set increment (positive or negative), the process 

variable value will be increased or decreased by this amount each time 

the button is activated. 

An automatic iteration can optionally be chosen so that pressing and 

holding the touch field adjusts the value quickly. 

The process variable which should be manipulated with this touch field is located in the Source 

field. 

The Assign... button opens a dialog box to select a variable with a suitable data type. 

Possible Settings Name of a process variable with one of the following data types: USINT, 

SINT, UINT, INT, UDINT, or DINT. 

After each operation of the touch field, a process variable of data type UINT can additionally be 

set to a predefined value. This makes requesting and evaluating input and operations easier to 

accomplish in the control application. 


Completion 

Value 

Use Limits 

Limit Min. 

Limit Max. 

Increment 

Autorepeat 

The process variable which should be manipulated after this touch field is activated is located in 

the Source field. 



This value is written to the Completion Data Point process variable after each operation of the 

touch field. 


This setting defines whether the value range for the connected variable should be limited when 

this touch field is used for input. If this option is enabled, input cannot be adjusted if it were to 

violated the limits set under Limit Min. and Limit Max.. 

However, adjustments can be made if the value is already outside the limits and is being 

adjusted in the direction of the valid value range. Regardless, adjustment takes places using the 

set increment. 

If this option is not selected, the process variable adjustment is limited by its data type. Thus it 

cannot be adjusted beyond the extreme values and jump over the minimum and maximum 

values (or vice versa). 

This setting is only activated if Use Limits is selected. The setting defines the lower limit of the 

allowed adjustment. 

This limit only has an effect when a negative Increment is used. 

Possible Settings Depends on the data type of the connected Data Point, but maximum 

from −32768 to 32767. 

This setting is only activated if Use Limits is selected. The setting defines the upper limit of the 


This limit only has an effect when a positive Increment is used. 


from −32768 to 32767. 

This setting defines the increment which occurs each time the touch field is activated. If the 

increment is positive, then the connected Data Point is increased; if the increment is negative, 

then the connected Data Point is decreased. 


from −32768 to 32767. 

If this option is selected, pressing and holding the touch field will continuously increase or 

reduce the value by the set increment. 

If this option is not selected, only one adjustment of the associated Data Point is caused 

regardless of the length of time the touch button is pressed. 


OK 

Cancel 

Buttons 



Note: 



Warning: 






3.2.4.1.5 Button Touch−Operated Field − Properties: Locking 

Allows the touch field to be locked depending on the current user or password entered. If the touch field is 

locked, then any activation of the field is ignored. Nothing changes in the appearance of the touch field. 

3.2.4.1.5.1 Image 

Activates touch field locking 

Locking 

Active 

Locking 

If selected, the touch field can be locked during runtime. A locked touch field is displayed on the 

touch screen but does not respond when touched. 

Locking concerns the affected touch field, not the connected variable or the linked action. A different 

field on the same page or a panel key can still change a connected process variable or trigger the 

action. 





Source 

Assign... 


Possible Settings Name of a USINT process variable. The same variable can be and 

usually is used as a password level for several input fields and/or 

touch fields. 










selected: 


the value 0. In every other case, the touch field is unlocked. 


< Level 


>= Level 




Password Level field, then the touch field will be unlocked. 




Password Level field, then the touch field will be unlocked. 





OK 

Cancel 

Buttons 



Note: 



Warning: 



3.2.4.2 HotSpot Touch−Operated Field − Reference 

The HotSpot touch−operated field allows invisible surfaces to be configured in a visualization picture. After it is 

set, the button functions like a conventional panel key. The available actions are applied to the area of operation 

on touch screen systems. 

The HotSpot does not possess its own image either in its pressed or released states. Therefore, other elements 

such as bitmaps, rectangles, or circles can brighten and enhance its touch function. 

This touch−operated field is exclusively operated using the touch screen. 

General 


Function Operation of the visualization application using invisible surfaces on the touch screen. 

Actions 

The following actions can be triggered by a a HotSpot: 

Change Picture Changes to another picture in the project. 

Next Picture Changes to the next picture. 

Previous Picture Changes to the previous picture. 

Set USINT Sets a USINT process variable to a defined value. 

Set UINT Sets a UINT process variable to a defined value. 

Toggle USINT Switches a USINT process variable between two values. 

Toggle UINT Switches a UINT process variable between two values. 

Momentary USINT Sets a USINT process variable when activated. 

Increment/Decrement Increases or decreases a process variable incrementally. 


124 3.2.4.2 HotSpot Touch−Operated Field − Reference


Availability 

Special 

Features 

Operator panels with a graphic touch screen (touch screens on QVGA, VGA and larger displays 

with the IPC2001 and IPC5000 families) 


• HotSpots can be analyzed using the key matrix. Jog key operation is possible by setting 

the priority of the key driver (touch driver). 

• Replaces function keys on operator panels with touch screens. 

• Input locking (using the touch−operated field) using the connected Status process 

variable for simple user management. 



from external stations (depending on the configured action). 

Appearance Does not possess its own representation 

Individual 

Colors 

None 

Operation Touching the invisible configured buttons on the touch screen. 

Properties 

The properties of the touch−operated field are set under the various tabs of the properties dialog box. Field 

properties can be displayed by double−clicking on the touch field in the editor and are automatically shown after 

a new field is inserted. 



Parameter 

Action 

Description 

Basic parameters of touch fields such as position, size, connected variable, and status are defined 

under this tab. This page must be configured for all created touch fields. 

Defines the action to be carried out with this button. This setting must be set for each 

touch−operated field of this type. 

Settings for the selected action are also defined under this tab. 

The input of descriptive text for this touch field is possible under this tab. This text is saved in the 

Visual Components project but is not transferred to or processed on the target system. 


3.2.4.2.1 HotSpot Touch−Operated Field − Properties: Parameter 

Provides the general settings for the HotSpot touch field. 

3.2.4.2.1.1 Image 

3.2.4.2 HotSpot Touch−Operated Field − Reference 125

Dimension 

Determines the touch field position and size on the screen. Different touch fields may not overlap in any place. 

Left 

Top 

Width 

Height 




Possible Settings The field can be placed freely in the display, so that Left can be set from 0 to the 





Possible Settings The field can be placed freely in the display, so that Top can be set from 0 to 

the height of the display minus the height of the field in pixels. 

Determines the touch field width in pixels. 

Possible Settings From 1 to the display width. 


Determines the touch field height in pixels. 

Possible Settings From 1 to the display height. 


Key Matrix Offset 

Determines the location of the touch−operated field in the key matrix. This setting is only required if the touch 

field should be queried using the key matrix. No setting is required here for the actions which can be configured 

for the touch field directly in the Visual Components editor. 

Key Matrix 

Offset 


This option defines whether a user defined offset should be defined in the key matrix for this 

element. 

If this option is selected, the HotSpot offset must be defined in the input field. If applicable, the 



Effective 

Index 

offset counts starting with the existing keys of the operator panel which is used. 

Example: 

Panel with 24 keys 

Offset set to 17 

The touch field is located at Index [41] of the key matrix. 

Possible Settings 0 to 255 minus the number of existing keys on the panel. 

(The resulting index may result in 255 at the most) 

Displays the resulting index in the key matrix for informational purposes. This information is only 

shown if Key Matrix Offset is selected. 

Status 


Source 

Assign... 


OK 

Cancel 



Possible Values Bit 1 If 1, no operation of the touch field is permitted. (locked) 




Buttons 



Note: 



Warning: 



3.2.4.2.2 HotSpot Touch−Operated Field − Properties: Action 

Determines the action which occurs when the HotSpot is pressed. 

3.2.4.2.2.1 Image 


Key Type 

Determines the action to occur when this touch button is activated. Depending on the selection in 

this list, the appropriate dialog fields are shown displaying possible settings for this action. 

In the following section, related actions are summarized into groups with references to the 

detailed descriptions of these group actions described further down the page. 

Change picture 

Next picture 

Previous picture 

Set USINT 

Set UINT 

Toggle USINT 

Toggle UINT 


Increment/Decrement 

Changes pictures when the touch field is activated. 

Detailed description See Change Picture 

Allows the simple, configurable control of an connected process variable 

with respect to its data type. 

Detailed description See Setting and Jogging Process Variables 

Adjusts a connected process variable by increasing or decreasing the 

value by a preset amount. A process variable can conveniently be adjusted 

in both directions using two such touch fields. 

Detailed description See Increasing and Decreasing Process Variables 

Change Picture 


The actions in this group allow pictures to be changed by pressing the touch field. The following additional 

settings will appear in the dialog box: 



If the current picture is used at the target picture, then it switches to the previous picture during runtime. 

For example, if Pic3 has switched to Pic4 and a picture change to Pic4 is triggered in this same picture (Pic4), 

then it actually switches back to Pic3. This function is especially suitable for help pages since it always switches 

back to the picture where it started from. 

This picture history only stores one picture though. This means that a picture change from Pic3 to itself would 

switch back to Pic4 and not the picture which switched to Pic3 in the first place. 

Key Type 

Target 

Picture 

Defines the action to occur for the touch field. The following actions are described in this section: 

Change Picture Switches the picture to the one specified under Target Picture. Many 

independent touch fields can be configured with this action. 

Next Picture Changes to the next picture which can be set under Target Picture. This picture 

is understood as a global setting for the current picture. In other words, all touch 

fields and function keys of key type Next Picture will always change to the same 

'next picture'. 

Previous Picture Changes to the previous picture which can be set under Target Picture. This 

picture is understood as a global setting for the current picture. This means that 

all touch buttons and function keys of key type Previous Picture will always 

change to the same 'next picture'. 

Specifies the picture to be displayed when this touch field is activated. In the case of the Next Picture 

and Previous Picture settings under Key Type, the respective setting is made for this picture in the 

key list (see above). 

Possible Settings Any picture in the project can be chosen from the list with the exception of 

the current and global picture. 

Setting and Jogging Process Variables 


With the actions in this group, process variables can be set or jogged (only set while the touch field is being 

activated). The following additional settings are offered in the dialog box: 

Key Type Defines the action to occur for the touch field. The following actions are 

described in this section: 

Set USINT The USINT connected process variable is set to the value in field 




is released. 


Set UINT The UINT connected process variable is set to the value in field 


Toggle 

USINT 




is released. 










Toggle UINT The UINT connected process variable is set to the value in the 





Data Point 

Value 1 

Value 2 


Momentary 

USINT 







Value 1 field when the touch field is touched. 

When the touch−operated field is released, the process variable 

is set to the value 0 (predefined). 


The process variable which should be manipulated with this touch field is located 

in the Source field. 


type. 


Set USINT 

Toggle USINT 


Set UINT 

Toggle UINT 

Name of a USINT process 

variable 

Name of a UINT process 

variable 




Set USINT 

Toggle USINT 


Set UINT 

Toggle UINT 

0 − 255 

0 − 65535 




Toggle USINT 0 − 255 

Toggle UINT 0 − 65535 

Set USINT 

Set UINT 


No settings possible or 

required. 

After each operation of the touch field, a process variable of data type UINT can 

additionally be set to a predefined value. This makes requesting and evaluating 

input and operations easier to accomplish in the control application. 

The process variable which should be manipulated after this touch field is 

activated is located in the Source field. 


type. 


Completion Value This value is written to the Completion Data Point process variable after each 

operation of the touch field. 



Increasing and Decreasing the Process Variable 

A process variable can be increased or decreased by a predefined amount using the actions described in this 

section. Convenient up/down control of a value can be accomplished using a combination of two such touch 

buttons. Up/Down control is internally limited by the INT16 data type. This means a maximum value of 32,768 

and a minimum value of −32,767 are used for the limits. 

The following additional settings are offered for this key type: 

Key Type 

Data Point 

Completion 

Data Point 


Defines the action to occur for the touch field. The following actions are described in this 

section: 

Increment/Decrement Depending on the set increment (positive or negative), the process 

variable value will be increased or decreased by this amount each time 

the button is activated. 

An automatic iteration can optionally be chosen so that pressing and 

holding the touch field adjusts the value quickly. 

The process variable which should be manipulated with this touch field is located in the Source 

field. 


Possible Settings Name of a process variable with one of the following data types: USINT, 

SINT, UINT, INT, UDINT, or DINT. 

After each operation of the touch field, a process variable of data type UINT can additionally be 

set to a predefined value. This makes requesting and evaluating input and operations easier to 

accomplish in the control application. 

The process variable which should be manipulated after this touch field is activated is located in 

the Source field. 




Completion 

Value 

Use Limits 

Limit Min. 

Limit Max. 

Increment 

Autorepeat 


This value is written to the Completion Data Point process variable after each operation of the 

touch field. 


This setting defines whether the value range for the connected variable should be limited when 

this touch field is used for input. If this option is enabled, input cannot be adjusted if it were to 

violated the limits set under Limit Min. and Limit Max.. 

However, adjustments can be made if the value is already outside the limits and is being 

adjusted in the direction of the valid value range. Regardless, adjustment takes places using the 

set increment. 

If this option is not selected, the process variable adjustment is limited by its data type. Thus it 

cannot be adjusted beyond the extreme values and jump over the minimum and maximum 

values (or vice versa). 

This setting is only activated if Use Limits is selected. The setting defines the lower limit of the 


This limit only has an effect when a negative Increment is used. 


from −32768 to 32767. 

This setting is only activated if Use Limits is selected. The setting defines the upper limit of the 


This limit only has an effect when a positive Increment is used. 


from −32768 to 32767. 

This setting defines the increment which occurs each time the touch field is activated. If the 

increment is positive, then the connected Data Point is increased; if the increment is negative, 

then the connected Data Point is decreased. 


from −32768 to 32767. 

If this option is selected, pressing and holding the touch field will continuously increase or 

reduce the value by the set increment. 

If this option is not selected, only one adjustment of the associated Data Point is caused 

regardless of the length of time the touch button is pressed. 


OK 

Cancel 

Buttons 



Note: 



Warning: 




3.3 Programming Interface for Controller Tasks − VISAPI 

The programming interface provides the opportunity to build a bridge between the controller application and the 

Visual Components application. It enables control of the visualization application while it is operating as well as 

output of user−defined graphics from the control application. 

This section provides a brief VISAPI overview which discusses the most important functions used. 

For a more detailed description of each function, click on the respective link. 

The VISAPI − General tutorial should be read before reading descriptions of the individual functions. 

3.3.1 Requirements and Initializing 

VA_Setup 

VA_SetupX 

VA_Saccess, VA_Srelease 

Call Description 

Initializing the 

VISAPI 

Advanced 

Initialization 

General 

Functions 

The VISAPI is initialized with these functions. It is very important that these functions are used correctly. 

Therefore, we recommend reading VISAPI − General Instructions. 

3.3.2 Graphics and Text 


VA_Rect Rectangles 

VA_Line Lines 

VA_Ellipse Ellipses and Circles 

VA_Textout, VA_GetTextByTextGroup Texts 

VA_Redraw, VA_GetDisplayInfo General 

These routines can be used to output general text and graphics. Functions for drawing lines, rectangles, and 

ellipses are available. 

3.3.3 Setting Contrast and Brightness 


VA_SetContrast Contrast 

VA_SetBrightness Brightness 

These functions can be used to change contrast and brightness on the target. 


134 3.3 Programming Interface for Controller Tasks − VISAPI


3.3.4 Reading the Key Matrix 


VA_GetKeyMatrix Reading the Key Matrix 

The VA_GetKeyMatix function allows the current key status to be read. 

See also Key Matrix. 

3.3.5 Touch Screen 


VA_StartTouchCal,VA_GetCalStatus, Example Calibrating the Touch Screen 

VA_GetTouchAction User−Defined Touch Operation 

Everything applying to touch. Reads status and calibration. 

3.3.6 Manual Project Control 


VA_StartProject Starting Projects 

VA_StopProject Stopping Projects 

VA_SetUserParam User−Defined Project Settings 

In some cases, it is necessary to stop a running project or change the start parameter for individual drivers. 

These things can all be managed using these functions. 

3.3.7 Reading Alarm Lists 


VA_GetAlarmList Reading Historical Alarm Lists 

VA_GetExAlarmList Reading the Extended Historical Alarm List 

VA_GetActAlarmList Reading the Current Extended Alarm List 

VA_DelAlarmHistory Deleting the Alarm History 

These functions are used to access current alarm lists. 

3.3.8 Palettes 


VA_SetPaletteColor Setting Palette Color 

3.3.4 Reading the Key Matrix 135

VA_GetPaletteColor Retrieving Palette Color 

IPC Colors IPC Color Display Palette 

SG3 Colors SG3 Black and White Palette 

An overview of available colors can be found here. 

3.3.8.1 Copying a Rectangular Screen Area − VA_CopyScreenRect 

The VA_CopyScreenRect function copies a rectangular screen area (x1, y1, x2, y2) by dx pixels horizontally and 

dy pixels vertically. 

Note: 

This function is only available on VGA displays. 

3.3.8.1.1 Parameter 

I/O Parameter Type Meaning 

IN enable BOOL This function is only executed if enable is TRUE. 

IN VCHandle UDINT The handle returned by VA_Setup. 

IN x1/y1 UINT Coordinates of the upper left corner of the rectangle 

IN x2/y2 UINT The width and height of the rectangle to be copied 

IN dx/dy INT Number of pixels in the X and Y directions in which the rectangle should be copied. 

OUT Return Value UINT Not equal to 0 if error occurs 

3.3.8.1.2 Example for Automation Basic 

(* cyclic program *) 

x1 = 100 

y1 = 150 

x2 = 250 

y2 = 150 

dx = 10 

dy = 10 

if ready 1 then 

VC_HANDLE = VA_Setup(1 "vga") , 

VC_HANDLE if 0 then 

ready = 1 

endif 

endif 

if ready = 1 then 

VA_Saccess(1,VC_HANDLE)= if 

0 then 

VA_CopyScreenRect (1,VC_HANDLE,x1,y1, 

width,height,dx,dy) 

VA_Srelease(1,VC_HANDLE) 

endif 

endif 

3.3.8.1.3 Example for C Programming 

#include 

#include 

#include 

UINT _GLOBAL ready; 

unsigned long VC_HANDLE; 

UINT _GLOBAL x1; 

UINT _GLOBAL width; 

UINT _GLOBAL y1; 

UINT _GLOBAL height; 

SINT _GLOBAL dx; 

SINT _GLOBAL dy; 

_CYCLIC void Cyclic (void) 

{ 


136 3.3.8.1 Copying a Rectangular Screen Area − VA_CopyScreenRect


x1 = 150; 

y1 = 100; 

x2 = 100; 

y2 = 150; 

dx = 10; 

dy = 10; 

if (!ready) 

{ 

VC_HANDLE = VA_Setup(1 "vga"); , 

if (VC_HANDLE) 

ready = 1; 

} 

if (ready) 

{ 

if (!VA_Saccess(1,VC_HANDLE)) 

{ 

VA_CopyScreenRect width,heighty2,dx,dy); 

(1,VC_HANDLE,x1,y1, 

VA_Srelease(1,VC_HANDLE); 

} 

} 

} 

3.3.8.2 Displaying a Bitmap − VA_DrawBitmap 

The VA_DrawBitmap function draws a bitmap at the specified coordinates on the screen. This bitmap must exist 

and be used in the project. 

Note: 

This function is only available on VGA displays. 





IN index UINT Bitmap index in the project (must be used in the project). 

IN x UINT X coordinate of the upper left corner of the bitmap. 

IN y UINT Y coordinate of the upper left corner of the bitmap. 




x = 100 

y = 150 

index = 1 



if VC_HANDLE 0 then 

ready = 1 

endif 

endif 


if VA_Saccess(1,VC_HANDLE)= 0 then 

VA_DrawBitmap (1,VC_HANDLE,index,x,y) 


endif 

endif 


#include 

#include 

#include 

3.3.8.2 Displaying a Bitmap − VA_DrawBitmap 137



UINT _GLOBAL x; 

UINT _GLOBAL y; 

UINT _GLOBAL index; 


{ 

x = 150; 

y = 100; 

index = 1; 

if (!ready) 

{ 



ready = 1; 

} 

if (ready) 

{ 


{ 

VA_DrawBitmap (1,VC_HANDLE,index,x,y); 


} 

} 

} 

3.3.8.3 Deleting the Alarm History − VA_DelAlarmHistory 

The VA_DelAlarmHistory function deletes both the data object alarm as 

well as all alarms in the runtime history. 









VC_HANDLE = VA_Setup(1 "visu") , 


ready = 1 

endif 

endif 



0 then 

if del = 1 then 

status = VA_DelAlarmHistory(1,VC_HANDLE) 

del = 0; 

endif 


endif 

endif 


#include 

#include 

#include 


UINT _GLOBAL status; 


138 3.3.8.3 Deleting the Alarm History − VA_DelAlarmHistory


BOOL _GLOBAL del; 


_CYCLIC void Cyclic(void) 

{ 

if (!ready) 

{ 

VC_HANDLE = VA_Setup(1 , "visu"); 


ready = 1; 

} 

if (ready) 

{ 


{ 

if (del) 

{ 

status = VA_DelAlarmHistory(1,VC_HANDLE); 

del = 0; 

} 


} 

} 

} 

3.3.8.4 Graphics and Text Output − VA_Ellipse 

Draws an ellipse or circle. 

Note: 

This function is not supported on the PP41. 





IN x/y UINT Coordinates for the center of the ellipse 

IN height UINT Height of the ellipse in pixels 

IN width UINT Width of the ellipse in pixels 

IN fill UINT Ellipse fill color 

IN color UINT Ellipse border color 




x = 100 

y = 150 

height = 30 

width = 60 

fill = 255 

color = 0 

; Transparent 

; Black 




ready = 1 

endif 

endif 



0 then 

VA_Ellipse (1,VC_HANDLE,x,y,heigth,width,fill,color) 

endif 


3.3.8.4 Graphics and Text Output − VA_Ellipse 139

endif 


#include 

#include 

#include 



UINT _GLOBAL x; 

UINT _GLOBAL y; 

UINT _GLOBAL fill; 

UINT _GLOBAL color; 

UINT _GLOBAL width; 

UINT _GLOBAL height; 


{ 

x = 150; 

y = 100; 

height = 30; 

width = 60; 

fill = /* 255; Transparent */ 

color /* = 0; Black */ 

if (!ready) 

{ 



ready = 1; 

} 

if (ready) 

{ 


{ 

VA_Ellipse (1,VC_HANDLE,x,y,height,width,fill,color); 


} 

} 

} 

3.3.8.5 VA_ExchangeFont 

The VA_ExchangeFont function is only used internally. 

3.3.8.6 Read Current Alarm List − VA_GetActAlarmList 

All queued alarms can be read with the the VA_GetActAlarmList function. This function returns all alarms as 

they are output in the alarm list. This is also dependent on the alarm configuration (acknowledgement 

necessary, acknowledgement possible, etc., see Creating and Configuring Alarms). 

The VA_Setup function must also be called once for alarm system functions, and VA_Saccess must be 

executed before each use of VISAPI alarm functions. 

Important: 

After receiving the status value 240 (end of list), VA_GetActAlarmList can no longer be called when the value of 

iFunction is 2 (read next alarm). Otherwise, values will be read which no longer concern the alarm list. If the 

value 240 is returned to the status variable, the value of iFunction has to be 1 the next time the function is 

called. 






140 3.3.8.4 Graphics and Text Output − VA_Ellipse


IN pcAlarmLine DINT Text array to be used as the alarm line 

IN plLen DINT 

IN iFunction UINT 

Address of a DINT variable which contains the length of the text field. 

After the function is called, this variable is set to the actual length. 

1 ..... Read first current alarm 

2 ..... Read next current alarm 

IN cSeperator USINT Separation character to be inserted into the alarm line 

IN cDateTimeFormat USINT 

Desired format for date and time output in the alarm list 

0 ... DD.MM.YY_HH:MM:SS 

1 ... DD.MM.YY_HH:MM:SSa 

2 ... HH_MM_SS 

3 ... HH_MM_SSa 

4 ... HH_MM 

5 ... HH_MMa 

6 ... NO_TIME_NO_DATE 




VC_HANDLE = VA_Setup(1, "Compact") 


ready = 1 

endif 

else 

Access_Status = VA_Saccess (1,VC_HANDLE) 

if Access_Status = 0 then 

case step of 

action 1: 

Alarmlen = 80 

;Hyphen Seperator = 45 

;Read first Alarmtype alarm = 1 

;DD.MM.YY TimeDateForm HH.MM.SS = 0 

GetActAL_Status = VA_GetActAlarmList UDINT(ADR(Alarmstring)),UDINT(ADR(Alarmlen)),Alarmtype,Sepe 

(1,VC_HANDLE, 

if GetActAL_Status = 0 then 

step = 2 

endif 

endaction 

2: action 

Alarmlen = 80 

;Hyphen Seperator = 45 

;Read next Alarmtype alarm = 2 

;DD.MM.YY TimeDateForm HH.MM.SS = 0 

GetActAL_Status = VA_GetActAlarmList UDINT(ADR(Alarmstring)),UDINT(ADR(Alarmlen)),Alarmtype,Sepe 

(1,VC_HANDLE, 

if GetActAL_Status = 240 then 

step = 1 

endif 

endaction 

endcase 


endif 

endif 


#include 

#include 

#include 

_GLOBAL USINT ready; 

_GLOBAL UDINT VC_HANDLE; 

_LOCAL UINT Access_Status, GetActAlarmList_Status; 

_LOCAL char AlarmString[80]; 

_LOCAL UINT Alarmlen; 

_LOCAL USINT Seperator,step; 

_LOCAL USINT TimeDateForm; 

_LOCAL USINT Alarmtype; 

3.3.8.6 Read Current Alarm List − VA_GetActAlarmList 141

void _CYCLIC test( void ) 

{ 

if (ready == 0) 

{ 

VC_HANDLE = VA_Setup (1,"Compact"); 

if (VC_HANDLE != 0) 

ready = 1; 

} 

else 

{ 

Access_Status = VA_Saccess (1,VC_HANDLE); 

if (Access_Status == 0) 

{ switch (step) 

{ 

case 1: 

{ 

Alarmlen = 80; 

Seperator = 45; /*Hyphen*/ 

Alarmtype /*First alarm*/ = 1; 

TimeDateForm /*DD.MM.YY = 1; HH.MM.SS*/ 

GetActAlarmList_Status = VA_GetActAlarmList (1, unsigned VC_HANDLE, int)AlarmString,(unsigned ( 

int) &Alarmlen 

,Alarmtype,Seperator,TimeDateForm); 

if (GetActAlarmList_Status == 0) 

step = 2; 

break; 

} 

case 2: 

{ 

Alarmlen = 80; 

Seperator = /*Hyphen*/ 

45; 

Alarmtype = /*First 2; alarm*/ 

TimeDateForm /*DD.MM.YY = 1; HH.MM.SS*/ 

GetActAlarmList_Status = VA_GetActAlarmList (1, unsigned VC_HANDLE, int)AlarmString,(unsigned ( 

int) &Alarmlen 

if (GetActAlarmList_Status == 240) 

step = 1; 

break; 

} 

}/*step switch*/ 

VA_Srelease (1,VC_HANDLE); 

}/*VA_Saccess == 0*/ 

}/*Visapi initialized, ready != 0*/ 

}/* end cyclic*/ 

3.3.8.7 Reading Alarm Lists − VA_GetAlarmList 

,Alarmtype,Seperator,TimeDateForm); 

Two functions can be used to read the alarm history VA_GetAlarmList and VA_GetExAlarmList. Both 

functions return a result string which must then be evaluated. 

It is important to call VA_Setup once before alarm system functions are called and to execute VA_Saccess 

before each use of Visapi alarm functions. 

To format the alarm line, the function VA_GetExAlarmList can be used. 






IN plLen DINT 




1 ..... Read first alarm 

2 ..... Read next alarm 

4 ..... Read previous alarm 

8 ..... Read last alarm 


142 3.3.8.7 Reading Alarm Lists − VA_GetAlarmList





VC_HANDLE = VA_Setup(1, "vga") 


ready = 1 

endif 

else 



;Alarm Alarmlen string = 80 length 

Alarmtype = 1 ;Read first alarm 

endif 

endif 


#include 

#include 

#include 

GetAL_Status = VA_GetAlarmList UDINT(ADR(Alarmstring)),UDINT(ADR(Alarmlen)),Alarmtype) 

(1,VC_HANDLE, 

VA_Srelease (1,VC_HANDLE) 


STRING _GLOBAL pcAlarmline[80]; 

DINT _GLOBAL lLen; 

UINT _GLOBAL iFunction; 



{ 

if (!ready) 

{ 



ready = 1; 

} 

if (ready) 

{ 


{ 

lLen = 80; 

iFunction = 1; 

VA_GetAlarmList( 

1,VC_HANDLE, (DINT) pcAlarmline, (DINT) &lLen,iFunction); 


} 

} 

} 

3.3.8.8 Alarm Information at the Cursor Position − VA_GetAlCurPos 

The VA_GetAlCurPos ascertains the group and alarm numbers of an alarm entry at the current cursor position 

in an alarm list. 





IN pGroupNumber USINT Group number of the alarm entry at the current cursor position. 

IN pAlarmNumber USINT Alarm number of the alarm entry at the current cursor position. 


3.3.8.7 Reading Alarm Lists − VA_GetAlarmList 143






ready = 1 

endif 

endif 



0 then 

VA_GetAlCurPos(1,VC_HANDLE, 

adr(Groupnumber),adr(Alarmnumber)) 


endif 

endif 


#include 

#include 

#include 


DINT _GLOBAL Groupnumber; 

DINT _GLOBAL Alarmnumber; 



{ 

if (!ready) 

{ 



ready = 1; 

} 

if (ready) 

{ 


{ 

1,VC_HANDLE, VA_GetAlCurPos( 

(DINT) &Groupnumber, (DINT) &Alarmnumber); 


} 

} 

} 

3.3.8.9 Touch Screen Calibration − VA_GetCalStatus 

VA_GetCalStatus can be used to inquire whether calibration already took place with the VA_StartTouchCal 

function and whether it was completed successfully. 





OUT Return Value UINT 






ready = 1 

0 ................. Touch screen was successfully calibrated 

0xFFFF ......... A general error occurred 

All others ...... Calibration still active. 


144 3.3.8.8 Alarm Information at the Cursor Position − VA_GetAlCurPos


endif 

endif 



0 then 

status = VA_GetCalStatus (1,VC_HANDLE) 


endif 

endif 


#include 

#include 

#include 



UDINT _GLOBAL status; 

_CYCLIC void Initialization (void) 

{ 

if (!ready) 

{ 



ready = 1; 

} 

if (ready) 

{ 


{ 

status = VA_GetCalStatus (1,VC_HANDLE); 


} 

} 

} 

3.3.8.9.4 Example of a complete touch calibration program 

#include 

#include 

#include 

_GLOBAL UINT stat,CalibStatus; 

_GLOBAL UINT calib; 

_GLOBAL UDINT VCHandle; 

_GLOBAL UINT MeinStatus; 

_INIT void init(void) 

{ 

calib = 0; 

MeinStatus = 0; 

VCHandle=0; 

} 

_CYCLIC void Touchcalib(void) 

{ 

if (!VCHandle) 

{ 

} 

else 

{ 

VCHandle = VA_Setup(1, "vis2"); 

calib = 0; 

MeinStatus = 0; 

switch (calib) 

{ 

case 0: /* Touch is calibrated */ break; 

case 1: calib = 2;break; 

case 2: 

if (!VA_Saccess(1,VCHandle)) 

{ 

CalibStatus=VA_StartTouchCal(1, VCHandle); 

3.3.8.9 Touch Screen Calibration − VA_GetCalStatus 145

eak; 

} 

case 3: 

(!VA_Saccess(1,VCHandle)) if 

{ 

/*Touch Calib OK*/ 

if (MeinStatus == 0) 

break; 

} 

/*VC HAndle } !=0*/ 

} 

} 

VA_Srelease(1,VCHandle); 

calib = 3; 

MeinStatus = VA_GetCalStatus(1, VCHandle); 

VA_Srelease(1,VCHandle); 

calib = 0; 

3.3.8.10 Determining Contrast − VA_GetContrast 

The VA_GetContrast function returns the set contrast value of the display (0−100). 

Note: 

This function is only available on the PP41. 





OUT Return Value UINT Set contrast value of the display.. 






ready = 1 

endif 

endif 



0 then 

endif 


#include 

#include 

#include 


UINT _GLOBAL Contrast; 


Contrast = VA_GetContrast(1,VC_HANDLE) 


endif 


{ 

if (!ready) 

{ 



ready = 1; 

} 

if (ready) 

{ 



146 3.3.8.10 Determining Contrast − VA_GetContrast


} 

} 

{ 

} 

Contrast 1,VC_HANDLE); = VA_GetContrast( 


3.3.8.11 Reading Display Information − VA_GetDisplayInfo 

This function can be used to query information such as: max. X pixel, max. Y pixel, and the number of bits per 

pixel. 

Note: 

This function can only be used on IPCs and is not supported on SG3 targets. 





IN InfoType UDINT 

Index of the value to be queried 

1 − Number of pixels in the X direction 

2 − Number of pixels in the Y direction 

3 − Number of bits per pixel 

IN Value UDINT Return value of the queried info type 






ready = 1 

endif 

endif 



0 then 

endif 

VA_GetDisplayInfo (1,VC_HANDLE,InfoType, 

UDINT(adr(Value))) 


endif 


#include 

#include 

#include 


UDINT _GLOBAL InfoType; 

UDINT _GLOBAL Value 



{ 

if (!ready) 

{ 



ready = 1; 

} 

if (ready) 

{ 


{ 

VA_GetDisplayInfo(1,VC_HANDLE,InfoType,&Value 

); 

3.3.8.11 Reading Display Information − VA_GetDisplayInfo 147


} 

} 

} 

3.3.8.12 Reading Alarm Lists − VA_GetExAlarmList 

Two functions can be used to read the alarm history VA_GetAlarmList and VA_GetExAlarmList. Both 

functions return a result string which then must be evaluated. 

It is important to call VA_Setup once before alarm system functions are called and to execute VA_Saccess 

before each use of Visapi alarm functions. 






IN plLen DINT 




1 ..... Read first alarm 

2 ..... Read next alarm 

4 ..... Read previous alarm 

8 ..... Read last alarm 

IN cSeperator USINT Separation character to be inserted into the alarm line 

IN cDateTimeFormat USINT 

Desired format for date and time output in the alarm list 

0 ... DD.MM.YY_HH:MM:SS 

1 ... DD.MM.YY_HH:MM:SSa 

2 ... HH_MM_SS 

3 ... HH_MM_SSa 

4 ... HH_MM 

5 ... HH_MMa 

6 ... NO_TIME_NO_DATE 






ready = 1 

endif 

else 



endif 

endif 

Alarmlen = 80 

Seperator = ;Hyphen 45 

;Read Alarmtype first alarm = 1 

TimeDateForm ;DD.MM.YY = 0 HH.MM.SS 


#include 

#include 

#include 

GetExAL_Status = VA_GetExAlarmList UDINT(ADR(Alarmstring)),UDINT(ADR(Alarmlen)),Alarmtype,Seperato 

(1,VC_HANDLE, 



STRING _GLOBAL pcAlarmline[80]; 

DINT _GLOBAL lLen; 


148 3.3.8.12 Reading Alarm Lists − VA_GetExAlarmList


UINT _GLOBAL iFunction; 

USINT _GLOBAL cSeperator; 

USINT _GLOBAL cDateTimeFormat; 



{ 

if (!ready) 

{ 



ready = 1; 

} 

if (ready) 

{ 


{ 

lLen = 80; 

cSeperator = ' '; 

cDateTimeFormat = 0; 

iFunction = 1; 

} 

} 

} 

1,VC_HANDLE, VA_GetExAlarmList( 

(DINT) pcAlarmline, (DINT) &lLen, iFunction, cSeperator, cDateTimeFormat); 


3.3.8.13 Reading the Key Matrix − VA_GetKeyMatrix 

The VA_GetKeyMatrix function returns information about whether and which keys on a target system are 

currently being pressed. 





IN KeyMatrix UDINT Start address of the key address array 

IN KeysToRead UDINT Number of keys to be read 

IN KeysRead UDINT Number of keys read 



See also Reading the Matrix 

3.3.8.14 Querying the Palette Color − VA_GetPaletteColor 

Using VA_GetPaletteColor, it is possible to dynamically query each individual color value. Naturally, this is only 

possible on an IPC (color or black/white display). 





IN index UINT Index of the color which should be retrieved (0−255). 

OUT Return Value UDINT 

Color. The color value is arranged as follows: 

Bits 0 .. 8 Red value (0−255) 

Bits 8 .. 16 Green value (0−255) 

Bits 16 .. 24 Blue value (0−255) 

Bits 24 .. 32 0 

3.3.8.13 Reading the Key Matrix − VA_GetKeyMatrix 149



color = 0 ; Black 




ready = 1 

endif 

endif 



color = VA_GetPaletteColor(1,VC_HANDLE,0) 


endif 

endif 


#include 

#include 

#include 



UDINT _GLOBAL color; 



{ 

color /* = Black 0; */ 

if (!ready) 

{ 



ready = 1; 

} 

if (ready) 

{ 


{ 

color = VA_GetPaletteColor(1,VC_HANDLE,0); 


} 

} 

} 

3.3.8.15 Graphics and Text Output − VA_GetTextByTextGroup 

An individual line can be read from text groups with the VA_GetTextByTextGroup command. 





IN TG_id USINT ID number of the text group to be read. 

IN TGT_id USINT ID number of the line to be read in the text group. 

IN pcText UDINT Text which is read (STRING) 

IN pcTextlength UDINT Length of the STRING to be read 



150 3.3.8.14 Querying the Palette Color − VA_GetPaletteColor


Important: 

Text groups must be on the target if they are to be read. The pcTextlength variable has to transfer a string 

length. If the read length is smaller than the value input, then the actual length of the string is displayed. 




VC_HANDLE = VA_Setup(1,"visu") 


ready = 1 

endif 

else 



pcTextlength = 70 

if (ReadingText = 1) then 

ReadingText = 0 

status = VA_GetTextByTextGroup(1,VC_HANDLE,TG_id,TGT_id, 

UDINT(ADR(pcText)),UDINT(ADR(pcTextlength))) 

endif 

endif 

endif 



#include 

#include 

#include 


_GLOBAL USINT ready; 

_GLOBAL USINT TG_id; 

_GLOBAL USINT TGT_id; 

_GLOBAL STRING pcText[80]; 

_GLOBAL UDINT pcTextlength; 

_GLOBAL UINT status; 


{ 

if (!ready) 

{ 

VC_HANDLE = VA_Setup(1 , "vga"); 


ready = 1; 

} 

if (ready) 

{ 


{ 

status = VA_GetTextByTextGroup(1,VC_HANDLE,TG_id,TGT_id,(UDINT)pcText,(UDINT)&pcTextlength); 


} 

} 

} 

3.3.8.16 User−Defined Touch Operation − VA_GetTouchAction 

The VA_GetTouchAction function can be used to retrieve the location of the current touch position, as well as 

the touch status (pressed/released). 





IN type UDINT Retrieval type. 

0 ... Processed 

1 ... REALTIME 

3.3.8.15 Graphics and Text Output − VA_GetTextByTextGroup 151

REALTIME means that each touch action can be queried in real−time. 

Processed means that touch actions (i.e. with opened touch input) do not get 

through. 

IN status UDINT Address of a TouchAction structure. This will be described further down the page. 


3.3.8.16.2 TouchAction structure 

Variable Meaning 

x The last pressed X position 

y The last pressed Y position 

status 

1 ... pressed 

2 ... released 

The TouchAction structure records the current touch status. 






ready = 1 

endif 

endif 



endif 

VA_GetTouchAction (1,0, UDINT(adr(touch))) 

VC_HANDLE, 

x_position = touch.x 

y_position = touch.y 

touch_status = touch.status 


endif 


#include 

#include 

#include 


TouchAction _GLOBAL touch; 

UDINT _GLOBAL x_position; 

UDINT _GLOBAL y_position; 

UDINT _GLOBAL touch_status; 



{ 

if (!ready) 

{ 



ready = 1; 

} 


152 3.3.8.16 User−Defined Touch Operation − VA_GetTouchAction


if (ready) 

{ 


{ 

x_position = touch.x; 

} 

} 

} 

3.3.8.17 VA_Invblnk 

VA_GetTouchAction (1,VC_HANDLE, 0, &touch); 


y_position = touch.y; 

touch_status = touch.status; 

The VA_Invblnk function is only used internally. 

3.3.8.18 Graphics and Text Output − VA_Line 

Drawing a line takes place with the VA_Line command. 





IN x1/y1 UINT Coordinates of the upper left edge of the line 

IN x2/y2 UINT Coordinates of the lower right edge of the line 

IN color UINT Color of the line 




x1 = 100 

y1 = 150 

x2 = 300 

y2 = 350 





ready = 1 

endif 

endif 



0 then 

VA_Line (1,VC_HANDLE,x1,y1,x2,y2,color) 

endif 

endif 



#include 

#include 

#include 






3.3.8.17 VA_Invblnk 153




{ 

x1 = 150; 

y1 = 100; 

x2 = 100; 

y2 = 150; 

color /* = Black 0; */ 

if (!ready) 

{ 



ready = 1; 

} 

if (ready) 

{ 


{ 

VA_Line (1,VC_HANDLE,x1,y1,x2,y2,color); 


} 

} 

} 

3.3.8.19 Acknowledging Alarms from a Certain Group − VA_QuitAlarms 

Using the VA_QuitAlarms function, alarms can be acknowledged from a certain group which triggers the group 

alarms. All alarms are acknowledged if group number 65536 (0xffff) is specified. 




IN VCHandle UDINT The handle returned by VA_Setup 

IN GroupNumber UINT Group number which should be acknowledged 







ready = 1 

endif 

endif 



0 then 

endif 


#include 

#include 

#include 


UINT _GLOBAL Groupnumber; 



VA_QuitAlarms(1,VC_HANDLE, Groupnumber) 


endif 


154 3.3.8.19 Acknowledging Alarms from a Certain Group − VA_QuitAlarms


{ 

if (!ready) 

{ 



ready = 1; 

} 

if (ready) 

{ 


{ 

1, VC_HANDLE, VA_QuitAlarms( 

Groupnumber); 


} 

} 

} 

3.3.8.20 Graphics and Text Output − VA_Rect 

A rectangle is drawn with the VA_Rect command. 





IN x1/y1 UINT Coordinates of the upper left corner of the rectangle 

IN width/height UINT Width and height of the rectangle 

IN fill UINT Filling color of the rectangle 

IN color UINT Border color of the rectangle 


VGA: 

If fill == 255, then an empty rectangle is drawn. Otherwise, it is filled with the color in fill. 

PP41: 

If fill == 0, then an empty rectangle is drawn. Otherwise, it is filled with the color in fill. 

On the PP41, a rectangle can be deleted by setting color and fill to 0. 

3.3.8.20.2 

Example for Automation Basic 


x1 = 100 

y1 = 150 

x2 = 250 

y2 = 150 

fill = 255 ; Transparent 





ready = 1 

endif 

endif 



0 then 

VA_Rect (1,VC_HANDLE,x1,y1,x2,y2,fill,color) 


endif 

endif 

3.3.8.20 Graphics and Text Output − VA_Rect 155


#include 

#include 

#include 










{ 

x1 = 150; 

y1 = 100; 

x2 = 100; 

y2 = 150; 

fill = /* 255; Transparent */ 

color /* = 0; Black */ 

if (!ready) 

{ 



ready = 1; 

} 

if (ready) 

{ 


{ 

VA_Rect (1,VC_HANDLE,x1,y1,x2,y2,fill,color); 


} 

} 

} 

3.3.8.21 Graphics and Text Output − VA_Redraw 

The VA_Redraw function clears all VISAPI output and 

then redraws the picture. 






Warning: 

This function works asynchronously. This means that in some circumstances, subsequent Visapi functions (i.e. 

VA_Rect, etc.) are not drawn. 

In this case, the subsequent functions have already been executed before the VA_Redraw function is finished. 

If the VA_Redraw function now finishes (afterward), then all drawing functions which had been carried out after 

this function was called are erased. 






ready = 1 

endif 


156 3.3.8.20 Graphics and Text Output − VA_Rect


endif 



0 then 

VA_Redraw (1,VC_HANDLE) 


endif 

endif 


#include 

#include 

#include 




{ 

if (!ready) 

{ 



ready = 1; 

} 

if (ready) 

{ 


{ 


} 

} 

} 

VA_Redraw (1,VC_HANDLE); 

3.3.8.22 Requirements and Initialization − VA_Saccess 

This is one of the most important functions in the VISAPI. VA_Saccess makes it possible to carry out drawing 

operations. 

Drawing is ONLY possible if this function returns ERR_OK. This means that this function has to be called before 

any drawing commands. If ERROR_BUSY is returned, the VA_Saccess function must be called again in the 

next cycle. This occurs until ERR_OK is returned. 

Important: 

No VISAPI function can be used until VA_Saccess(...) returns ERR_OK. 

After that, any number of VISAPI functions can be executed. After all of this, VA_Srelease must be called in 

each case. 

The following rules must absolutely be followed: 

• Drawing functions can only be written between a VA_Saccess and VA_Srelease block 

• VA_Srelease should only be called if VA_Saccess returned ERR_OK. 










3.3.8.21 Graphics and Text Output − VA_Redraw 157


ready = 1 

endif 

endif 



.... 

.... 

endif 

endif 


#include 

#include 

#include 




{ 

if (!ready) 

{ 



ready = 1; 

} 

if (ready) 

{ 


{ 

.... 

.... 

} 

} 

} 

Here are some typical errors associated with VA_Saccess and VA_Srelease: 

• VA_Saccess(1, VC_HANDLE); 

VA_Line(1,VC_HANDLE, 10, 10, 100, 100, 1); 


This is incorrect! VA_Srelease is called even if VA_Saccess fails. 

• ... 

... 

if (VA_Saccess(1,VC_HANDLE) == ERR_OK) 

{ 


} 

... 

... 

This is incorrect! VA_Srelease has been left out. 

• CYCLIC void test(void) 

{ 


} 

This is incorrect! VA_Saccess hasn't been called here. 


158 3.3.8.22 Requirements and Initialization − VA_Saccess


3.3.8.23 Saving Settings − VA_SaveSettings 

Used to store contrast and brightness settings on the PP100. 





IN uiAction UINT 1...Store 

2...Check whether storing is active 

OUT Return Value UINT 1 = Storing is currently running, 0 = Store successful, >= 1 Error 






ready = 1 

endif 

endif 



if StartSaving=1 then 

Status=VA_SaveSettings (1,VC_HANDLE,2) 

if Status=0 then 

Status=VA_SaveSettings(1,VC_HANDLE,1) 

StartSaving=0 

endif 

endif 


endif 

endif 


#include 

#include 

#include 



UINT _GLOBAL Status; 

BOOL _GLOBAL StartSaving; 


{ 

if (!ready) 

{ 



ready = 1; 

} 

if (ready) 

{ 


{ 

if (StartSaving) 

{ 

Status=VA_SaveSettings (1,VC_HANDLE,2); 

if(!Status) 

{ 

Status=VA_SaveSettings (1,VC_HANDLE,1); 

StartSaving=0; 

} 

} 


} 

} 

3.3.8.23 Saving Settings − VA_SaveSettings 159

} 

3.3.8.24 Disable − enable backlight − VA_SetBacklight 

The backlight can be enable and disable by the function VA_SetBacklight. 


I/O Parameter Type Bedeutung 



IN blnState BOOL 

Disable − enable backlight 

000disable 

10 enabel 

OUT Rückgabewert UINT Not equal to 0 if error occursl 




VC_HANDLE = VA_Setup(1,"visu") 


ready = 1 

endif 

endif 



VA_SetBacklight(1,VC_HANDLE,blnState) 


endif 

endif 


#include 

#include 

#include 


BOOL _GLOBAL blnState; 


_CYCLIC void Zyklisch(void) 

{ 

if (!ready) 

{ 

VC_HANDLE = VA_Setup(1 "visu"); , 


ready = 1; 

} 

if (ready) 

{ 


{ 

Backlight(1,VC_HANDLE,blnState); 

VA_Set 


} 

} 

} 

3.3.8.25 Setting Contrast and Brightness − VA_SetBrightness 


The brightness of a PP can be set with the VA_SetBrightness function. This function is available on TFT and 

LCD displays. 

160 3.3.8.24 Disable − enable backlight − VA_SetBacklight






IN percent UDINT 

Brightness intensity 

000 dark 

500 standard 

100 light 







ready = 1 

endif 

endif 



0 then 

endif 


#include 

#include 

#include 


UDINT _GLOBAL percent; 


VA_SetBrightness(1,VC_HANDLE,percent) 


endif 


{ 

if (!ready) 

{ 



ready = 1; 

} 

if (ready) 

{ 


{ 

VA_SetBrightness(1,VC_HANDLE,percent); 


} 

} 

} 

3.3.8.26 Setting Contrast and Brightness − VA_SetContrast 

PP contrast can be set with the VA_SetContrast function. 

Note: 

This function is only available on LCD Displays. 




3.3.8.25 Setting Contrast and Brightness − VA_SetBrightness 161


IN percent UDINT 

Contrast intensity 

000 dark 

500 standard 

100 light 







ready = 1 

endif 

endif 



0 then 

endif 


#include 

#include 

#include 


UDINT _GLOBAL percent; 


VA_SetContrast(1,VC_HANDLE,percent) 


endif 


{ 

if (!ready) 

{ 



ready = 1; 

} 

if (ready) 

{ 


{ 

VA_SetContrast(1,VC_HANDLE,percent); 


} 

} 

} 

3.3.8.26.4 Example: Setting Contrast/Brightness 

#include 


#include #include #define VC_SETUP 0 #define VC_WAIT 10 

#define VC_SETCONTRAST 30 #define VC_SETBRIGHTNESS 40 _GLOBAL UDINT VC_Handle; _LOCAL UINT Step, 

ContrastValue, OldContrastValue, BrightnessValue, OldBrightnessValue; _INIT void Init_Routine(void) 

{ VC_Handle=0; if (ContrastValue == 0) ContrastValue = 60; else if (BrightnessValue==0) 

BrightnessValue=60; Step = VC_SETUP; } _CYCLIC void Cyclic_Routine(void) { switch (Step) { case 

VC_SETUP: VC_Handle = VA_Setup(1, "visu"); if (VC_Handle != 0) Step = VC_WAIT; break; case VC_WAIT: if 

(ContrastValue != OldContrastValue) { OldContrastValue = ContrastValue; Step = VC_SETCONTRAST; } if 

(BrightnessValue != OldBrightnessValue) { OldBrightnessValue=BrightnessValue; Step= 

VC_SETBRIGHTNESS; } break; case VC_SETCONTRAST: if (!VA_Saccess(1,VC_Handle)) { 

VA_SetContrast(1,VC_Handle,ContrastValue); VA_Srelease(1,VC_Handle); } Step = VC_WAIT; break; case 

VC_SETBRIGHTNESS: if (!VA_Saccess(1,VC_Handle)) { VA_SetBrightness(1,VC_Handle,BrightnessValue); 

VA_Srelease(1,VC_Handle); } Step = VC_WAIT; break; } } 

162 3.3.8.26 Setting Contrast and Brightness − VA_SetContrast


3.3.8.27 Setting the Palette Color − VA_SetPaletteColor 

It is possible to dynamically change color values for each individual color using the VA_SetPaletteColor function. 

Naturally, this is only possible on an IPC (color or black/white display). 

If a palette color is changed, it will remain so until it is either changed again or a warm/cold restart is executed. 





IN index UINT Index of the color which should be changed (0−255). 

IN color UDINT 

New color. The color value is arranged as follows: 

Bits 00 − 80 Red value (0−255) 

Bits 08 − 16 Green value (0−255) 

Bits 16 − 24 Blue value (0−255) 

Bits 24 − 32 0 







ready = 1 

endif 

endif 



color = (255 OR SHL(255,8) OR SHL(255,16)) 

VA_SetPaletteColor(1,VC_HANDLE,color_index, color) 


endif 

endif 


#include 

#include 

#include 


UINT _GLOBAL color_index 

UDINT _GLOBAL color; 



{ 

if (!ready) 

{ 



ready = 1; 

} 

if (ready) 

{ 


{ 

color = (0xFF | (0xFF

} 

} 

} 

3.3.8.28 Requirements and Initialization − VA_Setup 

Sets up a connection to Runtime. Runtime, including all drivers, must be on the target system, and the panel 

project must have been started already. 

If the function is successful, then a handle is returned. This handle must be transferred when any other VISAPI 

functions are used. 

If VA_Setup fails (returns 0), then the function must be called cyclically until a valid handle is returned. 




IN interpreter STRING[80] 

OUT Return 

Value 

UDINT 




VC_HANDLE = VA_Setup(1 "Visu") , 


ready = 1 

endif 

endif 

('Visu' is the name of the panel object) 


#include 

#include 

#include 




{ 

if (!ready) 

{ 

VC_HANDLE = VA_Setup(1 "Visu"); , 


ready = 1; 

} 

The name of the project runnning must be specified here. 


The handle which must be specified for all further VISAPI functions. 

0 is returned if an error occurs. 

164 3.3.8.28 Requirements and Initialization − VA_Setup


} 


3.3.8.29 Requirements and Initialization − VA_SetupX 

This function was adopted from AS version 2.0 for compatibility reasons. 

This call takes place similarly to VA_Setup. 

In addition, this function can retrieve an error code in case VA_Setup fails! 

Note: 

This function is only used with the C programming language. 




IN VCHandle UDINT The address of a VCHandle. This is necessary for all further VISAPI operations. 

IN interpreter STRING[80] 

OUT Return 

Value 

The name of the project runnning must be specified here. 

UINT A value other than 0 is returned if error occurs. 


This function couldn't be uses with Automation Basic. 



#include 

#include 

#include 




{ 

if (!ready) 

{ 

VC_HANDLE = VA_SetupX(1 ,&VC_HANDLE "Visu"); 


ready = 1; 

} 

} 

3.3.8.30 Manual Project Control − VA_SetUserParam 

The VA_SetUserParam function can be used to change individual driver parameters during runtime for devices 

used by Visual Components (displays, panel keys, touch, etc.). 

3.3.8.29 Requirements and Initialization − VA_SetupX 165

This is not required for normal Visual Components operation and should only be done in conjunction with your 

relevant B&R support contact or application technician. The necessary parameters, along with their values, are 

listed here in case they are needed. 





IN Type USINT 

IN Parameter UDINT New parameter string 

Type of driver whose parameters should be changed 

1 Display driver 

2 Key driver 

4 Touch driver 


The project may not be run while changing driver parameters. The correct sequence for changing driver 

parameters is as follows: 

• Stop the project with VA_StopProject 

• Change the driver parameter(s) with VA_SetUserParam 

• Start the project with VA_StartProject 

3.3.8.31 Shutdown − VA_Shutdown 

This function is no longer used in the current version of the Visapi library (V2.3), but wasn't removed from the 

library itself for compatibility reasons. We recommend not using this function anymore in new projects. 

The VA_Shutdown function should only be executed before a project is started. 






3.3.8.32 Requirements and Initialization − VA_Srelease 

The VA_Srelease function must always be called at the end of a VISAPI function in a cyclic task. Otherwise, no 

more VA_Saccess functions can be called. 











ready = 1 

endif 

endif 





166 3.3.8.30 Manual Project Control − VA_SetUserParam


endif 

endif 


#include 

#include 

#include 




{ 

if (!ready) 

{ 



ready = 1; 

} 

if (ready) 

{ 


{ 


} 

} 

} 

3.3.8.33 Manual Project Control − VA_StartProject 

A stopped project can be started again with the VA_StartProject command. 

A project can be stopped from the PLC program by the VA_StopProject function, or the 'Manual Project Start' 

option could have been transferred. Starting a project manually allows driver parameters to be changed with 

VA_SetUserParam, as well as other preparatory measures like variable initialization. 

Using this, it is also possible to determine exactly when the visualization project is started. This can guarantee 

that the machine can be operated immediately. In other words, the PLC program is finished initializing as soon 

as the visualization application appears. 






Warning: 

VA_Saccess cannot be called before the VA_StartProject function. 


(* init program *) 

ready = 0 


IF ready 1 THEN 


IF VC_HANDLE 0 THEN 

ready = 1 

ENDIF 

ENDIF 

IF ready = 1 THEN 

3.3.8.32 Requirements and Initialization − VA_Srelease 167

CASE selection OF 

ACTION 1: 

ENDACTION 

Status = VA_StopProject(1,VC_HANDLE) 

ACTION 2: 

AccessStatus = VA_Saccess(1,VC_HANDLE) 

IF AccessStatus = 0 THEN 

VA_Line(1,VC_HANDLE, 10,10,100,100,1) 


ENDIF 

ENDACTION 

ACTION 3: 

ENDACTION 

ELSEACTION : 

ENDACTION 

ENDCASE 

ENDIF 

selection = 0 


#include 

#include 

#include 

_GLOBAL UINT ready; 

_GLOBAL USINT Type; 

_GLOBAL UINT selection; 

_GLOBAL UDINT Status; 


_GLOBAL UDINT AccessStatus; 

_INIT void InitSp(void) 

{ 

ready=0; 

selection=0; 

} 


{ 

if (!ready) 

{ 



ready = 1; 

} 

if (ready) 

{ 

switch(selection) 

Status = VA_StartProject(1,VC_HANDLE) 

{ 

case 1:Status=VA_StopProject(1,VC_HANDLE);break; /* Project is stopped */ 

case 2: AccessStatus=VA_Saccess(1,VC_HANDLE); 

if (AccessStatus==0) 

{ 

VA_Line(1,VC_HANDLE,10,10,100,100,1); 


} 

break; 

case 3:Status=VA_StartProject(1,VC_HANDLE);break; /* Project is started */ 

default: break; 

} 

selection = 0; 

} 

} 


168 3.3.8.33 Manual Project Control − VA_StartProject


3.3.8.34 Touch Screen Calibration − VA_StartTouchCal 

The VA_StartTouchCal function provides touch calibration since different tolerances arise when touch screens 

are manufactured. 

3.3.8.34.1 Operation 

Touch the crosses in the order that they appear on the screen. 

This function only needs to be called once. 

The status can also be queried with the VA_GetCalStatus function. 











ready = 1 

endif 

endif 



VA_StartTouchCal (1,VC_HANDLE) 


endif 

endif 


#include 

#include 

#include 



_CYCLIC void Initialization (void) 

{ 

if (!ready) 

{ 



ready = 1; 

} 

if (ready) 

{ 


{ 

VA_StartTouchCal (1,VC_HANDLE); 


} 

} 

} 

3.3.8.35 Manual Project Control − VA_StopProject 

A project can be halted with the VA_StopProject function. This seldom needs to be done unless parameters 

need to be changed for used drivers with the VA_SetUserParam function, for example. 

3.3.8.34 Touch Screen Calibration − VA_StartTouchCal 169






Warning: 

VA_Saccess cannot be called before the VA_StopProject function. 



ready = 0 


IF ready 1 THEN 



ready = 1 

ENDIF 

ENDIF 

IF ready = 1 THEN 

CASE selection OF 

ACTION 1: 

ENDACTION 

Status = VA_StopProject(1,VC_HANDLE) 

ACTION 2: 

AccessStatus = VA_Saccess(1,VC_HANDLE) 

IF AccessStatus = 0 THEN 

VA_Line(1,VC_HANDLE, 10,10,100,100,1) 


ENDIF 

ENDACTION 

ACTION 3: 

ENDACTION 

ELSEACTION : 

ENDACTION 

ENDCASE 

ENDIF 

selection = 0 


#include 

#include 

#include 

_GLOBAL UINT ready; 

_GLOBAL USINT Type; 

_GLOBAL UINT selection; 

_GLOBAL UDINT Status; 


_GLOBAL UDINT AccessStatus; 

_INIT void InitSp(void) 

{ 

ready=0; 

selection=0; 

} 


{ 

Status = VA_StartProject(1,VC_HANDLE) 


170 3.3.8.35 Manual Project Control − VA_StopProject


if (!ready) 

{ 



ready = 1; 

} 

if (ready) 

{ 

switch(selection) 

{ 

case 1:Status=VA_StopProject(1,VC_HANDLE);break; /* Project is stopped */ 

case 2: AccessStatus=VA_Saccess(1,VC_HANDLE); 

if (AccessStatus==0) 

{ 

VA_Line(1,VC_HANDLE,10,10,100,100,1); 


} 

break; 

case 3:Status=VA_StartProject(1,VC_HANDLE);break; /* Project is started */ 

default: break; 

} 

selection = 0; 

} 

} 

3.3.8.36 Graphics and Text Output − VA_Textout 

Writes a text on the screen. 

The text is placed at the x and y coordinates. (For graphic displays, these are in pixels. For text displays, the 

coordinates refer to the current character size). The background color can be changed with the bC variable, and 

the foreground color with the fC variable. If '......' appears on the display, then the font index is invalid. 

PP41: The foreground (fC) and background (bC) can only be 0, 1, or 255. 





IN font_index UINT 

Index of the font to be used 

IN x/y UINT Upper left corner of the text 

IN fC USINT Foreground color of the text 

IN bC USINT Background color of the text 

IN str STRING[80] Text to be output 

OUT Return 

Value 

The font index corresponds to the font number used in the VC editor (beginning 

with 0). 

UINT Not equal to 0 if error occurs 

3.3.8.36 Graphics and Text Output − VA_Textout 171






ready = 1 

endif 

endif 



0 then 

endif 

VA_Textout (1,VC_HANDLE,1,100,100,0,1, 

"HELLO") 


endif 


#include 

#include 

#include 




{ 

if (!ready) 

{ 



ready = 1; 

} 

if (ready) 

{ 


{ 

VA_Textout (1,VC_HANDLE,1,100,100,0,1, 

"HELLO"); 


} 

} 

} 

3.3.9 Color Table − VISAPI 

3.3.9.1 Color Palette for IPC Color Displays 

Reserved Colors: 255 − can be used for transparent effect 

Index Preview RGB Index Preview RGB Index Preview RGB Index Preview RGB 

0 000 000 000 60 

1 000 000 170 61 

2 000 170 000 62 

3 000 170 170 63 

4 170 000 000 64 

5 170 000 170 65 

6 150 120 015 66 

7 170 170 170 67 

8 127 127 127 68 

9 110 110 197 69 

CC99CC 

204 153 204 

CC66CC 

204 102 204 

CC33CC 

204 51 204 

CC00CC 

204 00 204 

CCFF99 

204 255 153 

CCCC99 

204 204 153 

CC9999 

204 153 153 

CC6699 

204 102 153 

CC3399 

204 51 153 

CC0099 

204 00 153 

120 

121 

122 

123 

124 

125 

126 

127 

128 

129 

999900 

153 153 00 

996600 

153 102 00 

993300 

153 51 00 

990000 

153 00 00 

66FFFF 

102 255 255 

66CCFF 

102 204 255 

6699FF 

102 153 255 

6666FF 

102 102 255 

6633FF 

102 51 255 

6600FF 

102 00 255 


180 

181 

182 

183 

184 

185 

186 

187 

188 

189 

339966 

51 153 102 

336666 

51 102 102 

333366 

51 51 102 

330066 

51 00 102 

33FF33 

51 255 51 

33CC33 

51 204 51 

339933 

51 153 51 

336633 

51 102 51 

333333 

51 51 51 

330033 

51 00 51 

172 3.3.8.36 Graphics and Text Output − VA_Textout


10 000 255 005 70 

11 000 170 255 71 

12 170 000 085 72 

13 17000 0 255 73 

14 240 240 095 74 

15 255 255 255 75 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

FFFFFF 

255 255 255 

FFCCFF 

255 204 255 

FF99FF 

255 153 255 

FF66FF 

255 102 255 

FF33FF 

255 51 255 

FF00FF 

255 00 255 

FFFFCC 

255 255 204 

FFCCCC 

255 204 204 

FF99CC 

255 153 204 

FF66CC 

255 102 204 

FF33CC 

255 51 204 

FF00CC 

255 00 204 

FFFF99 

255 255 153 

FFCC99 

255 204 153 

FF9999 

255 153 153 

FF6699 

255 102 153 

FF3399 

255 51 153 

FF0099 

255 00 153 

FFFF66 

255 255 102 

FFCC66 

255 204 102 

FF9966 

255 153 102 

FF6666 

255 102 102 

FF3366 

255 51 102 

FF0066 

255 00 102 

FFFF33 

255 255 51 

FFCC33 

255 204 51 

FF9933 

255 153 51 

FF6633 

255 102 51 

FF3333 

255 51 51 

FF0033 

255 00 51 

FFFF00 

255 255 00 

FFCC00 

255 204 00 

76 

77 

78 

79 

80 

81 

82 

83 

84 

85 

86 

87 

88 

89 

90 

91 

92 

93 

94 

95 

96 

97 

98 

99 

100 

101 

102 

103 

104 

105 

106 

107 

CCFF66 

204 255 102 

CCCC66 

204 204 102 

CC9966 

204 153 102 

CC6666 

204 102 102 

CC3366 

204 51 102 

CC0066 

204 00 102 

CCFF33 

204 255 51 

CCCC33 

204 204 51 

CC9933 

204 153 51 

CC6633 

204 102 51 

CC3333 

204 51 51 

CC0033 

204 00 51 

CCFF00 

204 255 00 

CCCC00 

204 204 00 

CC9900 

204 153 00 

CC6600 

204 102 00 

CC3300 

204 51 00 

CC0000 

204 00 00 

99FFFF 

153 255 255 

99CCFF 

153 204 255 

9999FF 

153 153 255 

9966FF 

153 102 255 

9933FF 

153 51 255 

9900FF 

153 00 255 

99FFCC 

153 255 204 

99CCCC 

153 204 204 

9999CC 

153 153 204 

9966CC 

153 102 204 

9933CC 

153 51 204 

9900CC 

153 00 204 

99FF99 

153 255 153 

99CC99 

153 204 153 

999999 

153 153 153 

996699 

153 102 153 

9933999 

153 51 153 

990099 

153 00 153 

99FF66 

153 255 102 

99CC66 

153 204 102 

130 

131 

132 

133 

134 

135 

136 

137 

138 

139 

140 

141 

142 

143 

144 

145 

146 

147 

148 

149 

150 

151 

152 

153 

154 

155 

156 

157 

158 

159 

160 

161 

162 

163 

164 

165 

166 

167 

66FFCC 

102 255 204 

66CCCC 

102 204 204 

6699CC 

102 153 204 

6666CC 

102 102 204 

6633CC 

102 51 204 

6600CC 

102 00 204 

66FF99 

102 255 153 

66CC99 

102 204 153 

669999 

102 153 153 

666699 

102 102 153 

663399 

102 51 153 

660099 

102 00 153 

66FF66 

102 255 102 

66CC66 

102 204 102 

669966 

102 153 102 

666666 

102 102 102 

663366 

102 51 102 

660099 

102 00 153 

66FF33 

102 255 51 

66CC33 

102 204 51 

669933 

102 153 51 

666633 

102 102 51 

663333 

102 51 51 

660033 

102 00 51 

66FF00 

102 255 00 

66CC00 

102 204 00 

669900 

102 153 00 

666600 

102 102 00 

663300 

102 51 00 

660000 

102 00 00 

33FFFF 

51 255 255 

33CCFF 

51 204 255 

3399FF 

51 153 255 

3366FF 

51 102 255 

3333FF 

51 51 255 

3300FF 

51 00 255 

33FFCC 

51 255 204 

33CCCC 

51 204 204 

190 

191 

192 

193 

194 

195 

196 

197 

198 

199 

200 

201 

202 

203 

204 

205 

206 

207 

208 

209 

210 

211 

212 

213 

214 

215 

216 

217 

218 

219 

220 

221 

222 

223 

224 

225 

226 

227 

33FF00 

51 255 00 

33CC00 

51 204 00 

339900 

51 153 00 

336600 

51 102 00 

333300 

51 51 00 

330000 

51 00 00 

00FFFF 

00 255 255 

00CCFF 

00 204 255 

0099FF 

00 153 255 

0066FF 

00 102 255 

0033FF 

00 51 255 

0000FF 

00 00 255 

00FFCC 

00 255 204 

00CCFF 

00 204 255 

0099CC 

00 153 204 

0066CC 

00 102 204 

0033CC 

00 51 204 

0000CC 

00 00 204 

00FF99 

00 255 153 

00CC99 

00 204 153 

009999 

00 153 153 

006699 

00 102 153 

003399 

00 51 153 

000099 

00 00 153 

00FF66 

00 255 102 

00CC66 

00 204 102 

009966 

00 153 102 

006666 

00 102 102 

003366 

00 51 102 

000066 

00 00 102 

00FF33 

00 255 51 

00CC33 

00 255 51 

009933 

00 153 51 

006633 

00 102 51 

003333 

00 51 51 

000033 

00 00 51 

00FF00 

00 255 00 

00CC00 

00 204 00 

3.3.8.36 Graphics and Text Output − VA_Textout 173

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

FF9900 

255 153 00 

FF6600 

255 102 00 

FF3300 

255 51 00 

FF0000 

255 00 00 

CCFFFF 

204 255 255 

CCCCFF 

204 204 255 

CC99FF 

204 153 255 

CC66FF 

204 102 255 

CC33FF 

204 51 255 

CC00FF 

204 00 255 

CCFFCC 

204 255 204 

CCCCCC 

204 204 204 

CC99CC 

204 153 204 

108 

109 

110 

111 

112 

113 

114 

115 

116 

117 

118 

119 

120 

999966 

153 153 102 

996666 

153 102 102 

993366 

153 51 102 

990066 

153 00 102 

99FF33 

153 255 51 

99CC33 

153 204 51 

999933 

153 153 51 

996633 

153 102 51 

993333 

153 51 51 

990033 

153 00 51 

99FF00 

153 255 00 

99CC00 

153 204 00 

999900 

153 153 00 

168 

169 

170 

171 

172 

173 

174 

175 

176 

177 

178 

179 

180 

3399CC 

51 153 204 

3366CC 

51 102 204 

3333CC 

51 51 204 

3300CC 

51 00 204 

33FF99 

51 255 153 

33CC99 

51 204 153 

339999 

51 153 153 

336699 

51 102 153 

333399 

51 51 153 

330099 

51 00 153 

33FF66 

51 255 102 

33CC66 

51 204 102 

339966 

51 153 102 

228 

229 

230 

231 

..... 

..... 

..... 

..... 

..... 

..... 

..... 

254 

255 

TRANS− 

PARENT 

Note: 

This is the standard color palette for VGA displays. If this palette is replaced by a user−defined palette, then 

naturally that one applies! 

3.3.9.2 Color Palette for SG3 Black/White Displays 

Reserved Colors: none 

Index Preview RGB 

1 000 000 000 

0 255 255 255 

3.3.10 Error Codes − VISAPI 

3.3.10.1 Error Codes 

Code Meaning Occurs when... 

100 VISAPI not initialized 

3004 VA_Textout font not present 

7000 

Drawing currently in progress 

(BUSY) 

7010 No project found 

7030 No project found 

7090 Invalid parameter 

Everything else 

Invalid parameters in individual 

functions (more exact error code) 


Occurs when a VISAPI function is called before 

VA_Setup(....) is called. 

Occurs when a font index which isn't used at 

runtime is specified. 

Occurs with the VA_Saccess function when no 

access to the display is currently possible. 

Attempted again in the next cycle. 

Project name specified with VA_Setup(...) is 

incorrect 

Project name specified with VA_Setup(...) is 

incorrect 

i.e. negative coordinates in drawing command, 

invalid pointer, etc. 

i.e. negative coordinates in drawing command, 

invalid pointer, etc. 

009900 

00 153 00 

006600 

00 102 00 

003300 

00 51 00 

000000 

00 00 00 

000000 

00 00 00 

000000 

00 00 00 

000000 

00 00 00 

000000 

00 00 00 

000000 

00 00 00 

000000 

00 00 00 

000000 

00 00 00 

000000 

00 00 00 

TRANS− 

PARENT 

174 3.3.9.2 Color Palette for SG3 Black/White DisplaysReserved Colors: none


3.4 Supported Hardware − Reference 

This section contains information about hardware supported by Visual Components. 

3.4.1 Key Matrix 

The following is a list of references to the respective key matrices classifications for all supported operator 

panels which are equipped with panel keys. For the sake of completeness, there is also an image for all other 

panels. 

3.4.1.1 Operator Panels for the CAN Controller C130 

Panel 4B1270.00−490 

Panel 4D1164.00−590 

Panel 4D1165.00−490 

Panel 4D1166.00−490 

Panel 4D1167.00−490 

3.4.1.2 PowerPanel Controllers 

Panel 4P0420.00−490 

Panel 4P3040.00−490 

3.4.1.3 Operator Panels for the IPC2001 Family 

Panel 5D2000.02 

Panel 5D2210.01 

Panel 5D2210.01C (Compact IPC2002) 

Panel 5D2219.01 

Panel 5D2219.02 

Panel 5D2510.01 

Panel 5D2510.10 

Panel 5D2510.22 

Panel 5D2519.01 

Panel 5D2519.02 

3.4.1.4 Operator Panels for the IPC5000 Family 

Panel 5D5210.01 

Panel 5D5211.02 

Panel 5D5211.03 

Panel 5D5212.02 

Panel 5D5212.04 

Panel 5D5500.10 

Panel 5D5501.01 

Panel 5D5510.10 

Panel 5D5600.01 

Panel 5D5600.02 

Panel 5D5600.03 

Panel 5D5601.01 

Panel 5D5601.02 

Panel 5D5601.03 

3.4.2 Key Matrix − Panel 4B1270.00−490 

The numbers in the picture specify the index of the corresponding key in the key matrix. 

For keys with LED, the number also specifies the index of the corresponding LED in the LED matrix. 

3.4 Supported Hardware − Reference 175

3.4.3 Key Matrix − Panel 4D1164.00−590 




176 3.4.3 Key Matrix − Panel 4D1164.00−590





3.4.4 Key Matrix − Panel 4D1165.00−490 177








178 3.4.5 Key Matrix − Panel 4D1166.00−490


3.4.7 Key Matrix − Panel 4P0420.00−490 



3.4.7 Key Matrix − Panel 4P0420.00−490 179

3.4.8 Key Matrix − Panel 4P3040.00−490 




180 3.4.8 Key Matrix − Panel 4P3040.00−490


3.4.9 Key Matrix − Panel 5D2000.02 



3.4.9 Key Matrix − Panel 5D2000.02 181





182 3.4.10 Key Matrix − Panel 5D2210.01


3.4.11 Key Matrix − Panel 5D2210.01C (Compact IPC2001) 



3.4.11 Key Matrix − Panel 5D2210.01C (Compact IPC2001) 183
























































































































3.5 Software Modules on the Controller 

Runtime system resources consist of .BR modules. These modules contain executable code for the drivers and 

Visual Components Runtime (command interpreter). They also contain compiled byte code of the Visual 

Components editor project, including the necessary resource files. 

All required modules are automatically inserted by the project manager. The following is a list of individual 

modules including some examples provided for better understanding. 

3.5.1 Executable Visual Components Modules 


The Visual Components runtime environment is divided into code and data objects. This section discusses 

executable modules in .BR format. 

There are many specialized modules due to the various platforms (CPU types), displays, and panel units. 

When a new project is created, the most recent versions of executable .BR modules are automatically 

transferred to the project. Different modules are used depending on the project and hardware. 

Modules are automatically transferred to the target system when the project is downloaded. 

All Visual Components runtime modules are tied to the system as non−cyclic tasks with lower priority than cyclic 

tasks. Cyclic user tasks (task classes) are therefore not influenced by runtime performance. Visual Components 

runtime modules run in the system idle time with low priority. 

A simple and clear definition of timing performance is difficult because of the different ways that application 

software loads down the CPU. This is mainly due to the lower priority of Visual Components runtime modules. 

If a system does not have much idle time available, then display speed and key reaction are slower on the target 

system. 

Example: 

A cyclic task running every 10 ms requires 8ms from the CPU to complete the task. Thus, approx. 2 ms remain 

on the CPU for the remaining system operations (I/O updates, system routines, communication). In the 

remaining time (2 ms), Visual Components loses CPU time as well. In this example, this is less than 20%. If 

20% is sufficient, then problems do not occur. If this is not sufficient, then display speed and key reaction time to 

input are slow. This can cause problems for extensive pictures which have many input and output fields. 

Time bottlenecks can occur for INA2000 communication (Automation Studio online connection / PVI 

visualization) since it also runs during idle time, i.e. the connection to the PC (AS or PVI) can be interrupted or 

206 3.5 Software Modules on the Controller


the Visual Components visualization can become slower. 

To remedy this, a 1 or 2 ms idle time can be set in the TC#1 system configuration as long as the application 

allows it. 

3.5.1.1 Module Versions 

Starting with AS Version 2.1, only Visual Components .BR modules of version 01.10 are used. Older versions 

must be manually updated if this does not occur automatically. 

When a new project is created, the most recent versions of .BR modules are automatically transferred to the 

project. 

Here is a list of modules with brief descriptions: 

3.5.1.2 VC Project Management Module 

Module 

Name: 

ApLib.br 

Function: Base module for managing the project on the target system. 

CPU Ver.: m68k, i386 

Dependency: SysLib 

Remark: 

Initializes and de−initializes when downloading, synchronizes separate modules procedures 

when downloading projects, manages the modules if multiple projects are running on a target, 

provides Visual Components system services for the VISAPI library. 

3.5.1.3 VC Interpreter Module 

Module Name: vcinter.br 

Function: Interpreter for Visual Components 


Dependency: SysLib, DataObj, ApLib 

Remark: 

3.5.1.4 VC VGA Display Driver 

Module 

Name: 

Ddpdcvga.br 

Interprets Visual Components data objects, executes the project, starts the drivers for 

the corresponding project, and coordinates all input and output in the project. 

Runs on i386 targets in 100 ms intervals (corresponding to idle time). On m68k 

systems, a 200 ms interval is used. 

This module is substantially larger on i386 systems than on m68k systems. This is due 

to advanced options (touch operation, color displays). 

Function: Driver for IPC200x and IPC5000 (1/4 VGA, VGA, SVGA and XGA) connections 

CPU Ver.: i386 

Dependency: ApLib 

Remark: 

3.5.1.5 VC IPC Key Driver 

Display controller for i386 panel systems based on the C&T chip sets. Functions are preset to 

the interpreter module for display control. 

Module Name: DdPkIpc.br 

Function: Driver for IPC keys (IPC2000 and IPC5000) 



Remark: 

Key operation for IPC2000 and IPC5000 systems. Front keys are supplied to the 

interpreter module. Jog keys can be queried using a FBK. A high priority watchdog 

secures the jog keys. 

3.5.1.1 Module Versions 207

3.5.1.6 VC IPC Touch Driver 

Module 

Name: 

DdptIpc.br 

Function: Touch driver for the COM port (IPC2000 and IPC5000) 



Remark: 

3.5.1.7 VC CAN Panel Driver 

Module 

Name: 

Touch operation for IPC2000 and IPC5000 systems. Touch support for the front panel is 

prepared for the interpreter module. Jog keys can be queried using a FBK. A high priority 

watchdog secures the touch buttons. 

DdpcCan.br 

Function: CAN panel driver 



Remark: 

Driver for CAN panel output and input (4B1270 and C130 controller including displays). The 

driver uses the CAN_LIB library to show interpreter commands on the display. 

Secured jog keys can be read using a FBK. 

3.5.1.8 VC Power Panel Driver 

Module Name: Ddpcpp41.br 

Function: Display and key driver for Power Panel devices 

CPU Ver.: m68k 


Remark: 

3.5.1.9 VC Printer Driver 

Module Name: Ddpapi.br 

Driver for output and input on PowerPanel devices (PP41 and PP21). 

Secured jog keys can be read using a FBK. 

Function: Controls the printer on the parallel port (alarm system) 



Remark: 

The alarm system can be printed out using this driver on i386 devices. The driver only supports 

the printer text mode. 

3.5.1.10 VC AT Keyboard Driver 

Module 

Name: 

ddpkbipc.br 

Function: AT keyboard driver for IPC projects 



Remark: 

This driver supports a defined set of AT keyboard keys. However, they can only be used for 

editing and controlling pictures. A key matrix cannot be generated. 

3.5.1.11 VC Graphics Driver for PPxx 

Module Name: ddpdcx55.br 

Function: Display driver for PPxx 



208 3.5.1.6 VC IPC Touch Driver



Remark: 

3.5.1.12 VC Graphics Driver for PPxx 

Module 

Name: 

ddpkxx.br 

Function: Display driver for PPxx 


Dependency: ApLib, sys_lib 

Remark: 

Display controller for PPxx panel systems based on Geode chip sets. Functions are 

preset to the interpreter module for display control. 

Key operation for PPxx systems. Front keys are supplied to the interpreter module. Jog keys 

can be queried using a FBK. 

3.5.1.13 Compact IPC2001 Modules (Example) 

The following example contains an overview of the required modules for a project using the Compact IPC2001 

(VGA with touch operation). 

The APLIB, DDPCDCVGA, DDPTIPC, and VCINTER modules are described in the Executable Visual 

Components Modules section. 

VGA data objects, as well as the VGA01 and VGA02 modules, are described in the Visual Component Data 

Modules section. 

The VISAPI module is the user interface of the Visualization Library. Library functions are found in the 

Automation Studio Library Manager (see also VISAPI Functions Overview). 

3.5.1.14 CP360 Modules (Example) 

The following example shows a sample project based on a CP360 with a CAN panel. 

3.5.1.12 VC Graphics Driver for PPxx 209

The APLIB, DDPCCAN, and VCINTER modules are described in the Executable Visual Components Modules 

section. 

VIS data objects, as well as the VIS01 and VIS02 modules, are described in the Visual Components Data 

Modules section. 

The CAN_LIB module represents the CAN connection to the panel. CAN driver DDPCCAN is used by Visual 

Components. 

DATAOBJ routines are called by the Visual Components alarm system. 

3.5.1.15 CP476 Modules (Example) 


In the following section, all modules are shown for a Visual Components project which uses a CP476 with a 

C130 controller and a 4D1167 panel. 

The APLIB, DDPCCAN, and VCINTER modules are described in the Executable Visual Components Modules 

section. 

4D1167 data objects, as well the as 4D116701 and 4D116702 modules, are described in the Visual 

Components Data Modules section. 

The RTK68, SYS_LIB, and RUNTIME modules are partially required by Visual Components modules. The 

CAN_LIB module represents the CAN connection to the panel. CAN driver DDPCCAN is used by Visual 


210 3.5.1.15 CP476 Modules (Example)


DATAOBJ routines are called by the Visual Components alarm system. 

3.5.2 Visual Components Data Modules 

In addition to executable code modules and drivers, a Visual Components project also consists of data objects. 

These data objects are created when a project is compiled and are automatically transferred to the target 

system. 

A Visual Components project consists of 3 different data objects. 2 resource modules are always attached to a 

project global module. The 'xxx01' module contains picture description data. The 'xxx02' module contains project 

fonts and bitmaps. 

This division can be seen here in this simple project example. 

The main module in this project is the 'VISU' panel object. Global project data are contained in this module. 

Additional modules are always labeled with the project name plus a 2−digit number. 

Picture and field information for project pictures is contained in the 'VISU01' module, which belongs to the 'VISU' 

project. 

All necessary resource data for bitmaps and fonts are stored in the 'VISU02' module. This module can become 

very large (many different character fonts and bitmaps). If nothing has been changed in the texts and bitmaps, 

they will not be retransferred to the target system. 

3.5.3 Internal Details About Project Storage 

A list of required files is shown here to gain a better understanding of the proper Visual Components structure 

and to better analyze problems. 

To secure data, the project file is copied after each successful compilation. 

Warning: 

Please do not change, delete, or move any files or directories from the AS project. This can cause the project to 

crash! 

3.5.3.1 Project Storage Example 

3.5.2 Visual Components Data Modules 211

The image above shows an Automation Studio project which uses a System 2005 CP360 with a 4B1270 panel. 

The directory tree shown below displays the file system structure of the project. There is a 'VisualComponents' 

directory in the 'CPU' subdirectory. The VC.INI file is located in this directory, as well as subdirectories for all 

other panel objects in a project. In this example, the 'VIS' directory is found here. 

These are the relevant files in the CPU directory of a project: 

The 'VIS.WAF' file is important here. This file represents the Visual Components editor object. Drivers and data 

objects are described in the following sections: 

• List of All Executable Modules 

• List of Project Data Modules 

VisualComponents Directory: 


212 3.5.2 Visual Components Data Modules


The VC.INI file contains information about the panel projects which exist in this Automation Studio project 

(CP360). Parameters connecting the panel object to the hardware are entered in this file and updated when the 

project is opened. 

This example uses an object with the name 'vis' (panel object name). There is also a subdirectory with the same 

name for this project. 

All files required by the panel editor for managing the project are found in the 'VIS' subdirectory. 

Files ending with '.BR' are project files which have already been compiled. 

Files ending with '.BRC' are checksum files for the .BR modules. 

The TFont1x1.BMP file is a font file in bitmap format. 

The VIS.PWC file is the actual project file containing all the information for the editor. 

Additional information for the editor is contained in the VIS.PWL file. 

Backup Copy: 

A copy of the project module is made after every successful compilation. The project module has the ending 

'.PWC'. The backup copy has the ending '.BAK'. In case a project crashes or can no longer be opened, try to 

replace the project file with the backup copy. 

Other bitmaps, text, and binary files can be included depending on the project and target hardware. In general, 

all project files are contained in this directory and subdirectories. 

Warning: 

Please do not change, delete, or move any files or directories from the AS project. This can cause the project to 

crash! 

3.5.2 Visual Components Data Modules 213


214 3.5.2 Visual Components Data Modules


4.1 Welcome to Visual Components 

4.1.1 New Functions in Visual Components 2.4 

• 4.1.2 New Visapi Functions 

The Backlight could be enabled/(diabled with an API function 

(see VC_SetBacklight) 

• Screenshot Library 

(see VCScrSht) 


• ListBox Input 

The ListBox input field can be used by the user to select input from a ListBox. 

(see ListBox Input Field) 

• Touch Pad Selection 

Using touch pad selection allows the user to choose different touch pads for a project 

(see Touch Pad Selection) 

• Expanded Alarm System Configuration 

Data object configuration for the historical alarm list. The user can decide whether a data object should 

be created or not. If one is created, the size of the ring buffer can also be configured. 

(See Configuring the Alarm System) 

Additional parameters in the alarm settings allow the user to acknowledge active alarms. 

(See Creating and Configuring Alarms) 

• New Visapi Functions 

The historical alarm list can now also be deleted during runtime 

(See VA_DelAlarmHistory) 

An entire alarm group can also be acknowledged. 

(See VA_QuitAlarms) 

Information about the display panel can be read. 

(See VA_GetDisplayInfo) 

• Formatted Tags for Touch Buttons 

Touch button texts can also contain formatted texts. 

• VNC Server 

Visualization applications can be displayed on a PC using the VNC server (see libvncserv). 

This can be used to implement a 'master office'. 

4 Visual Components User's Manual 215


• Touch Configuration 

As an update for using touch displays with IPC 2000 and 5000 systems, now any free serial 

interface can be used and configured for the touch screen. Interfaces which are used by other 

devices (i.e. C100) are automatically not available. 

(See Touch Configuration) 

• Variable Numbering of Text Groups 

Up to now, text numbers (indices) of texts could only be increased beginning with the number 0. Now 

the text numbers of each text can optionally be set individually. For example, error numbers can be 

more easily assigned an appropriate error text in this way. 

(See Advanced Text Group Options) 

• Variables in Text Group Texts 

Texts in a text group no longer have to contain only static texts. Dynamic texts can also be put together 

at runtime using the contents of PLC process variables. In this way, error messages can be extended to 

include additional information, for example, or high−performance status displays can be easily 

implemented. 

(See Advanced Text Group Options) 

• Saving Variables in the Alarm List 

In addition to information stored previously in the alarm list, four pieces of numeric information from PLC 

process variables can now also be stored with the alarm text. In this way, alarms can be written with 

additional information such as the error number of errors pertaining to intelligent I/O components, or the 

item which caused the error to occur. Configuration takes place in the same way as text group variables. 

(See Creating and Configuring Alarms) 

• Standardized Scaling 

Scaling of numeric data types was extremely simplified since all numeric data types (except UDINT and 

FLOAT) are able to be scaled to the entire DINT range in the future. This removes the previous 

restriction which only allowed process variables to be scaled within the value range of its own data type. 

(See reference manual − Scaling − Input Numeric and Scaling − Output Numeric) 

• Compressed Bitmaps 

Color bitmaps can be saved in compressed format with Visual Components 2.2 which allows them to be 

displayed very quickly. Compression is optimized for graphics with large, monochrome surfaces like 

those which are very frequently used for system images and schematic representations. Optimal 

compression is enabled in this way. 

Bitmaps are managed and used as previously; compression takes place automatically with all supported 

controllers the next time the project is Built. 

• New Controllers 

In addition to the previously supported CAN operator panels, now serial operator panels can be 

connected to the RS232 interface(s) of the CPU and configured with Visual Components. All display 

units which could be used previously with the C130 CAN controller can be connected to the C100 

controller. 

• PS/2 AT Keyboard Support for IPC Systems 


216 4.1.4 New Functions in Visual Components 2.2


With AT keyboard support, a lot of time can be saved by the simplified input of texts and numbers, 

especially during the startup phase. In this way, the operator panel can be laid out more to the operation 

specifications of the machine when an AT keyboard is used during initial operations. By default, Visual 

Components supports German and English (US) keyboard formats. Other formats can be defined as 

needed. 

(See Keys, LED, and Touch Support) 

• Importing and Exporting Projects and Parts of Projects 

Visual Components now supports importing and exporting of projects and parts of projects; work 

invested can be more easily reused in new projects than previously. All components from the Visual 

Components tree view can be individually or collectively exported and imported. Dependencies are 

taken into consideration automatically so that exporting can never be incomplete. Exporting and 

importing take place in XML format; naturally, exporting and importing text in ASCII format is available. 

(See Importing and Exporting) 


The following functions are available beginning with Version 2.1. 

• Project Creation with Color Display 

Process pictures shown using the color possibilities of the target system. Possibility to use a variable to 

control the colors (16 bit value − high byte foreground, low byte background color). This allows visibility 

to be controlled during runtime, and blink effects can be created. 

• Expanded Font Possibilities 

'True Type Fonts' are supported on the graphic target system. Any fonts and symbols from Windows 

can be integrated into a project. The fonts are always shown with fixed character widths on the 

visualization device − proportional fonts are converted respectively. It should be noted that some fonts 

are copyrighted. 

• Status Variables 

Object display can be switched on and off (bit 0) using status variables. Input can also be locked during 

runtime (bit 1). For INA Client communication, an 'Edit' bit was added (bit 15 − set or cleared by the 

interpreter while an entry field is being edited). 

• Screen Saver 

Any process picture can be defined as a screen saver and displayed automatically after a set delay. 

• Uniform Input and Output Fields 

Assigning explicit data types is no longer necessary when configuring input and output fields. There are 

only numeric and alphanumeric input and output fields. The scaling size is automatically set. 

• Variable Scaling 

Scaling and value limitation for fields can take place using variables. 

• SVGA / XGA 

In addition to existing VGA panels (640x480), SVGA (800x600) and XGA (1024x768) panels can also 

be configured with up to 256 colors. 

• Editor − Grid Functions 

4.1.5 New Functions in Visual Components 2.1 217

The editor can arrange static objects such as lines, rectangles, and ellipses into levels using the 

shortcut menu. Pressing the 'CTRL' key allows horizontal or vertical lines as well as squares and circles 

to be drawn. Settings for the grid can be defined directly using the grid icon menu in the toolbar. Objects 

can be positioned with pixel precision or using the defined grid. 

• Button and HotSpot 

These new elements are only for Touch displays. Buttons can be configured as desired (size, with or 

without bitmap and/or text, color, and function). Blink effects are possible using color variables. 

HotSpots are invisible switches (touch sensitive areas). In this way, invisible switching functions can be 

placed at certain locations. The representation can be configured with bitmaps or line graphics. 

• ListBoxes 

A list of texts can be shown on the display with this output field. Texts can be output from a text group or 

a process variable. For this, a text can be highlighted. Selecting the highlighted text takes place using a 

process variable. 

• Key Levels 

Using shift keys, panel keys can be used to enter up to 4 different characters per key. Other key 

functions can only be configured on the first level. 

• Split Download 

The project is divided over multiple modules. Bitmaps and fonts, which make up the majority of a 

project, are packed in a module. This module only has to be transferred again if bitmaps or fonts have 

been added or changed. This greatly reduces the download time during the development phase. 

• Multiple Projects 

Several CAN panels can be operated on a CPU. A CAN panel can also be operated at the same time as 

a VGA visualization device. For this, each panel is configured in a separate project. 

• API Expansions 

The API interface was changed because of the possibility to execute multiple projects on the target 

system. New functions include reading touch coordinates, setting contrast and brightness, and reading 

alarms. 

Necessary changes in existing projects can be found under Upgrading Visual Components 2.0 Projects. 

• Data Point List 

All variables used in the individual pictures can be saved in a text file. This list can be used to further 

process INA CLIENT FBKs. 

• Decimal Point Representation 

Fields with decimal representation can also be entered without the decimal point key. 

• Alarm System 

Saving the historical alarm list takes place in a data object. Printing the alarms on IPC based devices is 

possible using the parallel interface. 

• Increment/Decrement 


A variable can be increased or decreased incrementally using a button. Optionally, a repeat function 

and upper/lower limits can be configured. 

218 4.1.5 New Functions in Visual Components 2.1


• Jog Keys 

Using an API function, jog key functions (key matrix) can be programmed based on the task classes. 

This allows priorities to be set for reading keys. 

• Variable Color Palette 

The color palette of 256 colors can be adjusted in a project specific manner. If several shades of a color 

are required, then this palette adjustment can be made in the editor. 

Color palette settings can also be changed during runtime using API. This helps create fade−in and 

fade−out effects. (Only applies to i386 systems with VGA controllers) 

4.2 Getting Started with Visual Components 2.4 

The tutorial application examples serve as an introduction to each specific B&R Visual Components hardware 

environment. 

It will be possible to set up simple projects independently after configuring an application example using the 

specifications in the individual tutorials. Solutions to specific questions which are not fully covered in 'Getting 

Started' are explained in detail in the Visual Components Help system. 

4.2.1 CP476 with B127 CAN Display − Example 

The following steps describe how to create a simple application using Visual Components. This example shows 

the use of Visual Components in connection with a CP476 and a remote CAN display. The application contain 

inputs and outputs as well as keys. Using these will allow LED states to be changed on the keypad. 

Other CPUs from the 20xx family can also be used. Modifications are also possible for remote CAN operator 

panels. The LED functions described in step 7 are only possible with operator panels which also have LEDs built 

into their keys. 

The following is a list of the individual steps for this application example: 

1. Creating a New Automation Studio Project 

2. Inserting a Display 

3. Inserting PV Variables 

4. Applying Global Settings to Visual Components 

5. Inserting an Input Field 

6. Inserting an Output Field 

7. Connecting an LED with a PV 

8. Defining INC/DEC Keys 

9. Compiling and Transferring the Project 

10. Testing Functions 

4.2.1.1 CAN − Step 1: Creating a New Automation Studio Project 

First, start a new project using Automation Studio. For this, select "New Project..." from the "File" menu. This will 

start the Project Wizard. Use "vc_can" as the project name (max. 8 characters). Proceed by clicking on the Next 

button in the Wizard. 

4.2 Getting Started with Visual Components 2.4 219

Next, the CPU to be used must be selected. You should select a "7CP476.60−1" CPU from the 2003 series. 

Again, click on Next to proceed. All selected settings are summarized one more time in the final view. The 

Wizard is ended once you click on Finish. 

The new project is now ready to go. 

4.2.1.2 CAN − Step 2: Inserting a Display 


The easiest way to begin a new visualization project is to insert the desired display. Since you are working with 

a remote CAN operator panel in this case, the panel is integrated into this existing project using a CAN I/O node. 

First, you should change from the Software tab to the CAN tab in the project view. Now right−click on the free 

line next to the slot symbol and select the Insert entry from the shortcut menu. 

220 4.2.1.2 CAN − Step 2: Inserting a Display


A list of all compatible displays for this slot is shown under 'Panel'. Select the entry "4B1270.00−490" for a B127 

panel controller from the list and acknowledge the selection with the Next button. 

In the next window, enter the CAN node number which is set on the B127 controller to enable communication 

between the CPU and the panel controller. 500 kBaud is automatically set as the baud rate by the system. Make 

sure that this transfer rate is also configured on the panel controller. After checking the controller settings and 

entering the correct node number, proceed by clicking Next once again. 

4.2.1.2 CAN − Step 2: Inserting a Display 221

In this window, you will connect the new display with the panel object. So that you don't have to create the new 

panel object manually, the next dialog box offers the opportunity to create it by simply entering a new object 

name in the input field. This new panel object is then automatically connected to the new display. In this 

example, enter the name 'canpanel' in the input field. Click on OK to acknowledge. 

Automation Studio now has all necessary information and creates the new panel object. It is already correctly 

connected with the display being used. Hardware assignment, as you are probably accustomed to when using 

I/O variables, no longer needs to be taken care of separately for the panel object. 

Depending on the type of CPU being used, a dialog box appears like the one shown here. It displays system 

settings that have changed for the Visual Components project. We don't really need this information in this 

example so simply close the dialog box with OK. 

The newly created panel object is immediately opened for editing: 


222 4.2.1.2 CAN − Step 2: Inserting a Display


Go back to the main Automation Studio project window for a moment to see which changes have been made to 

the project. 

As you can see, the Wizard has not only created your new panel object with the name "canpanel", it has also 

added all the necessary drivers and system modules to the project. For some target systems, system settings 

must also be changed. This is done automatically. All changes made to the configuration are shown for your 

information. 

You have now completed all necessary preparations and can continue to the next step where you will begin 

programming the controller and setting up pictures for the visualization. 

4.2.1.3 CAN − Step 3: Inserting PV Variables 

In this step, you will create a few variables for the example project. The following two possibilities exist for this: 

4.2.1.3 CAN − Step 3: Inserting PV Variables 223

• Inserting Using the Variable Declaration Dialog Box 

• Inserting a Cyclic Task 

4.2.1.3.1 Inserting Using the Variable Declaration Dialog Box 

In the Software view, right click on CPU. Choose Declaration from the shortcut menu. This opens the dialog box 

for declaring variables. 

Place the mouse pointer anywhere in the empty area of the variable list. Right mouse click and select New 

Variable from the shortcut menu. Enter the name of the variable to be used. In this case, it will be called 

"IOValue". Pressing "Enter" creates the variable. 

Now double−click in the "Type" column to specify the data type for the variable. 

Choose data type UDINT for an unsigned 32−bit integer value and confirm with OK. 

Now create a second variable with the name "LedCtrl" of data type USINT. Your variable declarations should 

now look like this. 

Now close the declaration dialog box. 

To save memory, variables are only sent to the controller if they are used in at least one control task. To meet 

this requirement, we will create a very small task in Automation Basic which uses these variables. 

Right click on CPU and choose Insert Object... from the shortcut menu. 


224 4.2.1.3 CAN − Step 3: Inserting PV Variables


This will open the Insert Object Wizard. 

Select "Cyclic Object" to add a user task to the project. Confirm your selection by clicking Next. The next window 

of the Insert Object Wizard is displayed. 

4.2.1.3 CAN − Step 3: Inserting PV Variables 225

Enter the name "dummy," set the type to "B&R Automation Basic", and select the resource "Cyclic #4 − [10 

ms]". Confirm your selection by clicking Finish. 

A new editor window for entering source code for the new task is displayed. Enter the source code seen below 

in the image: 

Save your input by clicking on the icon in the toolbar and then close the editor window. 

Both of these variables now suffice for this example. In an actual project, the variables would not just be 

assigned to themselves. Instead, they would normally be used as calculation elements for the control tasks. 

We have now created the necessary variables and can move on to the Next Step. 

4.2.1.3.2 Inserting a Cyclic Task 

Advanced users can use a programming language to insert a cyclic task in the system. The variables to be used 

are created according to the programming language which is used. For our example, we will use a simple ANSI 

C task. In this programming language, the variables are defined as a part of the source code. 

In the following, you can see the necessary C source code which defines the same variables used in the 

previous section. For information about integrating an ANSI C task, please refer to the Automation Studio Help. 

/* Begin C Source */ 

#include 

#include 

_GLOBAL UDINT IOValue; 

_GLOBAL USINT LedCtrl; 


226 4.2.1.3 CAN − Step 3: Inserting PV Variables


_INIT void C_Prog_init(void) /* Init Procedure */ 

{ 

IOValue = 0; 

LedCtrl = 0; 

} 

_CYCLIC void C_Prog_cycle(void) /* Cyclic Procedure */ 

{ 

} 

/* End C Source */ 

4.2.1.4 CAN − Step 4: Applying Global Settings to Visual Components 

If you double−click on the "canpanel" panel object in the software view, the Visual Components editor opens 

with the global project options showing. 

For this simple example, no special settings are required. We can continue directly to the next step. 

4.2.1.5 CAN − Step 5: Inserting an Input Field 

In this step, you will insert a simple input field. 

The input field has to be inserted into a picture. Visual Components has already created the first picture for you 

which you only have to select as shown below. By doing so, the Visual Components editor display switches to 

the picture editor for the 'INIT_PIC' picture. 

4.2.1.4 CAN − Step 4: Applying Global Settings to Visual Components 227

As soon as the picture editor is shown, it can be arranged according to requirements. We would like to insert an 

input field. To do so, click on the icon in the toolbar. 

Select Input Numeric from the menu which appears. The cursor changes into a crosshair pointer. Now you only 

have to left click on the location in the image where you want to insert the input field. 

The following configuration dialog box is shown after the input field is placed: 


The variable dialog box appears after clicking on the Assign... button in the Data Point area. In this dialog box, 

select the "IOValue" variable by double−clicking on it. 

228 4.2.1.4 CAN − Step 4: Applying Global Settings to Visual Components


"IOValue" is now assigned as the data point in the "Input Numeric" dialog box. After confirming the dialog box 

with OK, the input field is displayed in the picture editor. The input field can be moved around in the picture at 

any time. In this example, move the field to the right side of the second line. 

In addition, write the static text "Input:" before the field. To do this, select the text icon in the toolbar and 

place the cursor in the desired position. A dialog box will then open for you to enter the desired text. After 

confirming the input with the 'Enter' key, the dialog box can then be closed by clicking on OK. Further details 

concerning static text can be found in its respective section. 

The picture should now look similar to the one shown above. 

4.2.1.6 CAN − Step 6: Inserting an Output Field 

In this step, you will insert a simple output field. To do so, select the icon in the toolbar. 

After selecting Output Numeric from the menu, click on the desired location in the picture editor where you want 

to place the output field. 

4.2.1.6 CAN − Step 6: Inserting an Output Field 229

The configuration dialog box for the output field is then opened. By clicking the Assign... button in the Data Point 

area, you can once again select the 'IOValue' variable from the list. 

Confirm with OK. 


Now place the text 'Output:' before the output field as described in Step 5. Your picture in the editor should now 

look something like this: 

230 4.2.1.6 CAN − Step 6: Inserting an Output Field


4.2.1.7 CAN − Step 7: Connecting an LED with a Process Variable 

In this step, you will add an LED to the project which can be operated from the control application. To achieve 

this, the LED is connected with a variable from the control application. 

Right click on the round area of the F1 key in the Key window and select LED Control from PLC from the menu. 

This opens the following dialog box: 

The LED Control from PLC mode is already preset. In the Data Point area, open the variable dialog box with the 

Assign... button and assign the 'LedCtrl' PV which will be responsible for the blink status of the LED. 

In the next step, you will define the function keys used to manipulate the 'LedCtrl' PV. 

4.2.1.7 CAN − Step 7: Connecting an LED with a Process Variable 231

4.2.1.8 CAN − Step 8: Defining INC/DEC Keys 


In order to manipulate the "LedCtrl" PV which has direct influence on the F1 LED blink status, we define F2 as 

an increment key which raises the "LedCtrl" variable by one value per keystroke (maximum 3). F3 will be set up 

as a decrement key. It will reduce the PV by one value per keystroke (minimum 0). 

First, the F2 function key must be set with the increment/decrement function. For this, right click on the F2 key in 

the Key window (but not within the LED). Select Increment/Decrement from the shortcut menu. 

A dialog box appears which provides a more exact definition of all necessary function parameters. 

The Data Point area under the Parameter tab determines which PV should be manipulated. Select the 'LedCtrl' 

PV from the variable dialog box which appears after you have clicked on the Assign... button. 

Under the Function tab, activate the Use Limits option to define the maximum as 3. This is because an LED can 

only have 4 different states (0−3). The Increment rate is defined as 1. We confirm our selections with OK, and 

232 4.2.1.8 CAN − Step 8: Defining INC/DEC Keys


now our F2 function key is completely configured. 

Configuring the F3 function key takes place in the same way except for the Increment rate setting under the 

Function tab. Select an Increment rate of −1 for the F3 function key. 

Now, the LED status can be manipulated in ascending order with the F2 key (off (0) −> on (1) −> blinking (2) −> 

fast blinking (3)) and in reverse order using the F3 key. 

In the next step, you will compile the project and transfer it to the controller. 

4.2.1.9 CAN − Step 9: Compiling and Transferring the Project 

Save the changes to the project and close the panel object. Now you are ready to compile the project and 

transfer it to the controller. 

Click on the icon in the toolbar to compile the project. This doesn't just affect the panel object; all 

components in the project that have been changed or added are compiled. Compilation progress is displayed. 

4.2.1.9 CAN − Step 9: Compiling and Transferring the Project 233

If the compilation was successful, then the following dialog box prompts you to transfer the project. Just click on 

Transfer and Automation Studio transfers all necessary components to the controller. 

A progress indicator is displayed once again while the project is being transferred. 

The configuration of the controller is updated if it has changed or hasn't been set yet. Since the controller has to 

be restarted for this, the following dialog box is shown: 

Confirm with Yes to update the configuration and transfer the project to the controller. 

After compiling and transferring the project, you will see the start picture of the "INIT_PIC" panel object on the 

target system display. The input field blinks since it has the focus. In the next step, you will test the application 

that you have just created. 

4.2.1.10 CAN − Step 10: Test Operations 

After you have transferred the project to the controller, the picture you have configured should be displayed on 

the CAN operator panel screen. You have implemented the following functions in your first project: 

4.2.1.10.1 Input Field / Output Field 

The numeric keys on the display can be used to enter values in the input field. The values are accepted by 

pressing 'Enter'. Pressing a numeric key changes to input mode. The input value is displayed directly in the 

output field below for checking. 

4.2.1.10.2 Changing the LED Status 


The 'F1' LED key blinks depending on the "LedCtrl" variable value. This value can also be monitored and/or 

manipulated by the 'Watch' function in Automation Studio. 

234 4.2.1.10 CAN − Step 10: Test Operations


4.2.1.10.3 Increment/Decrement 

The 'LedCtrl' variable can be changed using the 'F2' (increment) and 'F3' (decrement) keys. This changes the 

'F1' LED status during runtime. 

You are now familiar with the essential steps involved in creating a Visual Components project. Other functions 

can be found in the online help. 

4.2.2 Compact IPC2002 − Example 

Creating a Visual Components application is described in the following steps with special emphasis given to 

graphic elements (button, bitmap, ListBox) as well as input using a touch display (HotSpot, button). In this 

example, the target platform is an IPC2000 Compact with a VGA touch display. 

Other touch displays than the one given in the example can also be used since the defined elements of 

individual pages can also fit on smaller displays (1/4 VGA). Larger displays can also be used problem−free. An 

IPC5000 with a suitable touch display can also be used in place of an IPC2000. 

Note: 

If you use different hardware than is suggested here, make sure that you select the correct hardware in the 

Visual Components project. This must always match the hardware which is actually used! 

This example application is divided into the following sections: 

1. Creating a New Automation Studio Project 

2. Inserting a Display 

3. Inserting PV Variables 

4. Applying Global Settings to Visual Components 

5. Adding Pages 

6. Adding Bitmaps 

7. Creating a Text Group 

8. Creating HotSpots for Page Changing 

9. Page 1: Inserting a Dynamic Bitmap 

10. Page 2: Inserting an Ellipse whose Fill Color Can Be Dynamically Changed Using Input 

11. Page 3: Inserting a ListBox with Control Buttons 

12. Compiling and Transferring the Project 

13. Testing Functions 

4.2.2.1 IPC − Step 1: Creating a New Automation Studio Project 

First, start a new project using Automation Studio. For this, select "New Project..." from the "File" menu. This will 

start the Project Wizard. Use "vc_ipc" as the project name (max. 8 characters). Proceed by clicking on the Next 

button in the Wizard. 

4.2.1.10 CAN − Step 10: Test Operations 235

Next, the CPU to be used must be selected. For this, select a "1A4601.02" CPU from the IPC2000 series. 

Continue by pressing the Next button. 

All selected settings are summarized one more time in the final view. The Wizard is ended once you click on 

Finish. 

The new project is now ready to go. 

4.2.2.2 IPC − Step 2: Inserting a Display 

The easiest way to begin a new visualization project is to insert the desired display. 


To do so, right click in the empty space to the left of the 'Display' label in the hardware tree and select Insert... 

from the shortcut menu. 

236 4.2.2.2 IPC − Step 2: Inserting a Display


A list of all supported displays is displayed. Select the entry '5D2210.0C' from this list for a Compact IPC with a 

10.4 inch VGA color display with touch screen and confirm by clicking OK. 

In the 'Enter Panel Name' dialog box, the new display is connected with a panel object (Visual Components 

project). So that you don't have to create the new panel object manually, the dialog box offers the opportunity to 

create this by simply entering a new object name in the input field. This new panel object is automatically 

connected to the display which is already inserted. In this example, enter the name 'ipcpanel' in the input field 

and confirm the input with OK. 

4.2.2.2 IPC − Step 2: Inserting a Display 237

Automation Studio now has all necessary information and will create the new panel object. It is already correctly 

connected with the display being used. Hardware assignment, as you are probably accustomed to when using 

I/O variables, no longer needs to be taken care of separately for the panel object. 

The configuration dialog box is displayed after the inserted panel and touch display are defined. 

Settings are accepted with 'OK'. 

The newly created panel object is immediately opened for editing: 


238 4.2.2.2 IPC − Step 2: Inserting a Display


Go back to the main Automation Studio project window for a moment to see which changes have been made to 

the project. 

As you can see, the Wizard not only created your new panel object with the name "ipcpanel", it has also added 

all the necessary drivers and system modules to the project. For some target systems, system settings must 

also be changed. This is done automatically. All changes made to the configuration are shown for your 

information. 

You have now completed all necessary preparations and can continue to the next step where you will begin 

programming the controller and setting up pictures for the visualization. 

4.2.2.3 IPC − Step 3: Inserting PV Variables 

In this step, you will create a few variables for our example project. The following two possibilities exist for this: 

• Inserting Using the Variable Declaration Dialog Box 

4.2.2.3 IPC − Step 3: Inserting PV Variables 239

• Inserting a Cyclic Task 

4.2.2.3.1 Inserting Using the Variable Declaration Dialog Box 

In the Software view, right click on CPU. Choose Declaration from the shortcut menu. The variable declaration 

dialog box is now open. 

Place the mouse pointer anywhere in the empty area of the variable list. Right mouse click and select New 

Variable from the shortcut menu. Enter the name of the variable, in this case "Bmpldx". Pressing "Enter" creates 

the variable. 

Now double−click in the "Type" column to specify the data type for the variable. 

Choose data type UINT for an unsigned 16 bit integer value and confirm with OK. 

Now define the rest of the variables as shown in the following image. 

To save memory, variables are only sent to the controller if they are used in at least one control task. To meet 

this requirement, we will create a very small task in Automation Basic which uses these variables. 

Right click on CPU and choose Insert Object... from the shortcut menu. 


240 4.2.2.3 IPC − Step 3: Inserting PV Variables


This will open the Insert Object Wizard. 

Select Cyclic Object to add a normal task to the project. Confirm your selection by clicking Next. The next 

window of the Insert Object Wizard is displayed. 

4.2.2.3 IPC − Step 3: Inserting PV Variables 241

Enter the name "dummy," set the type to "B&R Automation Basic", and select the resource "Cyclic #8 − [10 

ms]". Confirm your selection by clicking Finish. 

A new editor window for entering source code for the new task is displayed. Enter the source code seen below 

in the image: 

Save your input by clicking on the icon in the toolbar and then close the editor window. 

These variables now suffice for this example. In an actual project, the variables would not just be assigned to 

themselves. Instead, they would normally be used as calculation elements for the control tasks. 

We have now created the necessary variables and can move on to the Next Step. 

4.2.2.3.2 Inserting a Cyclic Task 

Advanced users can use a programming language to insert a cyclic task in the system. The variables to be used 

are created according to the programming language which is used. For our example, we will use a simple ANSI 

C task. In this programming language, the variables are defined as a part of the source code. 

In the following, you can see the necessary C source code which defines the same variables used in the 

previous section. For information about integrating an ANSI C task, please refer to the Automation Studio Help. 

/* Begin C Source */ 

#include 

#include 

_GLOBAL UINT BmpIdx; 

_GLOBAL USINT LBCurIdx; 

_GLOBAL USINT LBSelIdx; 

_GLOBAL USINT LBButtonDown; 

_GLOBAL UINT ObjColor; 

_INIT void C_Prog_init(void) /* Init procedure */ 

{ 

BmpIdx = 0; 

LBCurIdx = 0; 

LBSelIdx = 0; 

LBButtonDown = 0; 

ObjColor = 0; 

} 

_CYCLIC void C_Prog_cycle(void) /* Cyclic procedure */ 

{ 

} 

/* End C Source */ 

Once the C task has been inserted, we can proceed to the next step. 

4.2.2.4 IPC − Step 4: Applying Global Settings to Visual Components 


If you double−click on the "ipcpanel" panel object in the software view, the Visual Components editor opens with 

the global project options showing. 

242 4.2.2.3 IPC − Step 3: Inserting PV Variables


For this simple example, no special settings are required. We can continue directly to the next step. 

4.2.2.5 IPC − Step 5: Adding Pictures 

This project should be composed of a total of 3 pictures. One of these pictures is automatically generated and 

defined as the start picture of the project when the project is created. This picture is called 'INIT_PC'. In this 

step, you will add two additional pictures so that three pictures are available overall. 

To do this, right click on Pictures in the Visual Components project tree. Select "New" from the shortcut menu 

which appears. 

A new item is then entered under the Pictures node. A picture name must now be entered. Give this picture the 

4.2.2.5 IPC − Step 5: Adding Pictures 243

name 'PAGE2'. 

Repeat this procedure to create "PAGE3". 

At the end, the project tree should look like the one shown above. 

Before you can configure the 3 pictures, a few preparations must be made in the next steps to guarantee their 

planned functionality. 

4.2.2.6 IPC − Step 6: Adding Bitmaps 


Since a dynamic bitmap is eventually created on Page 1 ("INIT_PIC"), the bitmaps which will make up that 

dynamic bitmap must be inserted first. 

In case you noticed the two bitmaps already present in the project tree, they offer interactive touch input, where 

touching an input field inserts the appropriate bitmap automatically. For this reason, these two bitmaps are 

added automatically when the project was created. 

But now to the bitmaps that you need. Basically, it is possible to add any bitmap. It should be noted however, 

that all bitmaps which are used together in a dynamic bitmap must have the same pixel size. In this example, 

simply use the monochrome bitmaps included. 

First, you must right click on the Bitmaps tree node. A shortcut menu with the New entry appears. Select this 

entry using a normal mouse click. 

244 4.2.2.6 IPC − Step 6: Adding Bitmaps


Since you want to use bitmaps which already exist, select Load Bitmaps from Files in the next dialog box and 

click on the Browse... button. 

The standard Windows File Open dialog box is displayed to select the bitmaps. Change to the 

AS\VCSamples\VC_Demo1.pgp\pgm\NEUERIPC\CPU\VisualComponents\vis2\ subdirectory which is within the 

directory where you installed Automation Studio. There you will find some bitmaps which can be used in the 

project. Highlight these and then click on the Open button (click on the first bitmap and then press and hold the 

Shift key while you click on the fifth bitmap. This selects all the bitmaps at one time). 

The program switches back to the Project view where you can see the inserted bitmaps. 

4.2.2.6 IPC − Step 6: Adding Bitmaps 245

Under the Bitmaps node, you now see your five inserted bitmaps in addition to the 2 default bitmaps. If you click 

on the Bitmaps node, a list of the bitmaps and some details (i.e. size in pixels and bytes) are shown in the right 

hand window. 

4.2.2.7 IPC − Step 7: Creating a Text Group 


Two text groups are needed to label buttons and act as a data source for the planned ListBox on Page 3 of the 

example project. 

To insert a new text group, right click on the TextGroups project tree node. Select New from the shortcut menu 

which appears. 

A new item should be inserted under TextGroups. A name must be given for this text group. In this case, enter 

the name 'TG1' for text group 1. Confirm the input with the Enter key. 

246 4.2.2.7 IPC − Step 7: Creating a Text Group


A table appears on the right side for entering texts into the selected text group. A text entry consists of the text 

number in the current group and the actual text. 

To insert a text, simply press the Ins key. 

This opens the 'Text Input' dialog box. Just enter 'Text1' in the input field and confirm by clicking on the OK 

button. 

The first entry now appears in the table. Repeat this procedure until the table appears as shown in the image 

below: 

For the button labels, create a second text group with the name 'TG2' and insert the following text: 'Up', 'Down' 

and 'Enter'. To do so, repeat the steps that were described for the 'TG1' text group. 

4.2.2.7 IPC − Step 7: Creating a Text Group 247

The entries 'TG1' and 'TG2' should now appear in the project tree under TextGroups. Clicking on either of the 

text groups displays its contents in the right−hand window. These texts can be modified at any time. 

4.2.2.8 IPC − Step 8: Creating HotSpots for Changing Pictures 

Before configuring the individual pictures, you should first set up navigation between them. In this example, a 

simple switch sequence is implemented in the order 'INIT_PIC' −−> 'PAGE2' −−> 'PAGE3' −−> 'INIT_PIC' −−> 

etc. 

Since a touch display will be used, an area must be defined on each page for triggering the page change by 

touch. In Visual Components, these areas are known as 'HotSpots'. HotSpots are rectangular, invisible areas on 

a page, which can be assigned the same functions as 'real' function keys. It could therefore be said that 

HotSpots, as well as touch buttons, are virtual function keys. 

To insert a HotSpot on the 'INIT_PIC' page, click on the 'INIT_PIC' entry under Pictures in the project tree. The 

blank area of your first page appears in the right−hand window. 

Click on the icon in the toolbar and select HotSpot from the menu. 


248 4.2.2.8 IPC − Step 8: Creating HotSpots for Changing Pictures


The cursor changes to the positioning crosshair . Set your editor window in such a way that you have the 

bottom right corner in the picture (if necessary, use the scrollbars on the right−hand and bottom edges of the 

editor window). Click a little ways to the upper left of the lower right corner (in the editor area) and drag the 

corresponding rectangle to the lower right corner while holding the left mouse button down. Once there, release 

the mouse button. 

Now a rectangle is located in the lower right corner as shown in the following image. 

Other fields are also placed in the picture using the same method as the HotSpot: After selecting the desired 

field, the mouse marks the area in the picture which should be covered by this field. 

Now click on in the toolbar to change back to editor mode. The mouse pointer assumes its original form 

again. Clicking on the HotSpot now causes black squares to appear on the border which can be clicked and 

dragged to change the size of the HotSpot. The cursor also changes to 'move' mode if it is placed over the 

HotSpot while it is 'active'. When this is the case, you can move the HotSpot by holding down the left mouse 

button and 'dragging' it. 

Using these editor functions should allow you to position the HotSpot exactly in the lower right corner if it is not 

already there. 

Now right click on the HotSpot. Select Object Properties from the shortcut menu. 

The HotSpot object dialog box appears. Switch from the Parameter tab to the Action tab. The Key Type field 

contains supported functions which can be triggered when the HotSpot is touched. Select the entry 'Change 

Picture' from the list. 

4.2.2.8 IPC − Step 8: Creating HotSpots for Changing Pictures 249

Another field called Target Picture appears. It contains all of the pictures present in the current project. Select 

the picture from there which should be switched to when the HotSpot is triggered. In this case, select 'PAGE2' 

since INIT_PIC (the page containing this current HotSpot) should switch to 'PAGE2'. 

Click on OK to confirm this setting. 


To simplify the procedure for the other 2 pages, copy the HotSpot using the tool. Then switch to 'PAGE2' by 

clicking on it in the project tree. Paste the HotSpot using . It appears in the upper left corner of the page. 

250 4.2.2.8 IPC − Step 8: Creating HotSpots for Changing Pictures


Drag the HotSpot to the lower right corner, as explained above. Open the 'Object Properties' dialog box and 

change the target page to 'PAGE3' under the Action tab. Follow the same procedure for 'PAGE3'. Here, you will 

set 'INIT_PIC' as the target page. 

In order to make the picture−changing function recognizable in the picture, write 'Next−>' in the rectangle 

covered by the HotSpot. In this way, the picture can be changed by touching the text while the visualization 

application is running. 

To do this, select the text icon from the toolbar. The cursor changes to the positioning crosshair . Click 

in the left area of the rectangle. The Text Object dialog box appears and prompts you for text entry. Type 

'Next−>' and confirm with 'Enter'. Then close the dialog box by clicking 'OK'. 

Switch back to editor mode by selecting from the toolbar. You can now properly align the text as you did 

before with the HotSpot if it didn't look quite right when it was inserted. 

Copy the text (same method as copying HotSpots) with Copy −> Paste on each of the other pages so that the 

HotSpots there can also be made 'visible'. 

4.2.2.9 IPC − Step 9: Page 1 (INIT_PIC) − Inserting a Dynamic Bitmap 

After all the preparations in the previous steps, all requirements have now been met to allow us to begin 

arranging the first picture of the example visualization. Our goal is to insert a dynamic bitmap object into the 

picture and to select the currently displayed bitmap using 2 buttons. 

For this, switch to the first picture 'INIT_PIC' (click on it in the project tree). Nothing should be visible on this 

4.2.2.9 IPC − Step 9: Page 1 (INIT_PIC) − Inserting a Dynamic Bitmap 251


page except the HotSpot inserted earlier for the page change. Click on the icon for output objects in the 

toolbar. Select Output Bitmap Graphic from the menu. 

The cursor switches to the positioning crosshair . Click on the center of the page. This opens the Bitmap 

Graphic dialog box. Upon opening, the table in the Bitmaps area is blank. Using the Add button, you can insert 

bitmaps which are present in the project into the list (see Step 6). When you click on Add, a combo box appears 

which contains all available bitmaps. Select the first one. Repeat this process until all five bitmaps appear in the 

table. 

Now a variable still has to be specified which is responsible for determining which bitmap should be currently 

displayed. This can be done by clicking on Assign... in the Data Point area. 

This opens the Variable dialog box. Expanding the 'GLOBAL' node displays the variables inserted in Step 3. 

Click on 'Bmpldx' and confirm the selection by clicking OK. 

252 4.2.2.9 IPC − Step 9: Page 1 (INIT_PIC) − Inserting a Dynamic Bitmap


The Bitmap Graphic dialog box should now look like this: 

Confirm the input by clicking OK. 


In the editor window, you now see the first bitmap from the list of bitmaps defined earlier. Switch back to editor 

mode by clicking on in the toolbar. If you click on the bitmap now, then it becomes highlighted and can be 

moved. 

In order to see later which bitmap (index) in the list is current, insert a numeric output field underneath the 

dynamic bitmap object. 

For this, click on the Output symbol in the toolbar and select Output Numeric. 

Using the positioning crosshair, click underneath the bitmap object. 


In the Output Numeric 'Properties' dialog box which appears, the field must still be connected with the 'Bmpldx' 

variable. To do so, you can use the field in the Data Point area to select the variable instead of having to use the 

Variable Dialog Box. It contains variables which are already being used in the visualization project. 

254 4.2.2.9 IPC − Step 9: Page 1 (INIT_PIC) − Inserting a Dynamic Bitmap


Once the dialog box looks like the one shown here, confirm your input with OK. Adjust the position of the input 

field in the editor so that it is centered directly below the bitmap object. 

Since you have a dynamic bitmap object and an output field which contains the current index, you now need to 

insert two touch buttons (one to the right of the bitmap, and one to the left) so that the index can actually be 

changed. 

Touch buttons are handled the same way as HotSpots except for their visual appearance. Therefore, if 

something is unclear to you in the following paragraphs, read over Step 8 again. 

Touch buttons are inserted by selecting 'Touch Button' from the menu after clicking on the 'Touch Key' icon in 

the toolbar. Now draw a button (just like with a HotSpot) to the left of the bitmap object. Choose the size in such 

a way that the key can later be operated easily on the touch screen. 

Open the 'Object Properties' dialog box for the button and switch to the Appearance tab. You are able to set the 

visual appearance of the button here. 

The font and border width should not be changed in this example. The button label must naturally be adjusted. 

To do so, select the entry 'TG2' from the Text Group combo box in the Released Button area. All texts from text 

group 'TG2' are now contained in the Text combo box. Select 'Down'. 

Do the same thing for the Pressed Button area. 


Once the dialog box looks like the one shown above, switch to the Action tab. Once there, select the 

'Increment/Decrement' entry from the Key Type combo box. 

Further settings for this key type will then appear. In the Data Point area, select 'Bmpldx' from the Source combo 

box to use it as the variable to be manipulated. In addition, activate the Use Limits option. Restrict the value 

range using Limit Min 0 and Limit Max 4. Then set the Increment to −1 (the variable is therefore decreased by 

one with each activation of the button). 


Now copy the 'Down' button and insert a copy of it to the right of the bitmap. Then edit the copy so that 'Up' is 

selected as the text under the Appearance tab, and the Increment under the Action tab is set to 1. In this way, 

the button increases the 'Bmpldx' variable by 1 when pressed. 

Now the center of the 'INIT_PIC' looks like the following image. 

4.2.2.10 IPC − Step 10: Page 2 − Ellipse with a Dynamic, Changeable Fill Color 

In the next picture, 'Page 2', you will draw an ellipse whose fill color can be changed during runtime using a 

variable. 

First, we will draw the ellipse. To do this, select the icon from the toolbar. With the positioning crosshair, 

'drag' the ellipse to any size somewhere near the center of the page. 


256 4.2.2.10 IPC − Step 10: Page 2 − Ellipse with a Dynamic, Changeable Fill Color


Then open the 'Object Properties' dialog box for the ellipse and switch to the Colors tab. Switch off the Use 

Global option, select the Fill property, and connect the 'ObjColor' variable with the ellipse using the Assign... 

button in the Colors Variable area. Confirm your input by clicking OK. 

Next, insert a numeric input field underneath the ellipse. To do this, select the input icon from the toolbar and 

choose the Input Numeric entry from the menu that appears. 

Click underneath the ellipse with the positioning crosshair to position the input field. The 'Input Numeric' dialog 

box appears. Connect the input field in the Data Point area to the 'ObjColor' variable using the Source combo 

field. 

4.2.2.10 IPC − Step 10: Page 2 − Ellipse with a Dynamic, Changeable Fill Color 257

After confirming the input with OK, 'PAGE2' should look like the following image: 

4.2.2.11 IPC − Step 11: Page 3 − Inserting a ListBox with Control Buttons 


A ListBox is created on 'PAGE3' (the third and final picture). In addition to highlighting the current item, this 

ListBox allows the currently selected item to be rewritten to another variable in the form of its index. 

First, insert the ListBox. To do this, select the output symbol in the toolbar and the ListBox entry from the menu. 

258 4.2.2.11 IPC − Step 11: Page 3 − Inserting a ListBox with Control Buttons


Using the positioning crosshair, 'drag' the ListBox a little bit to the left of the center of the picture. The size is not 

important right now since you will set it it the 'Object Properties' dialog box. When you have drawn the ListBox, 

open the 'Object Properties' dialog box. 

Select the Gfont2x2 font from the Font combo box in the Appearance area at the very top of the Parameter tab. 

Set Max. Text Length to 8 and Rows to 6. The ListBox now has a maximum width of 8 characters and is 6 lines 

high. 

Text group 1 ('TG1'), which was set a few steps earlier, will be the data source. For this, choose the entry 'TG1' 

from the Text Group combo box found in the Source of Texts area. 

Now the variable which is responsible for the currently selected entry has to be set. This is controlled by the 

index, i.e. the numeric value of the variable corresponds to the position of the text in the text group. To do this, 

select the 'LBCurldx' variable using the Assign... button in the Selected Item area. 

When you are finished with the settings, confirm with OK. 

Now create two buttons with the function 'Increment/Decrement' and label them 'Up' and 'Down'. Connect these, 

as well as a numeric output field with the 'LBCurldx' variable. These elements are created as described in Step 

9. For the output field, you should also use the 'Gfont2x2' font. The limits for the function 'Increment/Decrement' 

must correspond to the number of texts in the 'TG1' text group (10), so they should be set from 0 to 9. 

Tip: 

You can also copy the respective screen elements from 'INIT_PIC' and paste them in the picture. Corresponding 

changes can then be made to the settings. In this way, many similar fields in a project can later be created 

quickly and efficiently. 

You should then have an picture like the one shown here. 

4.2.2.11 IPC − Step 11: Page 3 − Inserting a ListBox with Control Buttons 259

Now you will add the function which copies the index of the current selection to an additional variable when a 

key is pressed. 

First you will need a touch button whose Key Type under the Action tab is set to "Momentary USINT". In the 

Data Point area, select the variable 'LBButtonDown' using the Assign... button and enter the number 1 as Value 

1. This button function means that the 'LBButtonDown' variable keeps the value 1 as long as the button is 

pressed down on the screen. If the button is released, then the variable is set back to the value 0. 

Under the Appearance tab, choose 'Enter' from the Text combo box. 


Next to the new 'Enter' button, add a numeric input field which is connected to the 'LBSelldx' variable. The value 

of the currently selected entry is stored in this variable after the 'Enter' button is pressed. 

The finished picture is shown in the following image: 


260 4.2.2.11 IPC − Step 11: Page 3 − Inserting a ListBox with Control Buttons


The Automation Basic task 'dummy' has to be expanded a bit for the 'Enter' button to function properly. The 

variables are now executed in the Init−SP part of the task. The Init−SP part can be shown if you move the 

'splitter' on the upper border of the source code window to the middle (see image). 

The IF condition is true so long as the 'Enter' button is pressed. Then the contents of the LBCurldx variable 

(which contains the current index of the ListBox) are copied to the LBSelldx variable which is displayed in a 

separate output field in this example. In a real application, this type of function could be used for loading or 

saving a recipe. 

This ends the configuration process of the example project. The next step concerns compiling and transferring 

the project to Automation Runtime. 

4.2.2.12 IPC − Step 12: Compiling and Transferring the Project 

Save the changes to the project and close the panel object. Now you are ready to compile the project and 

transfer it to the controller. 

Click on the icon in the toolbar to compile the project. This doesn't just affect the panel object; all 

components in the project that have been changed or added are compiled. Compilation progress is displayed. 

4.2.2.12 IPC − Step 12: Compiling and Transferring the Project 261

If the compilation was successful, then the following dialog box prompts you to transfer the project. Just click on 

Transfer and Automation Studio transfers all necessary components to the controller. 

A progress indicator is displayed once again while the project is being transferred. 

The configuration of the controller is updated if it has changed or hasn't been set yet. Since the controller has to 

be restarted for this, the following dialog box is shown: 

Confirm with Yes to update the configuration and transfer the project to the controller. 

After compiling and transferring the project, you will see the start picture of the "INIT_PIC" panel object on the 

target system display. In the next step, you will test the application that you have just created. 

4.2.2.13 IPC − Step 13: Test Operations 

After you have transferred the project to the controller, the 'INIT_PIC' start page which you configured should be 

displayed on the IPC screen. You have now implemented the following functions in your project: 

4.2.2.13.1 Page 1: Dynamic Bitmap 

The first picture contains a dynamic bitmap which can be adjusted using the two touch buttons located on its left 

and right sides. The number of the currently displayed bitmap is shown in the output field underneath the bitmap 

object. 

Using the HotSpot in the lower right corner takes you to 'PAGE2'. 

4.2.2.13.2 Page 2: Ellipse with a Dynamic Fill Color 

This picture displays an ellipse which is filled in with the color which is numerically represented by the input field 

located directly underneath it. The input field must be pressed to change the value. A numeric keypad is then 

opened to enter the value. After confirming the entry, the ellipse is displayed with the selected color. 

Using the HotSpot in the lower right corner takes you to 'PAGE3'. 

4.2.2.13.3 Page 3: ListBox with Selection Confirmation 

This picture contains a ListBox with 10 items, 'Text1' to 'Text10'. 6 texts are displayed simultaneously. The 

selected item is changed using the "Up" and "Down" buttons (the selection bar moves up or down). The output 

field between the buttons shows the index of the currently selected item. Using the 'Enter' button, the currently 

selected item or index can be saved to another variable which is connected to the output field on the right side of 

the 'Enter' button. 

Pressing the HotSpot in the lower right corner takes you back to Page 1 − the 'INIT_PIC'. 


262 4.2.2.13 IPC − Step 13: Test Operations


4.2.3 Getting Started with the VISAPI Programming Interface 

This section contains an introduction to the Visual Components programming interface. Using this interface, 

many interesting additions can be created which cannot be configured using the Visual Components editor (i.e. 

trend). 

Interface functions are called using either functions or function blocks. Calling methods depend on which 

programming language is used. Our examples, which are written in C and Automation Basic, use functions. 

This section is for new users of the Visual Components programming interface and contains basic steps for 

interface "start−up", including simple function calls which execute character functions. 

Knowledge of Automation Basic or the C programming language is necessary in this section. If you do not 

possess this knowledge, please refer to the corresponding section of the Automation Studio documentation. 

These are the individual steps of the application example: 

1. Inserting a Visapi Library 

2. Inserting a Cyclic Task 

3a. C Example Part 1 

3a. C Example Part 2 

3b. Automation Basic Example 

4.2.3.1 Visapi − Tutorial − Inserting the Visapi Library 

The Visapi interface is integrated as a library in the Automation Software. The Library Manager must therefore 

be opened first to insert the Visapi library into your project. 

To do this, click on Open in the menu bar and select Library Manager from the menu. 

The Library Manager window appears on the screen. The 'runtime' library is already visible in the library tree. 

This is the standard library inserted in each Automation Studio project. Now the necessary Visapi library must be 

inserted into the existing library list. 

To do this, click on the Insert menu and select the Library entry. 

4.2.3 Getting Started with the VISAPI Programming Interface 263


The Insert Library dialog box is displayed. Select the Add Library option and search for the Visapi library in the 

library list. Select it with the mouse and then click OK. 

If this was done properly, you should see the Visapi library in the left−hand window of the Library Manager. If the 

Visapi tree is expanded, then all library functions are displayed. Now click on any function to display its 

parameters in the right−hand window. Pressing the F1 key takes you directly to the corresponding help for the 

selected function. 

264 4.2.3 Getting Started with the VISAPI Programming Interface


4.2.3.2 Visapi − Tutorial − Inserting a Cyclic Task 

In this step, you will insert a cyclic task which will execute your special character commands using Visapi 

functions. 

Switch to the software view of your Automation Studio project. Click on CPU and then select Insert Object.... 

4.2.3.2 Visapi − Tutorial − Inserting a Cyclic Task 265

The "Insert Object" dialog box opens up. 

Select Cyclic Object and then click on Next. 

First, you will select a name for your task in the 'New Object' dialog box which appears. Use 'Visu' for this 

example. In addition, you can select the desired programming language for this task in the Type combo box. For 

this example, you can choose either 'B&R Automation Basic' or 'C Language' (ANSI C); therefore, choose 

whichever you prefer. 

Lastly, select the desired task class under Resource (for this example, preferably 'Cyclic #3 − [50 ms]') and 

confirm all of your selections with the Finish button. 

Choose your next step depending on whether you selected Automation Basic or C: 

Automation Basic Example 

C Example 


266 4.2.3.2 Visapi − Tutorial − Inserting a Cyclic Task


4.2.3.3 Visapi − Tutorial − Automation Basic Example 

After the Automation Basic task has been inserted, Automation Studio opens up the editor for input and is ready 

to create the new task. 

A rectangle, a line, and an ellipse should be drawn in this example. A text should also be output. 

To do this, input the following program code in the Initialization part of the task (Init−SP): 


x1 = 100 

y1 = 150 

x2 = 250 

y2 = 250 

height = 40 

width = 80 



ready = 0 

Now input the following program code for the cyclic part of the task: 


If ready 1 Then 

VC_HANDLE = VA_Setup(1 , "vga") 

If VC_HANDLE 0 Then 

ready = 1 

EndIf 

EndIf 

If ready = 1 Then 

If VA_Saccess(1,VC_HANDLE) = 0 Then 

VA_Rect(1,VC_HANDLE,x1,y1,x2,y2,fill,color) ;Draws a rectangle 

VA_Line(1,VC_HANDLE,x1,y1,x2,y2,color) ;Draws a line 

VA_Ellipse(1,VC_HANDLE,x2,y2,heigth,width,fill,color) ;Draws an ellipse 

;Outputs a text 

VA_Textout(1,VC_HANDLE,1,100,100,color,fill,"A rectangle, a line, and an ellipse") 


EndIf 

EndIf 

You can naturally use the Windows Clipboard to copy this source code into Automation Studio. 

Declare the variables to be used as shown in the following image: 

4.2.3.3 Visapi − Tutorial − Automation Basic Example 267

The program is very short and constrained on purpose to encourage experimentation. It would be best to 

compile the program now and load it to Automation Runtime. But first change the 'vga' string variable in the 

VA_Setup function in the cyclic part and replace it with the name of the visualization project to which output 

should take place. 

Expand the program to include more output or change the parameters either in the program or using the Watch 

command in Automation Studio. If necessary, use the Visapi Documentation in the reference manual to refer to 

details. 

The following is a brief overview of the example code: 

• Some variables are defined in the Initialization part of the task which mostly serve as place holders for 

the position and color of the elements to be drawn. An exception is the ready variable. This variable 

makes a note of whether the Visapi library was completely and successfully initialized. 

• Using VA_Setup, the first part of the program establishes a connection to the Visual Components 

interpreter or to its management routine (aplib.br), the runtime. This is necessary, since both the 

interpreter and the Visapi functions access the same resources, and accessing these resources must be 

managed. 

• If the function is successful, a unique VCHandle is returned. This is necessary since several Visual 

Components projects can run at the same time. Therefore an exact differentiation must be made 

regarding the destination of the Visapi functions (to which project and also to which display). 

Subsequently, the handle must be transferred with every other Visapi function. 

• If VA_Setup fails (returns 0) , then the function in the example is called cyclically until a valid handle is 

returned. As soon as VA_Setup was successfully executed and a handle is available, the ready 

variable is set to 1 and the actual working part of the task is 'released'. 

• Once a handle is available, then the panel resources are requested using VA_Saccess. It is possible for 

drawing operations to be carried out only after a successful call (return value is 0). 

• If the panel resources can be successfully requested with VA_Saccess, then the drawing function can 

be called. The function names display the respective tasks, and parameters are listed in the 

documentation for the respective function in the reference manual. 

(Click the corresponding function in the Library Manager and press F1 to receive help). 

• Finally, the resources are released by the program with VA_Srelease. 

Warning: 

Only call VA_Srelease if VA_Saccess has returned 0. 

Warning: 

Always call VA_Srelease if VA_Saccess was successfully executed! Otherwise the Visual Components 

editor can no longer output to the display and the visualization freezes. 

4.2.3.4 Visapi − Tutorial − Preparing the C Example 


If you decided to use an ANSI C implementation, then a dialog box opens with the title 'Add C Files'. First you 

create a new C file which contains the program. To do this, input 'visu.c' under File Name (without the single 

quotes) and confirm with Add. 

268 4.2.3.4 Visapi − Tutorial − Preparing the C Example


To program in C, the necessary libraries must be added manually. For this, right click on the 'visu' C task that 

you inserted previously and select Insert File... from the shortcut menu. 

The 'Add C Files' dialog box appears again. To use Visapi library functions in our C task, the file 'libvisapi.a' and 

the header file 'visapi.h' must be added to the task. 

To find these files, switch from the CPU directory − where the 'visu.c' file is located − to three directories higher 

(with the icon in the dialog box). From here, change to the 'Library' directory and then to the 'visapi' directory. 

Depending on the type of CPU you are using, select the 'i386' directory (for Automation Runtime systems − 

IPC2000, IPC5000, and CP3xx) or the 'm68k' directory (for older CPU models). 

Mark both of the files named above and confirm with Add. 

4.2.3.4 Visapi − Tutorial − Preparing the C Example 269

The C editor is opened by double−clicking on the 'visu.c' file in the Software view. 

You will create the actual program in the next step. 

4.2.3.5 Visapi − Tutorial − Finishing the C Example 

A rectangle, a line, and an ellipse should be drawn in this example. A text should also be output. 

To do this, input the following program code in the 'visu.c' file: 

#include 

#include #include _LOCAL UINT ready; _LOCAL UINT x1; _LOCAL 

UINT x2; _LOCAL UINT y1; _LOCAL UINT y2; _LOCAL USINT fill; _LOCAL USINT color; _LOCAL UINT heigth; 

_LOCAL UINT width; _LOCAL UDINT VC_HANDLE; _INIT void Initialization(void) { x1 = 150; y1 = 100; x2 

= 100; y2 = 150; fill = 255; /* Transparent */ color = 0; /* Black */ heigth = 40; width = 80; ready 

= 0; } _CYCLIC void Cyclic(void) { if (!ready) { VC_HANDLE = VA_Setup(1 , "vga"); if (VC_HANDLE) ready 

= 1; } if (ready) { if (!VA_Saccess(1,VC_HANDLE)) /* Reserves access to the visualization */ { 

VA_Rect (1,VC_HANDLE,x1,y1,x2,y2,fill,color); /* Draw rectangle */ VA_Line 

(1,VC_HANDLE,x1,y1,x2,y2,color); /* Draw line */ VA_Ellipse 

(1,VC_HANDLE,x2,y2,height,width,fill,color); /* Draw ellipse */ /* Text output */ VA_Textout 

(1,VC_HANDLE,1,50,50,color,fill,"A rectangle, a line, and an ellipse"); VA_Srelease(1,VC_HANDLE); 

/* Releases the visualization */ } } } 

You can naturally use the Windows Clipboard to copy this source code into Automation Studio. 

The program is very short and constrained on purpose to encourage experimentation. It would be best to 

compile the program now and load it to Automation Runtime. But first change the 'vga' string variable in the 

VA_Setup function in the cyclic part and replace it with the name of the visualization project to which output 

should take place. 

Expand the program to include more output or change the parameters either in the program or using the Watch 

command in Automation Studio. If necessary, use the Visapi Documentation in the reference manual to refer to 

details. 

The following is a brief overview of the example code: 


• Some variables are defined in the Initialization part of the task which mostly serve as place holders for 

the position and color of the elements to be drawn. An exception is the ready variable. This variable 

makes a note of whether the Visapi library was completely and successfully initialized. 

• Using VA_Setup, the first part of the program establishes a connection to the Visual Components 

interpreter or to its management routine (aplib.br), the runtime. This is necessary, since both the 

interpreter and the Visapi functions access the same resources, and accessing these resources must be 

managed. 

• If the function is successful, a unique VCHandle is returned. This is necessary since several Visual 

Components projects can run at the same time. Therefore an exact differentiation must be made 

regarding the destination of the Visapi functions (to which project and also to which display). 

Subsequently, the handle must be transferred with every other Visapi function. 

• If VA_Setup fails (returns 0) , then the function in the example is called cyclically until a valid handle is 

returned. As soon as VA_Setup was successfully executed and a handle is available, the ready 

variable is set to 1 and the actual working part of the task is 'released'. 

270 4.2.3.5 Visapi − Tutorial − Finishing the C Example


• Once a handle is available, then the panel resources are requested using VA_Saccess. It is possible for 

drawing operations to be carried out only after a successful call (return value is 0). 

• If the panel resources can be successfully requested with VA_Saccess, then the drawing function can 

be called. The function names display the respective tasks, and parameters are listed in the 

documentation for the respective function in the reference manual. 

(Click the corresponding function in the Library Manager and press F1 to receive help). 

• Finally, the resources are released by the program with VA_Srelease. 

Warning: 

Only call VA_Srelease if VA_Saccess has returned 0. 

Warning: 

Always call VA_Srelease if VA_Saccess was successfully executed! Otherwise the Visual Components 

editor can no longer output to the display and the visualization freezes. 

4.2.4 Sample Projects 

Visual Components sample projects can also be installed when installing B&R Automation Software. These 

examples can be used as ideas for separate projects and for becoming acquainted with Visual Components. 

In the following sections, the sample projects delivered with Visual Components are described together with 

respect to the hardware used and the appropriate functions. 

Note: 

B&R Automation Software setup can be run at any time to install the example projects. 

Basic functions of Visual Components are shown in the example projects (Step 1 − Step 7). They indicate 

solutions for frequent terms when creating a Visual Components visualization application. 

4.2.4.1 Example: Step 1 

Project Name: BrAutomation\Samples\VisualComponents\Step1.pgp 

Target System: 4P0420.00−490 (4 lines of 20 characters, keys) PP21 

Contents: Start page, page change, simple input and output fields 

Remark: Scaling function for input/output field 



Target System: 4P3040.00−490 (320x240 pixels, keys) PP41 

Contents: 

Remark: 



Target 

System: 

Contents: 

Start page, page change, simple input and output fields, language switch, 

bitmap display, LED control, using a global picture 

Use of Up/Down input, LEDs are on/off/blinking/blinking fast, dynamic 

bitmap output using an ANSI C task 

IPC2001 (AR 2.61) with 5D2519.02 display (320x240 pixels, color display with keys) 

Start page, page change, simple output fields, simple selection using a ListBox, advanced text 

output 

Remark: Use of the LED and key matrix, language switching, Up/Down input, dynamic bitmaps 

4.2.4 Sample Projects 271


Project 

Name: 

Target 

System: 

BrAutomation\Samples\VisualComponents\Step4.pgp 


Contents: Start page, page change, simple recipe management 

Remark: 


Project 

Name: 

Target 

System: 

This example demonstrates simple recipe management using dynamic variables in an ANSI C 

task. Dynamic variables are used to change the input fields during runtime. 

In addition to the recipe system, other dynamic indications can be added. 



Contents: Start page, page change, simple output fields, trend recorder demonstration 

Remark: 


Project 

Name: 

Target 

System: 

Contents: 

The use of the VISAPI library is demonstrated with an ANSI C task which draws a trend curve on 

the display. The current picture number is ascertained using the PLC variable. 


IPC2001 Compact (AR 2.04) with VGA touch display (640x480 pixels, color) 

Start page, page change, bar graph demonstration, alarm system demonstration (with alarm list, 

alarm overview, and alarm history), screen saver function. 

Remark: The bar graph demonstration shows dynamic changing of variables. 

4.2.4.7 Example: Step 7 − CAN 


Target 

System: 

7CP476.60−1 (V 2.27) with CAN panel controller 4B1270.00−490 (4 lines of 20 characters, 

keys) 

Contents: Start page, LED matrix, sting input, scaling 

Remark: The LED matrix is accessed and set using input fields 

4.2.4.8 Example: Step 8 − VGA / CAN 


Target 

System: 

IPC2001 Compact (AR 2.61) with CAN panel controller 4B1270.00−490 (4 lines of 20 

characters, keys) 

Contents: Screen saver, bar graphs, ListBoxes 

Remark: The selected ListBox element is output on the CAN panel. 

4.2.4.9 Example: VC_Demo 

Project Name: BrAutomation\Samples\VisualComponents\VC_Demo.pgp 

Target System: IPC2002 Compact (AR 2.04) with VGA touch display (640x480 pixels, color) 

Contents: Demonstration Application 

Remark: Overview of Visual Components main elements 

− Input of numeric and alphanumeric characters using the touch display 

− Language switching 

− Setting date and time 


272 4.2.4.4 Example: Step 4


− Task visualization 

− Simple recipe management 

− Alarm system 

− Touch calibration 

− The VISAPI library functions are displayed using a character demonstration 

4.2.4.10 Example: VC_WebDemo 

Project 

Name: 

Target 

System: 

BrAutomation\Samples\VisualComponents\VC_WebDemo1 

IPC2002 Compact (AR 2.04) with VGA touch display (640x480 pixels, color) 


Remark: 

− Task visualization 


After the Brwebsrv.ini file is transferred to the target system (AR 2.04), the ASP files can be 

transferred to the Runtime. The files must be transferred to the 'Web' directory for this. 

To start the web application, a browser has to load the gesamt.asp page. 

Tested with IE 6.0 

Note: 

− A dongle is required to operate the Web Server module 

− Pay attention to the TCP/IP configuration on the target and Windows computers 

− Web Server pages must be transferred with FTP (−> Configuration files) 

It is recommended to have some experience with internet tecnologies! 

4.2.4.11 Example: VC_Alarm 

Project 

Name: 

Target 

System: 

BrAutomation\Samples\VisualComponents\VC_Alarm.pgp 

IPC2002 Compact (AR 2.61) with VGA touch display (640*480 pixels, color) 


Remark: 

The application shows the many capabilities of the alarm system. 

It is recommended to have previously read the Alarm System Documentation or to be familiar 

with it already. 

− Contents directory 

− Task simulation for creating alarms 

− Screen saver 

− Language switching − German/English 


* Alarm history with and without filters in various implementations 

* Alarm summary with and without filters 

* Alarm lists in 2 different designs with VISAPI function VA_GetAlCurPos 

* VISAPI function VA_GetAlarmlist 

* Complete overview of all alarms defined in the project and output field states 

* Alarm system text with variables − representation on individual pages 

4.3 Working with Visual Components 

This section of the User's Manual describes the Visual Components user interface within Automation Studio. 

This includes the division of the Visual Components editor windows and the individual editor views for the 

various resources of a Visual Components project. 

In this sense, resources mean the individual components which make up an entire visualization project. These 

include pictures, fonts, text groups, etc. These resources, as well as their corresponding Visual Components 

editors, are described in the following. 

4.2.4.10 Example: VC_WebDemo 273

4.3.1 Resource Types 

The resources in the editor are divided into the following elements which are grouped in the tree view on the left 

side. 

• Pictures 

• Variables 

• Text Groups 

• Bitmap 

• Fonts 

• Alarms 

• Languages 

All of the items listed above are managed in the Visual Components editor. These resources are located in file 

format in the directory structure of the project to be edited. All of these resources can be inserted, deleted, and 

edited using the editor. There is a specific editor for each resource type. 

4.3.2 Creating a Visual Components Project 

A Visual Components project is part of an Automation Studio project. Visual Components projects can be 

created by adding either hardware suitable for visualization or by adding a panel object and connecting it to the 

hardware. 

4.3.2.1 Creating a Visual Components Project 

There are two ways to create a project. The usual method begins by inserting visualization hardware. This 

automatically opens a Wizard which creates a visualization object and connects it to the hardware. 

This procedure is described in detail in the Getting Started section. 


The second possibility works by creating a software object. This can be assigned to a suitable hardware device. 

See Inserting a Panel Object on a PP21 Power Panel. 

A software object must be connected to a hardware object (display). This allows the hardware properties to be 

accepted by the Visual Components project. 

As shown above, the hardware object (panel '5D2210.0C') is assigned to the software object ('vis_al'). Any 

panel object in the AS project can be assigned in the 'Object Name' column. The first 6 characters of a panel 

object name must be unique in the project. Assignments should only be changed if there are several objects for 

this hardware in the project. 

Note: 

The software object (VC object) is automatically converted for the new hardware if the assignment is changed. 

Information may be lost when changing from VGA to 1/4 VGA! This data cannot be recovered. 

The Visual Components runtime module version is entered in the 'Version' column. All versions are displayed in 

this column. The highest version number indicates the most current state. Whenever a selection is made here, 

the required VC project drivers and system modules are updated. 

The 'Key Matrix Priority' column specifies the priority of the key driver in the system. In this way, the priority of 

jog key matrix updates can be determined by requesting them with the VISAPI interface. Therefore, the key 

driver can possibly interrupt cyclic tasks. Higher loads can negatively affect the runtime system (=cycle time 

274 4.3.1 Resource Types


violation). 

4.3.2.2 Inserting a Panel Object 

In addition to creating a panel object by adding hardware, the possibility also exists to create a software object 

and connect it to the hardware. 

The first step is to insert a new object in the right side of the project tree. 'Advanced Object' is then selected (see 

diagram). 

The name, object type ('Panel'), and resource ('Panel Objects') are defined in the next step. 

The Visual Components editor is then opened automatically. As you can see in the diagram, the software object 

is still not connected. 

4.3.2.2 Inserting a Panel Object 275

By assigning the panel object to a hardware object in the hardware tree, the Visual Components editor receives 

the necessary information for editing the visualization application. 

The Visual Components Editor then applies the properties of the connected hardware: 

Several software objects for a panel can be managed in one project using this method. This can be used to 

manage multiple visualization devices for one machine type. 

4.3.3 Creating Advanced Visual Components Projects 

Creating a complete application is described in the Introduction. Creating and managing a simple Visual 

Components project is explained here. Basic project management consists of a panel object connected with a 

display object − software and hardware. 

Advanced options for Visual Components project management involve using several software and panel objects 

in an Automation Studio project. This section aims to clarify the potential complexity of visualization solutions. To 

do this, the concept of object management is illustrated using software and hardware objects. Advantages of 

this solution will be demonstrated. 

Applications can be implemented in one of the following ways: 

• Several Software Objects and One Panel 

• Several Software Objects and Several Panels 


276 4.3.3 Creating Advanced Visual Components Projects


Both of these possibilities can also be used together. 

4.3.3.1 Several Software Objects and One Panel 

Several software objects can exist for one panel in an AS project. These software objects can be created as 

described in Inserting a Panel Object. 

Only the software object which is assigned to a display is executed on the target system. The object which is not 

used should be disabled. 

As shown below, the 'vis_al' software object is assigned to the display panel. This object is executed on the 

target system after it is downloaded. 

Reassignment in the selection list could also cause the 'vis_al1' object to be executed for a certain machine 

type. 

The first 6 characters of a panel object name must be different from all other object names in the project. This 

applies when several panel objects are managed within a project. 

4.3.3.2 Several Software Objects and Several Panels 

An AS project can also consist of several objects which are executed on different hardware. Possible examples 

of this might include: 

• Automation Runtime CPU with a VGA display visualization device and remote CAN panels 

• Automation Runtime CPU with several CAN panels 

The following consists of a VGA display, a 2x20 character CAN display (4B1270), and a 16x40 character CAN 

display. 

This view illustrates the complexity of possible Visual Components solutions. 

It allows a wide range of applications. This is how CAN panels can be used for temporary service purposes. For 

example, accessing the same variable base allows options to be enabled with a CAN panel. 

4.3.3.1 Several Software Objects and One Panel 277

Note for SG3 Automation Runtime System: 

When using multiple panel objects on an m68k CPU, performance problems can occur involving memory 

capacity and system configuration. 

In contrast to i386 target systems, memory capacity is limited on these CPUs. 

In addition, operating system configuration is kept to a minimum. In certain situations, it is necessary to increase 

the number of semaphores, AVT entries, and cyclic/non−cyclic objects. 

After first build of panel object the project system resources are automatically adjusted. Under certain 

circumstances, however, this can be insufficient with extensive projects. Contact B&R Support if problems 

occur. 

4.3.4 Editor Views 

The Visual Components editor has several views for editing pictures. All project resources are displayed in the 

tree view on the left. The corresponding editor is shown on the right depending on the selected project option. 

Picture editing is active in this view. The process picture can be seen in the upper−right. 

4.3.5 Picture Management 

Pictures can be added, deleted, renamed, and repositioned in the project using the Picture Manager. A picture 

stored in the manager can be edited using the Picture Editor. 

4.3.5.1 General Picture Management 


278 4.3.4 Editor Views


The Picture Manager is found in the 'Pictures' section in the upper left of the project tree. 

All of the pictures in a project are shown under 'Pictures'. Each picture can be individually named. For controlling 

purposes, pictures can also be selected by their picture number. In the view on the right, the number is shown 

above the picture name. 

All editing actions can be selected in the Picture Manager using a shortcut menu. Each picture has a few global 

properties which can be configured in the shortcut menu for the picture. A project can contain a total of 65,535 

pictures as long as enough memory is available. The number of picture commands, as well as a 'branch list' 

(over the keys), are displayed for the pictures. 

The pictures can be viewed sequentially using the "PgUp" and "PgDwn" keys. 

Picture management options are explained in the following section. The following actions can be carried out in 

the Picture Manager: 

• Adding a New Picture 

• Deleting a Picture 

• Renaming a Picture 

• Changing Picture Sequence 

• Changing Special Picture Properties 

• Defining the Start Picture 

• Defining the Global Picture 

4.3.5.2 Adding a New Picture 

A new picture can be inserted by selecting 'New' from the 'Pictures' 

shortcut menu. The 'Blank Page' icon can also be selected from the 

toolbar. 

A new picture icon is inserted in the tree view. The new picture must 

now be named. 

The name must be different from all other names in the project or an 

error message will appear. 

Picture names can have up to 15 characters and may contain spaces 

and other special characters. 

4.3.5.2 Adding a New Picture 279

Newly created pictures are always added to the bottom of the picture tree. If a new picture is created with the 

'INS' key, it will be inserted below the picture selected with the cursor. 

The project may contain a maximum of 65,535 pictures. 

4.3.5.3 Deleting a Picture 

A picture is deleted by selecting 'Delete' from its shortcut menu or by 

pressing the 'DEL' key. Deleting can be confirmed with 'OK' as long as 

removing the picture is possible. 

Exceptions: 

Pictures which are referenced by keys in other pictures cannot be deleted. 

In this case, the picture changing action must be switched to another 

picture first. This picture can be deleted once there are no longer any 

references to this picture. Open 'Binding...' from the shortcut menu, to see 

which pictures reference the picture to be deleted. 

The start picture cannot be directly deleted either. A new picture must first 

be configured as the start picture. Once this takes place, the previous start 

picture can be deleted. 

4.3.5.4 Renaming a Picture 

A picture can be renamed by selecting 'Rename' from the shortcut menu. The same rules apply here as when 

naming a new picture. (Max. 15 characters, unique name). 

Picture views and assignments from other pictures are updated with the new picture name. 

4.3.5.5 Changing the Picture Sequence 

The picture sequence is only used to assign picture numbers for the runtime system. Every picture on the target 

system can be accessed using its position in the picture sequence. When the position is changed, the picture 

number is also changed on the target system. For large projects, individual pictures can be grouped according 

to their functions. 

The start picture is always first in the sequence. As long as the start picture is configured as the start picture, its 

position cannot be changed. The sequence of all other pictures can be changed at any time. 

The sequence is changed using the arrow symbols. 

4.3.5.6 Changing Special Picture Properties 


Specific settings can be made for each picture using its 'Properties' dialog box. The Up/Down keys for input 

fields are also configured in this 'Properties' window. This dialog box is opened using the shortcut menu for the 

picture in the Picture Manager. 

280 4.3.5.3 Deleting a Picture


Use Global Background Color: 

In addition to the global background color, each 

picture can be defined an individual background color. 

(see also Color Settings) 

Use Global Picture: 

Elements predefined in the global picture can be 

applied to the current picture. This is only possible if a 

global picture is present. 

Enable Picture Change by PLC: 

This option enables the picture to be changed from 

the control application. 

A picture index can also be used. This determines the 

picture number which is written to the picture change 

address and the current picture number variable. 

Up/Down Keys: 

The Up/Down keys for input fields are specified in this 

window. Using Up/Down keys only needs to be 

specified in input fields. 

The number of elements in a picture is displayed in the command counter field. Up to 65,535 elements are 

possible in a picture. 

Warning: 

The number of elements has an effect on performance (speed) when displaying pictures on the runtime system. 

4.3.5.7 Defining the Start Picture 

The start picture is the first picture displayed after the controller is started. When a new project is created, a 

default picture called 'INIT_PIC' is always created by the Visual Components editor. If there are several pictures 

in a project, any of these could be configured later as the start picture. 

The start picture can be selected using a combo box in the global settings. 

4.3.5.7 Defining the Start Picture 281

4.3.5.8 Defining the Global Picture 

The global picture is intended as a type of template. This picture can be optionally added into any other picture. 

Picture elements which are to be used in most of the pictures are added to the global picture to prevent having 

to insert them repeatedly (logos, time, key assignment, etc.). This template can be applied to all pictures by 

selecting 'Use Global Picture' (see Changing Special Picture Properties). 

A picture named 'GLOBAL' is added to the picture list, if "Use Global Picture" is selected. The name of the 

global picture cannot be changed. 

4.3.6 Picture Editor 

The picture editor can be used for editing pictures which are located in the Picture Manager. It allows individual 

process pictures to be edited. Its function depends essentially on the picture objects. 

In the picture editor, individual objects of a picture are added and configured, and control variables are 

connected. This section describes general editor functions such as the grid, snap to grid, zoom settings, object 

selection, and other possibilities. 

A picture can contain up to 65,535 commands (static and dynamic objects on a picture for input and output). 

• General Picture Editor Operation 

• Grid and Snap−to−Grid Functions 

• Zoom Functions 

• Picture Editor Views 

4.3.6.1 General Picture Editor Operation 

All objects can be drawn, moved, and modified using the mouse. Special features using the mouse and shortcut 

keys are described here. 

Edit Mode 

Edit mode is enabled in the display editor shortcut menu. This is enabled by selecting the mouse icon (arrow) 

from the toolbar. 

Object Selection 

Several objects can be selected in the editor by clicking and dragging a box over them. Objects can be selected 

or unselected from the group of objects by holding down the 'CTRL' key and clicking on the object with the 

mouse. 

Key Functions 

The following keys have useful functions in the editor. 

• The 'TAB' key switches from the selected object to the next object. 'SHIFT' + 'TAB' reverses the 

sequence. 

• The 'Object Properties' dialog box is opened by pressing 'ALT' + 'ENTER'. 

• 'DEL' deletes a selected object. 

• One or more selected objects can be moved with the cursor keys. 

4.3.6.2 Grid and Snap−to−Grid Functions 


The picture editor provides the optional grid function for positioning objects. Objects can be automatically 

aligned to this grid (snap to grid function). 

282 4.3.5.8 Defining the Global Picture


4.3.6.3 Zoom Function 

The grid is adjusted by clicking the icon (grid). If this function is 

selected, then grid lines are shown on the display. The lines are colored 

light gray. 

Grid intervals are adjustable. The grid is not displayed at all zoom levels. If 

necessary, objects can be positioned on the grid. 

The properties dialog box for the grid and zoom settings are accessed by 

clicking on the grid icon shortcut menu. 

Objects which are placed, moved, or whose size has changed can be aligned 

if the 'Snap Moving Objects to Grid' option is set. If the function is enabled, 

then a check mark appears next to the menu item. 

Grid Spacing: 

The distance between grid lines can be adjusted in pixels 

according to height and width. 

Start Showing Grid at Zoom: 

The grid can be activated starting at a certain zoom level 

here. Zoom levels less than the level set here will not display 

the grid. 

A picture can be viewed as desired using the zoom function. This function is helpful when using much smaller 

displays (2x20 lines CAN) or much larger displays (1024x768 XGA). The display can be optimized to meet your 

requirements. 

The zoom function is controlled using the magnifying glass icons (zoom out / zoom in). 

The grid is displayed according to current zoom settings, as described above. 

4.3.7 Variable Editor 

The variable editor and the variable view show all the variables used in a Visual Components project. Two 

different views are available. One view is used to make changes. The second is only used for viewing. The 

variable selection dialog box is used for selecting variables. 

• Variable Editor 

• Variable View by Picture 

• Variable Selection Dialog Box 

4.3.7.1 Variable Editor 

4.3.6.3 Zoom Function 283

In the editor view, all project variables can 

be seen and changed if necessary. 

Variables can also be inserted here. 

All variables from this view always appear 

in the variable selection dialog box list. 

If a variable is changed or deleted in this view, it is also changed or deleted in the corresponding application 

objects! 

4.3.7.1.1 Insert variable 

A variable is inserted by pressing the 'INS' key. The variable dialog box is opened and a variable can be 

selected from the existing application program resources. It should be noted that some PLC variables are only 

available after compilation. Variables from IEC languages are immediately available (also see Variable Selection 

Dialog Box). 

The inserted variable is displayed in the overview. From this point on, it is available in the 'Data Point' combo 

boxes for individual objects. 

4.3.7.1.2 Delete variable 

A variable is deleted by selecting it and by pressing the 'DEL' key. If the variable is still in use, then a warning 

message is displayed. Once deleted, a variable is also removed from corresponding objects. This can also 

cause errors during compilation. 

4.3.7.1.3 Modify variable 

If a variable is used several times in a project, it can be changed to another variable in the variable dialog box. 

This can replace editing individual objects on different pages. 

Double−clicking on the variable name opens the variable dialog box with the current variable. Another variable 

can be selected from this window. 

Warning: 

It should be noted that not every variable data type can be connected to every field. Incorrect data type 

assignment causes an error when the project is compiled. 

4.3.7.2 Variable View by Picture 

Arranging variables according to picture allows for quick orientation within a project. This list can also be saved 

in an ASCII file and further edited. This list can be used for coupling an INA2000 client FBK to other B&R 

systems. 

The list view can be displayed for all or individual pictures. 

In the example above, the view has only been selected for the INIT_PIC. Selection is made by name in the 

combo box. 

The following information is displayed in the columns from left to right: 


284 4.3.7.1 Variable Editor


Picture Number on the PLC − This can be transferred to the control application during runtime. 

Picture Name − Used for informational purposes. 

Variable Name − The variable name in plain text − possibly with the task name placed in front (local variable). 

Variable Type − Specifies the data type and format of the variable. 

Access Type − Specifies whether the variable will be read or written in the visualization application. It is 

possible to write to and read from input fields. Output fields are only used to read. 

4.3.7.3 Variable Selection Dialog Box 

The selection dialog box supports variable selection from an Automation Studio project. The selection can be 

made using the data type and/or a task and variable name. 

This dialog box shows all available AS variables. They are displayed according to scope (task names), variable 

name, and data type. Complex data types, user defined types, and arrays can also be selected. Selection takes 

place using either the mouse or keyboard. 

Selection can be accelerated by activating the data type filter or by typing the name. 

4.3.8 Text Group Editor 

The text group editor is used for creating and managing text groups. Texts are integrated into groups for various 

reasons. 

Depending on requirements, these texts can be used for a dynamic text output field (Advanced Text Output), a 

ListBox, or for button labels. Text groups support language−switching. They are stored and managed in several 

languages. 

• Text Group Editor (Overview) 

• Inserting a New Text Group 

• Inserting a Text into a Text Group 

• Changing Texts in a Text Group 

• Deleting Texts and Text Groups 

• Arranging Texts in a Group 

• Variable Numbering of Text Groups 

4.3.8.1 Text Group Editor (Overview) 

4.3.7.3 Variable Selection Dialog Box 285

Text groups are managed in the tree view on the left side of the text group editor. Text groups can be inserted, 

renamed, or deleted. These actions can be done using the shortcut menus for the text groups. 

All the texts in a text group are displayed on the right side. Individual texts can be inserted, deleted, and edited 

here. A second text layer, 'English', is defined at the top next to the 'Default' language. Texts are automatically 

applied to all other text layers after a text is inserted for the default language. 

4.3.8.2 Inserting a New Text Group 

A new text group is inserted using the shortcut menu. If the text group view is active, then a new text group can 

also be added using the 'INS' key. 

4.3.8.3 Inserting a Text into a Text Group 

Text group names cannot have more than 20 characters. Each text group name 

must be unique. The name can be changed at any time as long as the text group 

is not used (i.e. connected with an output field or button). 

A text can be added to a specific text group via its shortcut menu or by pressing the 'INS' key. 


After selecting the 'Insert Text' menu item, a box is opened where text can be 

entered. When you are finished entering the, confirm by pressing 'Enter'. The 

new text is immediately displayed in the text view. 

The text number specifies the number which is used to display the text during runtime. This value is also 

contained in variables when used for 'Dynamic Text Output'. 

To insert more texts, the 'INS' key must be pressed or the mouse must be moved to the next line and 'Insert' 

selected from the shortcut menu. Text length is limited to 255 characters. All texts are only output as lines 

(line−oriented). Line breaks are not supported. 

286 4.3.8.2 Inserting a New Text Group


4.3.8.4 Changing Texts in a Text Group 

In the above example, the text in the default language has been used for all other text layers as well. If this text 

should be changed for the 'English' language, then the text editing window can be opened by double−clicking on 

the corresponding text. After the text is edited, the window is closed by pressing 'Enter'. The 'Esc' key retains the 

original text. 

Warning: 

If texts are added to existing text groups, objects which are connected with this text group may be affected. In 

some cases, inserting texts is only possible at the end of a text group. The connection between an object and 

the text group must then be lifted in order to insert desired texts. 

4.3.8.5 Deleting Texts and Text Groups 

A text is deleted by marking it and using the shortcut menu or by pressing the 'DEL' key. 

Texts which are already connected with objects cannot be deleted. The same restrictions apply for deleting texts 

as for adding texts. The connection to an object must first be removed or the object must be deleted. 

Deleting a Text Group 

The procedure for deleting a text group is the same as that for deleting texts. The following also applies here: 

text groups which are already in use cannot be deleted. 

4.3.8.6 Arranging Texts in a Group 

Texts can be moved up or down in a text group by using the arrow icons in the toolbar. Changing in this way 

automatically changes the index value (text number). 

As seen in the example above, other operations such as inserting, deleting, and editing can be done using the 

toolbar. 

Arranging Text Groups 

Text groups arrangement is not supported since their sequence is irrelevant to the project. 

4.3.8.7 Variable Numbering of Text Groups 

Text numbers for texts in a group can be edited and numbered flexibly. In this way, gaps in text groups are 

possible, i.e. if error messages should begin with number 1000. 

4.3.8.4 Changing Texts in a Text Group 287

Simply double−clicking on the text number to be changed allows it to be edited. If this text group is already 

connected with a ListBox element, then its numbers can no longer be changed. 

This allows the text group to be subdivided once more. 

Text numbers are limited by the UNIT data type. Numbers from 0 to 65535 can be entered. 

4.3.9 Bitmap Management 

Bitmaps are an essential part of visualization applications. The Visual Components editor supports monochrome 

bitmaps as well as those with a color resolution of up to 256 predefined colors. Not all displays can support this. 

A bitmap must be added to the Bitmap Manager before it can be inserted into a process picture as a background 

or dynamic bitmap. 

Note: 

Please click on the following button to start a demo: 

New bitmaps can be created using an external bitmap editor. Existing bitmaps can be edited at any time. 

• Bitmap Manager Overview 

• Inserting Bitmaps 

• Creating Bitmaps 

• Editing Bitmaps 

• Deleting Bitmaps 

• Creating Transparent Effects 

• External Bitmap Editor 

4.3.9.1 Bitmap Manager Overview 

The Bitmap Manager lists all bitmaps available in the project. 


288 4.3.9 Bitmap Management


All bitmaps are displayed in the project tree. The bitmap overview is displayed with the following information by 

clicking on the 'Bitmap' entry in the project tree. 

Name 

Bitmap name. Can be up to 20 characters long. Can't have the same name as another bitmap in 

the project. 

Size Size of the bitmap in pixels (length * width) 

Compiled 

size 

Size / Memory required for the bitmap on the target system. 

Index Bitmap index on the target system for the API interface. 

Note Indicates how often this bitmap is used in the project. 

Bitmaps can be displayed as monochrome or using up to 256 colors. Monochrome bitmaps are displayed on the 

target system using the current foreground and background colors. 

Color bitmaps can be used with 256 colors. When a new bitmap is inserted, its colors are automatically 

converted to this color table. 

Up to 32,000 pictures can be managed in a project. However, the number of pictures and the size of the entire 

project mostly depends on the amount of memory available on the target system. 

Bitmaps are stored in a project as a copy of the original in the Automation Studio − Visual Components project 

directory. 

4.3.9.2 Inserting Bitmaps 

Bitmaps can be inserted in the manager using either 'New' from the shortcut menu or by pressing the 'INS' key. 

Two possibilities exist in the 'Insert' dialog box: 

• Inserting existing bitmaps 

• Creating a new bitmap (using the external editor) 

Inserting a bitmap: 

Clicking on the 'Browse Bitmaps" button 

opens the Windows dialog box to insert 

bitmap files. 

Clicking on a bitmap file adds it to the 

project. Multiple bitmaps can also be 

selected and added simultaneously. 

However, only monochrome and 256 

color bitmaps can be inserted. 

4.3.9.2 Inserting Bitmaps 289

After they are inserted, bitmaps are converted to the Visual Components internal color palette. However, this 

may cause color distortions if, for example, many shades of the same color are used. 

A red rose contains more the 100 shades of red. However, Visual Components has only a few tones of red 

available. This could cause a distorted display. 

The 256 color limit is used because of the size of True Color bitmaps. 

4.3.9.3 Creating Bitmaps 

Along with adding bitmaps, new bitmaps can also be created directly from Visual Components. If this option is 

chosen, an external bitmap editor (i.e. MS Paint, CorelDRAW, etc.) must be available and configured on the 

development system. 

The same limits for inserting bitmaps apply for creating bitmaps. 

4.3.9.4 Editing Bitmaps 

4.3.9.5 Deleting Bitmaps 

Creating a new bitmap: 

After entering the bitmap name, width, 

height, and color depth (monochrome or 

256 colors), a blank bitmap is inserted 

by clicking 'OK'. 

The external bitmap editor specified in 

the Visual Components settings is also 

automatically started. 

This bitmap is visible in the editor after it 

is edited and saved. 

The external bitmap editor is started by either double−clicking on 

the bitmap or selecting 'Edit' from its shortcut menu. 

The external bitmap editor should already be configured. 

The bitmap must be completed using 'Save' rather than 'Save 

As...'. Otherwise changes are not applied in the project. 

Bitmaps are stored in a project as a copy of the original in the Automation Studio − Visual Components project 

directory. 

Bitmaps that are not used in the project can be deleted. Bitmaps which are used in a picture or object cannot be 

deleted. 

Bitmaps can be deleted by selecting 'Delete' from their shortcut menu or by pressing the 'Del' key. 

Warning: 

Both the bitmap entry in the manager and the bitmap file in the project directory are deleted. 


290 4.3.9.3 Creating Bitmaps


4.3.9.6 External Bitmap Editor 

The external bitmap editor must first be configured before it can be used. Configuration takes place under the 

'Project' tab after the 'VC Settings...' entry is selected from the 'Tools' menu. 

This field determines the file path for the 

bitmap editor. The 'Browse' button can be 

used to select a desired file. 

In this example, the Windows drawing program 'MS Paint' is used. This should be available on all Windows 

systems. 

Note: 

The program name and path is not always the same on all Windows versions! 

4.3.9.7 Transparent Bitmaps 

Transparent effects can be applied to bitmaps using the Visual Components editor. In other words, a specified 

color can be 'disabled' during runtime, i.e. shown with the background color of the display. 

4.3.9.7.1 How do transparent bitmaps work? 

This function is explained in the following example. 

The icon shown here to the right is 

used for the example. This icon has a 

white background. 

The icon should have a blue 

background since it is surrounded by a 

blue border. 

After activating Transparent mode, the 

white color of the icon is no longer 

displayed. This is how the background 

color is displayed during runtime. 

4.3.9.7.2 Creating transparent effects 

Transparent effects are configured in the bitmap view. 

4.3.9.6 External Bitmap Editor 291

The function is activated by selecting 'Use User's Transparent Color'. The color pipette (toolbar symbol) is then 

selected. 

Selecting the color which should be displayed as transparent is done by moving the mouse cursor (pipette 

shape) and clicking on the desired color. The transparent color is displayed in the corresponding field. 

White is now set as the transparent color. White pixels will not be displayed whenever this bitmap is used. 

4.3.9.8 Color Table 

To create visualization applications as effectively as possible while using the least amount of resources, Visual 

Component projects have a fixed color table for target systems with color displays. This color palette uses the 

standard used on the Internet/Web. The following is a list of all available colors. Bitmap editor colors can be 

adjusted using the RGB values. 

Colors are also displayed in the Visual Components Color Dialog Box. 

*) Index 255 is reserved for the display of transparent colors in a bitmap. 

4.3.9.8.1 Visual Components Color dialog box 

Color settings can be made in the editor 

using this dialog box. 

The tool tip (in yellow) displays the color 

index as well as the RGB value of the 

selected color. 

The dialog box completely corresponds to 

the target system color palette. The color 

index specification is also valid for 

character functions. 


292 4.3.9.8 Color Table


4.3.10 Font Management 

Using different fonts allows an individual arrangement of text information. Information can be better presented 

when different fonts are used. Important words can be displayed large and bold, for example. 

Visual Components allows the use of various fonts and supports familiar Windows True Type standard fonts. 

Therefore, the entire variety of Windows fonts can be used with Visual Components. 

Fonts are subject to copyright law and are the property of the authors. This is to be considered before they are 

used! 

Many freeware fonts can be found on the internet. 

Fonts cannot be loaded on all panels. Some panels only support one font size. 

Warning: 

Many fonts are copyrighted. Their use can be subject to certain license conditions. Using some fonts often 

requires payment. Legality should always be checked before using a font! 

• Fonts − General 

• Inserting Fonts 

• Changing Fonts 

• Deleting Fonts 

• B&R, Standard Fonts, and Windows... 

• More Information About Fonts 

4.3.10.1 General Font Management 

4.3.10 Font Management 293

A panel's default fonts are present in a new project. These fonts are displayed on the right side. Not all panels 

are the same. But at least one font is always supported by a panel. Different font sizes are supported in IPC 

projects, Power Panel projects, and projects using C130 graphic displays. Full graphic panels can also integrate 

other fonts created according to the True Type standard. 

Therefore, all Windows fonts can be used by Visual Components. 

Warning: 

Check copyrights! 

Certain editors (not included in Visual Components) can be used to create True Type fonts for use in Visual 


Currently, the following fonts are supplied by Visual Components: 


• GFont1x1 Character size 6 x 8 pixels 



Text Displays 

• TFont1x1 Character size 6 x 8 pixels 



4.3.10.2 Inserting Fonts 

Generally, only True Type fonts which are installed on the Windows system can be imported and inserted. 

Fonts are added to the project by selecting 'Insert' from the shortcut menu or by pressing the 'INS' key. 

A logical name must be given for every 

font. The name must not already be used 

in the project. 

After entering the name, a dialog box appears which lists all available fonts. 


294 4.3.10.2 Inserting Fonts


All fonts available on the system are displayed in the listbox. A specific font size can be selected with 'Size'. The 

'Pixel Size' line specifies the font size in pixels. This pixel size is very important for the use of fonts in a Visual 

Components application. 

The font can also be shown in bold or italic type. 'Char set' defines the character set for the font to be used. 

Text entered in the 'Sample String' box is also shown in the preview window. In this way, the appearance of the 

text can be checked. 

The 'Character Optimizing' option only transfers characters (from that font) which are used in the text. This 

saves memory on certain target systems. This option is not currently supported. The storage requirements of 

a character set can be improved when UNICODE character sets are used later. 

4.3.10.3 Changing Fonts 

Double−clicking on a font opens its selection and configuration dialog box. All settings can be changed as 

described in the Inserting Fonts section. 

Note: 

Your project is affected if fonts are changed which are already used in your pictures. The apperance changes. 

Texts can overlap or the length of a text can exceed the display size. In this case, an error message appears. 

The font will not be changed. 

The new size should not exceed the old. This prevents any potential display problems. 

4.3.10.4 Deleting Fonts 

Basic rule: All fonts which are not used can be deleted. 

Fonts which are used cannot be deleted. The respective text must first be set to another font. Then the font can 

be deleted. 

4.3.10.5 B&R, Standard Fonts, and Windows... 

B&R supplies separate fonts for individual panels. These fonts are adapted to the respective panel hardware. 

Some of these fonts are also stored in the panel hardware (Flash or ROM memory). 

The characters from 0 to 127 in these fonts correspond to the ASCII standard. Characters above 127 are not the 

same on all panels. 

Windows fonts also have different characters on the positions larger than 127. Only UNICODE character sets 

are subject to an exact world wide standard. 

The special characters of a certain font can be viewed and selected using the CharBox. 

The entire character set of a font is displayed in the CharBox. The number in the dialog box corresponds to the 

character offset in the character set. 

Due to the fact that characters over 127 do not correspond to a uniform standard, sometimes display problems 

occur in the editor when using particular fonts. On the target system, the correct character from the 

corresponding character set should always be seen. 

These display problems result from the fact that Windows controls are used in the editor. These are operated 

with the character font defined in the Windows system configuration. 

By changing the system font, the editor can be specialized to a certain character set. 

4.3.10.6 More Information About Fonts 

4.3.10.6.1 Freeware Fonts 

Many freeware fonts can be found on the Internet. Before using such fonts, check whether commercial use is 

really free of costs and obligations. 

Here are a few links to freeware font sites. 

4.3.10.3 Changing Fonts 295

http://www.flashkit.com/fonts/ 

http://www.fontasy.de/ 

http://freewarehome.com/Graphics/Fonts/Fonts_L−M_t.html 

http://www.rotodesign.com/fonts/fonts.html 

http://www.all−4−free.com/fonts/ ¬ Links to font sites (approx. 20 links) 

http://www.1001freefonts.com/ 

http://www.freefever.com/graphics/ 

http://www.hugemcgriffin.com/ 

http://fonts.tom7.com/ 

http://www.myfonts.com/ 

The web sites listed above are not guaranteed to be valid. Sources for freeware fonts can always be found in 

various search engines (Lycos, Fireball, Altavista, and Yahoo). 

4.3.10.6.2 Creating Fonts 

In addition to using freeware fonts, there is also the possibility to create True Type fonts. There are special tools 

for doing this which can be found in freeware and shareware programs such as FontCreator or TrueTypeEditor. 

Professional manufacturers such as Adobe and CorelDRAW also offer solutions for creating and editing fonts. 

These tools can also be used to modify existing fonts. 

4.3.11 Language Management 

Projects using several languages can be created with Visual Components. A project can contain texts from 10 or 

more different languages. 

Languages can be enabled and disabled in the Language Manager. Languages which are disabled are not 

included when compiling to the target system. This optimized target system memory. 

Languages are added and deleted using the Language Manager or the 'Languages' shortcut menu. 

A detailed explanation of language switching can be found in the Multilingual Project Capabilities section. 

Languages are switched on the target system by redefining a language variable. All text resources are 

automatically updated and output correctly. 

4.3.12 Color Configuration 

4.3.12.1 Setting Standard Colors 

Settings project colors is described in the following section. There are 3 ways to set colors: 

• Globally in the project 

• Specifically for an object 

• Dynamically for an object 

This sequence also represents the priority. Dynamic color control has priority over object specific assignment. 

Object specific assignments are individually explained in their respective sections. The global configuration is 

intended as a template. 

The editor itself always transfers the static setting from the last object when drawing a new object. In this way, 

several similar objects can more conveniently be drawn one after another. 

In addition to static colors, variables can also be used for assigning dynamic colors. 

Not all displays support colors or the specific handling of colors. 


296 4.3.10.6 More Information About Fonts


The number of available colors in a project is limited to 256. Depending on the target system, this can also be 

only 2 colors (monochrome displays). 

Global Colors: 

This setting applies to foreground and background color settings. All objects like texts, rectangles, circles, etc., 

are drawn using these settings. 

Global Colors Variable: 

Using this variable, color setting can be dynamically changed on the target system (see also Setting Dynamic 

Colors). 

Focus Colors: 

Colors are defined here for elements which currently hold the focus for input. This setting is valid for whichever 

input field is active. 

Focus Colors Variable: 

The color used for the input focus can also be dynamically modified. 

Color Objects: 

Specific color settings can be made for listed objects. For example, input and output fields, as well as alarm 

views, can be defined with fixed color values in a project. In this way, these fields are immediately recognizable 

to the end user as well as the project planner because of the color arrangement. 

Use Static Text's Transparent Color: 

With this option, a transparent effect can be applied to static texts. This means that text only uses its foreground 

color (text color) over the respective existing background. Text can be displayed on a bitmap using this method. 

Option Active: Option Inactive: 

4.3.10.6 More Information About Fonts 297

4.3.12.1.1 

4.3.12.2 Dynamic Color Control 

By connecting a process variable to the 'Colors Variable' field, the color of the respective object or the global 

color definitions can be influenced during runtime. The variable to be used must be at least 16 bits − thus, type 

INT or UINT. 

The higher value byte represents the foreground color (0−255). 

The lower value byte represents the background color (0−255). 

The text can be set to blink by simply swapping the variable bytes. 

If both bytes are set to the same value, then the text is hidden. 

The interval and combinations are dependent on the control application. 

Note: 

The appropriate color values can be found in the general color table. Specific colors can be read directly from 

the tool tips index value in the color dialog box. Not all panels provide the same colors. In each case, the table 

can be modified to specific user needs. 

Example: 

A brief example for dynamic color arrangement. 

Text blink effect: 

/* Task needs to run in a 100 ms task class */ 

#include #include /* Macros for foreground and background color 

definition */ #define VC_COLOR UINT #define COLOR(FOREGROUND, BACKGROUND) ((FOREGROUND


4.3.13.1 Exporting Pictures 

If complete pictures should be exported, then the picture has to be selected and the export function called in its 

shortcut menu. 

The name and directory where the export file should be saved is specified here. 

Other resources in the picture, such as bitmaps, fonts, and text groups, can also be exported using the export 

dialog box and the 'Export Dependency' field. In addition, each individually listed element can be selected or 

deselected for exporting. 

4.3.13.1 Exporting Pictures 299

The user receives a message when the export is successful. 

4.3.13.2 Importing Pictures 

Importing pictures can be selected using the shortcut menu for 'Pictures' in the pictures view. Pictures must be 

imported one at a time. 

First, the picture to be imported must be selected. 


If a picture already exists in the project with the same name, then the user is requested to enter a new name or 

the import is cancelled. 

300 4.3.13.2 Importing Pictures


A message is displayed when importing is successful. In addition, details about the import are displayed in the 

output window. 

Important: 

When importing/exporting fonts, it is important that the registered Windows font is installed on the computer 

doing the importing. This is necessary for it to be displayed in the editor. Only the properties of the font are 

imported or exported (size, Windows font name, bold, italics, etc.), not the font itself. 

File extensions for import/export files: 

Type Extension 

Pictures *.vcpXML 

Text Groups *.vctXML 

Bitmap *.vcbXML 

Fonts *.vcfXML 

Alarm Groups *.vcaXML 

4.3.14 Project Options 

Automation Studio includes separate global settings for Visual Components projects. These settings are only 

valid for the corresponding workstation (Automation Studio installation). They are not transported with the 

project. 

In addition to these global options, each project can be specifically configured. Each project−specific 

configuration is found on the start page of a Visual Components project. 

4.3.14.1 Project−Specific Configuration 

The configuration of project−specific properties (as opposed to individual picture configuration) is displayed on 

the global project configuration. To display this configuration, 'Panel' must be selected from the tree view. 

Configuration is divided between the following items: 

• Hardware 

• Picture Settings 

• Global Properties (+ Color Settings) 

• Alarm System 

• Touchpads 

4.3.14 Project Options 301

Details about individual configuration possibilities are described in the following sections. All of these options 

only apply to the current project. Not all options are available for all panels. Some options are only available 

when other options are enabled. 

Source: 

This field can be used to assign a process variable. This variable affects the chosen function. If an option is 

enabled, the corresponding combo box and button for selecting variables become available. 

4.3.14.1.1 Hardware 

The hardware description is shown in this field. This is only displayed for information purposes and cannot be 

changed. 

4.3.14.1.2 Picture Settings 


Init Picture: 

A start picture can be selected from a list of all the pictures in the project. The start picture is shown first after the 

system is switched on. 

The start picture always holds the first position in the picture list and always holds the number 0. It cannot be 

302 4.3.14.1 Project−Specific Configuration


deleted (see also Start Picture). 

ScreenSaver Pic: 

A picture can be selected as a screen saver from a list of all the pictures in the project. This picture is shown 

automatically after a specified amount of time has passed. Setting the time is explained in the following section. 

In contrast to conventional screen savers, this one does not automatically switch back to the picture displayed 

before it was activated. This must be set explicitly when configuring the application project. 

The time period before the screen saver activates is set in minutes. A variable from the controller can also be 

used to do this. Note that values have to be specified in seconds when enabling screen savers with RPS 

variables. Values < 60 are not allowed. 

This time begins after each time a key is pressed (phys. key or touch key). 

Activate Screen Saver: 

The screen saver mode is activated when this option is selected. 

Use Global Picture: 

A global picture can be selected for the project by selecting this option. A picture with the name "GLOBAL" is 

added to the picture list when this option is selected (see also Defining the Global Picture). 

Backlight Switch Off: 

The background light (or display) can be automatically shut off after a specified time by selecting this option. The 

time is set in minutes. 

Note: 

Not all panels support this option. 

Ignore First Key During Background Lighting: 

If this option is selected, only the background lighting is affected (turned on) when the first key is pressed. 

Otherwise, the first keystroke will carry out the task it was designed to do. 

Manual Project Start: 

If this option is selected, then a project cannot be automatically started on the target system. The project can be 

started after completing specific control application initializations. 

A special function block from the VISAPI interface is provided for this. This function block also supports specific 

CAN interface initializations for the project (see also VA_StartProject). 

4.3.14.1.3 Global Settings 

Transfer Key Matrix: 

This field enables the transfer of a key matrix to the control program. The status of all keys (0=not pressed, 

1=pressed) is transferred to a byte array in the PLC where it can be evaluated. 

The matrix also contains buttons for touch displays. Information is transferred asynchronous to the PLC program 

procedure. 

4.3.14.1 Project−Specific Configuration 303

Warning: 

This function is not suitable for jog key (momentary) operation. Jog keys have to be transferred using a VISAPI 

library function block (see also VA_GetKeyMatrix). 

Transfer LED Matrix: 

In addition to configuring LEDs individually, LED information can also be transferred using a byte array. 

However, only one method can be selected. Otherwise inconsistencies will occur. This information is read 

asynchronously. 

Change Picture From PLC: 

A certain picture can be selected from the control application using this variable. For example, this could allow 

certain pictures to be displayed or locked if an error occurs during runtime. If the picture change is successful, 

then the interpreter writes the value 65535 to this variable (handshake for picture change). This variable should 

only be defined once for a picture change (non−cyclic). 

The number of the next picture (to be changed to) can be read in the Picture Overview. 

Transmit Current Picture Number: 

The number of the currently displayed picture can be transferred to the control application. The picture number 

can be read in the Picture Overview. 

This number is changed when a picture is inserted or deleted. 

Enable Text Layer Switching: 

Text layers can be switched by the control application. Each text layer is assigned an index number in the 

Language Manager. This index number is the value for enabling a certain language. 

Transfer Current Key Level: 

Certain panels support up to 4 levels of key assignment. This active key assignment can be changed by other 

keys. The variable defined here gives information about which key assignment is active at the moment. 

Disable Cursor Movement On Enter: 

By default, the next input field is selected after pressing the Enter key. Using this option, the Enter key can be 

suppressed in the entire project. The cursor remains on the current input field after Enter has been pressed. 

This allows a new value to be given immediately. The next field is selected using appropriate Key Functions. 

Activate Alphanumeric Level: 

A keypad assignment level can be predefined for alphanumeric input. The runtime system recognizes 

alphanumeric entries and uses the defined key level. Alphanumeric characters must first be configured for this to 

function properly. 

Activate Automatic Comma Input: 

For input fields which contain decimal places, the entry is automatically advanced by the number of decimal 

places. If 2 decimal places are defined in a field, then an entry of 5−0−0 is converted to the value '5.00'. 

If this option is not selected, 5−0−0 is converted to a value of '500'. A decimal point key must then be defined (if 

not already). 

Colors: 

This button provides the default color settings of a project. 

Keyboard: 


A standard PC/AT keyboard can be defined as an input device when the 'AT Keyboard' option field is selected. 

The 'Layout' field defines which keyboard layout should be used. 

304 4.3.14.1 Project−Specific Configuration


4.3.14.1.4 Alarm System 

Use Alarm System: 

Enables the alarm system. This is explained in greater detail in the Alarm System section. By activating the 

alarm system, the alarm view immediately becomes available in the project tree. The icon for inserting alarm 

fields also becomes available in the picture editor. 

Use Alarm Printer: 

If this option is selected, then a printer can be defined for the alarm list. 

Printer Settings...: 

Specifies settings for printing alarms (see also Printing Alarms). 

4.3.15 Project Options 

Automation Studio includes separate global settings for Visual Components projects. These settings are only 

valid for the corresponding workstation (Automation Studio installation). They are not transported with the 

project. 

These settings are opened by selecting 'VC Options...' from the 'Tools' menu. 

In addition to these global options, each project can be specifically configured. Each project−specific 

configuration is found on the start page of a Visual Components project. 

4.3.15.1 Global Settings − General 

An external command (.EXE file) can be run on this page. This command is executed after a Visual 

Components compilation is carried out. 

This option is reserved for internal B&R purposes. 

4.3.14.1 Project−Specific Configuration 305

4.3.15.2 Global Settings − Project 

Bitmap/Font Editor: 

A bitmap editor can be defined here. This editor is used to create or edit bitmaps. Any bitmap program can be 

selected by clicking on 'Browse'. MSPaint is set as the default editor. Unfortunately, the name and directory are 

not the same on all systems. Therefore, it may be necessary to adjust this setting after installation. 

Compilation: 

Generate Text File: 

The editor generates detailed information about the project in the Automation Studio output window during 

compilation. In addition, a text file is created with debug information. This option is intended for internal B&R 

debugging purposes. 

Compilation is substantially faster if this option is deactivated. 

Generate Variables by Picture to CSV File: 

If this option is selected, then a CSV text file is created during compilation. The contents include the entire 

variable list sorted by picture. This file can be processed later to acquire variables. A small project is illustrated 

below: 

File contents: 

65535;< Global Variables >;UintVar1;UINT;W; 

65535;< Global Variables >;UsintArray;USINT[100];W; 

1;PIC1;BoolVar1;BIT;W; 

1;PIC1;DintVar1;DINT;R/W; 

The project: 


306 4.3.15.2 Global Settings − Project


4.3.15.3 Global Settings − Picture 

Initial Zoom: 

The editor uses this zoom setting when opening a project. Desired zoom levels can be set here. 

Grid − Settings: 

Settings for Grid Display are set here. 

Show Locked Character Positions: 

If text layers are active, then the longest text of a language is displayed in gray. This option is no longer 

supported. All outputs have object properties. The number of characters is defined there. 

Automatically Open Character Box: 

A character box (CharBox) is displayed for editing the text. 

Copy coordinates: 

Options where copied object are inserted after copy /paste. 

4.3.15.4 Grid − Settings 

Grid settings can be changed using the Grid Dialog Box. Grid settings can also be opened by clicking on the grid 

icon in the toolbar. 

4.3.15.3 Global Settings − Picture 307

Width: 

Adjustable grid width in pixels. 

Height: 

Adjustable grid height in pixels. 

Start Showing Grid at Zoom: 

Specifies at which zoom level the grid should be displayed. Using this option, the grid will not be displayed at 

lower zoom levels when different zoom levels are used. 

Show Grid as Default: 

Specifies whether the grid is automatically displayed when a project is opened. 

Touch Grid: 

This option creates a 40x40 pixel grid. This option is frequently used when working with touch devices. The size 

corresponds to an average finger width. 

Snap Moving Objects to Grid: 

If this function is selected, then objects which are created, moved, or changed can be directly aligned on the 

grid. This function is often indicated in graphics programs as 'Snap−to−Grid'. The 'snap' refers to the grid itself. 

4.4 Visual Components User's Manual 

4.4.1 Touch Configuration 

This allows interface settings for the display which is used to be changed. 


When inserting a display with touch functionality, the configuration dialog box is displayed after inserting the 

display name. 

308 4.4 Visual Components User's Manual


All interfaces which do not have serial devices assigned to them are listed in the box. Selecting the desired 

interface can be done using either the keyboard or the mouse. The selection is confirmed and saved with 

clicking 'OK' or pressing 'Enter'. 

4.4.1.1 Change Settings 

Touch settings can be changed in the display properties or the properties of the serial object. This touch 

configuration is required with old projects (V2.1) in order to assign the touch panel to an interface. 

Possibility 1: Display properties 

4.4.1.1 Change Settings 309

Possibility 2: Serial object properties 

The dialog box at the top of this page is shown. 

4.5 Arranging Static Picture Components 

Static picture elements are only drawn once during a picture change. In this way, system runtime behavior is 

only more heavily loaded during picture construction (picture change) than it would be with cyclic output of 

dynamic picture elements. There are exceptions such as when the status variable is used or active color 

assignment is made using a variable (see also Changing Colors Using Variables or Controlling Fields with 

Status Variables). 

Static picture elements can be placed at different layers using the editor. In the object shortcut menu, Bring 

Forward or Send Backward changes the display layer. (See Overlapping Objects). This overlap is then 

converted into a character sequence (picture structure) for the target system. 

Since certain elements such as circles, touch buttons, etc., cannot be used on all hardware, individual items 

may not be available depending on the display type (display disabled). 

Generally, every object (text, circle, etc.) has special object properties. Object properties are opened in the 

editor using the object's shortcut menu. Properties can also be opened using the keyboard by pressing 'Alt' + 

'Enter'. Pressing the 'Tab' key changes the focus to the next object. 

Static picture elements can be selected from the toolbar in the Visual Components editor. 

Symbol Function text 

4.5.1 Texts 

Selection tool 

Text mode 

Line mode 

Rectangle mode 

Ellipse mode 

Background bitmap mode 

Zoom in 

Zoom out 

Grid and snap−to−grid mode 

Static texts are available on all panels supported by Visual Components. However, the number of fonts and text 

sizes varies. At least one character set is always available for text. On some panels, additional fonts may 

integrated (see also Font Management). 

Language switching is possible for all static texts (see also Language Management). 

4.5.1.1 Inserting Text 

Select the icon on the toolbar to activate text mode. In this mode, the positioning tool can be placed 

anywhere on the display to insert a static text. 


310 4.5 Arranging Static Picture Components


Note: 

Static texts may not overlap. 

The text dialog box is automatically opened after adding a static text. 

4.5.1.2 Texts 

4.5.1.2.1 Editing Texts 

The static text is entered in this dialog box. Possible 

text length is already adjusted to the selected font. 

Input can be cancelled at any time by pressing the 

ESC key. A mouse click on another editor position 

also interrupts the editing process. 

Text is visible on the display after the 'Enter' key is 

pressed. Text can be changed at a later time by 

double−clicking on the text element. 

A different font can be selected after a successful 

entry has been made. If the font is changed, the 

length cannot exceed the display size. 

After the entry is completed, another text can be 

inserted by clicking somewhere else on the display. 

The last selected font is also used by default for new 

text entries. 

If several text layers are active, then they are shown 

by name in the first column. Text for this text layer is 

entered in the second column. 

A text object can only consist of one font. 

An existing text can be edited by activating the selection tool and double−clicking on the desired text. The 

corresponding editing window is opened. Double−clicking on the text layer name opens an additional text entry 

window. 

The CharBox is opened with this icon to input special characters. This allows special characters from 

the panel character set to be selected which cannot normally be input using the keyboard. 

The appearance of the character in the CharBox corresponds to its actual representation on the target system. 

The character also corresponds to its appearance on the target system in the picture editor. In the other dialog 

boxes and tables, different representations of some special characters can occur when using non−standard 

character sets. 

4.5.1.2 Texts 311

4.5.1.2.2 Text Position 

Text position is determined by the following factors. 

• Not every panel can position text with single pixel precision. 

• A 'Snap−to−Grid' mode can be set in the editor. 

The text can be moved using the mouse according to these possibilities. The mouse pointer position is 

displayed in the lower left corner of the editor. For better alignment, the snap−to−grid option can be selected or 

the grid can be displayed. The grid can be individually set. 

4.5.1.2.3 Selecting Texts 

Each text can be selected individually using the mouse. Multiple selection is possible by pressing the 'Ctrl' key 

and simultaneously clicking on the respective objects or dragging a box over them with the mouse. In this way, 

texts and other elements can be copied and inserted in another position or in another picture. Inserting always 

takes place with reference to the upper−left corner of the picture. 

Tip: 

If several texts are to be copied from a page and inserted in the same position on another page, a character can 

be inserted in the upper left corner of the source picture. If this character is also selected for copying, then all 

other texts will be inserted in the position they were in on the source picture. Then the character can be deleted 

from the top left of both pictures. 

4.5.1.3 Texts 

4.5.1.3.1 Text Color Settings 

Foreground and background colors can be defined during the design phase and runtime for static texts. The 

number of colors depends on the panel being used. The editor uses the limits of the corresponding panel type. 

There are 3 ways to assign color: 

• Global Color Setting 

• Individual Color Setting 

• Dynamic Color Setting Using a Variable 

The sequence listed above also determines the priority on the target system. Assigning a variable to an object 

has the highest priority. In this way, specific blink effects as well as displaying/not displaying text are possible. 

4.5.1.3.1.1 Global Color Setting for Text 

In the global color settings for the project, the global 

foreground and background colors are used by default 

for static text (in the Global Colors section). 

In this example, black text is placed on a white 

background. This global setting can be overwritten by a 

runtime system variable which can be conneted under 

Global Colors Variable. 

'Use static text's transparent color' only defines the 

foreground color for the editor. If the text is written on 

any background (i.e. bitmap), then only the characters 

are displayed. 

The background color can also be changed using this 

option. 

If this option is not selected, text is always output with 

foreground and background colors. 


312 4.5.1.2 Texts


4.5.1.3.1.2 Individual Text Colors 

Individual color settings can be made for each text 

object under Colors in the static text 'Properties' 

dialog box. 

By deactivating the Use Global option, individual 

Foreground and Background colors, as well as Use 

Transparent Color, become available. 

If transparent mode is selected, then only the 

foreground color is displayed. 

Settings made last are saved by the editor as a 

presetting for the next created static text field. In this 

way, several texts can conveniently be created using 

the same settings. 

4.5.1.3.1.3 Dynamic Text Colors 

Object colors can be changed during runtime by connecting a variable to the Colors Variable field. The variable 

has to be of data type UINT. 

The higher value byte represents the foreground color (0−255). 

The lower value byte represents the background color (0−255). 

The text can be set to blink by simply swapping the variable bytes. If both bytes are set to the same value, then 

the text is hidden. The interval and combinations are adjustable depending on the control application. 

4.5.1.3 Texts 313

Note: 

Corresponding color values can be found in in the Color Table. 

Specific colors can be read directly from the tool tips index value in the color dialog box. 

4.5.1.4 Texts 

4.5.1.4.1 Advanced Text Properties 

Changing the position of the text and modifying the connected status variable are both considered additional text 

properties. 

The position can be set exactly (in pixels) with the 

'Top' and 'Left' fields. On text panels, these 

specifications refer to rows and columns. These 

settings cannot be changed during runtime. 

The Status Variable is of data type UINT. For static 

text, bit 0 is responsible for determining whether the 

text is displayed or not. 

BIT 0 == 1 − Text not shown 

BIT 0 == 0 − Text shown 

Tip: 

Dynamic Text output provides additional possibilities for designing the visualization task. 

4.5.2 Lines 

Lines are used for arranging pictures in the Visual Components editor. 

Lines can be only be drawn with a width of 1 pixel. Not all panels support lines. Some panels only support 

horizontal and vertical lines. Slanted lines can only be drawn on graphic panels. This hardware limitation is 

taken into account by the editor. 

4.5.2.1 Drawing Lines 

The line mode is activated by selecting the line icon from the toolbar. The start point is determined by 

clicking the left mouse button in the display. The end point is set by holding down the left mouse button and 

dragging the positioning tool to the desired end position. 

Note: 

Some panels can only display horizontal and vertical lines. 

Line width is always 1 pixel. The line can later be moved or edited in the editor. If Ctrl is held down while drawing 

the line, then the editor will only allow a horizontal or vertical line to be drawn. If 'Snap Moving Objects to Grid' is 

activated, then the endpoint of the line can only be on an intersecting point of the set grid. A line can be deleted 

using the shortcut menu or the Del key. 

The 'Object Properties' dialog box is opened by double−clicking on the line. 


314 4.5.1.4 Texts


The position of the line can be set exactly (in pixels) 

under the Parameter tab. The Top, Left, Right and 

Bottom settings specify the position of the respective 

endpoint in pixels. 

The Status Variable is of data type UINT. For lines, bit 

0 is responsible for determining whether the line is 

drawn or not. 

BIT 0 == 1 − Line not shown 

BIT 0 == 0 − Line shown 

Basic colors for all lines can be set under the global 

color settings. These global settings apply to all lines 

which have this option selected. 

Lines may also have individual color settings. 

Individual colors can be selected by disabling the Use 

Global option. 

The optional variable in the Colors Variable field can 

change the line color during runtime. The variable has 

to be of data type UINT. 

The higher value byte sets the foreground line color 

(0−255). The lower value byte is not used. 

4.5.3 Rectangle and Square 

Rectangles can be drawn with any size and color using the editor. Not all panels support rectangles. Some 

panels cannot draw rectangles filled with color. This hardware limitation is taken into account by the editor. 

4.5.3.1 Drawing Rectangles 

Rectangle mode is enabled by selecting the rectangle icon from the toolbar. A rectangle can be drawn on 

the display in this mode by pressing the left mouse button. Drawing squares takes place while simultaneously 

holding down the Ctrl key while drawing. The line width for a rectangle is always 1 pixel. The position and size of 

the rectangle can be changed after it has been drawn. 

Double−clicking on the rectangle opens the Object Properties dialog box. 

A selected rectangle is displayed in the editor 

with a border. It can now be enlarged or 

reduced. 

As shown here, selection mode has to be 

active (mouse pointer icon). 

Right clicking on an empty area in the editor 

changes from selection mode to object editing 

mode. 

4.5.3 Rectangle and Square 315

4.5.3.2 Rectangle and Square 

4.5.3.2.1 Rectangle Properties 

Rectangles can be drawn in different colors with or without being filled. The 'Object Properties' dialog box is 

used for editing a rectangle. 

The 'Object Properties' dialog box is opened by double−clicking on a rectangle. 

The corner points of the rectangle can be set exactly 

(in pixels) by using the Top, Left, Right, and Bottom 

settings under the Parameter tab. 

Status variable 

The Status Variable is of data type UINT. For 

rectangles, bit 0 of the status variable is responsible 

for determining whether the rectangle is drawn or not. 

BIT 0 == 1 − Rectangle not shown 

BIT 0 == 0 − Rectangle shown 

Rectangle colors are globally defined using the 

foreground and background colors. The global setting 

applies to all rectangles which have the Use Global 

option selected. 

Rectangles may also have individual color settings. 

Specific colors can be selected by disabling the global 

settings. 

The rectangle is filled with the foreground color if the 

Fill option is selected. The background color is used 

for rectangle borders. 


change rectangle colors during runtime. The variable 

has to be of data type UINT. 

The higher value byte represents the foreground color 

(0−255). The lower value byte represents the 

background color (0−255). 


316 4.5.3.2 Rectangle and Square


4.5.4 Ellipse and Circle 

Ellipses and circles are static picture elements. They can be created in any size with individually adapted colors 

in the picture editor. Drawing circles and ellipses is not supported on all displays. This hardware limitation is 

taken into account by the editor if necessary. 

4.5.4.1 Drawing Circles and Ellipses 

Ellipses and circles can be drawn on the display by selecting the ellipse icon from the toolbar and clicking 

on the screen. Pressing and holding the mouse button defines the starting point of the ellipse. Releasing the 

mouse button defines where the ellipse is finished. 

Drawing circles is simplified by holding down the Ctrl key while drawing. The editor ensures that the height and 

width is the same and a circle is formed. The line width for a circle is always 1 pixel. The position and size of the 

ellipse can be changed after it has been drawn. 

Double−clicking on the circle opens up the Object Properties dialog box. 

A circle can be drawn over other existing static 

pictures. The circle is selected if a dashed rectangle 

can be seen around it. It can now be made larger, 

smaller, or be moved. Pressing the Del key deletes it. 

Static picture elements can be drawn in any desired 

layer. 

If necessary, an exact ellipse or circle can be drawn 

using the Grid or Snap−to−Grid Function. 

4.5.4.2 Ellipse and Circle 

4.5.4.2.1 Circle and Ellipse Properties 

Circles can be drawn in different colors with or without being filled. The 'Object Properties' dialog box is used for 

editing the properties of the circle. 

Double−clicking on a circle opens the 'Object Properties' dialog box. 

Under the Parameter tab, the corner points can be set 

for a circle or ellipse. For this, the enveloping 

rectangle can be defined in pixels using the Top, Left, 

Right, and Bottom settings. 

The Status Variable is of data type UINT. For ellipses, 

bit 0 is responsible for determining whether the ellipse 

is drawn or not. 

BIT 0 == 1 − Circle not shown 

BIT 0 == 0 − Circle shown 

4.5.4 Ellipse and Circle 317

Circle colors are globally defined using the foreground 

and background colors. The global setting applies to 

all circles which have the Use Global option selected. 

Each circles may also have individual color settings. 

Specific colors can be selected for the Foreground 

and Background by disabling the global settings. 

The circle is filled with the background color if the Fill 

option is selected. The foreground color is used for 

the border of the circle. 


change circle colors during runtime. The variable has 

to be of data type UINT. 

The higher value byte represents the foreground color 

(0−255). The lower byte represents the background 

color (0−255) − see also Changing Colors Using 

Variables. 

4.5.5 Arranging Static Picture Components 

4.5.5.1 Overlapping Static Objects 

Using static pictures, Visual Components provides the possibility to draw objects on multiple layers. These 

layers only apply during the design phase. During runtime, a character sequence is created from them which 

can no longer be changed. 

Each static object contains a shortcut menu with which the object can be moved one layer forward or backward. 

Basically, the order in which the objects were created determines the output layer. Starting from this point, the 

display can influence overlapping objects using the 'Bring Forward' or 'Send Backward' menus. 

Tip: 

Complex graphics should be created with a graphic program and saved as a 256−color bitmap. RGB color 

values should be considered for optimal results (see Color Palette). 

Examples: 

This symbolic illustration of a wrist watch consists of 4 

rectangles and a circle. 

The objects are appropriately placed with each other 

using the layer function so that they are displayed 

correctly. 

All objects can be selected and copied. 

Individual objects cannot be grouped or combined into 

one object. 

The properties of individual objects can be changed 

later. 

Tip: If problems arise while selecting objects, then the 

Tab key can be used to move to the next object. The 

Shift + Tab combination switches to the previous 

object. 

The Alt + Enter combination opens up the 

corresponding properties dialog box. 


318 4.5.5 Arranging Static Picture Components


Procedure for changing the position of an object: 

Select the desired object. 

The selection frame becomes visible. 

An object can be set to a different layer by selecting 

'Bring Forward' or 'Send Backward' from the shortcut 

menu. In this example, the marked circle is being set in 

the foreground. 

4.5.5 Arranging Static Picture Components 319

4.5.6 Background Bitmaps 

In this view, the circle is now in the foreground. 

In certain cases, Bring Forward or Send Backward 

must be selected several times since the object is only 

moved one layer at a time. The order in which objects 

were created is relevant here. 

Graphic panels provide the possibility to display monochrome or 256−color bitmaps on the display. 

Before bitmaps can be used, they must first be imported into the Visual Components or have already been 

created (see Bitmap Management). 

Static bitmaps (background bitmaps) are only output once when a page is changed and cannot be modified 

during runtime. If a modification is necessary during runtime, the 'Output Bitmap' output field must be used. 

Bitmaps can be combined with other objects, i.e. text or Overlapping Objects. 

If the display supports bitmap display, then they can be inserted using the icon in the toolbar. After selecting 

a bitmap, it can be inserted on the display by clicking where the upper−left corner of the bitmaps should be. 

Once the bitmap has been positioned, the dialog box for inserting background bitmaps is opened. 

Bitmap 

A Bitmap from any bitmap existing in the project can be 

selected in the combo box. Bitmaps are sorted 

alphabetically. 

Size 

Specifies the pixel size of the selected bitmap. This is 

only for display; input is not possible. If the size of the 

bitmap should be changed, this must be taken care of 

in a suitable graphics program before being imported 

into the Visual Components editor. 

Position 

Shows the X and Y pixel coordinates where this bitmap 

is inserted on the display. 

Status 

The status variable is of data type UINT. For bitmaps, 

bit 0 is responsible for determining whether the bitmap 

is drawn or not. 

BIT 0 == 1 − Bitmap not shown 

BIT 0 == 0 − Bitmap shown 

Preview 

Shows a reduced image of the bitmap to simplify 

selection and insertion. The preview is detailed 

according to the output size. 


An appropriate error message is given if the position and size of the bitmap exceed the display size in pixels. 

320 4.5.6 Background Bitmaps


Tip: 

If your bitmap is not represented correctly, this may be because of conversion to 256 colors in the editor. If 

necessary, these bitmaps must be created with this color palette, or the individual colors of the bitmap must be 

converted into Visual Components Color Tones. 

The representation could also be incorrect due to the Windows color configuration. If possible, use a screen 

setting with at least 32,768 colors in Windows. Otherwise, display errors can occur when bitmaps are used. 

4.6 Configuring Output Fields for Data 

Visual Components offers many possibilities for displaying process variables. The following section explains 

these possibilities. 

All fields can be inserted in a desired location and then configured in the picture editor. All output fields are listed 

in a common toolbar menu. 

If this tool is selected, the following menu appears where the desired output field can be selected. 

The following sections describe how the different output fields can be used. Detailed descriptions about 

individual output fields and adjustable parameters can be found in the reference manual. 

Output fields can be edited using either the mouse or keyboard. Double−clicking or Alt+Enter opens the 

'Properties' dialog box for the respective output field. Output field size can be adjusted by clicking and dragging 

on its borders. An output field can be moved by clicking on it and then dragging the field itself. 

The following sections describe the different possibilities for outputting process variables using Visual 


4.6.1 Recommendations 

Output fields provided by Visual Components are described in this section. Similar output fields have been 

summarized together to allow a better overview. 

Basic functions for operating Visual Components editors and dialog boxes are not described here. Such 

information can be found in the following sections. 

• Getting Started with Visual Components 

This section contains examples which give step−by−step instructions for simple Visual Components 

tasks. 

• Working with Visual Components 

This section describes Visual Components editors and their elements. 

The following sections are recommended for working with Visual Components: 

• Displaying Texts and Numbers 

Describes the possibilites to use process variables in text and numeric form in the visualization 

application. 

4.6 Configuring Output Fields for Data 321

• Displaying Analog Values 

Describes the representation of numeric process variables in analog, graphic form using bar graphs. 

• Text and Graphics Output Using an Index 

Describes text and bitmap output depending on the value of a numeric process variable. 

• Advanced Control of Screen Elements 

Describes details about connecting status variables and their possibilities, as well as controlling output 

field color during runtime. 

4.6.2 Displaying Texts and Numbers 

Visual Components offers a series of output fields for displaying text or numeric values. Depending on the 

output field, various display possibilities exist for representing process variables of different data types. 

The following value and text outputs are supported by Visual Components. 

• Numeric Output 

All numeric process variables, regardless if they are integer or floating point data types, are displayed 

using the universal Output Numeric field. 

• Text Output 

Character strings which are stored in process variables on the controller can be displayed in the 

visualization application as text. Any character from the font being used can be displayed. Text output is 

displayed using the Output String field. 

• Date and Time Output 

An Output Date/Time field is available which also allows appropriate display formatting. If the format for 

this output field does not suffice, then a string with date or time information can be entered in the control 

application and displayed as text output. 

Additional possibilites for displaying texts from a text group or a graphic bitmap − depending on a numeric 

process variable − are described in the Text and Graphics Output Using an Index section. 

4.6.2.1 General 


All output fields are placed in the picture in the picture editor by clicking the icon in the toolbar and selecting 

the appropriate output field. After placing the field, the 'Object Properties' dialog box is opened and the output 

field can be adjusted according to requirements. 

Size, format, output field position, and the connected process variable can all be configured under the 

'Parameter' tab. 

322 4.6.2 Displaying Texts and Numbers


4.6.2.1.1 Format 

The maximum number of digits to be displayed is set in the Number of Digits field. The number of decimal 

places to be displayed from this is set using Digits After Decimal Point. These decimal places are "real" decimal 

places only when a REAL variable is used. For integer variables, only one decimal point is displayed in the 

appropriate place. The value is still a whole number. For a two digit decimal setting, 1725 on the controller is 

displayed as 17.25 in the input field. 

Depending on whether decimal places are displayed, the field width corresponds to the Number of Digits. It can 

be displayed as one character wider if the decimal point is used. 

Leading places can be filled with zeroes if the option Display Leading Zeros is selected. By default, leading 

places are filled with spaces. 

4.6.2.1.2 Position 

Allows the precise placement (in pixels) of the output field by entering coordinates in the X and Y fields. When 

the 'Object Properties' dialog box is opened, the current coordinates of the output field are indicated. 

The output field can be more simply and conveniently positioned with the mouse by clicking and dragging it. The 

exact position can be adapted to a grid (see also The Picture Editor). 

4.6.2.1.3 Data Point 

The process variable whose value is to be represented in the output field is connected in the Source input field. 

The variable name can be directly entered or selected by clicking the Assign... button. 

4.6.2.1.4 Status 

Allows the connection of a process variable which influences the output field during runtime (see also Controlling 

Fields with Status Variables). 

4.6.2.1.5 Preview 

Shows how the field will be displayed during runtime with the current settings. 

4.6.2.1 General 323

4.6.2.1.6 Colors 

If the Use Global option is selected, the colors set in the global project options are used. Otherwise, individual 

colors can be set for this output field. 

If global colors are not used, text and background colors for the output field can be set with the Foreground and 

Background settings. Colors used for cursor operation, as well as other distinctions, always use the global 

settings. 

A variable which allows colors to be changed during runtime can be connected under Colors Variable (see also 

Changing Colors Using Variables). 

4.6.2.1.7 Simulation 


A text can be defined for each output field which is displayed when the editor is in Simulation mode. In this way, 

pictures containing practical values in the output fields can be created for documentation. 

324 4.6.2.1 General


The set value is not evaluated by Visual Components either in the editor or during runtime. 

4.6.2.1.8 Description 

Allows text to be stored for documentation purposes. 

4.6.2.2 Output Numeric 

The following process variable data types can be connected in this output field: USINT, SINT, UINT, INT, 

UDINT, DINT, REAL. 

Numeric values are usually justified to the right side of the output field. 

Some special settings are available for numeric output. 

4.6.2.1 General 325

4.6.2.2.1 Scaling 

Numeric output fields support scaling of the displayed value. 


This setting allows values on the controller to be converted to values suitable for display and editing. For this, 

the optimal value range can be selected for exact calculations in the control application while the display in the 

visualization project uses clearly understandable measurement units for operators. 

Scaling refers to the definition of two value ranges. The value in the first value range is properly converted 

relative to the (scaled) value in the second value range. 

The Scaling Active option must be selected for this output field to use scaling. Turning on scaling also enables 

the other scaling settings in the dialog box. 

326 4.6.2.2 Output Numeric


The permissible value range of the variable is determined in the control application using PLC Value Range. If 

the range exceeds the specified limits on the controller, asterisks (*) are displayed instead of the value to 

indicate an overflow. 

Scaled Value Range sets the appropriate value range for the display of the value. The 0% value corresponds to 

the 0% value in the PLC value range and the 100% value to the 100% value in the PLC value range. Scaling 

takes place using a straight line function. 

For both value ranges, settings for the 0% and 100% values can be made directly in the dialog box or using a 

process variable during runtime. The appropriate Parameters from PLC box has to be selected to define value 

ranges with PLC process variables (see picture − value range panels). In this way, the input fields change 

themselves into selection fields for limiting using variables. Variable names can be directly entered or selected 

from a list by clicking on the Assign... button. 

Using the Shift Decimal Point setting, a process variable can be connected which is able to move the decimal 

point around within the output field during runtime. For this, a postive variable value means more decimal places 

(decimal point moves to the left) according to the value. A negative value means less decimal places (decimal 

point moves to the right). 

Note: 

The Shift Decimal Point setting is only possible if at least one decimal place was set under the Parameter tab of 

the 'Object Properties' dialog box. 

4.6.2.3 Output String 

This output field allows STRING[] process variables (STRING array with any length) to be represented. Only 

characters up to the 'Number of Characters' setting are displayed even if a longer text is stored in the process 

variable. 

4.6.2.4 Output Date/Time 

The date and time on the controller can be displayed during runtime using this output field. Output format can be 

selected according to requirements. However, it cannot be changed during runtime or switched with the 

language. If more flexibility is needed, then an Output String field can be used instead. Formatting the output 

text takes place in the control application. 

4.6.2.4.1 Time Format 

This setting determines how the date and time are formatted for display. For this, only the formats in the list are 

available. Other formats can be implemented in the control application and displayed using a string output field. 

4.6.2.3 Output String 327

Specifying the field length in characters is not necessary since the format determines the length of the field. 

4.6.3 Displaying Analog Values 

This section describes ways of implementing graphic and analog output using Visual Components. Analog 

representations do not describe process variables with numbers. Instead, a graphic is used which changes with 

respect to the process variable. This works just like an analog measuring instrument or a progress indicator 

which is displayed when installing software. 

Visual Components uses bars graphs which can extend in all four directions to represent analog information for 

process variables. 

Note: 

Please click on the following button to start a demo: 

More analog outputs can be created by the user with the help of the Visual Components programming interface 

(see also VISAPI Functions Overview). 

4.6.3.1 Bar Graph Output 

A bar graph can be selected using the output field shortcut menu in the picture editor. 

After selecting Output Bar Graph and placing it in the picture, a half−filled bar graph with borders is shown in the 

editor. In this way, the source of the bar graph can be better checked during the design phase. Bar graph 

borders are drawn only during the design phase, not at runtime. If this is necessary, then a static rectangle can 

be used (see also Rectangles and Squares). 

The 'Object Properties' dialog box is opened by double−clicking on the bar graph. 


328 4.6.3 Displaying Analog Values


4.6.3.1.1 Format 

The size and direction of the bar graph is set here. Length determines the bar length and Width determines the 

bar width depending on which direction the bar graph extends. In this way, the bar can be rotated without having 

to reset the proportions. 


The direction of the bar graph is set 

with Direction. In the picture shown 

here, all four possible directions are 

shown as they are displayed in the 

editor. The bar graph is half full, 

representing a setting of 50%. The 

black area is the filled, active part 

of the bar while the white, empty 

section within the borders is the 

background and can be set to any 

available color. 

Exact bar location can be set by entering the position in the X and Y fields. When the 'Object Properties' dialog 

box is opened, the current coordinates of the output field are indicated. 

The bar graph can be more simply and conveniently positioned with the mouse by clicking and dragging it. The 


4.6.3.1 Bar Graph Output 329


Variable whose value determines the size of the bar. As long as the bar does not use scaling, the variable value 

specifies the exact length of the bar in pixels. A variable of type USINT or UINT can be used. Negative values 

are not supported, but another bar graph can be used which has the output directior reversed. 

The variable can be directly entered under Source or selected by clicking the Assign... button. 

4.6.3.1.4 Status 

Allows a status variable to be connection which can influence the output field during runtime (see also 

Controlling Fields with Status Variables). 

4.6.3.1.5 Preview 

Shows how the output field is displayed with the current settings. By clicking OK, the dialog box is closed and 

the settings are applied to the output field. 

4.6.3.1.6 Color 

The colors set in the global options can be used for the bar when the Use Global option is selected. 

If this option is not selected, bar graph colors can be chosen from a color palette using the Foreground and 

Background settings. Background refers to the empty space shown in the bar graph if the bar is less than 100% 

full. 

A UINT process variable can be connected in the Colors Variable field to change colors during runtime (see also 


4.6.3.1.7 Scaling 


By default, the bar graph is controlled by the process variable using one pixel increments. In other words, if the 

variable has the value 17, the bar will have a length of 17 pixels. 

If this default does not suffice, then a different conversion can be defined (control variable to bar length) under 

the Scaling tab. 

330 4.6.3.1 Bar Graph Output


The Scaling Active option must be selected to apply user defined scaling. 

Values which determine when the bar is empty or full are set in the 0% Value and 100% Value fields, 

respectively. These specifications are automatically converted to the set length of the bar. 


Text can be entered here for documentation purposes. This text is not evaluated by Visual Components. 

4.6.4 Text and Graphics Output Using an Index 

This type of output field is used for displaying dynamic status information where the value of a numeric process 

variable corresponds to a text or bitmap from a predefined collection. The PLC application only needs to process 

the numeric status information. Visual Components automatically takes care of displaying the correct text or 

bitmap in the visualization application. 

In this way, the same status information can be represented several times in the visualization application, i.e. 

once as a text and again as a bitmap graphic. 

The following output fields are possible: 

• Advanced Text Output 

• ListBox 

• Bitmap Graphic 

The displayed text or bitmap can be changed at any time by changing the value in the control application. 

Language switching can also be used for these dynamically displayed texts. 

Text or bitmap lists can no longer be influenced during runtime (except for ListBoxes which can use a process 

variable for the preparation of texts. In this case, language switching has to be turned off in the PLC application). 

Tip: 

By combining output fields described in this section with HotSpots, active input elements can be created very 

easily with bitmaps and texts! 

4.6.3.1 Bar Graph Output 331

4.6.4.1 Advanced Text Output 

This output field shows a text from a text group depending on the value of the connected process variable. The 

appearance of the text can also be changed during runtime using attribute and status variables. Text groups 

have to be created in the Text Group Editor before this type of output field is configured. 

The 'Object Properties' dialog box is opened by double−clicking on the output field. 

4.6.4.1.1 Format 

Number of Digits specifies the width of the output field in characters. Texts which are longer than this width are 

truncated when output. However, the value of the process variable is not changed. 

Font determines the font for the output text. Any font available in the project can be selected from the list (see 

also Font Management). 

Text Group determines the text group which contains the text to be displayed (see also Text Group Editor). A 

text group can be used for as many output fields as necessary. The number of texts in a text group is limited by 

the amount of memory available on the target system. 

Texts from the text group are always output using the index of the connected process variable. Additional 

scaling is not possible but may be implemented in the control application if necessary. Text indices in the text 

group can also be adjusted beginning with Visual Components version 2.2. 







332 4.6.4.1 Advanced Text Output


4.6.4.1.3 Text Number Data Point 

Process variable which selects the text to be displayed at runtime. The current value of this process variable 

corresponds to the numbers of the texts in the text group. Whichever value the process variable holds will 

determine which text from the text group is displayed. 

If the process variable contains an invalid value, then this text field is displayed on the target system filled with 

asterisks (*). If the variable does not exist because the task has not yet been transferred to the controller, for 

example, then the error is indicated with dashes (−). 

4.6.4.1.4 Attribute Data Point 

A process variable which determines more details of the displayed text can be connected here. The variable 

must be of data type UINT and can indicate two states at this time. 

Process 

variable 

0 Text is displayed using the set colors. 

1 

4.6.4.1.5 Status 

Effects 

Depending on the display used, text is output inverted (with reversed foreground and 

background colors) or blinking. 

Blinking is used on all displays which cannot display graphics. Text is inverted on all other 

displays including graphic displays with C130 CAN controllers. 

Allows the connection of a process variable which can influence the output field (see also Controlling Fields with 

Status Variables). 

4.6.4.1.6 Preview 

Shows how the field will be displayed with the current settings. The settings are only applied when OK is clicked. 

4.6.4.1.7 Colors 

4.6.4.1 Advanced Text Output 333

If the Use Global option is selected, then colors defined in the global project settings are used. If this option is 

not selected, text and background output color can be specified using the Foreground and Background settings. 

A variable which allows colors to be changed during runtime can be connected under Colors Variable (see also 



A text can be entered here which is displayed in the editor in Simulation mode. 

4.6.4.2 ListBox 

This output field is very similar to the Advanced Text output field. However, several texts are shown 

simultaneously in a list with the currently selected text accentuated by a different color. 

The ListBox is conceived as an output field and therefore does not receive any user interaction. The selected 

text is determined by a process variable from the PLC program. 

In this way, touch−operated elements can very easily implement any desired operation in the application if a 

panel with a touch screen is used. Naturally, key operation can also be implemented easily. 

ListBox properties correspond in many ways to those of Advanced Text Output. Different settings for the ListBox 

will be described in the following. 

4.6.4.2.1 Format 

In addition to the format properties of Advanced Text, the number of ListBox lines can be determined using the 

Rows parameter. 

4.6.4.2.2 Source of Texts 

There are 2 possibilities to choose from when displaying text with the ListBox: 


An existing text group can be connected using the Text Group setting. All texts from this text group are 

displayed in the ListBox during runtime in the order they were entered. The sequence or number of texts cannot 

be changed dynamically at runtime. However, text numbering within the text group can be adjusted during the 

design phase in the text group editor to meet corresponding requirements. 

334 4.6.4.1 Advanced Text Output


Texts are output from an array of string variables if the second setting, String Array, is selected. These texts can 

be composed in the control application during runtime and then output dynamically. Each line corresponds to a 

string from the array of strings. It should be noted that a string is an array by default. Therefore, an array of 

arrays must be created for this process variable. 

In contrast to the Text Group setting, switching languages between the text layers defined in Visual Components 

cannot be applied (since texts are only made available during runtime from the PLC program and are therefore 

not recognized by the Visual Components editor). Language switching must be disabled by the control 

application if necessary. 

4.6.4.2.3 Variables 

The Selected Item setting selects the highlighted line from the list. The list is always automatically advanced so 

that the element is visible. 

4.6.4.2.4 Colors 

In addition to color settings for Advanced Text, the color of the highlighted line in the ListBox also has to be set. 

4.6.4.3 Bitmap Graphic 

This output field uses bitmaps to represent a dynamically changing status. For this, a process variable from the 

PLC program can be used to switch between up to 255 different bitmaps. The upper−left corner of the bitmap is 

always located at the specified position of the bitmap output field. 

The background is not cleared when bitmaps are switched. Instead, only the new bitmap is output. Therefore, all 

bitmaps should be the same size so that the rest of the previous bitmap does not remain on the display when it 

is switched. 

At the moment, bitmap output is only possible on IPC target systems (in color or black/white depending on the 

display) or the PP41 PowerPanel. Displays used by the C130 CAN controller do not support bitmap output 

fields. 

The following settings can be defined for the bitmap field under the 'Parameter' tab: 

4.6.4.2 ListBox 335







A process variable is connected here whose value determines which bitmap should be selected. The variable 

must be of data type UINT and should only be set in a value range corresponding to how the bitmaps are 

defined. Selecting undefined bitmap numbers is not supported. 

4.6.4.3.3 Status 

Allows the connection of an additional process variable which enables further output field control (see also 

Controlling Fields with Status Variables). 

4.6.4.3.4 Bitmaps 


A list of bitmaps is managed in this panel. They are displayed depending on the value of the connected variable. 

The bitmap number is shown in the first column. This is the same value which the process variable must have in 

order to show this bitmap. 

The name of the bitmap appears in the second column. Clicking on the field opens a list where the desired 

bitmap can be selected. 

336 4.6.4.3 Bitmap Graphic


Entries can be added, inserted, removed, or the sequence changed using the buttons under the bitmap list. The 

list cannot have empty spaces since bitmaps are numbered in consecutive, ascending order. 

4.6.4.3.5 Preview 

The bitmap currently selected under Bitmaps is displayed in this area. 

Bitmaps should be as close to the same size as possible for consistent display. The field size in the editor is 

determined using the largest inserted bitmap in the X and Y directions. 

4.7 Configuring Input Fields for Data 

Visual Components supports the input of process information in both numeric and text form. These input fields 

can be placed and configured anywhere in a picture. This section describes these input fields and how they are 

used in a Visual Components project. 

Input can also be assigned to panel keys with Visual Components. When these keys are pressed, certain 

interactions take place with the connected process variable, i.e. the variable is set to a certain value or the 

variable value is increased by a predetermined increment. These same functions are also possible on a touch 

screen using the appropriate touch fields. 

Assigning keys to variable interactions is described in the Keys, LED, and Touch Support section. 

4.7.1 ListBox 

The ListBox input control looks the same and is configured just like the ListBox output control. However, this 

control allows the user to directly input selections using cursor control. 

4.7.1.1 

Text group 

A text group with consecutive index numbering beginning with 0. A text group 

with gaps in the index (i.e. 0 − 1 − 4 − 12) cannot be connected. 

4.6.4.3 Bitmap Graphic 337

4.7.1.2 Option bytes 

This field accepts a byte array. The length of this byte array has to correspond at least to the number of texts 

used in the text group. Using this byte array, texts can be locked runtime (value = 1) or made invisible (value = 

2). Each index in the array describes the state of its corresponding text element (OptionByte[10] = Text #10 in 

the text group). Value 0 sets the text back to visible and unlocked. 

4.7.1.3 Cursor Character 

The cursor character has been integrated into the ListBox input control for black/white displays. 

Since colors can't be configured to differentiate between selected elements 

and cursor elements, a character has been introduced for the cursor. 

This character is inserted before the text where the cursor is located. 

4.7.1.4 Selected Item 

Variable on which the index of the selected item is mapped. 

4.7.1.5 Status 

Status variable. This variable can be used to lock this control or make it invisible. 

(see also Controlling Fields with Status Variables). 

Up key: Key for upward movement in the ListBox 

Down key: Key for downward movement in the ListBox 

Select key: Key for selecting an element 

Note when configuring control keys: 

Keys for up/down control have to be configured. If an Enter key is already present on the operator panel (or 

display), then a selection key is not necessary. In this case, the Enter key itself is used as the selection key. The 

Enter key can even be used to switch to the next selection element. If a separate selection key has been 

configured, then a "Goto Input" control key is required to move to other input fields. 

Procedure: 

At runtime, the user receives a cursor for choosing text and a cursor for the selected element (text group 

variable). In contrast to the ListBox output control, scrolling up or down through the entries is possible without 

changing the value of the connected variable. The index of the element under the cursor is written to the text 

group variable with the Enter or selection key. 

4.7.1.6 Colors 


338 4.7.1.2 Option bytes


Foreground and background colors, as well color variables for the ListBox input control, can be 

specified for the selected item and the locked element in the Color dialog box. 

4.7.1.7 Completion Data Point 

This setting allows input to be monitored after it is completed or the Increment/Decrement keys are no longer 

pressed. To achieve this, a variable is entered under Completion Data Point. Every time the 'Enter' key is 

pressed or an Increment/Decrement key is released, the variable is set to the value entered in Completion Value 

regardless of the value which was input. 

The same completion data point can be defined for any number of input fields with various completion values. In 

doing so, monitoring changes and input in the control application becomes much more simplified. 

4.7.1.7 Completion Data Point 339

4.7.1.8 Locking Input 

In this window, configuration for locking the element can be made. 

See Securing Input with Password Levels 

4.7.1.9 Description 


Control descriptions can be added in this field. This is only to display information for the programmer and 

doesn't have any influence on the target system. 

340 4.7.1.8 Locking Input


4.7.2 Numeric Input 

Entries in a visualization application are usually made using numeric input fields. Visual Components provides a 

special input field which meets nearly all of the possibilities for numeric input. If user−defined input is necessary, 

this can be taken care of by using string input fields which are described in the next section (see also Text 

Input). 

A numeric input field is inserted in the Visual Components picture editor. After selecting the 

icon (shown here to the left) from the toolbar, this menu appears. Selecting Input Numeric 

switches the editor to insert mode for numeric input fields. 

Any number of input fields can be inserted. The 'Properties' dialog box appears to edit the 

newly inserted field once it has been placed. 'Properties' can also be opened by 

double−clicking on an existing input field. 

4.7.2.1 Formatting and Handling Input 

This input field supports many settings and options to meet the needs of the application. 

4.7.2.1.1 Format 

The maximum number of digits to be displayed is set using Number of Digits. The number of decimal places to 

be displayed is set using Digits After Decimal Point. These decimal places are "real" decimal places only when a 

REAL variable is used. For integer variables, only one decimal point is displayed in the appropriate place. The 

value is still a whole number. For a two digit decimal setting, 1725 on the controller is displayed as 17.25 in the 

input field. The input of 32.68 sets the value of the connected variable to 3268. 



Leading places can be filled with zeroes if the option Display Leading Zeros is selected. By default, leading 

places are filled with spaces. 

4.7.2 Numeric Input 341

The Activate Automatic Comma Input option in the global properties of the project determines if the decimal 

point must be manually entered during input. If this option is selected and the input field is set for two decimal 

places, then '17.25' is displayed by typing '1 − 7 − 2 − 5 − Enter'. If this option is not selected, then '1725' will be 

displayed regardless of the decimal place setting. 

If Automatic Comma Input is not used, then a decimal must be defined when defining keys. 

If the Disable Cursor Movement On Enter option is selected, then the cursor will not automatically go to the next 

field when input is completed. 


A pixel perfect field location can be set by entering the position coordinates in the X and Y fields. The default 

value corresponds to where the field was placed with the mouse. 

4.7.2.1.3 Preview 

Displays the input field with the currently selected settings. These settings for the input field in the picture are 

applied when confirmed with the OK button. 

4.7.2.1.4 Colors 


342 4.7.2.1 Formatting and Handling Input


By selecting Use Global, the colors set in the global project options can be selected. Otherwise, individual colors 

can be set. 

If the global colors are not used, the text and background color for the input field can be set using the 

Foreground and Background settings. Colors used for the cursor during operation, as well as other distinctions, 

always use the global settings. 

A variable which allows colors to be used or changed during runtime can be entered under Colors Variable. 

4.7.2.1.5 Adjusting Input Up / Down 

Up/Down keys can be used instead of number keys to enter input into fields in the picture. In this way, an input 

value can be increased or decreased with the specified Up/Down keys once the field has the focus. 

The respective keys are set under the 'UpDown' tab in the 'Properties' dialog box of the picture, and there 

cannot be more than one of each for one picture. 

The keys which are used to increase and decrease input values are listed under Increment Key and Decrement 

Key. 

If the key is pressed briefly, then the value shifts one step. If the key is held down longer, then the value 

increases/decreases more quickly. 

4.7.2.1 Formatting and Handling Input 343

'Up/Down Input' must be activated for any input fields which should use these defined keys. Keys defined for 

'Increment Key' and 'Decrement Key' are displayed here. 

The input field must have the focus to use these keys for input there. If a variable is constantly being adjusted or 

if a user−defined increment should be used, then an Increment/Decrement function key can be used in place of 

this setting. 

The advantage of the setting described here for these keys lies in the several usage possibilities for different 

types of input. For example, completely functional input can be implemented using only three keys (a key which 

accepts input and advances to the next input field, and the 'Increment' and 'Decrement' keys). 

4.7.2.2 Connecting Variables 

The link with the control application is made by connecting corresponding variable(s). The following variables 

can be connected. 


Process variable whose value can be displayed and changed. 

4.7.2.2.2 Status 

A variable can be connected here to further monitor the input field during runtime (see also Controlling Fields 

with the Status Variable). 

4.7.2.2.3 Completion Data Point 


344 4.7.2.2 Connecting Variables


This setting allows input to be monitored after it is completed or the Increment/Decrement keys are no longer 

pressed. To achieve this, a variable is entered under Completion Data Point. Every time the 'Enter' key is 

pressed or an Increment/Decrement key is released, the variable is set to the value entered in Completion Value 

regardless of the value which was input. 

The same completion data point can be defined for any number of input fields with various completion values. In 


4.7.2.2.4 Scaling 

This setting allows values on the controller to be converted to values suitable for display and editing. For this, 

the optimal value range can be selected for exact calculations in the control application while the display in the 

visualization project uses clearly understandable measurement units. 

Scaling refers to the definition of two value ranges. The value in the first value range is properly converted 

relative to the (scaled) value in the second value range. 

4.7.2.2 Connecting Variables 345

The Scaling Active option must be selected for this input field to use scaling. This activates the two following 

options. 

The permissible value range of the variable is determined in the control application using PLC Value Range. No 

values outside of this range can be input in the visualization application. If a variable is entered which falls 

outside of this range, then it is automatically corrected to the nearest permissible value. The user is notified and 

and can confirm the change. 

If the Parameters from PLC option is checked, then variables can be connected and used as upper and lower 

limits of the PLC value range. This allows the scaling range to be changed by the controller during runtime. 

Scaled Value Range sets the appropriate value range for value display and input. When this value is input, 

decimal places might possibly have to be entered as well. Automatic decimal input only has an effect on Visual 

Components during runtime. It does not have an effect on the editor. 

Variables for the upper and lower limits of the value range can also be connected for this area by selecting the 

'Parameters from PLC' option. 

A variable can also be connected here which allows the decimal point to be shifted during runtime. However, 

this option is only active if decimal places are defined for the field. 

4.7.2.3 Additional Settings 



A text can be defined for each input field which is displayed when the editor is in Simulation mode. In this way, 

pictures containing practical values in the input fields can be created for documentation . 

346 4.7.2.3 Additional Settings


The set value is not evaluated by the Visual Components editor or during runtime. 



4.7.2.3.3 Locking 

See Securing Input with Password Levels. 

4.7.2.3.4 Touch Screen 

Additional settings are possible when touch screen displays are used. These settings are available for both 

numeric and textual input. 

See Using Input Fields on Touch Screens. 

4.7.3 Text Input 

Text input uses alphanumeric characters (0−9, A−Z, a−z, etc.) and is stored in the controller as a string or byte 

array. 

4.7.3.1 Formatting the Input 

A text input field is inserted in the Visual Components picture editor. This menu 

appears after selecting the icon (shown here to the left) from the toolbar. Selecting 

Input String from this menu allows the string input field to be inserted. 

Any number of input fields can be placed. The 'Properties' dialog box appears after 

a new field is inserted. 'Properties' can also be opened by double−clicking on an 

existing input field. 

Properties are automatically displayed after a new input field is inserted. 

4.7.2.3 Additional Settings 347

4.7.3.1.1 Format 

The width of the input field is set in characters using the Number of Characters field. Input fields only support the 

entry of single line texts. Input fields composed of several lines or automatic lines breaks are not supported. 

The font is selected from the Font selection list. Any font configured in the project can be selected. 


The exact location of the field in pixels can be set by entering the position in the X and Y fields. The default 

value corresponds to where the field was placed with the mouse. 

4.7.3.1.3 Preview 

Displays the input field with the currently selected settings. These settings are applied to the input field in the 

picture editor by clicking the OK button. 

4.7.3.1.4 Colors 


348 4.7.3.1 Formatting the Input


The Use Global setting determines whether global project or separate individual color settings should be used 

for this input field. 

If global colors are not used, then text and background colors for the input field can be set using the Foreground 

and Background settings. Colors used for the cursor during operation, as well as other distinctions, always use 

the global settings. 

A variable which allows colors to be used or changed during runtime can be entered under Colors Variable. 

4.7.3.2 Input Field Operation 

A series of options are provided under the Keys tab which support many different possibilities for inputting text. 

Each possibility described in this section applies exclusively to panel keys. The Edit Mode setting is an 

exception since it can also apply to touch operation. 

4.7.3.2 Input Field Operation 349

4.7.3.2.1 Keys 

These settings allow additional keys to be configured which handle input functions. The following functions can 

be assigned: 

Function Description 

Cursor Left key 

Cursor Right key 

Delete key 

Backspace key 

4.7.3.2.2 Tabulator 

Moves the cursor one character to the left without altering input. This allows the cursor to 

be moved back a few places to correct a mistake or add a forgotten letter. 

Moves the cursor one character to the right without altering input. The cursor can be 

moved to a maximum of one place beyond the last character entered. 

Deletes the character to the right of the cursor and advances the remaining characters (to 

the right) one step forward. No gap is left when this key is pressed. 

This key should be used even if the cursor keys were configured. 

Deletes the character to the left of the cursor and moves all remaining characters one 

place to the left. 

Using the tabulator key (tab), the cursor can move more than one character to the right. The number of 

characters that the cursor moves when pressing the tab key can be set using Tab distance. 

AutoTab Mode can also be selected as an alternative so that the cursor moves to the next word. In this case, 

words consist of entities using the letters a−z in upper or lower case. All other characters are considered 

separators. 

4.7.3.2.3 Mode 

Different modes can be more practical than others for data input depending on the type of input. The number 

and type of available keys can also affect how information is entered. 

The Edit Mode list offers the following possibilities: 

Edit 

Clear 

Mode Meaning 

Key−Dependent 

Password 

4.7.3.3 Connecting Variables 


In this mode, an input field is edited normally. If the content should be changed, then the 

previous contents must first be deleted using the Delete and/or Backspace keys. 

In this mode, the previously existing text is basically overwritten. Editing the old text is not 

possible since it is deleted when the first key is pressed to enter new input in the active field. 

This mode combines the two previous modes depending on the first key used when editing the 

field. 

If the first key pressed is a cursor key, then the appropriate cursor movement occurs and the 

text is preserved. This behavior corresponds to Edit mode. 

Otherwise, the text is completely replaced. This behavior corresponds to Clear mode. 

Operation is the same as Clear mode except that characters entered (as well as the existing) 

are not displayed on the screen. 

In this way, the input of hidden passwords and similar data is possible without having to be 

displayed on the screen. 

Symbols to be displayed in place of actual entered characters can be set in Password char. An 

asterisk (*) is used by default. 

Connecting with the control application takes place by connecting the appropriate variables. The following 

variables can be connected. 

350 4.7.3.2 Input Field Operation


4.7.3.3.1 Destination Data Point 

Process variable whose value can be displayed and changed. 

4.7.3.3.2 Status 

A variable can be connected here to further monitor the input field during runtime (see also Controlling Fields 

with the Status Variable). 

4.7.3.3.3 Completion Data Point 

This setting allows input to be monitored after it is completed by pressing the 'Enter' key. To achieve this, a 

variable is entered under Completion Data Point. Every time the 'Enter' key is pressed, the variable is set to the 

value entered in Completion value regardless of the given value. 

4.7.3.3 Connecting Variables 351

The same completion data point can be used for any number of input fields with various completion values. In 




A text can be defined for each input field which is displayed when the editor is in Simulation mode. In this way, 

pictures containing practical values in the input fields can be created for documentation. 

The set value is not evaluated by the Visual Components editor or during runtime. 



4.7.3.4.3 Locking 

This setting is discussed separately. 

See Securing Input with Password Levels. 

4.7.3.4.4 Touch Screen 

Additional settings are possible when touch screen displays are used. These settings are available for both 

numeric and textual input. 

See Using Input Fields on Touch Screens. 

4.7.4 Securing Input with Password Levels 


Securing input is frequently a requirement of visualization applications. Visual Components basically supports 

any type of security which can define a process variable using the currently set security level in numeric form as 

a result. 

Visual Components provides special password input fields for locking entries using passwords. Other 

mechanisms for this can be produced on the controller using application tasks. For example, a key switch could 

be requested using I/O variables, or a serial device which reads cards with electronic chips could be addressed 

using the FRAME library. However, these possibilities are application specific and so will not be expanded upon 

352 4.7.3.4 Additional Settings


here. 

4.7.4.1 Configuring Locking for Input Fields 

The first step in securing input is configuring each individual input field. Individual input field settings can be 

made at any time. In the following, an Input Numeric dialog box is shown. However, settings are applied the 

same for all other input fields. 

Configuring input locking takes place under the 'Locking' tab of the Properties dialog box for the input field. The 

following settings are available there: 

The Locking Active option determines if this input field should be locked. If this option is not selected, then the 

corresponding input can be handled at any time. 

A variable which specifies the current security level has to be connected in the Password Value Data Point field. 

The application can determine how these security levels are laid out. 

'Input Locked If' determines when input is not possible. The following settings are possible. 

Setting Description 

Password value is zero 

Password value < Level 

Password value >= Level 

The input field is locked if the variable has the value 0. Any other value unlocks the 

field. 

If input fields are grouped together, a separate variable can be used for each of 

these groups to unlock input. 

This setting is used if a single variable is used to manage rights and numerically 

'smaller' password levels possess more rights than 'large' password levels. 

It should be noted that the password must be 'less than' the set password level to 

unlock the input field. If they are equal, then the input field is still locked. 

With this setting, input is unlocked if the connected variable is greater than or equal 

to the set password level. 

4.7.4.1 Configuring Locking for Input Fields 353

The comparative value is determined according to the setting in the 'Password level' field. This must be set in 

the editor during the creation phase. 

4.7.4.2 Entering Passwords 

Visual Components provides two methods for entering passwords. The first method allows password operation 

to be configured in Visual Components during the creation phase. The second possibility entails evaluating the 

actual input using the controller application. 

Both fields are inserted in the Visual Components picture editor. After selecting the icon 

(shown here to the left) from the toolbar, this menu appears. 

Evaluating passwords can be applied by selecting Input String. A variable is connected 

which writes the password to a string variable or byte array using echo characters (i.e. 

*****). The input string is evaluated in the application program. 

Password logic is managed in Visual Components with the Input Password option. In 

contrast to string input, however, this method is limited to the number of password levels. 

After inserting the desired input field, the 'Properties' dialog box appears to edit it. 'Properties' can also be 

opened by double−clicking on an existing input field. 

4.7.4.2.1 Formatting the Input 

Password input essentially supports the same positioning, formatting, and colors as string input fields (see also 

Text Input). The maximum length of a password field is 6 characters. This is also the maximum length for 

adjustable passwords. 

Additionally, the Echo character field determines which characters should be used to display on the screen in 

place of the entered password characters (for security reasons, actual character input is not directly visible). 

4.7.4.2.2 Connecting Variables 


A numeric variable has to be connected in the 'Destination (Password) Data Point' field. The input field 

recognizes the possible passwords and converts them to the appropriate authorization level. The variables 

connected here can be used directly as password variables for input fields, as described above. For this, the 

Password value >= Level mode is used and the desired password level entered. 

354 4.7.4.2 Entering Passwords


A status variable or completion data point can also be defined if necessary. 

4.7.4.2.3 Defining Passwords 

Passwords for this field are determined during the creation phase and can no longer be changed while the 

program is running. If changing passwords during runtime is necessary, string input in Password mode and 

controller application logic need to be used. 

Up to 4 password levels can be defined which are numbered from 0 to 3. The number of the corresponding 

password level is transferred to the password variable. If a valid password is not entered, then 0 is written to this 

variable. This level must therefore be used for inputs which are always available. Password levels 1 to 3 can be 

set under the Passwords tab. 

The number of password levels can be set under Number of Password Levels. 2 to 4 levels are possible. The 

first level (level 0) is used if an incorrect password was entered. 

Corresponding passwords are entered in the input fields Password #1 to Password #3. The password variable is 

set to the appropriate value (the number before the # character) after a password is successfully entered. If an 

incorrect password is entered, then the password variable receives the value 0. 

4.7.5 Using Input Fields on Touch Screens 

Guiding users through the input of numeric and alphanumeric characters is different on display units with touch 

screens than it is on displays with keys. 

Visual Components provides the possibility to display a virtual keypad on these touch displays. It opens 

automatically when an input field is touched and allows characters to be input to the field which is to be edited. 

Support is limited to graphic touch displays (display units for the IPC2001 and IPC5000 series). Matrix touch 

displays, which can be operated with the C130 CAN controller, are not supported in this way. Operations are 

carried out as with normal keys. 

4.7.5.1 Using Touch Keypads 

4.7.4.2 Entering Passwords 355

4.7.5.1.1 Numeric Input 

A standardized touch keypad for numeric input exists for all supported display units. All characters necessary for 

numeric input fields are supported. 

4.7.5.1.2 Alphanumeric Input 

The active input field is displayed in the upper part of the keypad during 

runtime. Its operation is very similar to a numeric keypad. 

Numeric values are input using the number keys 0 to 9. 

Input is cancelled by pressing the 'Cancel' key. All input made in the 

field to this point is discarded. 

Characters to the left of the cursor are deleted using the 'Backspace' 

key. 

The input value is confirmed and accepted by the input field when 

the this 'Enter' key is pressed. As long as input is between the limits, 

the touch keypad closes and the value is written to the connected 

control variable. 

If the upper limit is exceeded or the lower limit not reached, then the 

value is corrected to the nearest limit value and is only accepted 

once 'Enter' is pressed again. 

The sign (pos/neg) for the input can be changed with this key. 

A decimal point can be added to the input by pressing this key. This 

is only for input fields using decimal places or floating points. 

Alphanumeric entries have even more input possibilities. By default, a 640x240 (pixel) keypad based on a 

standard AT keyboard appears to allow input to string and password fields. 

The string to be entered into the input field is displayed in the upper left area. 

Most keys function the same as they would on a normal PC AT keyboard. Some exceptions are summarized in 

the following table. 

Image Description 

The cursor can be moved left or right using these keys. They do not cause changes in the 

input. 

Pressing this 'Cancel' key cancels the input and closes the touch keypad. 


356 4.7.5.1 Using Touch Keypads


The backspace key deletes the character to the left of the cursor and moves the entire 

remaining text (to the right of the cursor) one place to the left. 

Pressing the 'Enter' key confirms the input and the input field accepts the entered string. 

This 'Caps Lock' key allows several capitalized letters to be entered in succession. Capitalized 

letters (or lowercase letters, as the case may be) are input until the 'Caps Lock' key is pressed 

again. 

A single letter can be capitalized or a special character can be entered using the 'Shift' key. To 

do this, the 'Shift' key must be pressed before the desired letter key. 

Warning: Pressing several keys simultaneously on the touch keypad is not possible 

due to the construction of the analog touch display! Therefore, characters 

must be entered one after another. The 'Caps Lock' key can be used if 

several capitalized letters are entered in a row. 

To save space, the spacebar is located in the Right Shift key position. 

A split keypad with the same input possibilities is available during runtime for alphanumeric input on a 1/4 VGA 

display (QVGA). 

This keypad consists of three tabs which are arranged like the inside of a dialog box. Two of the three keypad 

tabs are displayed here. 

The first tab, marked by 0−9, contains digits and special characters. The two other tabs contain the letters A−P 

and Q−Z. The Q−Z page also contains some punctuation marks and special characters which are not included 

on the first tab due to lack of space. 

The value being edited is displayed in the upper, blank part of the keypad. The entire QVGA display surface 

(320x240 pixels) is required when this input dialog box is open. 

Some special keypad assignments are described in the following table. 

Image Description 

The desired tab is selected using the register tabs on the left side of the keypad. It is 

displayed and the desired characters can then be entered. The selected tab remains 

displayed until another tab is selected or the input is closed by pressing the 'Enter' key. 

4.7.5.1 Using Touch Keypads 357

A single letter can be capitalized or a special character can be entered using the 'Shift' key. 

To do this, the 'Shift' key must be pressed before the desired letter key. 

Warning: 

Pressing several keys simultaneously on the touch keypad is not possible due to the 

construction of the analog touch display! Therefore, characters must be entered one after 

another. The 'Caps Lock' key can be used if several capitalized letters are entered in a row. 

Pressing this 'Cancel' key cancels the input and closes the touch keypad. 

Pressing the 'Enter' key confirms the input and the input field accepts the entered string. 

The spacebar is located on the lower right of the touch keypad. 

4.8 Advanced Control of Screen Elements 

Beginning with version 2.1, Visual Components input and output fields have some new, common control 

possibilities available for the controller application. Because of this, the visualization project can be adapted to 

the controller application's processes and states. 

4.8.1 Recommendations for New Users 

The topics in this section require knowledge about configuring fields and operating the Visual Components 

editor. 

This information can be found in the following sections: 

• Getting Started with Visual Components 2.1 

Creating a Visual Components project is described step−by−step in this section. 

• Working with the Visual Components Editor 

This section contains an introduction and explanation of the individual Visual Components editors and 

their dialog boxes. 

• Arranging Static Picture Components 

This section describes how static picture elements are used for picture layout. They include static texts, 

lines, circles, rectangles, and bitmaps. 

• Configuring Output Fields for Data 

Outputting data is described in this section (output fields). Numeric, text, and graphic output are all 

described in this section. 

• Configuring Input Fields for Data 

This section describes how to configure and use input fields. It also describes the differences between 

touch system input and conventional systems which use operator panel keys. 

4.8.2 Changing Colors Using Variables 


Normally, color for visualization picture elements is set in the editor during the design phase. Global color 

settings for frequently used colors are also set in the editor, but can be adjusted for each individual picture 

element. 

If it is necessary to change the color of a picture element during runtime, it can be done using a color variable. 

358 4.8 Advanced Control of Screen Elements


4.8.2.1 Connection 

One or more color variables can be connected in the Properties dialog box of each field, depending on which 

type of field is used. Fixed color settings are also entered here during the design phase. 

The following image describes the color settings for a numeric input field. Other fields are connected similarly. 

A variable can be connected in the Source input field located under Colors Variable. If the control variable name 

is known, then it can be entered directly or chosen from a list by clicking the Assign... button. 

The connected variable must be of data type UINT. 

If the variable is not present during runtime, then the colors set in the configuration dialog box are used. 

4.8.2.2 Color Variable Structure 

Two pieces of color information are stored in a color variable simultaneously: The foreground color and 

background color for the affected field (or part of it). Colors can be assigned to the corresponding setting in the 

dialog box. 

4.8.2.1 Connection 359

In this dialog box (color settings for a touch button), the color variable refers to the two adjustable colors of the 

same group. The left−hand color defines the foreground color. The right−hand color defines the background 

color. This color information is read into the high byte and low byte of the color variable. 

The color variable must be a 16−bit UINT data type. From these 16 bits, 8 bits are used for the foreground color 

and 8 bits for the background color. In this way, 256 color shades are possible for both the foreground and 

background color. 

Bit 

No. 

Dec. 

Value 

Hex 

Value 

0−7 255 0x00FF Background 

8−15 65280 0xFF00 Foreground 

4.8.2.3 Application Possibilities 

Name Description 

The background color of the element is set with the lower 8 bits of the 

color variable. All 256 colors from the color palette of the current project 

can be used. 

Setting 255 is transparent, i.e. the corresponding area is not colored. This 

setting does not work with all fields and can only be used if the picture 

does not change after it is constructed. 

The foreground color of the element is set with the upper 8 bits of the 

color variable. 

It is not possible to cover all of the details of such an implementation in this section. Applications and concrete 

examples in C and Automation Basic can be found in the Tips and Tricks section. 

• 4.8.2.3.1 Using Static Texts as Status Indicators 

Status indicators can be easily displayed using the color variable and static texts. 


The application sets the color value for static text depending on the state of the option to be indicated. If 

the foreground and background are set to the same value, the surface will be displayed as one color. 

Otherwise, the text is displayed with the respective color. 

In this way, indicators such as 'Motor Off', 'Motor On', and 'Motor Error' can be implemented using 

simple color switching. 

360 4.8.2.3 Application Possibilities


Tip: 

Dynamic texts can be used if the text should be appropriately modified for output. 

• 4.8.2.3.2 Blinking Element on the Screen 

Foreground and background colors are changed to a desired blink frequency in order to output a 

blinking element on the screen. 

A field connected with this variable then blinks automatically with the selected colors. 

If the element should only blink because of a special state (i.e. in the event of error), a separate color 

variable is used and, depending on the status, set to the blink variable value or the "resting state" value. 

• 4.8.2.3.3 Bar Graphs with Color Changes 

Bars graphs with changing colors can also be used in the application. According to the limits, changing 

colors can be implemented at runtime by modifying the color variable. 

4.8.3 Controlling Fields with Status Variables 

Status variables can be connected to all fields in Visual Components which enables visibility control, input 

release, and synchronization with external variables. 


The status variable is entered under the Parameter tab of the Properties dialog box. The following image shows 

the Parameter tab for a numeric input field. 

The connected status variable must be of data type UINT. The same variable can also be used for several fields 

as long as the synchronize function is not used. If the synchronize function is used, then it makes sense to use 

separate variables for each field, so that the processed (active) field can be more accurately determined. 

4.8.3.2 Assignment 

The status variable uses individual bits to control different field tasks. Depending on requirements, these bits 

can be set and/or evaluated by the application. If the status variable is 0, or if no status variable is connected, 

4.8.2.3 Application Possibilities 361

then the field operates as before. 

Bit No. 

Dec. 

Value 

0 1 0x0001 Invisible 

1 2 0x0002 Locked 

2−13 16380 0x7FFC Reserved 

14 16384 0x4000 HasFocus 

15 32768 0x8000 EditActive 

Hex Value Name Description 


This bit is set by the user (or control application) in order to 

make the field invisible. If the bit is 0, the field will be displayed 

normally. 

The bit can be switched at any time. The picture is then 

redrawn accordingly and the corresponding field is displayed 

as either visible or invisible. The update occurs at a maximum 

of once per second. 

Input can be locked by setting this bit to 1. This function can be 

used in place of or in addition to the normal password levels. 

This setting is checked when the field is selected. In other 

words, when the cursor moves over the field or it is touched 

(touch screen). 

This bit is only evaluated for input and touch−operated fields. 

Other fields do not normally react to user input. 

These bits are reserved for future updates and should be 

initialized to 0 before starting the application. This ensures that 

future updates will not have unwanted effects on the 

application. 

These bits cannot be changed or evaluated during runtime. 

This bit is set to 1 by the editor when the input field is marked 

as active (i.e. has the input focus). If another input field is 

selected, then this bit is set back to 0. 

Using this bit, the control application can determine which 

input field has just been chosen by the user and can respond 

accordingly. This could be useful for displaying appropriate 

help text in a status bar, for example. 

This bit is only set for input fields and is reserved for all other 

fields. 

This bit is set to 1 by the editor if the input field has been 

opened for editing. It is reset to 0 when the input has been 

completed. This allows a more exact determination of the 

editing status of a field than would normally be possible using 

only the completion address. 

This bit can be evaluated in the control application, so that 

variables which are acquired over a network (i.e. INA client 

FBKs) can be synchronized accordingly. 

If the bit changes from 0 to 1, the variable must be excluded 

from being read so that it is not overwritten by the network 

copy routine after editing. 

When the bit is changed from 1 to 0, the variable must be 

transferred (written) once to the remote station. The variable 

can then be enabled again for reading. 

This bit is only set for input fields and is reserved for all other 

fields. 

362 4.8.2.3 Application Possibilities


4.8.3.3 Application Possibilities 

This section contains a few examples concerning the use of status bits. It is not possible to completely cover all 

of the details of such an implementation in this section. Applications and concrete examples in C and 

Automation Basic can be found in the Tips and Tricks section. 

• Synchronized Data Acquisition Over a Network 

Transporting variables from remote stations can be coordinated using the EditAction bit (15). By default, 

active variables are read cyclically and then displayed. 

If the variable's EditActive bit changes from 0 to 1, then this field was opened to be edited on the 

visualization unit. Cyclic reading for the respective variable must be disabled until the input is complete. 

This is indicated when the bit switches back to 0. This means that this variable can be written back to 

the remote station. As an option, the value can be checked to make sure it is within permitted 

boundaries. 

When completed, the variable is activated again for cyclic reading. 

• Configurable Visualization 

By default, Visual Components does not support a dynamic visualization arrangement on the runtime 

system. Such behavior can be partially reproduced using the Invisible bit. In this way, options on the 

machine which either are either not available or not paid for are hidden from the visualization user. 

Although the layout cannot be changed in this way, certain option controls can be taken from the screen 

as well as appropriate pages from the page switching system. 

This allows extensive configurations to be implemented by integrating the Visual Components 

visualization into the control application. 

• User−Defined Input Locking 

If input field password levels are not sufficient, or if status variables for visibility control are already being 

used in the application, then it is easier to control input locking in the application. 

If these conditions are not met, then using password levels is usually easier and less complicated when 

handled and maintained in the visualization. 

• User−Dependent Information Display 

With its password management system for input fields, Visual Components supports the simple 

administration of Write abilities (rights) in the visualization, depending on the current user level. 

In some visualization applications, certain information should only be displayed to privileged users. By 

default, this is not directly supported by Visual Components. 

However, this behavior may now be implemented in the application with the Invisible bit which can 

switch fields visible or invisible. 

• Context−Sensitive Help 

Using the HasFocus bit (14), the control application can determine which input field is activated (has the 

input focus). This may allow an appropriate help text to be very easily displayed in a status bar or other 

suitable field. 

4.8.4 Advanced Text Group Options − Formatted Texts 

Alarm texts and texts from text groups can be linked with so−called tags (formatted variables) and can output 

strings and numeric values which are generated during runtime. Using these tags, flexible texts and texts 

adjustable at runtime can be defined. However, alarm texts are limited to 4 numeric variables. 

4.8.3.3 Application Possibilities 363


Tag variables are inserted using the Tag button in the Text Input dialog box. The length, format, and the variable 

to be connected are all inserted in the Format Wizard using variable dialog boxes. The following image shows 

the Format Wizard dialog box for a numeric variable. 

Supported data types: 

BOOL 

USINT 

SINT 

UINT 

INT 

UDINT 

DINT 

STRING (the alarm system does not support strings) 

4.8.4.2 Format 


The maximum number of digits to be displayed is set in the Number of Digits field. The number of decimal 

places to be displayed from this is set using Digits After Decimal Point. For variables, only one decimal point is 

displayed in the appropriate place. The value still remains a whole number. For a two−digit decimal setting, 

1725 on the controller is displayed as 17.25 in the input field. The input of 32.68 sets the value of the connected 

variable to 3268. 



Using Fill Space With Character determines whether leading places should be filled with blank spaces (i.e. 

zeroes). These empty character spaces can be defined by the user. By default, leading spaces are filled with 

zeroes. 

364 4.8.4.1 Connection


4.8.4.3 Data Point 

The process variable to be displayed is selected under Source. A process variable which is not in the Source list 

can be selected from the variable dialog box using the Assign... button. 

The inserted tag consists of the formatting and the process variable in brackets. Text and tags can be inserted 

individually. The number of tags in Text Groups is limited to a maximum of 4 per text and language. 

The same procedure is used with alarm texts. However, texts are limited to a maximum of 4 numeric 

variables regardless of how many languages are configured. 

4.9 VC Project Multilingual Capabilities 

Visual Components provides the opportunity to create projects in several languages. These languages are 

configured during project creation. Picture contents can also be viewed in several languages in the picture 

editor. In this way, screen page changes can be checked using different texts. 

The editor also allows language texts to be exported in either a .CSV format (Excel) or plain text. Texts can be 

translated there and then imported back into the Visual Components editor. 

The language can then be switched to a different language layer during runtime. The picture on the display is 

redrawn after the language variable is changed. 

It is also possible to activate and deactivate configured languages. If the project is recompiled, then only the 

active text layers are compiled which changes the project size on the target system. 

The necessary steps for creating a multilingual project are explained in the following sections. The sections 

contain a step−by−step example and should be read in order. 

4.9.1 Project Multilingual Capabilities 

4.9.1.1 Adding and Activating Text Layers 

A text layer indicates all the texts which belong to a language and can be compiled. Static texts, dynamic texts, 

and alarm system texts are all parts of text layers. 

By default, a new project is created with only one text layer. This text layer is called 'Default'. All configured text 

layers can be seen in the project tree under 'Languages'. 

4.8.4.3 Data Point 365

A new text layer is inserted from the 'Languages' shortcut menu or by pressing the 'INS' key in the language 

view (right side). 

New text layers must be named in this dialog box. 

The 'Compile Text Layer' option specifies whether the text layer should be compiled for the target system. 

If there is not a lot of memory on the target system, then it doesn't make sense to compile languages which are 

not necessary. In addition, languages can optionally be supplied to end customers. 

A new text layer is inserted after entering the the language name 'English' and selecting the 'Compile Text 

Layer' option. 

Text layers can later be renamed or removed. 

After a new text layer has been created, all texts in the project are transferred from the 'Default' text layer to the 

new text layer. This makes certain that all texts will always be seen. 


4.9.2.1 Configuring Texts in Several Languages 

After one or more text layers have been added to a Visual Components project, the input dialog box for static 

texts looks different when opened. All additional languages are displayed beneath the "default" column with the 

texts in the default language. These can be translated accordingly. 

The existing text of the 'Default' language is transferred to the new layers. 

Double−clicking the text for the appropriate language allows translation to take place. 


366 4.9.2 Project Multilingual Capabilities


If there are several text layers, then they are inserted in the following lines. Each language can be translated 

separately. Since the translated texts are sometimes a different length then the default language texts, the 

picture is partially changed. 

Translation results can immediately be checked in the Language Switching Design View. 


4.9.3.1 Switching Languages During the Design Phase 

The possibility exists to switch text layers in all editors. In this way, project translation can be checked and 

translations can be input directly. 

This preview allows texts with different lengths to be rearranged if necessary. 

There are two text layers in this example − 'Default' and 'English'. Any defined language can be selected from a 

combo box in the picture editor toolbar. 

Selecting 'English' automatically switches to the English text layer. As long as a translation is available, texts in 

the picture are displayed in their respective language. 

4.9.3 Project Multilingual Capabilities 367

When there is a difference in text length, the longest text of a text layer is indicated. It is identified by a dashed 

border. 


4.9.4.1 Text Groups in Several Languages 

Text groups are also displayed in the editor in several languages. They appear in columns under the text layer 

names. 

After inserting a new text layer, default texts are automatically transferred to it and can be directly translated in 

the appropriate editor. 

Warning: 

Since a text group is assigned to a dynamic text field with a fixed length (see also Text and Graphics Output 

Using an Index), texts which are too long will be truncated automatically at runtime. Text length and assignment 

to the corresponding text field must be considered during the design phase. 

4.9.5 Multilingual Project Capabilities 

4.9.5.1 Switching Languages During Runtime 


Switching languages during runtime is done from the application program (i.e. writing to the language variable 

from the visualization application). The variable value must correspond to the text layer index. 

Language variable changes are checked cyclically during runtime. When the value is changed to a valid text 

index, the current picture is redrawn with the new language. 

Language switching is activated by selecting 'Enable Text Layer Switching' from the 'Panel' global project 

settings. Languages are changed during runtime by modifying the value of the connected variable. 

368 4.9.4 Project Multilingual Capabilities


If the project is started on the target system, the value of the 'Language_Index' variable is used as the text layer 

index. 

If the 'Language_Index' variable has a value of 0, the project is displayed with the 'Default' text layer. 

If the 'Language_Index' variable has a value of 1, all texts are displayed in English. 

4.9.6 Multilingual Project Capabilities 

4.9.6.1 Importing and Exporting Texts 

Visual Components provides the opportunity to export all project texts. Translation can then be done in another 

program. Translated texts can then be imported back into the project. 

Texts can be exported in either a *.TXT or *.CSV file. In this way, texts can be edited using any text editor or MS 

Excel. 

Texts are exported and imported by selecting 'Text Export...' or 'Text Import...' from the 'Tools' menu. These 

menu items become available when at least one additional text layer has been inserted. 

4.9.6.1.1 Text Export 

One or more text layers can be exported at the same time. 

4.9.6 Multilingual Project Capabilities 369

The export file format is determined by how many languages are selected. Each language is stored in a 

separate column in the export file and separated by some sort of character (i.e. ';'). 

The sequence of the languages, as well as their accompanying ID (internal text identification), is set in 'Format'. 

Warning: 

The IDText must not be changed. This is used for text assignment when importing. 

Export File Structure: 

In the export file, one text layer is stored per column. This text file contains keywords beginning with the # 

character. These keywords must not be changed. 

Default;English;IDText; /* Heading*/ 

#PANEL 

#PICTURE 

#TEXT_GROUP 

#ALARM_GROUP 

#ALARM_GROUP 

#ALARM_GROUP 

#ALARM_SETTINGS 

After a keyword (i.e. #PICTURE), all texts in the corresponding group follow. 

#PICTURE 

11;TextDefault;Text;Text;1; 

2;F1;F1;F1;2; 


The length of the longest text within a text layer is specified in the first column. All texts from the corresponding 

text layer (according to the export configuration) are given in the following columns. The internal text ID is 

specified in last column (according to the export configuration) and must not be changed. 

'0' is specified for alarm text length. In this way, alarms with any length are output since these texts can be 

output to a display and an alarm printer with various lengths. 

370 4.9.6 Multilingual Project Capabilities


4.9.6.1.2 Text Import 

Translated texts can be imported back into a project. Texts from any text layer (including 'Default') can be 

changed. When importing, the ID text is used to assign texts to the project and its text layers. 

4.10 Keys, LED, and Touch Support 

Keys are a central component of a visualization application. They are used for numeric/alphanumeric input, 

changing pictures, navigation, as well as direct manipulation of control variables. 

Visual Components recognizes four types of keys, each of which has various application ranges and usage 

possibilities. 

• Operator Panel Keys 

Visual Components supports numerous operator panels, a majority of which are equipped with 

integrated keys. By default, these keys are imprinted (i.e with number pads and other frequently used 

keys) and can also be arranged appropriately by using legend sheets. 

Fixed key functions are already preconfigured for all Visual Components panels. All other keys can be 

set according to the needs of the application. 

Some of these keys are also equipped with LEDs. These can also be configured with Visual 


4.9.6.1 Importing and Exporting Texts 371

• Graphic Keypad on Touch Systems 

A graphic keypad is used on touch systems to input numeric and alphanumeric information. 

Adjusting this keypad is not possible. It is automatically displayed by the Visual Components runtime 

system. 

• 'Button' and 'HotSpot' Touch Fields 

'Button' and 'HotSpot' touch fields can be used to configure virtual keys on panels equipped with a touch 

screen. These keys are updated frequently (high priority) and allow a jog key function (see also Using 

the Key Matrix). 

• Standard AT PS/2 Keyboard 

The possibility exists on IPC systems to configure input using a standard PS/2 AT keyboard (see Project 

Options). Essentially, this allows a lot of input to be entered during the commissioning phase. By default, 

German and English (US) keyboard formats are supported. 

4.10.1 Configuring Panel Keys 

A key in a project must first be appropriately configured before it can be assigned a function in the picture editor. 

At the same time, imprinted keys have preconfigured functions so the user only has to define application specific 

keys. 

Keys are configured in the picture overview. This is opened by selecting the 

'Pictures' node in the Visual Components editor tree view. 

Keys which have already been assigned can also be deleted in this global 

picture area! 

Panel key configuration is found in the lower right−hand part of the view. 


372 4.10.1 Configuring Panel Keys


The keys can be individually configured in this view. Double−click on a key to configure it. Configuration takes 

place in the following dialog box: 

Basic key functions are defined under the first tab − 'Key Type'. The following settings are possible: 

• None 

Selecting 'None' means that this key has no special function. It is either not used or only used for 

entering numbers. To assign an alphanumeric character to the key, the desired character must be 

4.10.1 Configuring Panel Keys 373

entered in '0. Level' under the 'Key Levels' tab. 

See also Configuring Several Key Levels. 

• Function Key 

A function key is required to carry out special functions in the individual pictures. (see also Using 

Function Keys). A function key can be assigned a name composed of 1 to 4 characters which is valid in 

the entire project (i.e. F1, QUIT, etc.). 

• Control Key 

Control keys provide a uniform predefined function which is valid in the entire project, i.e. these 

functions apply in every picture. The following control keys are available, some of which are assigned to 

the fixed printed keys. 

Next Picture 

Previous Picture 

Enter 

Next Input 

Label Function 

Assigning the 'Next Picture' takes place from the corresponding source 

picture. 

The same function can also be achieved using a function key. 

Assigning the 'Previous Picture' takes place from the corresponding source 

picture. 

The same function can also be achieved using a function key. 

This control key corresponds to the input completion key and finalizes entered 

data in numeric and/or alphanumeric input fields. 

This key is required in all projects which do not use a touch screen for 

entering numeric and alphanumeric data. 

Moves the cursor to the next input field. The cursor control sequence is 

defined in the picture editor with Next Input / Previous Input. 

Clear Deletes the current input field entry. 

Backspace 

Deletes the character to the left of the cursor and moves the remainder (right 

of the cursor) to the left. 

Sign Change Changes the sign (+/−) of numeric input fields. 

Previous Input 


Moves the cursor to the previous input field. The cursor control sequence is 

defined in the picture editor with Next Input / Previous Input. 

Acknowledge All acknowledgeable queued alarms are acknowledged with this key. 

374 4.10.1 Configuring Panel Keys


Additional settings can be made for some control keys using picture dependent key configurations (see 

also Configuring Keys to Picture Levels). 

• Switch Levels Key 

This key is used to switch between multiple key levels (see also Configuring Several Key Levels). 

4.10.2 Configuring Keys to Picture Levels 

After global keys have been configured, key functions can be assigned in each picture corresponding to the key 

configuration. 

A key function can be assigned to a function key. The 'Next Picture' and 'Previous Picture' control keys require a 

picture−dependent configuration (picture assignment) to function. 

4.10.2.1 Key Editor 

The picture−dependent key is configured for the respective picture in the picture editor. The picture to be edited 

is selected from the Visual Components project tree. 

Once the the picture editor opens, displays which have keys can be configured in the lower area. 

Assigning a key function to a key takes place using a symbol illustrated on the respective key. There are two 

types of key assignments: 

4.10.2 Configuring Keys to Picture Levels 375

Symbol Meaning 

This symbol indicates that the key has been assigned to a picture element (input field +/− 

shift, alarm system paging / acknowledgement, etc.). 

A key must be either redefined in the accompanying field or deleted to make it available for 

another function. 

This symbol indicates that this key has been configured for an action in this picture. This key 

can be edited or freed in this editor. 

All other key symbols indicate control keys. In the above example, the control keys 'Next Picture', 'Previous 

Picture', 'Backspace', and 'Enter'. 

4.10.2.2 Key List 

A list of all existing and assigned keys is displayed to the right of the key editor. 

This list displays which functions have been assigned in the editor or fields to the keys in the current picture. The 

F1, F2, and F3 keys in the picture above are assigned to an alarm line. F1 is assigned for alarm 

acknowledgement. F2 and F3 are assigned for paging through the current alarms. These keys can only be 

edited in their respective fields. 

The F7 and F8 keys have been configured here in the editor. F7 is assigned to change to the next input field to 

the right. F8 is assigned to change to the 'SECOND' picture. Double−clicking on a key displays the settings for 

the selected action. For example, the direction for changing to the next input field can be redefined. (see also 

Using Function Keys). 

4.10.2.3 Assigning Keys 

This section describes assigning a function and its properties to a function key (see also Using Function Keys). 

Possible functions apply to both keys and touch−operated fields. 

Control keys settings are also described since only a panel key can be configured as a control key. 

4.10.2.3.1 Assigning Functions to Function Keys 


A function is assigned to a function key in the shortcut menu of the key. The desired key function has to be 

selected from the function list. 

Warning: 

If the shortcut menu for the circle is opened, then possible LED functions are displayed (see also Configuring 

and Controlling LEDs). 

376 4.10.2.2 Key List


After a function is selected, its dialog box is displayed and configuration can take place. 

4.10.2.3.2 Setting Function Parameters 

Dialog boxes containing settings for functions which are already assigned can be opened by double−clicking on 

the key in the key editor or in the key assignment list. 

Warning: 

Double−clicking on the circular LED symbol opens its configuration dialog box. 

4.10.2.3.3 'Next Picture' and 'Previous Picture' Control Keys 

The 'Next Picture' and 'Previous Picture' control keys switch through the application pictures based on a 

user−defined sequence. 

Target pictures are displayed in the bottom two lines of the key list with their respective control keys icons. 

Picture assignment can be changed by double−clicking one of the two lines. 

4.10.2.3 Assigning Keys 377

4.10.3 Creating Keys on the Touch Display 

Displays which do not have panel keys are operated using a touch screen. This allows input of numeric and 

alphanumeric values, the operation of the application, as well as visualization process operation. 

Tools for entering numeric or alphanumeric values are automatically provided by Visual Components if the panel 

comes with a touch display. 

This section describes options for implementing key functions using the touch display. 

4.10.3.1 Inserting Touch−Operated Fields 

Two types of fields are available for touch displays: 

A touch field is inserted using the icon from the picture editor toolbar. 

After selecting the desired touch field, insert mode is activated and as many touch fields as desired can be 

placed on the current page. 

Both touch fields allow their pressed states to be edited along with the action which is triggered when they are 

activated. 

The difference between the two fields is their graphic appearance. The touch button allows a visible, 

configurable surface. 

Using the HotSpot, the user can create an invisible touch field whose appearance is configured later by the user. 

Visual Components only provides the surface. 

4.10.3.2 HotSpot 


The HotSpot is invisible during runtime and can be used to define areas and actions in bitmaps. The HotSpot is 

displayed in the editor as a dashed rectangle. 

378 4.10.3 Creating Keys on the Touch Display


Settings and options for the HotSpot are as unlimited as those for the touch button. Therefore, common 

properties will only be described once. 

4.10.3.2.1 Dimension 

These settings determine the exact position and size of the touch field on the screen. The 'Left' and 'Top' default 

values correspond to where the field was placed with the mouse. 

4.10.3.2.2 Key Matrix Offset 

If it is also necessary to map a touch field in the key matrix, its offset can be defined here. 

If this setting is selected, the position in the matrix can be assigned in the input field after any possibly existing 

panel keys. The panel keys are stored in a defined sequence at the beginning of the key matrix. 

The display field shows the effective index resulting from the setting in the matrix for this touch field. This 

corresponds to the sum of the panel keys and the adjusted offset. 

4.10.3.2.3 Status 

See also Controlling Fields with Status Variables. 

4.10.3.2 HotSpot 379

4.10.3.2.4 Action 

Under the 'Action' tab, the function which is triggered by pressing the touch field can be selected from a list. The 

same settings are available as for panel keys configured as function keys (see also Using Function Keys). 

4.10.3.3 Touch Button 

Functionally, a touch button is the same as a HotSpot but happens to possess additional display options. Touch 

button appearance corresponds to that of a visible button. There are additional settings with regard to 

appearance. 

In the above example, the button on the left is the Visual Components standard button (except for the large 

font). The button on the right has a wider border, customized colors, and is provided with an additional bitmap. 



380 4.10.3.2 HotSpot


4.10.3.3.2 Dimension 

These settings determine the exact position and size of the touch field on the screen. The 'Left' and 'Top' default 

values correspond to where the field was placed with the mouse. 

4.10.3.3.3 Key Matrix Offset 

If it is also necessary to map a touch field in the key matrix, its offset can be defined here. 

If this setting is selected, the position in the matrix can be assigned in the input field after any possibly existing 

panel keys. The panel keys are stored in a defined sequence at the beginning of the key matrix. 

The display field shows the effective index resulting from the setting in the matrix for this touch field. This 

corresponds to the sum of the panel keys and the adjusted offset. 

4.10.3.3.4 Status 

See also Controlling Fields with Status Variables. 

4.10.3.3.5 Appearance 

4.10.3.3 Touch Button 381

4.10.3.3.6 Logical Font 

Defines the font to be used for the button label. Any font in the project can be used for this. The font applies for 

both the pressed and released button states. 

4.10.3.3.7 Border Width 

Determines the button border width. The button is accentuated with suitable colors (see picture above). Border 

width is set here depending on the type of hardware used (different for each button). 

4.10.3.3.8 Released Button and Pressed Button 

The respective appearance of the button is determined for both the released and pressed states in these two 

groups. Settings can be made individually for each state. By default, the setting for the released button is also 

used for the pressed button. 

Button text can be chosen using 'Text Group' and 'Text'. The text must be defined in a text group (see also Text 

Group Editor). After assigning a text group, the appropriate text must be selected from it. Direct entry of text is 

not supported. 

A bitmap can also be entered for each state. It will appear on the left side of the button. If a bitmap is entered, 

then text is centered on the right side of the button. Otherwise, text is placed directly in the middle. If only a 

bitmap is connected, then it is also placed in the middle of the button. 

Any bitmaps in the project can be used in color, black/white, or using transparent effects. 

The result is shown in the 'Preview' area. Using the 'Released' and 'Pressed' option fields, the button can be 

viewed in their different states. 

4.10.3.3.9 Colors 


Button colors can be individually set and optionally controlled during application runtime by connecting variables 

to them (see also Changing Colors Using Variables). 

382 4.10.3.3 Touch Button


4.10.3.3.10 Border 

Sets the border colors for the key. The 'raised' setting is used for the left and top borders when the button is 

released and the right and bottom borders when pressed. The 'sunken' setting is used for the other borders. 

To make the button look like it is being selected, 'raised' should be set with a bright color and 'sunken' with a 

darker color. To display a flat button without 3D effects, the same colors can be used for both its 'raised' and 

'sunken' states. 

4.10.3.3.11 Released Button and Pressed Button 

Determines the colors for the surface of the button as well as the inscription. Pressed button settings are 

especially important for buttons with a toggle function since the pressed state is visible for a longer time. 

4.10.3.3.12 Action 

4.10.3.3 Touch Button 383

Under the 'Action' tab, the function which is triggered by pressing the touch field can be selected from a list. The 

same settings are available as for panel keys configured as function keys (see also Using Function Keys). 

4.10.3.3.13 Additional Settings 

Settings under the 'Locking' and 'Description' tabs are explained in the general input field documentation (see 

also Securing Input with Password Levels). 

4.10.4 Using Function Keys 

Function keys can be configured for both panel keys and touch operated elements. 

When function keys are used, several interactions are possible between the visualization and the control 

application. Most of the functions described below can be configured for both panel keys and touch−operated 

elements. 

The settings illustrated in the following are mainly for panel keys. With an appropriate layout, however, these 

settings can be also adapted for touch operated elements. 

4.10.4.1 Interaction with Control Variables 

4.10.4.1.1 General 

4.10.4.1.1.1 Input Field Description 

All dialog boxes have essentially the same structure. 

The individual elements have the following meanings. 

Element Meaning 


384 4.10.3.3 Touch Button


Source 

'Assign...' Button 

Value1, Value2 

4.10.4.1.1.2 Completion Data Point 

A variable from the control application is connected here. This variable must already exist in 

the control application in order to be assigned or input directly, i.e. already entered in the 

variable declaration section. 

Pressing this button opens the variable selection dialog box where an existing variable from 

the control application can be assigned. By default, only variables with suitable data types 

are displayed in the dialog box. 

Depending on the function, one or more values can be defined which are assigned to the 

key according to function and key status. 

A variable can optionally be connected which allows a user−defined value to be set when then key action has 

been completed. 

The completion data point can be used to centrally record and query changes in the control application. In this 

way, application code is created easier and is better maintained. 

4.10.4.1.2 Set USINT and Set UINT 

If a key is defined with the 'Set ...' function, then the connected variable is set to the defined value when the key 

is pressed. The value has to be reset in the control application. 

The same settings apply to both variations. Only the data types are different. 

4.10.4.1.3 Toggle USINT and Toggle UINT 

This function switches the status of the connected variable between 2 predefined values. This allows application 

software functions to be switched on or off. 

4.10.4.1 Interaction with Control Variables 385

The same settings apply to both variations. Only the data types are different. 

If the connected variable has the value set under 'Value 1' when the function is triggered, then it will be set to 

'Value 2'. Otherwise, the connected variable is set to 'Value 1'. 

4.10.4.1.4 Momentary USINT 

Using this function, a variable is set to a certain value as long as the key is pressed. When the key is released, 

the value resets to 0. 

This jogging operating cannot be carried out if the variable is updated with lower priority. In this case, the 

real−time capable key matrix is used (see also Using the Key Matrix). 

4.10.4.1.5 Increment/Decrement 


Using this function, a variable can be increased or decreased by using an adjustable increment (+/− keys). 

386 4.10.4.1 Interaction with Control Variables


The appropriate variable from the control application is entered under the Parameter tab. Limits as well as the 

increment are set in the Function dialog box for this key. 

The individual elements of this dialog box are described in the following. 

Element Meaning 

Use Limits 

Limit Min 

Limit Max 

Autorepeat 

Increment 

If this option is selected, maximum and minimum limits can be specified in the input fields. If no limit 

is specified, then the limits of whichever data type is used apply. 

Specifies the minimum allowable value of the variable. If the variable is already at or below this 

value, then it cannot be further decreased with this function. Automatic corrections do not occur. 

Specifies the maximum allowable value of the variable. If the variable is already at or above this 

value, then it cannot be further increased with this function. Automatic corrections do not occur. 

If this option is selected, then this function automatically repeats when a key is pressed and held. 

Otherwise, the variable only changes with each new key stroke. 

This setting determines the increment of the value when it changes. 

The variable is increased with positive values and decreased with negative values. 

4.10.4.2 Controlling Picture Changes 

4.10.4.2.1 Change Picture 

Using this function, a picture can be changed to any other picture created in the project. The target picture can 

be selected from a list of all the pictures available in the project. 

4.10.4.2 Controlling Picture Changes 387

4.10.4.2.2 Next Picture and Previous Picture 

These functions are only available for touch input fields. For panel keys, these functions can be achieved using 

control keys of this type. This function is essentially identical to the Change Picture function. These key 

functions are displayed in the picture editor key list. 

4.10.4.3 Navigating Input Fields 

4.10.4.3.1 Goto Input 


With this key function, input fields can be navigated when they are arranged geometrically. In this way, it does 

not matter in which order the fields are normally edited. 

This function is only available for panel keys. On touch screen panels, input fields can be selected and edited by 

directly touching them. Therefore, navigation keys are not necessary on these systems. 

388 4.10.4.2 Controlling Picture Changes


Positioning the cursor is configurable using the four main directions. 

It should be noted that the input fields should be arranged geometrically. If an input field within the size (width / 

height) of the original field is not found in the direction specified, then searching continues over the screen 

edges in the same direction. 

4.10.5 Configuring Several Key Levels 

Only a few keys are available on smaller panels. The possibility exists to enter up to four different characters per 

key so that alphanumeric input can also be input alongside numeric input. A function key can also be assigned 

up to three additional characters. Control keys apply to all key levels and cannot be set with additional 

characters. 

To implement multiple key levels, some additional settings have to be made. 

4.10.5.1 Setting the 'Switch Levels' Key 

In order to set characters in additional key levels, one (or more) switch level key(s) must be defined. 

Configuration for this takes place in the global key configuration in the picture overview. 

The 'Properties' dialog box is opened by double−clicking the key which should be configured as the switch key. 

4.10.5 Configuring Several Key Levels 389

This key becomes a switch key when 'Switch Levels Key' is selected. The 'Mode' selection list opens which 

allows exact settings for the switch key to be made. 

Increment 

Mode Function 

Increment Single 

Decrement 

Decrement Single 

Set 

Set Single 

In this mode, this key increases the key level by one. After reaching the highest possible 

key level (3), the key level returns again to 0. This allows each key level to be reached 

using a single switch key. 

In this mode, the key level for inputting one character is increased by 1. After the character 

is entered, the mode is reset to the original value (before the switch key was pressed). 

In this mode, the key decreases the current key level by 1. After reaching the lowest key 

level (0), the key level is set to the highest key level (3). This allows each key level to be 

reached using a single switch key. 

In this mode, the key level for inputting one character is decreased by 1. After the 

character is entered, the mode is reset to the original value (before the switch key was 

pressed). 

In this mode, the key changes to the key level defined in the 'Level' selection list. If this 

mode is set, then a separate switch key must be defined for each key level used. 

Switch keys in this mode should not be combined with switch keys from the 'Increment' 

and 'Decrement' modes. This can complicate key level selection. 

This functions like the 'Set' mode, but the level is only changed for the next character 

entered. After the character is entered, the mode is reset to the original value (before the 

switch key was pressed). 

When a key is selected as a switch key, it basically applies to all key levels. This kind of key cannot be assigned 

additional characters in other key levels. 

4.10.5.2 Configuring Additional Key Levels 

In addition to general panel key configuration, each panel key can be assigned an alphanumeric character for 

each available key level. Settings are made in the global key editor by double−clicking on the corresponding 

key. 

The character to be displayed can be directly entered in the fields in this dialog box. Upper and lower case 

letters are distinguished here. 

Many different key levels can be assigned depending on how the keys were configured. 

Key Type Available levels for alphanumeric input 

None 


If the key has not been assigned any special function, then alphanumeric characters can be 

entered on all 4 levels. 

390 4.10.5.2 Configuring Additional Key Levels


Function 

Key 

Control 

Key 

A key configured as a function key can be assigned an alphanumeric character for key levels 1−3. 

The key function is deactivated for all key levels except for 0 if at least one alphanumeric character 

has been assigned. If a function key is available in several (all) key levels, then no alphanumeric 

characters can be assigned to it. 

A control key cannot be assigned any alphanumeric characters and is therefore always available in 

all key levels. Instead of the 'Previous Picture' and 'Next Picture' control keys, alternative function 

keys can be used with the picture change function. This allows additional alphanumeric characters 

to be assigned to the keys. 

Switch 

This key cannot be assigned any alphanumeric characters. 

Levels Key 


Additional options can be set for editing key levels in the global project settings. 

4.10.5.3.1 Transmit Current Key Level 

Using this setting, the key level currently set in Visual Components runtime can be evaluated in the control 

application. In this way, the user is provided a way to display the current key level via the LED or the screen. 

The variable can also be defined. This may be used to implement a "Numlock" key, for example. 

The connected variable must be of type USINT. The variable name can be directly entered or selected by 

clicking the 'Assign...' button. 

4.10.5.3.2 Activate Alphanumeric Level 

If this setting is selected, an automatic switch to the specified key level takes place when changing to an 

alphanumeric input field (string or password). In this way, behavior from Visual Components 2.0 is copied in 

which a special key level was available only for alphanumeric input. Key levels 1−3 can be controlled with this 

property. As soon as switching to a string input field occurs, switching also takes place to this level. 

4.10.6 Configuring and Controlling LEDs 

For some display units, Visual Components or the control application can be used to control key LEDs. There 

are two possibilities available for controlling LEDs. 

One possibility for configuring LEDs uses Visual Components to configure the appropriate key LED in the 

appropriate pictures. If this possibility does not suffice, then LEDs can also be controlled from the control 

application using the LED Matrix. 

Warning: 

Both control possibilities cannot be combined in the current Visual Components version. If this occurs, there is 

no way of predicting which output will actually be displayed on the LED! 

4.10.5.3 Additional Settings 391

4.10.6.1 Configuration in the Editor 

LED parameters are set in the key editor for picture dependent configuration. Configuring LEDs globally is not 

necessary. 

Options for LED control (LED functions) are displayed in the shortcut menu of the LED icon (circle located on 

the keys). 

If a function is assigned to an LED, then the circle is colored yellow. 

The following settings are available: 

Setting Meaning 

LED None 

No action is executed with the LED. The LED is switched off since all LEDs are basically reset 

when the picture changes. 

LED On The LED is always turned on. 

LED Off The LED is always turned off. 

LED 

Blinking 

LED Fast 

Blinking 

LED Control 

From PLC 

The LED blinks slowly (depending on the hardware, approx. 1 Hz) 

The LED blinks quickly (depending on the hardware, approx. 4 Hz) 


The LED is controlled by a PLC variable. Using this setting, a part of the LED can also be actively 

influenced by the control application when LED operation is configured. This setting should 

preferably be used in place of the LED matrix if only some LEDs are controlled by the control 

application at runtime and the majority are set to fixed values depending on the picture. 

When 'LED Control From PLC' is selected, the following dialog box appears to connect the appropriate variable. 

392 4.10.6.1 Configuration in the Editor


A USINT variable must be connected which can control LED states as follows. 

Variable Value LED Status 

0 The LED is turned off 

1 The LED is turned on 

2 

3 

The LED blinks slowly (depending on the hardware, approx. 1 

Hz) 

The LED blinks quickly (depending on the hardware, approx. 4 

Hz) 

Any other value in the connected variable is invalid. 

Depending on the control application workload, the LED status update can take some time. Updating takes 

place in the context of the interpreter. 

4.10.6.2 Direct Operation from the Control Application 

If configuration in the Visual Components picture editor is not sufficient, then LEDs can be handled completely 

by the control application. In this case, all LEDs must be configured as 'LED None' (default). Otherwise, the 

outcome is not defined. 

LEDs are operated using an array of USINT variables which is connected to Visual Components and and which 

possesses an entry for each LED on the panel. The LED sequence is thus dependent on the panel and is 

described in its technical documentation or with the update for the respective customer specific panel. This 

sequence cannot be changed. 

Tip: 

If the appropriate documentation is not available, then the LED sequence can be determined by connecting an 

appropriate variable and testing the individual array indices in the Watch window in Automation Studio. 

The array is connected on the global properties page of the Visual Components editor after its corresponding 

size has been specified in the control application. 

4.10.6.2 Direct Operation from the Control Application 393

After the 'Transmit LED Matrix' option has been selected, the variable can be connected in the 'Source' field. To 

do so, the variable name can be entered directly or selected by clicking the 'Assign...' button. 

To control LEDs, the array elements must be defined with the following values: 

Element Value Associated LED Status 

0 The LED is turned off 

1 The LED is turned on 

2 The LED blinks slowly (depending on the hardware, approx. 1 Hz) 

3 The LED blinks quickly (depending on the hardware, approx. 4 Hz) 

4.10.7 Using the Key Matrix 

Function keys provide a series of possibilities to influence variables within the control application from the 

current visualization project. These variables are defined in the context of the visualization idle time. 

Function keys are not suitable for implementing true jog key operations or other similar time−critical functions. 

The same constraint also applies to the key matrix parameters configured in the Visual Components project. 

The key matrix can be connected to a variable. This is also only implemented in idle time and is not suitable for 

time critical operations. 

To solve this problem, a new implementation of the key matrix is available beginning with Visual Components 

Version 2.1 in which the user can actively trigger the acquisition of key information using a function. 

4.10.7.1 Using the Key Matrix 

Key matrix operation is possible using the Visual Components programming interface (VISAPI Functions 

Overview). Using this interface, optimal timing can be actively predefined in the control application. 

4.10.7.1.1 1. Integrating the Library 

The Visual Components programming interface is contained in the 'Visapi' library. It must be imported to the 

current project using the Library Manager. Details about importing libraries can be found in the general 

Automation Studio documentation. 

4.10.7.1.2 2. Selecting a Programming Language 

The functions in the programming interface can be used in all text−based languages which can use library 

functions (this is not possible in the Ladder Diagram). 

Examples of implementation in Automation Basic and ANSI C are described in the following. 


394 4.10.7 Using the Key Matrix


4.10.7.1.3 3. Creating the User Task for Key Matrix Operation 

The task must be created in the task class where key matrix handling also takes place. It is easiest to have key 

matrix acquisition retrieval and evaluation in the same task. In this way, the logic in the application always works 

with the most current key data and the highest possible performance can be achieved. 50 milliseconds is a 

recommendable task cycle time for key matrix operation. 

The following examples illustrate how such a task could look in the Automation Basic and ANSI C programming 

languages. These examples can be adapted to specific application needs. 

4.10.7.1.3.1 3.1 Automation Basic 

4.10.7.1.3.1.1 Init subprogram 


step = 0 

erase = 1 

4.10.7.1.3.1.2 Cyclic program 


(* get handle for project "vga1" *) 

IF step = 0 THEN 

VC_HANDLE := VA_Setup(1, "vga1") 


step := 1 

ENDIF 

ENDIF 

(* try to read the current key matrix *) 

IF step = 1 THEN 

status := VA_GetKeyMatrix(1, VC_HANDLE, ADR(mtxKeys), 48, ADR(mtxSize)) 

IF status 0 THEN 

(* could not read matrix *) 

erase = 1 

(* handle project overload, handle becomes invalid *) 

IF status = 100 THEN 

step := 0 

ENDIF 

ENDIF 

ENDIF 

(* erase the key matrix in case of error *) 

IF erase = 1 THEN 

LOOP i := 0 TO 47 DO 

mtxKeys[i] = 0 

ENDLOOP 

erase := 0 

ENDIF 

(* your key handling code goes here *) 

4.10.7.1.3.1.3 Declaration 

An array of USINT variables must be created using an appropriate length for the key matrix stored in the 

'mtxKeys' variable. If another length should be used, the VA_GetKeyMatrix function call must be adjusted 

4.10.7.1 Using the Key Matrix 395

accordingly in the cyclic program. 

4.10.7.1.3.2 3.2 ANSI C 

4.10.7.1.3.2.1 Source code 

#include 

#include #include "visapi.h" _LOCAL UDINT VC_HANDLE; _LOCAL UINT 

status; _LOCAL USINT step; _LOCAL USINT erase; _LOCAL USINT mtxKeys[48]; _LOCAL UDINT mtxSize; 

_INIT void SetupKeyMatrix(void) { step = 0; erase = 1; } _CYCLIC void RunKeyMatrix(void) { int i; /* 

get handle for project "vga1" */ if (step == 0) { VC_HANDLE = VA_Setup(1, "vga1"); if (VC_HANDLE) 

step = 1; } /* try to get the key matrix */ if (step == 1) { status = VA_GetKeyMatrix(1, VC_HANDLE, 

(UDINT) &mtxKeys[0], sizeof(mtxKeys) / sizeof(mtxKeys[0]), (UDINT) &mtxSize); if (status) { /* cannot 

read the matrix */ erase = 1; /* handle project overload, handle becomes invalid */ if (status == 

100) step = 0; } } if (erase == 1) { /* reset all key information to unpressed on error */ for (i = 

0; i < (sizeof(mtxKeys) /sizeof(mtxKeys[0])); i++) { mtxKeys[i] = 0; } erase = 0; } /* your key 

handling code goes here */ } 

4.10.7.1.3.3 3.3 Example Description 

In the Init subprogram, the 'init' and 'erase' variables are both preset so that a connection is established first with 

the respective project and the key matrix is started at 0. In this way, no key strokes can remain in the matrix if 

the visualization project has not yet been started. 

In the cyclic program, a connection is established with the current Visual Components project using the 

VA_Setup function. This is valid until a hardware is restarted or the visualization is overloaded. 

If successful, the key matrix is read with VA_GetKeyMatrix in the next code section. The size of the connected 

key matrix is specified here. The actual number of keys which were copied is returned in the mtxSize parameter. 

More keys than actually exist on the panel can also be requested. When touch keys are used, the number of 

keys changes depending on the currently displayed picture. The user should ignore keys which do not exist in 

the matrix or delete them. This is not included in the examples. 

If the error code determines that the handle has become invalid in the project, a new handle is requested and 

the matrix is deleted. 

The last part of the cyclic program deletes the key matrix at the beginning and if an error occurs. 

4.10.7.1.4 4. Adding the Application Logic 

The key matrix is ready to be used by the application when the application logic is added. The corresponding 

links can be placed in the the cyclic program right after the example code. 

4.10.7.2 Key Matrix from Visual Components Version 2.0 

For compatibility reasons, the key matrix from Visual Components Version 2.0 is still supported. However, using 

the new key matrix function is recommended. Future versions of Visual Components may not support the old 

key matrix. 

In order to replace the old key matrix with the new one, the old one must first be deactivated using the Visual 

Components global options. The new function is then used to acquire the new key matrix. 

4.11 Alarm System 


Alarms are used to record certain conditions and occurrences in a machine. These can include passing a 

threshold limit, an absence of a resource, unauthorized use of a component, or any other machine specific 

situation. 

Visual Components provides an integrated alarm system for managing and visualizing these alarms. The alarm 

396 4.10.7.1 Using the Key Matrix


system controls the monitoring/recording and display of these alarms (appearance and format). Writing to an 

alarm history list is also an option. 

4.11.1 Notes for Visual Components Version 2.0 Users 

Beginning with Automation Studio 2.2, tags (variables) can now be inserted in alarm texts. See Advanced Text 

Group Formatting. 

Advancements in the alarm system were made in Automation Software version 2.1. The following sections 

provide information about all alarm system innovations. 

Support for an alarm printer on the parallel interface is new in Visual Components 2.1. See Printing Alarms. 

In addition, Visual Components 2.1 supports an alarm history log. The number of stored alarms can be set. See 

Configuring the Alarm System. 

4.11.2 Preparations 

In order to use the Visual Components alarm system, a few things have to be prepared in the project. 

The following steps must be carried out: 

• Defining the Alarm Bit Field 

• Enabling the Alarm System 

These steps are explained in the following. 

4.11.2.1 Defining the Alarm Bit Field 

Information about which alarms are currently active must first be present for the alarm system (i.e. which states 

are occuring at the moment). 

The Visual Components alarm system uses one bit for each individual alarm to indicate if it is active or not. This 

bit is defined as a variable of type BOOL in the application task. 

All alarms that belong to a group must be arranged one after another in an array. The first alarm must be set 

with Index 0 of the array. The rest of the alarms follow directly in order. 

Division into groups takes place by the user according to logical groupings within the machine or equipment. 

Grouped alarms are constantly checked within Visual Components using the same attention to modification. 

Alarms which should be scanned frequently should be arranged into a single group. 

Depending on the programming language used in the project, the array for the alarm information is created as 

follows: 

4.11.2.1.1 ANSI C 

In the ANSI C programming language, the alarm bit array can be defined like every other PV in the C source file. 

The corresponding entry in the Automation Studio variable declaration dialog box is made automatically. 

The following source code can be used to create an alarm bit array for 50 alarms: 

#include 

#include 

_GLOBAL BOOL alarmbit[50]; 

The alarm bit array, like every other variable entered in Visual Components, must be defined as either locally 

(_LOCAL) for the application task or globally (_GLOBAL) for the controller project, as shown above. Pure ANSI 

C variables cannot be used. 

4.11.1 Notes for Visual Components Version 2.0 Users 397

4.11.2.1.2 IEC Programming Languages 

For the remaining Automation Studio programming languages, declaring the alarm bit array takes place 

uniformly using the variable declaration dialog box. The variable declaration dialog box can be opened by 

highlighting the application task in the software view of Automation Studio and selecting the 'Open −> 

Declaration' menu option. Other ways to open the declarations box can be found in the documentation of the 

project window or in the editors of the individual programming languages. 

The free row under the entries that already exist should be marked in the opened dialog box. The [INS] key 

enters a new variable. The new alarm bit array variable has to be entered in the Name column. 

The data type must be set to an array of BOOL variables. BOOL[50] must be entered into the Type column to 

create an alarm bit array for 50 alarms. 

The Scope column determines whether the variable should only be used locally in this task (i.e. only this task 

should enter alarms in this group), or globally in the entire project − LOCAL or GLOBAL. 

4.11.2.2 Enabling the Alarm System 

Since the alarm system is an optional component of Visual Components, it must first be switched on in the 

Project Options before it can be used (Panel). This setting is unique to each project and is stored as such. 

Therefore, it can be individually determined for each project whether the alarm system should be used or not. 

The alarm system is activated on the Panel page under the Alarm System group. 


398 4.11.2.1 Defining the Alarm Bit Field


When enabled, the alarm group is immediately added to the tree view on the left side of the panel. 

4.11.3 Configuring the Alarm System 

Some settings are made globally for the entire Visual Components alarm system. 

4.11.3.1 Global Configuration 

The appropriate dialog box is opened using the 'Configuration' option from the shortcut menu found in the tree 

view: 

Global settings are made under the 'Alarm Configuration' tab. Settings for printing out alarms are made under 

the 'Alarm Printer' tab. 

4.11.3.1.1 Language 

This setting determines which language the texts currently displayed in the dialog box are valid for. Texts can be 

customized for each language depending on requirements. 

4.11.3 Configuring the Alarm System 399

4.11.3.1.2 Texts 

All texts in this dialog box are used to display specified states in the alarm printout as long as they are used in 

the appropriate format. These texts must be adapted accordingly for each language in the project. 

The texts used in "Alarm System Printer Text Configuration" are used for printouts. These texts can also be 

displayed on large screens (at least 40 characters screen width). 

4.11.3.1.3 Alarm History List Length 

Triggered alarms are saved permanently on the controller. This setting defines how many alarms are stored in 

the alarm history log (ring buffer). Up to 1,000 alarm lines can be configured. In addition, they can be stored in a 

data object. Alarm data is lost howerver after the system is restarted. 

4.11.3.1.4 Status Abbreviations 

Pressing the "Edit" button opens the following dialog box: 

Letters and numbers can be defined here as abbreviations for different alarm states. They are used on small 

displays to represent as much information as possible about alarm conditions and changes. 

4.11.4 Using Alarm Groups 

Alarms which are in user tasks in a common alarm bit array are combined into group alarms. Each alarm group 

provides common settings which apply to all alarms in that group. Scan time is an important alarm group setting 

which specifies the time which is used for monitoring the individual alarm bits for changes. 

Each alarm in the Visual Components alarm system must be assigned to an alarm group. An alarm bit array 

must be assigned to this alarm group. Variables for bypassing alarms and acknowledgement status inquiries 

can also be connected. 

Each alarm group can contain a maximum of 128 alarms. 

4.11.4.1 Preset Alarms 


The 'System Alarms' group is always a part of the Visual Components alarm system. This group cannot be 

edited or removed. 

400 4.11.3.1 Global Configuration


In this group, alarms are defined which are triggered within Visual Components or Automation Runtime. These 

include a printer buffer overflow when printing alarms or an empty buffer battery in the controller, for example. 

Although system alarm group numbers and parameters cannot be edited, the individual alarm texts can be 

modified and adapted to requirements. If more than one language is used in the project, a separate column for 

each language is displayed in the alarm list. Alarm texts may be edited for each language. 

4.11.4.2 Adding, Removing, and Editing Groups 

A new alarm group can be added by selecting 'New' in the 'Alarm Groups' shortcut menu. A name has to be 

entered for this alarm group. 

After entering the name, a dialog box opens automatically to edit the alarm group settings. 

An alarm group can also be edited or removed using the shortcut menu options. 

4.11.4.2 Adding, Removing, and Editing Groups 401

4.11.4.3 Alarm Group Parameters 

After creating an alarm group, a parameter dialog box opens automatically. The parameter dialog box can also 

be opened by selecting the 'Properties' option from the shortcut menu of the group itself. Settings in this dialog 

box apply to all alarms in this group. 

4.11.4.3.1 Alarm Bit Field 

At least one BOOL array variable must be connected to the 'Alarm Bit Field' in the alarm group settings. If this 

variable is not connected, then an error will be displayed when closing the dialog box with the OK button. If the 

variable is not present while compiling the project, an error message will also be output. This alarm variable is 

checked for status changes and the assigned alarm texts are displayed accordingly. 

The first alarm in the group corresponds to the bit at array position 0, the second alarm at position 1, etc. 

4.11.4.3.2 Group Alarm 

During alarm configuration, there is an option to specify whether this alarm can trigger a group alarm. If a 

change in the alarm variable status causes this alarm to be displayed, this variable remains set to "1" until all 

alarms in that group which can trigger a group alarm have been reset and/or acknowledged. The variable is then 

reset to 0. 

Specifying this variable is optional. 


402 4.11.4.3 Alarm Group Parameters


4.11.4.3.3 Bypass Image 

A triggered alarm can be ignored when it is bypassed, i.e. it is not indicated in the alarm array. The size of the 

bypass image must be identical to that of the alarm bit field (BOOL array). The image position in the bypass 

image is that of the triggered alarm. 


4.11.4.3.4 Acknowledgement Image 

The acknowledgment image is written to the connected variable when an unacknowledged alarm is 

acknowledged or when a group acknowledgment takes place for the connected variable. The size of the 

acknowledgement image must be identical to the alarm bit field. In other words, both have to be of data type 

BOOL, and the array length must be the same. The position of the image in the acknowledgment image is that 

of the occurring alarm. 


4.11.4.3.5 Alarm Scan Rate 

The alarm scan rate defines how often the alarm image is cyclically read by the alarm system for each group. 

The respective bit in the alarm bit field has to maintain its status for at least this amount of time so that the alarm 

is recognized as safe. 

4.11.4.3.6 Priority 

This entry sets the priority of all alarms in an alarm group. Priority can optionally be displayed in alarm arrays, or 

it can be evaluated in the alarm history log using filter functions. The display of alarms according to priority is 

only evaluated in the Last Alarm alarm line. The last unacknowledged alarm with the highest priority is output in 

this field. 

Priority Scale: 

Lowest priority 

0 

Highest priority 

9 

4.11.5 Creating and Configuring Alarms 

In Visual Components, alarms are managed in alarm groups. Alarms can only be created if alarm groups are 

present and have already been configured. See Using Alarm Groups. 

4.11.5.1 Setting Up and Editing Alarms 

A new alarm can be inserted into the list by selecting the menu option "Insert Alarm" in the shortcut menu of the 

appropriate alarm group. An alarm can also be created with the [INS] key. A maximum of 128 alarms can be 

defined per alarm group. 

4.11.4.3 Alarm Group Parameters 403

A dialog field is displayed in which the alarm text for the default language can be entered. The default language 

is always the furthest to the left in the table. The text for the other languages can be entered once the dialog box 

is closed. By default, texts entered for the default language are also set to the other languages. 

In addition, tags (formatted variables) can be inserted in alarm texts. Formatting is limited to 4 numeric variables 

per text when alarm texts are used. The exact procedure is explained in Advanced Text Formatting. 

With the help of the icons in the toolbar, the sequence of texts can be adjusted to the position of the 

alarms in the alarm bit array. For an alarm which needs to be moved, it should be selected and moved to the 

correct position using these buttons. The keys [CTRL]+[up arrow] or [CTRL]+[down arrow] can also be used to 

to move alarms. 

An alarm can be deleted with the toolbar icon. The [DEL] key can also be used. 

4.11.5.2 Alarm Properties 


Selecting the "Properties..." menu option from the shortcut menu of an alarm entry allows the properties of the 

selected alarm to be edited. 

404 4.11.5.2 Alarm Properties


This opens the following dialog box: 

4.11.5.2.1 Acknowledgement Possible 

This entry determines whether acknowledgement of an occurring alarm is possible and is further evaluated by 

the "Acknowledgement Necessary" option. 

4.11.5.2.2 Acknowledgement Necessary 

This entry determines whether acknowledging a triggered alarm is absolutely necessary. 

4.11.5.2.3 Allow Acknowledge While Active 

This entry determines whether an active alarm can be acknowledged or not. 

Acknowledgement possible = yes 

Acknowledgement necessary = yes 

Allow acknowledge while active = no 

If an alarm is displayed, then it is only taken off the alarm display if it is also acknowledged, 

regardless of whether the alarm bit is reset. 


Acknowledgement necessary = no 


If an alarm is displayed, then it can be acknowledged until the alarm bit is reset. If the alarm bit 

is reset before it is acknowledged, it is removed from the display. 

Acknowledgement possible = no 



4.11.5.2 Alarm Properties 405

The alarm text is displayed as long as the alarm bit is set. Acknowledgement is not possible. 



Allow acknowledge while active = yes 

The alarm text is displayed as long as the alarm bit is set. Acknowledgement is then allowed 

while the alarm is active. The alarm is taken out of the list. 


Acknowledgement necessary = yes 

Allow acknowledge while active = yes 

If an alarm is displayed, then it is only removed from the list if it is acknowledged − regardless of 

whether the alarm bit is reset or not. 

Acknowledgement is also allowed while the alarm is active. The alarm is taken out of the list. 

4.11.5.2.4 Bypass Allowed 

This entry determines whether bypassing this alarm is possible. An alarm can be bypassed or have a bypass 

cleared in the alarm overview. If an alarm is bypassed, it is removed from the alarm list regardless of the alarm 

status. If a bypass is cleared, the alarm is displayed again corresponding to the alarm status. 

4.11.5.2.5 Trigger Group Alarm 

If this entry is selected, this alarm is included in the evaluation of the group alarm. The group alarm is a sum 

alarm for the group and indicates whether one of the groups, having an alarm with this option marked, is to be 

flagged (see also Group Alarms). 

4.11.5.2.6 Latched Alarm 

This entry determines whether the time for the first occurrence of the alarm should be displayed. If the alarm 

status changes repeatedly, then the time of the first occurrence is displayed in the alarm list, depending on the 

acknowledgement configuration. 

4.11.5.2.7 Disable Printing When... 

This entry determines that an alarm of a corresponding type does not appear in the historical alarm list or in a 

printout. Other output formats for the alarms are not affected by it. 

4.11.6 Alarm Visualization 

A sequence of special fields exists which can be used according to user needs and existing hardware (screen 

size, etc) to display triggered alarms on the visualization device. 

To insert these types of fields, an additional button is enabled in the toolbar when the alarm system is activated. 

Clicking on the button opens a selection list showing the following available alarm fields: 


Each of these fields has special properties and application possibilities. The following sections describe the 

properties and possibilities for each of these fields. 

Note: 

Only one alarm field can be used per picture. For example, it is not possible at present to use both an alarm line 

406 4.11.5.2 Alarm Properties


and an alarm summary on the same page. 

Alarm fields cannot be defined in the global picture. 

A detailed breakdown of all features can be found in the reference manual. Corresponding references are 

provided at the end of this document. 

General knowledge of Visual Components picture editor operation is assumed in this section. Corresponding 

references are found at the end of this document. 

4.11.6.1 Alarm Line 

Only one alarm from the list of pending alarms is displayed in an alarm line. The following settings are possible 

for an alarm line: 

4.11.6.1.1 Type of Alarm Line 

There are three types of alarm lines to choose from: 

First Alarm 

Last Alarm 

Active Alarm 

This field displays the oldest unacknowledged alarm. If all alarms are acknowledged, then the 

oldest acknowledged alarm is displayed. If no alarms are active, the default text configured in 

the global settings is displayed. The displayed alarm can be acknowledged. 

This field displays the newest unacknowledged alarm with the highest priority. If all alarms are 

acknowledged, the newest acknowledged alarm with the highest priority is displayed. If no 

alarms are active in the entire system, the default text configured in the global settings is 

displayed. The displayed alarm can be acknowledged. 

4.11.6.1 Alarm Line 407

4.11.6.1.2 Format 

This field shows the last queued alarm. Cursor keys can be used to scroll through alarm entries 

in this list. The displayed alarm can be acknowledged. 

Defines the length of the alarm line in characters and the font to be used. 

4.11.6.1.3 Key Assignment 

Determines the keys which are to be used for the corresponding action. These could be either keys from the 

operator panel being used (configured as function keys) or buttons/hot spots in the case of panels with touch 

screens. 

A corresponding function key has to be assigned to each key. Otherwise, otherwise an error message appears 

and the dialog box cannot be closed with OK. 

The 'Previous Alarm' and 'Next Alarm' keys are only provided for 'Active Alarm' lines. The other alarm line types 

only have an 'Acknowledgement' key. 


Under the 'Colors' tab of the dialog box, colors used for alarm line display can be set or a color control variable 

can be connected. 

The information displayed in the alarm line and the separators to be used are set under the 'Field Format' tab. A 

detailed listing of all settings can be found in the reference manual (see references at the end of this page). 

4.11.6.2 Alarm List 


An alarm list displays the same information as an 'Active Alarm' line but displays several lines. Field size can be 

selected as desired, but the number of alarms which can be displayed simultaneously depends on the available 

display surface and the selected font. 

Two keys can be used to scroll thorough the previous (newer) or next (older) alarms in the alarm list. The alarm 

with the current cursor focus can be acknowledged with the acknowledgement key. The function keys to be 

used must be configured (see below). 

408 4.11.6.1 Alarm Line


4.11.6.2.1 Format 

In contrast to the alarm line, the number of lines displayed in the field can be defined for alarm lists. All other 

settings are identical to the alarm line. 


Essentially, the same settings as for an alarm line are provided. 

See above 

4.11.6.3 Alarm Summary 

All alarms are displayed in the alarm summary regardless of their status. Two keys can be used to scroll through 

the previous (older) or next (newer) entries in this alarm summary. Using the 'Bypass' key, an alarm can be 

bypassed or not bypassed as long as this is allowed for the respective alarm. 

Alarm summary output can be influenced using Alarm Number Filters and Group Number Filters. 

4.11.6.2 Alarm List 409

Alarm summary settings correspond to the pattern already described for the alarm list. 

4.11.6.3.1 Format and Position 

Specifies the position, size, and font to be used. 


A function key has to be connected to the 'Bypass,' 'Previous Alarm' and 'Next Alarm' keys. Of course, 

appropriate touch−operated fields can also be connected here. 


The alarm field display format is configured under the 'Field Format' tab. Optional variables for filtering alarms 

are defined under the 'Filter' tab. 

4.11.6.4 Alarm History 


Depending on the configuration of the alarms under the 'Disable Printing When...' setting, each alarm event is 

entered in an alarm history list and can be displayed using this field. In this alarm summary, alarms can be 

scrolled through using two keys for the previous (older) or next (later) entry. 

410 4.11.6.3 Alarm Summary


4.11.6.4.1 Format and Position 

Specifies the position, size, and font of the field. 


For key assignment, a function key has to be connected to the 'Previous Alarm' and 'Next Alarm' keys. 

Appropriate touch−operated fields can also be connected. 


The alarm field display format is configured under the 'Field Format' tab. Optional variables for all historical 

alarm list filtering possibilities are defined under the 'Filter' tab (Alarm Number Filter and Group Number Filter ). 

4.11.7 Optimizing the Alarm Display 

This section describes additional options for customizing alarm displays to user wishes and hardware 

requirements (i.e. display size). 

These options are provided for all alarm fields to a varying extent. This depends on the constraints of various 

fields and differences in settings. 

This section contains descriptions for options which concern alarm appearance: 

• Adjusting the Display Format 

• Adjusting Status Abbreviations 

• Filtering the Displayed Alarm 

These measures can be combined as desired, depending on application requirements. 

4.11.7.1 Adjusting the Display Format 

The display format of a single alarm line can be customized to user needs. Depending on the tasks of various 

alarm fields, useful combinations are displayed for selecting the different information and display options for 

alarm fields. 

4.11.6.4 Alarm History 411

Settings for all alarm fields can be found individually under the 'Field Format' tab. 

'Field Format' for the alarm list is displayed here as an example. The other alarm fields have different dialog tabs 

but the function is identical for all alarm fields. 

Depending on the settings, it can be determined whether the corresponding information is displayed or not (and 

in which format). 

4.11.7.1.1 Cursor Character (all alarm fields except the alarm line) 

For alarm fields with several lines, the alarm list can be browsed through using two cursor keys. The selected 

line can be either displayed as inverted, or a cursor character appears before the alarm line (*, −, , # or ! can 

be used). 

4.11.7.1.2 Time Format (all alarm fields except the alarm summary) 

Time and date of alarm occurrences can be displayed for all alarm fields except for the alarm summary. This 

time format applies for all alarms in this alarm field. 

4.11.7.1.3 Group Number / Alarm Number (all alarm fields) 

If the alarm system consists of several alarm groups, the group and alarm numbers for this group can also be 

displayed (1−3 places). Displaying corresponding numbers can also be disabled. 

4.11.7.1.4 Alarm Text (all alarm fields) 

If an alarm is detected during runtime, it can be displayed as text. This is set as default but can also be changed 

as needed. If changed, the alarm number (and if necessary the group number) should be displayed at the very 

least. 

4.11.7.1.5 Info (active alarm line, alarm list) 


In addition to the alarm text, acknowledgement information can be displayed in the alarm line and alarm list. The 

corresponding status abbreviation can be changed in the global options of the alarm system and set separately 

for each language. 

412 4.11.7.1 Adjusting the Display Format


4.11.7.1.6 Priority (active alarm line, alarm list, alarm summary) 

Outputs the priority of the alarm which was configured in the alarm group. 

4.11.7.1.7 Alarm Status (alarm summary) 

The alarm status (active/inactive) is displayed with the appropriate abbreviation. This abbreviation can be 

individually set for each language in the global options menu of the alarm system. 

4.11.7.1.8 Acknowledgement Status (alarm line for the first/last alarm, alarm summary, alarm history) 

The alarm acknowledgement status (acknowledged / unacknowledged) is displayed with the appropriate 

abbreviation. This abbreviation can be individually set for each language in the global options menu of the alarm 

system. 

4.11.7.1.9 Bypass Status (alarm summary) 

In the alarm summary, the alarm selected from the list can be either bypassed or not bypassed using a function 

key. The status (bypassed / not bypassed) can be displayed with an appropriate abbreviation. This abbreviation 

can be individually set for each language in the global options menu of the alarm system. 

4.11.7.1.10 Event (alarm history) 

Each event is entered into the alarm history (triggered, reset, acknowledged, etc.). The revised status can be 

entered in the list as text, a status abbreviation, or nothing at all. 

4.11.7.1.11 Separator (all alarm fields) 

Individual items of an alarm line can be divided using a separator (none − the fields follow directly after one 

another, space, period, hyphen). 

4.11.7.1.12 Preview 

The selected alarm text format is displayed here. The length of the alarm text is shortened and displayed 

according to the size of the alarm field. 

4.11.7.2 Adjusting Status Abbreviations 

This setting is accessed through the global alarm system settings. Thus, the settings apply uniformly to the 

entire project. However, settings can be made separately for each language present in the project. 

4.11.7.1 Adjusting the Display Format 413

4.11.7.2.1 Triggered / Reset (event) 

Abbreviations to be displayed indicating alarm triggering or resetting in the control application. These 

abbreviations are used to display status changes. 

4.11.7.2.2 Acknowledged / Unacknowledged 

Abbreviations indicating whether the corresponding alarm has been acknowledged or not. 

4.11.7.2.3 Alarm is on / off 0 (status) 

Abbreviations indicating whether the alarm was (still) active at the time of entry. These abbreviations are used to 

display the current status. 

4.11.7.2.4 Alarm bypassed / not bypassed (status) 

Abbreviations indicating whether the corresponding alarm is currently bypassed or not. 

4.11.7.2.5 Alarm bypassed / not bypassed (event) 

Abbreviations indicating if the alarm was bypassed or not. Thus, these abbreviations display changes in the 

alarm bypass status. 

4.11.7.3 Filtering the Displayed Alarm 

The alarm fields 'Alarm Summary' and 'Alarm History' have filter functions. Using these functions, alarm list 

output can be controlled during runtime, i.e. certain outputs in these lists can be suppressed. 

Both alarm fields support various filter possibilities depending on their task definition. Therefore, settings for the 

two fields are discussed separately. 

4.11.7.3.1 Alarm Summary 


414 4.11.7.2 Adjusting Status Abbreviations


4.11.7.3.1.1 Alarm Number Filter / Group Number Filter 

A variable can be connected for the Alarm Number Filter and/or Group Number Filter fields. If a variable is 

connected to the group filter, then only alarms of this group are displayed if the group number is valid. If a 

variable is not connected to Alarm Number Filter or an invalid alarm number is read, then all alarms are 

displayed starting with offset = 0. If the alarm number is valid, all alarms starting with this alarm number are 

displayed. 

If a variable is only connected to the Alarm Number Filter, then alarms from all groups can be displayed 

beginning with the valid alarm number. 

4.11.7.3.2 Alarm History 

4.11.7.3.2.1 Filter Control Byte 

If a variable is connected, the filter control byte is simultaneously evaluated with all alarm filters (if used). If no 

variable is connected, then no filter is active. 

Filter byte Meaning 

0 No filter active, all entries are displayed. 

1 "Newer than" filter 

2 "Older than" filter 

3 Group filter 

4 Priority filter 

5 "Newer than" and group filter 

6 "Older than" and group filter 

7 "Newer than" and priority filter 

8 "Older than" and priority filter 

9 "Newer than", group, and priority filter 

10 "Older than" , group, and priority filter 

11 Group and priority filter 

4.11.7.3 Filtering the Displayed Alarm 415

4.11.7.3.2.2 Group Number Filter 

The Group Number Filter uses the variables 'Filter Control Byte', 'Group Number Filter', and 'Alarm Number 

Filter'. Only group entries which are read from the 'Group Number Filter' variable are displayed. If a value of 0 or 

an invalid value is read, all alarms are displayed regardless of the group filter or alarm filter. 

If one of the valid alarm numbers for this group is in the 'Alarm Number Filter' variable, then alarms are 

displayed starting with this alarm. The latest event is displayed if the alarm number is valid but not evaluated by 

another Filter Control Byte condition, or if the alarm number is invalid or 0. 

4.11.7.3.2.3 Priority Filter 

The priority filter uses the 'Filter Control Byte' and 'Priority Filter' variables. Entries are only displayed if they 

have the same or higher priority as the variable value in 'Priority Filter'. 

4.11.7.3.2.4 Time Filter 

The time filter corresponds to the filter entries 'Newer Than' or 'Older Than'. It uses the 'Filter Time' and 'Filter 

Control Byte' variables. Entries are only displayed if the time is larger or smaller than the "Filter Time" variable. 

A variable with data type USINT array with the length of 6 bytes is to be connected to the time filter. The time 

format is entered in this USINT array as follows: 

Offset Contents 

0 Seconds 

1 Minutes 

2 Hours 

3 Day 

4 Month 

5 Year 

4.11.8 Printing Alarms 

Visual Components provides the possibility to connect an alarm printer to target systems which have parallel 

printer interfaces. Alarms are printed if their status is changed and this particular change has been selected to 

trigger printing in the configuration. 

The following steps should be followed to use an alarm printer: 

• Activating the Alarm Printer 

• Configuring the Printer 

• Configuring Status Texts 

• Configuring the Print Format 

4.11.8.1 Activating the Alarm Printer 

The alarm printer is activated in the global settings of the project (Panel) under the Alarm System group. 

4.11.8.2 Configuring the Printer 

After 'Use Alarm Printer' has been selected, the 'Printer Settings...' button is used to configure the settings for 

the printer. 

Clicking on 'Printer Settings...' opens the following dialog box: 


416 4.11.7.3 Filtering the Displayed Alarm


The settings here are explained in further detail. 

4.11.8.2.1 Printer Page Layout 

The number of lines on a page, as well as the number of characters per line, can be set here. Visual 

Components supports formatted printing on all line printers which can receive and print ASCII characters and 

which use character fonts with a fixed character width. 

The 'Form Feed' setting determines how a new page is started (or the previous ejected). The LF setting (line 

feed) is used for continuous paper feed. The FF setting (form feed) is used for sheet fed or page printers (i.e. 

LED or laser printers). 

Some printers require special settings in this field and/or on the printer itself. These features are not part of this 

documentation. Details about printers can be found in their user manuals. 

4.11.8.2.2 Printer Interface Configuration 

Currently, only parallel printers on the first parallel printer interface of IPCs are supported. Therefore, the 'Port' 

setting has to be set to LPT1. Remaining parameters are reserved for future updates and serial alarm printers. 

4.11.8.2.3 Printout Header Text 

Header text can be individually configured for every language in the project. The language currently set on the 

target system is used when printing. In this way, the printout matches the screen display. 

4.11.8.2.4 Printer Init Sequences 

These two adjustments enable the connected printer to be configured with [ESC] sequences. These are special 

character strings which allow the connected printer to recognize a command and execute appropriate actions. 

These character strings frequently begin with the [ESC] character − ASCII code 27. 

The first sequence is sent to the printer before printing begins; the second one is sent before each new page. 

This allows the printer to be configured to suit specific user needs. 

The [ESC] key can be used for inputting sequences directly just as the [CTRL] key can be used for shortcut 

combinations or the [ALT] and number pad keys for input. Details regarding possible sequences for the selected 

printer can be found in its documentation. 

4.11.8.2 Configuring the Printer 417

4.11.8.3 Configuring Status Texts 

As already described in the general configuration section of the alarm system, texts used for printing different 

alarm states can be adapted to print requirements. 

The appropriate dialog box is opened by selecting 'Configuration' from the Alarm Groups shortcut menu in the 

Visual Components project tree. 

Text can be customized for the events or states such as 'Triggered', 'Reset', 'Acknowledged', 'Unacknowledged', 

'Bypassed' and 'Not bypassed'. 

These settings can be made accordingly for each language in the project. For this, languages can be switched 

using the 'Language' selection list. 

4.11.8.4 Configuring the Print Format 


The second tab of the dialog field shown above is exclusively used for the alarm printer. The settings are 

entered as follows. 

418 4.11.8.3 Configuring Status Texts


4.11.8.4.1 Panel Printer Sequences 

[ESC] sequences can be defined here for alarm lines of different types. Thus bold print can be selected for 

certain events to set them apart from other alarms. 

Structures for necessary sequences are documented in the printer manual of the corresponding alarm printer. 

The [ESC] key can be used for inputting sequences directly just as the [CTRL] key can be used for shortcut 

combinations or the [ALT] and number pad keys for input. 

4.11.8.4.2 Panel Printer Configuration 

Determines the format for printer output. It can be chosen for each entry whether and how printing the 

corresponding information should take place. The currently set format is displayed in the Preview line. 

4.11.9 Group Alarms 

Group alarms make it possible to form a sum alarm from groups of alarms. Exactly one group alarm can be 

formed for each alarm group which has been configured in the alarm system. It can be determined for each 

alarm in this group whether it should be included in the formation of the group alarm. 

4.11.9.1 Operation 

Visual Components has a special group within the alarm system in which group alarms are defined. As with 

system alarms, the user cannot add or remove any alarms here. 

4.11.8.4 Configuring the Print Format 419

As shown in the dialog box, each alarm group created by the user (not the system and group alarms) is 

automatically assigned an alarm in this group. The sequence of the alarms in this list corresponds to the 

sequence of the alarm groups in the project tree. 

The alarm text of each individual group alarm can be edited for all languages in the project. 

The number of each alarm group (and thus of the accompanying group alarm) is displayed in the outline of the 

alarm system (select 'Alarm Groups' in the project tree). 

4.11.9.2 Settings 


Group alarms have the same properties as every other alarm in the system (however, the setting 'Trigger Group 

Alarm' has no effect). The settings can be accessed from the group alarm shortcut menu. 

420 4.11.9.2 Settings


Alarm properties are identical to those of a 'normal' alarm. 

Individual properties are described in the alarm properties (Creating and Configuring Alarms). 

4.11.9.3 Choosing Alarms for the Group 

Whether or not the corresponding group alarm should be triggered for a specific alarm is set under that alarm 

(shortcut menu of the respective alarm). 

The option 'Trigger Group Alarm' is selected in order to integrate an alarm to the group alarm formation. 

4.11.9.3 Choosing Alarms for the Group 421

As a result, the appropriate group alarm is active and is used together with the individual alarms for all areas of 

the alarm system. 

If a group alarm is acknowledged, then the triggering alarm is also acknowledged as long as it is valid. This also 

applies to bypassing alarms. 

4.11.10 Bypass and Acknowledgement Images 

In addition to the alarm bit field, two more connections of individual alarms can be made between the Visual 

Components alarm system and the control application. The user then has the option to acknowledge or bypass 

the alarms. 

4.11.10.1 Usage 

The alarm bit fields for bypass and acknowledgement use the same indexing (item numbering). In other words, 

the alarm in item [2] of the alarm bit field is connected with the acknowledgement information in item [2] of the 

acknowledgement bit field and the bypass information in item [2] of the bypass bit field. 

4.11.10.1.1 Bypass Bit Field 

In the bypass bit field, the alarm system records whether the appropriate alarm was bypassed. In this way, a 

block caused by the alarm can be bypassed using the controller. 

A data element in the bypass bit field is 0 if the alarm is bypassed, and 1 if the alarm is not bypassed. 

Evaluation of the bypass must take place in the control application. The alarm system only provides the 

necessary control elements and the bypass bit field for the application. 

4.11.10.1.2 Acknowledgement Bit Field 

This bit field contains information concerning whether the appropriate alarm has been acknowledged. This 

information can be evaluated in the control application. 

A data element in the acknowledgement bit field is 1 if the alarm is acknowledged, and 0 if unacknowledged. 

Alarm latch implementation, which requires acknowledgement, is provided in the Visual Components alarm 

system display. 

Advanced alarm acknowledgement processes are very application specific and must be programmed in the 


4.11.10.2 Setting Parameters 


Variables for the bypass and acknowledgement bit fields, if used, must have the same data type and length as 

the alarm bit field. This also applies if only alarms with a lower index are considered for bypass or 

acknowledgement in the application. 

422 4.11.10 Bypass and Acknowledgement Images


Variables for the bypass bit field are connected in the Alarm Group settings dialog box. Settings for a group of 

alarms can be accessed in the shortcut menu of Visual Components editor tree view. 

Group properties can be displayed where the bypass bit field and/or the acknowledgement bit field can be 

connected. 

In this dialog box, the appropriate bit fields can be entered under 'Bypass Image' and 'Acknowledgement Image'. 

Configuring whether an alarm can be bypassed (allowable by the alarm system) or whether an alarm can/must 

be acknowledged affects each alarm individually and is described in the appropriate section. 

4.11.11 General − VISAPI 

4.11.11.1 General Information 

A connection to a project must be established before a VISAPI function can be used. This is accomplished with 

the functions VA_Setup or VA_SetupX. These functions return a handle which must be transferred to all 

following VISAPI function calls. This handle identifies the project specified with VA_Setup or VA_SetupX and is 

4.11.11 General − VISAPI 423

esponsible for managing access. 

4.11.11.2 Requirements 

There are a few rules concerning the VISAPI that must absolutely be observed. 

4.11.11.2.1 1. Screen Access 

Each VISAPI function which draws something on the screen must be called between the VA_Saccess and 

VA_Srelease functions. Several VISAPI drawing functions may be called in one block. 

VA_Saccess attempts to reserve access to the screen for the task. If successful, the function returns 0. 

Otherwise, it returns a corresponding error code. Drawing functions can only be used if VA_Saccess was called 

successfully. 

VA_Srelease gives up access to the screen again so it can be used by other tasks or the Visual Components 

interpreter. 

Warning: 

If VA_Srelease is not called after VA_Saccess was successfully called, then other tasks (or the Visual 

Components interpreter) cannot access the screen. 

If your visualization project uses VISAPI and suddenly 'freezes', then make sure that you have correctly called 

VA_Srelease! 

Example in the C Programming Language: 

if (!VA_Saccess(TRUE, handle)) 

{ 

VA_Line(......); 

VA_Rect(......); 

VA_Srelease(TRUE, handle); 

} 

4.11.11.2.2 

Cyclic Operation 

The VISAPI library is designed to operate in cyclic tasks. In particular, this should be considered when using the 

VA_Saccess function. If this function returns an error stating that access to the screen is not possible at the 

moment, then a new attempt is made in the next cycle. 

It usually doesn't make sense to try reserving the screen in the same cycle. An exception might be if VISAPI 

drawing functions are carried out in a higher priority task class. 

Example in the C Programming Language: 

_CYCLIC void main(void) 

{ 

if (!VA_Saccess(TRUE, handle)) 

{ 

VA_Line(......); 

VA_Rect(......); 

VA_Srelease(TRUE, handle); 

} 

} 

4.11.11.2.3 Cycle Times 

Like every other control task, a VISAPI task runs during a fixed cycle time. This should be considered when 

programming with the VISAPI. Functions which require longer times to carry out drawing functions (i.e. ellipse) 

can cause cycle time violations under certain circumstances if they are placed in faster task classes. 

If necessary, place the task in a slower task class of use fewer functions in one cycle. 


424 4.11.11.2 Requirements


4.11.12 General/Drawing − VISAPI 

This is an example of a small VISAPI program in the B&R Automation Basic programming language, followed by 

an explanation: 

1: 

2: 

3: 

4: 

5: 

6: 

7: 

8: 

9: 

10: 

11: 

12: 

13: 

14: 

15: 

16: 

17: 

18: 

19: 

20: 

21: 

22: 

23: 

24: 

25: 

26: 

27: 

28: 

29: 

30: 

31: 


x1 = 100 

y1 = 150 

x2 = 250 

y2 = 250 

height = 40 

width = 80 



If ready 1 Then 

VC_HANDLE = VA_Setup(1 , "vga") 

If VC_HANDLE 0 Then 

ready = 1 

EndIf 

EndIf 

If ready = 1 Then 

If VA_Saccess(1,VC_HANDLE)= 0 Then 

VA_Rect (1,VC_HANDLE,x1,y1,x2,y2,fill,color) 

VA_Line (1,VC_HANDLE,x1,y1,x2,y2,color) 

;Draws a rectangle 

;Draws a line 

VA_Ellipse(1,VC_HANDLE,x2,y2,heigth,width,fill,color) ;Draws an ellipse 

VA_Textout (1,VC_HANDLE,1,100,100,color,fill,"a rectangle, a line and an ellipse");Outputs a te 


EndIf 

EndIf 

This program draws a rectangle, a line, an ellipse, and outputs text. The following steps are required to do this: 

Line(s) Description 

3 − 10 Initializes variables 

12 This flag stores whether the VISAPI has already been successfully initialized. 

13 

16 

Initializes the VISAPI and establishes the connection to the specifed project ('vga' in this example). If 

the project name is valid and the VISAPI library is initialized, then a handle is returned which is stored 

in the VC_HANDLE variable. 

VC_HANDLE is valid, since it is 0. Therefore, the initialization flag can be set to 1 to prevent 

repeated initializations and let the rest of the task continue. 

19 Checks whether the VISAPI is initialized. 

20 Calls VA_Saccess since drawing should now begin. 

21 − 27 VA_Saccess did not return any errors, therefore drawing can take place. 

29 After a successful VA_Saccess(...) call, VA_Srelease absolutely has to be called. 

4.12 Tips and Tricks 

Many functions are tightly integrated in Visual Components and can be used right away. This section gives more 

information about additional Visual Components options. 

Usually, only a few lines of code are necessary to implement striking effects and completely new functions. 

4.12.1 A Few Tips 

• Configuring a Help Picture 

• Input Field Cursor Navigation 

• Blinking Text (or Button) 

4.11.12 General/Drawing − VISAPI 425

• Logging User Actions 

• Creating Recipe Management 

• Adjusting the Touch Pad 

• VC System Tuning 

• Importing / Exporting Panel Projects 

• Creating a Separate Number or Alpha Pad 

4.12.2 Configuring a Help Picture 

4.12.2.1 Problem 

A picture with help text has been configured in the project. Several pictures can branch to this picture. This help 

picture should lead back to the source picture using a 'Back' button or key. 

How can this be achieved without additional programming and knowledge about the source picture? 

4.12.2.2 Solution 

By configuring a picture change on the current picture, the runtime system saves the previous picture internally 

(the caller of the new picture). If there has been a picture change configured in the 'Help' picture which leads to 

the same (help) picture, then it changes to the previous picture (caller of the picture) during runtime. 

4.12.3 Input Field Cursor Navigation 


A configured picture looks like the one below. The 'Up,' 'Down,' 'Left', or 'Right' keys should be used to navigate 

between the input fields or change their order. 


The input change order becomes visible by pressing 'CTRL + D' in the picture editor. Using a number, the order 

of the input fields which are called after pressing the 'Enter' key is shown. Clicking through the input fields in the 

desired order can change this. 

Pressing 'CTRL + D' again deactivates this view. 


Navigation can also take place using cursor keys. To do this, 4 function keys need to be defined. In the key 

shortcut menu, the desired direction is defined under 'Goto Input'. 

426 4.12.2 Configuring a Help Picture


During runtime, the next input field within the width of the current output field is looked for in the defined cursor 

direction. If there is no input field available in this direction, or if the next input field is outside the width of the 

output field, then searching continues on the other side of the screen (i.e. with 'search direction up', it will search 

again from the bottom of the screen). If there is still no available input field, then focus switching does not occur. 

4.12.4 Blinking Text (or Button) 


A text or button should blink to make the user aware of a certain situation. 


A color variable can be connected to the text or the button. 

The 'text blink effect' variable must switch the foreground and background colors using a particular timing (see 

also Dynamic Color Control). 

The same applies to blinking buttons or other elements. 

4.12.4 Blinking Text (or Button) 427

4.12.5 Adjusting the Touch Keypad 

Visual Components touch keypads have a very simple design and can be used directly in most applications. If 

desired, the keypad can be modified to suit the look and feel of the application. 

Visual Components keypads were designed as bitmaps and can be modified as needed. However, only the 

design of the keys can be modified, not the function or the layout. 

Any graphics program which supports the Windows Bitmap format (.BMP) can be used to edit the keypad 

bitmaps. 

Visual Components runtime handles and displays the touch keypads just like any other bitmap. 256 colors are 

available just like for all other bitmaps in the project (see also Color Table). 

Various keypad bitmaps are added to the project depending on whether a 1/4 VGA display or a VGA (or larger) 

display is used. If a 1/4 VGA display is used, a bitmap for the numeric keypad and three bitmaps for the 

alphanumeric keypads are integrated (each 'page' uses a separate bitmap). For VGA (and larger), two bitmaps 

are integrated: One for the numeric keypad and one for the alphanumeric keypad. 

4.12.6 Tips and Tricks 

4.12.6.1 Logging User Actions 

Logging user actions for security reasons is an important topic. Visual Components does not offer a complete 

solution here. 

By using a few existing components and some programming code, a relatively easy solution for this problem can 

be found. 

The following lines do not contain a complete example. Instead, they only show ideas and concepts which can 

be used to record when a user logs on and logs off. Of course, this approach can be expanded later to record 

picture changes or the altering of values in variables. 

The Alarm System from Visual Components is used for this plan. 

Times when a user logs on and logs off are recorded in a separate alarm groups. 

A string input field allows the entry of the user name. String fields also provide the possibility to hide input 

(Mode: Password) which is used for password input. 

The password and user name are checked in the application program. If input is valid, then the user login time is 

recorded by having the alarm system set the corresponding alarm bit. 

Texts for user login and logout data are defined in the alarm group. 


The alarm system logs this entry with the system time and permanently saves the entry in the alarm history. 

On the alarm page, the actions of a certain 'user' alarm group can be output using group and alarm filters. Only 

alarms from a certain alarm group can be shown if a group filter is used. 

Note: 

Changes in machine data can also be recorded using this method. Multilingual output of alarm texts is also 

possible. 

428 4.12.5 Adjusting the Touch Keypad


4.12.7 Tips and Tricks 

4.12.7.1 Creating Recipe Management 

The following section describes simple recipe management using Visual Components and dynamic variables. 

Data is stored in a user−defined structure and displayed with the help of dynamic variables. 

Notes for dynamic variables: 

• What is a dynamic PV? 

• How does it differ from 'normal' PVs? 

• Why are dynamic PVs necessary? 

• How is a dynamic PV stored? 

Notes for recipe management: 

• Executing the Recipe Page 

• Coding Example in Automatic Basic 

• Coding Example in ANSI C 

4.12.7.1.1 What is a Dynamic PV? 

A dynamic PV (process variable) is a reference or pointer to a 'normal' PV. Due to this property, it is possible for 

a dynamic PC to reference several static variables of the same type during its lifespan. Dynamic PVs can only 

be used in the Automation Basic and ANSI C languages. 

4.12.7.1.2 How Does it Differ from 'Normal' PVs? 

4.12.7.1.2.1 Memory Allocation 

The biggest difference is in its memory usage. While a static variable occupies its actual physical size in the 

memory (i.e. ULONG = 4 bytes), a dynamic PV is only a reference to a static variable, i.e. in reality it only 

contains the address of the static PV it refers to. However, since addresses also occupy 4 bytes in the memory, 

this difference only has an effect when using arrays and structures with several elements. 

4.12.7.1.2.2 Dynamic Response of Contents 

Dynamic PVs have the ability to switch between several static PVs using their referencing property. However, a 

reference is more than simply 'pointing'. When a dynamic PV points to a static PV, it also provides access to the 

data contained in the static PV. 

4.12.7.1.3 Why are dynamic PVs necessary? 

4.12.7.1.3.1 Example: 

Only one element should be displayed in the visualization unit from an array which contains various data (i.e. 

recipe data). Whichever data an index variable refers to is displayed. 

In the variable output field on the display, an output field of the same data type as the array element is used and 

linked to a dynamic variable. Depending on the value of the index variable, the corresponding static array value 

which is referenced by the dynamic variable is displayed. 

Advantages of dynamic variables: 

If a recipe (structure array) is stored in an application task, then not all recipes also have to be configured in the 

visualization application and connected to individual components. A recipe (controller, parameter sets) and its 

elements only have to be configured using dynamic variables. They can then switch between the individual 

recipes in the application task using a recipe index. 

4.12.7.1.4 How is a dynamic PV stored? 

There are differences between Automation Basic and ANSI C when creating dynamic PVs. 

4.12.7 Tips and Tricks 429

4.12.7.1.4.1 In an Automation Basic task 

1. Uses the PV in the code: 

The dynamic variable name is defined in the variable declaration dialog box after the variable name is 

declared in the source code and ENTER is pressed. However, the dynamic PV has to reference a static 

PV in the source code (i.e. rec_array access adr(stat_array)). 

2. Properties Change: 

The scope of the dynamic variable changes from 'remanent' to 'dynamic'. 

Automation Basic Example 

4.12.7.1.4.2 In a C task 

A dynamic PV is declared in C using the following syntax: 

_LOCAL *; 

The PV must be declared as _LOCAL. 

C Example 

4.12.7.2 Executing the Recipe Page 


The following example shows the recipe page execution (including Automation Basic and ANSI C code) on the 

basis of the dynamic PVs decribed above. 

430 4.12.7.1 Creating Recipe Management


The input field for the recipe no. is connected to the static PV (see code). Input fields for 

elements 1 − 5 are connected to the dynamic PVs to (see code). 

The contents of the fields for elements 1 − 5 can now be controlled using the recipe number. A change in the 

recipe number in the code causes the dynamic PV to 'transfer' to the array element with the index 

. Both the array (with 5 elements) and the dynamic PV are of type which 

contains 5 UDINT (unsigned long) elements (elem1 − elem5). 

4.12.7.3 Code in Automation Basic 

4.12.7.3.1 Initialization Section 

In the initialization section, 5 array elements of type are initialized with values, the current recipe 

number is set to recipe 1, and the old recipe number is set to 0. The control 

variable is set to 1 if the new recipe number differs from the old number; it is set to 0 at the 

beginning. 


loop i = 0 to 5 do 

rec_arr[i].elem1 = 100 * i + 1; 

rec_arr[i].elem2 = 100 * i + 2; 

rec_arr[i].elem3 = 100 * i + 3; 

rec_arr[i].elem4 = 100 * i + 4; 

rec_arr[i].elem5 = 100 * i + 5; 

endloop 

recipeNrAct = 1; 

recipeNrOld = 0; 

recipeChanged = 0; 

4.12.7.3.2 Cyclic Section 

The cyclic part checks whether the current recipe number is different from the old recipe number 

if the user selects a new recipe number using an input field. In this case, the new recipe number 

4.12.7.3 Code in Automation Basic 431

eplaces the old recipe number and the control variable is set to 1. 

In order to avoid invalid memory accesses, recipe number input is checked for the max. available recipes. 

The second IF−statement is fulfilled if the control variable 0. In other words, the dynamic variable references 

the current recipe number. 


if (recipeNrAct recipeNrOld) then 

if (recipeNrAct > 5) then 

recipeNrAct = 5; 

endif 


recipeNrOld = recipeNrAct; 

endif 

if (recipeChanged > 0) then 

pRec access adr(rec_arr[recipeNrAct−1]); 


endif 

Read the Notes at the end of the chapter. 

4.12.7.4 Code in ANSI C 

The code described above in C: 

#include 

#include struct recipe { unsigned long elem1; unsigned long elem2; 

unsigned long elem3; unsigned long elem4; unsigned long elem5; }; struct recipe rec_arr[5]; _GLOBAL 

unsigned char recipeNrAct; _GLOBAL unsigned char recipeNrOld; _GLOBAL unsigned char recipeChanged; 

_LOCAL struct recipe *pRec; _INIT init_func(void) { int i; for(i = 0; i < 5; i++) { rec_arr[i].elem1 

= 100 * i + 1; rec_arr[i].elem2 = 100 * i + 2; rec_arr[i].elem3 = 100 * i + 3; rec_arr[i].elem4 = 

100 * i + 4; rec_arr[i].elem5 = 100 * i + 5; } recipeNrAct = 1; recipeNrOld = 0; recipeChanged = 0; 

} _CYCLIC cyc_func(void) { if(recipeNrAct != recipeNrOld) { if(recipeNrAct > 5) { recipeNrAct = 5; } 

recipeChanged = 1; recipeNrOld = recipeNrAct; } if(recipeChanged > 0) { pRec = 

&rec_arr[recipeNrAct−1]; recipeChanged = 0; } } 

4.12.7.4.1 Important notes 

A dynamic variable does not limit itself to referencing static variables of the same data type; rather, it can 

reference any memory address. However, this can lead to big problems. When using dynamic variables, it 

should be noted that they should already be initialized when first accessed (null pointer error) and not pointed to 

an invalid memory range during runtime. 

If limits were not set for the max. recipe number in the above example, a value of another variable or even 

program code could have possibly been overwritten. This can crash a program or cause invalid data to be 

displayed. 

4.12.8 VC System Tuning 

All Visual Components runtime modules are tied to the system as non−cyclic tasks with lower priority than cyclic 

tasks. Cyclic user tasks (task classes) are therefore not influenced by runtime performance. Visual Components 

runtime modules run in the system idle time with low priority. 

A simple and clear definition of timing performance is difficult because of the different ways that application 

software loads down the CPU. This is mainly due to the lower priority of Visual Components runtime modules. 

If a system does not have much idle time available, then display speed and key reaction are slower on the target 

system. Therefore, attention should be paid to how much idle time is available on the system. An 'unfavorable' 

configuration example will show how this works in practice. 

We will use the following configuration: 


432 4.12.7.4 Code in ANSI C


Task class 4 is an 'idle time class' from the point of view of the cyclic 

Automation Studio program. Idle time would be important here in a project 

which contains visualization componenets. 

TC#4 is set to 10 ms in our example. Here, the tolerance time is very often set 

to 1000 ms or more. If TC#4 executes longer than 10 ms, then it will be 

restarted after another 10 ms at the latest. 

For example, if TC#4 executes 19 ms (10 ms grid and 1000 ms tolerance), then only 1 ms idle time remains in a 

20 ms period. 

TC#4 is then immediately restarted in the 20th ms by the set 10 ms grid. 

If the cycle time for TC#4 is increased to 30 ms and 19 ms is still the execution time, then 11 ms idle time can be 

used for the visualization application. 

A further increase to 50 ms gives 31 ms within the 50 ms cycle. 

1 ms from 20 ms = 5% for idle time 

11 ms from 30 ms = approx. 30 % for idle time 

31 ms from 50 ms = approx. 60% for idle time 

(Of course, these figures only apply if all other tasks use 0% of the CPU or something similar) 

As made evident by the example, idle time can be very much improved by using a careful approach. It is 

especially recommended to critically examine all components according to their time requirements when the 

CPU load is very high. 

In addition to cyclic programming, B&R Automation Studio provides non−cyclic programming. With this special 

variant, additional optimized results can be achieved with regard to the runtime behavior of the system. 

Non−cyclic taks can be activated with any priority and are not dependent on runtime monitoring. 

4.12.9 Tips and Tricks − Touch Pad 

It is possible in Visual Components 2.3 to create separate touch pads. 

The following files are necessary to do so: 

− a *.tpi file 

− a *.bmp file 

Note the following when creating .tpi files: 

File extension of an original .tpi file (numpad): 

 

 

 

 

− RasterCountX" Value="10" − Bitmap size divided by the grid point size 

− RasterCountY" Value="12" − Bitmap size divided by the grid point size 

− RasterSizeX" Value="20" − always half of the actual key size 

− RasterSizeY" Value="20" − always half of the actual key size 

(example above) 

Important: 

The same settings in the .tpi file are also valid for alpha pads. 

Creating a Bitmap File: 

Any current graphics program can be used to create a graphic touc pad. 

You only need to pay attention to the bitmap size and the grid point size. In addition, the bitmap 

has to be saved in 256 colors for Visual Components. 

Inserting Both Files in Automation Studio: 

Both files (*.tpi und *.bmp) have to be copied to the AS\VisualComponents\Bitmaps\Touch Pad 

directory. 

Automation Studio must then be restarted before the new pad will be available for selection. 

Please note: 

The resolution of the touch pad may not exceed the resolution of the screen. 

4.12.10 Importing / Exporting Panel Projects 

A complete panel object can be exported and then imported into a different project with the Import/Export 

functions in Automation Studio. It is important that the hardware for the panel object matches or is compatible 

with that of the new project. Otherwise, data will be lost. 

The procedure for exporting and importing complete projects is described in the following: 

4.12.10.1 Exporting Panel Objects 


434 4.12.10 Importing / Exporting Panel Projects


First, the panel object to be exported should be selected. Then 'Export' should be selected from the 'File' menu. 

Now a name can be input for the export file. By default, the name of the respective panel is suggested. 

4.12.10 Importing / Exporting Panel Projects 435

Exporting begins by clicking on the 'Export' button. In the directory, you will then see a header file (here visu.txt) 

and a new directory (here visu.export) where the complete panel project is saved. 

4.12.10.2 Importing Panel Objects 


Importing complete panel object pictures starts by selecting 'Import' from the 'File' menu in Automation Studio. 

The ?????.export directory and the ?????.txt file must be present to import the panel object. Now, the .txt file 

can be selected for importing. 

The panel object in inserted into the project with 'Import'. Next, the appropriate display still has to be inserted. 

436 4.12.10.2 Importing Panel Objects


4.12.10.2 Importing Panel Objects 437

Now, the application can use the complete panel project. 

You must be careful when importing complete panel objects when different display hardware is used for both 

projects. Only the properties of the target hardware (project) should be supported which are then adapted to the 

imported project. 

4.13 Frequently Asked Questions (FAQ) 

4.13.1 Frequently Asked Questions (FAQ) − Input Fields 

How can passwords longer than those provided with password input fields (6 characters) be entered? 

A maximum of 6 characters can be entered for passwords when password input fields are used. If this length is 

not sufficient, then a string input field can be used with the "Password" edit mode. 

4.13.2 Frequently Asked Questions (FAQ) − Scaling 

4.13.2.1 General 

Scaling in Visual Components 2.2 fulfills two tasks. On one hand, input can be limited to a value range different 

than that of the connected data type. On the other hand, values can actually be scaled linearly. 

The following description gives an overview of how scaling functions internally, which features are included, and 

how internal performance is affected with different configurations. 

This document should be considered as a reference for developers and as a helpful aid to configuration for 

users. We have tried to describe all types of configurations and to supply the background necessary to 

understand VC 2.2 Runtime. 

Scaling can be illustrated with Step 9 in the demo project. 

4.13.2.2 Mathematics Reference 

Scaling in VC 2.2 basically functions the same as a linear function with the equation 

Linear Equation: 

y = k * x + d 

Straight Line Slope: 

k=dy/dx 

Shifting to the Y axis is calculated as follows: 

d=Yp −(xp*dy/dx) 

y ... Function value à scaled value 

x ... Output value à value to be scaled 

k ... Slope 

d ... Shift to the Y axis 


438 4.13 Frequently Asked Questions (FAQ)


Since VC 2.2 Runtime supports m68k targets in addition to i386 targets, the imprecise floating decimal data type 

"double" should be avoided when calculating scaling internally. Calculation takes place with int32 data types 

instead. 

To prevent problems with value overflows, actual calculations are processed with the aid of Assembler routines 

which allow 64−bit operations. 

When scaling in VC 2.2, the slope 'k' from the linear function is made up of the PLC−Min, PLC−Max, 

Display−Min, and Display−Max parameters. These configurable values (fixed or dynamic using PVs) result in 

the slope 'k' whereby either x or y is represented depending on the scaling direction. 

k = (ymax ymin) / (xmax xmin) 

d=ymin−(xmin *k) 

This results in the following scaling formula, whose scope is general: 

y = (ymax ymin) / (xmax xmin) * x + (ymin −(xmin*(ymax ymin) / (xmax xmin))) 

Example: 

Following configuration: 

PLCmin=2 

PLCmax=4 

SCALmin=−10 

SCALmax=100 

Needed: Displayed value when PLCValue=3 

k=(100−(−10)/4−2)) 

k=55 

d=−10−(2*55) 

d=−120 

Y=55*3 −120 

Y=45 

The parameters defined above in detail: 

Parameter Description 

PLC Min Permitted lower limit of the values of a PV on the target 

PLC Max Permitted upper limit of the values of a PV on the target 

Display Min Permitted lower limit of the displayed values of a PV on the display 

Display Max Permitted upper limit of the displayed values of a PV on the display 

4.13.2.3 Restrictions 

Using scaling, even unsigned PVs (on the target) can accept a signed value range on the display. PVs of data 

type float are normally excluded from scaling because their special properties and non−linear cardinality would 

cause unforeseen side effects for the user. The following table shows all data types which can be scaled: 

PV Data Type Display Value Range 

BOOL DINT 

USINT DINT 

SINT DINT 

UINT DINT 

INT DINT 

UDINT UDINT 

DINT DINT 

4.13.2.3 Restrictions 439

The following describes how VC 2.2 Runtime performs with scaling and the possibilities available to the user. In 

addition, how user settings are processed internally is shown to give the user and developer a better idea of this. 

4.13.2.4 Internal Performance 

Without having to go too much into detail, two principle VC 2.2 Runtime procedures are described: 

− Scaling Output 

− Scaling Input 

For the most part, code excerpts have been avoided when describing internal processes. Instead, we will try to 

explain things using graphics and text alone. 

4.13.2.5 Decimal Places 

A potentially configured decimal place exerts an exceptional influence on the display value range limits. There is 

basically one rule to keep in mind: 

The decimal place does not have any effect on the actual calculation. It only has an effect on the format 

of the output string which is formed as display output after the values are calculated. 

When decimal positions are referred to in the following, it always means the sum from fixed and dynamic 

decimal places using PVs. 

The decimal place only exerts this aforementioned influence when fixed limit values are scaled. This influence 

works in such a way that the maximum display value is greater internally by the number of "zeroes", as decimal 

places are present. An example shows this more clearly: 

Ex. a) 

Field length: 5 Decimal places: 2 Configured maximum display value: 100.33 

Internal maximum display value: 10033 

Ex. b) 

Field length: 5 Decimal places: 2 Configured maximum display value: 100 


Ex. c) 


When this configuration is attempted, the editor changes this value to 999.99. 

This is because it is necessary that the entire maximum value plus the decimal places may not exceed the 

maximum field length. From 1000 comes 1000.00 which corresponds to a field length of 6 places à can't be 

displayed. 

This problem should be taken into account when using dynamic decimal point shifts. Each increase in the 

decimal position increases the maximum display value limit by a factor of 10. In turn, this leads to an increase of 

places in the display string when entering the configured maximum value. 

Ex. a) 


Dynamic decimal point shift: 0 


Input: 100 à 100.0 (4 numeric places) à OK 


440 4.13.2.4 Internal Performance




Input: 100 à 100.00 (5 numeric places) à OK 



Input: 100 à 100,000 (6 numeric places) à cannot be displayed 

Since only PVs with non−floating decimal data types can be used when scaling with dynamic limit values, the 

decimal position does not take the same position value with this type of scaling. This means that the decimal 

position doesn't increase the maximum display limit value since otherwise it would never be possible to display 

values other than 0 behind the decimal point. The decimal is thus "just" inserted at the appropriate decimal 

position in the string. 

Ex. a) 

Field length: 5 Decimal places: 1 

Value of the maximum display value PV: 133 à Output: 13.3 


Field length: 5 Decimal places: 2 



General Rule: 

The input value * 10 number of decimal places is written to the PLC when scaling dynamically. 

The input value is written to the PLC when scaling statically. 

4.13.2.6 Scaling Output 

Basically the formula described above, 

y = (ymax ymin) / (xmax xmin) * x 

where the values are put together as follows: 

y ... + d = value which is shown on the display 

ymax ... DisplayMax 

ymin ... DisplayMin 

xmax ... PLCMax 

xmin … PLCMin 

x … value that the PV on the target holds 

Output scaling is used in 2 cases: 

a) Numerically scaled output fields 

b) Numerically scaled input fields 

In both cases, output scaling is used, as the name suggests, before the value is output on the display. The 

following sequence chain is carried out: 

4.13.2.6 Scaling Output 441

4.13.2.7 Scaling Input 

Basically the formula described above, 

y = (ymax ymin) / (xmax xmin) * x 

where the values are put together as follows: 

y ... + d = value that is written to the target PV 

ymax ... PLCMax 

ymin ... PLCMin 

xmax ... DisplayMax 

xmin … DisplayMin 

x … value that was read via display input 

Input scaling is used in one case in combination with output scaling: 

− Numerically scaled input field 

The following sequence chain is carried out: 


442 4.13.2.7 Scaling Input


4.13.3 Frequently Asked Questions (FAQ) − Keys 

Where do I clear function keys? 

Function keys on a display which has hardware keys can only be cleared in the 'Pictures' overview image. 

4.13.4 Frequently Asked Questions (FAQ) − VISAPI 

VA_Setup returns 0 and all other VISAPI functions return 7090. 

This means that the VISAPI could not be initialized because either the target was not running a project or the 

project name for the VA_Setup or VA_SetupX function was specified incorrectly. 

A task which uses the VISAPI causes cycle time violations. 

Pay attention that some drawing functions require a relatively long execution time, i.e. drawing an ellipse with 

the VA_Ellipse function. If the task is executed in a very fast task class or there is very little idle time available to 

the system, then cycle time violations can occur. 

Try to move the task with the VISAPI functions into a slower task class. If that doesn't work, try to use fewer 

drawing commands for each cycle of the task. Lastly, there is the possibility that a task in a high priority task 

class demands so much time that task classes with lower priority do not have sufficient idle time available. 

Nothing else can be drawn once a cycle is complete. 

Perhaps VA_Srelease was not called even though VA_Saccess was successfully called. If this is the case, the 

screen was reserved for output but was no longer released. 

4.13.3 Frequently Asked Questions (FAQ) − Keys 443

Check the program logic of the task so that VA_Srelease is always called after VA_Saccess has been 

successfully executed. 

Can the VA_Setup function also be executed in the INIT−SP? 

The VA_Setup function should always be called in the cyclic part of the task. It cannot be ensured that the 

interpreter has completely finished booting when INIT−SPs are called. This can cause a function error when 

VA_Setup is called (Status0). For this reason, it is recommended to execute this function in the cyclic part 

since this guarantees that the interpreter has booted. 

When I execute certain functions cyclically, my application is noticeably delayed. 

Functions such as VA_SetContrast and VA_SetBrightness for setting contrast and brightness require a relatively 

long time to execute (depending on the hardware used). If these functions are executed cyclically, then a 

bottleneck can occur with regards to the idle time. Therefore, these functions should only be called when a value 

has changed. 

When is touch calibration necessary? 

Deviations can occur regarding touch operation due to outside influences and manufacturing tolerances. The 

touch area can be recalibrated using touch calibration (VA_StartTouchCal). This function should be executed on 

a blank screen and called only once. 

4.14 Upgrading Visual Components 2.0 Projects 

4.14.1 Modification Notes 

Because of the many changes from Version 2.0, it is essential to read the upgrade notes for Version 2.1. 

Functions that may have been more difficult to implement in Version 2.0 are now substantially easier (see also 

New Functions in 2.1). 

It was also necessary to make a few changes. We hope for your understanding for these modifications. 

The following pages describe these changes and provide tips for modifying existing projects. We recommend 

that these notes be considered. In case there are problems with existing projects, refer to the appropriate notes. 

• Color Representation for IPC Projects 

• Changing Pictures 

• API Functions from the VISAPI Library 

• Keys and Key Matrix for Touch Systems 

• VCInfo Data Structure 

• Character Set Representation 

• Customer Specific Panels 

Note: 

Because of numerous functions and the possibility to integrate auxiliary programs, not all projects can be 

guaranteed an error−free conversion. Partial changes have to be made manually both in the individual editors 

and in the control application source code after opening the project with Visual Components V2.1. If there is a 

problem with converting, B&R Support can be contacted to further analyze the problem. 

4.14.1.1 Color Representation for IPC Projects 


The editor now offers the ability to directly configure colors. Projects adopted from Version 2.0 will be displayed 

using default colors. Colors which were changed during runtime with the 'VCInfo' structure are no longer shown. 

All colors must now be configured in the editor. To do so, global color settings offer suitable dialog boxes for 

setting static and dynamic colors. Additional possibilities like transparent effects and individual color 

444 4.14 Upgrading Visual Components 2.0 Projects


arrangement for particular picture elements may also be used. 

Note: 

Color values have not changed. These can be taken directly from the data structure in the global color setting. 

4.14.1.2 Changing Pictures 

Visual Components V2.1 can now manage up to 65,000 pictures in a project. In earlier projects, only 250 

pictures were possible. 

If picture numbers are used in the project for changing pictures or for evaluating the current picture number, the 

application (source) is to be modified as follows: 

• Variable data types for changing pictures, as well as for the current picture number, have been changed 

from USINT (8−bit) to UINT (16−bit). Therefore, the picture number or picture change data point has to 

be changed to a UINT data type. 

• 255 is no longer written to the variable to confirm a picture change. Instead, the variable takes the value 

65535. In the application source code, the query for a successful picture change must now correspond 

to 65535 and not 255. 

Picture change variables which are not of type INT or UINT produce a compiler error. 

VISU:(0):Error Variable for picture change from PLC "picture_number" must have data type of INT or 

UINT 

4.14.1.3 API Functions from the VISAPI Library 

The VISAPI library introduced in version 2.0 has been substantially expanded (see also VISAPI Documentation). 

Because of the ability to manage several projects on the target system, it became necessary to introduce an 

additional parameter. This additional parameter specifies the target project (handle). 

Furthermore, a few term names have changed. 

It is therefore necessary to revise and test all functions programmed with the VISAPI. Existing functions will not 

be changed for future upgrades. 

4.14.1.4 Keys and Key Matrix for Touch Systems 

Keys 

In version 2.0, touch−based panel support was only available using a fixed grid of touch keys. Touch keys were 

also only available in a fixed size. 

In the current version, buttons or HotSpots can be represented in any size, position, function, and color − with or 

without bitmaps or text. 

Existing keys on a touch system are automatically converted to HotSpots. For each touch key, a dashed 

rectangles is drawn on the display screen for the new HotSpot. The HotSpot takes over the properties of the 

key. 

These HotSpots can then be later moved and resized. 

In many cases, these HotSpots can be switched to buttons to meet the necessary appearance requirements of 

the application. In this way, the project becomes clearer (buttons instead of dynamic bitmaps and overlapping 

HotSpots) and performance is improved (see also Creating Keys on the Touch Screen). 

Key Matrix 

The key matrix for touch−operated devices was set to a fixed grid (40 pixels x 40 pixels). Variables for changing 

the key matrix received the touch position in an array of 192 bytes directly converted using the touch position. 

This computation was based on the fixed 40x40 pixel grid. 

Buttons and HotSpots status are currently transferred in the key matrix. 

It is recommended to use buttons and HotSpots instead of the touch matrix used in the project parameters. 

For this transition, one of two possibilities can be used: 

4.14.1.2 Changing Pictures 445

• HotSpot Controls for the Key Matrix 

• Calculating the Key Matrix 

These solutions should only be used for existing projects and not for creating new projects in V2.1. In future 

versions, button and HotSpot functionality will be expanded even more. Projects will be more concise and 

require less executable code. 

4.14.1.5 VCInfo Data Structure 

The 'VCInfo[0]' data structure was deleted and not replaced. 

• Controlling Colors now takes place directly by the editor or by variables on the target system. 

• The API Interface provides functions for adjusting settings for brightness and contrast, etc. 

• The Touch Calibration function is also available using the API interface. 

This change corresponds to the Automation Studio concept. 

4.14.1.6 Character Set Representation 

Bitmap font technology and their editing possibilities are being replaced by the new True Type font standard. 

The new version allows the integration of True Type fonts. Symbol fonts are also supported. The possibility to 

use UNICODE character sets (IPC target systems) is planned for the next version. 

Existing projects with modified bitmap fonts are correctly transferred. Display errors may occur when there are 

more than 127 characters in a particular set. The CharBox can be used for these instances. 

These representation problems can occur particularly on CAN systems. Standardized character sets were not 

used on them in the past. They are now not always displayed correctly in the editor partly because of reserved 

character ranges in Windows. 

Workaround: CharBox. 

4.14.1.7 Customer−Specific Panels 

When using customer−specific panels, don't forget to reinstall the hardware description files after installing 

version 2.1 (in case the directory is deleted or another directory is used). 

Only B&R standard panels are included in Automation Studio 2.1 delivery. 

4.14.2 Upgrading Visual Components 2.0 Projects 

4.14.2.1 HotSpot Controls for the Key Matrix 


HotSpots can be defined next to one another in the global picture with a size of 40x40 pixels. These HotSpots 

can then be assigned to a fixed grid position in the key matrix. In this way, 192 rectangles can be drawn in the 

global picture when a VGA display is used. Also in this way, the familiar key matrix from V2.0 can be 

implemented. 

446 4.14.1.5 VCInfo Data Structure


The fixed position of the HotSpot in the key grid is assigned in the dialog box. This allows the old key matrix to 

be reestablished. 

This method is somewhat elaborate and is only meant as a transition. 

In the long term, the project should be changed to use button and HotSpot technology. 

4.14.2.2 Calculating the Key Matrix 

Another possibility exists to convert old matrix information by reading the matrix position using the VISAPI. The 

VA_GetTouchAction() function from the VISAPI Library 

The following is an excerpt of code for converting the key matrix for a VGA display. This only applies for a VGA 

display. For 1/4 VGA, calculation takes place using lines and columns. 

#include 

#include #include "visapi.h" #define T_SIZE 192 /* VGA 40x40 pixel array 

from 640x480*/ UINT _LOCAL ready; TouchAction _GLOBAL touch; UDINT _GLOBAL x_position; UDINT 

_GLOBAL y_position; USINT _GLOBAL touch_status; _GLOBAL unsigned char KeyMatrix[T_SIZE]; _GLOBAL 

unsigned long VC_HANDLE; _CYCLIC void Cyclic(void) { int lines; int columns; int offset; if (!ready) { 

VC_HANDLE = VA_Setup(1 , "display"); /* VC project name */ if (VC_HANDLE) ready = 1; } if (ready) { 

if (!VA_Saccess(1,VC_HANDLE)) { VA_GetTouchAction (1,VC_HANDLE,&touch); VA_Srelease(1,VC_HANDLE); 

x_position = touch.x + 1; y_position = touch.y + 1; touch_status = touch.status; if(touch_status == 

2) /* Nothing pressed */ memset(KeyMatrix,0,T_SIZE); else { /* Columns */ columns = (x_position / 

40); /* Lines */ lines = (y_position / 40); offset = (columns + (lines*16)); /* Since 16 columns per 

line (640/40)*/ if(offset < T_SIZE) KeyMatrix[offset] = 1; /* Current touch field */ else 

memset(KeyMatrix,0,T_SIZE); /* Error */ } } } } 

Tip: 

This new VISAPI function permits an exact pixel evaluation of the pressed coordinates. 

4.14.2.2 Calculating the Key Matrix 447


448 4.14.2.2 Calculating the Key Matrix

2 Visual Components Manuals

Create successful ePaper yourself

Delete template?

Save as template?