9100 Options 2 (V6 Software Release)
Contents
1. 9100A 279 9100A 283 9100A 284 DESCRIPTION When doing a TEST BUS with the 9 132A POD and a fault message causes the MORE INFORMATION LED to come on the LED does NOT go off when the CONT key is pressed even though the new message fits in the window The actual fault was BAD CHIP SELECT on the ROM MODULE caused by tied high W R line PASSED message is not erased correctly DESCRIPTION After doing a bus test on a 9132A POD you have to press the BUS TEST key twice to erase the PASSED message A single press of another key such as the down arrow will erase the message I believe a single press of BUS TEST used to erase the PASSED Repeat never did Stack overflow error in UUT compiler DESCRIPTION When compiling a UUT an Infinite Recursion or Stack Overflow error occurred WORK AROUND This can occur if the reflist contains several hundred entries and they are in alphabetical order To workaround this move the middle entry to the beginning of the reflist and recompile For example if the reflist is 600 lines long move the entry at line 300 to line 5 lines 14 of the reflist are title lines Cannot RESTORE Pod Name between different packag estyles of the same POD DESCRIPTION Using a 68000 Pod with 3 different Packages covered by three different POD NAMES I did a SETUP POD NAME to the desired POD I then saved system settings in a UUT When restarting a cold system RESTORE SYSTEM SET TINGS lea2. and enter a POD NAME of 6802 The 9100 will load the pod database and return the error message enabled line causes timeout which is normal when the pod is in selftest The pod database loaded now is for the 6802 pod as evidenced by the ADDR OPTION ENABLE line names and POD NAME however the pod will pass selftest and seems to work normally for other functions as well Selftest at least should be able to tell that the pod type does not match the database that is loaded since the pod reset string includes its name The POD NAME entered should also be checked against the actual pod installed This seems to happen specifically with the Z80 pod and the 6802 database Other combinations of pod and database mis matches do give an error message if the wrong name is en tered but the mis matched database is still loaded Debugger SHOW and SET do not work for array refer ences DESCRIPTION SHOW and SET in the debugger do not work for army refer ences 1 Array indices cannot be specified in SHOW or SET Page 20 6 0 Release Notes Bugs Fixed in Version 6 0 9100A 268 9100A 269 9100A 271 2 SHOW and SET can be used with just the army name and this appears to show the lowest subscripted clement HELP in the E DISK LOAD command can be confusing DESCRIPTION When choosing a UUT to load into the E DISK the user as per normal can push the HELP button when in the UUT NAME field of the E DISK load command on t
3. off This really represents a shortcoming of the implcmcntation because it currently does not allow any spaces in identifier names separated by single quotes whereas TL 1 docs allow them This problem also shows up where we have a TL 1 program with a space in the name such as test program This relat ed problem should also be fixed This fix will allow the fol lowing test program slotname value TL 1 hangs up when you use remove menu command DESCRIPTION If the following TL 1 program lines are executed it will lock up the system define menu mx I label First Entry define menu mx 2 label Second Entry define menu mx 3 label Third Entry remove menu mx or remove menu mx 2 or remove menu mx 3 Removing whole menus does work however For example remove menu mx will work Shift Field Select does not work in PROGRAM info win dow DESCRIPTION The Shift Field Select key does not change the field value for the WRITE PROTEC T field in PROGRAM info windows Learn key won t clear error Page 26 6 0 Release Notes Bugs Fixed in Version 6 0 9100A 399 9100A 415 9100A 427 DESCRIPTION When editing a response file if the cursor is moved beyond the last node entry and the learn key is pressed an error mes sage appears is not a valid ref pin name which is correct If you then move the cursor back up to a valid n
4. 9100 9105 Version 6 0 Software Release Customer Information Version 6 0 of the 9100A system software is a ma jor software release The TL 1 program interpret er has been replaced with a faster memory effi cient compiled TL 1 runtime system The 6 0 re lease also contains new features performance enhancements and fixes for reported bugs These notes provide a brief description of new features in 6 0 instructions for installing version 6 0 soft ware a list of bugs fixed since the 5 0 software re lease and a list of bugs known to exist in version 6 0 IMPORTANT NOTE Version 6 0 is not fully compatible with prior software releases Please read section 2 Incompatibilities Between Version 6 0 and 5 0 before upgrading to Version 6 0 P N 899658 May 1991 Rev 1 6 91 c 1991 John Fluke Mfg Co Inc All Rights Reserved Litho in U S A Contents This document accompanies version 6 0 of the 9100 9 105 operating software The document is divided into sections SECTION 1 New Features of Version 6 0 0 This section gives a brief description of the new features in the 6 0 software release Incompatibilities Between Version 6 0 and 5 0 This section describes the incompatibilities between this software release and the previous release IMPORTANT NOTE Version 6 0 is not fully compati ble with prior software releases Please read section 2 before up grading to Version 6 0
5. F1 the debugger won t necessarily single step It may con tinue Also if you are at the line before a function that will raise a fault you might think STEP F1 would stop you on the first line of the fault handler It doesn t gfi status returns untested when it shouldn t DESCRIPTION If you perform GFI from the front panel and then execute a TL program that calls gfi status then gfi status always returns a status of untested It doesn t seem to know about the pins which were tested from the front panel Displayed data truncated in READ VIRTUAL DESCRIPTION The displayed data is truncated when READ VIRTUAL is performed from the operator s interface if the EXTADDR and ADDR values have more than 8 digits total For example if the data value read is FFFF READ VIRTUAL EXTADDR 2000000 ADDR 0 FFFF will be displayed correctly but READ VIRTUAL EXTADDR 200000 ADDR 64 FFF A is truncated at the right hand edge of the display This means that the whole data value of 16 bits cannot be read by the op erator Confusing error message when illegal UUT name entered DESCRIPTION If the UUT is inadvertently changed to something illegal then trying to execute TEST BUS with a9 132 pod gives the error message Bad Object Name Ist char not alphanumeric Page 22 6 0 Release Notes Bugs Fixed in Version 6 0 9100A 282 9100A 287 9100A 289 9100A 293 To repeat 1 P
6. Version 6 0 Upgrade Kit Contents This section describes the items you should have received with your software upgrade kit installing New System Software This section descsribes how to update your unit from ver sion 3 0 or later software to version 6 0 Bugs Fixed in Version 6 0 e seenees T his section describes the bugs fixed between version 5 0 and 6 0 Known Bugs in Version 6 0 ecsseeeees This section describes the bugs that are known to exist in version 6 0 Page 3 11 14 16 19 30 6 0 Release Notes New Features of Version 6 0 1 New Features of Version 6 0 1 1 Compiled TL 1 Runtime System The TL 1 interpreter has been replaced with a compiled TL 1 runtime system Larger programs can now be executed because the compiler based runtime system is more memory efficient than the interpreter was In general it is also faster than the interpreter resulting in decreased board test times The compiled nmtime system also allows you to distribute compiled object pro grams which can be executed but cannot be modified When you execute a TL 1 program with the 6 0 release the new TL 1 runtime system will automatically compile the program as it is read off the disk The program is compiled directly into memory and the resulting object program is executed This process is very fast and programs actually begin execution faster than they did under the TL 1 interpreter
7. Known Bugs in Version 6 0 6 0 Release Notes 6 Known Bugs in Version 6 0 The following bugs are known to exist in version 6 0 software A description of each bug is provided A workaround is described if one is known 9100A 249 9100A 250 Marking characters on a long line can mess up attributes DESCRIPTION This bug involves MARKing characters on the bottom line of the screen so that the screen has to scroll The line attributes holding are wrong To reproduce 1 Edit a text file Put a long line in it that takes up several rows on the CRT Position it on the CRT so that the first row of the long line is on the bottom of the CRT The second row of the long line is off the screen Put the cursor on the first row of the long line 2 Press MARK and right arrow until the screen scrolls and you ve marked a few characters on the second row of the long line 3 Press left arrow a few times The bolding is not removed as the cursor backs up NOTE The editor does YANK CUT the correct of charac ters it s only the bolding that is messed up Editor positions cursor improperly on long lines DESCRIPTION In the example below position the cursor on the line marked with Then press the lt End Line gt key or the lt Begin Lino key followed by the lt Retun gt key Example below declare global string dvm 02 8840 on IEEE address 2 global numeric ieee_out global numeric ieee_in global numeric disp end decla
8. a ready message appears on the operator s display If the ready message does not appear see the Power up of a 9100A section in the Technical User s Manual The original system disks should be stored in a safe place as back ups 9105 Software Installation Procedure The following procedure should be followed to install a new version of the operating software on the 9105 Page 17 Installing New System Software 6 0 Release Notes 1 2 3 4 5 Restart your 9105 by depressing the recessed RESTART button on the mainframe right side panel at the front or by turning the power switch on the back of the mainframe near the power cord off then on After the system performs its self test you are prompted to insert the disk labelled System Disk 1 into Drive 1 the upper micro floppy disk drive When the disk is read you are prompted to insert the next system disk into Drive 1 This step is repeated for each system disk After the System Disks are read you are asked whether there are any Optional feature disks to be loaded The IEEE 488 disk is an Op tional Feature disk You do not have to load this disk if your 9105 does not have IEEE 488 or if your 9105 has IEEE 488 but you do not want to use this capability If there are no feature disks to be loaded press CLEAR NO To load a feature disk press ENTER YES Insert the disk into Drive 1 when prompted When the disk has been read the main
9. etc IMPORTANT NOTE It is strongly recommended that you pre com pile all your TL 1 programs from the editor before executing them with version 6 0 Pre compiling your programs will allow you to find all the compilation errors at one time in the editor environment where it is convenient to fix the programs Programs that contain compilation errors cannot be executed until the errors are fixed 2 4 TLA Variable Initialization mm Global string variables are now initialized to the empty string not initialized before They were The default value for floating variables has been changed to 0 0 The default value used to be 1 234568E 123 2 5 TLA Arithmetic Overflow TL 1 now wraps through zero on arithmetic overflow and underflow For ex ample the expression FFFFFFFF 1 will result in a value of zero The ex pression 0 1 will result in a value of SFFFFFFFF Arithmetic overflow and underflow used to be detected in some cases and would result in a program error 2 6 Response Files Response files that use the new don f care feature to describe asynchronous or clocked level histories cannot be used with version 5 0 or earlier Page 12 6 0 Release Notes Incompatibilities Between Version 6 0 and 5 0 2 7 GFI UFI Databases GFI and UFI databases that include don t cure levels for the asynchronous or clocked level history cannot be used with 5 0 or earlier software Page 13 Version 6 0 Upgrade
10. 0 Release Notes Known Bugs in Version 6 0 9100A 298 9100A 323 left or right does not silence the bell However pressing Con trol C will silence the bell This is intermittent and difticult to reproduce WORK AROUND Press Control C Editor Debugger Wrap Around Error DESCRIPTION I was using the debugger on a program I pressed QUIT to exit the debugger When in the debugger the top line was a wrap around with one character extended to the next line The debugger was exited but upon an attempt to shift the screen back over the screen was frozen with the wrap around still in place Using the up arrow and down arrow keys caused the current line number to update even though the screen was fro zen 1 pressed SCROLL FORWARD and the screen updated An attempt to duplicate the error was unsuccessful WORKAROUND Press the lt Scroll Forward gt key pred O UUT compiler crashes on 6 0 response files DESCRIPTION At release 6 0 the file format for response files changed to support don t care logic levels for GFI The response files are not backward compatible If you save a response file in the new format and try to compile it with a 5 0 or earlier UUT compiler the system will crash and needs to be rebooted WORK AROUND To determine if an incompatible file format caused the system crash reboot the system and edit the response file that was be ing compiled If the file is incompatible the editor will dis play the err
11. 22A and the operator aborts the transfer by pressing a control C on the 1722A keyboard WORK AROUND If this problem occurs it usually can be corrected by resetting the ADDRESS FUNCTION or TLK TERM from the front panel of the 9 100 Page 36 6 0 Release Notes Known Bugs in Version 6 0 9100A 489 Bus Error when copying userdisks onto MDR DESCRPTION On some 9100s you cannot copy userdisks onto the hard disk If you try to copy DRI to HDR from the front panel the copy doesn t work The following error message is dis played and the 9 100 has to be rebooted Root application exited abnormally Internal Error 102 Bus Error Press any key to continue If you encounter this bug please call the Fluke Field Sup port Group at 206 3564786 Page 37
12. Agreement Documents Page 14 6 0 Release Notes Version 6 0 Upgrade Kit Contents 34 91WA 904 This kit upgrades version 3 0 or later 9100 systems with programming to ver sion 6 0 System Disk 1 Ver 6 0 Technical User s Manual text System Disk 2 Ver 6 0 Automated Qpns Manual text System Disk 3 Ver 6 0 TL Reference Manual text TEEE 488 Disk Ver 6 0 Programmer s Manual text Programmer s Disk Ver 6 0 TL 1 Quick Reference Card Master Userdisk 1 Ver 6 0 IEEE Quick Reference Card Master Userdisk 2 Ver 6 0 Release Notes Software Support Agreement Documents Page 15 Installing New System Software 4 The procedure for installing new system software depends on whether the Installing New System Software mainframe is a 9100 or 9105 4 1 The following procedure should be followed to install a new version of the system software on a 9100 which is running version 3 0 or later software IMPORTANT NOTE If you are upgrading to Version 6 0 please read sections 1 and 2 of this document before installing the system software Version 6 0 is not fully compatible with prior software ver sions 9100 Software Installation Procedure IMPORTANT NOTE If your 9100 is running Version 2 2 or earlier software it must be upgraded to Version 3 0 before Version 6 0 can be installed Failure to update from 2 2 to 3 0 before installing Ver sion 6 0 will leave your 9100A in an unusable State IMPORTAN
13. Because the compilation hap pens automatically your procedures for executing programs do not have to change However using this method the programs are compiled each time they are executed For the best speed performance programs can be pm compiled from the editor see section 1 2 IL 1 Program Compiler Using this method programs are compiled only once and the executable object program is saved on disk When you execute a pre compiled program the TL 1 run time system simply loads the executable object program This is the fastest method of executing programs Once a program has been pre compiled the TL I runtime stystem automati cally maintains the compiled object file If both the TL 1 source program and compiled object file are present when a program is executed TL 1 compares the two files to make sure that the object file was generated from the source program If they do not match e g because the source program has been modified the TL 1 runtime system will automatically recompile the program before executing it The new object program will be saved on disk Page 5 New Features of Version 6 0 6 0 Release Notes IMPORTANT NOTE Every effort has been made to insure identical behavior between TL programs executed under the interpreter and the compiled run time system However a few differences were unavoidable For example because programs execute faster software loops that were being used to detect time out e
14. Kit Contents 6 0 Release Notes 3 Version 6 0 Upgrade Kit Contents 3 1 9100A 7200 903 Software Support Upgrade This kit upgrades version 5 0 9100 or 9105 systems to version 6 0 System Disk 1 Ver 6 0 System Disk 2 Ver 6 0 System Disk 3 Ver 6 0 TEEE 488 Disk Ver 6 0 Master Userdisk Ver 6 0 Master Userdisk 2 Ver 6 0 Technical User s Manual text TL 1 Quick Reference Card IEEE Quick Reference Card Manual Update Package Release Notes Software Support Agreement Documents 3 2 91 OOA 7200 904 Software Support Upgrade This kit upgrades version 5 0 9100 systems with programming to version 6 0 System Disk 1 Ver 6 0 System Disk 2 Ver 6 0 System Disk 3 Ver 6 0 TEEE488 Disk _ Ver 6 0 Programmer s Disk Ver 6 0 Master Userdisk 1 Ver 6 0 Master Userdisk 2 Ver 6 0 Technical User s Manual text Programmer s Manual text TL 1 Quick Reference Card TIEFE Quick Reference Card Manual Update Package Release Notes Software Support Agreement Documents 3 3 91 OOA 903 This kit upgrades version 3 0 or later9100 or 9105 systems to version 6 0 System Disk 1 Ver 6 0 System Disk 2 Ver 6 0 System Disk 3 Ver 6 0 TEEE 488 Disk Ver 6 0 Master Userdisk 1 Ver 6 0 Master Userdisk 2 Ver 6 0 Technical User s Manual text Automated Opns Manual text TL 1 Reference Manual text TL 1 Quick Reference Card IEEE Quick Reference Card Release Notes Software Support
15. T NOTE Once you have begun the installation proce dure do not restart or power down your 9100 until all disks are copied If you do you run the risk of leaving your 9100 in an unusable state Page 16 6 0 Release Notes 6 0 Release Notes Installing New System Software 2 3 4 5 4 2 Copy each of the new System Disks and Optional Features Disks to the hard disk by selecting the command MAIN COPY DISK FROM DRI TO HDR under the MAIN MENU key on the operator s interface If your 9100 does not have IEEE 488 you do not have to copy the IEEE Optional Feature Disk If your 9100 does not have a program mer s station you do not have to copy the Prograrnmcr s Optional Feature Disk If your upgrade includes new Master User Disks you may copy them to the 9100A hard disk by selecting the command MAIN COPY DISK FROM DRI TO HDR under the MAIN MENU key on the operator s interface IMPORTANT NOTE If you saved modified copies of any programs from the Master User Disks onto your 9100 hard disk and you did not change their names the modified programs will be over written when you load new Master User Disks Restart your 9100 by depressing the recessed RESTART button on the mainframe right side panel at the front or by turning the power switch on the back of the mainframe near the power cord off then on After the system completes its self test and loads the system soft ware from the hard disk
16. e expected response defined in a response file Prior to 6 0 if an asyn chronous level history or clocked level history was used as part of a node s expected response an exact match on all three states high low invalid was required in order for the node to be good It is now possible to specify one or more don t cure states in an expected level history A don t cure state is ig nored during the comparison of the expected and measured level histories To specify a don r care level edit a response file and enter a character in the asynchronous or clocked level fields The is interpreted based on its position in the field Each field is three columns wide The columns represent from left to right high tristate and low Insert the in the leftmost column to mean don t cure on high in the middle column to mean don f cure on tristate and in the rightmost column to mean don t cure on low For example 120 means don t care on tristate 0 means don t cure on high and tristate Compatibility response files and databases that contain don t cure levels cannot be used with 5 0 or earlier software 1 a UUT Directories Can Contain Parts A UUT directory can now contain part descriptions Prior to 6 0 part descrip tions could only be stored in the Part Library PARTLIB This feature allows you to locally redefine parts as required by a specific UUT The GFI and UFI compiler will use the following search pa
17. etcleared off To see this have a pod that has the QUICK tests eg 68000 and press IROMI TEST ROM QUICK ENTER IRAM TEST RAM QUICK ENTER ROM and notice that the parameters still exist and the parameters that show up are the parameters for the TEST RAM QUICK test Also notice that pressing ENTER again brings up the correct parameters for TEST ROM QUICK and pressing ENTER yet another time finally executes the test Editor SEARCH inactive if cursor in leftmost column DESCRIPTION In the editor when you press the SEARCH softkey you are prompted to enter the search string If you use the Shifted cursor keys to edit the default search pattern and then leave the cursor at the leftmost column of the prompt when you press RETURN nothing happens Improper front panel arguments displayed for TEST BUS DESCRIPTION I first did an EXEC UUT TD93991 PROGRAM TRANS LATE When this program executes it prompts for argu ments I did not execute the program after the prompts were displayed but instead tried to run BUS TEST which dis played the program TRANSLATE arguments This is similiar to 9100A 427 Some Master Userdisk Part Descriptions are Incorrect DESCRIPTION The following parts which are contained on Master Userdisk 2 in the parthb directory have been corrected Page 28 6 0 Release Notes Bugs Fixed in Version 6 0 2675 74151 28842 2016 41128 74657A 7472 SLIDESW 74373 7413 74122 and 74123 Page 29
18. frame asks for any more feature disks If there are additional feature disks to be loaded press ENTER YES If there are no more feature disks press CLEAR NO It is a good idea to load all the feature disks at least once to verify they are readable on your machine When the power up procedure is completed a ready message ap pears on the operator s display If the ready message does not appear see the Power up of a 9105A section in the Technical User s Manual Make a working copy of each disk The originals should be stored in a safe place as backups To copy the disks follow the procedure in Duplicating a Disk Using a9100A 9105A in the Technical U ser s Manual Page 18 6 0 Release Notes Bugs Fixed in Version 6 0 Se Bugs Fixed in Version 6 0 The following bugs reported in previous versions of the system software have been corrected in version 6 0 The bug descriptions are furnished for refer ence only they are not needed for programs running under version 6 0 or lat er 9100A 247 9100A 248 9100A 265 TL 1 sometimes loads programs more than once DESCRIPTION Occasionally unusual disk activity was observed when a TL 1 program was executed in a loop These programs were usu ally pod special programs The problem was that the program was named FOO but was invoked as foo The operating system looks for the program on disk case insensitively and when it finds the program it executes it Howeve
19. g loop for i 1 to 1000 may need to be changed Please read section 2 Incompatibilities Between Version 6 0 and 5 0 for a list of the known differences between the interpreter and the compiled run time system That section also includes a rec ommendation that you pre compile all pro grams when you install version 6 0 1 2 TL Program Compiler TL 1 programs can be compiled from the editor before they are executed This pre compilation will result in faster startup when a program is executed and lets you find compilation errors in the editor rather then when the program is executed Each of the directories that contains TL programs now contains a COM PILE softkey To compile a program edit a UUT PROGLIB or POD Press the COMPILE softkey select the TL 1 compiler using the field select key and then enter the name of the program to be compiled The wildcar dchar acter can be used to compile multiple programs Next use the licld select key to select YES in response to the prompt USE CURRENT TL COM PILER OPTIONS and then press the Return key to start the compile If the program is successfully compiled an executable object program OBJPROG will be saved on disk The compilation can be aborted at any time by pressing the Quit key During compilation error messages are displayed on the monitor screen The TL compiler has an option that allows you to save these messages in a text file It also has options that con
20. he application interface and get a list of the UUTs on the current disk However if the user sets the DRIVE field in the E DISK LOAD command to a disk different than the current disk as set in the SETUP command the command still lists out the contents of the current disk It would be intuitive that it should list out the contents of the disk that the user chose in the E DISK LOAD command This can be confusing Debugger exits when the QUIT key is pressed DESCRIPTION Consider the program fragmenr program a execute large_program0 enda In the debugger if you execute program a then press the QUIT key during the time large_program is being loaded from the disk then ask to SHOW an undeclared name there is a brief flurry of disk activity then the debugger exits sud denly and the application display shows the message OB JECT DOES NOT EXIST Hyper Help bug with greater than 105 files DESCRIPTION If there are more than 105 of a given object when hyper help is invoked to select a file from that object type Hyper Help beeps and displays only 105 of the files You may then scroll past the end of the files lose the cursor and never get it back The No Clear button exits Hyper Help correctly Page 21 Bugs Fixed in Version 6 0 6 0 Release Notes 9100A 274 9100A 276 9100A 280 9100A 281 Problems with debugger STEP DESCRIPTION If you are at the last statement of a function and press STEP
21. ode and press the learn softkey it again displays the same error message and will not allow you to learn any nodes Note that it seems to have modified the response file by the cursor movement even though the modified flag is not displayed You can press the end file key and the cursor will move to that last line you moved the cursor to even though they are all blank softkey labels disappear after Offset Window HELP DESCRIPTION If you are in the response OFFSET window and press HELP while you are being prompted and then press QUIT to abort from the prompts the softkey labels disappear To reproduce press this sequence of keys OFFSET to enter offset window EXEC to execute a program HELP when you are being prompted for program name the help window appears HELP to remove the help window the prompt reappears QUIT to abort the execute prompts The softkey labels are missing Stale Parameters on TEST ROM HYPER DESCRIPTION If you execute a TEST ROM HYPER after a TEST RAM HYPER the RAM TEST parameters appear on the 3 line dis play BEFORE pressing the enter key and calling the program The correct default parameters appear AFTER pressing the ENTER key Parameters for TEST ROM RAM QUICK don t go away Page 27 Bugs Fixed in Version 6 0 6 0 Release Notes 9100A 438 9100A 449 9100A 481 DESCRIPTION This is the same as 9100A 415 except for the QUICK option The pod dependent test parameters don t g
22. or Long Directory Style The STYLE softkey controls the way that directories are displayed when a USERDISK UUT LIBRARY or POD is edited The LONG style now dis plays the file size in addition to the modification date and time The directory style will be retained during an edit session and will be reset to BRIEF each time the editor is started When a USERDISK UUT LIBRARY or POD is copied to a port the direc tory will be sent in the current style BRIEF or LONG 1 12 Save System Calibration Settings The front panel SETUP SAVE menu can be used to save the current system settings or calibration settings on disk These settings can be saved in the cur rent userdisk or in a specified UUT Prior to 6 0 an error would occur if you tried to save the settings in a UUT that did not exist Now the UUT will au tomatically be created if it does not exist Page 9 New Features of Version 6 0 6 0 Release Notes 1 13 E Disk Changes The front panel MAIN MENU EDISK LOAD menu has two new fields that allow optional loading of TL source programs PROGRAM and com piled programs OBJPROG into the E disk Prior to 6 0 TL 1 programs were always loaded into the E disk If all of your TL 1 programs have been compiled the source TL 1 source pro grams are not needed when a program is executed This means that you can load the E disk faster and use less memory for the E disk if you load the compiled object programs which are required for e
23. or message Load failed old format A 6 0 response file can be converted to a pre 6 0 file format as follows Page 35 Known Bugs in Version 6 0 6 0 Release Notes 9100A 380 9100 398 9100A 459 1 load 6 0 software on your 9100 and then COPY the rc sponse file to a text file 2 edit the text file and replace any characters that appear in the Async LVL or Clk LVL fields with a space 3 load 5 0 or earlier software on your 9 100 and then COPY the text file to a response file COPY to Port does not copy all of RESPONSE file data DESCRIPTION When using COPY in the editor to print RESPONSE files copy the file to a port the Priority Pin section of the file is not copied Doing a COPY to coerce the RESPONSE file to a TEXT file also loses the Priority Pin data This means that there is no way for a user to get a printout of all ofthe infor mation in a RESPONSE file QUIT key not always recognized in OFFSET window DESCRIPTION If you enter the response OFFSET window and begin LOOP ing the QUIT key should abort the program execution How ever sometimes you must press the QUIT key several times before it is responded to WORKAROUND Pres the QUIT key several times Intermittent Hanging of IEEE 488 DESCRIPTION TEEE488 communication between a 9400FT and a Fluke 1722A occasionally hangs It is difficult to reproduce the problem but it seems to happen more often when the 9100 is tmasferring a file to the 17
24. r it stored the program in a case sensitive symbol table as required by the published semantics of TL 1 The next time the program was invoked the symbol table was searched for foo F00 was in the symbol table but not foo so the program was loaded again The bug is that the actual name of the program was not checked once the program was loaded TL 1 should preserve linkage amp space when exercising faults DESCRIPTION Space and linkage should be the same for each iteration of an exerciser It isn t being newly set so if an exerciser does a set space second and subsequent iterations may perform differ ent UUT accesses from the first iteration which is bad Editor PASTE misbehaves if there are blanks at the end of the line Page 19 Rugs Fixed in Version 6 0 6 0 Release Notes 9100A 266 9100A 267 DESCRIPTION It is not possible to PASTE at the end of a program line if the line ends in one or more blanks Instead of the pasted text be ing put at the end of the line it is inserted before the trailing blanks and all of the blanks remain at the end of the line For example on the following line with the cursor at the end print Test line lt cursor is here gt PASTE text has this result print Test line This is the pasted text lt end of line here gt 9100 cannot always tell if pod database name does not match pod type DESCRIPTION Plug in a Z80 pod with the UUT cable in the selftest socket
25. re jeee_out open device portl as output mode unbuf fered CR print term Page 30 6 0 Release Notes Known Bugs in Version 6 0 9100A 253 9100A 256 9100A 257 icee_in open device portl as input disp open device fterm2 as output vatious bugs using TL 1 editor DESCRIPTION Here are a couple of intermittent bugs When scrolling up or down the screen will go blank On the left side of the screen lt s appear in inverse video The up and down scrolls lock up but one can recover by pressing the Begin File key Also duplicate lines are made when scrolling up and down The last line on the bottom is duplicated and stays on screen until it is scrolled past Also scrolling up and down causes stuck beeper on 9100 WORKAROUND Press the lt Begin File gt key Application interface loses cursor DESCRIPTION 1 Place the front panel cursor in rightmost field of the address option display DWORD of 80386 MEMORY DWORD 2 Execute a program that leaves the machine in a memory space with less fields in the address option I O space of 80386 3 Try to do a read or other function from the front panel When you go down to the address option field the cursor dis appears WORK AROUND A left arrow key will make the cursor appear Editor REPLACE can t replace with in programs DESCRIPTION On the following TL I line t t REPLACE with and it worked for the fir
26. remote mode when successive print on ieee_device statements arc issued from TL 1 without a sufficient time delay between the statements the talker listener device breaks out of remote mode before the data from the second print statement hasbeen sent and displays FLUKE DIGITAL TEST STATION READY TestRAMfast bug DESCRIPTION When running RAM TEST with a data mask that is not FFFF a RAM TEST fault message shows that data was written to bits that were zeroed out in the data mask IEEE REMOTE get setspace bug DESCRIF TION When TL 1 setspace is used within the REMOTE interface it does not take effect until the remote interface is exited and restarted i e from IEEE controller s point of view with 9 1 XX as Talk Listen Controller 91XX GoToRemote lt fine gt setspace space 3 lt fine gt read adclr 0 lt reads at address 0 in default address space not 3 gt GoToLocal lt fine gt GoToRemote lt fine gt read addr 0 lt reads at address 0 in address space 3 gt IEEE REMOTE cannot podsetup DESCRIPTION Because of the syntax of podsetup commands they cannot be called through the remote interface For example the TL I call podsetup report intr off has no representation in the remote message syntax Page 25 Bugs Fixed in Version 6 0 6 0 Release Notes 9100A 309 9100A 317 9100A 339 The fix will allow the following invocation syntax podsetup report intr
27. ress TEST BUS ENTER and bus test runs 2 Press EXEC 3 Press REPEAT which enters an _ in the UUT field 4 Now press ALPHA ENTER You get an error message 5 Instead Press ALPHA REPEAT Bus Test works The problem is that _ is an illegal UUT name so an error occurs when you attempt to search for the program in uut _ Error message doesn t display argument name DESCRIPTION In the following program function bar is called with an ille gal argument blah The error message that results is is not a legal argument The name blah should appear between the quotes program foo function bar return end function bar blah 1 end program TL 1 exercisers not found if fault was re faulted DESCRIPTION If a built in fault is handied by a handler then re raised via the refault command TL 1 cannot find the exerciser for the fault Memory Gobbler Looping 9132 Pod Self Test DESCRIPTION Looping Selftest on a 9132 Pod eats memory in 4Kchunks This is on a working POD with selftest passing I know it ex ists on with a 386 pod support package but believe it to be with any support package Testing ONLY Sync Module when bug discovered 9100 ignores illegal parameter pod fault on write virtual Page 23 Bugs Fixed in Version 6 0 6 0 Release Notes 9100A 295 9100A 297 9100A 299 9100A 302 DESCRIPTION The 9100 ignores the illegal parameter fault bit when rctumced by a 9132 pod on a write vi
28. rtual operation The 9132 sets the fault when illegal data is written to a special address This is intended to let the user know he wrote illegal data but wc cannot give him the message Trailing characters after valid floating point number ig nored by TL 1 isflt DESCRIPTION The isflt operator evalutes a string expression and returns 1 if it is a valid floating point expression and 0 if it is not Cur rently isflt returns 1 valid on a particular invalid floating point expression Strings of the form 2 3e or 2e or 2E are considered val id by isflt however they are treated as syntax errors when a floating point number is set to their floating point equivalents The trailing characters after a valid floating point number are ignored by isflt The function uses only the leading valid part Disk ID error after sector COPY DESCRIPTION If you do a sector copy COPY DR1 to DR1 and immedi ately afterwards try to edit DR1 you get the following error Disk ID Error 9105 hangs when you try to open a file on the hard disk DESCRIPTION If you execute the following program on a 9105 it will hang program x ch open device HDR JANET as output close channel ch end program IEEE remote interface needs delay between print state ments Page 24 6 0 Release Notes Bugs Fixed in Version 6 0 9100A 304 9100A 305 9100A 306 DESCRIPTION On a talker listener device operating in
29. st quote Do a SHIFT REPLACE for the second quote and the following message is displayed Page 31 Known Bugs in Version 6 0 6 0 Release Notes 9100A 261 9100A 264 9100A 273 9100A 278 String not closed by end of line Missing double quote TEST BUS menu selection display disappears DESCRIPTION Perform TEST BUS from the front panel Select another op eration such as READ ADDR Press the BUS TEST key At this point the bus test softkey labels are missing There should be two selections displayed WORK AROUND Press BUS TEST key a second time or press the left arrow key to get the selections to be displayed Editor display problems DESCRIPTION Using the up arrow and down arrow keys in the editor the screen gets garbled with just a gt shown in the left margin Sometimes when using the up arrow and down arrow keys lines are duplicated WORK AROUND This appears to be related to the problem of displaying long lines lines which wrap around A work around for both cas es is to hit the INFO key which forces the screen to redisplay properly FutureNET translate bug in CADTrans DESCRIPTION A customer uses a DATA statement after the SIG statement and before the NAME statement FutureNET incorrectly throws away these net names WORK AROUND Remove the DATA statement from the FutureNET netlist MORE INFORMATION LED left on incorrectly Page 32 6 0 Release Notes Known Bugs in Version 6 0
30. th to resolve part references First they will look in the UUT If the part is not found there they will look in the part library If it is not found there an error message will be displayed Compatibility UUTs that are created with 6 0 or later software and contain parts can be used with 5 0 or earlier software however the parts will not ap pear in the UUT directory and cannot be accessed Page 8 6 0 Release Notes New Features of Version 6 0 1 9 Editor Line Syntax Checking The line syntax checking can now be disabled for TL 1 programs and node lists To disable line syntax checking edit a program or node list and simultaneous ly press the Shift key and the CHECK softkey This key combination will toggle the line checker on and off The current mode is displayed in the status line at the top of the CRT The line checking mode is shared between pro grams and node lists and is saved across edit sessions The current line must be correct before the line checking mode can be changed Comnatibility programs and node lists that were saved with line syntax er rors can be edited with 5 0 or earlier software 1 10 Terminal Emulator Improvements The terminal emulator has been improved to support transferring TL pro grams and node lists Prior to 6 0 only text files could be transferred To send or receive a file enter the file name and then use the field selectkey to select the file type TEXT or PROGRAM or NODE 1 11 Edit
31. trol the type of warning messages that are is sued Warning messages are precautionary and attempt to identify features of Pag e6 6 0 Release Notes New Features of Version 6 0 the TL l program that could be bugs or are unnecessary Refer to section 3 1 9 Compiling a TL Program in the Programmer s M anual for a com plete description of the se options and how to change them 1 3 TLA Program Debugger Improvements The TL 1 debugger has been improved to allow debugging across multiple programs This includes the ability to display called programs set break points in a called program and step into a called program Another improve ment allows access to array variable elements For fastest debugger start up pre compile the TL 1 programs to be debugged A new VIEW softkey prompts for a program name and then displays the pro gram The STEP softkey now steps into a called program and automatically displays the called program The BREAK softkey can now set breakpoints in any program that is displayed 1 4 TLA Check The TL 1 program checker is invoked when a program is being edited and the CHECK softkey is pressed CHECK has been improved to detect many errors which previously were not found until program execution CHECK now identifies the same errors that the new TL 1 compiler will identify and has the effect of embedding compiler error messages into the program To check a program edit the program and press the CHECK softke
32. ves the PODNAME at the default pod instead of changing to the stored podname Page 33 Known Bugs in Version 6 0 6 0 Release Notes 9100A 286 9100A 292 9100A 296 WORK AROUND Possibly do a manual setup pod name before restoresystcm settings I don t know of any bad side effects The reverse order setup after restore probably changes some setup info back to default Empty TL 1 loop cannot be stopped DESCRIPTION The following five line program will cause the system to lock up when run in the debugger By commenting out the close channel line the bug will disappear and the program can be stopped by pressing the QUIT key program bug ochannel open device term2 as output mode unbuffered ochannell open device term2 win close channel ochannell loo nt loop end program old parameter list displayed for 9132 bustest DESCRIPTION If RAMTEST HYPER is executed on a 9 132 pod then BUS TEST key is pressed the RAMTEST HYPER parameters ap pear on the 3 line display after the words TEST BUS WORK AROUND Press the left arrow key until the cursor is in the left most field This will cause the BUS TEST parameters to appear Constant Bell At End Of Editor Line DESCRIPTION A constant bell can occur when scrolling to the end of a line with the RIGHT SCROLL key pressed down At the end of the line the bell continuously sounds and scrolling up down Page 34 6
33. xecution but do not load the TL 1 source programs into the E disk If you specify that OBJPROGs should be loaded and PROGRAMS should not be loaded the system will generate a warning message if it finds that a PROGRAM needs to be compiled or an OBJPROG needs to be recompiled e g the TL 1 source program was modified but not recompiled Page 10 6 0 Release Notes Incompatibilities Between Version 6 0 and 5 0 2 Incompatibilities Between Version 6 0 and 5 0 Every effort has been made to insure identical behavior between TL 1 pro grams executed under the interpreter and the compiled runtime system How ever some differences were unavoidable and these differences are described below 2 1 TL Software Timing Loops Compiled TL 1 programs execute faster than interpreted TL 1 programs Therefore any software timing loops in TL I programs may need to be mod ified An example of a software timing loop appears below loop for i to 1000 end loop 2 2 Implicit UUT Timing Programs may also contain implied timing that assumes a relationship be tween TL 1 execution speed and UUT activity For example a program may send a sequence of commands to an electromechanical device such as a vac uum fixture relay or disk drive This program may have worked properly with the 5 0 software because the device had enough time to carry out each command before it received the next command from the TL 1 program However with the increased e
34. xecution speed of 6 0 the TL I program may send commands to the device before the device is ready 2 3 TL Programs Can t Be Executed Due to Compilation Errors There are many kinds of program errors that were not found by the TL 1 in terpreter until program execution An example of such an error is assigning a string value to a numeric variable With the interpreter you would encoun ter these errors one at a time when a statement with an error was executed If these errors were in a branch of the code that had not been executed previ ously you may not even be aware of these errors With the compiled runtime system all of these types of errors are discovered before the program is executed when it is compiled This lets you be confi dent that fewer runtime errors will occur to stop execution of your programs However because the compiled T L rtmtime system examines every pro gram statement when it compiles the program some programs may not com pile and the new compiled runtime system cannot execute a program unless it compiles successfully Page 11 Incompatibilities Between Version 6 0 and 5 0 6 0 Release Notes This means that some programs that you were able to execute with the inter preter cannot be executed with the compiled runtime system until you fix all the compilation errors Typically these errors are very easy to fix and often involve things like misspelled variable names incorrect arguments to func tions
35. y Use the field select key to select YES in response to the prompt USE CURRENT TL 1 COMPILER OPTIONS and then press the Return key The program checker has options that control the types of warning messages that are issued Warning messages are precautionary and attempt to identify features of the TL 1 program that could be bugs or are unnecessary Refer to section 3 1 6 Using the CHECK Function in the Programmer s Manual for a complete description of these options and how to change them 1 5 New TL 1 Function diagnoserom The diagnoserom function provides access to the existing ROM diagnostics This function can be used with your customized ROM tests or with Pod Quick Tests to provide diagnostics and fault conditions which are consistent with those of the testromfull ROM test Usage diagnoserom addr upto mask addrstep a or diagnoserom addr lt addr gt upto lt upto gt mask lt mask gt addrstep lt addrstep gt Page 7 New Features of Version 6 0 6 0 Release Notes 1 6 New TL 1 Function sysinfo The sysinfo function returns information about the system Currently the system software version or the model name can be obtained Usage version sysinfo get system version version sysinfo get system model returns one of the following 9100A 9105A 9100FT or 9105FT 1 7 GFI Don t Care Logic Levels GFI and UFI determine if a node is good by comparing a measured response with th
Download Pdf Manuals
Related Search