VEGA VEGASCAN 850 Modbus signal output - Manual (Page 13)

Modbus signal output VEGASCAN 850 13
Start
Slave
address
Function
code
Diagnostic
Code
Diagnostic
Data
Error
Check
End
No. of
bytes
Value
range
Meaning
Structure of the diagnostic function from Modbus master to VEGASCAN 850
ASCII enquiry telegram diagnostic (function code 08)
1 2 2 4 4 2 2
: 1 .. 247 08 0 0 ... 65.535 LRC CR LF
No. of
bytes
Value
range
Meaning
Structure of the acknowledgement from VEGASCAN 850 to Modbus master
ASCII acknowledgement telegram diagnostic (function code 08)
: 0 1 0 8 0 0 0 0 A 5 3 7 X X CR LF
Start
Slave
address
Function
code
Diagnostic
Code
Diagnostic
Data
Error
Check
End
1 2 2 4 4 2 2
: 1 .. 247 08 0 0 ... 65.535 LRC CR LF
: 0 1 0 8 0 0 0 0 A 5 3 7 X X CR LF
Data transmission with Modbus ASCII
With the command "Preset Multiple Registers“, the data for the parameter enquiry are trans-
ferred to VEGACOM 557. For reading access, 3 register words are necessary and for writing
access, 4 register words.
After VEGASCAN has confirmed the transfer, a cyclical enquiry must be made with a second
command "Read Input Registers“ (function code 04), to get the information that the processing
is finished. VEGASCAN signals an Exception Code "Slave Device Busy“, (0x06) until either the
data has been processed or the processing time has elapsed. As start address are valid,
e.g. 30.500, 31.500 or 32.500, etc. for the Modicon or 499, 1.499 or 2.499, etc. when access-
ing with your own communication driver.
For further information, please contact one of our employees.
Diagnostic message in RTU mode
Function code 08 (diagnostics) enables the diagnostics of the Modbus-participants through
the Modbus-Master. VEGASCAN supports the Diagnostic Code 0x0000 (return of the data). In
the field "Diagnostic Data“ any approved data can be entered, which are returned unchanged
from the functioning VEGASCAN.
Example of a diagnostic telegram:
The Modbus participant with the Slave address 1 shall confirm the diagnostics data 0xA5,
0x37.