Creating a custom scalar-based translation – Echelon i.LON SmartServer 2.0 Power Line User Manual

Page 129

Advertising
background image

i.LON SmartServer 2.0 Power Line Repeating Network Management Guide

115

rule specifies the value to be copied to the output points. Once you create a custom type translator
rule, you can select it from the list of defined rules and use it for other translations.

Creating a Custom Scalar-Based Translation

You can create a custom scalar-based translation with the Type Translator. This is useful if you need
to perform some scaling on the value of the input point before it is translated to the output point. If
you do not need to scale the input point, you can use the pre-defined Copy Input DP to Output DP
translation.

To create a custom scalar-based translation, follow these steps:

1. On the Rule box, click Add Rule.

2. Enter a descriptive name for the new custom scalar-based translation in the dialog that opens and

then click OK.

3. The Type Translator: Rule Web page opens. Click Submit.

4. Optionally, in the Description box, you can enter a description of the type translation.

5. By default, Show Data Point Names is selected, which means that the names of the selected data

points are displayed by location in the following format: network/channel/device/functional
block/data point. Click Show Nicknames to display the programmatic names of the selected data
points, which are much shorter. For example, selecting Show Nicknames abbreviates a data point
with the name Net/LON/Lamp 1/Digital Output/DO_Digital_1 to DO_Digital_1. The graphics in
this section use the Show Data Points Name option.

6. In the Copy rule, the first input and output points added to the type translator are listed to the left

and right of the TO operator, respectively. This means that the values stored in the input point to
the right will always be copied to output point to the left. Note that you do not need to modify the
top-level and second-level cases, which are set to ALWAYS by default, because you are creating
a scalar-based translation.

Advertising