System information
Table Of Contents
- Table of Contents
- 1 Introduction to the SmartServer SOAP/XML Interface
- 2 SOAP Messages and the SmartServer WSDL File
- 2.1 SmartServer Naming Structure
- 2.2 SmartServer WSDL File
- 2.3 Security
- 2.4 SOAP Request and Response Message Structure
- 2.5 SOAP Messages Formats
- 2.6 Data Point References
- 2.7 UCPTcurrentConfig
- 2.8 Fault Structure
- 2.9 LonString type
- 2.10 SOAP Message Examples
- 3 SmartServer Applications and the SOAP/XML Interface
- 3.1 Overview of SmartServer Applications
- 3.2 SmartServer XML Configuration Files
- 3.3 SmartServer Resource Files
- 3.3.1 Standard Network Variable Type (SNVT) Device Resource Files
- 3.3.2 Standard Configuration Property Type (SCPT) Device Resource Files
- 3.3.3 User Defined Network Variable Type (UNVT) Device Resource Files
- 3.3.4 User Defined Configuration Property Type (UCPT) Device Resource Files
- 3.3.5 Data Point Templates
- 3.3.6 Data Formatting
- 3.4 SOAP Functions
- 3.5 Performance Issues
- 4 Using the SmartServer Data Server
- 4.1 Creating and Modifying the Data Point XML Files
- 4.2 Overview of the Data Point XML File
- 4.3 Data Server SOAP Interface
- 4.3.1 Using the List Function on the Data Server
- 4.3.2 Using the Get Function on the Data Server
- 4.3.3 Using the Set Function on the Data Server
- 4.3.4 Using the Read Function on the Data Server
- 4.3.5 Using the Write Function on the Data Server
- 4.3.6 Using the Invoke Function to Reset Data Point Priorities
- 4.3.7 Data Point Values and Priority Levels
- 4.3.8 Using the Delete Function on the Data Server
- 4.4 Using the Web Binder Application
- 5 Data Loggers
- 5.1 Overview of the Data Logger XML File
- 5.2 Creating and Modifying the Data Logger XML File
- 5.3 Data Logger SOAP Interface
- 6 Alarm Generator
- 6.1 Overview of the Alarm Generator XML File
- 6.2 Creating and Modifying the Alarm Generator XML File
- 6.3 Alarm Generator SOAP Interface
- 7 Alarm Notifier
- 7.1 Overview of the AlarmNotifier XML File
- 7.2 Creating and Modifying the Alarm Notifier XML File
- 7.3 Alarm Notifier SOAP Interface
- 7.3.1 Using the List Function on an Alarm Notifier
- 7.3.2 Using the Get Function on an Alarm Notifier
- 7.3.3 Using the Set Function on an Alarm Notifier
- 7.3.4 Using the Read Function on an Alarm Notifier
- 7.3.5 Using the Write Function on an Alarm Notifier Log File
- 7.3.6 Using the Clear Function on an Alarm Notifier Log File
- 7.3.7 Using the Delete Function on an Alarm Notifier
- 8 Analog Function Block
- 9 Scheduler
- 9.1 Overview of the Scheduler XML File
- 9.2 Creating and Modifying the Scheduler XML File
- 9.3 Scheduler SOAP Interface
- 10 Calendar
- 10.1 Overview of the Calendar XML File
- 10.2 Creating and Modifying the Calendar XML File
- 10.3 Calendar SOAP Interface
- 11 Real Time Clock
- 12 Type Translator
- 12.1 Overview of the Type Translator XML File
- 12.2 Creating and Modifying the Type Translator XML File
- 12.3 Type Translator SOAP Interface
- 12.3.1 Using the List Function on a Type Translator
- 12.3.2 Using the Get Function on a Type Translator
- 12.3.3 Using the Set Function on a Type Translator
- 12.3.4 Pre Defined Type Translator Rules
- 12.3.4.1 16xSNVT_switch_TO_SNVT_state
- 12.3.4.2 SNVT_lev_disc_TO_SNVT_occupancy
- 12.3.4.3 SNVT_lev_disc_TO_SNVT_switch
- 12.3.4.4 SNVT_occupancy_TO_SNVT_setting
- 12.3.4.5 SNVT_scene_TO_SNVT_setting
- 12.3.4.6 SNVT_scene_TO_SNVT_switch
- 12.3.4.7 SNVT_setting_TO_SNVT_switch
- 12.3.4.8 SNVT_state_TO_16xSNVT_switch
- 12.3.4.9 SNVT_switch_TO_SNVT_lev_disc
- 13 Type Translator Rules
- 14 LonWorks Driver
- 14.1 LonWorks Networks
- 14.2 LonWorks Channels
- 14.3 LonWorks Devices
- 14.4 Routers
- 14.5 Remote Network Interface
- 14.6 LonWorks Functional Blocks
- 14.7 Network Variables (LonWorks Data Points)
- 14.8 Configuration Properties (LonWorks Data Points)
- 14.9 LonWorks Connections
- 15 Modbus Driver
- 16 M Bus Driver
- 17 Virtual Driver
- 18 File System Data
- 19 System Information Methods
- 20 Using the SOAP Interface as a Web Service
- 21 Programming Examples
- 21.1 Visual C#.NET Examples
- 21.1.1 Reading and Writing Data Point Values in Visual C# .NET
- 21.1.2 Creating and Reading a Data Logger in Visual C# .NET
- 21.1.3 Creating a Scheduler and Calendar in Visual C# .NET
- 21.1.4 Creating and Installing a LonWorks Device in Visual C# .NET
- 21.1.5 Commissioning External Devices in Visual C# .NET
- 21.1.6 Discovering and Installing External Devices in Visual C# .NET
- 21.1.7 Configuring the SmartServer in Visual C# .NET
- 21.2 Visual Basic.NET Examples
- 21.2.1 Reading and Writing Data Point Values in Visual Basic.NET
- 21.2.2 Creating and Reading a Data Logger in Visual Basic. NET
- 21.2.3 Creating a Scheduler and Calendar in Visual Basic.NET
- 21.2.4 Creating and Installing a LonWorks Device in Visual Basic.NET
- 21.2.5 Commissioning External Devices in Visual Basic.NET
- 21.2.6 Discovering and Installing External Devices in Visual Basic.NET
- 21.2.7 Configuring the SmartServer in Visual Basic.NET
- 21.1 Visual C#.NET Examples
- 22 Programming the SmartServer with Java
- Appendix A: SOAP Tester Example

i.LON SmartServer 2.0 Programmer’s Reference
4-3
• The data points on the SmartServer’s internal automated systems device (i.LON App), which
contains the functional blocks representing the SmartServer’s built-in applications, are stored in a
Dp.xml file in the root/config/network/Net/LON/iLONApp directory on the SmartServer flash
disk by default.
• The data points for an external L
ONWORKS digital input/output device connected to the
SmartServer might be stored in a Dp.xml file in the root/config/network/Net/LON/DIO-2
directory on the SmartServer flash disk.
• The data points on the SmartServer’s internal systems device (i.LON System), which contains
Interoperable Self-Installation (ISI) data points and data points containing connection manager and
LonTalk statistics, are stored in a Dp.xml file in the root/config/network/Net/VirtCh/iLONSystem
directory on the SmartServer flash disk.
• Note: The directories containing the Data Server’s Dp.xml files also contain separate
<driver>_Dp.xml files in which the data points’ driver properties are stored. The properties in
these files relate to a specific bus—L
ONWORKS, Modbus, M-Bus, Virtual, or FPM—and not the
Data Server. These driver-specific properties and how to use the List, Get, Set, and Delete
functions on them are described in Chapters 14–17.
You can manage the Dp.xml files manually using an XML text editor, and download them to the
root/config/network/<network>/<channel>/<device> directory of the SmartServer
via FTP. Echelon does not recommend this, as the SmartServer will require a reboot to read the
configuration of the downloaded XML files. Additionally, the SmartServer performs error checking
on all SOAP messages it receives before writing to the XML files. It will not perform error checking
on any XML files you download via FTP, and so the application may not boot properly.
However, if you plan to create or modify any XML files manually, you should review the rest of this
chapter first. This chapter describes the elements and properties in the Data Server configuration files
that define each data point’s configuration.
4.2
Overview of the Data Point XML File
The Dp.xml files on the SmartServer store the configurations of the data points that you have added to
the SmartServer under their respective parent network/channel/device directories. Each data point is
signified by an <Item> element of a Dp_Cfg type in the XML file. The configuration properties
contained in each <Item> element define the configuration of a data point, and are described later in
this chapter.
You can create new data points using the Set function, or by manually editing the Dp.xml file. You
can read the current value and status of a data point using the Read function, and you can write updated
values to data point using the Write function.
The following code represents a snippet of a sample Dp.xml file with one data point of an external
L
ONWORKS digital input/output device connected to the SmartServer:
<iLonItem>
<UCPTfaultCount>0</UCPTfaultCount>
<Item xsi:type="Dp_Cfg">
<UCPTname>Net/LON/DIO-3/Digital Output[0]/DO_Digital_1</UCPTname>
<UCPTannotation>Dp_In;xsi:type="LON_Dp_Cfg"</UCPTannotation>
<UCPThidden>0</UCPThidden>
<UCPTlastUpdate>2008-03-17T16:00:02.202-07:00</UCPTlastUpdate>
<UCPTdescription>Digital value to output</UCPTdescription>
<UCPTformatDescription>#0000000000000000[0].SNVT_switch</UCPTformatDescription>
<UCPTlength>2</UCPTlength>
<UCPTdirection LonFormat="UCPTdirection">DIR_IN</UCPTdirection>
<UCPTunit field="value">% of full level</UCPTunit>
<UCPTunit field="state">state code</UCPTunit>
<UCPTbaseType LonFormat="UCPTbaseType">BT_STRUCT</UCPTbaseType>
<UCPTmaxFields>2</UCPTmaxFields>
<SCPTmaxSendTime>0.0</SCPTmaxSendTime>
<SCPTmaxRcvTime>0.0</SCPTmaxRcvTime>