ZL0119-0F
Page 24 of 34
©2019 Veris Industries USA 800.354.8556 or +1.503.598.4564 / [email protected] 0119
Alta Labs, Enercept, Enspector, Hawkeye, Trustat, Aerospond, Veris, and the Veris ‘V’ logo are trademarks or registered trademarks of Veris Industries, L.L.C. in the USA and/or other countries.
Other companies’ trademarks are hereby acknowledged to belong to their respective owners.
TM
E50F2A, E50F5A Installation Guide
Configuring and
Commissioning
Without the Plugin
This section covers working with an E50 device when the plugin cannot be used (LNS not used or no plugin director/launcher).It is
not possible for this document to detail the full instructions for configuring and commissioning an E50 device using each and every
network integration tool or controller. The purpose of this section is merely to provide guidelines and clarify the options available
for configuration.
Using Resource Files
If manufacturer scoped resource files can be used, download the Veris E50 Resource File Set at www.veris.com, under Design
Resources -> Protocol -> LonWorks. These files aid in configuration by enabling the configuration properties to be named and
formatted correctly.
Creating the Device Template
The device interface (.XIF/.XFB) files must be used for the network variables to be correctly named. A device template created from
the device itself will only have NV indices rather than NV names. Download the device interface files at www.veris.com, under
Design Resources -> Protocol -> LonWorks. Once downloaded, extract the .XIF and .XFB files from the zip and create a device
template from either of them.
Configuring the Device
All of the user-defined configuration properties are implemented as configuration network variables so that they can be set as
either configuration properties or as input network variables. This allows the E50 device to be configured by either a network
integration tool (using either method) or by peer devices such as controllers (using the input network variables). The base types
for all of the configuration properties are also either SNVT_count or SNVT_state, so they may have the correct names and formats
without the resource files installed. If the names, types, and formats are not available, the configuration property table in this
document has both the base SNVT type and the user defined configuration property type (UCPT) index that the device template
references. These are given in the Configuration Property table as the name LonMaker reports, “UCP_Type_1” for user defined
type 1.
Formatting Power Correctly
LonMark Resource Files before version 13.04 default to formatting SNVT_power_f network variables in units of Btu/hr in the
U.S. This formatting results in power values being reported about 3.4 times higher than they actually are in Watts. Be sure
that the formatting for power values is in Watts. If LNS is used, changing the format of these power network variables to
SNVT_power_f#SI resolves the issue. If any other devices have input network variables bound to the E50’s power output network
variables, the formatting of the input network variables on these devices must also be changed. Installing the latest LonMark
Resource Files (if upgradable for the integration tool/ controller) also resolves the issue when using LNS. They can be found at
www.LonMark.org under “Technical Resources”-> “Resource Files”.
