General informations

The runnability of a COMSOL device requires a loadable firmware (LFW) as well as a suitable configuration by default. the first is provided in a firmware file (.nxf file). Depending on the procedure described below, the configuration in the form of one or more database files (.nxd file) is also required. For the driver to be able to handle the files, they are stored in a defined file directory. For this purpose, a root directory is created when the driver is installed:

• Windows: C:\Program Files\cifX Device Driver
• Linux: /opt/cifx/

Below the root directory, the folder structure is continued according to a specific scheme (see figure). For each device, a sub-directory is created, which depends either on the device ID and serial number or on the slot number of the device. The first requires the existence of a slot selection switch. If this is set greater than "0", the procedure follows according to the "slot number" method:

Image Modified

When starting the device, the driver automatically downloads the files to the target device, if there is no file or if the present files differs from the ones stored in the subdirectory. Replacing the file in the subdirectory and rebooting the device will therefore replace the files on the target device.

When using Sycon.NET on a Windows system, the file management will automatically take place via the respective download functions. A manual replacement of the files is possible, preferably via the cifx setup tool. However, this procedure is rather uncommon. On other operating systems like Linux things look a little different. Tools like Sycon.NET are not available for this purpose. The "manual" moving of the files normal procedure here.

TCP-Server

Sycon.NET can also be used outside of Windows, by using a TCP server. This allows the device to be remotely configured. It requires, that the target device has been recognized by the oposite operating system (Linux) and that the two computers can reach each other on the network. With this method, the TCP server and Sycon.NET automatically take over the file storage management, making them the least error-prone.

Target-Host Application

All driver packages of all operating systems contain sources for a TCP server application. It can be translated and started via an appropriate build environment. The application requires write access to the driver directory. After starting the application and successfully searching for installed devices, the current IP address of the TCP server is displayed.

Image Modified

Sycon.NET - TCP-Connector

The displayed IP address can now be used to connect Sycon.NET to the remote device via the TCP server. In the first step, if necessary, the proper driver has to be activated. In the dialog "Driver", which can be found in the Navigation Area, the "netX Driver" has to be activated. The network driver should be installed together with Sycon.NET.

Image Modified

In the dialog "netX Driver", the TCP connector can be activated and configured using the tab "TCP Connection". The dialog allows to create different profiles (IP_RANGE #), which can be changed as required. With the "+" button a profile can be created, with "x" it can be removed. After selecting an IP range, configuration parameters be entered successfully.

Image Modified

After saving the parameters, the device search should return results and these should be listed in the "Device Assigment" dialog. If the CifX Device Driver is still activated (see "Driver" dialog), local installed devices may also be displayed. Remote devices differ from local devices through a different Access Path. It also contains the IP address of the TCP server where the remote device is installed. After selecting the device, the further configuration procedure is identical.

Note: The selection behind "Device selection" is only a display filter. It should help, hiding uninteresting devices. If the desired device is not initially listed, changing the filter to "all" can help.

Image Modified

Configuration-Export - copy manually

As an alternative to the TCP server, the required files can also be moved / copied manually to the required subdirectories. The firmware file (.nxf) is static and ready to use. The configuration file (.nxd) must be generated first. Sycon.NET offers an export function for this purpose, which can be found under "Additional functions -> Export -> DBM / nxd ...". After the export, the file can be transferred to the Target-PC and stored in the channel # 0 folder of the device.

Depending on the protocol and role (master / slave), multiple files may be created by the export. You will receive a prefix in the file name that corresponds to the file name field in the export dialog. The main file must be named in "config.nxd". All other files have to be cleaned by the just mentioned prefix until the last "_". All files must be stored in the same way as the main file in the Channel # 0 directory.

Configuration via application

A complete renunciation of Sycon.NET is possible with an applicative configuration via the acyclic interface of the respective protocol API. Depending on the communication protocol used, it gets very complex and requires profound knowledge of the used protocol. If possible, this method should therefore not be chosen as a preferred procedure.

The application-specific configuration does not generate a configuration file. This only requires copying or storing the firmware file. The parameters are transferred directly to the device and processed. If the device does not have persistent memory (depending on the device type), configuration is required each time the device is restarted. The exact configuration procedure is documented in the respective protocol API documentation