The developer's resource for computer interfacing, especially USB, serial (COM) ports, mass storage, and embedded networking. (Formerly

Home > Articles > Device Controller

Control Your Devices from a Web Page

Jan Axelson

Use any Web browser to monitor and control your devices.

This article originally appeared in Nuts & Volts.

Of all of the millions of pages on the Web, most are hosted by large servers or at minimum, desktop PCs. But these aren't the only computers that can function as Web servers. Even very small devices can serve Web pages on request, including pages that display real-time information and respond to user input. The pages can be available within a local network or you can add an Internet connection and make the pages available to anyone on the Internet.

The Device Controller described in this article is a small circuit board that controls external circuits and also functions as a Web server. Users can access a Web page to monitor and control the Device Controller's circuits.

The Device Controller is based on a TINI module, which contains a CPU (central processing unit), networking support, and a Java runtime environment that enables the TINI to run Java programs. The TINI was developed by Dallas Semiconductor, a subsidiary of Maxim Integrated Products.

The Device Controller's Web page, which displays a virtual control panel:

From this page, users can click buttons to turn two LEDs on and off. After clicking a button, the browser's Web page updates to match the states of the LEDs.

In a similar way, you can program a TINI to monitor and control other circuits or processes and use a Web page to enable users to request data from the TINI and control the TINI's circuits.

Partner Links

About the TINI

Two options for the TINI module are the DSTINIm400 ($67) from Dallas Semiconductor:

and the TStik ($99) from Systronix:

The CPU in both boards is a Dallas Semiconductor DS80C400 Network Microcontroller. Each module plugs into an evaluation board that contains components and connectors for a power supply, RS-232 serial port, and Ethernet networking. The TStik has an on-board Ethernet transceiver, while the DSTINIm400's Ethernet transceiver is on the evaluation board (the DSTINIs400).

Creating the Device Controller software, compiling it, and deploying it to the TINI requires a variety of software tools. All are free downloads.

The TINI Software Developers Kit (SDK), available from Dallas Semiconductor, includes the TINIOS operating system and the Java Virtual Machine (JVM) that executes Java programs in the TINI. Dallas Semi also provides the JavaKit utility for configuring the TINI over its RS-232 serial port.

To compile Java programs for a TINI, you can use just about any Java compiler and Java development system, including the compiler in the free Java Development Kit (JDK) from Sun Microsystems. I use Borland's JBuilder environment, which includes a compiler and graphical interface for developing. A free Personal Edition is available. The Ant build tool and the TINI-specific add-on TiniAnt are useful for compiling code and deploying it to the TINI.

A Java application called a servlet engine enables the TINI to run Java programs called servlets, which can serve Web pages that contain real-time information and respond to mouse clicks and other user input. The servlet engine I used for the Device Controller is Shawn Silverman's Tynamo Web server, which is free for personal use.

The complete DeviceController servlet code and instructions for running it are available from my Web site at For loading files into the TINI and testing the Web server on a network, you'll need a PC with an RS-232 serial port and an Ethernet network port.

Why use Java? The Java language is designed from the ground up for use in networking applications, and the support built into the TINI's software greatly simplifies network programming. If you're not an experienced Java programmer, an introductory text will get you started. The TINI supports an older, simpler, but still very capable JDK distribution (1.1.8).

(If you prefer to program in C instead of Java, my Web site also has a Device Controller project written in C for Rabbit Semiconductor's RabbitCore modules.)

The Web Page

Listing 1 is the HTML source code of the page a browser might receive on requesting the Device Controller's Web page. The text between angle brackets (<>) contains HTML code that tells the Web browser how to display the text and images on the page.

The page includes four images. Ledon.gif and ledoff.gif are images of lit and unlit LEDs. The images reflect the states of the Device Controller's LEDs when the page was requested. The other two images are identical switches, or buttons (button.gif), which users click to toggle the LEDs.

When a user clicks a button's image, the browser's computer uses the Hypertext Transfer Protocol (HTTP) to send a GET request over the network to the Device Controller. If the user clicks the first LED's button, the request contains the text /servlet/DeviceController?button1. The /servlet/DeviceController portion of the request tells the Device Controller to run the DeviceController servlet. The text following the question mark tells the Device Controller which button the user clicked (button1 or button2).

Serving the Web Page

On receiving a request to run the DeviceController servlet, the TINI executes the doGet() method in Listing 2. One of the parameters passed to the method is an HttpServletRequest object that contains information about the request. If the user has clicked a button, the object's getQueryString() method contains either "button1" or "button2" to indicate which button was clicked.

If the query string contains button1 or button2, a call to the toggle() method in Listing 3 toggles the state of the corresponding LED. Port bits on the DS80C400 control the LEDs. Led1 is controlled by Port 5, bit 4, and led2 is controlled by Port 5, bit 5:

On the DSTINIs400 board, the bits are accessible from header J21. On the TStik, the bits are contacts 29 and 30 on the SIMM connector. I chose these bits in part because they're easily accessible. The bits also function as part of the SPI interface. which isn't available if you use the bits to control the LEDs. You can program the TINI to control any other I/O bits or peripherals you wish.

In the servlet code, led1 and led2 are BitPort objects in the TINI-specific class com.dalsemi.system.BitPort. The class's readLatch() method returns the last value written to a bit. The set() method sets a bit's value to 1, and the clear() method sets a bit's value to 0.

In Listing 2, after toggling the requested LED, the TINI sets the values of four variables that display the states of the LEDs as images and text on the Web page. The variables led1Image and led2Image each contain a file name ("ledon.gif" or " ledoff.gif"), depending on the state of the corresponding LED. In a similar way, the led1State and led2State variables each contain the text "on" or "off".

A call to the application's SendWebPage() method sends a Web page that displays images and text that match the states of the LEDs on the TINI. A series of out.print statements writes the Web page's contents to the ServletOutputStream object out. The browser that requested to run the servlet receives the Web page in an HTTP response.

This statement in the SendWebPage() method sends the contents of the page's <head> section, which contains the page's title:

out.print("<head><title>Device Controller</title></head>"

In a similar way, out.print statements send the rest of the HTML code that makes up the Web page.

In sending the page, the servlet inserts the file names and text that match the states of the LEDs. This statement places the contents of the led2Image variable (either "ledon.gif" or "ledoff.gif") on the Web page:


And this statement places the contents of the led1State variable (either "on" or "off") on the Web page:

out.print (led1State);

Running the Web Server

Running the servlet requires a series of steps to build the application webserver.tini, deploy webserver.tini and related files to the TINI module, and run the application. The webserver.tini file contains the code for both the Tynamo Web server and the DeviceController servlet.

These are the steps to follow:

1. Download the needed files. The DeviceController files are in, available from The file contains the file DeviceController_readme.htm, which has links to the other files required to build and deploy the Device Controller. Download these as well.

2. Building and deploying webserver.tini uses several configuration files. These are included in You must edit two of these files with information specific to your system.

The file contains the locations of the TINI SDK and the DeviceController servlet. Edit these lines to match the locations on your development PC:

# The location of the TINI SDK:

# The location of the servlet (

Use forward slashes (/) as separators in the paths, even under Windows.

The file contains information about the TINI. Edit these lines to match the information for your TINI:

# The TINI's IP address.

# The TINI's user ID and password:

You can view and set the TINI's Internet Protocol (IP) address using the TINI's ipconfig command. In JavaKit, type ipconfig to view the current settings, and type ipconfig help to view the options you can set.

3. To build webserver.tini, run the Ant build tool by opening a command-prompt window on your development PC, changing to the directory where you stored the Tynamo download, and entering ant on the command line. The Ant tool uses the information in the configuration files to find out what to build and where to find the files.

4. Copy the files ledon.gif, ledoff.gif, and button.gif to the http-root directory in Tynamo's home directory.

5. To deploy the Web server to the TINI, connect the TINI to your development PC via Ethernet. For a direct connection, attach a crossover cable directly from the TINI's Ethernet (RJ-45) connector to the PC's Ethernet connector. If your PC connects to an Ethernet repeater hub or switch, attach a straight-across cable between the TINI and an available port on the repeater hub or switch.

At a command prompt on the development PC, type ant deploy. This causes the Web server's files to transfer to the TINI via the File Transfer Protocol (FTP).

6. To run the Web server, in Windows' Hyperterminal or a similar application, create a Telnet connection with these settings:

Host Address = the TINI's IP address
Port = 23
Connect = TCP/IP

Click Call to connect to the TINI and run the Web server by entering this text in the Telnet window:

source web/bin/WebServer

When the server is running, the Telnet Window will display this text:

HttpServer: Server started.

The TINI is now ready to run the DeviceController servlet.

Accessing the Web Server

On a computer in the same local network as the TINI, in the Address text box of a Web browser, enter http://, followed by the TINI's IP address, /servlet/, and the servlet's name. For example, if the TINI's IP address is, enter this:

You should then see the Device Controller's Web page with images and text that match the states of the LEDs on the TINI module. Click a button and the corresponding LED on the TINI will toggle and the browser will update with a new Web page that reflects the change.

Making the Device Controller Available on the Internet

To access the Device Controller's Web page from the Internet, you need to have an Internet account that permits hosting a server and network-security settings that enable the TINI to receive connection requests on Port 80 (the default port for HTTP) or another port you specify.

Hosting a server may require a business account for Internet access. Accounts offered to home users typically forbid hosting servers because a server may draw more traffic than the provider can support at home-user prices. Some providers block incoming requests to open connections to port 80.

If the TINI accesses the Internet via a dial-up connection, you'll of course need a phone line that's available to the TINI whenever you want the Device Controller to be on line.

If you're wise, you use a firewall to protect your computers that access the Internet. A firewall may be software running on a PC in the local network or a piece of dedicated hardware. If your TINI is behind a firewall, you'll need to configure the firewall to allow the TINI to receive incoming HTTP requests. One way to achieve this is to set up the firewall so that all requests to open a connection to Port 80 are routed to the TINI.

To access the TINI from the Internet, you need to know its public IP address. If you use a firewall with Network Address Translation (NAT), the firewall will use a single public IP address for all Internet communications, converting between the public and local IP addresses as needed. The firewall should have a configuration page that displays its public IP address.

From a browser, you access the Device Controller the same as in a local network, except that you must use a public IP address. If the address is, you would enter this in the browser's Address box:

If the TINI's IP address has an assigned domain name, you can also access the Device Controller using the domain name:

In any case, it's best to check out the Device Controller on a local network before attempting to access it from the Internet.


This basic application can serve as a template for TINIs that perform other monitoring and control tasks and serve Web pages that enable users to view and control the TINI's activities.

My website ( has links to more documentation about the TINI and Tynamo Web Server and how to use them, as well as the complete source code for the Device Controller.


(Ant Build Tool)

(JBuilder Java environment and compiler)

Maxim/Dallas Semiconductor
(DSTINIm400 module)

Rabbit Semiconductor
(RabbitCore modules)

(Java Development Kit)

(TStik module)
(Systronix appears to be no longer in business.)

(TINI add-on for Ant)

(TINI Web server and servlet engine)