Program Block Properties

Different program blocks have different configurable properties; not all programming blocks have configurable properties. For detailed descriptions of individual programming block properties look in the Program Blocks section on page  of this manual.

However, all programming blocks have a Ref property and a Name property

Name ► For most blocks, the name of the block is used purely for reference purposes; however, where the block is associated with an object in the LNS database, the name of the block is propagated to the LNS database at compile time.  The names of the following blocks are propagated to the LNS database: AnalogInput, AnalogOutput, DigitalInput, DigitalOutput, PulseInput, Schedule, ScheduleInteger, ScheduleNumeric, ScheduleScene, ScheduleSwitch, TrendDigital, TrendNumeric, TrendInteger, TrendIntegerSample, TrendNumericSample.  As well, the associated network variable of any network variable blocks (such as NvInputNumeric, NvInputInteger, etc.), will be created in the LNS database according to the name assigned to the block in your program.

Ref ► The Ref property is used internally by the program, and Catalyst will automatically assign a unique value to this property; however, you can change this property as well.  The Ref property must use no more than seven letters or numerals. Spaces and punctuation marks cannot be used. For example: ‘Ramp1’ is valid, while ‘Ramp1*’ and ‘Ramp 1’ are not valid.

Index ► For blocks that have an ‘Index’ property, this property associates the block with with a corresponding object on the controller.  For example, the ‘Index’ property of the AnalogInput associates the program block with the physical input on your 400 series controller.  See ‘Associating a Programming Block with a Hardware Point’.

Schedule blocks, NvFanIn blocks, and all of the hardware programming blocks have an Index property: