Instructions
Table Of Contents
- 1 Preface
- 2 Safety
- 3 Preparation
- 4 About Anybus Communicator
- 5 Installation
- 6 Configuration Quick Guide
- 7 Communicator Configuration
- 7.1 Connecting the Communicator
- 7.2 Access the Built-In Web Interface From HMS IPconfig
- 7.3 Access the Built-In Web Interface From a Web Browser
- 7.4 Communicator Built-In Web Interface Overview
- 7.5 General Subnetwork Settings
- 7.6 About Transaction Templates
- 7.7 Build Transaction Templates
- 7.8 Nodes and Transactions
- 7.9 High Level Network Settings
- 7.10 Naming the Host
- 7.11 Station Name
- 7.12 I/O Data Map
- 7.13 Apply Configuration
- 7.14 Use an Existing Configuration
- 8 PLC Configuration
- 9 Verify Operation
- 10 Use Cases
- 11 Maintenance
- 12 Troubleshooting
- 13 Technical Data
- A Reference Guides
Use Cases
96 (124)
10.2.5 Create Transaction Templates
All frames are verified using a CRC-16-IBM checksum.
My Drive is using a request/response protocol to access parameters addressed with index and
sub index.
Map up control word, speed from PROFINET to My Drive and status word and actual speed from
the drive to PROFINET.
Create Read parameter (0x01)
The Communicator reads values delivered from to the My Drive node on to the PLC.
1. Add an Empty template and select it.
2. Name the template Read parameter (0x01).
3. In the Frame editor Request area, add five frame fields with the following settings:
Request frame fields
Frame fields
Name
Bytes/
Length
Type/
Checksum type
Endianess Fixed field Value
Constant
Function code
1 Byte
N/A
Yes
N/A
Node address Node ID
1 Byte
N/A N/A N/A
Constant
Index
2
Word (two
bytes)
Big-endian
No Min 0
Max 1000
Constant
Sub index
1 Byte
N/A
No Min 0
Max 255
Checksum Checksum
2 CRC
N/A N/A N/A
Anybus
®
Communicator
™
User Manual
SCM-1202-176 1.0 en-US