Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Module Diagnostics with OB82 and SFC51

Created by: subin at: 2/22/2011 10:31 AM (7 Replies)

Rating (0)

Thanks 4

8 Entries

2/22/2011 10:31 AM	Rate (0)
subin Posts: 84 Rating: (20)	I am trying to integrate CPU and I/O modules Diagnostic to my SCADA to display the faultoccurredat PLC. I had found help on module diagnostic with SFC51 over the help topic on Standard and system functions. I copied the STL source file code and pasted to Source file editor andcompiledbut got 44 errors. STL source file ------------------------------------ DATA_BLOCK DB 13 VERSION : 0.1 STRUCT COME : ARRAY [1 .. 16 ] OF BYTE ; GO : ARRAY [1 .. 16 ] OF BYTE ; END_STRUCT ; BEGIN COME[1] := B#16#0; COME[2] := B#16#0; COME[3] := B#16#0; COME[4] := B#16#0; COME[5] := B#16#0; COME[6] := B#16#0; COME[7] := B#16#0; COME[8] := B#16#0; COME[9] := B#16#0; COME[10] := B#16#0; COME[11] := B#16#0; COME[12] := B#16#0; COME[13] := B#16#0; COME[14] := B#16#0; COME[15] := B#16#0; COME[16] := B#16#0; GO[1] := B#16#0; GO[2] := B#16#0; GO[3] := B#16#0; GO[4] := B#16#0; GO[5] := B#16#0; GO[6] := B#16#0; GO[7] := B#16#0; GO[8] := B#16#0; GO[9] := B#16#0; GO[10] := B#16#0; GO[11] := B#16#0; GO[12] := B#16#0; GO[13] := B#16#0; GO[14] := B#16#0; GO[15] := B#16#0; GO[16] := B#16#0; END_DATA_BLOCK ORGANIZATION_BLOCK OB 82 TITLE = "I/O Point Fault" VERSION : 0.1 VAR_TEMP OB82_EV_CLASS : BYTE ; //16#39, Event class 3, Entering event state, //Internal fault event OB82_FLT_ID : BYTE ; //16#XX, Fault identification code OB82_PRIORITY : BYTE ; //26/28 (Priority of 1 is lowest) OB82_OB_NUMBR : BYTE ; //82 (Organization block 82, OB82) OB82_RESERVED_1 : BYTE ; //Reserved for system OB82_IO_FLAG : BYTE ; //Input (01010100), Output (01010101) OB82_MDL_ADDR : INT ; //Base address of module with fault OB82_MDL_DEFECT : BOOL ; //Module defective OB82_INT_FAULT : BOOL ; //Internal fault OB82_EXT_FAULT : BOOL ; //External fault OB82_PNT_INFO : BOOL ; //Point information OB82_EXT_VOLTAGE : BOOL ; //External voltage low OB82_FLD_CONNCTR : BOOL ; //Field wiring connector missing OB82_NO_CONFIG : BOOL ; //Module has no configuration data OB82_CONFIG_ERR : BOOL ; //Module has configuration error OB82_MDL_TYPE : BYTE ; //Type of module OB82_SUB_NDL_ERR : BOOL ; //Sub-Module is missing or has error OB82_COMM_FAULT : BOOL ; //Communication fault OB82_MDL_STOP : BOOL ; //Module is stopped OB82_WTCH_DOG_FLT : BOOL ; //Watch dog timer stopped module OB82_INT_PS_FLT : BOOL ; //Internal power supply fault OB82_PRIM_BATT_FLT : BOOL ; //Primary battery is in fault OB82_BCKUP_BATT_FLT : BOOL ; //Backup battery is in fault OB82_RESERVED_2 : BOOL ; //Reserved for system OB82_RACK_FLT : BOOL ; //Rack fault, only for bus interface module OB82_PROC_FLT : BOOL ; //Processor fault OB82_EPROM_FLT : BOOL ; //EPROM fault OB82_RAM_FLT : BOOL ; //RAM fault OB82_ADU_FLT : BOOL ; //ADU fault OB82_FUSE_FLT : BOOL ; //Fuse fault OB82_HW_INTR_FLT : BOOL ; //Hardware interrupt input in fault OB82_RESERVED_3 : BOOL ; //Reserved for system OB82_DATE_TIME : DATE_AND_TIME ; //Date and time OB82 started SZL_HEADER : STRUCT LENTHDR : WORD ; N_DR : WORD ; END_STRUCT ; END_VAR BEGIN NETWORK TITLE = //Form parameter INDEX for SFC 51 call: Bit 15 should be set in //#OB82_MDL_ADDR if //a diagnostic interrupt was requested //by an output channel L #OB82_IO_FLAG ; L B#16#54 ; ==I ; //Input? JC go ; //Bit 15 remains unchanged if input present L #OB82_MDL_ADDR ; L W#16#8000; OW ; //Set bit 15 T #OB82_MDL_ADDR ; //Determine whether incoming or outgoing event present go: L #OB82_EV_CLASS ; //Event class and IDs L B#16#39 ; ==I ; //Incoming event? JC come ; //Read out and save diagnostic information L #OB82_MDL_ADDR; T MW 30; CALL "RDSYSST" //Outgoing event REQ := TRUE, SZL_ID := W#16#00B3, INDEX := MW 30, RET_VAL := MW 102 , BUSY := M 101.7 , SZL_HEADER:= #SZL_HEADER, DR := DB13.GO) ; BEU ; come: CALL "RDSYSST" //Incoming event REQ := TRUE, SZL_ID := W#16#00B3, INDEX := MW 30, RET_VAL := MW 102, BUSY := M 101.7, SZL_HEADER:= #SZL_HEADER, DR := DB13.COME); BEU ; END_ORGANIZATION_BLOCK ORGANIZATION_BLOCK OB 1 TITLE = "Main Program Sweep (Cycle)" VERSION : 0.1 VAR_TEMP OB1_EV_CLASS : BYTE ; //Bits 0-3 = 1 (Coming event), Bits 4-7 = 1 (Event class 1) OB1_SCAN_1 : BYTE ; //1 (Cold restart scan 1 of OB 1), 3 (Scan 2-n of OB 1) OB1_PRIORITY : BYTE ; //1 (Priority of 1 is lowest) OB1_OB_NUMBR : BYTE ; //1 (Organization block 1, OB1) OB1_RESERVED_1 : BYTE ; //Reserved for system OB1_RESERVED_2 : BYTE ; //Reserved for system OB1_PREV_CYCLE : INT ; //Cycle time of previous OB1 scan (milliseconds) OB1_MIN_CYCLE : INT ; //Minimum cycle time of OB1 (milliseconds) OB1_MAX_CYCLE : INT ; //Maximum cycle time of OB1 (milliseconds) OB1_DATE_TIME : DATE_AND_TIME ; //Date and time OB1 started END_VAR BEGIN NETWORK TITLE = NOP 0; END_ORGANIZATION_BLOCK Errors ---------- E Ln 000130 Col 008: Syntax error at REQ. E Ln 000130 Col 021: Invalid operation for BOOL. E Ln 000131 Col 008: Symbol SZL_ID not found in symbol table. E Ln 000131 Col 018: Syntax error at :. E Ln 000131 Col 021: Constant with type HEX cannot be used in this statement. E Ln 000132 Col 008: Symbol INDEX not found in symbol table. E Ln 000132 Col 018: Syntax error at :. E Ln 000132 Col 027: Statement not permitted for BYTE/CHAR/WORD/INT/DWORD/DINT/REAL instruction addresse s. E Ln 000133 Col 008: Symbol RET_VAL not found in symbol table. E Ln 000133 Col 018: Syntax error at :. E Ln 000133 Col 024: Statement not permitted for BYTE/CHAR/WORD/INT/DWORD/DINT/REAL instruction addresse s. E Ln 000134 Col 008: Symbol BUSY not found in symbol table. E Ln 000134 Col 018: Syntax error at :. E Ln 000135 Col 008: Parameter SZL_HEADER does not belong to the called block. E Ln 000135 Col 018: Syntax error at :. E Ln 000135 Col 032: Invalid operation for SZL_HEADER. E Ln 000135 Col 032: Variable of a higher type cannot be used in this statement. E Ln 000136 Col 008: Symbol DR not found in symbol table. E Ln 000136 Col 018: Syntax error at :. E Ln 000136 Col 028: Syntax error at ). E Ln 000136 Col 028: Invalid operation for GO. E Ln 000136 Col 028: Variable of a higher type cannot be used in this statement. E Ln 000141 Col 008: Syntax error at REQ. E Ln 000141 Col 021: Invalid operation for BOOL. E Ln 000142 Col 008: Symbol SZL_ID not found in symbol table. E Ln 000142 Col 018: Syntax error at :. E Ln 000142 Col 021: Constant with type HEX cannot be used in this statement. E Ln 000143 Col 008: Symbol INDEX not found in symbol table. E Ln 000143 Col 018: Syntax error at :. E Ln 000143 Col 027: Statement not permitted for BYTE/CHAR/WORD/INT/DWORD/DINT/REAL instruction addresse s. E Ln 000144 Col 008: Symbol RET_VAL not found in symbol table. E Ln 000144 Col 018: Syntax error at :. E Ln 000144 Col 024: Statement not permitted for BYTE/CHAR/WORD/INT/DWORD/DINT/REAL instruction addresse s. E Ln 000145 Col 008: Symbol BUSY not found in symbol table. E Ln 000145 Col 018: Syntax error at :. E Ln 000146 Col 008: Parameter SZL_HEADER does not belong to the called block. E Ln 000146 Col 018: Syntax error at :. E Ln 000146 Col 032: Invalid operation for SZL_HEADER. E Ln 000146 Col 032: Variable of a higher type cannot be used in this statement. E Ln 000147 Col 008: Symbol DR not found in symbol table. E Ln 000147 Col 018: Syntax error at :. E Ln 000147 Col 030: Syntax error at ). E Ln 000147 Col 030: Invalid operation for COME. E Ln 000147 Col 030: Variable of a higher type cannot be used in this statement. Compiler result: 44 Error(s), 0 Warning(s) Can anyone please help me to write program to read diagnostics of CPU and I/O modules so i could integrate the fault messages to my SCADA
subin Posts: 84 Rating: (20)	Last edited by: subin at: 2/22/2011 10:34 AM
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users Chandra Tiwari

2/22/2011 11:21 AM	Rate (0)
Aret Posts: 2348 Rating: (264)	Guess you need "(" when you call SFC51 :^)
Aret Posts: 2348 Rating: (264)
Suggestion To thank Quote Answer

2/22/2011 11:28 AM	Rate (0)
subin Posts: 84 Rating: (20)	helloAret i didn't understood what u said about... hope u understood my problem thanks
subin Posts: 84 Rating: (20)
Suggestion To thank Quote Answer

2/22/2011 12:06 PM	Rate (0)
Chilly_Garfield Posts: 316 Rating: (37)	Aret means, you have to add a "(" after "CALL "RDSYSST" " \| v CALL "RDSYSST" ( //Outgoing event REQ := TRUE, SZL_ID := W#16#00B3, INDEX := MW 30, RET_VAL := MW 102 , BUSY := M 101.7 , SZL_HEADER:= #SZL_HEADER, DR := DB13.GO) ;
Chilly_Garfield Posts: 316 Rating: (37)
Suggestion To thank Quote Answer

2/23/2011 6:22 AM	Rate (0)
subin Posts: 84 Rating: (20)	Thank you very muchChilly_GarfieldandAretfor helping me out.... i am now studying over the program. wish to get more support on making a program to fetch CPU and I/O module faults to SCADA.. Thanks again..
subin Posts: 84 Rating: (20)
Suggestion To thank Quote Answer
This contribution was helpful to 2 thankful Users Aret Chilly_Garfield

1/14/2015 1:29 PM	Rate (0)
Chandra Tiwari Posts: 247 Rating: (2)	Dear Subin, can you forword your backup? i am also doing the same thing wants to show the PLC S7 300 diagnostics on SCADA and working on PCS7. If you will send your backup i will get some idea about my error. I am using SCF51 but i am getting error "-32638" i dont know what it means.
Chandra Tiwari Posts: 247 Rating: (2)
Suggestion To thank Quote Answer

2/8/2015 5:26 AM	Rate (0)
typedat Experienced Member Joined: 5/28/2014 Last visit: 10/21/2024 Posts: 32 Rating: (0)	Hi RaviS I am facing the same problem. did you solve your problem? if yes please help me out. i have copied the STL source file in OB82 and i want to display Diagnostis in my SCADA. Please help me out. Thanks

Suggestion To thank Quote Answer

4/20/2015 2:16 PM	Rate (0)
Navnag Platinum Member Joined: 11/21/2007 Last visit: 9/25/2024 Posts: 2325 Rating: (308)	Hello Please have a look at this : Diagnostic package PNIODiag for diagnostic evaluation for PROFIBUS DP and PROFINET IO (STEP 7 V5.x) A simple possibility for an evaluation of the diagnosis of distributed I/O modules in connection with SIMATIC S7 is needed. The diagnostics evaluation is done both for PROFIBUS DP master systems and also for PROFINET IO systems. https://support.industry.siemens.com/cs/in/en/view/98278878 Components of the diagnostic package PNIODiag The diagnostic package PNIODiag is available to you as a set-up with all the required components. It consists of the following components: Function Block FB126 Visualization Online help This documentation explains the structure of the data of the system and station diagnosis in the two data blocks in the diagnostic package PNIODiag, which allows you to evaluate and process the system and station statuses in the user program, the diagnostic package PNIO determines and displays in the visualization. Function Block FB126 In this documentation, you will find information about which modules you can use with the FB126. The FB126 is available in two variants: S7 block for CPUs with a storage capacity for S7 blocks of > 16 kbyte S7 block for CPUs with a storage capacity for S7 blocks of <= 16 kbyte Visualization The operation and evaluation of the diagnostic is done entirely by means of the visualization. The current diagnostic package PNIODiag contains a visualization for WinCC flexible 2008 SP1. The visualization for WinCC flexible 2008 SP1 supports the languages German and English. Moreover, there are various visualizations for WinCC V7.0. Differentiation occurs by number of monitored I/O systems (1 – 4). Expansion by further I/O systems is possible. Hope this helps Cheers Navnag
	There is no such thing as the last bug in a program There are no stubborn bugs, There are only stubborn Debuggers.
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users stplanken

|

Share this page:

Share this page on...

Follow us on