How to use EES without LNS for Fast Data Log Transfer? (KB1066)

You can use EES without a LNS Server to do Fast Data Log Transfer for SmartServers in Standalone Network management mode.  Fast Data Log Transfer is used to do Web Binding with attachments in order to periodically send data logs

In some cases you may want to have a LNS Network but you may want to transfer data logs to another PC other than the PC with the LNS Server. In this case you will have EES on two PCs. One EES, on the LNS Server PC, is used for Synchronization between the SmartServer (LNS mode) and the LNS Server.  The second EES without LNS is used only for data log transfer.

EES without LNS for Fast Data Log Transfer:

1. Verify that EES 2.0 has been installed on your computer running. See Chapter 1 of the Echelon Enterprise Services 2.0 User's Guide for how to perform this installation.  DO NOT INSTALL LNS SERVER or its Service Packs (SPs)

2. Verify that the device resource files for the subject data points are installed on your EES 2.0 computer. You can install the standard LONMARK resource files 3.14.02 on your EES 2.0 computer by installing the Echelon NodeBuilder Resource Editor from the i.LON SmartServer 2.0 DVD (see Installing Echelon NodeBuilder Resource Editor in Chapter 2 for how to do this). You can manually copy any user defined resource files to the LonWorks\types\user\<company> folder on your EES 2.0 computer. 

3. Create a Web connection between the SmartServer and the LNS Proxy Web service running on your EES 2.0 computer. (see Creating the Web Connection in Standalone Mode below).

4. Add a Data Logger or add an Alarm Generator and Alarm Notifier to your SmartServer and configure it. See Chapter 6 of for more information on configuring Alarm Generators and Alarm Notifiers, and see Creating a Data Logger earlier in this chapter for configuring data loggers.

5. Attach an alarm or data log file to the Web connection.

6. Configure a method for triggering updates to the source data point in the Web connection to which the data log file is attached.

7. View the extracted data log files.

Creating the Web Connection in Standalone Mode

To create a Web connection with the SmartServer running in standalone mode, follow these steps:

1. Add a WebBinder Target Server to the LAN in the SmartServer Web interface. To do this, follow these steps:
a. Right click the LAN icon at top of navigation pane, point to Add Host, click Server.
b. Click the Host option, and then enter IP address of your computer, which must be running the LNS Proxy Web service and LNS Turbo Server 3.2 (or newer).
c. Right click the server icon, point to Add Service, then and click WebBinder Target on the shortcut menu.
d. The Setup - Web Service Web page opens.
e. Enter the following properties:
" In the SOAP Path property, enter /LnsProxy/LnsProxyService (this is the SOAP path to the Echelon Enterprise Service running on your computer).
" In the HTTP Port property, enter the port on your computer used for accessing the Echelon Enterprise Service (80 by default).
" In the SOAP User Name property, enter the user name for logging into the Echelon Enterprise Service. The default user name is ilon.
" In the SOAP Password property, click Change Password, enter and re enter the password for logging into the Echelon Enterprise Service, and then click OK. The default password is ilon.
Note: If you changed the default user name and password for logging into EES 2.0, you can use the EES 2.0 tray icon in the notification area to check the current user name and password. See Chapter 3 of the Echelon Enterprise Services 2.0 User's Guide for more information on viewing and changing the Echelon Enterprise Service user name and password.
f. Click Submit.

2. From the navigation pane in the left frame of the SmartServer Web interface, right click an arbitrary source data point in the SmartServer tree and then click Add Binding in the shortcut menu. This example adds a SNVT_switch dynamic data point to the SmartServer i.LON App device's Virtual Functional Block (Net/LON/iLON App/VirtFB/nvoDlTrigger).

3. The Configure - WebBinder Web page opens and the hostnames of the local SmartServer and the WebBinder Target Server you added to the LAN in step 2 appear in the application frame to the right. The host devices in the right frame are collectively referred to as WebBinder Destinations.

4. From the Webbinder Destinations tree on the right frame, expand the WebBinder Target Server and then click *** Target ***. A reference to the target data point ( ) is added underneath the source data point in the SmartServer tree in the left frame.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk