Echelon i.LON SmartServer 2.0 - Manual (Page 190)

i.LON SmartServer 2.0 Programmer’s Reference 13-2
#0000000000000000[0].SNVT_switch
nvoSwitch
#0000000000000000[0].SNVT_switch
0
LonFormat="UCPTcompFunction">FN_NUL
LonFormat="">0
0
DataPointFormat[UCPTnickName=“nviSwitch1”]
state
DataPointFormat[UCPTnickName=“nvoSwitch”]
state
LonFormat="UCPTcompFunction">FN_NUL
1
DataPointFormat[UCPTnickName=“nviSwitch1”]
LonFormat="UCPTcompFunction">FN_NUL
LonFormat="">0
0
DataPointFormat[UCPTnickName=“nviSwitch2”]
value
DataPointFormat[UCPTnickName=“nvoSwitch”]
value
LonFormat="UCPTcompFunction">FN_NUL
13.2 Creating and Modifying the Type Translator Rule XML Files
You can create and manage the Type Translator rules with the Set SOAP function. The following
section, Type Translator Rule SOAP Interface, describes how to use Set and the other SOAP functions
provided for use with Type Translator rules.
Alternatively, you can create the XML files for your Type Translator Rules manually, with an XML
editor, and download them to the SmartServer via FTP. Echelon does not recommend this, as the
SmartServer will require a reboot to read the configuration of the downloaded file. Additionally, the
SmartServer performs error checking on all SOAP messages it receives before writing to the file. It
will not perform error checking on any XML files you download via FTP, and thus the application may
not boot properly.
If you plan to create the XML file manually, you should review the rest of this chapter first, as it
describes the elements and properties in the XML file that define each Type Translator’s configuration.
13.3 Type Translator Rule SOAP Interface
You can use the SOAP interface to perform the following functions on a type translator rule:
Function Description
List Generate a list of the type translator rules on the SmartServer.
Get Retrieve the configuration of the type translator rules on the
SmartServer.
Set Create a new type translator rule, or overwrite the configuration of an
existing type translator rule.