Circle OneClick Manufacturing Advanced Configuration

Manufacturer specific configurations

Production with SprintRay

Production with SprintRay can be carried out using either the RayWare desktop slicer or the SprintRay web interface, both of which are supported by OneClick Manufacturing.

• Stable web workflowDefault: When the stable web app workflow is selected, a new browser tab opens on the print setup page. The usual SprintRay web workflow can then be used to complete the print.
• Experimental web workflowExperimental: Selecting the experimental web app workflow opens a different browser tab, allowing users to drag and drop an STL file directly. This approach offers a higher level of integration but may be subject to change or removal in future releases.
• Desktop workflowDeprecated : When the desktop option is selected, RayWare will automatically launch upon processing an .ocm file. From there, the standard SprintRay print workflow can be followed. This workflow is deprecated, and only works with the Pro 55 S machine.

Production with VHF

VHF DentalCAM v8 can be configured to use a chairside workflow for an improved integration. To setup this workflow follow these steps inside DentalCAM8:

1. Go to the settings tab
2. Disable the manual import of STL files option
3. Enable the automatic import of STL files option
4. Enable Activate ChairsideCAM
5. Press the Apply button to save the configuration

⚠️ Note: If you change the path to the STL import folder in DentalCAM, you must also update its value in the Circle OneClick Manufacturing configuration (in the "Milling Software Settings" tab of the configuration window).

Production with Rapid Shape

By default, Circle OneOlick Manufacturing saves processed STL files to the Rapid Shape Print Studio working directory to ensure smooth integration with Rapid Shape. If the Print Studio's working directory cannot be found, Circle OneClick Manufacturing will instead place the case in its own data directory, open it in the file explorer, and alert the user to load the case manually.

Configuration File

For advanced users or automated deployments, Circle OneClick Manufacturing settings can be configured directly through a JSON configuration file.

File Location

The configuration file is stored at %APPDATA%\Roaming\Circle Dental\OneClick Manufacturing\config.json

Configuration Schema

{
  "asiga_exe_path": String,
  "vhf_exe_path":  String,
  "ag_exe_path":  String,
  "rayware_exe_path":  String,
  "z3d_exe_path":  String,
  "roland_exe_path":  String,
  "rapidshape_exe_path": String,
  "formlabs_exe_path": String,
  "custom_command_template": String,
  "sprintray_execution_type": Enum("RayWareDesktop", "RayWareWebAppStable", "RayWareWebAppExperimental"),
  "file_open_behavior": Enum("LaunchManufacturing", "UserDialog", "OpenExplorer"),
  "user_language" : Enum("English", "French"),
  "delete_processed_ocm_files": bool
}

Configuration File behavior

• Invalid Configurations: If the specified configuration contains invalid fields, it will automatically be overwritten with the default configuration
• Missing entries: Populated with system defaults
• Validation: Performed on application startup or when configured using the Configuration Panel

Custom Command Configuration

The custom command template system, located in the Advanced Configuration section in the GUI, allows the user to configure external applications to be called with dynamically generated file paths based on case data.

Basic Format

"\pathToCustomApp\customApp.exe" -s {stl} -p {pts}

Components Breakdown

Executable path (Mandatory)

• Format: "\pathToCustomApp\customApp.exe"
• Must be the first element in the template
• Must be enclosed in double quotes ("")
• Contains the absolute path to the executable file

Command Line Arguments

• Format: Everything after the executable path
• Examples: -s {stl} -p {pts}, --batch --stl_files {stl}
• Treated as command line arguments
• Can include flags, options and file placeholders

File Extension Placeholders

• Format: {extension} (curly braces around file extension)
• Function: Automatically replaced with corresponding file path from case_id folder

Examples

Considering the following file structure:

case_id\
├── example.stl
├── example.pts
└── example.constructioninfo

The following templates will be interpreted as such:

• "C:\Program Files\Publisher\program.exe" {constructioninfo} -> C:\Program Files\Publisher\program.exe case_id\example.constructioninfo
• "C:\Program Files\Publisher\program.exe" -s {stl} -p {pts} --verbose -> C:\Program Files\Publisher\program.exe -s case_id\example.stl -p case_iddirectory\example.pts --verbose