Video Instructions for Using the i.LON 100
15 Minutes to i.LON Vision Web Page Success
An instructional video showing how to quickly build web pages that display data from the i.LON 100 e3 Internet Server.
View now :15 Minutes to i.LON Vision Web Page Success
i.LON Vision Site Structure
An instructional video providing the essential background information for the i.LON Vision site structure.
View now :i.LON Vision Site Structure
i.LON Vision Menu Elements
An instructional video illustrating the use of the menu element.
View now :i.LON Vision Menu Elements
Setup with console
The i.LON 100 can be configured either from its console, or from the
built-in web page after doing a security access reset (SAR). This video
shows you how to use the console. Using the console requires a null-modem
cable (like the i.LON 1000) and HyperTerminal. 9600/8/n/1
Video file: i.LON
100 No1 - Setup with console.zip
Software install and firmware update
The i.LON 100 firmware can be updated using standard internet FTP.
Video file:
i.LON 100 No2 - Software install and firmware update.zip
Using i.LON 100 RNI
The i.LON 100 is known for its "web" applications like scheduling,
alarming and data logging, but it also can act as a remote network interface
(RNI). This is very helpful if for example you need to run LonMaker from
your office and manage devices at a remote site. Watch this video to learn
now to setup and use the RNI feature of the i.LON 100.
Video File: i.LON
100 No3 - Using i.LON 100 RNI.zip
Sending logs via email
The i.LON 100's 10 built-in data loggers can hold many days of information.
That information can be retrieved through one of the i.LON 100's built-in
web pages, using FTP, by using the i.LON 100's SOAP interface, or as this
video points out, by just having the i.LON 100 send you the data log as
an email attachment. This video series also demonstrates setting up a
simple alarm condition, using a type translator, the various log styles,
and the setup required to define an SMTP server as well as other email
attributes.
Video File:
i.LON
100 No4 - Sending logs via email - part 1.zip
i.LON
100 No4 - Sending logs via email - part 2.zip
i.LON
100 No4 - Sending logs via email - part 3.zip
i.LON
100 No4 - Sending logs via email - part 4.zip
i.LON
100 No4 - Sending logs via email - part 5.zip
Connecting to the Enterprise
The i.LON 100 exposes each of its internal applications and all of its
data points through a SOAP/XML web services interface. This may be the
perfect technology choice for interfacing with Enterprise systems. Part
1 of this video series describes a real world scenario where connecting
a control system to the enterprise saved a company millions of dollars
annually. Part 2 describes what web services are and the standards that
regulate them. Part 3 shows how to write a simple VB.NET application
that consumes a public web service to get a stock quote. Part 4 shows
how the same programming paradigm applied to the i.LON 100 allows you
to read a data point and a data log.
Video File:
i.LON 100 No6 - Connecting to the Enterprise - part1.zip
i.LON 100 No6 - Connecting to the Enterprise - part2.zip
i.LON 100 No6 - Connecting to the Enterprise - part3.zip
i.LON 100 No6 - Connecting to the Enterprise - part4.zip
Store LonMaker DB on the i.LON 100
Use the i.LON 100 as a repository to store a backup copy of your LonMaker
database.
This video shows you step by step how to backup your LonMaker drawing and
database and store it on the i.LON 100's FLASH disk. In this manner, the
database remains on-site and is always available to maintenance personnel.
Video File: i.LON 100 N07 - Store LonMaker DB on the i.LON 100.zip
Using an i.LON 100 Internet Server to create web pages for a pre-installed or self-installed network
Before an i.LON 100 Internet Server web page can be created, NVL or NVE tags must be created on the i.LON 100 Internet Server. This is simple and quite transparent if the network is installed with LonMaker, but more complicated and time consuming if you have to manually create i.LON 100 Internet Server configuration files. This video shows you how to connect a PC running LonMaker to an installed LonWorks network, recover information about the existing devices, add an i.LON 100, create NVE points, and create a web page displaying the points.
Video File:
i.LON 100 No 8 - Using an i.LON 100 with a self-installed network - Part 1.zip
i.LON 100 No 8 - Using an i.LON 100 with a self-installed network - Part 2.zip
i.LON 100 No 8 - Using an i.LON 100 with a self-installed network - Part 3.zip
Using the SOAP Tester
The i.LON 100 exposes its functionality through a web services interface. This SOAP/XML interface is commonly accessed using development environments like .Net and J2EE, but can also be accessed from a web page using JavaScript. This video profiles a handy utility for interacting directly with the i.LON 100's web services interface using just a web browser.
Video File: i.LON 100 No9 - Using the SOAP Tester.zip
Using the E2 M-BUS Driver
Version e2 of the i.LON 100 adds support for M-BUS devices. M-BUS is a European metering standard used in water, gas, and electric meters. This video shows how to attach to an M-BUS device, and how to setup the M-BUS driver to report values from the meter. Also covered is how to convert M-BUS data types to SNVT compatible data types. This unique i.LON 100 Internet Server capability allows M-BUS devices to interoperate on a LonWorks network. The network integrator doesn't need to learn M-BUS nomenclature or M-BUS installation tools. Once the M-BUS device is integrated by the i.LON 100 Internet server, the integrator's existing LonWorks knowledge is sufficient to bring up the system.
Video File: i.LON 100 No 10 - Using the E2 M-BUS Driver.zip
Reference File: M-Bus Integration Type Translator Rules for the i.LON 100 e2
Using the web page NV browser
The i.LON 100 e2 firmware contains many enhancements. This video highlights the e2's built-in network variable browser. The browser is implemented in a web page so it is accessible from anywhere.
Video File: i.LON 100 e2 No 11 - Using the web page NV browser.zip
Categorizing Data Points Using Locations
Locations allow you to group network variables for easy access. This video shows how to organize your network variables into logical groups making easy to find and manipulate.
Video File: i.LON 100 e2 No 12 - Categorizing Data Points Using Locations.zip
Using i.LON 100 e2 WebBinding to "push" NV updates over the Web
The i.LON 100 e2 firmware can be configured to use web binding to "push" network variable updates over HTTP from within corporate networks to public web servers. This allows multiple sites with i.LON 100's that reside behind corporate firewalls to pass information to a central monitoring center without the need to modify firewall security. In essence the i.LON 100 acts like a person browsing a web page from inside the corporate network - only instead of requesting web pages, or submitting a search request, the i.LON 100 sends network variable updates to the web server.
This video series shows you how to build a web service using VB.NET that accepts the i.LON 100's incoming web bind. It also shows you how to configure the i.LON 100 e2 to send an update to your web service. Once the web service receives the update it can be written to a database, handed off to a desktop dashboard - whatever your application requires......
Source Code File: i.LON 100 e2 No 13 - WebBinding to "push" NV updates over the Web.zip
Video File: i.LON 100 e2 No 13 - Part 1 WebBinding to "push" NV updates over the Web.zip
Video File: i.LON 100 e2 No 13 - Part 2 WebBinding to "push" NV updates over the Web.zip
Video File: i.LON 100 e2 No 13 - Part 3 WebBinding to "push" NV updates over the Web.zip
Pulse Counters, Type Translators, Recurring Events & Data Logging
This video demonstrates how to use an i.LON 100 e2 Internet Server's type translator to generate a periodic event. (i.LON 100 e2 type translators can do far more than just translate types!) The periodic event is then hooked up to one of the i.LON 100's relay outputs to create a series of one second pulses. The relay output of the i.LON 100 is wired to one of the i.LON 100 e2 pulse counter inputs to simulate an electricity, water or gas meter. The video then demonstrates how to setup a pulse counter to count pulses and log the simulated power usage to one of the i.LON 100 e2's built-in data loggers.
Video File: i.LON 100 e2 No 14 - Pulse Counter, Type Translator, Recurring Events, Datalog - Part 1.zip
Video File: i.LON 100 e2 No 14 - Pulse Counter, Type Translator, Recurring Events, Datalog - Part 2.zip
Video File: i.LON 100 e2 No 14 - Pulse Counter, Type Translator, Recurring Events, Datalog - Part 3.zip
i.LON to i.LON Web Bind
The video shows how to use an i.LON 100 e2 Internet Server to push network variable updates to an exposed web service. Previously, we have implemented the receiving web service on a PC, but did you know that an i.LON 100 e2 Internet Server can push an NV update over HTTP to another i.LON 100 e2 Internet Server? Watch this video to learn how.
This is a great way to connect two completely separate networks together. Imagine building #1 installed on domain 88 and building #2 (located anywhere) installed on domain 33af2e - two completely separate networks - two separate LonMaker databases - yet information is shared simply by configuring a few parameters in an i.LON 100 e2 Internet Server web page.
Video File: i.LON 100 e2 No 15 - Web Binding i.LON to i.LON - Part 1.zip
Video File: i.LON 100 e2 No 15 - Web Binding i.LON to i.LON - Part 2.zip
Using turnaround web binds to translate LonWorks types
One of the great things about LonWorks is that type integrity between any two connections is preserved automatically by the protocol and the binding tools. This prevents nonsensical binds like connecting a voltage output to a speed input.
There are times however, when it is useful to connect two different types -- connecting SNVT_switch to SNVT_lev_desc for example often makes sense. The most common way to make these kinds of type translations is to use the type translator blocks included in LonPoints(tm) or in the i.LON 100 Internet Server, however, i.LON 100 e2 Internet Server web binds can also be used for type conversion.
Watch these videos to learn how to take advantage of this great new e2 feature.
Video File: i.LON 100 e2 No 16 - Using turnaround Web Binds to translate type - Part 1.zip
Video File: i.LON 100 e2 No 16 - Using turnaround Web Binds to translate type - Part 2.zip
Using NodeUtil to create NVE tags and add an i.LON 100 e2 to a self-installed network
This video demonstrates how to use nodeutil to extract the necessary information from an existing network to create NVE tags that an i.LON 100 e2 can use to monitor and control the existing self-installed network. The preferred way to install an i.LON 100 e2 is to install the entire network using LonMaker, but in some cases that simply is not possible. The next best option is to use LonMaker to recover an existing network and then add an i.LON 100 e2 as described in i.LON 100 No 8 - Using an i.LON 100 with a self-installed network - Part 3.zip, however there are circumstances when that technique won't work -- for example recovering a network installed on the zero length domain. The technique described in this video offers another alternative for using i.LON 100s with non-LonMaker installed networks.
Video File: i.LON 100 e2 No 17 - Using NodeUtil to create NVE tags and add an i.LON 100 e2 to a self-installed network.zip
