manualshive.com logo in svg

Anybus CompactCom 40 Modbus-TCP, Network Manual, Page: 12 / 72

Share
Download
Anybus CompactCom 40 Modbus-TCP Network Manual Download Page 12

Basic Operation

10 (70)

3

Basic Operation

3.1

Software Requirements

No additional network support code needs to be written in order to support the Anybus Com-
pactCom 40 Modbus-TCP, however due to the nature of the Modbus-TCP networking system,
certain restrictions must be taken into account:

•

The total number of ADIs that can be represented on the network depends on their size. By
default, ADIs with instance numbers 1...3839 can be accessed from the network, each with
a size of up to 32 bytes.

•

ADI names, types and similar attributes cannot be accessed viaModbus-TCP. They are
however represented on the network through the built in web server.

•

A network write access of an ADI mapped to process data will result in a corresponding
write access of the process data buffer of the Anybus CompactCom 40 Modbus-TCP.

•

A network read access of an ADI, even if it is mapped to process data, will result in a corre-
sponding Get_Attribute command towards the application.

•

Modbus-TCP reset requests are not supported.

•

Up to 5 diagnostic instances (See Diagnostic Object) can be created by the host applica-
tion during normal conditions. An additional 6th instance may be created in event of a major
fault.

•

Modbus-TCP in itself does not impose any specific timing demands when it comes to acy-
clic requests (i.e. requests towards instances in the Application Data Object), however it is
generally recommended to process and respond to such requests within a reasonable time
period (exactly what this means in practice depends on the implementation and the actual
installation).

•

The use of advanced Modbus-TCP specific functionality may require in-depth knowledge
in Modbus-TCP networking internals and/or information from the official Modbus-TCP
specifications. In such cases, the people responsible for the implementation of this product
is expected either to obtain these specifications to gain sufficient knowledge or limit their
implementation is such a way that this is not necessary.

See also...

•

Application Data (ADIs), p. 13

•

Diagnostic Object (02h), p. 27

•

Anybus CompactCom 40 Software Design Guide, “Application Data Object (FEh)”

For in depth information regarding the Anybus CompactCom software interface, consult the
Anybus CompactCom 40 Software Design Guide.

Anybus

®

CompactCom

™

40 Modbus-TCP

®

Transparent Ethernet Network Guide

SCM-1202-022 1.1

Summary of Contents for CompactCom 40 Modbus-TCP

Page 1: ...Anybus CompactCom 40 Modbus TCP Transparent Ethernet NETWORK GUIDE SCM 1202 022 1 1 ENGLISH ...

Page 2: ... 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 issu...

Page 3: ...eration 10 3 1 Software Requirements 10 3 2 Device Customization 11 3 3 Communication Settings 12 3 4 Diagnostics 12 3 5 Network Data Exchange 12 4 Modbus TCP Register Implementation 15 4 1 Holding Registers 4x 15 4 2 Input Registers 3x 15 4 3 Coils 0x 15 4 4 Discrete Inputs 1x 15 5 Modbus TCP Functions 16 5 1 Read Coils 17 5 2 Read Discrete Inputs 17 5 3 Read Holding Registers 17 5 4 Read Input R...

Page 4: ...iguration Object 04h 29 8 6 Anybus File System Interface Object 0Ah 38 8 7 Network Ethernet Object 0Ch 39 9 Host Application Objects 40 9 1 General Information 40 9 2 Modbus Host Object FAh 41 9 3 Ethernet Host Object F9h 44 A Categorization of Functionality 49 A 1 Basic 49 A 2 Extended 49 B Implementation Details 50 B 1 SUP Bit Definition 50 B 2 Anybus State Machine 50 B 3 Application Watchdog Ti...

Page 5: ...nsparent Ethernet Network Guide SCM 1202 022 1 1 Table of Contents E Backward Compatibility 55 E 1 Initial Considerations 55 E 2 Hardware Compatibility 56 E 3 General Software 60 E 4 Network Specific Modbus TCP 62 F Copyright Notices 64 ...

Page 6: ...This page intentionally left blank ...

Page 7: ... 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 Gu...

Page 8: ...twork 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 for...

Page 9: ...k Information Anybus is a registered trademark of HMS Industrial Networks AB All other trademarks are the property of their respective holders Anybus CompactCom 40 Modbus TCP Transparent Ethernet Network Guide SCM 1202 022 1 1 ...

Page 10: ...ementation rather than a generic Anybus module 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 fu...

Page 11: ...parent Ethernet functionality has to be enabled during startup by setting at tribute 16 instance 1 in the Anybus Object 16 bit parallell mode can not be used as specific host application connector pins are reserved for transparent Ethernet Also TCP UDP ports may be reserved and can in that case not be used for the transparent Ethernet communication See also Transparent Ethernet p 20 Anybus Compact...

Page 12: ...e created by the host applica tion during normal conditions An additional 6th instance may be created in event of a major fault Modbus TCP in itself does not impose any specific timing demands when it comes to acy clic requests i e requests towards instances in the Application Data Object however it is generally recommended to process and respond to such requests within a reasonable time period ex...

Page 13: ... firmware version of the product Vendor URL no information returned by default Product Name no information returned by default Model Name no information returned by default User Application Name no information returned by default It is possible to customize this information by implementing the Modbus Host Object See Mod bus Host Object FAh p 41 for more information Anybus CompactCom 40 Modbus TCP ...

Page 14: ...Note This value can be accessed from the Modbus registers Note This value affects the behavior of the SUP bit See SUP Bit Definition p 50 See also Network Configuration Object 04h p 29 Anybus Module Object Secure HICP Secure Host IP Configuration Protocol p 51 3 4 Diagnostics Each instance within the Diagnostic Object 02h is represented on the network as a dedicated entry in the Modbus register ma...

Page 15: ...05h Holding Register ADI No 1010h 102Fh 1 1030h 104Fh 2 1050h 106Fh 3 1070h 108Fh 4 FFB0h FFCFh 1918 FFD0h FFEFh 1919 Each ADI is represented using 32 Modbus registers which means that up to 64 bytes of an ADI can be accessed from the network 3 5 3 Process Data Modbus does not feature a dedicated cyclic data channel in the same sense as many other net works In the Anybus CompactCom 40 implementati...

Page 16: ...rom the process data in one register 3 UINT8 FFh 4 UINT32 112233 44h 2 3344h LSB A 32 bit type occupies two Modbus registers MSB 5 6 3 1122h 7 8 BOOL 3 01h 4 0001h 9 00h 10 01h 5 3401h 11 UINT16 1234h 12 6 0012h High byte from unmapped process data is set to zero Anybus CompactCom 40 Modbus TCP Transparent Ethernet Network Guide SCM 1202 022 1 1 ...

Page 17: ...02FFh Write Process Data 0300h 07FFh Reserved 0800h Diagnostic Event Count Number of pending diagnostic events There may be gaps between active diagnostic events Inactive diagnostic events return 0000h when read 0801h Diagnostic Event 1 These registers corresponds to instances in the Diagnos tic Object 02h see Diagnostic Object 02h p 27 High byte Severity Low byte Event Code 0802h Diagnostic Event...

Page 18: ...rite Multiple Registers 23 Read Write Multiple Registers 43 14 Read Device Identification Exception Codes Code Name Description 0x01 Illegal function The function code in the query is not supported 0x02 Illegal data address The data address received in the query is outside the initialized memory area 0x03 Illegal data value The data in the request is illegal See also Modbus Host Object FAh p 41 An...

Page 19: ...e 2 Register Type 1x Discrete Inputs Details This function is mapped to the Write Process data the mapping is otherwise identical to that of the Read Coils function described above 5 3 Read Holding Registers Function Code 3 Register Type 4x Holding Registers Details Mapped to Read and Write Process Data ADIs and configuration registers It is allowed to read parts of a larger Anybus CompactCom data...

