Instance Attributes (Instance #1)
# | Name | Access | Data Type | Description | ||||
|---|---|---|---|---|---|---|---|---|
1 | State | Get | UINT8 | Current state of the Safety Module Please consult the manual for the Safety Module used. | ||||
2 | Vendor ID | Get | UINT16 | Identifies vendor of the Safety Module. E.g. 0001h (HMS Industrial Networks) Please consult the manual for the Safety Module used. | ||||
3 | IO Channel ID | Get | UINT16 | Describes the IO Channels that the Safety Module is equipped with. Please consult the manual for the Safety Module used. | ||||
4 | Firmware version | Get | Struct of UINT8 (Major) UINT8 (Minor) UINT8 (Build) | Safety Module firmware version. Format: version “2.18.3” would be represented as: first byte = 0x02, second byte = 0x12, third byte = 0x03. | ||||
5 | Serial number | Get | UINT32 | 32 bit number, assigned to the Safety Module at production. Please consult the manual for the Safety Module used. | ||||
6 | Output data | Get | Array of UINT8 | Current value of the Safety Module output data, i.e. data FROM the network. Note: This data is unsafe, since it is provided by the Anybus CompactCom module. | ||||
7 | Input data | Get | Array of UINT8 | Current value of the Safety Module input data, i.e. data sent TO the network. Note: This data is unsafe, since it is provided by the Anybus CompactCom module. | ||||
8 | Error counters | Get | Struct of UINT16 (ABCC DR) UINT16 (ABCC SE) UINT16 (SM DR) UINT16 (SM SE) | Error counters (each counter stops counting at FFFFh) | ||||
| ||||||||
9 | Event log | Get | Array of UINT8 | Latest Safety Module event information (if any) is logged to this attribute. Any older event information is erased when a new event is logged. For evaluation by HMS support. | ||||
10 | Exception information | Get | UINT8 | If the Exception Code in the Anybus object is set to “Safety communication error” (09h), additional exception information is presented here, see table below. | ||||
11 | Bootloader version | Get | Struct of UINT8 Major UINT8 Minor | Safety Module bootloader version. Format: version “2.12” would be represented as: first byte = 0x02, second byte = 0x0C | ||||
12 | Vendor block safe uc1 | Get | Array of UINT8 | The Safety Module may supply additional vendor-specific data to the Anybus CompactCom. If such data is available it is presented in this attribute. | ||||
13 | Vendor block safe uc2 | Get | Array of UINT8 | The Safety Module may supply additional vendor-specific data to the Anybus CompactCom. If such data is available it is presented in this attribute. |
Exception Information
If Exception Code 09h is set in the Anybus object, there is an error regarding the functional safety module in the application. Exception information is presented in instance attribute #10 according to this table:
Value | Exception Information |
|---|---|
00h | No information |
01h | Baud rate not supported |
02h | No start message |
03h | Unexpected message length |
04h | Unexpected command in response |
05h | Unexpected error code |
06h | Safety application not found |
07h | Invalid safety application CRC |
08h | No flash access |
09h | Answer from wrong safety processor during boot loader communication |
0Ah | Boot loader timeout |
0Bh | Network specific parameter error |
0Ch | Invalid IO configuration string |
0Dh | Response differed between the safety microprocessors (e.g. different module types) |
0Eh | Incompatible module (e.g. supported network) |
0Fh | Max number of retransmissions performed (e.g. due to CRC errors) |
10h | Firmware file error |
11h | The cycle time value in attribute #4 in the Functional Safety Host Object can not be used with the current baud rate |
12h | Invalid SPDU input size in start-up telegram |
13h | Invalid SPDU output size in start-up telegram |
14h | Badly formatted input SPDU |
15h | Anybus to safety module initialization failure |