MODULE 2 EC-GFX PROGRAM BASICS

MODULE 2 EC-GFX PROGRAM BASICS
2.1 – Graphical User Interface 2.2 – Programming Blocks 2.3 – Connection Rules 2.4 – Connection Types 2.5 – Build Sequencing 2.6 – Block Actions 2.7 – Saving a GFX Project

MODULE 2 EC-gfxPROGRAM BASICS
EST: 60:00 2.1 – Graphical User Interface 2.5 – Build Sequencing 2.2 – Programming Blocks 2.6 – Block Actions 2.3 – Connection Rules 2.7 – Saving a GFX Project 2.4 – Connection Types Module 2 Menu This module should take about 60 minutes. When you’ve completed this presentation on EC-gfxProgram Basics, click on the “QUIZ” button below to take a short quiz Then click the brown “NEXT MODULE” arrow below to advance to the next e-module – Module 3: Distech Controllers. Click to review Instructions >

GRAPHICAL USER INTERFACE Topic 2.1
EC-gfxProgram Module 2: EC-gfxProgram Basics Topic 1 – Graphical User Interface In this topic, you will: 1. Explore the basic menus, panes, and functions. GRAPHICAL USER INTERFACE Topic 2.1 BACK TO BASICS

Graphical User Interface
The diagram below represents the basic layout of EC-gfxProgram, from the center and rotating counter-clockwise: Programming sheet EC-gfxProgram button/ribbon Toolbar Code Library Output Error List Statistics Resource Viewer/ Favorites Search Results Watch List Status Indicators Task Viewer Project Explorer Properties Pane BACK TO BASICS

Programming Sheet (1) All device programming Grid with auto “snap”
One sheet per tab Re-sizable in Properties tab Thumbnail feature BACK TO BASICS

GFX Program Button/Ribbon (2)
The GFX Button has been replaced by the File menu. BACK TO BASICS

GFX Program Button/Ribbon (2) File Menu
Save Import Options BACK TO BASICS

GFX Program Button/Ribbon (2)
Quick Access Toolbar Ribbon Types Button Categories RIBBONS: File Home Drawing View Tools BACK TO BASICS

Ribbon (2) – Home BUTTONS: Clipboard Editing Project Debugging
BACK TO BASICS

Ribbon (2) – Drawing BUTTONS: Alignment Distribution Size
BACK TO BASICS

Ribbon (2) – View BUTTONS: Zoom Show/Hide Panes BACK TO BASICS

Ribbon (2) – Tools BUTTONS: Tools Current Platform Tools
BACK TO BASICS

Toolbox (3) and Code Library (4)
BACK TO BASICS

Panes PANES: Output Statistics Resources Viewer Search Results
Error List Watch List Task Viewer Panes BACK TO BASICS

Panes–Output (5) Shows background operations being done by EC-gfxProgram, such as the progress of a build. BACK TO BASICS

Panes–Error List (6) Indicates any errors that occur while building a project or control sequence. Assists the user to locate, troubleshoot, and debug problems. Also shows the user where exactly the problem is – when an error message is double-clicked, a tooltip points to the input, output, or object that is the source of the error on the Programming Sheet. GFX Options – allows errors to display in real time BACK TO BASICS

Panes–Error List (6) BACK TO BASICS

Panes–Statistics (7) Displays certain statistics: Code space usage
Memory usage Input/Output usage Compiling time RAM memory is used to store certain values that depend on the block used, type of connections between blocks and block layouts. BACK TO BASICS

Panes–Resource Viewer/Favorites (8)
Displays info about inputs, outputs, variables and constants in the device. BACK TO BASICS

BUTTONS: Refresh All Refresh Selected View Mode Quick Print Export Add Floating Pair BACK TO BASICS

Block Options – right-click drop-down BACK TO BASICS

Panes–Search Results (9)
Find Objects Panes–Search Results (9) BACK TO BASICS

Find All References Panes–Search Results (9) You can also activate Search Results by selecting “Find All References” from the Resource Viewer. You can also activate Search Results by selecting “Find All References” from the Resource Viewer. Right-click > BACK TO BASICS

Double-click on Reference Panes–Search Results (9) < Double-click BACK TO BASICS

Panes–Watch List (10) Shows a table of values from Monitor blocks in which a name has been assigned to the WatchVariableName in the Block Properties of the Monitor block. WatchVariableName MONITOR BLOCK WATCH LIST The Watch List shows a table of values from Monitor blocks in which a name has been assigned to the WatchVariableName in the Block Properties of the Monitor block. BACK TO BASICS

Panes–Status Indicators (11) Controller Connection / Debugging
Debugging Activity Server IP Address Path to the Controller AX Connection Status Controller’s Connection Status BACK TO BASICS

Panes–Task Viewer (12) EC-gfxProgram is able to carry out background tasks simultaneously during code creation. The Task Viewer shows the tasks waiting to be processed. EC-gfxProgram is able to carry out background tasks simultaneously during code creation. The Task Viewer shows the tasks waiting to be processed. BACK TO BASICS

Project Explorer (13) Tree-view list of all sheets, documents and blocks in a project Double-clicking a block highlights/blinks it on the programming sheet Right-click drop-down menu Tree-view list of all sheets, documents and blocks in a project Double-clicking a block highlights/blinks it on the programming sheet Right-click drop-down menu BACK TO BASICS

Properties (14) Project Properties Block Properties
Measurement System: Affects ONLY the current project. Measurement System: Affects ONLY the current project Available Block Actions (same as right-click menu) Click F4 on any block or programming sheet for properties. Click F4 on any block or programming sheet for properties. Available Block Actions (same as right-click menu) BACK TO BASICS

BACK TO BASICS MENU (CLICK HERE)

PROGRAMMING BLOCKS: An Overview Topic 2.2
EC-gfxProgram Module 2: EC-gfxProgram Basics Topic 2 – Programming Blocks: An Overview In this topic, you will: Explore the basic categories of programming blocks available in EC-gfxProgram. Review examples where some of the most common blocks are used. PROGRAMMING BLOCKS: An Overview Topic 2.2 BACK TO BASICS

Programming Blocks Programming blocks can be added to the Programming Sheet from the Code Library (as code snippets) or Toolbox. Programming blocks can be added to the Programming Sheet from the Code Library (as code snippets) or Toolbox. BACK TO BASICS

Programming Blocks–Code Snippets
Add to Code Library (right-click on a block) Right-click menu Saving a Code Snippet Retrieve from Code Library (drag and drop) Reusing a Code Snippet BACK TO BASICS

Programming Blocks–Description
BLOCK ELEMENTS: Icon Name (editable) Type and number Input (ports) Output (ports) Port connection indicator (white/red) Configuration type BACK TO BASICS

Programming Blocks–Toolbox Elements
Click each of the following Toolbox Elements below to find out more. Comparators Logic Constants & Variables Math Custom Psychrometric General Time Toolbox Elements Click each of the following Toolbox Elements below to find out more. Generics Tools HVAC VAV Inputs & Outputs BACK TO BASICS

Toolbox Elements–Comparators
Comparators evaluate 2 numeric inputs using a particular function. Output TRUE FALSE Compares Input 1 to Input and outputs a True/False BACK TO TOOLBOX

Toolbox Elements–Constants & Variables
Constants: blocks that are mostly used to configure set values (setpoints, delays, limits, etc.) that may need to be made available to an end-user graphical interface (Px) Variables: blocks that are mostly used to monitor changing values or calculate new values using old ones that may need to be made available to an end-user graphical interface (Px) Values and Constants are blocks that are used to set and monitor values. These values are either used for internal calculation only or they can be exposed to the network. The example below shows how a Supply Air Temperature Setpoint (Numeric Value block) is calculated based on the Outdoor Air Temperature (Hardware Input block) being interpolated linearly (Linear block) and limited (Limit block) by a Maximum and Minimum Supply Air Temperature (Numeric Value blocks) and a maximum and minimum outdoor air temperature (Internal Constant block). The Internal Constant blocks set the outdoor air temperature limits, which are not required to change. The Numeric Value blocks set the supply air temperature min and max values, which can be changed through an HMI over the network. The Linear block then creates a linear interpolation based on these min and max values and the Limit block sets the values received from the Numeric Value blocks as outdoor air temperature limits. The Hardware Input block sends the value of the Outdoor Air Temperature and the Supply Air Temperature Setpoint is calculated and outputted by the Limit block to the Numeric Value block where it can be monitored by an HMI over the network. BACK TO TOOLBOX

Toolbox Elements–Custom
Custom blocks are used to simplify code representation on a programming sheet by creating a block that contains code that makes up a unique sequence, function, or logic: Custom blocks are used to simplify code representation on a programming sheet by creating a block that contains code that makes up a unique sequence, function, or logic. Resetting temp setpoints Resetting damper positions Comparing temp/humidity to enable modes BACK TO TOOLBOX

Straight out of the toolbox, a custom block has no ports. You must build the internals and ports of the Custom block in one of 2 ways: From scratch Using a keyboard shortcut (CTRL+E) Straight out of the toolbox, a custom block has no ports. You must build the internals and ports of the Custom block in one of 2 ways: From scratch Using a keyboard shortcut (CTRL+E) BACK TO TOOLBOX

There are 3 types of Custom blocks: The regular Custom block is executed in sequence with other blocks in the code. The Conditional Custom block is used for advanced programming and allows for the execution of a part of the sequence when the block is enabled. The For Loop is used to simplify code by using a For Loop block that can sequentially process data. This block is usually used with Generics blocks. Click on each of the following to find out more > Regular Custom block Conditional Custom block For Loop Custom block BACK TO TOOLBOX

REGULAR CUSTOM BLOCK: The regular Custom block is executed in sequence with other blocks in the code. Regular Custom block Regular Custom block BACK TO CUSTOM

CONDITIONAL CUSTOM BLOCK: The Conditional Custom block is used for advanced programming and allows for the execution of a part of the sequence when the block is enabled. Conditional Custom block 2 Conditional Custom blocks BACK TO CUSTOM

FOR LOOP CUSTOM BLOCK: The For Loop custom block is used to simplify code by using a For Loop block that can sequentially process data – such as calculating Average, Minimum and Maximum Demand based on incoming Terminal Load from multiple VAV controllers. This block is usually used with Generics blocks. BACK TO CUSTOM

A Custom block can also be used to create blocks that don’t already exist in the standard Toolbox and can be saved in the Code Library for easy reuse. Custom blocks can also be converted into a toolbox with the Toolbox Builder. BACK TO TOOLBOX

Toolbox Elements–General
General blocks are used to perform various important control loop functions in a program to provide control and supervision of a process. Examples: Click each of the following to find out more > Hysteresis Limit / Linear PID Loop BACK TO TOOLBOX

HYSTERESIS: Used to hold the output value steady until the input value has surpassed either the high or low limits. It prevents the output from short-cycling due to small, yet frequent changes to the input. In this example, you want to avoid having the OA dampers (output) opening or closing based on small changes in Outside Air enthalpy vs. Return Air enthalpy (inputs). BACK TO GENERAL

LINEAR/LIMIT: A Linear block provides a linear proportional reset based on the equation y = mx + b (you might remember this from 9th grade algebra as the equation for the slope of a line). This is useful for applications such as supply air temperature reset in relation to the outside air temperature, or OA damper reset in relation to the fan speed. < Click to see an example of the linear reset graph.. In this example, as Duct Static Pressure decreases, Fan speed increases to maintain 1.5 in H2O pressure As fan speed increases to its max of 100%, OA Dampers will close down to its min position of 15%. BACK TO GENERAL

LINEAR/LIMIT: A Limit block is used to control the input value within a specified range. In this example, the Limit block limits the resulting OA Damper position to any value between 15% (Low limit) and 100% (High limit). BACK TO GENERAL

PID LOOP: Used to provide a proportional, integral, and derivative (PID) loop control. Each Pid Loop block is linked to a corresponding network property or variable which follows the same value as the Pid Loop block. Click above to see examples of the PID output for proportional, integral and derivative control. BACK TO GENERAL

PID LOOP (cont’d): A Live Trend Log of the response of the Pid loop’s Input, Setpoint, and Output can be used to view a graph of these variables so as to assist with PID loop tuning. While Debugging a Project, right-click the Pid Loop block and select View Trend Log. BACK TO GENERAL

Toolbox Elements–Generics
Generic blocks represent multiple instantiations of their root or base type. The generic block’s Number input selects the instance identity at any moment that the generic block is to assume. The For Loop block is ideal for use with a generic block as it cycles through a range of numbers allowing the generic block to go through each of its instantiations. Generic blocks are also useful for creating toolboxes since they allow reading and writing to resource blocks inside toolboxes, which is not possible using the standard blocks. BACK TO TOOLBOX

Toolbox Elements–HVAC
Used for standard HVAC requirements such as staging control (ON/OFF or analog) and optimum start/stop calculations. Staging Example: < Click diagram to see more detail about how this example is staged. BACK TO TOOLBOX

Toolbox Elements–Inputs/Outputs
Lonworks: Used to interface with various types of physical inputs and outputs, as well as network variable inputs (NVIs) and network variable outputs (NVOs). BACnet: Used to interface with various types of physical inputs and outputs, as well as network value inputs and outputs. Click each of the following to find out more > Hardware Inputs/Outputs Network blocks BACK TO TOOLBOX

HARDWARE INPUTS/OUTPUTS Used to interface with a physically connected hardware input/output. Each Hardware Input or Hardware Output block is linked to a corresponding network variable (Lonworks) or network value (BACnet), which follows the same value as the Hardware Input block. Example: < Click diagram to see more detail about this example . BACK TO INPUTS/OUTPUTS

NETWORK VARIABLE INPUTS/OUTPUTS Lon Example: NETWORK VALUES BACnet Example: Lonworks: Used to interface with any network variable output (NVO) that has a length up to 31 bytes or with a graphical interface (Px). BACnet: Used to read a value from (Input) or to write a value to (Output) any BACnet object available on the BACnet intranetwork, according to the block’s Input or Output mode. < Click either diagram to see more detail > about this example . BACK TO INPUTS/OUTPUTS

Toolbox Elements–Logic
Evaluates the binary values at two or more inputs according to the block’s Boolean (T/F) logic. Examples: And Or Not Switch BACK TO TOOLBOX

AND Output will only be True (1) when ALL inputs are True (1). Output will be False (0) when ANY input is False (0). Can have up to 10 Inputs. Is Occupancy NOT equal to a value of 2 (UNOCC)? Goes to Humidifier PID Loop Is humidity sensor output (SpaceHum) null? In this example – INPUT 1: if occupancy is NOT Unoccupied (value = 2) AND INPUT 2: if output from the humidity sensor (SpaceHum) is NOT null (will output a False (0)) – the Not block will invert a zero value to a True (1) … then, it will enable the Humidifier PID Loop. BACK TO LOGIC

OR Output will be True (1) when ANY input is True (1). Output will be False (0) when ALL inputs are False (0). Can have up to 10 Inputs. Is actual fan speed less than minimum allowed value (20%)? Goes to Cool & Heat PID Loops < Is either fan in a Stop Fault condition? In this example – INPUTS 1/2: if either Supply or Return Fan Speed is LESS THAN the minimum allowed (20%) OR INPUTS 3/4: if Supply or Return Fans are in a Stop Fault condition … then, it will disable both Cool & Heat PID Loops. BACK TO LOGIC

