All Categories ​>​ ​EVOLVE Fabrication ​>​ EVOLVE Fabrication Desktop App Manual

EVOLVE Fabrication Desktop App Manual

Updated 1 week ago by Kerry Poe

Control Client

EVOLVE Fabrication Client is a Windows application for managing and processing parts for machine automation, including bender and label printer devices. It provides a grid-based interface for part selection, device management, and automation workflows.

User Login

The application requires a login to the EVOLVE Foresite system by a user with a license of EVOLVE Fabrication. This login is used to determine the items which are available for processing by the client.

Configuration Setup

Configuration is managed via the Configuration Dialog (accessible from the toolbar or when prompted at startup if not configured).

Key Configuration Options
  • Profile Selection: Choose the machine profile for the workstation. This determines which device (e.g., Crippa Bender, Zebra Label Printer) is active.
  • Devices: Select which devices are active for this client.
  • Allow Multiple Selection: Enable or disable multi-select mode in the parts grid.
  • Auto Process Barcode Scans: If enabled, barcode scans are processed automatically.
  • PowerShell Scripts: Paths to optional PowerShell scripts for:
    • Barcode filtering
    • Barcode selection
    • Item pre-processing
    • Item post-processing
  • Conduit Size to Bender Mapping: Map conduit sizes to specific bender machine profiles for automated selection.

Configuration is persisted per user in %APPDATA%\eVolve\EVOLVE Fabrication\Configuration.xml. Any manual edits to this file must be performed while the program is closed.

Shortcut Keys

Key

Action

F5

Refresh data (reloads parts, profiles, conduit info)

Enter

Process selected parts

Escape

Clear selection in the parts grid

Double-click (row)

Process the double-clicked part

Basic Usage

Startup
  1. Launch the application. Only one instance is allowed per workstation.
  2. If not configured, you will be prompted to select a machine profile and configure devices.
Main Window
  • Parts Grid: Displays available parts with details (ID, project, size, status, etc.).
  • Toolbar: Provides access to login, configuration, refresh, and mapping dialogs.
  • Activity Log: Shows real-time log messages and system activity.
Common Actions
  • Select Parts: Click rows or use checkboxes (if multi-select enabled).
  • Process Parts: Press Enter or use the toolbar button to send selected parts to the configured device (bender, label printer, etc.).
  • Refresh Data: Press F5 or use the toolbar button to reload all data.
  • Clear Selection: Press Escape to clear all selections.
  • Configure: Use the configuration button to change profiles, devices, or mappings.
  • Map Conduit Sizes: Use the mapping dialog to associate conduit sizes with bender profiles.
    • Generally, this feature is used by label printer machines such that when labels are processed, the Adjusted Length can be calculated for the respective row based on the appropriate bender profile.
Barcode Scanning
  • If a barcode scanner is configured, scans can filter and select parts automatically.
    • Enable a barcode scanner by selecting the appropriate device within the Configuration Dialog.
  • If "Auto Process Barcode Scans" is enabled, scanned parts are processed immediately.

Advanced

  • PowerShell Integration: Custom scripts can be used for advanced filtering, selection, and processing logic.
  • Grid Layout: The grid layout and column order are saved/restored per user. This is done automatically.

Troubleshooting

  • Only one instance allowed: If you see a message about another instance running, close the other instance before starting a new one.
  • Device not configured: If prompted, ensure you select a valid machine profile and device.
  • Log Output: Double-click the log area to save logs to a file for support.

Server Redirection (Advanced Testing)

This function is intended for testing purposes only and is not supported in production environments.

To redirect the server which the EVOLVE Fabrication Client communicates with to receive data, use the following steps:

  1. On the Login Dialog, log out if you are currently logged in.
  2. Double right-click on the label which shows the version number.
  3. In the subsequent prompts, enter the appropriate server values as provided for testing.
  4. Follow the instructions provided by the confirmation dialog.
  5. Open the EVOLVE Fabrication Client and login with the appropriate credentials for the server you are connecting to.
    • You may get a login error upon initial launch. This would be expected.

