Anybus® CompactCom™ 40 - EtherNet/IP IIoT Secure

Appendix B. Compatibility to Standard Anybus CompactCom 40

The Anybus CompactCom 40 EtherNet/IP IIoT Secure is not compatible to standard Anybus CompactCom. The differences are summarized in the table below.

Issue

Description

User account configuration

“web_accs.cfg” and “ftp.cfg” files are not used for account configuration. User accounts are given roles and are configured using the internal web pages. They can also be configured using the JSON API. For more information see Initial Setup and Account Configuration.

HTTP(S) configuration

Changes are made to the “http.cfg” configuration file.

  • Web root cannot be configured. All URLs is from system root, but accounts have different access rights.

  • Access rights are controlled per role and are configured in this file.

  • The index page must be configured.

For more information see Secure Web Server (HTTPS).

File transfer protocol

File transfer protocol FTP changed to WebDAV

SSI

SSI removed.

JSON functions URL

The URLs to JSON functions is changed, to make it possible to configure access rights for each JSON API. For more information see JSON.

JSON function protection

For standard Anybus CompactCom 40 all JSON functions are protected by the root “web_accs.cfg” file. For Anybus CompactCom Security modules, JSON functions are instead protected independently in the same way as protecting file system resources. For more information see Secure Web Server (HTTPS).

OPC UA

File format changed for opcua.cfg.

In this section: