OSx Migration Cookbook: A Practical Planning and Implementation Guide for Migrating Tistar, PCS, and OSx to PCS 7 By David J. Marks Consulting Software Engineer Siemens Energy and Automation Spring House, PA, USA Based on PCS 7/505 V6.1 and PCS 7 V6.
OSx Migration Cookbook August 30, 2006 Table of Contents 1 – Introduction................................................................................................................... 3 2 – Comparing OSx and PCS 7........................................................................................... 5 3 – The Migration Process .................................................................................................. 8 4 – Hardware...........................................................
OSx Migration Cookbook August 30, 2006 1 – Introduction Introduction This book covers the migration of Siemens’ OSx control system to Siemens’ PCS 7 control system. It provides a guide for determining what needs to be migrated, how that might be done, and what the scope of such a project might be. The majority of OSx customers use it to supervise Simatic TI505 PLCs. Thus, the main thrust of this document is how to convert OSx customers to PCS 7/505 OS, i.e., PCS 7 with the Simatic TI505 OS option.
OSx Migration Cookbook August 30, 2006 validated to run with any hotfix newer than Hotfix 7. Recipe support for OSx style recipes was dropped in version 6.1. Contact Siemens for further guidance if you are migrating an OSx system that uses recipes and you need to have OSx style recipes in PCS 7.
OSx Migration Cookbook August 30, 2006 2 – Comparing OSx and PCS 7 Before proceeding with a migration project, understanding the differences and similarities between OSx and PCS 7 is crucial. Client/Server vs. Peer-to-Peer Two architectures have been used for OSx and PCS 7: client/server and peer-to-peer.
OSx Migration Cookbook August 30, 2006 2 – Comparing OSx and PCS 7 OSx – PCS 7 Comparison (Architecture/Hardware) Tistar Client/Server Architecture 2 redundant DEUs plus 10 IGTs Maximum number of computers OSx Peer-toPeer 16 stations with a maximum of 4 Supervisors PCS 7 Client/Server 12 redundant server pairs, 32 clients, 1 engineering 1 Single Station that is client, server, and engineering Microsoft Windows Per station/per option/per number of tags 1 DEU plus 1 IGT 1 Supervisor Operating Syste
OSx Migration Cookbook August 30, 2006 2 – Comparing OSx and PCS 7 OSx – PCS 7 Comparison (Architecture/Hardware) Computer Specific hardware required? Tistar Motorola M68XXX Single Board Computer in a VME Chassis or Intel 80386 PC OSx Intel Pentium, Pentium II, Pentium III PC PCS 7 Intel Pentium 4 PC H1, S7 No (minimum memory and hard disk requirements) Siemens CP1613 (for TI505), any MS Windows supported network card (for S7 and station to station) H1, S7 TCP/IP TCP/IP Yes Yes PLC Communicat
OSx Migration Cookbook August 30, 2006 3 – The Migration Process No two migration projects are alike. However, all such projects follow the same basic steps. Understanding the OSx system The first step is to understand the OSx system to be migrated. That means doing an evaluation of the system to understand how OSx has been applied. What features of OSx are being used and how much configuration data there is must be determined.
OSx Migration Cookbook August 30, 2006 3 – The Migration Process either way. Configurations that are imported in bulk use files that contain the configuration data. How these files are created and who creates them must be decided. Some of these files can be created via an export from the OSx system. They can also be created using Microsoft Windows tools such as Excel, or Notepad.
OSx Migration Cookbook August 30, 2006 4 – Hardware Stations Both OSx and PCS 7 use a personal computer for each station. In most cases the PC used in OSx cannot be reused in PCS 7. Two tables below show the minimum and recommended requirements for PCS 7 PCs. Unlike OSx PCS 7 does not require specific brands or models as long as they meet the minimum requirements. The exception to this is the graphics adapters for multiple displays and the network card for communications to Simatic TI 505 PLCs.
OSx Migration Cookbook August 30, 2006 4 – Hardware Operator Keyboard OSx had available a special membrane keyboard that has special keys that at runtime provide operators one-key access to certain OSx functions. No such equivalent keyboard exists for PCS 7. Because PCS 7 uses standard PC keyboards, any standard membrane keyboard can be used with PCS 7. Customers in harsh environments have a solution and Siemens does sell its own membrane keyboard.
OSx Migration Cookbook August 30, 2006 4 – Hardware PCS 7 does not support thin clients. However, it does support multiple displays on a single client and Web clients. Web clients have not been validated with PCS 7/505 OS 6.1, so at this time they are not supported. Up to four displays can be used with PCS 7/505 OS. Because PCS 7 must interact with the graphics drivers, it only supports specific graphics cards for multiple displays.
OSx Migration Cookbook August 30, 2006 5 – Networking Network Types Tistar, PCS/OSx, and PCS 7 use three different network/protocols for communications. Tistar uses the proprietary network called Tiway to communicate with PLCs. PCS/OSx and PCS 7 use H1/Sinec TF and S7. Additionally, PCS/OSx and PCS 7 use Ethernet/TCP/IP to communicate among stations. Tiway Migrating a Tistar system involves converting the PLCs from Tiway to H1/Sinec TF. Simatic TI505 PLCs communicate over H1.
OSx Migration Cookbook August 30, 2006 5 – Networking AUI versus Twisted Pair OSx systems have primarily used AUI (“Fat” coaxial Ethernet) for their network cabling. This is an older technology. The newer technology is twisted pair (TP) cables. Most business networks have switched from AUI to TP. Sites where the network changed from AUI to TP have had to install converters that allow AUI PCs to connect to a TP network. It is possible to make OSx 4.1.1 and 4.1.2/4.1.2A connect directly to a TP network.
OSx Migration Cookbook August 30, 2006 6 – Naming Issues Name spaces A name space is a set of names that are managed together. Names within one name space must be unique. Names in separate name spaces can coincide. OSx treats the names of tags, and action requests as separate name spaces. Therefore, an action request can have the same name as a tag. PCS 7/505 OS manages all of these in a single name space. Thus, an action request cannot have the same name as a 505 tag.
OSx Migration Cookbook August 30, 2006 7 – Software and data configurations PCS 7/505 OS uses the PCS 7 paradigm where a runtime PCS 7 system is running a PCS 7 project. OSx cannot have more than one project loaded on the system at one time. There are no distinctions between a system and a project. PCS 7 has this project notion. It is a “project” that is executed at runtime. More than one project can be on a system at any given time.
OSx Migration Cookbook August 30, 2006 8 - PLCs Old TI PLCs Tistar can communicate with older TI PLCs such as the 520, 530, and 560 series, and the PM550. PCS 7 cannot communicate with these. To migrate a Tistar system with these PLCs, their logic would have to be recreated Simatic S7 series PLCs. The old TI PLCs would be discarded. SIMATIC S5 PLCs PCS 7 does not support SIMATIC S5 PLCs. Therefore, migrating an OSx system that uses S5 requires that you recreate their logic on SIMATIC S7 series PLCs.
OSx Migration Cookbook August 30, 2006 9 – Tags The main unit of data used throughout the OSx and PCS 7 systems is the tag. However, each applies the term ‘tag’ differently. What is a tag? In OSx, a tag is a logical object that groups a particular type of data with its range, alarm, limits, status, deadband, etc. Each of these items is called an attribute of the tag. Some attributes are the same for all tag types. Others differ based on the type.
OSx Migration Cookbook August 30, 2006 9 – Tags OSx to PCS 7 tag mapping When DBA maps an OSx tag to PCS 7 it creates a PCS 7 tag structure with some number of external and internal tags. This is because some OSx tag attributes are not networkable. Different OSx tag types produce different numbers of external and internal tags. PCS 7 tag licensing The table below shows how many external tags are created for tags of each OSx tag type.
OSx Migration Cookbook August 30, 2006 9 – Tags Install.tag files Migrating 505 tags from OSx to PCS 7 requires feeding DBA one or more install.tag files. An install.tag file is a file that contains a description of one or more OSx tags. Install.tag files have a specific format that is used by OSx and PCS 7 505/OS DBA to import tags. DBA does not have a way to manually create PCS 7 tag structures, nor to create its member tags.
OSx Migration Cookbook August 30, 2006 9 – Tags How to Create Install.tag Files OSX/PCS/Tistar Version 4.1.2A 4.1.1, 4.1.0A 4.0.0B, 3.1.2A 3.1.0B, 3.0.2E, 2.0.1, 2.0.0P1, 1.3.
OSx Migration Cookbook August 30, 2006 9 – Tags Invalid Tag Types When creating install.tag files from OSx or APT, you might inadvertently include tags of types that PCS 7/505 does not have such as BATCH tags or custom tag types. DBA will happily add these tags to its list. However, they will not be compiled to PCS7 and will produce warnings in the compile log file. Area and Unit Tags If there are AREA or UNIT tags in your install.
OSx Migration Cookbook August 30, 2006 internal. For example, if you need non-networked text tags, you can create a new tag structure TEXTN that is a duplicate of the 505_TEXT structure, except for the fact that all the tag elements are designated as internal. If you need faceplates and symbols, you will have to create these also. These can also be copied from those used for the 505 structures. Then, for each non-networked OSx tag you want in PCS 7, create an instance of that all-internal tag structure.
OSx Migration Cookbook August 30, 2006 9 – Tags Alarming DBA sets the alarmability of a tag based on the install.tag file used to import it into PCS 7. Tags that are configured for alarming in OSx (but NOT Tistar) have RBE ids assigned to them. In the install.tag format RBE ids are optional and DBA can accept install.tag files with and without RBE ids. Files originating from APT, Tistar, and the OSx 4.1.2, 4.1.1 or 4.1.0/4.1.0A HMI do not have RBE ids. Files that originate from the 4.1.
OSx Migration Cookbook August 30, 2006 10 – Hierarchy OSx Screen Hierarchy OSx has a concept of a Screen Hierarchy where at runtime, graphics can be configured so that you can navigate from one graphic to the next. The navigation topology is a flat graph with up, down, left, right and home directions. In OSx this hierarchy is optional. Many implementations navigate via buttons on graphics or via the graphics selection list.
OSx Migration Cookbook August 30, 2006 11 – Action Requests An action request is a function that asks an operator to do something. The request can be as simple as asking the operator to acknowledge that some event occurred in the system, or as complex as asking the operator to provide a value or make a choice. Action requests allow the process to make requests to operators. An explanation of how these work is in the OSx manual set.
OSx Migration Cookbook August 30, 2006 11 – Action Requests their names are unique. Fast action requests In OSx properly configured action requests are reported by the PLC because trigger tags are configured as RBE tags. This means that action requests can be triggered and reset faster than once per second. OSx will see these action requests and operators will still have to respond. In PCS 7 the server scans for action request trigger tags and the scan cycle is no faster than once per second.
OSx Migration Cookbook August 30, 2006 12 – Batch/BCL OSx supports a form of batch processing that is NOT compliant with any standard. This feature uses a combination of Batch and Unit tags, and BCL programs. No analogue of this feature exists in PCS 7. PCS 7 does have a batch option called Simatic Batch, but it is not integrated with PCS 7/505 OS and cannot be used with SIMATIC TI505 PLCs.
OSx Migration Cookbook August 30, 2006 13 – Reports OSx has two report editors: Xess and Classic. Both have similar functionality, except Xess can produce graphical output while Classic is text only. Both work from a spreadsheet paradigm. PCS 7 has one editor – the Report Designer. This editor’s paradigm is a drawing canvas to which you add objects and text, some of which can get their data and attributes from tag values.
OSx Migration Cookbook August 30, 2006 14 – Graphics There are two types of graphics that you may be migrating. Those that originate in Tistar and those that originate in PCS OSx. Tistar graphics are made from VGA line drawings. PCS OSx are based on Kinesix’s Sammi HMI. Both of these have distinctly different internal formats from PCS 7 graphics which are based on a format used by WinCC. Both OSx and WinCC graphics have similar functionality.
OSx Migration Cookbook August 30, 2006 15 – History Trend data Both OSx and PCS 7 can capture and store actual tag values for future reference. This is called trend data. In OSx trending is configured via the Historical Trend Configurator, while in PCS 7 it is configured via Tag Logging in WinCC Explorer. Both have similar functionality. Alarm and process messages OSx captures alarm and process messages in a single file called the Daily Log File. PCS 7 captures these in the Alarm Log.
OSx Migration Cookbook August 30, 2006 16 –@aGlance and RDT @aGlance PCS 7 has an @aGlance server option, called @PCS 7, that you can install. If you were using @aGlance with OSx, the PCS 7 @aGlance server may work with your client. However, you may have to reconfigure the client as the data you were reading from OSx may differ in PCS 7. RDT There is no feature in PCS 7 that is equivalent to OSx’s RDT.
OSx Migration Cookbook August 30, 2006 17 – Window Groups Window Groups Later versions of OSx have a feature where you can capture the arrangement of up to three graphics and tag details and save it by name. This allows operators to bring up their favorite grouping of graphics and tag details arranged the way they want. PCS 7 has two ways that the equivalent can be done: Picture Windows and Picture Groups.
OSx Migration Cookbook August 30, 2006 17 – Testing the Migration Running OSx and One of the ways to determine the success of a migration is to run an PCS 7 side by side original station and a newly migrated station side by side. Ideally alarms and action requests that are triggered on the original station will also trigger on the migrated station. How this is set up depends on what install.tag files were used to create the PCS 7 project. Install.
OSx Migration Cookbook August 30, 2006 17 – Testing the Migration PCS/OSx 3.1.2A through 4.1.2 have a patch available (patch 20270) that can add that capability. There is no patch for PCS prior to 3.1.2A. For Tistar, no patch is necessary since RBE is not implemented. In systems where RBE can be turned off, it is done by setting the RBE delivery time in Network Setup to 0. A system that does not have RBE, or has it turned off, scans the PLCs instead of waiting to be informed.
OSx Migration Cookbook August 30, 2006 Appendix A – Install.tag format An install.tag file is a csv type file that contains three types of records delimited by commas. Tag records introduce a tag. Following a tag record are one or more attribute records. There are as many attribute records as there are attributes for that tag. Following all tag and attributes there can optionally be process group records. Process group records are only available in files generated by APT.
OSx Migration Cookbook August 30, 2006 Appendix B – Action Request csv file format Action request csv files are used by DBA to import action request configurations from OSx. These files have two types of records: action request records and process group records. There are always 32 process group records. All records are delimited by semicolons.
OSx Migration Cookbook August 30, 2006 Appendix B – Action Request csv file format Action Request Records (Continued) Field Number Field Data Type 11 Trigger Tag Bit 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 Answer Tag Name Answer Tag Attribute Reset Tag Name Reset Tag Attribute Reset Tag Bit Name Reset Tag Bit Embedded Tag1 Name Embedded Tag1 Attribute Embedded Tag2 Name Embedded Tag2 Attribute Embedded Tag3 Name Embedded Tag3 Attribute Choice1 Choice2 Choice3 Choice4 Max length Notes Hex
OSx Migration Cookbook August 30, 2006 Appendix B – Action Request csv file format Process Group Records Field Number 1 2 3 Field Record Identifier Process Group Number Process Group Description Data Type Max length Notes Text 1 The string P Text 2 An integer from 1 to 32 Text 30 39
OSx Migration Cookbook August 30, 2006 Appendix C – Fast Action Requests Fast Action Request Configuration Procedure DBA configuration of an Action Request results in a message created in Alarm Logging. The Action Request TRIGGER variable is monitored by Alarm Logging for changes. If the variable’s value is not otherwise being read by thePCS7, Alarm Logging will default to scanning it at a one second rate. This is standard PCS7 behavior.
OSx Migration Cookbook August 30, 2006 The OS505_ORIGINAL project holds the configuration for a single Action Request that also has its TRIGGER variable defined as an alarm. The project illustrates how to assign the alarm to a PCS7 Area that is “ignored” and not made visible to any operator. This “hiding” procedure involves configuration steps in DBA, in PCS7 “User Administration” and also in PCS7 “OS Project Editor”. The project can be unzipped to view the configuration directly.
OSx Migration Cookbook August 30, 2006 The Action Request configuration: 42
OSx Migration Cookbook August 30, 2006 The DO_0 has been configured as an alarm in DBA.
OSx Migration Cookbook August 30, 2006 After a DBA compile, open the PCS7 “OS PROJECT EDITOR” utility and make the setting to have the Area named “IGNORE_ALARMS” to be ignored.
OSx Migration Cookbook August 30, 2006 Now all that remains is to use the PCS7 “User Administrator” utility to make the settings for each user to have no access to the Area named “IGNORE_ALARMS”. With this configuration, the alarm for DO_0 will still occur, but the alarm message will no appear for any user. This configuration gives the desired behavior for an Action Request requiring RBE (so that no TRIGGER changes are missed).
OSx Migration Cookbook August 30, 2006 Appendix D – System Evaluation Tool Survey Questionnaire Introduction This questionnaire is meant to help those who want to evaluate an OSx/PCS or Tistar system for migration to PCS 7/505 OS. Migration means that the customer replaces his OSx/PCS or Tistar system with a PCS 7/505 OS system communicating with the same PLCs. The supervisory logic and strategy used in the OSx/PCS or Tistar system is replicated (as much as possible) on the PCS 7/505 OS system.
OSx Migration Cookbook August 30, 2006 Appendix E – System Evaluation Tool Survey Questionnaire Section 1 – System Architecture 1. OSx/PCS/Tistar Version You can get this information by logging into Linux or Unix as user tistar and running the following command: cat /usr/tistar/bin/deu.ver PAS R&D should be contacted for further help if the system version is other than 4.1.2A, 4.1.1, 4.1.0A, 4.0.0B, 3.1.2A, 3.1.0B, 3.0.2E, 2.0.1, 2.0.0P1, 1.3.3. What version of OSx/PCS/Tistar is involved? Comments: 2.
OSx Migration Cookbook August 30, 2006 Appendix E – System Evaluation Tool Survey Questionnaire b) List the new PCs that the customer will need and who will supply them using the form below. Comments: 3. PC Operating System Software PCS 7 runs on MS Windows 2000. Who will be supplying the Operating System for the new PCs? Comments: 4. Network Hardware/Topology Tistar: Tistar systems use the proprietary Tiway network to communicate with PLCs.
OSx Migration Cookbook August 30, 2006 Appendix E – System Evaluation Tool Survey Questionnaire Do TP-to-AUI converters need to be purchased? Comments: 5. Printers Older OSx/PCS/Tistar systems may be using printers that are no longer directly supported in MS Windows and would need additional drivers installed. These are being used because those versions of OSx/PCS/Tistar may not support newer printers. This may be a good time to replace these older printers with newer ones.
OSx Migration Cookbook August 30, 2006 Comments: 50
OSx Migration Cookbook August 30, 2006 Appendix E – System Evaluation Tool Survey Questionnaire Section 2 – Data, Functionality & Graphics Conversion Information To be able to gauge the level of effort required, fill in the forms below. Some data may not be directly transferable and may require custom programming such as using Global Scripting and the User Archive. 1. Tags OSx/PCS/Tistar type Tags must be imported into WinCC using OSx format install.tag files. There should be one install.
OSx Migration Cookbook August 30, 2006 Appendix E – System Evaluation Tool Survey Questionnaire 2. HMI Graphics Conversion a) Tistar Customers: Tistar uses VGA line graphics that cannot be converted to WinCC. These must be recreated by hand. Who will recreate the graphics? b) OSx/PCS Customers: OSx/PCS systems use SAMMI graphics. A service provided by PAS R&D can convert the static and dynamic objects in customer graphics to static objects in WinCC graphics.
OSx Migration Cookbook August 30, 2006 Appendix E – System Evaluation Tool Survey Questionnaire 4. Batch There is no PCS 7/505 feature exactly equivalent to OSx/PCS/Tistar Batch. See Section 12 above for a way to recreate OSx/PCS/Tistar Batch on PCS 7. Does the system use the OSx/PCS/Tistar Batch Feature? Comments: 5. Reports and BCL Programs OSx/PCS/Tistar reports and non-Batch OSx/PCS BCL programs can write to process data as a result process events.
OSx Migration Cookbook August 30, 2006 Appendix E – System Evaluation Tool Survey Questionnaire 8. Trend data Direct access to OSx/PCS/Tistar trend data from PCS 7/505 does not exist. Converting OSx/PCS/Tistar trend data for access from within PCS 7/505 is a special project. Using the htp (historical trend print) utility to dump OSx/PCS/Tistar trend data to text files is an option or keeping the old system for access to old trend data is another option.
OSx Migration Cookbook August 30, 2006 Appendix E – System Evaluation Tool Survey Questionnaire Section 3 – Customizations Use this section to describe any customizations that the OSx/PCS/Tistar system being converted has that will affect the conversion. These could include custom software, custom menus, etc. Be specific and indicate who did the customization. If there is any question, PAS R&D can evaluate the system.
Appendix E – System Evaluation Tool Survey Questionnaire OSx/PCS Station Table Name Type (Intel PC, HP Workstation) Function (Supervisor, Operator) # Xterminals licensed RDT (Y/N) @aGlance (None, 1 user, 10 user) Special Hardware (trackball, operator keyboard, touch screen, etc.
OSx Migration Cookbook August 30, 2006 Appendix E – System Evaluation Tool Survey Questionnaire OSx/PCS Station Table (continued) Name Type (Intel PC, HP Workstation) Function (Supervisor, Operator) # Xterminals licensed RDT (Y/N) 57 @aGlance (None, 1 user, 10 user) Special Hardware (trackball, operator keyboard, touch screen, etc.
Appendix E – System Evaluation Tool Survey Questionnaire Appendix 2 – Tistar System Description Form DEU (Main Data Computer) IGTs (HMI terminals) Tiway Network Redundant? Y N (Model 70 only) Number:___________ (Do not include onboard Model 20 IGT) Redundant? Y N
Appendix E – System Evaluation Tool Survey Questionnaire PCS 7/505 OS Station Table Name Function (OS Single, OS Client, OS Server, etc.
OSx Migration Cookbook August 30, 2006 Appendix E – System Evaluation Tool Survey Questionnaire PLC Table PLC Name PLC Model (TI545, TI555, TI575, S5, S7, etc.) PLC Version (1102, 416, etc.
Appendix E – System Evaluation Tool Survey Questionnaire Tag Type AI AO AREA CALC CTR DI DI10 DO DO10 IVAR LOOP MTR1 MTR2 RMTR TEXT TMR VLV1 VLV2 Number of Tags Number Networked Non-Networked
OSx Migration Cookbook August 30, 2006 Appendix E – System Evaluation Tool Survey Questionnaire OSx/PCS/Tistar Data Count Data Number Graphics Action Requests Areas Recipes Components Recipes Reports Write to process data Total Trend Points RDT Programs (OSx/PCS only) BCL Programs (OSx/PCS only) 62
OSx Migration Cookbook August 30, 2006 Appendix E – System Evaluation Tool Survey Questionnaire Off board IGT DEU Serial Tiway TI545 TI545 Tistar Model 20 Configuration 1 63 TI545
OSx Migration Cookbook August 30, 2006 Appendix E – System Evaluation Tool Survey Questionnaire DEU IGT Serial IGT Serial Tiway Tiway TI545 TI545 Tistar Model 70 Configuration 2 64 TI545
OSx Migration Cookbook August 30, 2006 Appendix E – System Evaluation Tool Survey Questionnaire Primary DEU Backup DEU IGT Serial Serial Ethernet IGT Serial Tiway Tiway TI545 TI545 TI545 Tistar Model 70 Configuration 3 65 IGT
OSx Migration Cookbook August 30, 2006 Appendix E – System Evaluation Tool Survey Questionnaire Failover circuit Primary Backup Supervisor Supervisor Operator Ethernet Ethernet S5-155U TI575 TI545 TI555 OSx/PCS Configuration 4 66 S7-416 Operator
OSx Migration Cookbook August 30, 2006 Appendix E – System Evaluation Tool Survey Questionnaire Primary Ethernet Ethernet S5-155U TI575 TI545 TI555 OSx/PCS Configuration 5 67 S7-416
OSx Migration Cookbook August 30, 2006 Appendix E – System Evaluation Tool Instructions Introduction These instructions explain how to use the System Evaluation Tool to gather data so that Tistar/PCS/OSx systems can be evaluated for candidacy for migration to PCS 7/505 OS and to help determine the scope of the project. Components • Questionnaire: This questionnaire (in Appendix D above) is the primary component of the tool.
OSx Migration Cookbook August 30, 2006 Appendix E – System Evaluation Tool Instructions General Procedure The steps below explain how to use this tool when no modifications are needed. 1. Obtain the questionnaire and the software tool. 2. Read the questionnaire to become familiar with the data needed to do an evaluation 3. Transfer the software tool floppy disk image to a Linux/Unix floppy disk. 4. Install the software tool onto the system to be evaluated using the Linux/Unix floppy disk. 5.
OSx Migration Cookbook August 30, 2006 Appendix E – System Evaluation Tool Instructions Transferring the Software Tool to a Linux/Unix Floppy This procedure should be done on any station of a PCS/OSx system or on the onboard IGT of a Tistar Model 20. Perform the following steps on 1.3.3, 3.0.2E, 3.1.0B, 4.0.0B, and 4.1.0A systems. 1. Save the compressed floppy disk image to an MS Windows floppy. 2. Log into Unix as user ‘root’ 3. Set the current directory to /tmp by typing: cd /tmp 4.
OSx Migration Cookbook August 30, 2006 Appendix E – System Evaluation Tool Instructions Perform the following steps on 4.1.1 and 4.1.2A systems. 1. Save the compressed tool floppy disk image to an MS Windows floppy. 2. Log into Linux as user ‘root’ 3. Set the current directory to /tmp by typing: cd /tmp 4. Insert the floppy disk into the floppy drive 5. Copy the compressed floppy disk image into the /tmp directory by typing: mcopy a:tool.Z tool.Z 6. Uncompress the image by typing: uncompress tool.Z 7.
OSx Migration Cookbook August 30, 2006 Appendix E – System Evaluation Tool Instructions Installing, Compiling and Running the Software Tool The following steps should be done on the Primary station of the PCS/OSx system being evaluated or on the onboard IGT of the Tistar Model 20 being evaluated. 1. Log into Linux or Unix as user ‘tistar’. 2. Set the current directory to be /tmp by typing: cd /tmp 3. Insert the Linux/Unix software tool floppy into the floppy drive. 4.
OSx Migration Cookbook August 30, 2006 Appendix E – System Evaluation Tool Instructions On 4.1.1 or 4.1.2A systems type: more data.txt 9. The data file, data.txt, can also be transferred to an MS Windows floppy for viewing and printing using MS Windows tools. Insert a DOS formatted floppy into the floppy Drive. On 1.3.3, 3.0.2E, 3.1.0B, 3.1.2A, 4.0.0B, or 4.1.0A systems type: doscp data.txt a: On 4.1.1 or 4.1.2A systems type: mcopy –a data.
OSx Migration Cookbook August 30, 2006 Appendix F – References The following references have been published for various versions of various software in differing years and under differing part numbers. Pick the version appropriate for your project. In most cases these references came or come with your software and systems.
