Skip to main content

CODESYS V3 / SQL4CODESYSV3 Version 5

Requirements​

Version 5 is functionally backward compatible with version 4. Starting with this version, encrypted communication with the connector (from V5.1.0.0) is now possible. The following chapters only deal with this (new) aspect of communication; for standard functions, please refer to the existing chapters. The configuration is shown below using a CODESYS RTE.

Hardware-architecture and SSL certificates​

  • PLC IP-Address: 10.100.100.215

  • SQL4automation Connector IP-Address: 10.100.100.211

CLIENT215

openssl genrsa -out client215.key 2048

openssl req -new -key client215.key -out client215.csr -subj "/C=CH/ST=Bern/L=Lyssach/CN=10.100.100.215/O=Inasoft"

openssl x509 -req -in client215.csr -CA rootCA.pem -CAkey rootCA.key -CAcreateserial -out client215.crt -days 1825 -sha256

openssl pkcs12 -export -out client215.p12 -inkey client215.key -in client215.crt

--> PWD: SSLtest

SERVER211

openssl genrsa -out server211.key 2048

openssl req -new -key server211.key -out server211.csr -subj "/C=CH/ST=Bern/L=Lyssach/CN=10.100.100.211/O=Inasoft"

openssl x509 -req -in server211.csr -CA rootCA.pem -CAkey rootCA.key -CAcreateserial -out server211.crt -days 1825 -sha256

openssl pkcs12 -export -out server211.p12 -inkey server211.key -in server211.crt

--> PWD: SSLtest

ROOT CA

openssl genrsa -out rootCA.key 2048

openssl req -x509 -new -nodes -key rootCA.key -sha256 -days 1825 -out rootCA.pem -subj "/C=CH/ST=Bern/L=Lyssach/CN=SQL4automation/O=Inasoft"

openssl pkcs12 -export -out rootCA.p12 -inkey rootCA.key -in rootCA.pem

--> PWD: SSLtest

Commissioning TLS encryption​

Before commissioning, the certificates for the SQL4automation Connector must be copied to the corresponding paths.

  • Path “C:\ProgramData\SQL4automation\certs\CA” 🡪 Copy the contents of RootCA to the file

  • Path “C:\ProgramData\SQL4automation\certs\S4AConnector” 🡪 The server certificates are copied to this location.

  • Path “C:\ProgramData\SQL4automation\certs\S4AQueryTool” 🡪 This is where the certificates are located for testing with the query tool.

After copying the RootCA, the SQL4automation Connector service must be restarted before operation.

In the next step, it is recommended to establish the connection between SQL4automation and the controller WITHOUT TLS encryption.

Only when communication works without encryption do we recommend activating encryption. Please note that the system time must be checked at this point and adjusted if necessary!

Passphrase: SSLtest

In the programming environment, select “View” 🡪 “Security Screen” and connect to the control system.

Select the “Devices” 🡪 “Own Certificates” area.

Select the “Devices” 🡪 “Own Certificates” area

Then click the “Download” button and select the client certificate.Select the “Devices” 🡪 “Own Certificates” area

Pwd: SSLtest

Pwd: SSLtest

Select the “Devices” 🡪 “Trusted Certificates” section.

Then click the “Download” button and select the server certificate.

Then click the “Download” button and select the server certificate

When calling SQL4Codesys, activate encryption and reference the corresponding certificates by name.

  • xTlsEnable: TRUE

  • sTlsCertificateCommonName: <IP-Address of PLC>

  • sTlsUseCase: SQL4automation

  • sTlsVersion: 1.3

Download the code changes online and run a test query.