2/4/2013 8:28 PM | |
Joined: 1/12/2011 Last visit: 3/13/2024 Posts: 68 Rating:
|
Dear experts! We have a S7 with: Rack0: CPU 317-2 PN/DP + 8x 8BH10-0AB0 Rack 1: 2x 8BH10-0AB0 So, total = 160 output channels to wire-break monitoring. We need to read only wire-break diagnostics (see Byte 9 to 24 - data record 1 - from the attached doc). What is the best: SFC 51: SSL_ID W#16#00B3 (All diagnostics data of 1 module) with a DB block to storage all the 16 channels faults... But, how can I check all these 10 modules if SFC 51 accepts only 4 jobs by project? Or... is SFC 59 (module by module too) better?? Regards Attachment6ES7322-8BH10-0AB0.pdf (549 Downloads) |
Last edited by: Maselo at: 2/15/2013 12:19 PMLast edited by: Maselo at: 2/6/2013 1:11 PMLast edited by: Maselo at: 2/5/2013 7:21 PM |
|
2/14/2013 8:36 PM | |
Joined: 1/12/2011 Last visit: 3/13/2024 Posts: 68 Rating:
|
No ideas???? Ok, I will summarize my question... We know that is possible to use OB 82 with SFC 51, but how to use just one SFC 51 job to check 10 modules if the CPU accepts up to 4 SFC 51 jobs??? Please, see the example of of Module Diagnostics in attached PDF file. Regards. AttachmentSFC 51.pdf (891 Downloads) |
2/28/2013 4:57 PM | |
Joined: 10/10/2005 Last visit: 7/24/2024 Posts: 1917 Rating:
|
Hello, I think it is better to call for each module the system function SFC51 and use for each module an own structured variable. So you can avoid to overwrite one variable with an other diagnosic module. See also an example: http://support.automation.siemens.com/WW/view/de/31895566 With best regards |
3/6/2013 1:32 PM | |
Joined: 1/12/2011 Last visit: 3/13/2024 Posts: 68 Rating:
|
Hello Cicero! I'll take a look to check how it works! Thanks! |
5/21/2013 6:18 AM | |
Joined: 1/12/2011 Last visit: 3/13/2024 Posts: 68 Rating:
|
Hi, all! Please, see these print screens images (inside attached zip file): SFC59 - normal but code 877F.jpg - The CPU and DO cards normal, faulty LEDs off, but SFC59 returns 877F error code (communication). SFC51 - normal no event.jpg - OB82 was not called yet, so no error code. SFC51 - wire break incoming.jpg - SFC51 returns the same 877F (34687) code. SFC51 - wire break outgoing.jpg - SFC51 returns 877F again!!??? I did this test using another CPU (315-2 DP) and the problem kept... Page 23 from "Open TCP/IP Communication via Industrial Ethernet" manual ( http://a248.e.akamai.net/cache.automation.siemens.com/dnl/jM2MTI2NDMA_22146612_DL/T-Bausteine_e.pdf ) 877F - CONNECT parameter: Internal error such as an invalid ANY reference Please, any suggestions??? AttachmentSFC51&59.zip (375 Downloads) |
5/21/2013 4:44 PM | |
Joined: 1/12/2011 Last visit: 3/13/2024 Posts: 68 Rating:
|
Thanks Aret
I used a Siemens manual example for SSL list (See SFC 51.pdf file in the 2nd topic post) . See the OB82_example.jpg from print_screens.zip attached file. I copied this example from the manual "Help on Standard and System Functions" (Example of Module Diagnostics with SFC51 (RDSYSST)) but it not work...
2, see: SZL_HEADER : STRUCT
Yeah!
I will try it!
See the attached files Diagnostics.jpg, CPU_channel_error.jpg and DO_channel_error.jpg from print_screens.zip
Ok, I will check it! Attachmentprint_screens.zip (292 Downloads) |
Follow us on