Bind#

1. Project Creation and General Operation#

• Project Creation: Start by creating a new project, selecting the specific HMI model (DOP-100 series), setting communication parameters (PLC type, communication port, protocol), and defining screen size and orientation.

• User Interface: DOPSoft features a standard Windows-based interface with menus, toolbars, a project explorer (showing screens, alarms, recipes, etc.), a property window for elements, and the main screen editing area.

• Workflow: The typical workflow involves creating screens, adding elements (buttons, displays, graphs), configuring element properties (address, appearance, actions), setting up communication, defining alarms and recipes, writing macros, compiling the project, and downloading it to the HMI.

2. Screen Elements#

DOPSoft offers a wide range of elements to design interactive HMI screens:

• Buttons:

  • Basic Buttons: Set to On, Set to Off, Maintained (Toggle), Momentary (Push). Control single bits.

  • Value Setting Buttons: Set Value, Set Constant, Increment/Decrement. Write specific values or adjust numeric values in registers.

  • Screen Navigation: Goto Screen. Switch between different screens.

  • Multistate Button: Changes appearance based on the value of a linked address.

  • System Buttons: Buttons for specific HMI functions like backlight control, buzzer, screen lock, etc.

• Data Display:

  • Numeric Display: Show values from registers in various formats (decimal, hexadecimal, binary, floating point).

  • Character Display: Show text strings from registers.

  • Date/Time/Week Display: Display current system date and time.

  • General Message Display: Display predefined messages based on a register’s value.

  • Moving Sign: Display scrolling text messages.

• Drawing Elements:

  • Basic Shapes: Line, Rectangle, Circle, Ellipse, Polygon. Used for screen layout and decoration.

  • Text: Static text labels.

  • Scale: Visual representation of a numeric value within a range.

  • Table: Display data in a tabular format.

  • Image: Display static images.

• Graphs:

  • Historical Trend Graph: Display historical data sampled from registers over time.

  • Real-time Trend Graph: Display current data trends.

• Meters: Analog-style meters to display values.

• Alarm Display: Show active and historical alarms.

• Recipe Display/Entry: Elements specifically designed for interacting with recipe data.

• Input Elements: Numeric Entry, Character Entry, Date/Time Entry, Keypad Call. Allow users to input data into registers.

3. Internal Memory#

The HMI utilizes various types of internal memory for storing data and system information.

• Internal Register ($):

  • Type: Volatile (data lost on power off).

  • Purpose: General-purpose data storage and configuration.

  • Size: 65536 sets of 16-bit registers ($0 to$65535).

  • Usage: Suitable for temporary data, intermediate calculations within macros, and storing values that do not need to persist across power cycles.

• Non-volatile Internal Register ($M):

  • Type: Non-volatile (data retained on power off).

  • Purpose: Storing important data that must be preserved, such as settings, counters, or status flags.

  • Size: 1024 sets of 16-bit registers ($M0.0 to$M1023.15). Each $M register is 16 bits (1 word). Bits within each word can be accessed (e.g.,$M10.5).

  • Usage: Configuration parameters, production counts, alarm history pointers, etc.

• Indirect Address Register (*$):

  • Type: Volatile.

  • Purpose: Allows dynamic access to other memory addresses. The value in a specified $ register is used as the address to read from or write to.

  • Syntax: *$n, where n is the address of an$ register containing the target address.

  • Example: If $100 contains the value 500, then *$100 refers to the content of register $500. Changing the value in$100 changes which register *$100 points to.

  • Usage: Implementing flexible data logging, accessing arrays of data, or creating dynamic displays based on runtime conditions.

• Internal Parameter:

  • Type: Read-only (cannot be written to directly by the user).

  • Purpose: Provides access to internal HMI system status and information.

  • Examples: TIME_YEAR, TIME_MONTH, TIME_DAY, TIME_HOUR, TIME_MINUTE, TIME_SECOND (system clock), SD_STATUS (SD card status), USB_STATUS (USB status), TP_X, TP_Y (touch coordinates), BATTERY_VOLTAGE, FW_VERSION1, FW_VERSION2 (firmware version), NET1_IP1, NET1_IP2, etc. (network parameters).

  • Usage: Displaying system time, monitoring hardware status, getting touch input, displaying network configuration. Only accessible via Word elements (like Numeric Display).

• **Recipe Registers (RCP, RCPNO, RCPG, RCP, ENRCP, ENRCPNO, ENRCPG, ENRCPGNAME, ENRCP): These registers are specifically used in conjunction with the Recipe function and are detailed further in the Recipe section.

4. Macro#

Macros in DOPSoft are powerful tools for executing custom logic and operations based on events or conditions. They are independent programs written using a specific command set.

• Macro Types:

  • On Macro / Off Macro: Attached to buttons. Execute once when the button’s state changes from Off to On (On Macro) or On to Off (Off Macro). Available for Set to On, Set to Off, Maintained, and Momentary buttons.

  • Before Execute Macro: Attached to buttons/inputs. Executes before the element’s primary action when pressed.

  • After Execute Macro: Attached to buttons/inputs. Executes after the element’s primary action when pressed.

  • Screen Open Macro: Executes once when a screen is loaded or switched to. Useful for initializing screen-specific data or settings.

  • Screen Close Macro: Executes once when a screen is exited or switched from. Useful for saving screen-specific data or cleaning up.

  • Screen Cycle Macro: Executes repeatedly while a screen is active, with a configurable cycle delay time. Suitable for periodic tasks like updating displays or checking conditions.

  • Submacro: Reusable blocks of macro commands, similar to subroutines. Up to 512 submacros (1-512) are available. Can be called from other macros. Can be password protected.

  • Initial Macro: Executes only once immediately after the HMI boots up. Ideal for global initialization tasks, setting default values, or checking system status on startup.

  • Background Macro: Executes repeatedly in the background, independent of the active screen. Processes a configurable number of lines per cycle (1-512). Suitable for continuous monitoring or background data processing.

  • Clock Macro: Executes repeatedly based on a set time interval (delay). Executes all commands within the macro at once when triggered. Priority (Low, Medium, High) can be set to influence execution timing accuracy. Suitable for time-based tasks.

• Macro Commands: The macro language includes commands for:

  • Arithmetic Operations: Addition, Subtraction, Multiplication, Division, Modulo, etc.

  • Logical Operations: AND, OR, XOR, NOT, Bit Shift.

  • Data Transfer: Move data between registers (MOV), Set/Clear bits (SET, CLR).

  • Data Conversion: Convert data types (e.g., Integer to Float).

  • Comparison: Compare values (EQ, NE, GT, LT, GE, LE).

  • Flow Control: Conditional execution (IF, ELSEIF, ELSE, ENDIF), loops (FOR, NEXT, WHILE, WEND), jumps (GOTO), calling submacros (CALL).

  • Bit Setting: Direct manipulation of individual bits.

  • Communication: Send/receive data to/from connected devices (PLCs, etc.).

  • Drawing: Control drawing elements dynamically.

  • File Access: Read/write data to/from external storage (USB, SD card) or FileSlots.

  • Others: System control commands (screen switch, buzzer, etc.), time/date functions.

• Macro Editor: DOPSoft provides an editor for writing, debugging, and managing macros.

5. Communication Settings#

• Configure communication drivers to connect the HMI to external devices, primarily PLCs.

• Select the PLC manufacturer and model.

• Configure communication parameters such as port (COM1, COM2, Ethernet), protocol (e.g., Modbus RTU/ASCII, Ethernet/IP), baud rate, data bits, stop bits, parity, and station address.

• Support for multiple communication ports and mixed protocols depending on the HMI model.

6. Control Block and Status Block#

These are dedicated memory areas used for system-level interaction.

• Control Block:

  • Purpose: Allows the PLC or macros to control HMI system functions by writing values to specific registers within this block.

  • Functionality: Screen switching, backlight control, buzzer control, alarm acknowledgment/clearing, history buffer sampling/clearing, recipe control (load, save, transfer), multi-language switching, printing.

  • Structure: A contiguous block of word registers. The starting address is configurable.

  • Examples of Registers (within the block): Screen Number, General Control Word, Recipe Control Word, Alarm Control Word.