Once a server redirection is in place, this will be used for all communication (instead of the production server). To remove the redirection:

  1. Make sure the EVOLVE Fabrication Client is closed on the local computer.
  2. Edit the Configuration File in Notepad.
  3. Remove the specialized setting value which defined the override (what was added in the previous steps).
  4. Save your changes.
  5. Open the EVOLVE Fabrication Client and login with your production credentials.
    • You may get a login error upon initial launch. This would be expected.

Crippa Bender Device

Overview

Crippa Bender Client is a Windows application for managing and outputting bend data to a Crippa Bender machine. It provides a simple interface for configuring output paths, monitoring activity, and integrating with the EEVOLVE Fabrication Client.

Configuration Setup

Configuration is managed via the main dialog window.

Key Configuration Options
  • Control File Path:
    • Full path and file name of the control file used to manage bend operations (e.g., D:\mem\PrgToSel.txt).
    • Must point to a valid directory. If the file does not exist, it will be created during execution.
    • Set using the "Browse" button next to the control file field or can be manually entered.
  • Bend Output Path:
    • Directory where output bend files are saved (e.g., D:\mem\wks.dir\evolve).
    • Must be a valid, existing directory.
    • Set using the "Browse" button next to the output path field or can be manually entered.
  • Delete Existing Output:
    • (Configured by editing the configuration file directly while the program is closed.)
    • If enabled, all existing output files matching the bend file pattern are deleted before new files are generated.
    • This ensures only the latest output files are present.

Configuration is saved automatically and persists per user in %APPDATA%\eVolve\Crippa Bender Client\Configuration.xml. Any manual edits to this file must be performed while the program is closed.

Basic Usage

Startup
  1. The application is launched automatically by the EVOLVE Fabrication Client as needed based on the configuration.
    • The application cannot be launched manually or standalone.
  2. The main dialog shows configuration fields and a log output area.
  3. Any detected configuration errors are shown in a message dialog on startup. Address any issues before sending data.
Main Window
  • Control File Path:
    • Set the path to the control file. This file is updated with the name of the latest bend file after processing.
  • Bend Output Path:
    • Set the directory where bend files will be written.
  • Activity Log:
    • Displays real-time log messages and system activity.
Common Actions
  • Configure Paths:
    • Use the "Browse" buttons to select the control file and output directory.
    • Ensure both paths are valid and accessible.
  • Monitor Activity:
    • The log area displays all actions, errors, and file operations.
    • Double-click the log area to save its contents to a file.
Processing Bend Data
  • The application receives bend data from the EVOLVE Fabrication Client.
  • For each part:
    • Validates and processes the bend data.
    • Writes output files (.mpf and .ybc) to the configured output directory.
    • Updates the control file with the name of the latest output file.
    • Deletes existing output files if configured to do so.
System Tray
  • Minimizing or closing the window sends the application to the system tray.
  • Right-click the tray icon for options to restore or exit.

Troubleshooting

  • Only one instance allowed: If you see a message about another instance running, close the other instance before starting a new one.
  • Invalid Path: Ensure the control file and output directory exist and are accessible.
  • Log Output: Double-click the log area to save logs to a file for support.

Zebra Barcode Scanner Device

Overview

Zebra Barcode Scanner Client is a Windows application for connecting to a Zebra barcode scanner, receiving barcode scans, and integrating scanned data with the EVOLVE Fabrication Client. It provides a simple interface for monitoring scan activity and logging events.

Configuration Setup

This device requires the Zebra Barcode Scanner SDK to be installed on the Windows machine.

Configuration is handled automatically. No manual configuration is required for most users.

  • Scanner Connection:
    • The application expects the Zebra scanner to be connected via SNAPI (USB).
    • On startup, the application detects connected scanners and subscribes to barcode scan events.
  • Logging:
    • All activity and scan events are logged in the application's log area.

