Re: [foxboro] HLBL Language and missing math functions PER Rejected

  • From: "Brown, Stanley" <stan.brown@xxxxxxxxxxxxxxxxx>
  • To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
  • Date: Tue, 8 Mar 2011 12:30:33 -0500

C programmer hat on:

Usually it's more than just .h files. It is usually linkable object modules 
that implement additional function calls.


> -----Original Message-----
> From: Stan Brown [mailto:stanb@xxxxxxxxx] On Behalf Of Bruley, Peter T
> Sent: Tuesday, March 08, 2011 10:03 AM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] HLBL Language and missing math functions PER
> Rejected
>
> Attempt #2:
>
> And here is the rest of the msg before the Thanks:
>
>
>  Hi Kevin
>
>       So you are saying that you built a program that ran back on your
> AW that did the steam table look up. By doing this you loose Fault
> Tolerant protection and loose a few BPC's because you have to pass
> values back and forth. I would really like to do the lookup every BPC
> and have it run native to the CP.
>
>       The HLBL compiler is basically a stripped down version of a C-
> Compiler. If Foxboro implemented my PER I am sure all they would have
> to add is a couple of header files on the Configurator box. Does anyone
> have experience in writing new functions for HLBL? Do you think this is
> feasible or is it more complicated than that?
>
> Thanks
>
> Peter
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-
> bounce@xxxxxxxxxxxxx] On Behalf Of Kevin Fitzgerrell
> Sent: Thursday, March 03, 2011 5:00 PM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] HLBL Language and missing math functions PER
> Rejected
>
> At the last plant I needed steam tables we used the Physical Properties
> Library and compiled C code.  If memory serves, we also used the
> Process Optimizer which used the C code.
> Regards,
>
> Kevin
>
>
> _______________________________________________________________________
> 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
>


The information contained in this message and any attached files may be 
privileged and/or confidential and protected from disclosure. If you are not 
the intended recipient, any disclosure, copying, distribution or use of any of 
the information contained in or attached to this transmission is strictly 
prohibited. If you have received this transmission in error, please so notify 
the sender immediately without reading it. Also, please promptly destroy the 
original transmission and its attachments. Any views or opinions presented in 
this message or attachments are those of the author and do not necessarily 
represent those of KapStone Paper and Packaging Corporation or its subsidiaries.
 
 
_______________________________________________________________________
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: