Magelis XBT GT, XBT GK HMI Controller EIO0000000638 04/2012 Magelis XBT GT, XBT GK HMI Controller Programming Guide EIO0000000638.04 04/2012 www.schneider-electric.
The information provided in this documentation contains general descriptions and/or technical characteristics of the performance of the products contained herein. This documentation is not intended as a substitute for and is not to be used for determining suitability or reliability of these products for specific user applications.
Table of Contents Safety Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 1 Starting with a New Project . . . . . . . . . . . . . . . . . . . . . . . 1.1 New Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a new Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Devices Tree Description . . . . . .
6.3 State Transitions and System Events . . . . . . . . . . . . . . . . . . . . . . . . . . . Controller States and Output Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . Commanding State Transitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Error Detection, Types, and Management . . . . . . . . . . . . . . . . . . . . . . . . Remanent Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Safety Information § Important Information NOTICE Read these instructions carefully, and look at the equipment to become familiar with the device before trying to install, operate, or maintain it. The following special messages may appear throughout this documentation or on the equipment to warn of potential hazards or to call attention to information that clarifies or simplifies a procedure.
PLEASE NOTE Electrical equipment should be installed, operated, serviced, and maintained only by qualified personnel. No responsibility is assumed by Schneider Electric for any consequences arising out of the use of this material. A qualified person is one who has skills and knowledge related to the construction and operation of electrical equipment and its installation, and has received safety training to recognize and avoid the hazards involved.
About the Book At a Glance Document Scope The purpose of this document is to: z show you how to program and operate your XBT GT/GK HMI Controller, z help you to understand how to program your XBT GT/GK HMI Controller functions, z help you to become familiar with the XBT GT/GK HMI Controller functions.
Magelis XBT Gx HMI Controller System Functions and Variables EIO0000000626 (ENG); XBT PLCSystem Library Guide EIO0000000627 (FRE); EIO0000000628 (GER); EIO0000000629 (SPA); EIO0000000630 (ITA); EIO0000000631 (CHS) SoMachine Modbus and ASCII Read/Write Functions PLCCommunication Library Guide EIO0000000361 (ENG); EIO0000000742 (FRE); EIO0000000743 (GER); EIO0000000744 (SPA); EIO0000000745 (ITA); EIO0000000746 (CHS) You can download these technical publications and other technical information from our websi
WARNING UNINTENDED EQUIPMENT OPERATION z z Only use software approved by Schneider Electric for use with this equipment. Update your application program every time you change the physical hardware configuration. Failure to follow these instructions can result in death, serious injury, or equipment damage. User Comments We welcome your comments about this document. You can reach us by e-mail at techcomm@schneider-electric.com.
EIO0000000638 04/2012
Magelis XBT GT, XBT GK HMI Controller New Project EIO0000000638 04/2012 Starting with a New Project 1 Introduction This chapter describes how to create a project with the XBT GT/GK HMI Controller and how to add devices. What’s in this Chapter? This chapter contains the following sections: Section EIO0000000638 04/2012 Topic Page 1.1 New Project 12 1.
New Project 1.1 New Project Introduction This section will guide you through creating a new XBT GT/GK HMI Controller project.
New Project Creating a new Project Introduction This section describes the general characteristics of the XBT GT/GK HMI Controller and how to create a new SoMachine project. Refer to Manage your project (see SoMachine, Programming Guide) for additional information on the project management.
New Project Controller Display Type Ethernet Interface Serial Interface USB Interface CF Card Interface XBT GK 2330 QVGA/TFT Color Yes Yes (1) Yes Yes XBT GK 5330 VGA/TFT Color Yes (1) Yes Yes Yes Legend 1 RS232/RS422/RS485 serial interface. SUB-D 9-pin connector NOTE: Refer to the Controller specifications (see Magelis XBT GT, XBT GK, XBT GH, Hardware Guide) for addtional information.
New Project Devices Tree Description Introduction The Devices tree shows the hardware objects such as the controller, field bus nodes, and I/O module, and also shows resources that are needed to run your application, such as tasks, POUs, and global variable lists. Refer to CoDeSys Online help for more information on the Devices Tree.
New Project Devices Tree Description The following table describes the items in the Devices tree: Item 16 Description HMI Application Used to configure the HMI part of your project PLC Logic Shows elements of your application: z GVL: Global Variables List z Library Manager: Application Library Manager z Task Configuration: MAST and other task configuration information COM1 / COM2 Embedded communication functions for Serial Line (see page 81) communication.
New Project 1.2 Adding Devices to the Project Introduction This section shows you how to add devices to your project.
New Project Adding an XBT GT/GK HMI Controller Introduction The following paragraphs explain how to add the XBT GT/GK HMI Controller to a SoMachine project. Adding the XBT GT/GK HMI Controller to the Project Tree Add the XBT GT/GK HMI Controller (available in the Devices window) to the project tree, using the default settings that are specific to each device. To set the parameters of the controller to your individual requirements, configure the devices via the Devices window.
New Project Step Action 2 In the Add Devices window, select the XBT GT device, as shown in the figure below. Note: To sort the devices by type in the Add Device window, select Schneider Electric in the Vendor list box. 3 Select the controller you want to add to your configuration.
New Project Step Action 4 Rename your device by typing a name in the Name field. Note: z Do not use spaces or special characters (%, #). z The length of the name cannot exceed 32 characters. 5 Click Add Device to add the device to your project. Result: The Add Device window re-opens. 6 To add another controller, repeat step 3 above. Otherwise, close the Add Device window.
New Project Adding a CANopen Expansion Module Introduction You can add one of the following CANopen expansion module with the XBT GT/GK HMI Controller: z XBT ZGCANM for standard application z XBT ZGCANMS0 for Solution Architecture application The CANbus node is automatically created. You can then add and configure further CANopen devices to the manager. Adding a CANopen expansion is explained in CANopen Interface Configuration (see page 74).
New Project 22 EIO0000000638 04/2012
Magelis XBT GT, XBT GK HMI Controller Libraries EIO0000000638 04/2012 Libraries 2 Libraries Introduction The libraries of the controller provide functions such as function blocks, data types and global variables that can be used to develop your project. The default extension for a library is “.library”. The Library Manager of SoMachine provides information about the libraries included in your project. You can also use the Library Manager to install new libraries.
Libraries 24 EIO0000000638 04/2012
Magelis XBT GT, XBT GK HMI Controller Variables EIO0000000638 04/2012 Supported Standard Data Types 3 Introduction This chapter provides the supported variables and explains how to exchange data between SoMachine (controller part) and Vijeo-Designer (HMI part).
Variables Supported Variables Supported Variables Types The following table provides the XBT GT/GK HMI Controller supported variables types: Controller Data type Lower limit Upper limit Information content Bidirectional Variable (SoMachine/VijeoDesigner) BOOL False True 1 Bit Yes DINT -2,147,483,648 2,147,483,647 32 Bit Yes INT -32,768 32,767 16 Bit Yes UINT 0 65,535 16 Bit Yes WORD 0 (hex) FFFF (hex) 16 Bit Yes UDINT 0 4,294,967,295 32 Bit Yes DWORD 0 (hex) FFFFFFFF (h
Variables Variables Exchange Introduction You can exchange variables with the XBT GT/GK HMI Controller range between SoMachine and Vijeo-Designer by publishing them. Controller and HMI Data Exchange For variable exchange between the controller and HMI parts, perform the following steps: z Create variables in the controller part. z Publish the variables by defining them as Symbols in the controller part. They are now available in the HMI part as SoMachine variables.
Variables 28 EIO0000000638 04/2012
Magelis XBT GT, XBT GK HMI Controller Memory EIO0000000638 04/2012 Controller Memory Mapping 4 Introduction This chapter provides the maximum size of an application for a XBT GT/GK HMI Controller, the size of the RAM , the located variables area and the libraries.
Memory Memory Mapping Introduction This section provides the RAM (Random Access Memory) size for each area of the XBT GT/GK HMI Controller. XBT GT/GK HMI Controller Memory This figure shows different types of areas and their corresponding size for the XBT GT/GK HMI Controller memory: Legend: 30 (1) 1024 Kbytes must be shared among application, symbol area, CANopen, without any limit inside these 1024 Kbytes. (2) The symbols area size is not checked at build time.
Memory Memory of the Supported Applications The following table lists the memory capacity of supported applications: Types of application or variables: Memory Capacity: User Application 1 Mbyte Retain variables 16 360 bytes (total of 16384 bytes where 24 bytes are reserved) Persistent variables(1) 488 bytes (total of 512 bytes where 24 bytes are reserved) (1) Legend: (1) EIO0000000638 04/2012 Refer to the CoDeSys Online-Help for additional information on variables 31
Memory Controllers and HMI Address Mapping Differences Introduction This following paragraphs provide instructions for double words and bits addressing between controller and the XBT GT/GK HMI Controller. If you do not program your application to recognize the differences in address mapping between the controller and HMI parts, the controller and the HMI will not communicate correctly and it will be possible for incorrect values to be written to memory areas responsible for output operations.
Memory Examples The following gives examples of memory match for the double words: z %MD2 memory area of the XBT GT/GK HMI Controller corresponds to %MD1 memory area of the controller. z %MD20 memory area of the XBT GT/GK HMI Controller corresponds to %MD10 memory area of the controller. The following gives examples of memory match for the bits: z %MW0:X9 memory area of the XBT GT/GK HMI Controller corresponds to %M1.
Memory 34 EIO0000000638 04/2012
Magelis XBT GT, XBT GK HMI Controller Tasks EIO0000000638 04/2012 Tasks 5 Introduction The Task Configuration node in the SoMachine device tree allows you to define one or several tasks to control the execution of your application program. The task types available are: z Cyclic z Freewheeling z Event This chapter begins with an explanation of these task types and provides information regarding the maximum number of tasks, the default task configuration, and task prioritization.
Tasks Maximum Number of Tasks Maximum Number of Tasks The maximum number of tasks you can define for the XBT GT/GK HMI Controller are: z Total number of tasks = 3 z Cyclic tasks = 3 z Freewheeling tasks = 1 z Event tasks = 2 36 EIO0000000638 04/2012
Tasks Task Configuration Screen Screen Description The following screen allows you to configure the tasks. Double click on the task that you want to configure in the device tree of the Devices window to access this screen. Each configuration task has its own parameters which are independent of the other tasks.
Tasks The following table describes the fields of the Task Configuration screen: Field Name Definition Priority You can configure the priority of each task with a number between 0 and 31 (0 is the highest priority, 31 is the lowest). Only one task at a time can be running. The priority determines when the task will run: z a higher priority task will preempt a lower priority task z tasks with same priority will run in turn (2 ms time-slice) NOTE: Do not assign tasks with the same priority.
Tasks XBT GT/GK HMI Controller Cycle Time Management The XBT GT/GK HMI Controller cycle time management is set with the following configuration: z 50% for the control z 50% for the HMI application You should use a cycle time superior or equal to 20 ms.The period for the entire cycle must be a multiple of 4 ms (20, 24, 28, 32, 36 ms, etc.). NOTE: For XBTGC1100, 2120, and 2230 Embedded I/Os: z There can be up to 4 ms latency between when an input gets a signal and when the controller gets this data.
Tasks Task Types Introduction The following section describes the various task types available for your program, along with a description of the task type characteristics. Cyclic Task A Cyclic task is assigned at a fixed cycle time using the Interval setting in the Type section of Configuration sub-tab for that task. Each Cyclic task type executes as follows: 1. Read Inputs: The input states are written to the %I input memory variable and other system operations are executed. 2.
Tasks Freewheeling Task A Freewheeling task does not have a fixed duration. Each Freewheeling task type executes as follows: 1. Read Inputs: The input states are written to the %I input memory variable and other system operations are executed. 2. Task Processing: The user code (POU, etc.) defined in the task is processed. The %Q output memory variable is updated according to your application program instructions but not written to the physical outputs during this operation. 3.
Tasks System and Task Watchdogs Introduction Two types of watchdog functionality are implemented for the XBT GT/GK HMI Controller. These are: z z System Watchdogs: These watchdogs are defined in and managed by the controller OS (firmware). These are not configurable by the user. Task Watchdogs: Optional watchdogs that can be defined for each task. These are managed by your application program and are configurable in SoMachine.
Tasks Task Priorities Introduction You can configure the priority of each task between 0 and 31 (0 is the highest priority, 31 is the lowest). Each task must have a unique priority. WARNING UNINTENDED EQUIPMENT OPERATION Do not assign the same priority to different tasks. Failure to follow these instructions can result in death, serious injury, or equipment damage. Task Priority Recommendations z z EIO0000000638 04/2012 Priority 0 to 24: Controller tasks.
Tasks Task Preemption Due to Task Priorities When a task cycle starts, it can interrupt any task with lower priority (task preemption). The interrupted task will resume when the higher priority task cycle is finished. NOTE: If the same input is used in different tasks the input image may change during the task cycle of the lower priority task. To improve the likelihood of proper output behavior during multitasking, an error is detected if outputs in the same byte are used in different tasks.
Tasks WARNING UNINTENDED EQUIPMENT OPERATION Map your inputs so that tasks do not alter the input images in an unexpected manner. Failure to follow these instructions can result in death, serious injury, or equipment damage.
Tasks Default Task Configuration Default Task Configuration For the XBT GT/GK HMI Controller: The MAST task can be configured in Freewheeling or Cyclic mode. The MAST task is automatically created by default in Cyclic mode. Its preset priority is medium (15), its preset interval is 20 ms, and its task watchdog service is activated with a time of 100 ms and a sensitivity of 1. Refer to Task Priorities (see page 43) for more information on priority settings.
Magelis XBT GT, XBT GK HMI Controller Controller States and Behaviors EIO0000000638 04/2012 Controller States and Behaviors 6 Introduction This chapter provides you with information on controller states, state transitions, and behaviors in response to system events. It begins with a detailed controller state diagram and a description of each state. It then defines the relationship of output states to controller states before explaining the commands and events that result in state transitions.
Controller States and Behaviors 6.
Controller States and Behaviors Legend: z Controller states are indicated in ALL-CAPS BOLD z User and application commands are indicated in Bold z System events are indicated in Italics z Decisions, decision results and general information are indicated in normal text (1) For details on STOPPED to RUNNING state transition, refer to Run Command (see page 59). (2) For details on RUNNING to STOPPED state transition, refer to Stop Command (see page 59).
Controller States and Behaviors Note 7 However, there are two important considerations in this regard: Online Change: An online change (partial download) initiated while the controller is in the RUNNING state returns the controller to the RUNNING state if successful.
Controller States and Behaviors Note 8 The SoMachine software platform allows many powerful options for managing task execution and output conditions while the controller is in the STOPPED or HALT states. Refer to Controller State and Output Behavior (see page 55) for further details. Note 9 To exit the HALT state it is necessary to issue one of the Reset commands (Reset Warm, Reset Cold, Reset Origin), download an application or cycle power.
Controller States and Behaviors 6.2 Controller States Description Controller States Description Introduction This section provides a detailed description of the controller states. WARNING UNINTENDED EQUIPMENT OPERATION Never assume that your controller is in a certain controller state before commanding a change of state, configuring your controller options, uploading a program, or modifying the physical configuration of the controller and its connected equipment.
Controller States and Behaviors Controller State Description RUNNING with This state is the same as the RUNNING state with the following exceptions: Breakpoint z The task-processing portion of the program does not resume until the breakpoint is cleared. See CoDeSys online help in SoMachine for details on breakpoints management. RUNNING with This state is the same as the normal RUNNING state. detection of an External Error STOPPED The controller has a valid application that is stopped.
Controller States and Behaviors The Write Outputs operation continues. The %Q output memory variable is updated to reflect either the Keep current values configuration or the Set all outputs to default configuration, adjusted for any output forcing, and then written to the physical outputs. NOTE: Commands received by Ethernet, Serial, USB, and CAN communications can continue to write to the memory variables. Changes to the %Q output memory variables are written to the physical outputs.
Controller States and Behaviors 6.3 State Transitions and System Events Overview This section begins with an explanation of the output states possible for the controller. It then presents the system commands used to transition between controller states and the system events that can also affect these states. It concludes with an explanation of the Remanent variables, and the circumstances under which different variables and data types are retained through state transitions.
Controller States and Behaviors Controller States and Output Behavior Introduction The XBT GT/GK HMI Controller defines output behavior in response to commands and system events in a way that allows for greater flexibility. An understanding of this behavior is necessary before discussing the commands and events that affect controller states. For example, typical controllers define only two options for output behavior in stop: fallback to default value or keep current value.
Controller States and Behaviors Set All Outputs to Default You can select this option by choosing Set all outputs to default in the Behaviour for outputs in Stop dropdown menu of the PLC Settings sub-tab of the Controller Editor. To access the Controller Editor, right-click on the controller in the device tree and select Edit Object. This output behavior applies in the STOPPED and HALT controller states.
Controller States and Behaviors WARNING UNINTENDED EQUIPMENT OPERATION z z z You must have a thorough understanding of how forcing will affect the outputs relative to the tasks being executed. Do not attempt to force I/O that is containted in tasks that you are not certain will be executed in a timely manner, unless your intent is for the forcing to take affect at the next execution of the task whenever that may be.
Controller States and Behaviors Commanding State Transitions Run Command Effect: Commands a transition to the RUNNING controller state. Starting Conditions: BOOTING or STOPPED state. Methods for Issuing a Run Command: SoMachine Online Menu: Select the Start command. z By an HMI command using the PLC_W. q_wPLCControl and PLC_W. q_uiOpenPLCControl system variables of the XBT PLCSystem library (see Magelis XBTGC, XBTGT, XBTGK HMI Controller, System Functions and Variables, XBT PLCSystem Library Guide).
Controller States and Behaviors z z REBOOT by Script: The file transfer script on a USB memory key can issue a REBOOT as its final command. The controller will be rebooted into the STOPPED state provided the other conditions of the boot sequence allow this to occur. Refer to Saving your Application and Firmware on a USB Memory Key (see page 93) and Reboot (see page 93) for further details. The controller is restarted into the STOPPED state automatically under certain conditions.
Controller States and Behaviors Methods for Issuing a Reset Cold Command: z SoMachine Online Menu: Select the Reset cold command. z By an internal call by the application or an HMI command using the PLC_W. q_wPLCControl and PLC_W. q_uiOpenPLCControl system variables of the XBT PLCSystem library (see Magelis XBTGC, XBTGT, XBTGK HMI Controller, System Functions and Variables, XBT PLCSystem Library Guide). Effects of the Reset Cold Command: 1. The application stops. 2. Forcing is erased. 3.
Controller States and Behaviors Reboot Effect: Commands a reboot of the controller. Starting Conditions: Any state. z ControllerLockout = 0. z Methods for Issuing the Reboot Command: z Power cycle. z REBOOT by Script: The file transfer script on a USB memory key issues a REBOOT as its final command. The controller will be rebooted into the STOPPED state provided the other conditions of the boot sequence allow this to occur.
Controller States and Behaviors 7. All fieldbus communications are stopped and restarted after the boot application is loaded successfully. 8. All I/O are reset to their initialization values and then to their user-configured default values if the controller assumes a STOPPED state after the reboot. For details on variables, refer to Remanent Variables (see page 67).
Controller States and Behaviors 8. All fieldbus communications are stopped and then any configured fieldbus of the new application is started after the download is complete. 9. All I/O are reset to their initialization values and then set to the new userconfigured default values after the download is complete. For details on variables, refer to Remanent Variables (see page 67). Effects of the FTP or USB memory key Download Command: There are no effect until the next reboot.
Controller States and Behaviors Error Detection, Types, and Management Detected Error Management The controller manages 3 types of detected errors: z external detected errors z application detected errors z system detected errors The following table describes the types of errors that may be detected: Type of Error Detected Description Resulting Controller State External Error Detected External errors are detected by the system while RUNNING or STOPPED but do not affect the ongoing controller state.
Controller States and Behaviors Type of Error Detected Description Resulting Controller State System Error Detected A system error is detected when the controller enters a condition that cannot be managed during runtime. Most such conditions result from firmware or hardware exceptions, but there are some cases when incorrect programming can result in the detection of a system error, for example, when attempting to write to memory that was reserved during runtime.
Controller States and Behaviors Remanent Variables Remanent Variables Remanent variables can retain their values in the event of power outages, reboots, resets, and application program downloads. There are multiple types of remanent variables, declared individually as "retain" or "persistent", or in combination as "retain-persistent". NOTE: For this controller, variables declared as persistent have the same behavior as variables declared as retain-persistent.
Controller States and Behaviors 68 EIO0000000638 04/2012
Magelis XBT GT, XBT GK HMI Controller Controller Configuration EIO0000000638 04/2012 Controller Configuration 7 Device Editor Introduction Configure and monitor your XBT GT/GK HMI Controller using the Device Editor. The following screen-shot shows the Information tab of the Device Editor window: For more detailed information refer to the CoDeSys Online-Help.
Controller Configuration Tabs Description The following table provides a description of the tabs available from the Device Editor window: Tab Description Communication Settings Allows configuring the connection between the programming system and the controller (not available for expansion modules). Applications Shows the applications currently running on the controller and allows removing applications from the controller (not available for expansion modules).
Magelis XBT GT, XBT GK HMI Controller Ethernet Configuration EIO0000000638 04/2012 Ethernet Configuration 8 IP Address Configuration Introduction Setting up an Ethernet connection and IP address configuration with the HMI controllers is done using Vijeo-Designer.
Ethernet Configuration The following table briefly explains the different parameters needed for setting up an Ethernet configuration: Element Description Download Choose the project download method you want in the drop down menu list. When configuring ethernet connection, select Ethernet. The project download methods are: z Ethernet z File System z USB z SoMachine IP Address IP address of the controller.
Magelis XBT GT, XBT GK HMI Controller CANopen Configuration EIO0000000638 04/2012 CANopen Configuration 9 Introduction This chapter describes how to configure the CANopen network interface of the XBT GT/GK HMI Controller.
CANopen Configuration CANopen Interface Configuration XBT GT/GK HMI Controller Maximum Hardware Configuration Up to 10 CANopen remote devices can be connected to the CANopen Master Unit. XBT GT/GK HMI Controller Software Requirements The maximum number of Received PDO RPDO is 20. The maximum number of Transmitted PDO TPDO is 20. Adding the CANopen Expansion Modules When adding a CANopen expansion module (XBT ZGCANM or XBT ZGCANMS0) to the XBT GT/GK HMI Controller, the CANbus node is automatically created.
CANopen Configuration Step 2 Action In the Add Device window, select the CANopen expansion module (XBT ZGCANM or XBT ZGCANMS0), as shown in the figure below: Note: To sort the devices by type in the Add Device window, select Schneider Electric in the Vendor list box. 3 Rename the CANopen expansion module by typing a name in the Name field. Note: z Do not use spaces or special characters (%, #). z The length of the name cannot exceed 32 characters. 4 Click Add Device to add the device to your project.
CANopen Configuration Baudrate Configuration The following table provides the procedure for accessing the CANopen Baudrate configuration screen: Step Action 1 Double click the CANbus node in the Devices window. Result: The CANbus configuration screen appears: 2 Select the CANbus tab. 3 Configure the baudrate using the Baudrate (bits/s) menu list. By default, the value is set to 250,000 bit/s. 4 Configure the net using the Net menu list. By default, the value is set to 0.
CANopen Configuration CANopen Optimized Manager Adding the CANopen Optimized Manager Add the CANopen_Optimized Manager to your project to attach a remote device. To add the CANopen_Optimized Manager follow the steps: Step 1 Action Right-click on the CANbus node in the Devices window and choose Add Device....
CANopen Configuration CANopen Remote Devices Adding a Remote Device to the CANopen_Optimized manager To add a remote device to the CANopen_Optimized manager, follow the steps in the table below: Step 78 Action 1 Right click on the CANopen_Optimized manager node and choose Add Device.
CANopen Configuration Step Action 3 Select the remote device you want to add. 4 Rename your device by typing a name in the Name field. Note: z Do not use spaces or special characters (%, #). z The name length cannot exceed 32 characters. 5 Click Add Device to add the device to your project. Result: The Device window is refreshed with the new remote devices associated to the CANopen_Manager. The Add Device window opens again.
CANopen Configuration 80 EIO0000000638 04/2012
Magelis XBT GT, XBT GK HMI Controller Serial Line Configuration EIO0000000638 04/2012 Serial Line Configuration 10 Introduction This chapter describes how to configure the serial line communication of the XBT GT/GK HMI Controller.
Serial Line Configuration Serial Line Configuration Introduction The serial line configuration window allows configuration of the serial line parameters (baud rate, parity, etc.). You can configure up to two serial ports with the XBT GT/GK HMI Controller.
Serial Line Configuration The following table provides the description of each parameter: Parameter Initial Values Range Description Baud rate 115.2 Kbauds 1.2...115.
Serial Line Configuration SoMachine Network Manager Adding a SoMachine Network Manager To add a SoMachine Network Manager proceed as explained in the following procedure: Step Action 1 Right click COM1 from the Devices window 2 Choose Add Object..., Result:The following figure appears: 3 Choose the SoMachine Network Manager object and click Open Result: The SoMachine Network Manager is added in the project structure from the Devices window.
Serial Line Configuration SoMachine Network Manager Configuration Window Double click SoMachine Network Manager in the device tree to access the COM1 Configuration tab: The following table provides the SoMachine-Network_Manager parameters description: EIO0000000638 04/2012 Parameter Initial Value Range Description Inter-frame delay 3 0...65,535 Delay between frames Address 1 0...
Serial Line Configuration Modbus Manager Adding a Modbus Network Manager To add a Modbus-Network_Manager proceed as explained in the following procedure: Step Action 1 Right click COM1 from the Devices window 2 Choose Add Object..., Result:The following figure appears: 3 Choose the Modbus-Network_Manager object and click Open Result: The Modbus-Network_Manager is added in the project structure from the Devices window.
Serial Line Configuration Modbus Manager Configuration Window Double click Modbus_Manager in the device tree to access the Modbus manager Configuration tab: The following table provides the Modbus parameters description: Element Description Modbus Parameters: Addressing Specify the device type: z Master z Slave Address [1...247] Modbus address of the device. Time between Frames (ms) Time required to avoid bus-collision. This parameter must be identical for each Modbus device on the link.
Serial Line Configuration 88 EIO0000000638 04/2012
Magelis XBT GT, XBT GK HMI Controller Managing Online Applications EIO0000000638 04/2012 Managing Online Applications 11 Connecting the Controller to a PC Application Transfer To transfer and run applications, connect your XBT GT/GK HMI Controller to a PC that has SoMachine installed. To transfer an application with an XBT GT/GK HMI Controller, use Ethernet, serial link, USB cables, USB memory key or CF card. NOTICE Possible electrical damage to controller components.
Managing Online Applications USB Cables Requirements To connect the controller to your PC, specific USB cables are required as shown in the following table: Product Name Reference Description USB Transfer Cable XBT ZG 935 Download project data created with the window Editor via the USB interface from the XBT GT/GK HMI Controller unit. USB Front Cable XBT ZGUSB Extension cable attaching USB port to front panel. USB Front Cable XBT ZGUSBB Extension cable attaching USB port to front panel.
Managing Online Applications The following diagram shows how to connect the XBT GT/GK HMI Controller directly to a PC: 2 1 Legend: 1: USB data transfer cable (XBT ZG 935) 2: USB connection on the XBT GT/GK HMI Controller; refer to the XBT GT/GK HMI Controller User Manual (see Magelis XBTGC HMI Controller, Hardware Guide) for more information on the USB holder EIO0000000638 04/2012 91
Managing Online Applications The following diagram shows how to connect the XBT GT/GK HMI Controller to a PC, when mounted on a front panel: 2 1 Legend: 1: USB data transfer cable (XBT ZGUSBB). 2: USB Min B to USB data transfer cable (TCS XCNA MUM3P or XBT ZG 935). NOTE: An alternative download method consist of connecting your PC to any controllers via USB cable, then connect your XBT GT/GK HMI Controller to the first one via serial link. However transfer speed is slow.
Managing Online Applications Application Download with Firmware Change The XBT GT/GK HMI Controller can download an application and change (either upgrade or downgrade) the firmware from a USB memory key. You must first save the application and the appropriate firmware version on a USB memory key. NOTICE Loss of Data Always save your application and firmware version on a USB memory key. Failure to follow these instructions can result in equipment damage.
Managing Online Applications Step Action 4 Select File System from the Download menu as shown in the following figure: 5 Set the directory from the Path menu to the USB memory key. NOTE: Select the root level of your USB memory key. 6 Click the OK button. Result: The directory is now set to the USB memory key. 7 Click Build → Download All from the Vijeo Designer main menu bar. Result: The application is saved onto the USB memory key.
Magelis XBT GT, XBT GK HMI Controller Troubleshooting and FAQ EIO0000000638 04/2012 Troubleshooting and FAQ 12 Introduction This chapter contains common troubleshooting procedures and frequently asked questions for the XBT GT/GK HMI Controller.
Troubleshooting and FAQ Troubleshooting Introduction This section lists the possible troubleshooting solutions with the XBT GT/GK HMI Controller, and procedures for troubleshooting them. Transferring the Application is not Possible Possible causes: PC cannot communicate with the controller. z SoMachine not configured for the current connection.
Troubleshooting and FAQ Resolution: Follow the flowchart below for troubleshooting purposes and then refer to the next table: Check Action 1 Check that: z The cable is correctly linked to the controller and to the PC, and is not damaged, z You used the specific cable or adapter, depending on the connection type: z Ethernet and Serial link connection. z XBT ZG 935 cable for a USB connection.
Troubleshooting and FAQ Check Action 2 Check that the XBT GT/GK HMI Controller has been detected by your PC: 1. Click Start → Control Panel → System, then select the Hardware tab and click Device Manager, 2. Check that the XBT GT/GK HMI Controller node appears in the list, as shown below: 3. If the XBT GT/GK HMI Controller node does not appear, or if there is an node, disconnect and reconnect the cable on the controller side. 3 icon in front of the Check that the active path is correct: 1.
Troubleshooting and FAQ Creating the Boot Application is not Possible Possible cause: Operation not possible while the controller is in RUN state. Resolution: z Select Stop Application. z Select Create Boot Project. Changing Device Name does not work Possible cause: Application is running. Resolution: Select Stop Application, z Change device name. z CANopen Heartbeat is not sent on a regular basis Possible cause: Heartbeat value is not correct.
Troubleshooting and FAQ Frequently Asked Questions How can I Determine the Firmware, Boot and Chip Version of the Controller? In online mode, double click the controller node in the device view. In the controller window, select the Service tab.
Troubleshooting and FAQ When should I use Freewheeling or Cyclic Mode? z z Freewheeling: use this mode if you accept a variable cycle time. The next cycle starts after a waiting duration that equals 30% of the last cycle execution time. Cyclic: use this mode if you want to control the frequency cycle.
Troubleshooting and FAQ To update the controller name you can: z Update manually (see page 102) the controller name in the HMI application to be consistent with the controller name used in SoMachine, or, z Update manually (see page 105) the controller name in SoMachine to be consistent with the controller name used in the HMI application (Vijeo-Designer), or, z Create a generic application (see page 107) that can be easily used without modifying the HMI application.
Troubleshooting and FAQ Step EIO0000000638 04/2012 Action 4 Click Edit...
Troubleshooting and FAQ Paste the controller device name into Vijeo-Designer Network Equipment Configuration window, as explained in the procedure below: Step 104 Action 1 Double click IO Manager → SoMachineNetwork → Your controller from the Vijeo-Designer Navigator Result: The Network Equipment Configuration window opens 2 Paste the controller device name in PLC Configuration → Equipment Address field 3 Click the OK button 4 Double click IO Manager → SoMachineNetwork → Your HMI from the VijeoDes
Troubleshooting and FAQ How do I manually update the Modicon M238 Logic Controller name in my SoMachine application using Vijeo-Designer? Paste the controller device name from Vijeo-Designer as explained in the procedure below: Step EIO0000000638 04/2012 Action 1 Double click IO Manager → SoMachineNetwork → Your controller from the Vijeo-Designer Navigator Result: The Network Equipment Configuration window opens 2 Copy the controller device name in PLC Configuration → Equipment Address field 3 Clic
Troubleshooting and FAQ Copy the controller device name into the SoMachine Device Editor as explained in the procedure below: Step 106 Action 1 Double click on the controller node from the SoMachine Devices window Result: The Device Editor window opens 2 Select the Communication Settings tab 3 Select your controller available in the gateway, as shown in the next figure EIO0000000638 04/2012
Troubleshooting and FAQ Step Action 4 Click Edit..., the Device window opens: 5 Paste the controller name available in the Address → Device Name field 6 Click the OK button Result: Your controller device name is now updated How do I create a generic application ? The following procedure shows the main steps for creating and using generic application.
Troubleshooting and FAQ Create a Project Archive File Create a project archive file by selecting File → Project Archive → Save/Send Archive from the SoMachine menu. Save the Controller Device Name Follow the procedure below to save the controller device name (LateConf.
Troubleshooting and FAQ Copy the Controller Device Name Follow the procedure below to copy the controller device name (LateConf.bin): Step Action 1 Double click on the controller node from the SoMachine window Result: The Device Editor window opens 2 Check that the controller is set as the Active Path from the Communication Settings tab 3 Locate the LateConf.bin file in the Host browser from the Filetab 4 Select the LateConf.
Troubleshooting and FAQ 110 EIO0000000638 04/2012
Magelis XBT GT, XBT GK HMI Controller Glossary EIO0000000638 04/2012 Glossary 0-9 %I According to the IEC standard, %I represents an input bit (for example a language object of type digital IN). %IW According to the IEC standard, %IW represents an input word register (for example a language object of type analog IN). %Q According to the IEC standard, %Q represents an output bit (for example a language object of type digital OUT).
Glossary A ASCII The american standard code for information interchange is a communication protocol for representing alphanumeric characters (letters, numbers, and certain graphic and control characters). B BCD The binary coded decimal format represents decimal numbers between 0 and 9 with a set of 4 bits (a nybble/nibble, also titled as Halfbyte). In this format, the 4 bits used to encode decimal numbers have an unused range of combinations.
Glossary BYTE When 8 bits are grouped together, they are called a BYTE. You can enter a BYTE either in binary mode or in base 8. The BYTE type is encoded in an 8-bit format that ranges from 16#00 to 16#FF (in hexadecimal format). C CANopen CANopen is an open industry-standard communication protocol and device profile specification. CFC The continuous function chart (an extension of the IEC61131-3 standard) is a graphical programming language that works like a flowchart.
Glossary DINT A double integer type is encoded in a 32-bit format. DNS The domain name system is the naming system for computers and devices connected to a LAN or the Internet. DWORD A double word type is encoded in a 32-bit format. E expansion bus The expansion bus is an electronic communication bus between expansion modules and a CPU. expansion I/O module An expansion input or output module is either a digital or analog module that adds additional I/O to the base controller.
Glossary G GVL The global variable list manages global variables that are available in every application POU. H HMI A human-machine interface is an operator interface (usually graphical) for industrial equipment. HSC high-speed counter I IEC 61131-3 The IEC 61131-3 is an international electrotechnical commission standard for industrial automation equipment (like controllers).
Glossary IL A program written in the instruction list language is composed of a series of instructions executed sequentially by the controller. Each instruction includes a line number, an instruction code, and an operand. (IL is IEC 61131-3 compliant.) INT A single integer is encoded in 16 bits. L latching input A latching input module interfaces with devices that transmit messages in short pulses. Incoming pulses are captured and recorded for later examination by the application.
Glossary master/slave The single direction of control in a network that implements the master/slave model is always from a master device or process to one or more slave devices. Modbus The Modbus communication protocol allows communications between many devices connected to the same network. N network A network includes interconnected devices that share a common data path and protocol for communications.
Glossary protocol A protocol is a convention or standard that controls or enables the connection, communication, and data transfer between two computing endpoints. PTO Pulse train outputs are used to control for instance stepper motors in open loop. PWM Pulse width modulation is used for regulation processes (e.g. actuators for temperature control) where a pulse signal is modulated in its length. For these kind of signals, transistor outputs are used.
Glossary SDO A service data object message is used by the fieldbus master to access (read/write) the object directories of network nodes in CAN-based networks. SDO types include service SDOs (SSDOs) and client SDOs (CSDOs). SFC A program written in the sequential function chart language can be used for processes that can be split into steps. SFC is composed of steps with associated actions, transitions with associated logic condition, and directed links between steps and transitions.
Glossary U UDINT This abbreviation for an unsigned double integer (encoded in 32 bits). UINT An unsigned integer is encoded in 16 bits.
Magelis XBT GT, XBT GK HMI Controller Index EIO0000000638 04/2012 B AC Index A Adding CANopen Module, 21 Controller, 18 Devices, 17 Addressing Modes differences, 32 Application Save, 93 Array Data Exchange, 26 C CANopen Adding Module, 21, 21 Baudrate Configuration, 76 Expansion Modules, 78 Hardware Configuration, 74 Interface Configuration, 74 Master Unit, 74 Network Manager, 76 Optimized Manager, 77 Remote Devices, 78, 79 Remote Devices Configuration Screen, 79 Software Requirements, 74 EIO0000000638
Index Devices Adding, 17 Tree, 15, 16 Window, 15 Devices Editor Window, 69 Download Application, 93 USB, 90 Download application, 63 I E M Editor Controller Device Editor, 69 Ethernet Configuration, 71, 71 Exchange Variables, 27 Expansion Modules CANopen, 74, 78 Memory Controller, 29 Mapping, 30 Supported Application Capacity, 31 Modbus Manager, 86 F FAQ, 100 Network Communication, 100 Communication is interrupted, 101 Connecting Multiple Controller through USB Ports, 101 Controller and HMI Communica
Index Serial Link SoMachine Network Manager, 84 SoMachine Network Manager, 84 State diagram, 48 Stop command, 59 Structure Data Exchange, 26 Supported Standard Data Types Supported Variables, 25 Supported Variables Types, 26 W Window Device Window, 15 X XBT GT/GK Controller creating projects, 13 T Task Controller tasks, 35 Cyclic task, 40 Event task, 41 Freewheeling task, 41 Types, 40 Watchdogs, 42 Troubleshooting, 96 Application Transfert, 96 Boot Application, 99 CANopen Heartbeat, 99 Communication, 96
Index 124 EIO0000000638 04/2012