Configuration is saved per user in %APPDATA%\eVolve\Zebra Barcode Scanner Client\Configuration.xml. Any manual edits to this file must be performed while the program is closed.

Basic Usage

Startup
  1. Connect your Zebra barcode scanner to the computer via USB (SNAPI).
  2. The application is launched automatically by the EVOLVE Fabrication Client as needed based on the configuration.
    • The application cannot be launched manually or standalone.
  3. The main dialog will appear, showing scan status and a log output area.
  4. Any detected configuration errors are shown in a message dialog on startup. Address any issues before sending data.
Main Window
  • Scan Status:
    • On startup, the application lists all detected scanners (model, serial number, interface).
    • Displays "Connected. Listening for scans." when ready.
  • Activity Log:
    • Shows all scan events, errors, and system activity.
    • Double-click the log area to save its contents to a file.
Scanning Barcodes
  • When a barcode is scanned:
    • The application logs the scan event and barcode data.
    • The scanned data is sent to the EVOLVE Fabrication Client for processing.
    • Any response from the server is logged.
System Tray
  • Minimizing or closing the window sends the application to the system tray.
  • Right-click the tray icon for options to restore or exit.

Troubleshooting

  • Only one instance allowed: If you see a message about another instance running, close the other instance before starting a new one.
  • No scanners detected: Ensure your Zebra scanner is connected via USB and recognized by Windows.
  • Log Output: Double-click the log area to save logs to a file for support.

Zebra Label Printer Device

Overview

Zebra Label Printer Client is a Windows application for printing labels using a Zebra label printer. It integrates with the EVOLVE Fabrication Client to receive part data, format labels using a template, and send print jobs to the configured printer.

Configuration Setup

This device requires the Zebra Printer Drivers to be installed on the Windows machine.

Configuration is managed via the main dialog window.

Key Configuration Options
  • Printer Connection:
    • Select the type of connection for the Zebra label printer (e.g., USB).
    • Set the printer name as recognized by Windows.
  • Label Template File Path:
    • Use the Zebra Label Template Software to create templates.
    • Specify the file path to the label template used for printing.
      • This is expected to a PRN file which is generated by exporting a label template using the "Print to File" option.
    • The template should contain tokens that will be replaced with part data.
      • Token values are found by hovering over a column header of the part grid of the EVOLVE Fabrication Client. For example, hovering over the Length column would show a token value of {LengthDisplay}
  • Printer Name:
    • Enter the name of the Zebra printer as it appears in Windows.

Configuration is saved automatically and persists per user in %APPDATA%\eVolve\Zebra Label Printer Client\Configuration.xml. Any manual edits to this file must be performed while the program is closed.

Basic Usage

Startup
  1. Connect your Zebra label printer to the computer (via USB).
  2. The application is launched automatically by the EVOLVE Fabrication Client as needed based on the configuration.
    • The application cannot be launched manually or standalone.
  3. The main dialog will appear, showing configuration fields and a log output area.
  4. Any detected configuration errors are shown in a message dialog on startup. Address any issues before sending data.
Main Window
  • Printer Connection:
    • Select the connection type and enter the printer name.
  • Label Template:
    • Set the path to the label template file.
  • Activity Log:
    • Displays real-time log messages and system activity.
Printing Labels
  • The application receives part data from the Machine Control Client system.
  • For each part:
    • Validates the data and loads the label template.
    • Performs token substitution to fill in part details.
    • Sends the formatted label to the configured Zebra printer.
    • Logs the result of each print job.
System Tray
  • Minimizing or closing the window sends the application to the system tray.
  • Right-click the tray icon for options to restore or exit.

Troubleshooting

  • Only one instance allowed: If you see a message about another instance running, close the other instance before starting a new one.
  • Printer not set: Ensure the printer connection type and name are correctly configured.
  • Label template file not found: Verify the template file path is correct and accessible.
  • Log Output: Double-click the log area to save logs to a file for support.

How did we do?

Powered by HelpDocs (opens in a new tab)

Powered by HelpDocs (opens in a new tab)