Welcome to the comprehensive documentation for AccuTrack Designer, the configuration tool for AccuTrack SCADA. This guide will help you understand, install, configure, and effectively use AccuTrack Designer to create and deploy industrial automation projects.

AccuTrack Designer is a comprehensive SCADA configuration tool that allows you to design, configure, and deploy industrial automation projects. It provides a complete environment for creating HMI screens, configuring data points (tags), setting up alarms, writing automation scripts, and managing communication with industrial devices.

This documentation covers everything from getting started to advanced features including Lua scripting, alarm configuration, communication setup, security, and deployment.

• 1. Introduction
• 2. Getting Started
• 3. User Interface Overview
• 4. Project Management
• 5. Working with Tags
• 6. Creating HMI Screens
• 7. Using Components
• 8. Scripting with Lua
• 9. Configuring Alarms
• 10. Communication Setup
• 11. Security Configuration
• 12. Schedules and Automation
• 13. Historical Data (Historian)
• 14. Building and Deploying
• 15. Device Management
• 16. Tips and Best Practices
• 17. Troubleshooting

What is AccuTrack Designer?

AccuTrack Designer is a comprehensive SCADA (Supervisory Control and Data Acquisition) configuration tool that allows you to design, configure, and deploy industrial automation projects. It provides a complete environment for creating HMI screens, configuring data points (tags), setting up alarms, writing automation scripts, and managing communication with industrial devices.

Key Features

• Visual HMI Design: Create interactive operator screens with drag-and-drop components
• Tag Management: Centralized database for process variables and data points
• Multi-Protocol Support: Connect to devices via Modbus, OPC UA, and other industrial protocols
• Lua Scripting: Add custom logic and automation with embedded Lua scripting engine (v5.4.7)
• Alarm Management: Configure and manage alarm conditions and notifications
• Security: Role-based access control and user management
• Historical Data: Configure data collection and trending
• Cross-Platform: Runs on Windows and Linux
• Machine Learning: Integrated ML models for predictive maintenance and performance tracking

System Requirements

Before installing AccuTrack Designer, ensure your system meets the following requirements:

• Operating System: Windows 10/11 or Linux (Ubuntu 20.04+)
• Qt Framework: Qt 6.10.1 or later
• Memory: Minimum 4GB RAM (8GB recommended)
• Disk Space: 500MB for installation, additional space for projects
• Display: 1280x720 minimum resolution

First Launch

When you first launch AccuTrack Designer, you'll see the Startup Page with the following options:

• Recent Projects: A list of recently opened projects (if any)
• New Project: Create a new SCADA project
• Open Project: Browse and open an existing project
• Remove: Remove a project from the recent projects list

Creating Your First Project

1. Click New Project on the startup page, or use File → New Project from the menu
2. In the file dialog, navigate to your desired location
3. Enter a project name (e.g., "MyFirstProject")
4. Click Save (projects are saved with .isc extension)
5. The project will be created and automatically opened

The project structure will be created with the following default folders:

• Tags/ - Tag database files
• Screens/ - HMI screen templates
• Scripts/ - Lua script files
• Communication/ - Communication module configurations
• Alarms/ - Alarm configurations
• Security/ - User and security settings
• Historian/ - Historical data configurations
• Schedules/ - Scheduled task configurations

The AccuTrack Designer interface is organized into several key areas:

Main Window Layout

The interface consists of:

• Menu Bar: File, Build, Download, Upload, Help menus
• Project View (Left Panel): Tree view of your project structure including SCADA projects, tags, screens, scripts, communication modules, alarms, schedules, historian, security, machine learning, and settings
• Editor Area (Center): Tabbed interface for open editors - each editor opens in its own tab
• Components Palette (Right Panel): Visual components available for HMI screens, organized by categories (Basic Controls, Industrial Components, Data Visualization, Layout Components)
• Bottom Panel: Output tab (build output), Debug tab (debug console), Properties tab (property editor for selected components)

Menu Bar

File Menu: New Project, Open Project, Recent Projects, Save, Save As, Close Project, Exit

Build Menu: Build Project, Clean Project

Download Menu: Download to Device (deploy project to target device)

Upload Menu: Upload from Device (retrieve project from device)

Help Menu: Documentation, About

Project Structure

AccuTrack projects are organized in a hierarchical structure:

• ProjectName.isc - Main project file
• SCADA Projects/SCADA_Name/ - Contains Tags, Screens, Scripts, Communication, Alarms, Schedules, Historian, Security, MachineLearning
• Settings/ - Project settings

Creating a New Project

1. File → New Project (or Ctrl+N)
2. Choose a location and enter project name
3. Project is created with default structure
4. Project automatically opens in the Project View

Opening and Saving Projects

Open Project: File → Open Project (or Ctrl+O) - Browse to the project file (.isc)

Save Project: File → Save (or Ctrl+S) - Saves all changes including tag tables, screen configurations, script files, and all module configurations

Tags are the fundamental data points in your SCADA system. They represent process variables, I/O points, and computed values.

Understanding Tags

A tag is a named data point that can represent:

• Input Tags (I): Values read from external devices (PLCs, sensors)
• Output Tags (O): Values written to external devices
• Memory Tags (M): Internal variables for calculations and logic

Tag Data Types

Supported data types include: Boolean, Integer (16-bit, 32-bit, 64-bit signed/unsigned), Float (32-bit and 64-bit), String, Enumeration, Array, and Structure.

Creating Tags

1. In Project View, expand your SCADA project
2. Right-click on Tags → New Tag Table (or double-click Tags)
3. The Tag Table Editor opens
4. Click Add Tag or press Insert
5. Configure tag properties: Name, Description, Type (I/O/Memory), Data Type, Address (for I/O tags), Value, Min/Max, Units, Scaling, Access Level

Tag Addressing

For I/O tags, addresses specify where to read/write data. Examples:

• Modbus: 40001 (Holding Register), 30001 (Input Register), 10001 (Coil), 00001 (Discrete Input)
• Bit Addressing: 40001.0 (Bit 0 of Holding Register 1)

HMI (Human-Machine Interface) screens are the visual interface operators interact with.

Screen Editor

The Screen Editor provides a visual canvas for designing operator interfaces.

Creating a New Screen

1. In Project View, right-click Screens → New Screen
2. Enter screen name and properties
3. Screen is created and opened in editor

Screen Canvas

The canvas provides: Grid (visual alignment guide), Snap to Grid, Zoom Controls, Selection Tools, and Layers (Z-order management).

Adding Components

Components can be added from the Components Palette by clicking and placing, drag-and-drop, or copy/paste.

Component Properties

When a component is selected, the Properties Panel shows all properties organized by category:

• General: Name, position, size, visibility
• Appearance: Colors, fonts, borders, styles
• Data: Tag bindings, expressions
• Behavior: Events, animations, interactions
• Security: Access levels, permissions

Components are the building blocks of HMI screens. They provide visual representation and interaction capabilities.

Component Categories

1. Basic Controls: Buttons, Text Input, Selection Controls (ComboBox, ListBox), Sliders and Spinners

2. Industrial Components: Pumps, Motors, Tanks, Valves, Conveyors - Visual representations with states and animations

3. Data Visualization: TrendView (real-time and historical trending), GaugeView (circular/linear gauges), AlarmView (alarm list display), TableView (data grid display)

4. Layout Components: TabComponent (multi-page layouts), PopupComponent (modal dialogs), Container Components (group boxes, panels, scroll areas)

Component Tag Binding

Most components can be bound to tags:

1. Select component
2. In Properties panel, find Tag or Data Source property
3. Click tag selector (... button)
4. Browse tag tables and select tag
5. Component will display/control tag value

Binding Types: Read (display tag value), Write (control tag value), Read/Write (both display and control)

AccuTrack Designer includes an embedded Lua scripting engine (v5.4.7) for custom logic and automation.

Creating Scripts

1. In Project View, expand Scripts
2. Right-click → New Script
3. Enter script name
4. Script Editor opens with syntax highlighting, code completion, and error marking
5. Write your Lua code
6. Save script (automatically saved with project)

Accessing Tags from Scripts

The Lua bridge provides access to tags:

-- Read tag value
local value = getTag("TagName")

-- Write tag value
setTag("TagName", 100)

-- Check tag quality
local quality = getTagQuality("TagName")
              

Script Execution Contexts

Scripts can execute in different contexts:

• Event-Triggered: Execute when specific events occur (tag value changes, button clicks, timer events, alarm conditions)
• Periodic: Execute at regular intervals with configurable scan rate
• Startup/Shutdown: Execute once for system initialization or cleanup

Common Script Functions

Available functions include: getTag(name), setTag(name, value), getTagQuality(name), acknowledgeAlarm(id), print(message), log(message, level), sleep(ms), and standard Lua math functions.

Alarms notify operators of abnormal conditions and events in the process.

Alarm Types

• Digital Alarms: Trigger on Boolean tag state changes (ON alarm, OFF alarm)
• Analog Alarms: Trigger on numeric tag threshold violations (High, Low, High-High, Low-Low)
• Deviation Alarms: Trigger when tag deviates from setpoint with deadband
• Rate-of-Change Alarms: Trigger on rapid value changes

Creating Alarms

1. In Project View, expand Alarms
2. Right-click → Open Alarms Editor (or double-click)
3. Click Add Alarm
4. Configure alarm properties:
   • Basic: Name, Description, Tag, Type
   • Condition: Condition, Threshold, Deadband, Delay
   • Priority: Priority (1-100), Severity, Category
   • Behavior: Latching, Auto-Acknowledge, Shelving

Alarm States

Alarms can be in various states: Normal, Active, Acknowledged, Shelved, Cleared

Alarm Actions

Alarms can trigger actions: Notifications (display messages, sounds), Scripts (execute Lua scripts), Tag Writes (set tag values), Screen Navigation, Logging (log to historian)

The Communication module configures connections to external devices (PLCs, sensors, etc.).

Supported Protocols

• Modbus TCP/RTU: Industrial standard protocol
• OPC UA/DA: OPC Foundation protocols
• Custom Protocols: Extensible protocol support

Modbus Configuration

Creating a Modbus Connection:

1. In Project View, expand Communication
2. Double-click Communication Modules to open editor
3. Click Add Connection
4. Select Modbus TCP or Modbus RTU
5. Configure connection properties:
   • Modbus TCP: Name, IP Address, Port (default 502), Unit ID, Timeout, Retry Count
   • Modbus RTU: Name, Port (COM1, /dev/ttyUSB0), Baud Rate, Data Bits, Parity, Stop Bits, Unit ID

Modbus Scanner

The Modbus Scanner helps discover devices:

1. Open Device Manager tab
2. Click Scan for Devices
3. Configure scan parameters
4. Start scan - discovered devices appear in list

OPC UA Configuration

For OPC UA connections, configure: Endpoint URL, Security Policy, Security Mode, Username/Password, Certificate. Use Browse Nodes to browse server address space and select nodes to map to tags.

The Security module manages user accounts, roles, and permissions.

User Management

Creating Users:

1. In Project View, expand Security
2. Double-click Security to open editor
3. Click Users tab → Add User
4. Configure user properties: Username, Full Name, Email, Password (SHA-256 hashed), Active status, Roles, Groups

User Roles

Roles define permission sets:

• Administrator: Full system access
• Operator: Operational access, limited configuration
• Viewer: Read-only access
• Engineer: Configuration access
• Custom Roles: User-defined roles

Permission System

Permissions control access to resources: View (read-only), Control (write/control), Configure (configuration access), Admin (administrative access)

Resources include: Tags, Screens, Scripts, Alarms, Communication, System settings

Access Levels

Tags and components can have access levels: Public (no authentication), Operator (operator role or higher), Engineer (engineer role or higher), Administrator (administrator only)

Schedules automate script execution and tasks.

Schedule Types

• One-Time Schedule: Execute once at specified time
• Daily Schedule: Execute daily at specified time(s)
• Weekly Schedule: Execute on specific days of week
• Monthly Schedule: Execute on specific days of month

Creating Schedules

1. In Project View, expand Schedules
2. Double-click Schedules to open editor
3. Click Add Schedule
4. Configure schedule properties:
   • Basic: Name, Description, Type, Enabled
   • Timing: Start Time, End Time, Scan Cycle, Days
   • Execution: Script, Parameters, Priority, Retry, Max Execution Time

The Historian module configures data collection and storage for trending and analysis.

Data Collection Configuration

Tag Selection: Select tags to collect - tags can be added individually or in groups. Configure collection settings per tag.

Collection Settings

Sampling Rate:

• Periodic: Sample at fixed interval
• On Change: Sample when value changes
• On Change with Deadband: Sample on significant change
• Rate of Change: Sample based on rate of change

Storage Settings

Storage options include: In-Memory Buffer (circular buffer size), Persistent Storage (archive to disk), Compression (data compression settings), Retention (how long to keep data)

Deadband Configuration

Deadband prevents excessive data collection: Absolute Deadband (value must change by fixed amount), Percent Deadband (value must change by percentage), Rate Deadband (rate of change threshold)

Data Retrieval

Retrieve historical data for: Trending (display in TrendView components), Reports (generate reports), Analysis (data analysis), Export (export to external formats)

Before deploying to Runtime, projects must be built (compiled).

Building a Project

1. Build → Build Project (or Ctrl+B)
2. Build process:
   • Validates project configuration
   • Compiles resources
   • Generates deployment package
   • Creates QML files for Runtime
   • Packages all assets
3. Monitor build progress in Output tab
4. Build errors displayed in Output tab

Build Validation

Build process validates: Tag References, Screen References, Script Syntax (Lua scripts compile), Communication Config, Security Config

Deployment to Device

Download to Device:

1. Download → Download to Device
2. Select target device
3. Configure deployment settings
4. Transfer project package
5. Verify deployment

Target device must have: AccuTrack Runtime installed, Network connectivity, Sufficient storage space, Required permissions

The Device Manager helps discover and manage industrial devices.

Device Discovery

Scanning for Devices:

1. Access via Project View → Devices tab
2. Click Scan for Devices
3. Configure scan parameters: Protocol (Modbus, OPC UA), IP Range, Port, Timeout
4. Start scan - discovered devices appear in list

Modbus Scanner

For Modbus devices, the scanner discovers: Device addresses, Available registers, Device information

Device Configuration

Adding Devices Manually: Click Add Device, configure device (Name, Type, Protocol, Address, Port), test connection, save device

Device Status

Monitor device status: Online (device is connected), Offline (device is disconnected), Error (communication error), Unknown (status unknown)

Project Organization

• Naming Conventions: Use consistent naming (Tags: Tank1_Level, Screens: MainScreen, Scripts: StartupScript)
• Folder Structure: Organize by function - group related tags, organize screens by area, separate scripts by purpose
• Documentation: Document complex configurations - add descriptions to tags, comment scripts, document screen purposes

Tag Management

• Tag Naming: Use descriptive names - include location/equipment, include measurement type, use consistent abbreviations
• Tag Organization: Group related tags - use tag tables for logical groups, organize by process area, separate I/O from memory tags
• Tag Validation: Validate early - check addresses before deployment, verify data types, test tag connections

Screen Design

• Layout: Design for clarity - group related information, use consistent positioning, follow operator workflow
• Colors: Use standard conventions - Red (Alarm, Stop), Green (Normal, Running), Yellow (Warning, Caution), Blue (Information)
• Components: Use appropriate components - match component to data type, use industrial components for equipment, provide clear visual feedback
• Navigation: Make navigation intuitive - clear navigation paths, breadcrumbs or menu bars, quick access to critical screens

Scripting

• Performance: Write efficient scripts - minimize tag reads/writes, use appropriate scan rates, avoid blocking operations
• Error Handling: Always handle errors - use pcall for risky operations, log errors appropriately, provide fallback behavior
• Modularity: Break into functions - reusable functions, clear function names, single responsibility

Common Issues and Solutions

Project Won't Open

Symptoms: Error opening project file

Solutions: Verify file is valid .isc file, check file permissions, verify project structure is intact, try opening backup version

Tags Not Updating

Symptoms: Tag values not changing

Solutions: Check communication connection status, verify tag addresses are correct, check device is online, verify tag data types match, check communication scan rate

Screen Components Not Displaying

Symptoms: Components missing or not visible

Solutions: Check component visibility property, verify component is not behind another, check Z-order/layering, verify screen size is correct, check component position is on screen

Script Errors

Symptoms: Scripts not executing or errors

Solutions: Check script syntax in editor, verify tag names are correct, check script execution context, review console output for errors, test script functions individually

Build Failures

Symptoms: Build process fails

Solutions: Check Output tab for specific errors, verify all referenced files exist, check tag references are valid, verify script syntax, clean project and rebuild

Communication Errors

Symptoms: Cannot connect to devices

Solutions: Verify network connectivity, check IP addresses and ports, verify device is powered and online, check firewall settings, verify protocol settings match device, test with device manufacturer's tools

Alarm Not Triggering

Symptoms: Alarms not activating when expected

Solutions: Verify alarm condition is correct, check tag value is updating, verify threshold values, check deadband settings, verify alarm is enabled, check alarm priority/severity

Getting Help

If you encounter issues not covered in this documentation:

• Check the system logs: Output and Debug tabs
• Review error messages carefully
• Contact Indusys LTD support: info@indusysltd.com
• Phone support: +254 706085547
• Visit our website: Contact Us

Keyboard Shortcuts

• Ctrl+N - New Project
• Ctrl+O - Open Project
• Ctrl+S - Save Project
• Ctrl+B - Build Project
• Ctrl+W - Close Tab
• Ctrl+C - Copy
• Ctrl+V - Paste
• Delete - Delete
• Ctrl+Z - Undo
• Ctrl+Y - Redo

File Extensions

• .isc - AccuTrack project file
• .lua - Lua script file
• .json - Configuration files
• .qml - QML screen files

Project File Locations

Projects are typically stored in:

• Windows: %USERPROFILE%\Documents\AccuTrack\Projects\
• Linux: ~/Documents/AccuTrack/Projects/

Support Resources

• User Guide: This document (also available as PDF)
• Video Tutorials: Available on our YouTube channel
• Training Courses: Contact us for on-site or online training
• Software Updates: Check for updates regularly