Re: [foxboro] IA Batch problems

Ken,

Try zeroing the phase command word (most likely II0007) and then re-issuing
the command.  The default old PHASE_EXEC (if that's what you're using) only
processes "new" commands.  If a previous command failed, re-issuing the same
one will be ignored even if all is now OK.

Your unit status and allocation discrepancies might be caused by the file
system reload.  IA Batch is the "master" and won't necessarily re-synch to
what is really happening in the control stations.  You need to make the
control station align with what IA Batch believes before it will behave
properly.

You can use the standard PhaseLogic and ProcStatus tools from the
Environment Display to read/write control station values...

Good luck!

Doug Lloyd
DGL Controls


-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Moore, Kenneth, Celanese/US
Sent: Monday, November 20, 2006 8:25 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] IA Batch problems

I've tried changing the phase status, but doesn't help. Batch isn't
getting any status at all on one unit, and on another Batch has it
allocated, but still shows up as available, shouldn't.=20


Regards,

Ken Moore

Process Controls Specialist
Celanese Emulsions
14355 Hwy. 221
Enoree, SC 29335

864-969-6745 (office)
864-978-9211 (mobile)
864-969-6711 (fax)

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Gabriel ODwyer
Sent: Monday, November 20, 2006 7:48 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] IA Batch problems

Ken, without knowing your configuration, heres a few things I'd check:=20
Try stopping and starting all the runtime applications.
Try validating your IALinker to see if it throws up any problems on that
front.
Try revalidating your recipes.
If you had batches in motion at the time of the lockup, make sure they
are deleted with all units released from them.
If you can identify the phase generating the "waiting on phase status"=20
message, manually set the phase status integers to other valid values
(careful, this may actually run the phase).
Best of luck.
Regards,
Gabriel.


"Moore, Kenneth, Celanese/US" <ken.e.moore@xxxxxxxxxxxx> Sent by:
foxboro-bounce@xxxxxxxxxxxxx
20/11/2006 11:23
Please respond to
foxboro@xxxxxxxxxxxxx


To
foxboro@xxxxxxxxxxxxx
cc

Subject
[foxboro] IA Batch problems






System specs: AW51B, IA ver 6.3, IA Batch ver 5.3 with 4 batch trains
The Story:=20
At about 0400 Saturday morning, IA Batch locked up and would not step=20
through the recipes. Found that /opt partition was 100% full. This is
due=20
to it being full of batch history files. So... I deleted some of the=20
larger H01*.dat files and H02*.dat files. Got /opt down to 87% full.
Then=20
restarted IA Batch.
Upon restart, Batch does not allocate equipment in one of the trains,
but=20
works fine in the other three. In the batch display, it states "waiting
on=20
phase status", the phase is idle, and has the correct codes to show that

it is available.  I called TAC at around 1900 and was told that erasing=20
the H01*.dat files was the cause, I didn't believe this, but it was=20
possible, the problem train was the first installed,  I'll try anything
to=20
get the system back up and running. So yesterday I spent most of the
day,=20
restoring the entire hard drive from a backup tape made in Sept. which
has=20
the /opt partition at 99% full. Then restarted Batch, and I still have
the=20
same problems.

So some how my phases and batch have lost connectivity, does anyone have

any idea what I can do to resolve this? I looked through the IALink
files,=20
and cannot see any differences between the trains that work, and the one

that does not.=20

Also, does anyone know if those HO*.dat files can be removed?  I have=20
history files going back to 2001, I only need to keep about 6 months=20
worth.





Ken Moore
Process Controls Specialist

Celanese
14355 Hwy. 221
Enoree, SC 29335





-- No attachments (even text) are allowed --
-- Type: application/ms-tnef
-- File: winmail.dat


=20
=20
_______________________________________________________________________
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
=20
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe:      =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20



=20
=20
_______________________________________________________________________
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
=20
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe:      =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
 
 
_______________________________________________________________________
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
 

 
 
_______________________________________________________________________
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: