Perfect Synergy Between Applications
Share data between applications with simple reads and writes to I/O registers in the IPm controller. (Yes, it is that easy!) Each application program runs independently in this multi-tasking / multi-user Linux environment. The 16 Megabytes (or more) of fast dynamic memory in the IPm easily accommodates multiple applications programs. (Programs in efficient embedded controllers tend to be quite small. For example, the entire ISaGRAF runtime executes in 150K of memory, complete with execution of all six supported languages.)

An Ideal Protocol Converter
An IPm controller makes the ideal protocol converter. Many I/O drivers can simultaneously run in this multitasking / multi-user environment. Each driver simply reads and writes I/O registers to the IPm I/O database. This shared database of discrete, integer (16 bit analog and counter values), long integer (32 bit), and floating point variables, may contain 50,000 (or more) I/O registers. SIXNET is helping system integrators and OEM customers develop I/O drivers to run on an IPm controller. Links to these partner's documentation are published to promote sharing of these solutions in the spirit of truly open systems. If you have developed an I/O driver that you would like to share, SIXNET will help you market your I/O driver product.

“Productizing” Your I/O Drivers and Applications Programs
SIXNET has developed a simple and flexible way to turn your application into a standard product that can be marketed as an IPm partnering product. Take a Quick Tour!

Develop and test your application in an IPm controller. There are no special rules or restrictions limiting how your program works or what it can accomplish. We suggest that you create a configuration file that your program reads at runtime to define the specific characteristics of the user’s application. In the case of an I/O driver, this might include the serial port to use, a list of I/O registers to exchange, and the desired update time. You may assign any unique name to this configuration file. In any event, let your program automatically read this pre-defined configuration when it initializes.

Create a simple Windows configuration utility to allow the user to define the parameters stored in the IPm runtime configuration file. By merely placing the configuration file’s name on the “Files to Load” list, it becomes part of the IPm controller’s project and will be automatically loaded by the SIXNET I/O Tool Kit software.

Your configuration utility can be added to the menus of the I/O Tool Kit and function as a integrated part of these comprehensive system tools. To the user, your tools and ours will appear as one synergistic product. All that is required is a simple “.ini” style text file to instruct the Tool Kit of the menu items that need to be displayed. View the IPm Technical Notes or contact SIXNET for more detailed information on this OEM partnering feature.

Referencing Registers by Address or Tag Name
Calls to I/O registers can be made by either their I/O address or their tag name. You will find function calls for both types of references in the ipm_io_call.pdf library documentation. In general, applications run faster if calls are made directly by I/O address. (All SIXNET applications reference I/O at runtime by I/O address. The tag names are displayed only in the Windows development tools for your convenience.) To reference I/O registers by tag name, a tag list files must be loaded into the IPm controller with your other project details. This is accomplished in the I/O Tool Kit configuration software by merely selecting the “Load Project Tag List” option in the “Files To Load” tab in the IPm configuration window.