Instructions
Table Of Contents
- P. About This Document
- 1. About the Anybus Communicator for PROFINET
- 2. Basic Operation
- 3. File System
- 4. Basic Network Configuration
- 5. FTP Server
- 6. Web Server
- 7. Server Side Include (SSI)
- 7.1 General
- 7.2 Functions
- DisplayMacID
- DisplaySerial
- DisplayFWVersion
- DisplayBLVersion
- DisplayIP
- DisplaySubnet
- DisplayGateway
- DisplayDNS1
- DisplayDNS2
- DisplayHostName
- DisplayDomainName
- DisplayDhcpState
- DisplayDhcpSupport
- DisplayEmailServer
- DisplaySMTPUser
- DisplaySMTPPswd
- DisplayStationName
- DisplayStationType
- DisplayVendorID
- DisplayDeviceID
- StoreEtnIPConfig
- GetText
- printf
- scanf
- IncludeFile
- SaveToFile
- SaveDataToFile
- DisplayScannerMode
- SetScannerMode
- 7.3 Changing SSI output
- 8. E-mail Client
- 3. Navigating ACM
- 10. Basic Settings
- 5. Nodes
- 6. Transactions
- 7. Frame Objects
- 8. Commands
- 9. DF1 Protocol Mode
- 10. Sub-network Monitor
- 11. Node Monitor
- 12. Data Logger
- 19. Configuration Wizards
- 14. Control and Status Registers
- 15. Advanced Fieldbus Configuration
- A. Connector Pin Assignments
- B. Technical Specification
- C. Troubleshooting
- D. ASCII Table
- F. Copyright Notices
Doc: HMSI-27-309, Rev. 3.11Anybus Communicator PROFINET User Manual
Chapter 14
14. Control and Status Registers
14.1 General
The Control and Status Registers are disabled by default, but can be enabled using ACM (see “Control/
Status Word” on page 25). These registers form an interface for exchanging status information between
the sub-network and the fieldbus control system.
The main purpose of these registers is to...
• Report sub-network related problems to the fieldbus control system
• Ensure that only valid data is exchanged in both directions
• Enable the fieldbus control system to start/stop data exchange with selected nodes on the sub-
network
If enabled, these registers occupy the first two bytes in the input and output data areas (0x000–0x001
and 0x200–0x201 respectively), which means they can be accessed from the fieldbus just like any other
data in these areas.
Note: Internally, these registers are stored in Motorola-format (i.e. MSB first). If the higher level net-
work uses a different byte order, the upper and lower bytes will appear swapped.
14.1.1 Handshaking Procedure
A special handshaking procedure, which is illustrated in the two flowcharts below, must be followed
when accessing these registers to ensure that both parts receive proper information.
Start
Read Status Register
Set CR_HS_CONFIRM
to SR_HS_SEND
CR_HS_CONFIRM=
SR_HS_SEND?
Yes
Done
Start
Read Status Register Write to Control Register
Write to Control Register
Toggle CR_HS_SEND
SR_HS_CONFIRM=
CR_HS_SEND?
No
No Yes
Done










