Industry Online Support
Technical Forum
9/29/2010 1:14 AM | |
Joined: 5/26/2010 Last visit: 1/9/2012 Posts: 6 Rating: (0) |
We're using a S7-317 as a communication master polling 16 S7-200 RTUs through Ethernet radios(317 uses onboard Ethernet port, 200 uses CP-243). We defined 16 connections in NetPro and all are OK/connected after reboot. 317 normally triggers GETblock one by one(e.g. every2 seconds) and triggers PUT block(s) under certain conditions. Originally wehad 1 GET block and 3 PUT block per RTU anddidn't use Enable(EN) bit of GET/PUT(always enabled).All 16 GETs were OKbut we got Error status of 0x14(20d) for PUT blocks of RTU 8 and higher. Error status couldn't be reset until we rebooted 317. Then we added trigger bit(used for REQ) as enable bit for those PUT blocks and seemed to be able to write to all 16 RTUs successfully. Further tests showed that if we trigger a single write for each RTU fast enough(e.g every 3 seconds), we saw the 0x14 error status again on RTU 8 or higher. Now we added trigger bit as enable bit for those GET block as well and lookslike the only way togenerate the 0x14 error is to trigger more than one PUT block of a RTU at the same time and do that one by one for more than 7 RTUs(we've tried to wait 20 seconds between RTUs). Again once thatstatus is ON, it can't be cleared until a 317 reboot(can't write to that RTU anymore w/o a reboot). We're planning to combine those 3 PUT blocksinto one. We did some research and believe the error means "Maximum number of parallel jobs/instances exceeded". Based on Siemens doc(https://support.automation.siemens.com/WW/llisapi.dll?func=cslib.csinfo&objId=22385333&ehbid=15364953&query=CP+343%2DIT+email&load=treecontent&lang=en&siteid=csius&aktprim=0&objaction=csview&extranet=standard&viewreg=WW), "If this number(16) of parallel jobs is exceeded, these jobs are permanently closed with an error and the status=20d" Several questions: [schnippschnapp] Is a job active when a GET/PUT block is enabled or whenit's triggered? [schnippschnapp] other questions are splitted to What's the meaning of parallel jobs?. Is there anyway to see how many parallel jobs running on the PLC?. Is that true that the 20d status can''t be reset until PLC is rebooted?. This is the 1st time we use S7 PLCs on a telemetry job and we've done many jobs using other PLCs(AB, Modicon...). Maybe we're not programming it per Siemens recommendations/rules. If someone could shed some light on it I'd really appreciate it. |
Last edited by: O_Moderator at: 9/30/2010 1:14 PMnew subject after splitting |
|
9/30/2010 9:12 PM | |
Joined: 12/22/2006 Last visit: 1/25/2022 Posts: 1742 Rating: (308) |
Hello, The S7-317 support 16 connections and 32 instances. If for each GET and each PUT you use a separate Instance DB, I believe that you are above the 32 possible instances. From the manual at p.362 Note S7-300: You can change the parameters in the addressing parameters ID and R ID while they are active. The new parameters are validated with each new job after the previous job has been closed. Here, you can link multiple FB pairs in one instance. Tip: You have the following possibilities to save instance DBs and therefore working memory: 1. With variable IDs you can use several connections via one data instance block. 2. With variable R_IDs you can define several identities of pairs of send and receive FBs for one job. 3. You can combine case 1 and case 2. at p.398 With SFB/FB 15 "PUT," you can write data to a remote CPU. S7-300: The data is sent on a rising edge at REQ. The parameters ID, ADDR_1 and SD_1 are transferred on each rising edge at REQ. After a job has been completed, you can assign new values to the ID, ADDR_1 and SD_1 parameters. By applying this (using one instance DB for 3 PUT jobs that you trigger in sequence), I have the feeling that you will reduce the number of instances. Let us know. |
Last edited by: jklm at: 9/30/2010 9:14 PMBest regards |
|
Follow us on