PMA KS800 - Data Read Procedure

3.5.4 Data read procedure
Start telegram:
Master sends: Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7
0x10 ID1 Code FB no. Fct._no. Type 0 0
Controller
replies:
Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7
0x10 Numb. real values
1)
Numb. integer values
1)
Data telegrams:
Master sends: Byte 0 Byte 1 Byte 2 Byte 3 Byte4-7 Controller replies: Byte 0 Byte 1 Byte 2 Byte 3 Byte4-7
0x68 count 0x68 count Value
Thereby, the first value is sent with Count = 1. For flow control, count is reflected by KS800 (? once). The
values are transmitted in the order real - integer.
End telegram:
Master sends: Byte 0 Byte 1 Byte 2 Byte 3 Byte4-7 Controller replies: Byte 0 Byte 1 Byte 2-3 Byte4-7
0x16 0x16 Result
3.6 Examples
3.6.1
Function block protocol principles
A function block has input and output data (process data) as well as parameter and configuration data. It is
addressable via a function block number.
The following access mechanisms are used:
3.6.2 Individual access
This access (code xx) can be used for reading or writing an individual value of a function.
Valid values for ID1:
Configuration as
FixPoint:
0 = integer real values are transmitted as integer (without digits behind the decimal point)
1 = real real values are transmitted as FixPoint (1 digit behind the decimal point)
Example 1: (message structure with data sending)
Transmission of parameter set number (ParNr = 1) to the controller (channel 2).
Start telegram:
Master sends:
Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7
0x10 0 31 52 5 0 0 1
Controller
replies:
Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7
0x10
Data telegrams:
Master sends:
Byte 0 Byte 1 Byte 2 Byte 3 Byte4-7 Controller replies: Byte 0 Byte 1 Byte 2 Byte 3 Byte4-7
0x68 1 1 0x68 1
End telegram:
Master sends:
Byte 0 Byte 1 Byte 2 Byte 3 Byte4-7 Controller replies: Byte 0 Byte 1 Byte2-3 Byte4-7
0x16 0x16 0
Process data
9499 040 50511 18
1) If a Read Service was refused, these values = 0