• Status Block:

  • Purpose: Provides the PLC or macros with information about the HMI’s current status by reading values from this block.

  • Functionality: HMI running status, communication status, alarm status, touch status, external storage status.

  • Structure: A contiguous block of word registers. The starting address is configurable.

7. Recipe#

The Recipe function is used to manage sets of parameters for different product types or operating modes.

• Purpose: Store and easily load/save groups of data values (parameters) to/from HMI memory or external storage. Reduces the need for the PLC to manage large parameter sets.

• Recipe Types:

  • 16-bit Recipe: Stores 16-bit (Word) data. Uses RCP (Recipe Data) and RCPNO (Recipe Number) registers.

  • 32-bit Recipe: Stores 32-bit (Double Word) data. Uses RCP, RCPNO, and RCPG (Recipe Group) registers. Supports grouping recipes.

  • Enhanced Recipe: An advanced type with more flexibility. Uses its own set of registers (ENRCP, ENRCPNO, ENRCPG, ENRCPGNAME, *ENRCP for indirect access).

• Structure: Recipes are typically organized into a recipe table with rows (recipes) and columns (parameters).

• Management:

  • Storage: Recipes can be stored in the HMI’s non-volatile memory, on a USB disk, or on an SD card.

  • Operations: Load a recipe from storage to HMI memory, save a recipe from HMI memory to storage, transfer recipe data between HMI and PLC registers. These operations can be triggered by buttons or macros using Control Block registers or specific macro commands.

8. Sampling#

The sampling function allows collecting data from registers over time for analysis and display.

• History Buffer: A temporary storage area in HMI memory for sampled data.

• Historical Trend Graph: Visualizes data from the history buffer as a trend line graph.

• Historical Data Tables: Display sampled data in a tabular format.

• Configuration: Define which registers to sample, the sampling interval (time-based or event-based), and the storage location (history buffer, external storage).

• Export: Sampled data can be exported to external storage (USB, SD card) for further analysis on a PC.

9. Alarm#

The alarm function is used to monitor conditions in the PLC or HMI and display corresponding messages when conditions are met.

• Alarm Settings: Define alarm triggers (based on bit status or register value ranges), alarm messages, alarm priorities, and acknowledgment requirements.

• Alarm History Table: Stores a log of all triggered alarms, including the time they occurred and were acknowledged.

• Active Alarm List: Displays a list of alarms that are currently active (triggered and not yet cleared or acknowledged).

• Alarm Frequency Table: Provides statistics on how often each alarm has been triggered.

• Export: Alarm history and frequency data can be exported to external storage.

• Control/Status: Alarm acknowledgment and clearing can be controlled via the Control Block.

10. Keypad#

DOPSoft provides various on-screen keypad options for data entry:

• Numeric Keypad: For entering numerical values.

• Character Keypad: For entering text characters.

• Full Keypad: A combination of numeric and character keys.

• Custom Keypad: Ability to design a custom keypad layout.

Keypads are typically linked to Numeric Entry or Character Entry elements.

11. Tools#

DOPSoft includes essential tools for project development and HMI management:

• Compile: Checks the project for errors and prepares it for download.

• Download: Transfers the compiled project from the PC to the HMI.

• Upload: Retrieves the project from the HMI to the PC.

• Online Simulation: Simulates the HMI project on the PC, allowing connection to a real or simulated PLC.

• Offline Simulation: Simulates the HMI project on the PC without connecting to a PLC.

• Firmware Update: Updates the HMI’s operating system.

• Reset HMI: Performs a software or factory reset of the HMI.

12. Advanced Settings#

• Tag Table: (Details not provided in snippets, but typically used for defining symbolic names for memory addresses).

• FileSlot File Management: Allows creating and managing virtual file areas (FileSlots) within the HMI’s memory. Macro commands enable reading, writing, removing, getting length, and importing/exporting data within these FileSlots. Useful for storing small data files or configuration settings directly on the HMI.

• Security: Configure user levels and passwords to restrict access to specific screens or functions (like macros or system settings).

13. Other Features#

• Multi-language Support: Design screens with multiple languages that can be switched at runtime.

• Screen Capture: Take screenshots of the HMI display.

• Printer Output: Print screen content or data tables to a connected printer.