Schenck process Intecont Satus - Error Codes; Subscriber Addresses; Process Values; Example Telegrams

16.5 Error codes
Only the error codes 01 to 03 are used. No reply is sent with CRC errors.
All errors described in the following are collected in the device to a ‘Communication Host’
group message. The message includes the Timeout.
Error Code Meaning
1 The requested function is not supported by the subscriber
2 Incorrect data address
ID or SC out of range
Data offset + length to large
3 Incorrect data type
Incorrect data with FC5 (0xff00 and 0x0000 are permitted)
Data length smaller than 0
Requested length too long
The IEEE or INT32 data address values are odd-numbered.
16.6 Subscriber addresses
Each scales has a slave address which begins at 1 and continues in ascending sequence.
The highest address it is possible to set is labeled MAXSLAVE in the following text. The
address can be set using the dialog window on the scales or in EasyServe. MAXSLAVE has
a value of 254. Address 0 is the broadcast address. In this case, the slaves send no reply.
16.7 Process values
Every segment of the cyclical user data contains values of the same type. From an address
standpoint, the data within a segment line up with no gap. The data of a segment can be
read or written with one telegram each.
Note:
A so-called ‘segment address’ must be added multiple times by the control system to the the
data address described (depending on the function code). Also, the data address must be
increased by 1, because the registry Modbus protocol addresses start at 1.
So the data address configuration rule is as follows:
Data address = segment address + INTECONT® Satus address + 1.
16.8 Example telegrams
Example telegrams are described in the section: Examples of telegrams for MODBUS and
MODBUS/TCP.
16.8 Example telegrams Modbus
80 BV-H2346GB / 0833 Operating Manual INTECONT® Satus
© Schenck Process