Program Synchronization¶

Synchronize robot programs between C-Gate and a local working directory with the C-Gate Desktop Companion.

Introduction¶

Legacy WebDAV Workflow Deprecated

The previous network drive and WebDAV-based workflow is deprecated and should no longer be used. Microsoft is gradually removing WebDAV support from Windows, so program synchronization is now handled by the C-Gate Desktop Companion.

The Desktop Companion synchronizes robot programs in both directions:

C-Gate to the local working directory
Local working directory to C-Gate

For synchronization to work, the robot must be able to actively access C-Gate.

At a Glance

Install the Desktop Companion with the MSI installer.
Configure robot access to C-Gate (URL and token).
Enter the C-Gate Hub address in the Desktop Companion and log in.
Synchronization starts automatically after login.

Requirements¶

C-Gate module: Operation Module (C-Gate.OP)
Robot option: Program Management with C-Gate
QIROX software version: QS2.12 or newer
C-Gate IoT Hub and Connector with robots connected
C-Gate Desktop Companion for Windows

Robot Connection¶

For robot-side communication, the C-Gate URL and token should point to the C-Gate IoT Connector.

In most setups, use the connector IP address as URL:

http://{ConnectorIP}

In the Server area of the robot user interface, configure the following fields:

Field	Description	Example
C-Gate URL	HTTP address that the robot uses to reach the C-Gate IoT Connector. HTTPS is currently not supported for this robot-side setting.	`http://{ConnectorIP}`
Token	Device-specific token for authentication for this robot connection. The corresponding token is shown on the IoT Connector web interface in the device view. If the connector is already connected to the C-Gate IoT Hub, the same token is also available in the C-Gate Hub device view.	IoT Connector web interface -> device view

After configuration, verify the connection from the robot's archive network access. No error should appear, and program transfer should be possible.

For detailed connection errors, check the robot operation logbook.

Troubleshooting robot connection

Confirm that the robot can reach the configured C-Gate URL over the network.
Check that the configured token belongs to the same robot device.
Review the robot operation logbook for detailed error messages.
Use the IoT Connector setup wizard and network configuration simulator to validate and troubleshoot the robot connection.

C-Gate Desktop Companion¶

Install the Desktop Companion¶

The C-Gate Desktop Companion is provided as an MSI installer.

Run the MSI installer.
Complete the setup wizard.
Start the C-Gate Desktop Companion.

Enter the C-Gate Hub server address in the application (for example, http://cgate.my-company.com).
Save your settings.
The app redirects you to the C-Gate login page inside the app.
Log in with your C-Gate account.
After login, the app connects and starts synchronization automatically.

Working directory (CLOOSDAT)

The Desktop Companion synchronizes programs to the directory defined by the CLOOSDAT environment variable.

If Carola EDI is already installed, this variable is already set to:

C:\ProgramData\Cloos Schweisstechnik\DATA

If you want to use a different folder, set CLOOSDAT to a directory of your choice as a system environment variable.

Synchronization Behavior¶

Synchronization works in both directions.
Notifications are shown when files are synchronized.
The app synchronizes only robots that have an Operation Module license on C-Gate.
Program folders of older robots that are not connected and not licensed on C-Gate are not modified in the working directory.
Those older robots can still be synchronized by Carola itself through the legacy LANCOM interface.

Application Settings¶

Available options:

Autostart
Start minimized

If both options are enabled, the app starts with Windows and is visible only as a tray icon. No main window opens.

Tray Behavior¶

Closing the main window does not stop the application. It minimizes to the tray icon, which remains available at all times.

This behavior is independent of the Autostart and Start minimized settings.

Migration from Carola EDI to C-Gate Program Management¶

This section describes typical migration paths from legacy Carola EDI program management to C-Gate program management.

LANCOM Deprecation

The LANCOM protocol used by legacy Carola EDI robot synchronization is deprecated for newer robots and is planned to be removed in QS 2.18.

Legacy Carola EDI Program Management¶

In legacy setups, one central PC in or near the machine network typically runs Carola EDI and synchronizes robot programs via LANCOM.

Common operating models:

Users work directly on the central Carola EDI PC
Users connect by remote desktop to that PC
The central PC shares the Carola EDI data directory as a network drive, and users work from personal PCs using Carola EDI or RoboPlan against that shared folder

In this model, robot synchronization is still performed by the central Carola EDI PC.

Hybrid Program Management (Legacy + C-Gate)¶

Hybrid program management is useful when older robots cannot run the newer robot software yet.

In this scenario:

Legacy robots continue to synchronize via Carola EDI and LANCOM
Newer robots synchronize via C-Gate program management
Both approaches run in parallel during migration

In many installations, the same central Carola EDI PC is connected to both machine and company networks and already provides the shared working directory.

Install C-Gate Desktop Companion on that central PC and use the same CLOOSDAT working directory. This allows newer robot programs from C-Gate and legacy robot programs from LANCOM to be available together on the existing network share.

Result: users on personal client PCs can keep their current workflow with minimal or no process changes.

Full migration option

To avoid hybrid operation long-term, legacy robots can be retrofitted with newer controller hardware and equipped with a C-Gate IoT Connector. For retrofit planning, contact retrofit@cloos.de.