Exceptions to Compatibility

$image\logo2_wmf.gif$

Product Catalog
SIXNET I/O Tool Kit

				q
$image\btn_Overview.gif$	$image\btn_New_Features32.gif$	$image\btn_Support.gif$	$image\btn_Upgrading.gif$	$image\btn_Compatibility.gif$	$image\btn_Requirements.gif$	$image\btn_Ordering.gif$	$image\btn_Options.gif$

SIXNET has taken great care to ensure that your upgrade path for your existing SIXNET projects will be trouble free. Compatibility is the prime directive at SIXNET. If you encounter any difficulty in upgrading existing projects, we always give priority attention to existing customers. We know that keeping your systems running is very important.

Here is a list of the planned exceptions in compatibility between the legacy software and the SIXNET I/O Tool Kit:

Plant Floor

All published features of all standard SixTRAK and VersaTRAK products are fully supported. The SCS feature set of the I/O Tool Kit is required for I/O Transfers (I/O moves between stations, formerly called "Action Tables").
Existing projects will be imported into the I/O Tool Kit, including their Bills of Materials.
Panel layouts are no longer required in the I/O Tool Kit (create panel views only if you wish to). Existing panel layouts will not be imported from Plant Floor into the I/O Tool Kit version 1.0 because of the conversion to true sizing of objects. Greater flexibility now exists in the way you create and organize panel layouts. Lists of products for each station will be imported and presented to you to enable you to quickly drag items into graphical panel views if you elect to do so.
Certain custom features, designed specifically for OEM customers, have been dropped with the agreement of the sponsoring OEM customer. Planned upgrade paths exist. Please contact your product manager for specific information.

Remote I/O Tool Kit

All published features of all standard RemoteTRAK and EtherTRAK I/O products are fully supported.
No known product exceptions exist.

Control Room

All existing IOmap databases and runtime tools will continue to run with the few exceptions noted below. Please note that the run-time elements of Control Room have been 32-bit compliant for many years. The run-time software has not been modified except to add upward compatible enhancements such as support for long file names and paths.
A license for the SCS feature set is required to run an IOmap shared resource database from the I/O Tool Kit.
IOmaps created with the I/O Tool Kit will not support 60-IBM/N network co-processors, nor any features specifically for the SIXNET two wire network. Upgrading to Ethernet networking is highly recommended.
The Tagview utility is no longer supported. However, the Test I/O windows in the I/O Tool Kit have all the functionality of IOview and Tagview combined, except for the saving of tag lists. Please use the new I/O test windows or HMI / third party tools to view I/O status.

Sixtags

All functionality of Sixtags has been integrated directly into the SIXNET I/O Tool Kit (except for configuration of Tagview lists, which are no longer supported). Extensive enhancements to the display of tags and the reporting of potential error conditions have been incorporated into all levels of the I/O Tool Kit.
All tag exporting to other applications (except for the Kepware OPC server) requires a SCS feature set license for the I/O Tool Kit.

Sixlog

All published features of Sixlog are fully supported with the minor exceptions noted below.
If you perform datalog transfers from other Windows applications, you will need to change the command you call from "Sixlog.exe" to "sxlogview.exe" to take advantage of the new enhancements New command line options for the communication device parameters have been added. Please note that if you leave the legacy version of Sixlog installed and continue to load Sixlog files into gateways and RTUs using the older software, than conversion to the new command line is not necessary.

Note: In response to numerous customer suggestions, the new Sixlog file format contains complete header information to eliminate the need to have the current project file on your run-time computer. Datalog files read from SIXNET stations will self-declare tag names and I/O scaling information to the Sixlog software.