Web Interface - Anybus CompactCom 40 Network Manual

Basic Operation
Anybus Data Type
UINT64
BITS8
BITS16
BITS32
OCTET
BITS1-7
PAD0-8
PAD9-16
BOOL1
3.6

Web Interface

The web interface can be fully customized to suit a particular application. Dynamic content can
be created by means of JSON and SSI scripting. Data and web pages are stored in a FLASH-based
file system, which can be accessed using any standard FTP-client.
See also...
• File System, p. 15
• FTP Server, p. 22
• Web Server, p. 24
• Server Side Include (SSI), p. 33
• JSON, p. 53
3.7 E-mail Client
The built-in e-mail client enables the host application to send e-mail messages stored in the file
system, or defined directly within the SMTP Client Object (09h). Messages are scanned for SSI
content, which means it's possible to embed dynamic information from the file system.
See also...
• File System, p. 15
3.8 Modular Device Functionality
Modular devices consist of a backplane with a certain number of slots. The first slot is occupied
by the "coupler" which contains the Anybus CompactCom module. All other slots may be empty
or occupied by modules.
When mapping ADIs to process data the application shall map the process data of each module
in slot order.
A list of modules in a Modular Device is available to the EtherNet/IP network master by a
request to the CIP Identity object.
See also ...
• "Modular Device Object (ECh)" (see Anybus CompactCom 40 Software Design Guide)
• Identity Object (01h), p. 98
Anybus CompactCom 40 EtherNet/IP IIoT Network Guide
CIP Data Type Comments
ULINT
BYTE Each ADI element of this type occupies one byte.
WORD
Each ADI element of this type occupies two bytes.
DWORD Each ADI element of this type occupies four bytes.
USINT
BYTE
Bit fields of size 1 - 7
BYTE
Bit fields of size 0 - 8 used for padding
BYTE Bit fields of size 9 - 16 used for padding
BOOL
(CIP object)
14 (244)
SCM-1202–069 1.9 en-US