Re: [foxboro] FDSI blocks
- From: "Johnson, Alex P \(IPS\)" <alex.johnson@xxxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Wed, 29 Aug 2007 19:47:30 -0400
Re: CAR
Yes, I think it is worth a CAR. This behavior seems quite odd.
Regards,
Alex Johnson
Invensys Systems, Inc.
10900 Equity Drive
Houston, TX 77041
713.329.8472 (voice)
713.329.1700 (fax)
713.329.1600 (switchboard)
alex.johnson@xxxxxxxxxxxxxxxx
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Pat Martens
Sent: Wednesday, August 29, 2007 3:15 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] FDSI blocks
Alex,
I have tried setpars and it looks like it has exactly the same problem:
it
is extremely slow for the FDSI blocks!
I have other users confirming this behaviour.
It took about 90 seconds for only 49 RIN blocks (which is also near 2
sec./block)
I need to set (in worst case) hundreds of SIMOPT's and I am just very
surprised that this is so very slow as compared to setting, for
instance,
the IOMOPT's of AIN/CIN/COUT etc.
Also when a FoxCAE download takes a very long time if the value of the
SIMOPT parm is different then that of the block in the CP270, which is
just
very annoying!
The fact that normally a CP270 does it's checkpoint in about 10 seconds
makes the problem of only 1 ICC session on the hosting terminal server
less
of a real problem. We work with several people on 1 project, using the
same
CP preparing most things with FoxCAE so we only 'lock' the CP during a
download which would normally take only about 10 seconds. The SIMOPT
delay
causes (in our case) a CP 'lock' of 10 to 30 minutes!!!
Should I write a CAR ?
Kind regards,
Patrick Martens
Total Raff. Ned. N.V. =
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On
Behalf Of Johnson, Alex P (IPS)
Sent: dinsdag 28 augustus 2007 20:05
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] FDSI blocks
I don't have an answer for your speed difference question, but I do have
a suggestion.
Have you tried /opt/fox/bin/tools/setpars? It won't update the workfile
like the ICC Driver task does, but that seems to be okay for your
application.
Regards,
Alex Johnson
Invensys Systems, Inc.
10900 Equity Drive
Houston, TX 77041
713.329.8472 (voice)
713.329.1700 (fax)
713.329.1600 (switchboard)
alex.johnson@xxxxxxxxxxxxxxxx
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Pat Martens
Sent: Tuesday, August 28, 2007 10:20 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] FDSI blocks
Dear list,
=3D
We are currently preparing a project which involves 6 serial modbus
interfaces through a number of FBM231.
=3D
We have a fully equipped lab-system (nodebus AW51E, CP60, COM30 etc,
ATS,
FCP270, FBM231, terminal server etc).
This system holds only 1 FCP270 so all our preparations are loaded in
this
one CP (approaching the 4000 block limit (-: ).
For testing purposes we have a set_for_sim script which will set the
SIMOPT
to 1 for hundreds of FDSI blocks.
This is were my question relates to: the set_for_sim script is an ICC
script. With this script we notice that setting the SIMOPT for 1 block
takes
about 2 seconds so the complete script takes hundreds of seconds to
finish
(takes about 15 minutes to finish!)
The same script is used, on the same control processor, to set
IOMOPT=3D3D2
for
AIN blocks and IOMOPT=3D3D0 for CIN/COUT & AOUT blocks and these are set
in
an
eye blink !? =3D
=3D
Why does setting a SIMOPT for an FDSI block take so much time?
=3D
The fact that a CP270 normally does a check-point in about 10 seconds is
completely wasted due to this behaviour! (although I must add that I
don't
run the set_for_sim script that often so it's not really causing a
problem).
I'm absolutely NO FAN in regards to FDSI blocks, IMHO they are just not
finished and this only adds to the list of negative points concerning
these
blocks.
=3D
Kind regards,
Patrick Martens
Total Raff. Ned. N.V.
=3D
=3D
=3D
=3D
=3D
=3D
_______________________________________________________________________
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
=3D
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin
to unsubscribe:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave
=3D
Confidentiality Notice:
The information contained in this electronic message and any
attachment(s) =3D
to this message are intended for the exclusive use of the recipient(s)
and =3D
may contain confidential, privileged or proprietary information. If you
are=3D
not the intended recipient, please notify the sender immediately,
delete a=3D
ll copies of this message and any attachment(s). Any other use of the
E-Mai=3D
l by you is prohibited.
=
=
_______________________________________________________________________
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: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=
=
=
_______________________________________________________________________
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: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=
Confidentiality Notice:
The information contained in this electronic message and any attachment(s) =
to this message are intended for the exclusive use of the recipient(s) and =
may contain confidential, privileged or proprietary information. If you are=
not the intended recipient, please notify the sender immediately, delete a=
ll copies of this message and any attachment(s). Any other use of the E-Mai=
l by you is prohibited.
_______________________________________________________________________
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: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
