1

Universal Inputs - Setup and Configuration

TECHNICAL BULLETIN

© 2001 Johnson Controls, Inc.

Code No. LIT-TD-2040

johnsoncontrols.com

NexSys 2.1 User’s Guide LIT-TD-2039

Issue Date 08/2001

1. Introduction ............................................................................................... 32. Universal Input Use................................................................................... 4

2.1 Different Input Selection Scenario ....................................................................... 4

2.2 Remote I/O Connection Scenario ......................................................................... 5

3. Universal Input Hardware Setup .............................................................. 53.1 Input Type Selection .............................................................................................. 5

3.2 Hardware Jumper Selection ................................................................................. 6

4. Universal Input SNVT Setup ..................................................................... 74.1 Break Bindings....................................................................................................... 7

4.2 Change NV Type ..................................................................................................... 8

5. Universal Input Software Setup ............................................................. 155.1 SNVT Units Conversion ....................................................................................... 15

5.2 Field Descriptions ................................................................................................ 15

5.3 0-5 Volt Humidity Sensor Example ..................................................................... 16

5.4 4-20 mA Temperature Sensor Example .............................................................. 17

6. Naming the New Universal Input ............................................................ 206.1 Editing Steps ......................................................................................................... 21

Index .............................................................................................................. 25

2Johnson Controls, Inc., reserves the right to update specifications when appropriate. Informationcontained in this document is based on specifications believed to be correct at the time of publi-cation.

NexSys® is a registered trademark of Johnson Controls, Inc. Echelon® and LNS are® registeredtrademarks of the Echelon Corp.

© 2001 Johnson Controls, Inc. All rights reserved.

3

Setup and Configurationof Universal Inputsfor NexSys ASCs

1. IntroductionThe document is an overview of the Universal Inputs of the Heat Pump, Fan Coil Unit,Roof Top Unit, and Packaged Equipment Controller.

This document explains how to:

• set the controller’s hardware input type

• set the hardware jumper settings

• break existing bindings

• change the NV type

• setup and use the LNS Object Browser software

• change the SNVT Id

• convert SNVT units

• name the new Universal Input

4

2. Universal Input UseThe HFRU controller board (Figure 1) is the base hardware platform for the following controllerline: Heat Pump Controller, Fan Controller, Roof Top Controller, and the Packaged EquipmentController. The controller board features 6 analog inputs which are preconfigured from the factory.The first four inputs are Thermistor temperature inputs and the last two are configured as Discrete.These inputs have standard use inside the controller and come preconfigured for the default applica-tion.There are two steps to the input’s setup. The first step is to configure the physical hardware input.The input must be configured to match the electrical equipment to which it is connected. The secondstep is the SNVT type selection. Example: An input could be configured as a current input. How-ever, the field transmitter (the device providing the current signal) could be measuring temperature,humidity, kilowatt-hour usage, or lux (illumination). Both sides must be properly configured tooperate properly.

��� ��� ��� ��� ��� ��� ����������

��

��

����

����

����

�� �� �� �� �� �� ��������������� ��������

��

�������

�

����

�

������

�

�������

����

���

������

�

�������������

���

�� �� � �� �� �

���

��������

���

��������

���

��������

���

��������

���

��������

��� ��� ��� ��� ���

�����

��

���

���

��� !"��

� �# ��$!�

� !%& ��'(

����� !%& ��'(

�$�)'*+

