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
3-3
3.3
SmartServer Resource Files
There are many configuration properties you can configure with the SOAP functions described in this
document. This document provides a general description of each property, and other information you
will need when configuring each one, such as minimum and maximum values for scalar properties, and
maximum string lengths for string properties. This information is also contained in the SmartServer
resource files. In order to successfully send a SOAP message to the SmartServer, all data in the
message must be formatted as described in this document and in the resource files.
The SmartServer resource files are added to the LNS resource file catalog by the SmartServer software
installation utility, but they also exist locally on the SmartServer. In fact, like LNS, the SmartServer
maintains a catalog of resource files to use when formatting data in SOAP messages, network variable
updates, and web tag data from the SmartServer web server.
You can use the Node Builder Resource Editor, which is included on the SmartServer software
installation CD, to create new resource files for your own custom data point types and formats. Note
that when creating custom resource files on a PC, it is common to organize the files into subdirectories
such as:
C:\LonWorks\Types\User\YourCompany\YourResourceFiles.*
When adding these files to the SmartServer, it is the best practice to FTP them to a location on the
SmartServer flash disk matching the path on your computer:
/root/lonworks/types/User/YourCompnay/YourResourceFiles.*
You only need to FTP your own custom resource files to the SmartServer. If the name of your file set
is "MyResourceFiles", then you must copy every file which starts with the name "MyResourceFiles".
After you have copied these files to the SmartServer you must reboot to be able to use the new type
definitions and formats. During boot the SmartServer reads the resource files in this directory and
updates its local catalog accordingly.
3.3.1
Standard Network Variable Type (SNVT) Device Resource Files
SNVT device resource files describe the data structures within LonMark
®
SNVTs, and the formats
used to display SNVT data. On the SmartServer, you can find these files in the
/root/lonworks/types directory. They are named STANDARD.ENU, STANDARD.TYP,
STANDARD.FMT, and STANDARD.FPT.
The default format for a SNVT is its native format, as described in STANDARD.FMT. When you
add a data point to the SmartServer, you will assign that data point a format type. If a specific SNVT
format is desired for a particular data point, the <UCPTformatDescription> of that data point must be
set to the name of that SNVT format.
You can browse the entire SNVT device resource files online at
http://types.lonmark.org.
3.3.2
Standard Configuration Property Type (SCPT) Device Resource Files
This is a set of files that describes the data structures within SCPTs, and also describes the formats
used to display SCPT data. On the SmartServer, these files can be found in the directory
/root/lonworks/types directory. These files are named STANDARD.ENU,
STANDARD.TYP, STANDARD.FMT and STANDARD.FPT.
Many configuration properties that are used by the SmartServer applications are based on the SCPTs
defined in these files. The information provided in this document, and in the SCPT resource files, will
help you determine what values to assign to the SCPTs referenced by the SmartServer.
You can browse the entire SCPT device resource files online at
http://types.lonmark.org.