Re: [foxboro] ICC field width (was Re: stddisp)
- From: "Douglas G. Lloyd" <DGLControls@xxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Tue, 22 Apr 2008 19:05:22 -0400
Hi All,
Here's another control configuration field length issue: you can't define a
string with more than 32 characters. This is even the case for sequence
block SN00xx parameters which are 80 characters. We originally thought that
this was an IACC issue, but it's a core issue which the ole ICC and iccdrvr
task have also. And, yes, my CAR was closed because the behavior was "as
designed"...
Regards,
Doug Lloyd
DGL Controls
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Corey R Clingo
Sent: Tuesday, April 22, 2008 7:28 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] ICC field width (was Re: stddisp)
That's because you are supposed to "upgrade" to IACC, er, IEE, um,
something that starts with "I".
This CAR is now closed. But the bar is open.
Corey Clingo
BASF Corporation
Sascha Wildner <swildner@xxxxxxxxxx>
Sent by: foxboro-bounce@xxxxxxxxxxxxx
04/22/2008 06:10 AM
Please respond to
foxboro@xxxxxxxxxxxxx
To
foxboro@xxxxxxxxxxxxx
cc
Subject
[foxboro] ICC field width (was Re: stddisp)
foxpat wrote:
>
> Reproduced mentioned problem at our site as well (created a query to
give me
> all PAKIN blocks where Compound + Block length exceeded 22 characters.
Found
> about 10 instances, all showing described problem!)
>
> I submitted a CAR today.
>
> Thanks again for pointing it out!
Speaking of maximum lengths (your mail just reminded me of it), the ICC
will not allow to enter a link that has the maximum number of characters
(which is 42) because the field is only 41 characters wide.
I submitted a CAR about it back in noughty nought, but they didn't even
get my point and it was closed without further action.
Regards,
--
Sascha Wildner
_______________________________________________________________________
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
_______________________________________________________________________
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:
