Anybus CompactCom 40 EtherNet/IP User Manual

Server Side Include (SSI) 42
Doc.Id. HMSI-27-212
Anybus CompactCom 40 EtherNet/IP
Doc.Rev. 1.5
6.3.9 printf()
This function returns a formatted string which may contain data from the Anybus module and/or ap-
plication. The formatting syntax used is similar to that of the standard C-function printf().
The function accepts a template string containing zero or more formatting tags, followed by a number
of arguments. Each formatting tag corresponds to a single argument, and determines how that argument
shall be converted to human readable form.
Syntax:
<?--#exec cmd_argument='printf("template" [, argument1, ..., argumentN])'-->
Default Output:
Example:
See also...
- “ABCCMessage()” on page 46
- “Example (Get_Attribute):” on page 48
Scenario Default Output
Success (printf() result)
ABCCMessage error ABCCMessage error string ( “Errors” on page 49)
template- Template which determines how the arguments shall be represented. May
contain any number of formatting tags which are substituted by subse-
quent arguments and formatted as requested. The number of format tags
must match the number of arguments; if not, the result is undefined.
Formatting tags are written as follows:
%[Flags][Width][.Precision][Modifier]type
See also...
• “Formatting Tags” on page 43
argument- Source arguments; optional parameters which specify the actual source of
the data that shall be inserted in the template string. The number of argu-
ments must match the number of formatting tags; if not, the result is un-
defined.
At the time of writing, the only allowed argument is ABCCMessage().
See also...
• “ABCCMessage()” on page 46

Anybus CompactCom 40 EtherNet/IP Specifications

General

Communication Protocol	EtherNet/IP
Form Factor	Compact
Protocol	Ethernet/IP
Data Rates	10/100 Mbps
Connector	RJ45
Certifications	CE, UL

Summary

Chapter 1 About the Anybus CompactCom 40 EtherNet/IP

1.2 Features

Lists the key features and functionalities offered by the module.

Chapter 2 Basic Operation

2.2 Device Customization

Details how to configure device identity, EDS files, and other settings.

2.3 Communication Settings

Explains TCP/IP and physical link settings for network communication.

2.4 Diagnostics

Describes how to access and interpret diagnostic information from the module.

2.5 Network Data Exchange

Covers application data, process data, and data type translation.

Chapter 4 Web Server

4.3 Server Configuration

Covers settings for the web server, including root directory and content types.

Chapter 6 Server Side Include (SSI)

6.3 Command Functions

Details various SSI command functions for interacting with the module.

Chapter 8 CIP Objects

8.3 Identity Object (01h)

Provides identification and general information about the module.

8.5 Assembly Object (04h)

Holds Process Data sent/received by the host application via static assemblies.

8.6 Connection Manager (06h)

Used for establishing and managing connections across subnets.

8.7 Parameter Object (0Fh)

Provides an interface to the module's configuration parameters.

8.12 ADI Object (A2h)

Maps instances in the Application Data Object to EtherNet/IP.

8.13 Port Object (F4h)

8.14 TCP/IP Interface Object (F5h)

Configures the TCP/IP network interface settings.

8.15 Ethernet Link Object (F6h)

Maintains link counters and status for IEEE 802.3 communications.

Chapter 9 Anybus Module Objects

9.3 Diagnostic Object (02h)

9.5 Network Configuration Object (04h)

Holds network-specific configuration parameters settable by the end user.

Chapter 10 Host Application Objects

10.2 Functional Safety Host Object (E8h)

Specifies safety settings and is mandatory if Functional Safety is supported.

10.3 CIP Identity Host Object (EDh)

10.2 EtherNet/IP Host Object (F8h)

Implements EtherNet/IP specific features in the host application.

10.3 Ethernet Host Object (F9h)

Implements Ethernet features in the host application.