YASKAWA SPEED7 300S+ CPU 315PN, Руководство пользователя

Страница: 137 / 209

For the cyclic access to the diagnostics data of the system SLIO module 050-1BA00 the
following example may be used in the OB 1:
AN M10.3 'If the reading terminated (BUSY=0) and
AN M10.1 'there is no job triggered (REQ=0) then
S M10.1 'start transfer of record (REQ:=1)
L W#16#4000 'Number of record set (0x4000)
T MW12
CALL SFB 52, DB52 'Call SFB 52 with Instance DB
REQ :=M10.1 'Trigger flag
ID :=DW#16#0018 'Smaller addr. of mixed module
INDEX :=MW12
MLEN :=14 'Length record set 0x4000
'with 1 entry
VALID :=M10.2 'Validity of the record set
BUSY :=M10.3 'Flag job just running
ERROR :=M10.4 'Error bit during read access
STATUS :=MD14 'Error codes
LEN :=MW16 'Length of the read record set
RECORD :=P#M 100.0 Byte 40
'Target (MB100, 40byte)
U M10.1
R M10.1 'Reset REQ
The system SLIO module 050-1BA00 serves for 20 byte diagnostics data. The diagnos-
tics data of the system SLIO module 050-1BA00 have the following structure:
Name: Bytes Function Default
ERR_A 1 Diagnostics 00h
MODTYP 1 Module information 18h
ERR_C 1 reserved 00h
ERR_D 1 Diagnostics 00h
CHTYP 1 Channel type 76h
NUMBIT 1 Number diagnostics bits per channel 08h
NUMCH 1 Number channels of the module 01h
CHERR 1 Channel error 00h
CH0ERR 1 Channel-specific error 00h
CH1ERR…CH7ERR 7 reserved 00h
DIAG_US 4 µs ticker 00h
More information about the diagnostics data may be found in the system
SLIO manual HB300_FM_050-1BA00.
Example OB1
Diagnostics data
System 300S +
Deployment Ethernet communication - PROFINET
PROFINET diagnostics > Diagnostics during runtime in the user program
HB140 | CPU | 315-4PN23 | en | 18-02 137