W&T connects
Interfaces for TCP/IP, Ethernet, RS-232, RS-485, USB, 20mA, glass and plastic fiber optic cable, http, SNMP, OPC, Modbus TCP, I/O digital, I/O analog, ISA, PCI

Application for Web-IO Digital, Web-IO Analog and Web-Thermographs:

Web-IO 2Go - access from anywhere to your Web-IO with the Android app for Web-IO

Web-IO ToGO - Android app

Just so you know: What we are presenting here is a project undertaken by our interns. We think the app programmed by our interns is very well done, and are therefore making it available to our customers.

If you would like to learn more about this project and its progress, simply click here.

Our interns are grateful for both critique and praise, and we will be pleased to implement meaningful changes whenever possible.

With this Android app you have access to W&T Web-IO products such as Web-IO Digital, Web-Thermographs, Web-IO Analog and Web-Counters. You can monitor inputs, outputs, temperatures, relative humidity, air pressure, currents and voltages and control digital and analog outputs. After configuring the IP address or the host name, the app determines the Web-IO type and automatically builds the interface appropriate to the device.

Screenshot: Web-IO Android-App


Screenshot: Web-IO Android-App

Device List

Screenshot: Web-IO Android-App

Inputs on a Web-IO Digital

Screenshot: Web-IO Android-App

Outputs on a Web-IO Digital

Screenshot: Web-IO Android-App


Screenshot: Web-IO Android-App

Web-IO Analog

The following steps are needed in order to work with the Web-IO 2Go app: QR-Code Web-IO 2Go App
You don’t have a Web-IO yet but would like to try the example out sometime?

No problem: We will be glad to send you the Web-IO Digital 2xInput, 2xOutput at no charge for 30 days. Simply fill out a sample ordering form, and we will ship the Web-IO for testing on an open invoice. If you return the unit within 30 days, we will simply mark the invoice as paid.

If you would like more details about this project by our interns and its progress, simply click here.

The path to our first Android app

1. Entering new territory
Our interns and students are constantly entering new territory. As a rule, they are accompanied and guided step-by-step by experienced colleagues.

But here there were no experienced colleagues for either the app development or the Java programming, so that both sides, supervisor and intern, entered on this adventure together.

2. Developing capabilities
The goal of study as well as training is to develop a whole set of capabilities so that at the end you are able to handle certain tasks confidently and independently.

At the beginning of our app project we didn’t even know what all had to be learned. To keep from getting bored for weeks with study of the literature and didactic mini-examples, we tried to divide the project into small sub-tasks, so that we could then go right to that first one. In this way we acquired step-by-step all the necessary concepts and methods required for a functioning app.

If you read our diary, the path will seem somewhat without direction, and some of the later corrections would have been unnecessary if we had already "known" it at the beginning. But no matter how you look at it, in the beginning you just don’t know and somehow you just have to go through the experience. But let it also be said that the path of concrete problem solving is an entirely fruitful and satisfying method.

3. Putting together a whole
For educational purposes it’s enough to learn many individual skills. But for a product or service which will actually be sold, a "whole" needs to be assembled which satisfies the requirements of many customers under a variety of conditions. Furthermore, this whole should not be a wild collection of many different functions, but rather totally "simple" - and yet function safely and reliably in thousands of different cases.

Whether our "training app" already meets these requirements is for you to decide. We believe this goal is already nearly achieved.

Now we need your help, your experience reports, your constructive criticism in order to take the last steps, so that you too will be glad every time you control your equipment with this app.

In the learning and development diary you can read which tasks we assigned to ourselves, what solutions we found and how we got closer and closer to a functioning whole:

Week 3 / 2013
  • The first ideas for the Android application emerged
  • The goal was to link Web-IO Digital devices over the WLAN interface of the smartphone
  • After various attempts, crude connection to the devices was possible, but still with problems and crashes and only with Android 2.
Week 4 / 2013
  • Connection errors mostly eliminated
  • Connection handling shifted to a dedicated class, thereby optimized for Android 4
  • First inputs and outputs can be displayed, but no other functions yet
  • Creation of a layout in portrait format
Week 5 / 2013
  • Inputs, counters and outputs are now graphically displayed
  • Application restricted to portrait format, since the app crashes when the cell phone is rotated and landscape format is not yet supported
Week 7 / 2013
  • First tests show that the current layout only works with the 57630 (Web-IO 12xDigital)
  • Layout made dynamic, allowing all Web-IO Digital devices to be linked
Week 8 / 2013
  • First approaches for switching the outputs are built in, but still without other functions such as clearing.
Week 10 / 2013
  • The outputs are now switchable and the corresponding state is displayed
  • Layout revised to simplify switching
  • Outputs are switched in nearly real-time