NOT Will reverse a digital value: Output will be True (1) when the input is False (0). Output will be False (0) when the input is True (1). Is humidity sensor output (SpaceHum) null? If False (0), the NOT will invert that to a True (1). If True (1), the NOT will invert that to a False (0).

SWITCH Used to select between two values based on a Boolean (0 or 1) condition: Outputs one value if it selects an On value – if Input is >/= 1 Outputs another value if it selects an Off value – if Input is < 1 OFF 2 1 ON In this example – EQUAL (HVAC Mode Convert): converts an incoming Cool HVAC mode value of 3 to a 0 value SWITCH (SAT SP): - If Input is Heat (1), then switch to ON port – pass output from Heating SAT Reset. - If Input is Cool (0), then switch to OFF port – pass output from Cooling SAT Reset

Toolbox Elements–Math
Evaluates the values at two or more inputs according to the block’s mathematical operator. Blocks most commonly used in building project code include: BLOCKS EXAMPLE USES Add Add multiple inputs to a setpoint to yield an effective setpoint Subtract Subtract a set value from another to provide a range to use as a deadband Min Provide the lowest value of all inputs Max Provide the highest value of all inputs Multiply Multiply an input by a -1 to yield a negative to positive range for a setpoint input BACK TO TOOLBOX

Toolbox Elements–Psychrometric
Used for measuring/calculating water vapor and heat in air samples. BACK TO TOOLBOX

Toolbox Elements–Time
Used to configure the following: Delays Schedules Time events and set the time/date for the controller through a Real-Time Clock (RTC). BACK TO TOOLBOX

Toolbox Elements–Tools
Used to help program developers keep code organized: Reference Hub Reference Target Text Used to assist in linking blocks together on different programming sheets: Used to monitor output values as a quick diagnostic tool: Live Trend Log BACK TO TOOLBOX

Toolbox Elements–VAV Used to interface with the flow sensor and actuator of a programmable VAV controller for single-duct and dual-duct applications. BACK TO TOOLBOX

BACK TO BASICS MENU (CLICK HERE)

CONNECTION RULES Topic 2.3
EC-gfxProgram Module 2: EC-gfxProgram Basics CONNECTION RULES Topic 2.3 BACK TO BASICS

Connecting to the Server
To connect to a Distech programmable device, you must first connect to the EC-BOS (server) using either: Connect to Server menu option in EC-gfxProgram Launch Wizard right-click menu option on a device in EC-NETAX GFX AX BACK TO BASICS

Connecting to the Server
An AX station must be running – either on an EC-BOS or on the localHost (PC) – in order for you to connect to it. BACK TO BASICS

Block Connection Rules
Two output ports cannot be connected to each other. Neither can two input ports be connected to each other. An output port can only be connected to an input port and an input port can only be connected to an output port. Any output can be connected to any input. Data types are automatically converted. An output port can be connected to multiple input ports. BACK TO BASICS

Block Connection Rules
An input port can only be connected to one output port. All blocks must have at least one connection (except for Custom blocks). Input and output ports with connection indicators must be connected. BACK TO BASICS

Connection Rules–Internal Constant
(Link To) Connection Rules–Internal Constant If there is an input port that the user does not need, but needs to be linked anyway, then connect it to an Internal Constant block and give it a value. < Right-click on specific port Providing a port format (i.e., units) for Internal Constants is not a coding requirement. BACK TO BASICS

Connection Rules–Monitors
If there is an output port that you wish to add to a Watch List, or that requires linking, then connect it to a Monitor block. Monitor All Outputs (Even multiple blocks) (Monitor All) Single Monitor block– (Link To > Monitor) < Right-click on center of any selected block < Right-click on specific port BACK TO BASICS

Associated Errors Errors in EC-gfxProgram are revealed in 2 ways:
Coding errors appear in the Error List pane at the bottom. Network/Connection errors appear in a pop-up either in an Exception Viewer or as Message History. BACK TO BASICS

Correcting Code Errors
Coding errors in EC-gfxProgram can be easily corrected – simply double- click on each error in the Error List and EC-gfxProgram takes you immediately to the offending block in the section of code where the error exists, complete with tooltip, blinking and red highlighting: Programming sheet & highlighted block with Tooltip Error List BACK TO BASICS

BLOCK CONNECTION TYPES Topic 2.4
EC-gfxProgram Module 2: EC-gfxProgram Basics BLOCK CONNECTION TYPES Topic 2.4 BACK TO BASICS

Connection Types Blocks can be connected in a variety of ways depending upon the user’s needs. The following is a list of the various connection types: Simple connection Monitoring a single output Monitoring all outputs Exposing a variable to the network Turnaround connection Fan-in connection Fan-out connection Connection via references A connection can either be started from an Output to an Input or from an Input to an Output. BACK TO BASICS

Connection Types–Simple
< Mouse cursor BACK TO BASICS

Connection Types–Turnaround
A turnaround is a way to inject into an input a previously calculated value. A turnaround connection in its simplest form is connecting an input port of a block to an output port of the same block. The purpose of this type of connection is to use the output value of a block as an input to the same block. BACK TO BASICS

Connection Types–Fan Out
A FAN-OUT connection is connecting the output port of one block to the input ports of one or more other blocks. This type of connection transmits information from one block to many blocks at once. BACK TO BASICS

Connection Types–References
A connection via references is done by connecting the output port of one block to a Reference Hub block and then connecting a corresponding Reference Target block to the input port(s) of other blocks. This is how you pass values between two Programming Sheets to inter-connect blocks. This type of connection helps to keep Programming Sheets clean (minimizing “spaghetti” linking), without having too many connectors and thus is easier to see where connections are going. Sheet #1 < Reference Hub Sheet #2 Reference Target > BACK TO BASICS

BUILD SEQUENCING Topic 2.5
EC-gfxProgram Module 2: EC-gfxProgram Basics BUILD SEQUENCING Topic 2.5 BACK TO BASICS

Build Sequencing After a control sequence is fully developed, it needs to be built to determine if there are any logical errors and to evaluate if the results are as expected. The way that blocks are connected and laid out affect the order in which the code is compiled. Proper planning in advance can save a lot of confusion and errors when it comes time to build. The compiler optimizes the code in a way that if a block or group of blocks does not execute something that is used or is not linked to any block giving an end result, these blocks are not executed. BACK TO BASICS

Build Sequencing Sometimes, it is possible to generate a sequence coding error by inadvertently omitting a link. No error location is provided, so these types of errors can be somewhat difficult to find. BACK TO BASICS

Build Sequencing The following determines how project code is compiled: The compiler locates the endpoints of the project code and starts the building process from here. It then follows the connections to the beginning of the sequence. ENDPOINTS If there are two or more separate groups of connected blocks, then the one located higher on the y-axis will be compiled before the lower ones and the one located further to the left of the x-axis will be compiled before the ones located further to the right. LOCATION If you change the relative order of blocks on the programming sheet, the project may need to be synchronized before the new code can be executed. BACK TO BASICS

BLOCK ACTIONS Topic 2.6 Module 2: EC-gfxProgram Basics EC-gfxProgram
BACK TO BASICS

Typical Block Actions Every block or resource has a set of actions that can be performed on it such as: Configure View Content Find all references Copy From Value and Mode (Manual/Auto) (Lonworks only) Override/Auto Configure Ports All of these actions are not available on every block, nor necessarily in this order; the type of block determines the actions that are available. BACK TO BASICS

BACnet Analog Value Actions
Block Actions Aside from the block configuration that can be done directly to the block or through the Properties pane, every block (except Reference Hub and Text blocks) is able to access one or more advanced configuration windows. Examples: Schedule Actions BACnet Analog Value Actions Custom Block Actions BACK TO BASICS

Block Actions–Defaults
Blocks have a default action when double-clicked. The default action for a block is shown in bold when you right-click on it. BACK TO BASICS

Block Actions–Setting Formats
Control (proxy) points can be created in the EC-NETAX station database that are subscribed to the data points in the controller. When possible, the name, format, and unit configured in EC-gfxProgram are automatically exported to the EC-NETAX proxy points and applied to them. EC-NETAX Proxy Point EC-gfx Block If no format is set for a block’s output port, the control (proxy) point in EC-NETAX will be numeric without a facet applied. BACK TO BASICS

Opening Block Actions Block actions can be opened/accessed in several ways: USER ACTION RESULT Right-clicking on a BLOCK provides a drop-down list from which to select an action Double-clicking on a BLOCK default action is activated Clicking the blue hyperlinks at the bottom of the PROPERTIES pane specific action is activated Right-clicking on an Input or Output RESOURCE in the Resource Viewer provides a short drop-down list – usually Configure, Overrides, Auto and Set < Click to see a graphical view of these actions. Port Formats cannot be accessed as a block action in the Resource Viewer. BACK TO BASICS

BLOCK ACTIONS Actions on Blocks Actions on Properties
< Double-click on block < Right-click on block Right-click menu F4 – Properties BLOCK ACTIONS Click on Action hyperlinks > Actions on Resources < Right-click on resource Right-click menu

SAVING A GFX PROJECT Topic 2.7
Auto-Save Auto-Backup Saving to a File Locally EC-gfxProgram Module 2: EC-gfxProgram Basics SAVING A GFX PROJECT Topic 2.7 BACK TO BASICS

Auto-Save Like EC-NETAX, EC-gfxProgram has an auto-save feature. Where AX auto-saves based on a timed interval (e.g., every 30 minutes), EC-gfxProgram saves a project to the AX server (EC-BOS) whenever ANY of the following occurs: Compiling/sending code – selecting Build & Send button Synchronizing a project – selecting the Synchronize button Placing GFX into the Debug (monitor) mode to view live values after a changed has been made to the code since the last save – code is built/sent to the controller AND SAVED to the EC-BOS (server) 3 2 1 BACK TO BASICS

Auto-Save The Auto-Save function is dependent on the Automatically Save option in EC-gfxProgram Options being checked. BACK TO BASICS

Manual Save (to AX Server)
An EC-gfxProgram project can be manually saved to the AX server (EC-BOS) by using the following keyboard shortcut: CTRL + S This saves the project to the File space of the AX station in a folder called “Bcp” as a generic file called “Project.gfx” under a coded folder designated in hexadecimal nomenclature for each specific controller under that EC-BOS. Whenever EC-gfxProgram asks you if you wish to Save a Project, it is asking if you want to save the project to the AX server (EC-BOS). BACK TO BASICS

Manual Save (to AX Server)
NEVER change the name of the coded folder OR the Project.gfx file or you will no longer be able to launch the project directly from EC-NET-AX. BACK TO BASICS

Auto-Backups Additionally, every time an EC-gfxProgram project is saved to the server (EC-BOS) using CTRL+S, it is also backed up to an Auto Backups folder on your laptop. Backed-up projects are organized by EC-BOS IP address and named using the same name you applied to the controller in EC-NETAX. BACK TO BASICS

Manual Save to a File Locally
You can also manually save an EC-gfxProgram project TO A FILE anywhere on your laptop. BACK TO BASICS

The QUIZ is still under development
The QUIZ is still under development. So click again and we’ll take you to the next module: Distech Controllers. NEXT MODULE

MODULE 2 EC-GFX PROGRAM BASICS

Similar presentations

Presentation on theme: "MODULE 2 EC-GFX PROGRAM BASICS"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

MODULE 2 EC-GFX PROGRAM BASICS

Similar presentations

Presentation on theme: "MODULE 2 EC-GFX PROGRAM BASICS"— Presentation transcript:

Similar presentations

About project

Feedback