�'(($,�-'(

�%$*.

'!���

�'(($,�-'(

//

�����')$*�(# �

/�(# �! (�0'1

� �# �

/�-1-��0� �# �!

$*2-,$� !%& ��'(

$*2-,$"��

�'(3-1 *��-'(�'*���0 1

4-(+"��

� �# �"��!

���

���

� .#$*!��5���5���5���5��6��(7���

Figure 1 HFRU Controller Board

If you want to connect a different type of input to the controller, then an additional manual setupmust be performed. The following scenarios are possible, but would require some reconfiguration ofthe controller:

2.1 Different Input Selection ScenarioThe first four inputs to the controllers are preconfigured as thermistor temperature inputs. If youhave an existing 4-20 mA outside air temperature sensor that you wanted to wire to the controller,this could be done. Since the input is still being used as a temperature, the SNVT type need not bechanged and the internal control algorithm remains the same. In this case, you would want to changethe hardware input, from a thermistor input to a 4-20 mA input, using the hardware jumpers. Setupwould be restricted to the hardware setup side only.

52.2 Remote I/O Connection ScenarioA controller was installed with a spare input available. Since this input is not being used for thecontrol sequence, it is available for use as a Spare or Remote I/O point. If you want to wire anambient light sensor to the controller, this could be done. Please note that this input will have to bebound to a Flexible System Controller or other controller since the internal algorithm of the ASC isnot designed to handle this type of input, and can do nothing locally with this value. The ASC could,however, send an alarm from this value.

In this case you would have to configure the hardware input to match the physical hardware connec-tion. In addition, the Network Variable associated with the point would need to be changed to reflectthe input type. It would be less meaningful if the hardware input was configured to match (currenttransmitter used with 0-20 mA input), but the light level in lux were sent over a variable whose unitswere degrees Celsius (SNVT mismatch). These must match to make the network side of the systemmore logical and easier to use.

3. Universal Input Hardware SetupThe controller board features 6 analog inputs (Figure 2) which can be configured in the followingmodes:

3.1 Input Type SelectionThere is a software selection for determining the hardware setup. There are initial calcula-tions made inside the controller which are more related to the type of hardware selected. Seebelow:

3.1.1 DiscreteA discrete input has only this input setting. Elsewhere, the input can be configured as aNormally Open or a Normally Closed input.

3.2.2 ThermistorA 10K thermistor is the only possibility here. There are no configuration options required forthis type of input.

3.2.3 VoltageThe voltage input on the controller can only be a 0-5 volt input. If a 0-10 volt input is de-sired, then an external voltage divider must be provided. However, the input can be config-ured for either 0-5 or 0-10 volt input. It does not matter which is selected.

3.2.4 CurrentThe current input on the controller can be configured as a 0-20 mA or a 4-20 mA input. Thisinput should match the field transducer.

63.2 Hardware Jumper Selection

You must set the hardware jumpers (Figure 3) when wiring the field input hardware. This setupprocess assures that the hardware jumper setting and the input point type match. Mismatcheshere could cause problems.

J2

GND I5 I4 GND I3 I2 VOUTI1GNDI6

UI1Disharge AirTemp

UI2Mixed AirTemp

UI3Space/ReturnAir Temp

UI4Outside AirTemp

UI5Fan Status

UI6EmergencyShutdwon

J4 J5 J6 J7 J8 J9

�� ��

�� �� �� �� �6 ��

�� �� �� �� �� �� ����������

��

������������

�����������

����������������������������

Figure 2 Factory Set Universal Inputs Figure 3 Jumper Settings

3.2.1 DiscreteThe hardware jumper should be in the Thermistor/Dry Contact position. On the HFRUhardware, this is the center jumper position, and was the default position when the unit wasshipped from the factory.

3.2.2 ThermistorThe hardware jumper should be in the Thermistor/Dry Contact position. On the HFRUhardware, this is the center jumper position, and was the default position when the unit wasshipped from the factory.

3.2.3 VoltageThe hardware jumper should be in the Voltage Input position, which is the bottom position.This is also the jumper position closest to the screw terminal blocks.

3.2.4 CurrentThe hardware jumper should be in the Current Input position, which is the top position. Thisis also the jumper position farthest from the screw terminal blocks.

7

4. Universal Input SNVT SetupThe Network Variable associated with the hardware input must be set. Again, the first four inputs onthe controller are preconfigured temperature inputs, all with the associated NV, which isSNVT_temp_p (#105). The last two inputs are SNVT_switch (#95). In order to proceed with thesetup, the SNVT should be set to the desired type.

4.1 Break BindingsWhen any node is placed on the physical tree, a default set of configuration data is put in place.One of these default settings is the Network Variable Outputs associated with each of the sixphysical hardware inputs are bound inside the controller. These bindings must be broken beforeproceeding. The reason is as follows (assuming the first temperature input).

Example:

The first hardware input is defined as the Discharge Air Temperature. This nvoUnivInput1 isbound to nviDischAirTemp, both having SNVT #105. If you change nvoUnivInput1 to a newSNVT type, with the old binding still in place, you would have two different Network Variablesbound together. For this reason, the binding must be broken to eliminate the above problem. TheBinding Editor will not allow you to change SNVT types with a binding in place.

To delete an existing bind:

1. Right click on the selected node. Select Edit/View Binding from the node pop-up menu.

2. The Binding Editor Window opens (Figure 4). You can view the bindings listed in theBinding Summary window to determine which NVs you will need to select.

Figure 4 Binding Editor

83. Select the NVO you want to delete the bind from.

4. The corresponding NVI will be displayed in the Connects To Window, and the button will be visible. Select the corresponding NVO.

NOTE: Not all binds can be deleted. If the button is grayed out, then that bind cannot be deleted.

5. Click to delete the binding.

6. You will be returned to the Binding Editor. The bind will no longer be displayed

7. Click to close the Binding Editor Window.

4.2 Change NV TypeThis NV setup requires you to use the LNS Object Browser application program. This Echelon®

program is not part of the NexSys software, but is installed along with it. This program is apowerful development tool that, in this case, is used to modify the SnvtId of the desired universalinput of the selected device.

4.2.1 Using the LNS Object BrowserBefore you use the LNS Object Browser, please read the following warning:

Warning: The LNS Object Browser application offers point-and-click access to almost everyobject, method, and property in the LNS Network Operating System. It can be used to manipu-late an LNS-based system by modifying properties and invoking methods.

You must, however, use this tool with extreme caution, and must be familiar with the use of theLNS objects, their properties, and methods. The LNS Object Browser includes minimal safetycode and only requires user confirmation in the most severe cases. Most operations can beperformed without additional confirmation, potentially causing severe malfunction on the net-work or corrupting the LNS network database. Always back up the LNS network databasebefore using the LNS Object Browser with anything other than a test network.

Never attempt to modify an operational network database if you are not an experienced LNSuser.

4.2.2 Minimize NexSys Workstation softwareIt is suggested that you minimize the NexSys Workstation software before running the LNSObject Browser. To minimize the NexSys Workstation and LNServer click on the minimize boxin the upper right corner of the NexSys Workstation window and the LNServer window.

4.2.3 Run LNS Object BrowserNOTE: You should only run the Object Browser from the server PC.

The LNS Object Browser application (LnsObjectBrowser.exe) is typically found in the C:\LONWORKS\BIN directory.

9To run the LNS Object Browser:

1. Double-click the LNS Object Browser icon. A Startup Preferences screen displays (Figure 5).

2. Change the Startup Preferences settings, on the General tab screen, from Don’t Change to Bea Full Client and Local, then check the Save as Default box (Figure 6). All other tabs in theStartup Preferences can be left to their defaults.

Figure 5 Default Preferences Figure 6 New Startup Preferences

3. Click on the OK button to save the changes and open the Object Browser (Figure 7).

Figure 7 Object Browser Read Only ModeNOTE: The Object Browser always starts in a “Read Only” mode. Before you can editthe universal inputs you must set the browser mode to Read/Write.

4. Click on the Options heading, then click the Allow Modifications option. The mode willchange from Read Only to Read/Write (Figure 8).

Figure 8 Object Browser Read/Write Mode5. Navigate the tree and begin the editing process.

104.2.3 Navigate the Tree

You will be required to navigate a series of nested objects to get to the device that has the univer-sal input you want to modify. Once you navigate to the desired device, you must select thedevice’s specific universal input, either input 1, 2, 3, 4, 5, or 6. Next you select the universalinput’s SNVT to modify the universal inputs SNVT ID.

Double-click the ObjectServer icon to display the tree (Figure 9)

.

Figure 9 ObjectServer Tree - Level 1

Double-click Networks (Figure 10) to open the tree to display a list of available networks. Next,double-click on the Network that has the device you want to edit. This example network name isLNS3 (Figure 11).

Figure 10 Available Networks Figure 11 Desired Network LNS3

11Double-click on the Systems to display the Network (Figure 12). Next, double-click on thenetwork name again (Figure 13). This example network name is LNS3.

Figure 12 Systems Icon Figure 13 Network Icon

12Double-click on Subsystems (Figure 14). Next double-click on the All (Figure 15).

Figure 14 Subsystems Figure 15 All

13Double-click on AppDevices (Figure 16). Next, double-click on the hardware device that has theuniversal input you want to edit (Figure 17). The example device is HPU-01 Building 9.

Figure 16 AppDevices Figure 17 Desired Hardware Device

14Double-click on Interface (Figure 18). Next, double-click on NetworkVariables (Figure 19) todisplay the available universal inputs.

Figure 18 Interface Figure 19 NetworkVariables

4.2.4 Select the NV desiredDouble-click the nvoUnivInput(x), where x is the number of the universal input you want tomodify. Universal Input 1 is used in this example. Next, in the window on the right, scroll downand double-click on SnvtId to display the editor (Figure 20).

Figure 20 nvoUnivInput1 With SnvtId Highlighted

154.2.5 Change the SNVT

Click in the New Value area of the editor and enter the new SNVT value (Figure 21). In thisexample we changed from a SNVT_temp_p SNVT 105 to a SNVT_lev_percent SNVT 81(Figure 22).

Figure 21 SnvtId Editor Before Changes (105) Figure 22 SnvtId Editor After Changes (81)

Check the Fully rebuild property list box, if you want the changes to be implemented immedi-ately.

Check the Keep editor open box, if you want to edit other inputs.

Click OK to complete the editing process.

5. Universal Input Software SetupLastly, the software must be configured to finish the point setup. The following is a detailed expla-nation of the setup of each configuration field.

5.1 SNVT Units ConversionSNVT unit conversion is somewhat mathematically intensive. You must pay close attention tothe SNVT documentation as numerical values are entered. Since the data fields in this setup areunit-less, all conversions must be done as the data is entered. Please carefully read the back-ground information, and also refer to the two sample scenarios.

5.1.1 Scale ValueBefore beginning, please get the most recent SNVT documentation. This is fundamentaldocumentation that is required before proceeding. The SNVT Master List and Programmer’sGuide is a good reference guide. It is available on the Echelon web site and also on theLONMark website. In the SNVT documentation, each Standard Network Variable Type isfully described. Most important is the RESOLUTION of the value.

If this resolution is inverted, this will result in a Scale Factor which will be referred tothroughout this section. Listed below are several common SNVTs, their associated resolu-tion, and their scale factors. Refer to Echelon® documentation for the complete list.

SNVT_lev_percent SNVT=81 Resolution=0.005 Scale Factor=200SNVT_temp_p SNVT=105 Resolution=0.01 Scale Factor=100SNVT_freq_hz SNVT=76 Resolution=0.1 Scale Factor=10SNVT_lux SNVT=79 Resolution=1 Scale Factor=1SNVT_flow SNVT=15 Resolution=1 Scale Factor=1SNVT_ppm SNVT=29 Resolution=1 Scale Factor=1

165.2 Field Descriptions5.2.1 Send on Delta

The Send on Delta value determines how much the input must change (in SNVT units)before the data is rebroadcast. This is also effected by the Min and Max Send Timers (notdescribed within this document). The Send on Delta is always a positive value. Again, thisvalue must be entered in SNVT units. However, the value being entered into

5.2.2 ZeroThe Zero is used in conjunction with the sensor Span (below). This is used to adjust thesensor’s offset. The below examples will provide more insight into the use of this field.

It should be noted that this field is not scaled with the same value as other fields. In thisregard, Zero and Span are unique (and also different with respect to each other). A specialdivisor value associated with Zero is: 200. This will be described below.

5.2.3 SpanThe Span is used in conjunction with the sensor Zero (above). The span is declared as theentire range of the sensor from lowest to highest value. The below examples will providemore insight into the use of this field.

It should be noted that this field is not scaled with the same value as other fields. In thisregard, Zero and Span are unique (and also different with respect to each other). A specialdivisor value associated with Span is: 2000. This will be described below.

5.2.4 Calibrate OffsetThe Calibrate Offset is used to adjust the sensor to achieve a calibrated value. For example,if many of the same kind of sensors are installed, the Zero and Span (above) will all beidentical. The setup of the sensors is the same. However, each individual unit differs slightlyfrom a field-calibration reference unit. Each sensor is calibrated to the reference sensor withthe Calibration Offset.

5.2.5 High Alarm LimitIf the input exceeds the High Alarm Limit, an alarm message will be generated.

5.2.6 Low Alarm LimitIf the input falls below the Low Alarm Limit, an alarm message will be generated.

5.2.7 Alarm HysteresisThe Alarm Hysteresis determines how much the input must return inside the alarm limitbefore the alarm condition is cleared.

5.3 0-5 Volt Humidity Sensor ExampleIn this example, we will assume that there is a 0-5 volt sensor which is measuring humidity inpercent. Therefore, the final sensor output will be in SNVT_lev_percent units (SNVT #81). Forthis particular sensor, 0 volts corresponds to 0% relative humidity, and 5 volts corresponds to100% relative humidity.

For the balance of this section, keep in mind that SNVT_lev_percent is used to communicaterelative humidity. The SNVT is a Signed 16-bit value, but has a range/resolution from –163.84% to 163.83%. It is impossible for Relative Humidity values to go negative so only therange 0% to 100.00% applies in this case. However, the full range of the SNVT always appliesto the mathematics. In both cases, the SNVT has a resolution of 0.005%.

Looking in the table enclosed, take the resolution of 0.005 and invert it. The result is 200. Thisis now the Scale Factor for the remaining conversions. Any value desired must be scaled up by200 to get it into SNVT units.

175.3.1 Send on Delta

If a value of 2.5% is required for the Send On Delta value, the resulting value is 2.5 * 200 =500. Enter this into the field.

5.3.1 ZeroIn this case, when the sensor is at zero volts, the output value is also zero. In this case, theymatch, so the value of 0 is applied to this field. The following example requires calculationof this value.

5.3.3 SpanSince the sensor should output 100% when the sensor is at full-scale output of 5 volts, theSpan is calculated to be: 100% * 200 = 20,000. However, the Span value is a scaled value.Divide this result by 2000 and enter it as 10.000. Enter this into the Span.

5.3.4 Calibrate OffsetFor example, the sensor installed is 10 years old. A field-calibration unit is brought in andmeasures the relative humidity to be exactly 65%. However, the sensor has experiencedsome drift and measures 70%. Therefore, the value needs to be calibrated down by 5%. Tocalculate the value, multiply: -5% * 200 = -1000. Enter this into the Calibrate Offset field.

5.3.5 High Alarm LimitFor this system, if the relative humidity reaches greater than 80%, the system operators mustmake some manual adjustments to the cooling towers to maintain optimal system efficiency.To alert the operators, 80% is entered: 80% * 200 = 16,000. This is entered into the HighAlarm Limit field.

5.3.6 Low Alarm LimitIf a Low Alarm Limit is required, it is calculated in the same fashion. In this case 20% isrequired so: 20% * 2000 = 4000. This is entered into the Low Alarm Field

5.3.7 Alarm HysteresisIn this case, 2.5% is the desired hysteresis. Once the alarm is registered, the humidity mustdrop 2.5% below the High Alarm Limit in order to come out of alarm. The calculation is:2.5% * 200 = 500. This is entered into the Alarm Hysteresis field (Figure 23).

Figure 23 Alarm Hysteresis - 0-5 Volt Humidity Sensor

185.4 4-20 mA Temperature Sensor Example

In this example, we will assume that there is a 4-20 mA temperature sensor which is measuringthe Outside Air Temperature. Therefore, the final sensor output will be in SNVT_temp_p units(SNVT #105). For this particular sensor, 4 mA corresponds to –20C, and 20 mA corresponds to40°C.

For the balance of this section, keep in mind that SNVT_temp_p is used to communicate relativehumidity. The SNVT is a Signed 16-bit value, but has a range/resolution from –273.17 to327.66°C. The sensor fits within the range of the sensor, so this will work. The SNVT has aresolution of 0.01°C.

Looking in the table enclosed, take the resolution of 0.01 and invert it. The result is 100. This isnow the Scale Factor for the remaining conversions. Any value desired must be scaled up by100 to get it into SNVT units.

5.4.1 Send on DeltaIf a value of 0.1C is required for the Send On Delta value, the resulting value is 0.10 * 100 =10. Enter this into the field.

5.4.2 ZeroIn this case, when the sensor is at 4 mA (the lowest sensor output), the sensor is measuring –20°C. Therefore, the output of the sensor must be skewed down by 20°C. Calculate the Zerovalue according to: -20 * 100 = -2000. However, remember that the Zero has the specialdivisor of 200. Divide this result by 200: -2000 / 200 = -10

5.4.3 SpanThe span of the sensor is from –20 to 40°C. This results in a span of 60C for the entiresensor. This results in the span calculation of: 40 –(-20) * 100 = 6,000. However, the Spanvalue has a special divisor. Divide this result by 2000: 6000 / 2000 = 3.000. Enter this intothe Span.

5.4.4 Calibrate OffsetThis sensor is new and requires no calibration. If it were required, it would be done as theother calculations: 0 * 100 = 0. Enter this into the Calibrate Offset field.

5.4.5 High Alarm LimitThe outside air temperature has a High Alarm Limit of 30°C. The value is determined: 30 *100 = 3000. This is entered into the High Alarm Limit field.

5.4.6 Low Alarm LimitThe outside air temperature has a Low Alarm Limit of –5°C. The value is determined: -5 *100 = -500.

5.4.7 Alarm HysteresisIn this case the temperature has an Alarm Hysteresis of 1.11°C. The calculation is: 1.11 *100 = 111. This is entered into the Alarm Hysteresis field (Figure 24).

19

Figure 24 Alarm Hysteresis - 4-20 mA Temperature Sensor

20

6. Naming the New Universal InputAfter you have changed the universal input type, it will still retain its old name. To avoid confu-sion you should change the input’s name to a correct descriptor. This process requires you tooverwrite the old name, one character at a time, by entering the decimal equivalent of the ASCIIletter/number of the name. NV name length is limited to a maximum of 30 characters. Decide onthe new name, then, using the ASCII chart (Figure 25), enter the new decimal values, one in eachASCII String array element location.

NOTE: If the old name is longer than the new name, then, after entering the last character, youmust enter a nul (digital 0) to close the string and not display the remaining characters. The nulmust be entered in the very next ASCII String array element location.

IICSA lamiceD IICSA lamiceD

lun 0 U 58

ecaps 23 V 68

% 73 W 78

0 84 X 88

1 94 Y 98

2 05 Z 09

3 15 a 79

4 25 b 89

5 35 c 99

6 45 d 001

7 55 e 101

8 65 f 201

9 75 g 301

A 56 h 401

B 66 i 501

C 76 j 601

D 86 k 701

E 96 l 801

F 07 m 901

G 17 n 011

H 27 o 111

I 37 p 211

J 47 q 311

K 57 r 411

L 67 s 511

M 77 t 611

N 87 u 711

O 97 v 811

P 08 w 911

Q 18 x 021

R 28 y 121

S 38 z 221

T 48

Figure 25 ASCII Chart

216.1 Editing Steps

1. Navigate the NexSys tree to the nvoUnivInput(x), where x is the number of the universalinput you want to rename (Figure 26). This example uses nvoUnivInput1 of the device HPU-01 Building 9. The factory default name of this point is UI1 Discharge Air Temperature In thisexample, the new name will be UI1 % Relative Humidity.

Figure 26 SCPT Location

The factory default name chart (Figure 27), and the new name chart (Figure 28) compare thedecimal equivalent of each ASCII character entered. Notice that, since the old name is 5 charac-ters longer than the new name, the old name’s decimal values are still present. Placing a nulcharacter after the last character of the new name, ascii(23) String array element slot in thisexample, ends the string and doesn’t display any further characters.

22Factory Default Name

ASCII(#) Screen Decimal

ascii(0) U 85

ascii(1) I 73

ascii(2) 1 49

ascii(3) Space 32

ascii(4) D 68

ascii(5) i 105

ascii(6) s 115

ascii(7) c 99

ascii(8) h 104

ascii(9) a 97

ascii(10) r 114

ascii(11) g 103

ascii(12) e 101

ascii(13) Space 32

ascii(14) A 65

ascii(15) i 105

ascii(16) r 114

ascii(17) Space 32

ascii(18) T 84

ascii(19) e 101

ascii(20) m 109

ascii(21) p 112

ascii(22) e 101

ascii(23) r 114

ascii(24) a 97

ascii(25) t 116

ascii(26) u 117

ascii(27) r 114

ascii(28) e 101

ascii(29) Space 32

ascii(30) nul 0

Figure 27 Factory Default Name Chart

New Name

ASCII(#) Screen Decimal

ascii(0) U 85

ascii(1) I 73

ascii(2) 1 49

ascii(3) Space 32

ascii(4) % 37

ascii(5) Space 32

ascii(6) R 82

ascii(7) e 101

ascii(8) l 108

ascii(9) a 97

ascii(10) t 116

ascii(11) i 105

ascii(12) v 118

ascii(13) e 101

ascii(14) Space 32

ascii(15) H 72

ascii(16) u 117

ascii(17) m 109

ascii(18) i 105

ascii(19) d 100

ascii(20) i 105

ascii(21) t 116

ascii(22) y 121

ascii(23) nul 0

ascii(24) a 97

ascii(25) t 116

ascii(26) u 117

ascii(27) r 114

ascii(28) e 101

ascii(29) Space 32

ascii(30) nul 0

Figure 28 New Name Chart

Note: The nul in ascii(23) ends the string andall characters after the nul don’t display.

232. Click on the SCPT of the selected NV to display the ASCII screen of the NV’s name (Figure29). Note that there is a Command column and a Status column. All entries are made in the

Command column. The Status column will display any changes after clicking the button.

Figure 29 SCPT Location ASCII Editor3. Enter the new name’s first letter’s decimal value into the ascii(0) String array element Com-mand column slot (Figure 29).

4. Enter the new name’s second letter decimal value in the ascii(1) String array element location.

5. Continue this process until you have entered all decimal values of the name, one for eachASCII string location. For naming purposes, the last entry possible is for the ascii(29) Stringarray element.

6. After entering the decimal value of the last character of the new name, enter a 0 in the verynext ascii String array element location to close the name string.

8. Ascii(30) String array element is used to close the name string, in the event the name uses allthirty characters, and must always have a digital value of 0. Changing this value will cause thenew name to not display and could produce undesired system results.

9. Click the button to save the name changes. Changed string values will be re-flected in the Status column on the right.

10. You must close the node and reopen it for the new name to appear.

24

25

Universal Input IndexSymbols

0-5 Volt Humidity Sensor Example 16Alarm Hysteresis 17Calibrate Offset 17High Alarm Limit 17Low Alarm Limit 17Send on Delta 17Span 17Zero 17

4-20 mA Temperature Sensor Example 18Alarm Hysteresis 18Calibrate Offset 18High Alarm Limit 18Low Alarm Limit 18Send on Delta 18Span 18Zero 18

D

Different Input Selection Scenario 4

F

Field Descriptions 16Alarm Hysteresis 16Calibrate Offset 16High Alarm Limit 16Low Alarm Limit 16Send on Delta 16Span 16Zero 16

H

Hardware JumperCurrent 6Discrete 6Thermistor 6Voltage 6

Hardware Jumper Selection 6

I

Input TypeCurrent 5Discrete 5Thermistor 5Voltage 5

Input Type Selection 5Introduction 3

R

Remote I/O Connection 5

S

SNVTUnits Conversion 15

Scale Value 15

U

Universal InputHardware Setup 5SNVT Setup 7

Break Bindings 7Change NV Type 8

Software Setup 15Universal Input Use 4

Universal Inputs- Setup and Configuration1. Introduction 2. Universal Input Use 2.1 Different Input Selection Scenario2.2 Remote I/O Connection Scenario

3. Universal Input Hardware Setup 3.1 Input Type Selection 3.2 Hardware Jumper Selection

4. Universal Input SNVT Setup 4.1 Break Bindings 4.2 Change NV Type

5. Universal Input Software Setup 5.1 SNVT Units Conversion 5.2 Field Descriptions 5.3 0-5 Volt Humidity Sensor Example 5.4 4-20 mA Temperature Sensor Example

6. Naming the New Universal Input 6.1 Editing Steps

Universal Input IndexSymbols0-5 Volt Humidity Sensor Example Alarm Hysteresis Calibrate Offset High Alarm Limit Low Alarm Limit Send on Delta Span Zero

4-20 mA Temperature Sensor Example Alarm Hysteresis Calibrate Offset High Alarm Limit Low Alarm Limit Send on Delta Span Zero

DDifferent Input Selection Scenario

FField Descriptions Alarm Hysteresis Calibrate Offset High Alarm Limit Low Alarm Limit Send on Delta Span Zero

HHardware JumperCurrent Discrete Thermistor Voltage

Hardware Jumper Selection

IInput TypeCurrent Discrete Thermistor Voltage

Input Type Selection Introduction

RRemote I/O Connection

SSNVTUnits Conversion Scale Value

UUniversal InputHardware Setup SNVT Setup Break Bindings Change NV Type

Software Setup

Universal Input Use