Page 20: ...scribed above 5 6 Write Single Register Function Code 6 Register Type 4x Holding Registers Details Mapped to Read and Write Process Data ADIs and configuration registers ADIs must be writ ten as a whole however the Process Data area accepts writes of any size 5 7 Write Multiple Coils Function Code 15 Register Type 0x Coils Details This function is mapped to the Read Process data and the mapping is...

Page 21: ...arts of larger data types and to read multiple ADIs using a single request The write operation is performed before the read If there is an overlap in the read and write ranges the newly written data will be returned by the read operation 5 10 Read Device Identification Function Code 43 subcode 14 Register Type Details Basic and regular device identification objects are supported according to the M...

Page 22: ... available when transparent Ethernet is enabled See the Anybus CompactCom M40 Hardware Design Guide for more information Safety black channel Industrial Ethernet communication Other Ethernet communication Anybus CompactCom 40 Host Application Network connector Anybus host connector RMII Router Industrial Ethernet software Application software TCP IP RMII Fig 1 Transparent Ethernet has to be enable...

Page 23: ...AC address from this object 6 4 IP Configuration Synchronization The host application TCP IP stack and the Anybus CompactCom 40 Modbus TCP TCP IP stack must use the same IP configuration when communicating on Ethernet The Anybus Compact Com 40 Modbus TCP will write its currently used IP configuration to instance attribute 16 in the Ethernet Host Object F9h whenever the configuration is assigned or...

Page 24: ... 01 0E CF XX XX XX 01 80 C2 00 00 0E 01 00 5E 40 F8 00 01 00 5E 40 FB FF X3 XX 00 00 00 00 X any number 0 F 6 5 3 UDP TCP Ports The following ports may be used by the Anybus CompactCom and must not be used by the host application UDP 67 68 DHCP UDP 161 SNMP UDP 3250 HICP The following ports are reserved for use by PROFINET UDP 34962 PROFINET RT Unicast UDP 34963 PROFINET RT Multicast UDP 34969 PRO...

Page 25: ...on FTP root The file module nfo in the firmware directory in theAnybus CompactCom file system has to be copied to the firmware directory in the host application file system FMII only The Anybus CompactCom file system is accessed via the Anybus File System Object 0Ah Once a firmware file has been downloaded the host application must be able to detect a new file in the firmware directory download th...

Page 26: ...e functionality in the Anybus CompactCom 40 Modbus TCP Standard Objects Anybus Object 01h p 25 Diagnostic Object 02h p 27 Network Object 03h p 28 Network Configuration Object 04h p 29 Network Specific Objects Anybus File System Interface Object 0Ah p 38 Network Ethernet Object 0Ch p 39 Anybus CompactCom 40 Modbus TCP Transparent Ethernet Network Guide SCM 1202 022 1 1 ...

Page 27: ...e for further information Instance Attributes Instance 1 Basic Name Access Type Value 1 Module type Get UINT16 0403h Standard Anybus CompactCom 40 2 11 Consult the general Anybus CompactCom 40 Software Design Guide for further information 12 LED colors Get struct of Value Color UINT8 LED1A 01h Green UINT8 LED1B 02h Red UINT8 LED2A 01h Green UINT8 LED2B 02h Red 13 15 Consult the general Anybus Comp...

Page 28: ...ttributes Get Set Consult the general Anybus CompactCom 40 Software Design Guide for further information 18 Black list White list Get Set 19 Network time Get UINT64 0 Not supported Anybus CompactCom 40 Modbus TCP Transparent Ethernet Network Guide SCM 1202 022 1 1 ...

Page 29: ...f the maximum number of instances there should always be one instance reserved for an event of severity level Major unrecoverable to force the module into the EXCEPTION state 12 Supported functionality Get BITS32 Bit 0 0 Latching events are not supported Bit 1 31 reserved shall be 0 Instance Attributes Instance 1 Extended Name Access Data Type Value 1 Severity Get UINT8 Consult the general Anybus ...

Page 30: ...s TCP 3 Data format Get ENUM 00h LSB first 4 Parameter data support Get BOOL True 5 Write process data size Get UINT16 Current write process data size in bytes Updated on every successful Map_ADI_Write_Area Consult the general Anybus CompactCom 40 Software Design Guide for further information 6 Read process data size Get UINT16 Current read process data size in bytes Updated on every successful Ma...

Page 31: ...on 1 Name Get Array of CHAR Network Configuration 2 Revision Get UINT8 01h 3 Number of instances Get UINT16 0012h 18 4 Highest instance number Get UINT16 0016h 22 Consult the general Anybus CompactCom 40 Software Design Guide for further information Instance Attributes Instance 3 IP Address Value is used after module reset Name Access Data Type Description 1 Name Get Array of CHAR IP address Multi...

Page 32: ... Descriptor Get UINT8 07h read write shared access 5 Value Get Set Array of UINT8 Any change is valid after reset Valid range 0 0 0 0 255 255 255 255 Default 0 0 0 0 6 Configured Value Get Array of UINT8 Holds the configured value which will be written to attribute 5 after the module has been reset Valid range 0 0 0 0 255 255 255 255 Default 0 0 0 0 Instance Attributes Instance 6 DHCP Enable Value...

Page 33: ...full duplex 03h 100HDX 100Mbit half duplex 04h 100FX 100Mbit full duplex Instance Attributes Instance 8 Ethernet Communication Settings 2 Changes have immediate effect Name Access Data Type Description 1 Name Get Array of CHAR Comm 2 Multilingual see page 37 2 Data type Get UINT8 08h ENUM 3 Number of elements Get UINT8 01h one element 4 Descriptor Get UINT8 07h read write shared access 5 Value Get...

Page 34: ... type Get UINT8 04h UINT8 3 Number of elements Get UINT8 04h four elements 4 Descriptor Get UINT8 07h read write shared access 5 Value Get Set Array of UINT8 Any change is valid after reset Valid range 0 0 0 0 255 255 255 255 Default 0 0 0 0 6 Configured Value Get Array of UINT8 Holds the configured value which will be written to attribute 5 after the module has been reset Valid range 0 0 0 0 255 ...

Page 35: ...et UINT8 07h CHAR 3 Number of elements Get UINT8 30h 48 elements 4 Descriptor Get UINT8 07h read write shared access 5 Value Get Set Array of CHAR Any change is valid after reset Domain name 48 characters 6 Configured Value Get Array of CHAR Holds the configured value which will be written to attribute 5 after the module has been reset Domain name 48 characters Anybus CompactCom 40 Modbus TCP Tran...

Page 36: ...type Get UINT8 08h ENUM 3 Number of elements Get UINT8 01h one element 4 Descriptor Get UINT8 07h read write shared access 5 Value Get Set ENUM Value ENUM 00h 01h 02h String Meaning Auto default MDI MDIX 6 Configured Value Get ENUM Holds the configured value which will be written to attribute 5 after the module has been reset Value ENUM 00h 01h 02h String Meaning Auto default MDI MDIX Anybus Compa...

Page 37: ...tes Instances 18 and 19 These instances are reserved for future attributes Instance Attributes Instance 20 Modbus connection timeout This instance holds the settings for the Modbus connection timeout Changes will be applied to new connec tions Existing connections will use the previous timeout value Name Access Data Type Description 1 Name Get Array of CHAR Conn tmo Multilingual see page 37 2 Data...

Page 38: ...itten to attribute 5 Default 0 milliseconds disable timeout Instance Attributes Instance 22 Word order This instance holds the Word order settings Value is used after module reset Name Access Data Type Description 1 Name Get Array of CHAR Word order Multilingual see page 37 2 Data type Get UINT8 04h UINT8 3 Number of elements Get UINT8 01h one element 4 Descriptor Get UINT8 07h read write shared a...

Page 39: ...100 HDX 100 FDX 100FDX 100 FDX 100 FDX 100 FDX 8 Comm 2 Komm 2 Comu 2 Connessione 2 Comm 2 Auto Auto Auto Auto Auto 10 HDX 10 HDX 10 HDX 10 HDX 10 HDX 10 FDX 10 FDX 10 FDX 10 FDX 10 FDX 100 HDX 100 HDX 100 HDX 100 HDX 100 HDX 100 FDX 100FDX 100 FDX 100 FDX 100 FDX 9 DNS1 DNS 1 DNS Primaria DNS1 DNS1 10 DNS2 DNS 2 DNS Secundia DNS2 DNS2 11 Host name Host name Nombre Host Nome Host Nom hôte 12 Domai...

Page 40: ...and contains services for file system operations This provides the host application with access to the built in file system of the module e g when application specific web pages are to be installed Instances are created and deleted dynamically during runtime This object is thoroughly described in Anybus CompactCom 40 Software Design Guide Anybus CompactCom 40 Modbus TCP Transparent Ethernet Networ...

Page 41: ...te Object Attributes Instance 0 Name Access Data Type Value 1 Name Get Array of CHAR Network Ethernet 2 Revision Get UINT8 01h 3 Number of instances Get UINT16 4 Highest instance no Get UINT16 Instance Attributes Instance 1 Name Access Data Type Description 1 MAC Address Get Array of UINT8 Current MAC address See also Ethernet Host Object F9h Anybus CompactCom 40 Modbus TCP Transparent Ethernet Ne...

Page 42: ...isted here may optionally be imple mented within the host application firmware to expand the implementation Standard Objects Application Object FFh see Anybus CompactCom 40 Software Design Guide Application Data Object FEh see Anybus CompactCom 40 Software Design Guide Network Specific Objects Ethernet Host Object F9h p 44 Modbus Host Object FAh p 41 Anybus CompactCom 40 Modbus TCP Transparent Eth...

Page 43: ...pond with an error message 06h Invalid CmdExt 0 In such case the module will use its default value If the module attempts to retrieve a value of an attribute not listed below respond with an error message 06h Invalid CmdExt 0 See also Anybus CompactCom 40 Software Design Guide Error Codes Supported Commands Object Get_Attribute Process modbus message Instance Get_Attribute Object Attributes Instan...

Page 44: ...rev 4 Vendor URL Get Array of CHAR 5 Product name Get Array of CHAR 6 Model name Get Array of CHAR 7 User Application Name Get Array of CHAR 8 Device ID Get Array of UINT8 Not used 9 No of ADI indexing bits Get UINT8 04h Value Meaning 00h each ADI 1 Modbus register 01h each ADI 2 Modbus registers 02h each ADI 4 Modbus registers 03h each ADI 8 Modbus registers 04h each ADI 16 Modbus registers 05h e...

Page 45: ...t 1 MsgData 0 n Modbus message frame Query Response Details Field Contents Comments CmdExt 0 reserved set to zero CmdExt 1 MsgData 0 n Modbus message frame Response The response data size must not exceed 254 bytes if more data is returned no Modbus response message will be sent to the originator of the request If the response contains no data no Modbus response will be sent to the originator of th...

Page 46: ...b 01 xx yy zz aa bb 02 and xx yy zz aa bb 03 with the first five octets not changing Name Ac cess Data Type Default Value Comment 1 MAC address Get Array of UINT8 6 byte physical address value overrides the preprog rammed Mac address Note that the new Mac address value must be obtained from the IEEE Do not implement this attribute if the preprogrammed Mac address is to be used 2 Enable HICP Get BO...

Page 47: ...not read by EtherCAT devices where Port 1 is always enabled This attribute is not used by PROFINET 00h Enabled 01h Disabled The port is treated as existing References to the port can exist e g in network protocol or on website 13 Port 2 State Get ENUM 0 Enabled The state of Ethernet port 2 This attribute is not read by EtherCAT devices where Port 2 is always enabled This attribute is not used by P...

Page 48: ...ring Max length is 32 22 DHCP Option 61 source Get ENUM 0 Disabled Note This attribute is currently only valid for Ethernet IP devices See below DHCP Option 61 Client Identifier 23 DHCP Option 61 generic string Get Array of UINT8 N A Note This attribute is currently only valid for Ethernet IP devices See below DHCP Option 61 Client Identifier 24 Enable DHCP Client Get BOOL 1 True Note This attribu...

Page 49: ...ient Identifier 3 Generic String Attribute 23 will be used as the Client Identifier Attribute 23 DHCP Option 61 generic string is used to set the Client Identifer when Attribute 22 has been set to 3 Generic String Attribute 23 contains the Type field and Client Identifier and shall comply with the definitions in RFC 2132 The allowed max length that can be passed to the module via attribute 23 is 6...

Page 50: ...This page intentionally left blank ...

Page 51: ...network are used Additional objects etc that will make it possible to certify the product also belong to this category A 2 Extended Use of the objects in this category extends the functionality of the application Access is given to the more specific characteristics of the industrial network not only the basic moving of data to and from the network Extra value is given to the application Some of th...

Page 52: ...ess conflict This state is only possible if Address Conflict Detection ACD is enabled in the Ethernet Host object enabled by default PROCESS_ACTIVE The module shifts to WAIT_PROCESS if no requests are received within the time stated by Process Active Timeout see Instance 21 in Network Configuration Object 04h p 29 IDLE The IDLE state can be entered exited by writ ing to the Modbus Enter Exit idle ...

Page 53: ...ility to restart reboot the device s C 2 Operation When the application is started the network is automatically scanned for Anybus products The network can be rescanned at any time by clicking Scan To alter the network settings of a module double click on its entry in the list A window will ap pear containing the settings for the module Fig 2 Validate the new settings by clicking Set or click Canc...

Page 54: ...tatus LEDs during startup D 1 2 Network Status LED LED State Description Off No IP address or in state EXCEPTION Green At least one Modbus message received Green flashing Waiting for first Modbus message Red IP address conflict detected FATAL ERROR Red flashing Connection timeout No Modbus message has been received within the configured process active timeout time A test sequence is performed on t...

Page 55: ...no activity Green Link 100 Mbit s established Green flickering Activity 100 Mbit s Yellow Link 10 Mbit s established Yellow flickering Activity 10 Mbit s D 1 5 Fatal Error If both the Network Status LED and the Module Status LED are red a fatal error has occurred D 1 6 Ethernet Interface The Ethernet interface 10 100Mbit full or half duplex operation Pin Name Description 1 TXD Transmit positive 1 ...

Page 56: ...t we reserve the right to change the exact power requirements of this product without prior notification However in any case the Anybus CompactCom 40 Modbus TCP will remain as a Class B module For more information about the power consumption classification used on the Anybus Compact Com 40 platform consult the general Anybus CompactCom 40 Hardware Design Guide It is strongly advised to design the ...

Page 57: ...e current design This is the fastest and easiest solution but with the drawback that many of the new fea tures available in the 40 series will not be enabled e g enhanced and faster commu nication interfaces larger memory areas and faster communication protocols You have to check the hardware and software differences below to make sure the host application is compatible with the 40 series modules ...

Page 58: ...ons outline connectors LED indicators mounting parts etc They are also available as modules without housing Fig 3 Anybus CompactCom M30 M40 E 2 2 Chip The chip C30 C40 versions of the Anybus CompactCom differ completely when it comes to physical dimensions There is no way to migrate a chip solution from the 30 series to the 40 series without a major hardware update Anybus CompactCom 40 Modbus TCP ...

Page 59: ... de veloped a separate brick version in the 40 series that can be used for migration This product B40 2 shares dimensions etc with the B30 Please contact HMS Industrial Networks AB for more information on the Anybus CompactCom B40 2 Fig 4 Anybus CompactCom B30 Fig 5 Anybus CompactCom B40 1 not for migration Fig 6 Anybus CompactCom B40 2 Anybus CompactCom 40 Modbus TCP Transparent Ethernet Network ...

Page 60: ...to a high Z digital input on the host processor it will be compatible with the 40 series An external pull up is recommended but not required If this pin is pulled low by the host during startup the 40 series module or brick will not enter the expected operating mode Related Information Anybus CompactCom M40 Hardware Design Guide HMSI 216 126 Sec tion Application Connector Pin Overview Module Ident...

Page 61: ...elated Information Anybus CompactCom M40 Hardware Design Guide HMSI 216 126 Sec tion LED Interface D8 D15 Data Bus GOP 0 1 LED4 A B These pins are outputs high state by default in the 30 series In the 40 series these pins are tri stated until the state NW_INIT and after that they become push pull active low LED outputs LED4A LED4B This change should not affect your product Related Information Anyb...

Page 62: ... driven applications parallel operating mode may see increased CPU load due to the increased speed E 3 3 Requests from CompactCom to Host Application During Startup All requests to software objects in the host application must be handled and responded to even if the object does not exist This applies for both the 30 series and the 40 series The 40 series introduces additional objects for new funct...

Page 63: ...sed Anybus CompactCom 30 example drivers from HMS comply with this difference Related Information Anybus CompactCom 40 Software Design Guide HMSI 216 125 section Status Register E 3 7 Control Register CTRL_R bit 30 series The application may change this bit at any time 40 series For the 8 bit parallel operating mode the bit is only allowed to transition from 1 to 0 when the STAT_M bit is set in th...

Page 64: ...10h 021Fh 1010h 101Fh ADI Number 2 0220h 022Fh 1020h 102Fh ADI Number 3839 FFF0h FFFFh Input Registers 3x Write Process Data 0000h 00FFh 0000h 02FFh Diagnostic Event Count 0100h 0800h Diagnostic Event 1 0101h 0801h Diagnostic Event 2 0102h 0802h Diagnostic Event 3 0103h 0803h Diagnostic Event 4 0104h 0804h Diagnostic Event 5 0105h 0805h Diagnostic Event 6 0106h 0806h Coils 0x Read Process Data 000...

Page 65: ...e and there is no difference between the 30 series and the 40 series If the attribute is not implemented the default value is used 11 Modbus read write registers com mand offset In the 30 series this register address offset is only applied when accessing holding regis ters with the command Read Write Multiple registers 23 The 40 series applies this register offset to all holding register access i ...

Page 66: ...are and associated documentation files the Software to deal in the Software without restriction including without limitation the rights to use copy modify merge publish distribute sublicense and or sell copies of the Software and to permit persons to whom the Software is furnished to do so subject to the following conditions The above copyright notice and this permission notice shall be included i...

Page 67: ...tion and use in source and binary forms with or without modification are permitted provided that the following conditions are met 1 Redistributions of source code must retain the above copyright notice this list of conditions and the following disclaimer 2 Redistributions in binary form must reproduce the above copyright notice this list of conditions and the following disclaimer in the documentat...

Page 68: ...VENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT INDIRECT INCIDENTAL SPECIAL EXEM PLARY OR CONSEQUENTIAL DAMAGES INCLUDING BUT NOT LIMITED TO PROCURE MENT OF SUBSTITUTE GOODS OR SERVICES LOSS OF USE DATA OR PROFITS OR BUSINESS INTERRUPTION HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY WHETHER IN CONTRACT STRICT LIABILITY OR TORT INCLUDING NEGLIGENCE OR OTHERWISE ARISING IN A...

Page 69: ...following disclaimer in the documentation and or other materials provided with the distribution 3 The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission THIS SOFTWARE IS PROVIDED BY THE AUTHOR AS IS AND ANY EXPRESS OR IM PLIED WARRANTIES INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FIT...

Page 70: ...tation would be appreciated but is not required 2 Altered source versions must be plainly marked as such and must not be misrepresented as being the original software 3 This notice may not be removed or altered from any source distribution L Peter Deutsch ghost aladdin com Anybus CompactCom 40 Modbus TCP Transparent Ethernet Network Guide SCM 1202 022 1 1 ...

Page 71: ...This page intentionally left blank ...

Page 72: ...last page 2017 HMS Industrial Networks AB Box 4126 300 04 Halmstad Sweden info hms se SCM 1202 022 1 1 4726 2017 07 11T09 25 39 ...

Reviews:

No comments