Contents
- 1 How does DBDOC affect the ABB system?
- 2 What is a Block?
- 3 My I/O sheets are not labelled correctly. Will this be a problem for building DBDOC?
- 4 How can I relate my files to a particular Loop, PCU and Module?
- 5 What is a Function Code (FC, fcode, code)?
- 6 What is a Spec / Input (specification)?
- 7 Is there an easy way to find changes in specs?
- 8 If we rebuild DBDOC with blocks taken out, how will monitoring show it on an old copy of DBDOC?
- 9 Do we need to have all tag names entered above the block on a CAD? Or will DBDOC do cross-referencing with just PCU, Module, Block number?
- 10 What is the BuildPlus configurator?
- 11 What is Hyperlink?
- 12 What is Decomposer?
- 13 What are slave tags?
- 14 See also
How does DBDOC affect the ABB system?
It doesn't: DBDOC is read-only. Real time monitoring uses the same resources as monitoring with the EWS.
What is a Block?
It is part of the specification process of a process-control point, as in Loop, PCU, Module, Block and is also a drawing element in a CAD file - "struct block".
My I/O sheets are not labelled correctly. Will this be a problem for building DBDOC?
No. We take the loop, PCU and Module from the .mhd file.
How can I relate my files to a particular Loop, PCU and Module?
BuildPlus does not set Loop, PCU and Module information for AutoCAD, Microstation, DXF or text files. BuildPlus will try to figure out the correct Loop, PCU and Module information for various other types of files, including batch (.B90), ladder, and RTU, by:
- Using the loop, pcu and module from the filename if possible
- Overriding with the directory name if it contains a loop, pcu and module.
What is a Function Code (FC, fcode, code)?
A primitive operation in the ABB hardware. Function Codes can appear on CAD EWS drawings, in Composer drawings and in Ladder diagrams. Function Codes have one or more specifications (see specs) - inputs - and one or more outputs.
What is a Spec / Input (specification)?
Specs are the inputs of function codes. Specs must be set at design time - i.e. when the drawing is created. The interpretation of the specs depends on the function code. Specs whose value is a block number are usually used to reference the value of that block.
Is there an easy way to find changes in specs?
If you leave your .vfy files in your CAD directories, DBDOC will build them into your .dbdoc file, so you can see variation between the module as downloaded and what is specified in your sheets. DBDOC does not currently have the ability to track changes in specs between builds. If you are interested in this feature, please contact us at support@gmcl.com.
If we rebuild DBDOC with blocks taken out, how will monitoring show it on an old copy of DBDOC?
Assuming the you have physically removed blocks from your ABB system and rebuilt your DBDOC project, monitoring blocks which have been removed from your ABB configuration will not harm your ABB system. It will merely result in Hyperview displaying red boxes for the blocks it can't retrieve.
Do we need to have all tag names entered above the block on a CAD? Or will DBDOC do cross-referencing with just PCU, Module, Block number?
PCU, Module and Block number are enough to link. DBDOC puts the tag name and description above the block "A" for Attributes in the .dbdoc file.
What is the BuildPlus configurator?
The configurator stage of the build uses the skeleton .RAW file to locate all of your current build source files. This is a transparent step for the user unless you need to specify special LPM for batch, ladder, AutoCAD and/or text files.
Rules for LPM batch, text, etc.
- Will use any internal loop, pcu, module it can find (generally only in batch and ladder files)
- Overridden with LPM from file name if it matches CAD Sheet naming convention
- Overridden with directory name - eg. 20406 Ref Def.B90 - This would be module 20406. This last option of modifying your directory name to include a LPM is the easiest way to apply special loop, pcu, module information to your set of files.
What is Hyperlink?
Hyperlink is the DBDOC compiler, which runs during a build. It analyzes various process control system documents performing the following operations:
- Generates the table of contents and various indexes
- Generates hyperlinks for:
- Tags and document names in ordinary text documents and applications
- Tags and document names in databases
- Tags and blocks, block inputs and outputs, IREFs and OREFs, inter-module inputs and function blocks on CAD drawings
- Tags, trend points and document names in graphics
- Generates metafiles to display CAD drawings and operator graphics
- Generates function block spec and output descriptions
To find out which Hyperlink version you are using, see Learning about this version of DBDOC.
What is Decomposer?
Decomposer is a DBDOC component which extracts .CAD files from Composer .CLD files during a build. For each Composer database processed, a Decomposer folder is created in the project directory.
What are slave tags?
Slave OREF and IREF Tags
- Makes a "slave tag" from the reference text on slave functions
- Allows links to AutoCAD and engineering data sheets for some clients
- Keyed on "link_slave_references"
- In the example, you will see that the "slave tag" <TCSD SYSFAIL> exists and would link to other documents
- noxioref directive stops links on references and may need to be disabled
- In DBDOC, we make names for blocks that come from slaves to Output References, including intervening logic blocks. These labels increase the chance that external documentation links will be made validly.
Module 1,03,13 Block 1325 has been given the tag "TCSD SYSFAIL", even though there is no database record of that name.
See also