The PICANOL BICOM OPC UA server offers an OPC UA interface for communication with various PICANOL machines, including those built on the “Plus” and “BlueBox” platforms. This server exposes a comprehensive set of parameters relevant for monitoring in textile production. These parameters include real-time information such as the produced length of the cloth, preselected length, density, pick counters, design patterns, and other essential data points.


version: v2.7.0

published: Jun 03, 2024

Download 64-bit installer for Windows - 1.54 MB

PICANOL machines

New PICANOL machine types are standard equipped with an RJ45 Ethernet.

Machines built on the “Plus” platform can be connected to Ethernet in case they are equipped with interactive display (color display). The placement of the Ethernet connection varies based on the type of interactive display (ID1, ID2 or ID3). However, “Plus” machines equipped with a keyboard display (black & white display) do not offer Ethernet connection capabilities.

Machines built on the “BlueBox” platform are always equipped with an Ethernet. connection.

The list below outlines the platform and interactive display type for various machine types that support Ethernet connectivity:

  • OmniPlus Plus - ID1
  • GamMax made before July 2005 Plus - ID1
  • GamMax made after July 2005 Plus - ID2
  • OmniPlus800 made before April 2008 Plus - ID2
  • OmniPlus800 made after April 2008 Plus - ID3
  • TerryPlus800 Plus - ID3
  • OptiMax Plus - ID3
  • GTMax-i Plus - ID3
  • OptiMax-i made before April 2016 Plus - ID3
  • OptiMax-i made after April 2016 - BlueBox
  • TerryMax-i - BlueBox
  • OmniPlus Summum - BlueBox
  • TerryPlus Summum - BlueBox
  • GTMax-i 3.0 - BlueBox

Required minimum software version for Ethernet BICOM protocol:

  • For machines that are based on the “Plus” platform: release 84.8
  • For machines that are based on the “BlueBox” platform: release 27.2

To enable Ethernet communication with the machine, ensure that the “Bicom” item in the MID (Machine Identification Device) is configured to “Ethernet.” Refer to the machine’s documentation for guidance on how to verify and adjust this setting.


Installation process is very simple and straight forward. Installer copies the following files to “%PROGRAMFILES%\X-tensive\DPA.UA\bicom\“ directory:

Firewall exception is added for executable.

If there is no certificate or private key for OPC UA server default instance, a self-signed certificate as well as private key are generated and placed to “instances\default\“ subfolder.

Installer is a simple console application that requires no user interaction or parameters. All output is sent to stdout and stderr. It is fine to run installer under SSH session. Here is a typical output:

dpa installer, 64-bit
Destination: C:\Program Files\X-tensive\DPA.UA\bicom\
Discovering services for ""...
Discovering services for ""...
Checking processes for ""...
Checking processes for ""...
Copying ""... ok
Copying ""... ok
Generating default certificate...
  default certificate exists already. Will skip.
Will configure firewall...
  exception for ""... ok
installation SUCCEEDED!

Update of running services

In case when a previous version was already installed and OPC UA server instances are up and running as Windows services, the installer will do update correctly. First, all running services of OPC UA server are shutdown gracefully. Old binaries are replaced with a new version. Finally, all previously running instances are started again.

Update of interactively running processes

In case when OPC UA server runs as interactive console process, installer kills this process before installation to release any locks of old binaries, otherwise installation and update of the binaries would fail. The installer does not attempt to restart interactive processes after binaries update.

Command line arguments


PICANOL device ip and port (optionally), like “” or “”.


PICANOL device serial number, like “123456”. If the serial number is set improperly, the PICANOL device will reject any communication attempts.


Optional. Specifies instance name for non-default instance. Instances are explained here.


Do not use certificates. Indicates that OPC UA server should not expose secured endpoints. Can optionally be applied only to OPC UA servers running interactively. Can not be applied to OPC UA servers running as Windows Services.


Optional. Specifies TCP port for OPC UA server. Default is 4840.

Running in Console mode

The OPC UA server can run interactively in console mode. For instance: /dev: /sn:123456

Ctrl+C gracefully shuts down the server.

Running as Windows Service

It’s very easy to run OPC UA server as Windows service. is used to list, register and unregister Windows Services for PICANOL BICOM OPC UA servers. For example, to register OPC UA server as a service: /install /dev: /sn:123456

If you need to connect several PICANOL devices, named instances must be used. Instances are explained here. The instance name is specified via the command line argument “instance”. Take into account, each instance must have unique tcp port to expose OPC UA endpoints: /install /dev: /sn:654321 /instance:dev2 /port:4841

To list all installed instances: /list

Typical output:

  instance: (default)
  port: 4840
  sn: 123456
  start type: auto
  status: stopped
  instance: dev2
  port: 4841
  sn: 654321
  start type: auto
  status: stopped

Finally, to start the (default) instance:


Or to start named instance “dev2”:

net start DPAOPCUA.BICOM.dev2

To unregister the Windows Service: /uninstall /instance:dev2

Take into account, the service is not stopped automatically when unregistering. It must be stopped with “net stop” command before.

Address space

PICANOL BICOM OPC UA server provides namespace.


Windows Service fails to start

In case OPC UA server fails to start as Windows Service, run it in Console mode with exactly the same command line arguments to check console output. Normally, all diagnostic messages are sent to stdout and stderr. For instance, when OPC UA server fails to read the certificate or the private key:

[2023-10-18 11:07:13.019 (UTC+0300)] fatal/server       Could not load certificate storage.

In that case ensure that .cert and .key files exist and are located according to Instances directory structure.

An invalid or corrupted alias.json file may cause service to fail to start:

[2023-10-18 11:08:54.418 (UTC+0300)] fatal/server       Could not load alias json.

In that case ensure that alias.json is valid and its content respects the demands described here. Take into account that empty alias.json file is considered as invalid. If aliases are not used, just remove alias.json.


If the license is not installed or if the license is not valid, for example, an expired TRIAL license, then the OPC UA server will function for 1 hour after starting the process. After the hour has elapsed, the OPC UA server will return a BADLICENSENOTAVAILABLE or BADLICENSEEXPIRED error on requests to read and write data, except for system objects and system variables of OPC UA server.

The variable “Objects/Server/Instance/LicenseKey” allows to read the loaded license and its status. Next, the license status can be checked with the command line utility target <OpcServerIp>

BICOM communication

To troubleshoot any BICOM communication issues, please, refer to “Objects/BICOM/link” variable. It provides detailed information about the status of BICOM TCP transactions as well as any errors detected, including the rich set of counters for various types of errors.