Re: [foxboro] ICCDRVR.tsk - GET script problem

Dimitris,

I don't think I can help you much, however, I experienced the exact same
problem some months ago. The problem is, no matter how hard I try, I cannot
remember what I did to solve it!
I loaded a script which runs on a daily base, always with success, onto an
AW70 integrator station with some test blocks in it. The scripts does
basically get all compound and block parameters.
When I ran this script on the AW70 my output file size kept increasing
rapidly and it never stopped. It just seemed to repeat endlessly.

I'am not convinced that the iccdrvr.tsk does not contain bugs.

One thing to check maybe is if you have any empty compounds.

We faced another problem not to long ago where FoxCAE, when downloading, did
not create the proper modify icc script. Somewhere along the line FoxCAE
uses the LIST command to retrieve all C:B's but for some reason the
resulting list was incomplete. When writing our own most basic icc script
with the LIST command we noticed the same problem. The only thing that was
special about is was that the last compound in the resulting list was empty,
although other empty compounds were processed without problem (compounds
after these did appear in the output file).
Using GET *:* did get ALL C:B's.
We solved this problem by adding a dummy block in the empty compound
concerned, after which the problem moved down to yet another empty compound
(although, again other empty compounds were in between). So we added a dummy
block in this compound as well.

We use these empty compounds to 'segregate' sections within our offline test
system CP's so we know which engineer put them there, preventing other
engineers from deleting development blocks of somebody else.
The naming convention for these empty compounds is like __PETERSTART__,
__PETEREND__, __JOHNSTART__, __JOHNEND__ etc. 

We've used FoxCAE in the past basically for all our projects and by no we've
generated some 50000 blocks with it without ever having a problem until this
particular instance.

My point is, iccdrvr.tsk may suddenly show unexpected results just due to a
combination of C:B naming/empty compounds etc.
Maybe you could load this CP on a test system, see if you can reproduce your
problem and start deleting sections of compounds to see if it disappears.

I am sorry I can't remember what caused the never-ending dump in my case but
maybe it comforts you a bit that others had this problem as well!

Kind regards,

Patrick Martens,
Process Automation Specialist
Total Raff. Ned. N.V.

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Dimitris Legakis
Sent: vrijdag 20 april 2007 13:51
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] ICCDRVR.tsk - GET script problem

One more clue for you is that the blocks that are repeated appear either 30 
or 31 time. No block appear more or less times than this.
I don't know if that says anything to anyone of you..

Regards,
Dimitris



 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: