[foxboro] Load MESH FCP Using iccdrvr.tsk and Print File format

To All,
     I wanted to summarize the problem that I had so it may be of some
benefit to someone in the future.  My problem did stem from the fact
that the ICCAPI task had already been registered/associated with the
FCP I was trying to load.  The problem wasn't with the input file I
was trying to use.
    It is possible/likely that I created the problem with the registry
myself as I was attempting to execute the correct syntax for the
iccdrvr.tsk function I wanted to perform.  Sean Redmond's suggestion
of using sipc to veryfy my problem produced this abbreviated result:

cd /opt/fox/bin/tools
sipc
list dt

romload_srvr     OL6704
OL2408           ICCAPIFCP002

     The ICCAPIFCP002 entry is the one that caused my error and as
Sean said, he doesn't know how to reset it by any other means than by
rebooting the host AW.  I assume, when all goes well with the
iccdrvr.tsk it registers and unregisters correctly but if things die
an untimely death during execution the registry gets hung up.  Our
Foxboro project team provided me with the latest SAVEALL of the CP
databases I was trying to load here in Hawaii on our training FCP and
I was able to do a CP LOADALL from within the standard ICC application
to get the desired results.  The moral of the story is don't mess up
while trying to use iccdrvr.tsk or you might have to reboot the AW to
fix it ;<)

Mele Kalikimaka,
Tom VandeWater
Control Conversions Inc.
Tesoro Hawaii Project Manager

Tom,

Looks like the IPC task name has already been registered.  Try running
sipc to see if you currently have a process registered with something
like ICCAPI[CPNAME]
cd /opt/fox/bin/tools
sipc
list dt

If your CP is in the list somewhere something else has not released
the IPC name.  I think the control configurator uses a different IPC
name from my memory(MTBF=10 minutes), which is why you can use the
control configurator.

If this is your problem the news is I do not know how to fix it other
than a reboot, but it is windows!  You might be able to trace the pid
of the ipc name.  type dt ICCAPI[CPNAME] in the sipc window and it
gives you information about the process.  The PID might be HEX from
that same dodgy memory.

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