Re: [foxboro] External Reference for Compound:Block.Parameter.Extension in HLBL?

  • From: "Johnson, Alex" <alexander.johnson@xxxxxxxxxxxxxxxxxxxxxx>
  • To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
  • Date: Thu, 15 Jan 2015 15:04:57 -0600

Re: Using bit extensions in HLBL

An HLBL external reference must have this syntax:

      <HLBL Variable> := C.B.P[.qualifier];
or
      <HLBL Variable> := SV;

As you can see, the assignment must have a CBP or SV on the right of the 
assignment operation. The only variation is that there are three specific 
qualifiers that allow the user to extract information from the status word of 
the CBP. These qualifiers are: .BAD, .OOS, and something I don't remember 
off-hand.

Many users believe that the bit extensions used in peer-to-peer communications 
are available everywhere and that's not the case. That belief is incorrect. The 
extensions are not a feature of the OM name. Rather, they are a configuration 
convenience on peer-to-peer connections only. FoxView does not support them and 
neither does HLBL.

When the CP's Block Processor (BP) encounters a bit extension, the BP extracts 
the appropriate information and places it into the input of the control block.

However, the HLBL compiler was not extended to support the bit extensions. It 
supports only the original ones that give access to the CBP's OM status bits.

To help with your challenge, you have two choices:
1) Use a block connection (INxxxx, BIxxxx, etc) with the bit extension and 
access it from within the HLBL code. That works.
2) Write bit extraction logic in CBP of interest in the block's HLBL code. That 
works, too, but it's cumbersome.

Hope this helps.

AJ
_____________________________________________________________________________________

Alex Johnson | Schneider Electric | Invensys | United States | System 
Architect, Next Generation Systems
Phone: +1 713 329 8472 | Fax: +1 713 329 1700
Email: alexander.johnson@xxxxxxxxxxxxxxxxxxxxxx | Site: www.invensys.com | 
Address: 10900 Equity Drive, 77041 Houston, TX, United States

*** Please note my new Schneider Electric email address effective immediately

*** Please consider the environment before printing this e-mail
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On 
Behalf Of Neufeld, Brahm
Sent: Thursday, January 15, 2015 2:34 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] External Reference for Compound:Block.Parameter.Extension in 
HLBL?

All-knowing list,
I have FCS 5.0 (Archestra IDE) and I would like to do some logic with more than 
24 boolean inputs (valve & motor statuses).

I cannot seem to figure out how to use COMPOUND:BLOCK.PARAM.EXT in HLBL, 
specifically the IND block.

For instance, I can define a bool under VARIABLES:
BOOL_VAR : B;
And assign an external reference to it in my STATEMENTS:


The block compiles with this syntax, but IDE shows the block with OP_ERR="-60", 
which B0400DF describes "param does not exist... the full pathname refers to a 
block that exists in the control database, but the parameter with given name 
does not exist in the block". The IND block is held in manual and doesn't do 
anything.

Other familiar IDE syntax like "COMPND.PAKIN_BLK.PAKCIN#B4" refuses to compile.

Any thoughts?

Thanks,

Brahm Neufeld
Process Control Engineer


________________________________
IMPORTANT NOTICE ! This E-Mail transmission and any accompanying attachments 
may contain confidential information intended only for the use of the 
individual or entity named above. Any dissemination, distribution, copying or 
action taken in reliance on the contents of this E-Mail by anyone other than 
the intended recipient is strictly prohibited and is not intended to, in 
anyway, waive privilege or confidentiality. If you have received this E-Mail in 
error please immediately delete it and notify sender at the above E-Mail 
address. Agrium uses state of the art anti-virus technology on all incoming and 
outgoing E-Mail. We encourage and promote the use of safe E-Mail management 
practices and recommend you check this, and all other E-Mail and attachments 
you receive for the presence of viruses. The sender and Agrium accept no 
liability for any damage caused by a virus or otherwise by the transmittal of 
this E-Mail.



_______________________________________________________________________
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 email has been scanned by the Symantec Email Security.cloud service.
______________________________________________________________________

*** Confidentiality Notice: This e-mail, including any associated or attached 
files, is intended solely for the individual or entity to which it is 
addressed. This e-mail is confidential and may well also be legally privileged. 
If you have received it in error, you are on notice of its status. Please 
notify the sender immediately by reply e-mail and then delete this message from 
your system. Please do not copy it or use it for any purposes, or disclose its 
contents to any other person. This email comes from a division of the Invensys 
Group, owned by Invensys Limited, which is a company registered in England and 
Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 
7AW (Registered number 166023). For a list of European legal entities within 
the Invensys Group, please select the Legal Entities link at invensys.com. 
Invensys Limited is owned by the Schneider-Electric Group.

You may contact Invensys Limited on +44 (0)20 3155 1200 or e-mail 
reception@xxxxxxxxxxxx. This e-mail and any attachments thereto may be subject 
to the terms of any agreements between Invensys (and/or its subsidiaries and 
affiliates) and the recipient (and/or its subsidiaries and affiliates).
 
 
_______________________________________________________________________
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: