Anybus CompactCom 40 EtherCAT Installation and maintenance instructions

Anybus®CompactCom™40
EtherCAT®
NETWORK GUIDE
SCM-1202-034 1.1 ENGLISH

Important User Information
Liability
Every care has been taken in the preparation of this document. Please inform HMS Industrial Networks AB of any
inaccuracies or omissions. The data and illustrations found in this document are not binding. We, HMS Industrial
Networks AB, reserve the right to modify our products in line with our policy of continuous product development.
The information in this document is subject to change without notice and should not be considered as a commit-
ment by HMS Industrial Networks AB. HMS Industrial Networks AB assumes no responsibility for any errors that
may appear in this document.
There are many applications of this product. Those responsible for the use of this device must ensure that all the
necessary steps have been taken to verify that the applications meet all performance and safety requirements in-
cluding any applicable laws, regulations, codes, and standards.
HMS Industrial Networks AB will under no circumstances assume liability or responsibility for any problems that
may arise as a result from the use of undocumented features, timing, or functional side effects found outside the
documented scope of this product. The effects caused by any direct or indirect use of such aspects of the product
are undefined, and may include e.g. compatibility issues and stability issues.
The examples and illustrations in this document are included solely for illustrative purposes. Because of the many
variables and requirements associated with any particular implementation, HMS Industrial Networks AB cannot as-
sume responsibility for actual use based on these examples and illustrations.
Intellectual Property Rights
HMS Industrial Networks AB has intellectual property rights relating to technology embodied in the product de-
scribed in this document. These intellectual property rights may include patents and pending patent applications in
the USA and other countries.

Anybus®CompactCom™40 EtherCAT®Network Guide SCM-1202-034 1.1
Table of Contents Page
1 Preface ............................................................................................................................... 5
1.1 About this document ......................................................................................................5
1.2 Related Documents .......................................................................................................5
1.3 Document History ..........................................................................................................5
1.4 Conventions ..................................................................................................................5
1.5 Document Specific Conventions......................................................................................6
1.6 Trademark Information ...................................................................................................6
2 About the Anybus CompactCom 40 EtherCAT........................................................ 7
2.1 General.........................................................................................................................7
2.2 Features .......................................................................................................................8
3 Basic Operation............................................................................................................... 9
3.1 General Information .......................................................................................................9
3.2 EtherCAT Implementation Details..................................................................................12
3.3 CANopen over EtherCAT Implementation Details ...........................................................14
3.4 Data exchange ............................................................................................................15
3.5 File System .................................................................................................................16
3.6 Communication Settings in Stand Alone Shift Register Mode ..........................................18
3.7 Network Reset Handling...............................................................................................19
3.8 Configured Station Alias (Node Address) .......................................................................19
3.9 Device ID ....................................................................................................................19
3.10 Modular Device Profile .................................................................................................20
4 Object Dictionary (CANopen over EtherCAT) ........................................................ 21
4.1 Standard Objects .........................................................................................................21
4.2 Manufacturer and Profile Specific Objects......................................................................26
5 Anybus Module Objects .............................................................................................. 32
5.1 General Information .....................................................................................................32
5.2 Anybus Object (01h) ....................................................................................................33
5.3 Diagnostic Object (02h) ................................................................................................34
5.4 Network Object (03h) ...................................................................................................36
5.5 Network Configuration Object (04h)...............................................................................38
5.6 Socket Interface Object (07h)........................................................................................43
5.7 SMTP Client Object (09h).............................................................................................60
5.8 Network Ethernet Object (0Ch) .....................................................................................65

Anybus®CompactCom™40 EtherCAT®Network Guide SCM-1202-034 1.1
Table of Contents
6 Host Application Objects ............................................................................................ 66
6.1 General Information .....................................................................................................66
6.2 Assembly Mapping Object (EBh)...................................................................................67
6.3 Sync Object (EEh) .......................................................................................................68
6.4 EtherCAT Object (F5h) .................................................................................................71
6.5 Ethernet Host Object (F9h) ...........................................................................................75
7 Web Server...................................................................................................................... 78
7.1 General Information .....................................................................................................78
7.2 Default Web Pages ......................................................................................................78
7.3 Server Configuration ....................................................................................................81
8 FTP Server ...................................................................................................................... 84
8.1 General Information .....................................................................................................84
8.2 User Accounts .............................................................................................................84
8.3 Session Example .........................................................................................................85
9 E-mail Client ................................................................................................................... 86
9.1 General Information .....................................................................................................86
9.2 How to Send E-mail Messages .....................................................................................86
10 Server Side Include (SSI) ............................................................................................ 87
10.1 General Information .....................................................................................................87
10.2 Include File..................................................................................................................87
10.3 Command Functions ....................................................................................................87
10.4 Argument Functions...................................................................................................102
10.5 SSI Output Configuration............................................................................................106
11 JSON...............................................................................................................................107
11.1 General Information ...................................................................................................107
11.2 JSON Objects............................................................................................................107
11.3 Example.................................................................................................................... 115
A Categorization of Functionality ............................................................................... 117
A.1 Basic......................................................................................................................... 117
A.2 Extended................................................................................................................... 117
B Implementation Details.............................................................................................. 118
B.1 SUP-bit Definition ...................................................................................................... 118
B.2 Anybus State Machine ............................................................................................... 118
B.3 Application Watchdog Timeout Handling ...................................................................... 118

Anybus®CompactCom™40 EtherCAT®Network Guide SCM-1202-034 1.1
Table of Contents
C Technical Specification ............................................................................................. 119
C.1 Front View................................................................................................................. 119
C.2 Functional Earth (FE) Requirements............................................................................ 121
C.3 Power Supply ............................................................................................................121
C.4 Environmental Specification........................................................................................122
C.5 EMC Compliance.......................................................................................................122
D Timing & Performance ...............................................................................................123
D.1 General Information ...................................................................................................123
D.2 Internal Timing...........................................................................................................123
E Secure HICP (Secure Host IP Configuration Protocol) .....................................125
E.1 General.....................................................................................................................125
E.2 Operation .................................................................................................................. 125
F Copyright Notices .......................................................................................................126

This page intentionally left blank

Preface 5 (136)
1 Preface
1.1 About this document
This document is intended to provide a good understanding of the functionality offered by the
Anybus CompactCom 40 EtherCAT. The document describes the features that are specific to
Anybus CompactCom 40 EtherCAT. For general information regarding Anybus CompactCom
40, consult the Anybus CompactCom 40 design guides.
The reader of this document is expected to be familiar with high level software design and com-
munication systems in general. The information in this network guide should normally be suffi-
cient to implement a design. However if advanced EtherCAT specific functionality is to be used,
in-depth knowledge of EtherCAT networking internals and/or information from the official Ether-
CAT specifications may be required. In such cases, the persons responsible for the implementa-
tion of this product should either obtain the EtherCAT specification to gain sufficient knowledge
or limit their implementation in such a way that this is not necessary.
For additional related documentation and file downloads, please visit the support website at
www.anybus.com/support.
1.2 Related Documents
Document Author Document ID
Anybus CompactCom 40 Software Design Guide HMS HMSI-216–125
Anybus CompactCom M40 Hardware Design Guide HMS HMSI-216–126
Anybus CompactCom B40 Design Guide HMS HMSI-27-230
Anybus CompactCom Host Application Implementation
Guide
HMS HMSI-27-334
IEC 61158-6 IEC
CiA Draft Standard 301 v4.02 CAN in Automation
1.3 Document History
Version Date Description
1.1 2017–01–19 FM to DOX, change of document number from HMSI-27-220 to SCM-
1202-027. Version numbering restarted.
M12 connectors added
Minor corrections
1.4 Conventions
Ordered lists are used for instructions that must be carried out in sequence:
1. First do this
2. Then do this
Unordered (bulleted) lists are used for:
• Itemized information
• Instructions that can be carried out in any order
...and for action-result type instructions:
• This action...
leads to this result
Anybus®CompactCom™40 EtherCAT®Network Guide SCM-1202-034 1.1

Preface 6 (136)
Bold typeface indicates interactive parts such as connectors and switches on the hardware, or
menus and buttons in a graphical user interface.
Monospaced text is used to indicate program code and other
kinds of data input/output such as configuration scripts.
This is a cross-reference within this document: Conventions, p. 5
This is an external link (URL): www.hms-networks.com
This is additional information which may facilitate installation and/or operation.
This instruction must be followed to avoid a risk of reduced functionality and/or
damage to the equipment, or to avoid a network security risk.
Caution
This instruction must be followed to avoid a risk of personal injury.
WARNING
This instruction must be followed to avoid a risk of death or serious injury.
1.5 Document Specific Conventions
• The terms “Anybus” or “module” refers to the Anybus CompactCom module.
• The terms “host” or “host application” refer to the device that hosts the Anybus.
• Hexadecimal values are written in the format NNNNh or 0xNNNN, where NNNN is the
hexadecimal value.
• A byte always consists of 8 bits.
• The terms “basic” and “extended” are used to classify objects, instances and attributes.
1.6 Trademark Information
Anybus®is a registered trademark of HMS Industrial Networks AB.
EtherCAT®is a registered trademark and patented technology, licensed by Beckhoff Automa-
tion GmbH, Germany.
All other trademarks are the property of their respective holders.
Anybus®CompactCom™40 EtherCAT®Network Guide SCM-1202-034 1.1

About the Anybus CompactCom 40 EtherCAT 7 (136)
2 About the Anybus CompactCom 40 EtherCAT
2.1 General
The Anybus CompactCom 40 EtherCAT communication module provides instant EtherCAT con-
formance tested connectivity via the patented Anybus CompactCom host interface. Any device
that supports this standard can take advantage of the features provided by the module, allowing
seamless network integration regardless of network type.
This product conforms to all aspects of the host interface for Anybus CompactCom 40 modules
defined in the Anybus CompactCom 40 Hardware and Software Design Guides, making it fully
interchangeable with any other device following that specification. Generally, no additional net-
work related software support is needed, however in order to be able to take full advantage of
advanced network specific functionality, a certain degree of dedicated software support may be
necessary.
Anybus®CompactCom™40 EtherCAT®Network Guide SCM-1202-034 1.1

About the Anybus CompactCom 40 EtherCAT 8 (136)
2.2 Features
• CANopen over EtherCAT (CoE)
• Support for Modular Device Profile
• Ethernet connectors or M12 connectors
• DS301 compliant
• Galvanically isolated bus electronics
• Network Identity customization
• EMCY support
• Up to 57343 ADIs can be accessed from the network as Manufacturer Specific Objects
and Device Profile Specific Objects (generic mode).
• Up to 16383 ADIs can be accessed form the network as Manufacturer Specific Objects
and Device Profile Specific Objects (modular device profile enabled)
• Up to 1486 bytes of fast cyclic I/O in each direction
• EtherCAT Slave Interface file provided by HMS
• Support for Sync0 functionality using distributed clocks
• Ethernet over EtherCAT (EoE)
• Web server with customizable content
• FTP server
• E-mail client
• Server Side Include (SSI) functionality
• JSON functionality
• File access over EtherCAT (FoE)
• Support for process data remap from the network
• Network cycle time down to 100 μs
• Possible to implement DS402 drive profile, Semi device profiles, and other device
profiles
If the TwinCAT 3, or a later version of 2.11, tool is used, the max amount of process data will be
1473 bytes, due to limitations in the tool.
Anybus®CompactCom™40 EtherCAT®Network Guide SCM-1202-034 1.1

Basic Operation 9 (136)
3 Basic Operation
3.1 General Information
3.1.1 Software Requirements
No additional network support code needs to be written in order to support the Anybus Com-
pactCom 40 EtherCAT, however due to the nature of the EtherCAT networking system, certain
restrictions must be taken into account:
• ADIs with instance numbers up to 57343 (DFFFh) can be accessed from the network. If
the Modular Device Profile is implemented and running, instance numbers are limited to
16383 (3FFFh).
• When mapping ADIs to process data, there is a limit of 1486 elements or 1486 bytes,
whichever comes first, that can be mapped in either direction.
• The flexible nature of the Anybus concept allows the application to modify the behavior
on EtherCAT in ways which contradict the generic EtherCAT Slave Information file or in
other ways voids network certification. Those responsible for the implementation of the
final product should ensure that their level of implementation matches their own require-
ments and policies regarding network certification and interoperability.
• The use of advanced EtherCAT-specific functionality may require in-depth knowledge in
EtherCAT networking internals and/or information from the official EtherCAT specifica-
tions. In such cases, those responsible for the implementation of the product should ei-
ther obtain the EtherCAT specification to gain sufficient knowledge or limit their
implementation is such a way that this is not necessary.
If the TwinCAT 3, or a later version of 2.11, tool is used, the max amount of process data will be
1473 bytes, due to limitations in the tool.
For in–depth information regarding the Anybus CompactCom software interface, consult the
Anybus CompactCom 40 Software Design Guide.
Anybus®CompactCom™40 EtherCAT®Network Guide SCM-1202-034 1.1

Basic Operation 10 (136)
3.1.2 EtherCAT Slave Interface (ESI) File
Each device on EtherCAT is associated with a EtherCAT Slave Interface (ESI) file in XML for-
mat, which holds a description of the device and its functions.
HMS Industrial Networks AB supplies a generic ESI file which can serve as a basis for new im-
plementations. However, due to the flexible nature of the Anybus CompactCom concept, it is
possible to alter the functionality of the module in ways which contradicts the information in this
file. This may cause trouble if the master expects the configuration stated in the file. In some
cases, these problems can be rectified by the end user by manually changing I/O parameters
etc. To ensure interoperability and to reduce the complexity for the end user, it is strongly rec-
ommended to create a custom ESI file to match the final implementation of the product.
The EtherCAT Technology Group (ETG) requires that the Vendor ID is changed to reflect the
vendor of the end product. The following scenarios, among others, may require additional
changes to the EtherCAT Slave Interface file.
• The use of a custom Product Code.
• The use of an own Vendor ID.
• Change of the product revision.
• The host application supports the Remap_ADI commands.
• The use of Ethernet over EtherCAT (EoE).
• Slow application response times. Explicit requests should be handled within 1 ms in or-
der to comply with the generic ESI file supplied by HMS. This may not be sufficient for a
slow serial link with a substantial amount of I/O (in such case, the mailbox timeout value
in the file needs to be increased accordingly).
Note that deviations from the generic ESI file requires the use of custom Product Codes apart
from the required custom Vendor ID.
3.1.3 Device Identity
In a generic implementation (i.e. no network specific support is implemented) the module will
appear as a generic HMS device with the following identity information:
Object Entry Value
Vendor ID E000 001Bh (HMS Industrial Networks Secondary Vendor ID, has to
be replaced by the Vendor ID of the end product vendor.)
Product Code 0000 0036h (Anybus CompactCom 40 EtherCAT)
Device Name Anybus CompactCom 40 EtherCAT
Serial Number (Assigned during manufacturing)
By implementing support for the EtherCAT Object (F5h), the module can be customized to ap-
pear as a vendor specific implementation rather than a generic Anybus device. For the end
product to pass the ETG conformance tests and be certified, a separate Vendor ID has to be re-
quested from ETG.
See also...
•EtherCAT Object (F5h), p. 71
Anybus®CompactCom™40 EtherCAT®Network Guide SCM-1202-034 1.1

Basic Operation 11 (136)
3.1.4 File Access over EtherCAT (FoE)
The module supports File Access over EtherCAT (FoE) for downloading firmware files from a
Client machine to the Server. All FoE requests not concerning files with the extension hiff (HMS
firmware files) or the extension .nfo, will be forwarded to the Application File System Interface
object. Since FoE offers only very basic FTP functionality, saved files (other than .hiff files) will
end up in the root folder of the Application File System Interface object.
If a firmware file, downloaded through FoE, is pending for update, the file with the extension hiff
will be possible to upload via FoE.
FoE is not supported for Anybus IP.
3.1.5 Ethernet over EtherCAT (EoE)
The module supports transparent tunneling of non-EtherCAT Ethernet frames to and from an
EtherCAT slave, using Ethernet over EtherCAT (EoE).
EoE is not supported for Anybus IP in limited mode.
With Ethernet over EtherCAT (EOE), the following features are supported:
• Web server with customizable content
• FTP server
• E-mail client
• Server Side Include (SSI) functionality
• JSON functionality
Since the Ethernet frames are embedded in mailbox communication, the performance will be
reduced compared to normal Ethernet communication. The data throughput will depend on...
• The EtherCAT process data cycle time
• The mailbox size (in bytes)
To be able to use Ethernet over EtherCAT (EoE), the Anybus CompactCom 40
device needs to be assigned a MAC address. Users with devices containing older
software (prior to software version 2.00) will need to set the MAC address
manually, in the Ethernet Host Object, to be able to use Ethernet over EtherCAT
(EoE).
To indicate or remove support for Ethernet over EtherCAT (EoE) in the ESI file, see the
following:
To support Ethernet over EtherCAT (EoE), the <Mailbox> element should look like this:
<Mailbox DataLinkLayer="1">
<EoE IP="0" MAC="0" TimeStamp="0" />
<CoE SdoInfo="1" CompleteAccess="1" PdoAssign="0" PdoConfig="0"
PdoUpload="1"/>
<FoE/>
</Mailbox>
To remove support for Ethernet over EtherCAT (EoE), the <Mailbox> element should look like
this:
<Mailbox DataLinkLayer="1">
Anybus®CompactCom™40 EtherCAT®Network Guide SCM-1202-034 1.1

Basic Operation 12 (136)
<CoE SdoInfo="1" CompleteAccess="1" PdoAssign="0" PdoConfig="0"
PdoUpload="1"/>
<FoE/>
</Mailbox>
3.2 EtherCAT Implementation Details
3.2.1 General Information
The module implements a full EtherCAT slave with the following basic properties:
Application Layer: CANopen over EtherCAT
FMMUs. 4
Sync Managers. 4
RAM Size: 16 kByte
See also...
•CANopen over EtherCAT Implementation Details, p. 14
3.2.2 EtherCAT Synchronization
EtherCAT synchronization and jitter accuracy may depend on different things:
• How often the master sends out sync frames
• Temperature variations in the environment (large impact)
• The implementation of the EtherCAT slave device
• Which Ethernet physical layer is used in the slave devices (RJ45, E-Bus etc.)
The Anybus CompactCom 40 EtherCAT modules all demonstrate less than 1 μs synchroniza-
tion accuracy. For RJ45 products the accuracy may be around 50 ns under good conditions,
and for E-Bus products around 30 ns.
3.2.3 Sync Managers
The module features four Sync Managers:
Sync Manager 0 Used for mailbox write transfers (Master to Slave).
The module has a configurable write mailbox size with default size of 276 bytes,
corresponding to 255 bytes plus relevant protocol headers and padding.
Sync Manager 1 Used for mailbox read transfers (Slave to Master).
The module has a configurable read mailbox size with default size of 276 bytes,
corresponding to 255 bytes plus relevant protocol headers and padding.
Sync Manager 2 Contains the RxPDOs (in practice, Sync Manager 2 holds the Read Process
Data).
Sync Manager 3 Contains the TxPDOs (in practice, Sync Manager 3 holds the Write Process Data).
3.2.4 FMMUs
There are four FMMUs. The EtherCAT master can use the FMMUs freely for any purpose.
Anybus®CompactCom™40 EtherCAT®Network Guide SCM-1202-034 1.1

Basic Operation 13 (136)
3.2.5 Addressing Modes
As a full EtherCAT, the module supports the following addressing modes:
• position addressing
• node addressing
• logical addressing
3.2.6 Watchdog Functionality
Output I/O Sync Manager Watchdog
If enabled, this watchdog monitors the PDO communication towards the Anybus module. If the
master doesn’t update the Read Process Data within the specified time period, this will trigger a
timeout condition in the module, causing it to shift from OPERATIONAL to SAFE-OPERATION-
AL. The supervision-bit (SUP) is also affected by this.
The sync manager watchdog is enabled by default in the ESI file, with a default time period of
100 ms.
The sync manager watchdog can always be disabled/enabled manually in the configuration tool
for the master.
See also...
•SUP-bit Definition, p. 118
PDI Watchdog
PD watchdog functionality is not supported.
Anybus®CompactCom™40 EtherCAT®Network Guide SCM-1202-034 1.1

Basic Operation 14 (136)
3.3 CANopen over EtherCAT Implementation Details
3.3.1 General Information
As mentioned previously, the module implements CANopen over EtherCAT. The object imple-
mentation is based on the DS301 communication profile.
See also...
•Data exchange, p. 15
•Object Dictionary (CANopen over EtherCAT), p. 21
3.3.2 Implemented Services
The module implements the following CANopen services:
Service Description
SDO Download Expedited Writes up to four octets to the slave
SDO Download Normal Writes up to a negotiated number of octets to the slave
Download SDO Segment Writes additional data if the object size exceeds the negotiated no. of octets.
SDO Upload Expedited Reads up to four octets from the slave
SDO Upload Normal Reads up to a negotiated number of octets from the slave§
Upload SDO Segment Reads additional data if the object size exceeds the negotiated no. of octets
Abort SDO Transfer Server abort of service in case of an erroneous condition
Get OD List Reads a list of available indices
Get Object Description Reads details of an index
Get Entry Description Reads details of a subindex
Emergency Reports unexpected conditions and diagnostic events.
Anybus®CompactCom™40 EtherCAT®Network Guide SCM-1202-034 1.1

Basic Operation 15 (136)
3.4 Data exchange
3.4.1 Application Data (ADI)
Application Data Instances (ADIs) can be accessed from the network via dedicated object en-
tries in the Manufacturer Specific range and the Profile range (2001h - FFFFh). The SDO infor-
mation protocol allows nodes to retrieve the name and data type of the ADI.
See also...
•Manufacturer and Profile Specific Objects, p. 26
3.4.2 Process Data
ADIs mapped as Process Data will be exchanged cyclically as Process Data Objects (PDOs)
on the bus. The actual PDO map is based on the Process Data map specified during startup or
how the application is implemented. It can be changed from the network during runtime, if the
application has implemented the remap commands in the Application Data Object.
The module supports up to 6 TPDOs and up to 6 RPDOs, each supporting up to 254 SDO map-
pings. Each SDO equals one Process Data mapped ADI element (i.e. mapping multiple element
ADIs will result in multiple SDO mappings). The number of TPDOs and RPDOs can be ex-
tended if the Assembly Mapping Object is implemented.
To gain in configurability, the Assembly Mapping Object can be used to remap and replace the
Process Data map specified at startup. Each PDO will be represented by an instance in the As-
sembly Mapping Object. The PDOs will then be remapped when the module enters the Safe-
Operational state.
If the Modular Device Object is implemented, i.e. the Modular Device Profile is enabled, the As-
sembly Mapping Object will be ignored.
Preferably, the EtherCAT Slave Information file should be altered to match the actual Process
Data implementation. This is not a general requirement, but it has a positive impact on compati-
bility with 3rd party masters.
See also...
•Standard Objects, p. 21
•Manufacturer and Profile Specific Objects, p. 26
•Assembly Mapping Object (EBh), p. 67
• Application Data Object (see Anybus CompactCom 40 Software Design Guide)
• Modular Device Object (see Anybus CompactCom 40 Software Design Guide)
Anybus®CompactCom™40 EtherCAT®Network Guide SCM-1202-034 1.1

Basic Operation 16 (136)
3.5 File System
3.5.1 Overview
The Anybus CompactCom 40 EtherCAT has a built-in file system, that can be accessed from
the application and from the network. Three directories are predefined:
VFS The virtual file system that e.g. holds the web pages of the module.
Application This directory provides access to the application file system through the
Application File System Interface Object (EAh) (optional).
Firmware The firmware directory points to the firmware candidate area where firmware files
can be uploaded.
In the firmware folder, it is not possible to use append mode when writing a file. Be sure to use
write mode only.
Anybus
CompactCom
File system
File 1
File 2
VFS
File 1
File 2
Application
Application
File system
File A1
File A2
Directory A1
File A1:1
File A1:2
The Anybus CompactCom accesses
the application file system through the
Application File System Interface Object.
Anybus CompactCom Application
Firmware
Fig. 1
Anybus®CompactCom™40 EtherCAT®Network Guide SCM-1202-034 1.1

Basic Operation 17 (136)
3.5.2 General Information
The built-in file system hosts 28 Mb of nonvolatile storage, which can be accessed by the HTTP
and FTP servers, the e-mail client, and the host application (through the Anybus File System In-
terface Object (0Ah).
Maximum number of directories and files that can be stored in the root directory is 511, if only
short filenames are used (8 bytes name + 3 bytes extension). If longer filenames are used, less
than 511 directories/files can be stored. This limitation does not apply to other directories in the
file system.
The file system uses the following conventions:
• \ (backslash) is used as a path separator
• Names may contain spaces, but must not begin or end with one.
• Valid characters in names are ASCII character numbers less than 127, excluding the
following characters: \ / : * ? “ < > |
• Names cannot be longer than 48 characters
• A path cannot be longer than 126 characters (filename included)
See also...
•FTP Server, p. 84
•Web Server, p. 78
•E-mail Client, p. 86
•Server Side Include (SSI), p. 87
The file system is located in flash memory. Due to technical reasons, each flash
segment can be erased approximately 100000 times before failure, making it
unsuitable for random access storage.
The following operations will erase one or more flash segments:
• Deleting, moving or renaming a file or directory
• Writing or appending data to an existing file
• Formatting the file system
3.5.3 System Files
The file system contains a set of files used for system configuration. These files, known as “sys-
tem files”, are regular ASCII files which can be altered using a standard text editor (such as the
Notepad in Microsoft Windows™). The format of these files are, with some exceptions, based
on the concept of keys, where each keys can be assigned a value, see below.
Example 1:
[Key1]
value of Key1
[Key2]
value of Key2
Anybus®CompactCom™40 EtherCAT®Network Guide SCM-1202-034 1.1

Basic Operation 18 (136)
3.6 Communication Settings in Stand Alone Shift Register
Mode
If the Anybus CompactCom 40 is used stand alone, there is no application from which to set the
IP address. The IP address is instead set using the DIP1 switches (IP address byte 3) and the
virtual attributes (Ethernet Host Object (F9h), attribute #17), that are written to the memory dur-
ing setup (IP address byte 0 – 2). A flowchart is shown below.
Start
DIP1 switch settings
(0 - 255)
2550
1 - 254
Values stored in
Network Conguration
Object instances #3 - #6
will be used
Ethernet
Host Object (F9h),
attribute #17
implemented
Yes
No Use default value for
IP address bytes 0 - 2:
192.168.0.X
Use DIP switch settings
for IP address byte 3
End
Use attribute #17 values
for IP address bytes 0 - 2
IP address is stored in Network
Conguration Object (04h),
instance #3
Check for DHCP
availability
Yes
No
DHCP will be used for
communication settings,
that will be stored in
Network Conguration
Object (04h), instances #3 - #6
Values stored in
Network Conguration
Object instances #3 - #6
will be used
Network Conguration Object (04h)
Instance #4, Subnet mask: 255.255.255.0
Instance #5 Gateway address: 0.0.0.0
Instance 6, DHCP: OFF
See also...
Ethernet Host Object (F9h), p. 75
Network Configuration Object (04h), p. 38
Anybus CompactCom M40 Hardware Design Guide
Anybus®CompactCom™40 EtherCAT®Network Guide SCM-1202-034 1.1