All our downloads from our Clouds

• Softing License Manager V4.63 (Windows)
• Softing License Manager V4.63 (Container for Linux)
• Softing License Manager | Checksums V4.63
• Preconfigured symbol files for SINUMERIK 840D
• edgeConnector 840D | DockerHub
• edgeConnector 840D | Microsoft Azure Marketplace
• Latest dataFEED Exporter Version

• Getting started with CNC Machine Data

Softing dataFEED edgeConnector 840D is a containerized SINUMERIK 840D SolutionLine and PowerLine connectivity module adding OPC UA Server and MQTT Publisher functionality. The software can run as IoT Edge Module. After the deployment, it is possible to configure Southbound and Northbound communication via local GUI or REST interface.

For southbound communication it is possible to connect up to 20 SINUMERIK 840D SolutionLine and PowerLine controllers. The Namespace configuration is pre-configured and can be extended via STEP7/TIA Portal or .awl files.

The northbound communication runs with standardized OPC UA communication for data integration into management systems like ERP, MES or SCADA or for data exchange with other docker containers like Microsoft OPC Publisher for cloud scenarios. In addition MQTT is available as protocol to connect MQTT Broker in local or cloud environments.

The application supports security standards like SSL/TLS, X.509 certificates, authentication and data encryption. The container runs for 72h in demo mode. Fully activate the application via BYOL from Softing. This also requires the installation of the Softing floating license server available for Windows/Linux.

After the Docker image has been pulled, a Docker container can be started. The webserver and OPC UA Server of the module have to be exposed on the host machine if dataFEED edgeConnector 840D shall be accessed from outside the dockerized environment.

To start dataFEED edgeConnector 840D with the default ports mapped 1:1 to the host machine:

docker container run -p 443:443 -p 4897:4897 softingindustrial/edgeconnector-840d

Softing licenseServer

Softing licenseServer is used to host network software licenses (also called floating licenses or shared licenses) that are installed locally on an individual users’ machine. The network licenses can be shared among many users and/or applications.

Softing licenseServer fulfills requests to run a network application if the required license is available. When the network license is released (for example, a user closes the application), the license is moved to the license server’s available license pool and is made available for other checkout requests.

The license server is used by several Softing products like the edgeConnector or plantPerfect product families.

Please read the user guide of the licenseServer for install and usage instructions. It is available as download on the Softing product pages using the licenseServer.

Installation

Download the docker image using the following command:

docker pull softingindustrial/license-server

Use the following commands to create and configure Docker container:

mkdir -p /var/lib/license-server
mkdir -p /var/lib/license-server/licenses
mkdir -p /var/lib/license-server/config
mkdir -p /var/lib/license-server/users
docker create --name license-server -p 8000:8000 -p 6200:6200 -v /var/lib/licenseserver/licenses:/root/.x-formation -v /var/lib/license-server/users:/root/sflm/users -v /var/lib/license-server/config:/root/sflm/config --restart=always softingindustrial/license-server
docker start license-server

The following ports are used by the license server:

These ports are mapped in the docker create call above 1:1 to the ports of the host system. Of course, you can map them to different ports on the host system by changing the first number on the -p option (example: -p 8400:8000).

To disable HTTPS, use the docker create command without a port mapping for port 8000.

Note: You will need access to the Web server to add licenses.

These following volumes are used by the license server:

The directory /var/lib/license-server is used to persist the configuration of the license server container. Of course, you can store it in a different folder on the host system by changing the first folder on the -v option (example: -v /home/xxx/ls:/root/.x-formation).

The option –restart=always will start the container on the startup of the system or restart it on failure.

Start the container with the following command:

docker start license-server

Stop the container with the following command:

docker stop license-server

Remove the container with the following command:

docker rm -f license-server