Week 11 / 2013
  • Clearing of counter states needs to be implemented, layout is modified accordingly
  • After the first attempts errors still occur whereby the wrong counter states are cleared
Week 12 / 2013
  • First error elimination in the layout, whereby counter states are shown at the wrong locations
  • After the errors in the layout are corrected, the correct counters are selected but no longer cleared.
  • Indexing errors in the clearing procedure are fixed. Now the correct counters are selected and the counter states cleared.
Week 14 / 2013
  • Idea for storing multiple Web-IOs and making them selectable
  • Drafting of a layout which shows "saved" devices
  • Save procedure is built into the app
  • Errors occur in which the text file with the data is not correctly saved
Week 15 / 2013
  • After the errors have been fixed, text files with the device data are saved on the smartphone
  • Now the configuration data for the invoked Web-IO are saved in a text file, making invoking of devices simpler
Week 16 / 2013
  • Revision of the layout needed for device selection
  • Function contains an error, whereby the wrong devices are invoked
Week 17 / 2013
  • Function for switching between devices simoplified and revised for display
  • Now connects to the correct devices
  • "Create new" and "Delete" are now possible, though still with some errors
  • Problems with "Create new" and "Delete" functions fixed
Week 21 / 2013
  • The text files are named from a combination of IP or hostname and port
  • File names are not always correct, which results in crashes and errors in the delete procedure
  • Tests are made on various Android smartphones
  • Files are now correctly named, eliminating crashes and errors in deleting
Week 24 / 2013
  • Save-to location now selectable (SD or internal memory)
  • After errors in saving on the SD card, now only the internal memory is supported, external saving is no longer possible
  • Layout for entering devices and the layout of the display for inputs, counters and outputs was revised and optimized
  • After the last error fix one can now link to Web-IO Digital devices without crashes or errors
Week 25 / 2013
  • Expansion of the application to linking to Web-Thermographs
  • Drafting of a layout for Web-Thermographs
  • Linking to these devices is now possible
  • Web-Thermographs are correctly stored and can now also be directly invoked
  • Changing between Web-Thermographs and Web-IO Digital devices is possible with no further problems
  • Measurement values are correctly polled and correctly entered into the layout
Week 26 / 2013
  • Drafting of layouts in landscape format
  • After minor problems have been eliminated, rotating the smartphone now no longer causes problems and functions well
  • Layouts again revised and optimized
  • It is not possible to access Web-IO Digital devices and Web-Thermo devices using the application
Week 27 / 2013
  • New layouts added
  • Tests are made on various Android smartphones to verify functionality
  • Older smartphones have performance problems
Week 29 / 2013
  • Source of the performance problems is sought and found in various functions
  • Application starts a new instance when the screen is turned, which results in the application crashing after multiple turns
  • Layout for listing the stored devices resulted in speed losses when there is large content
  • After revising the layout and inserting a new function which is triggered when the screen is rotated, the application now runs smoothly on all devices available for testing
Week 32 - 2013
  • Expansion of the application to linking to Web-IO Analog devices
  • Devices are correctly stored and can also be correctly invoked
  • Setting of analog outputs is now possible
  • Incorporation of a password function
Week 33 / 2013
  • Connecting to password-protected devices is now possible
  • Application is again checked for functionality
  • After checking everything and verifying function, the first version was uploaded to the Google Play Store
Week 34 / 2013
  • Began to respond to customer reviews and change the application accordingly
  • Files with the device information can now be named by the use for better recognition
  • New function for saving contains errors, whereby difficulties in connecting to the devices occur
  • Device files can now also be edited and do not have to be completely recreated
Week 35 / 2013
  • Retrieving of input and output names from the Web-IO Digital Devices implemented
  • Names are not yet correctly associated
  • Layout for Web-IO Digital devices modified
  • The names are now correctly retrieved and entered
Week 36 / 2013

  • Retrieving of sensor names from Web-Thermo and Web-IO Analog devices
  • Errors in revising the layouts of Web-Thermo devices
Week 38 / 2013
  • Free naming of devices fully implemented
  • New version of the app almost ready for publication
Week 45 / 2013
  • Change in colour design
Week 48 / 2013
  • Internal saving of configuration changed
Week 49 / 2013
  • Screen organization optimised
Week 50 / 2013
  • Sensor names are copied over from the Web-IO
Week 02 / 2014
  • Problems in representing special characters in sensor names fixed
Week 03 / 2014
  • Problems in handling special characters in passwords eliminated
Week 05 / 2014
  • Long sensor names in small displays can be scrolled
Week 07 / 2014
  • Scaling for different display sizes revised
Week 11 / 2014
  • Release of new APP version

In planning is graphical representation of the curves for temperature, relative humidity, air pressure and other analog values

Hide details