Project

General

Profile

Support #1175 » TLAOfflineReadMe.txt

JonR, 06/20/2016 07:42 AM

 
1

    
2
===========================================================
3
                   Tektronix TLA Offline (TM)
4
                       Version 5.0
5
                       June 7, 2005
6
===========================================================
7

    
8

    
9
This readme file briefly discusses the Offline capability of the
10
TLA application software and ways to configure it so that it will
11
simulate the presence of LA and DSO acquisition modules.
12

    
13
Contents of this readme file:
14

    
15
    1.  INTENDED USE
16
    2.  DISTRIBUTION & AVAILABILITY
17
    3.  LICENSING
18
    4.  INSTALLATION, COMPATIBILITY, POSSIBLE PROBLEMS
19
    5.  BEHAVIOR & LIMITATIONS
20
    6.  VIEWING DATA
21
    7.  MICROPROCESSOR SUPPORT PACKAGES
22
    8.  TPI & TLASCRIPT
23
    9.  TECHNICAL SUPPORT
24
    10. TLA CONFIGURATION FILE
25
    11. STRUCTURE OF THE TLA CONFIGURATION FILE
26
    12. WAYS TO MODIFY THE TLA CONFIGURATION FILE
27
    13. LOAD SYSTEM
28
    14. VISASTUB.INI FRAGMENTS
29
    15. EDITING VISASTUB.INI
30
    16. EXPANSION MAINFRAMES
31
    17. EXTERNAL OSCILLOSCOPE
32
    18. TLA OFFLINE SUPPORT FILES
33

    
34

    
35
---------------
36
1. INTENDED USE
37
---------------
38

    
39
offline data viewing that complements the
40
Tektronix Logic Analyzer Family.  The primary purpose of Offline is to
41
allow TLA users to view, from a regular PC, TLA acquisition data that
42
was previously acquired and saved to an accessible file.  Although you
43
can configure Offline to contain simulated LA and DSO modules, that is
44
not the primary purpose of the software.
45

    
46
Offline supports the TLA700, TLA600, TLA5000 and TLA7000 Series Logic Analyzers.
47

    
48
TLA Offline does not support the Tektronix TLA7PG2 Pattern Generator modules.  
49

    
50

    
51
------------------------------
52
2. DISTRIBUTION & AVAILABILITY
53
------------------------------
54

    
55
Starting with V5.0, TLA Offline is a standard part Tektronix Logic 
56
Analyzer Software.
57

    
58
------------
59
3. LICENSING
60
------------
61

    
62
The TLA application software must be used in accordance with the 
63
terms of the accompanying license.
64

    
65
-------------------------------------------------
66
4. INSTALLATION, COMPATIBILITY, POSSIBLE PROBLEMS
67
-------------------------------------------------
68

    
69
TLA software is distributed on CD-ROM.  To install install it execute the 
70
Setup.exe program located on the CD-ROM (for example, D:\TLA Application SW\Disk1\Setup.exe).
71
TLA Software is compatable with Microsoft .NET Framework, thus is fully 
72
compatible only with Windows 2000 Professional and Windows XP Professional.  
73

    
74

    
75
This version of TLA Software is compatible with V4.4 TLA application software
76
or earlier (can read save files from V4.4 and older).  For best
77
results, use with data acquired by a TLA running V4.4 TLA application
78
software.  
79

    
80
--------------------------
81
5. BEHAVIOR & LIMITATIONS
82
--------------------------
83

    
84
When operating the TLA Aplication software in Offline operating mode
85
the system operates with some ability to simulate hardware functions.
86
For TLA users,the primary intended purpose of Offline is to provide a way 
87
to view previously acquired and saved TLA data "offline" on a separate PC.
88
Offline can also be configured to "contain" simulated LA and DSO
89
modules.  
90

    
91
If you choose to configure it with simulated acquisition modules you 
92
should be aware that only a small amount of the actual functionality of 
93
the module is simulated.  Most of the TLA's acquisition capabilities are 
94
not supported.  Here is a very brief and incomplete list TLA features 
95
and their support in TLA Offline:
96

    
97
	Viewing saved data	Supported
98
	LA Modules		Simulated
99
	DSO Modules		Simulated
100
	External Oscilloscope	Simulated
101
	Expansion Mainframes	Simulated
102
	Running (acquiring)	Simulated
103
	Acquisition Data	Simulated
104
	Viewing simulated data	Supported
105
	Glitch Data		Simulated
106
	LA Channel Grouping	Supported
107
	LA Memory Depth		Simulated
108
	LA Trigger Position	Simulated
109
	LA Triggering		No effect on data
110
	LA Storage Settings	No effect on data
111
	DSO vertical		Simulated
112
	DSO Horizontal		Simulated
113
	DSO Trigger Position	Simulated
114
	DSO Trigger		No effect on data
115
	Cal & Diagnostics	Simulated
116
	TPI			Supported/Simulated
117
	TLAScript		Supported/Simulated
118
        Most other stuff	Supported
119

    
120
In a nutshell, operations that involve interaction with the module
121
hardware are either ignored or simulated (mostly ignored).  Operations
122
that are pure software mostly work as usual.
123

    
124
For detailed information on the behavior of the software, refer to the
125
TLA online help.
126

    
127
---------------
128
6. VIEWING DATA
129
---------------
130

    
131
Here are the major steps you should follow to use TLA Offline to view 
132
previously acquired TLA acquisition data.
133

    
134
	Step 1) Acquire data on a TLA
135
	Step 2) Save the acquired data
136
	Step 3) View the data using TLA Offline on a PC or TLA.
137

    
138
Step 1 is to acquire the acquisition data on a TLA.  It doesn't really
139
matter what the hardware or software configuration of the TLA is.  You
140
can use any module and any support package.  TLA Offline can be used to view
141
data acquired on a TLA that is running a version of TLA application
142
software that is pre-version 4.4 because Offline is compatible with
143
previous versions of TLA save files (.tla files).  It is recommended,
144
however, that the TLA be running version 4.4 software.
145

    
146
Step 2 is to save the acquired data somewhere that is accessible by the
147
PC or TLA.  It is most convenient, of course, if you can save
148
the data to a networked drive that is accessible to both the TLA and
149
the machine running TLA Offline.  The TLA's internal CD-RW drive may be used
150
to save large amounts of acquisition data on a CD for easy transfer to
151
other machines.  
152

    
153
There are a couple of different ways that you can actually save the
154
data:
155

    
156
	a) Save Module
157
	b) Save System
158

    
159
The Save Module operation saves only the raw data that was acquired by
160
a specific module.  It does not save any of the data windows that may
161
exist that are displaying that data.  If you use this operation to save
162
the acquisition data you will need to create a completely new data
163
window to view that data (as opposed to loading a previously
164
saved data window).
165

    
166
The Save System operation saves all of the raw data for all of the
167
modules in the system and it also saves all of the data windows that
168
exist that are displaying data from any data source (real or previously
169
saved).  If you use this operation to save the acquisition data you
170
will have the choice of creating a completely new data window
171
to view the data, loading one of the data windows that was saved when
172
you did the Save System, or doing a Load System operation to load all
173
modules, acquisition data and data windows from the saved system.
174

    
175
Step 3 is to view the data in TLA Offline.  There are three ways to view the 
176
previously saved data:
177

    
178
	a) Load System
179
	b) New Data Window
180
	c) Load Data Window
181

    
182
The Load System operation loads the previously saved system.
183
This operation actually changes the Configuration of the TLA application
184
that is using Offline operating mode.   The Offline configuration will
185
match that of the saved system.  All of the modules, acquisition data
186
and data windows in the saved system are loaded.
187

    
188
The New Data Window operation creates a completely new data window.
189
You can either create a data window that initially has no data in it
190
and then incrementally add waveforms or columns of data, or you can
191
create a new data window and specify your previously saved data as the
192
data source.  In either case you will at some point in the process need
193
to press a button named "Add Data Source...".  This is where you
194
specify the file that contains the saved data.  This method of viewing
195
saved data (New Data Window) will work with a file that was created by
196
either the Save Module or the Save System operation on the TLA.
197

    
198
The Load Data Window operation loads a previously saved data window.
199
This will only work if the file containing the saved data was created
200
on the TLA using the Save System operation.  This is because only the
201
Save System operation saves data windows.
202

    
203
If your data was being viewed in a disassembled format, you will need
204
to install the appropriate microprocessor support package on the PC or
205
TLA mainframe running TLA software.
206

    
207
----------------------------------
208
7. MICROPROCESSOR SUPPORT PACKAGES
209
----------------------------------
210

    
211
If you are using a microprocessor support package on the TLA, you will
212
need to also install that support package on any PC that is to display
213
this data.  The media used to install the support package on the TLA 
214
can also be used to install the support package on your PC.
215

    
216
------------------
217
8. TPI & TLASCRIPT
218
------------------
219

    
220
TLA Offline can be programmatically controlled via TPI, TPI.NET, or
221
TLAScript.  All of these can be used with Offline and they pretty much
222
act as they would with a real TLA with the exception that data
223
acquisitions are simulated.  Refer to the online TPI or TLAScript 
224
documentation for details.
225

    
226
If you you have more than one TLA application running, TPI.NET will only
227
support communications to one of these applications.  That is, the first
228
TLA Application started.
229

    
230
--------------------
231
9. TECHNICAL SUPPORT
232
--------------------
233

    
234
For technical support of TLA Offline, contact the Tektronix technical support
235
organization.  For contact information see the TLA online help
236
(choose Help > Technical Support in the TLA menu bar).
237

    
238
----------------------------
239
10. TLA OFFLINE CONFIGURATION FILE
240
----------------------------
241

    
242
TLA Offline is capable of simulating the presence of LA and DSO modules.
243
When TLA software starts, it reads a configuration file to see which LA and
244
DSO modules, if any, it should simulate.  That configuration file is:
245

    
246
	C:\Program Files\TLA 700\System\visastub.ini
247

    
248
To modify the TLA Offline configuration, you must modify this file.  Like any
249
program's .ini file, this information is formatted in a very specific
250
and exacting manner.  See the following sections for details.
251

    
252
---------------------------------------------
253
11. STRUCTURE OF THE TLA CONFIGURATION FILE
254
---------------------------------------------
255

    
256
The basic structure of the TLA Offline confuration file, visastub.ini,
257
is fairly simple.  It looks like this:
258

    
259
	Header
260
	Module 1 information
261
	Module 2 information
262
	...
263

    
264
The complexity is in the contents of each per-module information
265
section of the file.  This per-module information consists of many
266
lines of text, some of which must be unique for each module in the
267
configuration.
268

    
269
We have provided some files, located in the
270
C:\Program Files\TLA 700\Tools\TLAVu directory, that may help you 
271
should you want to change the configuration.  This support is 
272
discussed in sections that follow.
273

    
274
-----------------------------------------------
275
12. WAYS TO MODIFY THE TLA CONFIGURATION FILE
276
-----------------------------------------------
277

    
278
There are two different methods of modifying the OFFLINE configuration:
279

    
280
	A) Load System
281
	B) visastub.ini fragment files
282

    
283
These are described in the sections that follow.
284

    
285
---------------
286
13. LOAD SYSTEM
287
---------------
288

    
289
When the TLA Application is operatedn in Offline operating mode all
290
save restore operations are defined by the visastub.ini file.
291

    
292
The Load System operation, executed from the TLA application, loads a
293
previously saved system.    This operation actually changes
294
the configuration of TLA Offline to match that of the saved system.  All of
295
the modules, acquisition data and data windows in the saved system are
296
loaded.  Performing this operation actually modifies the
297
configuration file.  This is method is the most common means for reconfiguring
298
Offline.
299

    
300
If you don't have access to your own saved TLA system files, you can
301
modify the configuration by loading one of the demo files that is
302
shipped with TLA Software.  Do a Load System operation and browse to one of
303
the files in C:\Program Files\TLA 700\Tools\TLAVu\TLAFiles.
304

    
305
Because the configuration file is modified when you do a Load
306
System operation, the default configuration of TLA Software (configuration
307
when TLA Offline is started) and the behavior of the Default System operation
308
are affected by the previous Load System operation performed.  In other
309
words, the "default system" for TLA Offline is the configuration that
310
resulted from the previous Load System operation.
311

    
312
--------------------------
313
14. VISASTUB.INI FRAGMENTS
314
--------------------------
315

    
316
If you want to create a TLA configuration file that consists of an
317
arbitrary combination of modules, you will need to:
318
	1) Build yourself a custom visastub.ini file.  
319
	2) Then update the TekVISA resource list by opening the TekVISA
320
	   Instrument Manager and pressing the update button.
321

    
322
The best way to create a new visastub file is to use the
323
visastub.ini fragments that are located in the
324
C:\Program Files\TLA 700\Tools\TLAVu\Fragments directory.  We have 
325
built several visastub.ini file fragments, one for each unique type 
326
of TLA700 module.  The files are named:
327

    
328
	TLA***.TXT
329

    
330
where TLA*** is replaced by the name of the specific module type.
331
For example, TLA7N4.TXT or TLA7D1.TXT.  There is also a file that 
332
contains the header needed at the beginning of the visastub.ini file.  
333
It's name is:
334

    
335
	HEADER.TXT
336

    
337
Building your custom visastub.ini file consists of three steps:
338

    
339
	Step 1) Build the basic file
340
	Step 2) Edit the file so it will actually work
341
	Step 3) Copy it over to where it needs to reside
342
	Stup 4) Update the TekVISA Resource manager.
343

    
344
Step 1 consists of constructing a visastub.ini file that contains all
345
of the major sections of data needed to simulate the desired modules.
346
Something like this will work:
347

    
348
	COPY HEADER.TXT + TLA7P4.TXT + TLA7E2.TXT  MYSTUB.INI
349

    
350
Basically, you want to create a file that has the header at the top
351
followed by one section for each of the desired modules.  The example
352
above creates a file named MYSTUB.INI that contains the header, a P4
353
module, and an E2 module.  You might want to do this somewhere other
354
than the Fragments directory to reduce that chance of accidentally
355
moving or deleting one of the fragment files.  The TLA711, TLA720 or
356
TLA721 Controller "module" does not appear in the visastub.ini file as
357
a module per-se.  Simulating Expansion Mainframes is described in a
358
later section.
359

    
360
Step 2 is to edit the new ini file so that it will actually work.  This
361
is necessary except in the case where your new visastub.ini file
362
contains only one module.  If your file contains more than one module
363
you must edit the file for it to work properly.  This editing is
364
discussed in the following section.
365

    
366
Step 3, after you've edited the file appropriately, is to put it where
367
it needs to be - C:\Program Files\TLA 700\System\visastub.ini.  You
368
might want to backup the old visastub.ini file first in case you need
369
to recover you previous configuration.
370

    
371
Step 4 is done by right clicking on the yellow icon in on the windows
372
task bar.  Open the Instrument Manager.  Then press the Update button.
373
You should see a list of VXI1::N::INSTR Modules that make up your new 
374
configuration.
375

    
376
------------------------
377
15. EDITING VISASTUB.INI
378
------------------------
379

    
380
If your custom visastub.ini file was created by concatenating two or
381
more visastub.ini fragments, you will need at the very least to modify
382
the "VXI Info Line" of all of the modules except the first one.
383

    
384
VXI Info Line
385
-------------
386

    
387
	Each module section contains a line like the one below.
388
	Each field of the VXI Info Line is described in more
389
	detail below.
390

    
391
		4093 2004 3 255 V
392
		|||| |||| |  |
393
		|||| |||| |  +-----Logical Address (always 255)
394
		|||| |||| |
395
		|||| |||| +--------Slot Number     (varies)
396
		|||| ||||
397
		|||| ++++----------Model Code      (varies)
398
		||||
399
		++++---------------Manufacturer ID (always 4093)
400

    
401
	Note that there is a "V" at the end of the line.
402
	This is important - it needs to be there.  Don't
403
	accidentally delete it.
404

    
405
  Manufacturer ID
406

    
407
	Manufacturer ID is the first field in the VXI Info Line.
408
	The manufacturer ID must always be 4093.
409
	This identifies Tektronix as the module manufacturer.
410

    
411
  Model Code
412

    
413
	Model Code is the second field in the VXI Info Line.
414
	Here are the model codes currently in use:
415

    
416
	---------------------------------------------
417
	LA Modules	Model Code	Width	Depth
418
	---------------------------------------------
419
	TLA7L1		2033		34	128K
420
	TLA7L2		2034		68	128K
421
	TLA7L3		2035		102	128K
422
	TLA7L4		2036		136	128K
423

    
424
	TLA7M1		2037		34	512K
425
	TLA7M2		2038		68	512K
426
	TLA7M3		2039		102	512K
427
	TLA7M4		2040		136	512K
428

    
429
	TLA7N1		2001		34	4M
430
	TLA7N2		2002		68	4M
431
	TLA7N3		2003		102	4M
432
	TLA7N4		2004		136	4M
433

    
434
	TLA7P2		2006		68	16M
435
	TLA7P4		2008		136	16M
436

    
437
	TLA7Q2		2010		68	64M
438
	TLA7Q4		2012		136	64M
439

    
440
	TLA7AA1		1962		34	32M
441
	TLA7AA2		1963		68	32M
442
	TLA7AA3		1964		102	32M
443
	TLA7AA4		1965		136	32M
444

    
445
	TLA7AB2		1967		68	64M
446
	TLA7AB4		1969		136	64M
447

    
448
	TLA7NA1		1937		34	32M
449
	TLA7NA2		1938		68	32M
450
	TLA7NA3		1939		102	32M
451
	TLA7NA4		1940		136	32M
452

    
453
	-------------------------------------------------
454
	DSO Modules	Model Code	Chans	Bandwidth
455
	-------------------------------------------------
456
	TLA7D1		2025		2	500MHz
457
	TLA7D2		2026		4	500MHz
458

    
459
	TLA7E1		2027		2	1GHz
460
	TLA7E2		2028		4	1GHz
461

    
462
	-------------------------------------------------
463
	XM Module	Model Code
464
	-------------------------------------------------
465
	TLA7XM		3584  (Expansion Interface Module)
466

    
467
	-------------------------------------------------
468
	TLA600		Model Code	Width	Depth
469
	-------------------------------------------------
470
	TLA601		1024		34	256K
471
	TLA611		1024		34	256K
472
	TLA621		1028		34	1M
473
	TLA602		1025		68	256K
474
	TLA612		1025		68	256K
475
	TLA622		1029		68	1M
476
	TLA603		1026		102	256K
477
	TLA613		1026		102	256K
478
	TLA623		1030		102	1M
479
	TLA604		1027		136	256K
480
	TLA614		1027		136	256K
481
	TLA624		1031		136	1M
482

    
483
	-------------------------------------------------
484
	TLA5000		Model Code	Width	Depth
485
	-------------------------------------------------
486
	TLA5201		1041		34	8M
487
	TLA5202		1042		68	8M
488
	TLA5203		1043		102	8M
489
	TLA5204		1044		136	8M
490

    
491

    
492
  Slot Number
493

    
494
	Slot Number is the third field in the VXI Info Line.  It
495
	contains the VXI slot number that the module is installed in.
496
	It must be unique for each module within a given mainframe.
497
	Legal values are 0-12.  If TLA is configured as a benchtop
498
	mainframe, you will normally locate modules in slots 3-11
499
	because the TLA721 benchtop controller, which doesn't appear in
500
	the configuration file, occupies slots 0-2.  If TLA is
501
	configured as a portable mainframe, you will locate modules in
502
	slots 1-4.  Each LA and DSO module occupies two slots, so, for
503
	example, you can't have one LA or DSO module in slot 3 and
504
	another in slot 4.  The Expansion Interface Module occupies one
505
	slot.
506

    
507
  Logical Address
508

    
509
	Logical Address is the fourth field in the VXI Info Line.
510
	It must always be 255, which causes dynamic logical
511
	address assignment.
512

    
513
The visastub.ini fragments provided are not set up to allow merging of
514
multiple LA modules into a wider logical module.  If you want to do
515
this you will need to modify the "LA Merging Line" of the LA modules in
516
your visastub.ini file.
517

    
518
LA Merging Line 
519
---------------
520

    
521
	Each LA module has the a line like the following:
522

    
523
		>SYST:CONF:WELD:RES?<>XXXX>
524
		                      ++++
525

    
526
	Change the "XXXX" above to one of the following:
527

    
528
		NONE = not mergable
529
		MAST = connected to the module on the right
530
		SLAV = connected to the module on the left
531
		BOTH = connected to both adjacent modules
532

    
533
	Mergeable LA modules must be in adjacent slots.  In a two-way
534
	merge the first module would be set to MAST and the second one
535
	would be set to SLAV.  In a three-way merge the first module
536
	would be set to MAST, the middle one would be set to BOTH, and
537
	the third module would be set to SLAV.  There are other merging
538
	rules.  Look up "merge" in the TLA online help.
539

    
540
There are a few other lines in the visastub.ini file that are variant
541
and may be of interest.  They are described below.
542

    
543
Mainframe Type Line
544
-------------------
545

    
546
	Each visastub.ini file should have one line that identifies the
547
	mainframe type.  It looks like this:
548

    
549
		[CONTROLLER X X]
550

    
551
	Use one of the following:
552

    
553
	[CONTROLLER 1  0] 	# TLA704 Mainframe
554
	[CONTROLLER 0  0] 	# TLA711 Mainframe
555
	[CONTROLLER 1  4] 	# TLA714 Mainframe
556
	[CONTROLLER 0  4] 	# TLA720 Mainframe
557
	[CONTROLLER 0  5] 	# TLA600 Mainframe without front panel
558
	[CONTROLLER 1  5] 	# TLA600 Mainframe with front panel
559
	[CONTROLLER 1 13] 	# TLA5200 Mainframe
560
	[CONTROLLER 1 14] 	# TLA714 Mainframe with upgraded controller
561
	[CONTROLLER 1 15] 	# TLA715 Mainframe
562
	[CONTROLLER 0 15] 	# TLA721 Mainframe
563
	[CONTROLLER 1 1] 	# TLA7012 Mainframe
564
	[CONTROLLER 0 1] 	# TLA7016 Mainframe
565

    
566

    
567
Environment Lines
568
-----------------
569

    
570
	You should have the following lines in the file header:
571

    
572
		[DISPLAY_MESSAGE OFF]
573
		[TRACE ON]
574

    
575
	You should have the following line immediately following
576
	the VXI Info Line for each module section:
577

    
578
		[TERMINATION LF]
579

    
580
Module Configuration Line
581
-------------------------
582

    
583
	Each module has a line like the following:
584

    
585
		>*IDN?<>TEKTRONIX,TLAXXX,B000000,SCPI:94.0 FVER:9.9 S>
586
		                  ++++++
587

    
588
	Change the TLAXXX to a valid module type (see above).
589
	Must be consistent with the Model Code in the VXI Info Line.
590
	Everything else in the line is constant.
591

    
592
LA Width Line
593
-------------
594

    
595
	Each LA module has a line like the following:
596

    
597
		>SYST:CONF:WIDT?<>XXX>
598
		                  +++
599

    
600
	Change the XXX to a valid module width.  Legal values are 34,
601
	68, 102 or 136.  Must be consistent with the Model Code in the
602
	VXI Info Line and the module type in the LA Module
603
	Configuration Line.  Everything else in the line is constant.
604
	Remember that this is the width of the single, physical module,
605
	not the width of a logical merged module.
606

    
607
LA Depth Line
608
-------------
609

    
610
	Each LA module has a line like the following:
611

    
612
		>SYST:CONF:DEPT?<>XXXXXXXX>
613
		                  ++++++++
614

    
615
	Change the XXXXXXXX to a valid module depth.
616
	Legal values per module type are as follows:
617

    
618
		TLA7L*:	 32768, 131072
619
		TLA7M*:	 524288
620
		TLA7N*:	 65536, 262144, 1048576, 4194304
621
		TLA7P*:	 16777216
622
		TLA7Q*:  67108864
623
		TLA7AA*: 131072, 524288, 2097152, 8388608, 33554432
624
		TLA7AB*: 67108864
625
		TLA7NA*: 131072, 524288, 2097152, 8388608, 33554432
626
		TLA60*:  65536, 262144
627
		TLA61*:  65536, 262144
628
		TLA62*:  1048576
629
		TLA520*: 524288, 2097152, 8388608
630

    
631
LA Sync Speed Line
632
------------------
633

    
634
	Each LA module has a line like the following:
635

    
636
		>SYST:CONF:SPE?<>XXX>
637
		                 +++
638

    
639
	Change the XXX to a valid maximum synchronous acquisition speed
640
	in MHz for the module.  Legal values per module type are as
641
	follows:
642

    
643
		TLA7L*:	 100, 200
644
		TLA7M*:	 100, 200
645
		TLA7N*:	 100, 200
646
		TLA7P*:	 100, 200
647
		TLA7Q*:  100, 200
648
		TLA7A**: 120, 235, 450
649
		TLA7NA*: 235, 450
650
		TLA6**:  100, 200
651
		TLA520*: 235
652

    
653
LA Async Clock Period Line
654
--------------------------
655

    
656
	Each LA module has a line like the following:
657

    
658
		>SOUR:CLOC:PER?<>XXXXXXXXXXX>
659
		                 +++++++++++
660

    
661
	Change the XXXXXXXXXX to a valid minimum asynchronous 
662
	acquisition clock period in seconds for the module.
663
	Legal values per module type are as follows:
664

    
665
		TLA7L*:	 4.0000e-009
666
		TLA7M*:	 4.0000e-009
667
		TLA7N*:	 4.0000e-009
668
		TLA7P*:	 4.0000e-009
669
		TLA7Q*:  4.0000e-009
670
		TLA7A**: 2.0000e-009
671
		TLA7NA*: 2.0000e-009
672
		TLA6**:  4.0000e-009
673
		TLA520*: 2.0000e-009
674

    
675
MagniVu Sample Rate Line
676
------------------------
677

    
678
	Each LA module has a line like the following:
679

    
680
		>SYST:CONF:TICL:HRES?<>XXX>
681
		                       +++
682

    
683
	Change the XXX to the correct MagniVu sample rate in ps for 
684
	the module.  Legal values per module type are as follows:
685

    
686
		TLA7L*:	 500
687
		TLA7M*:	 500
688
		TLA7N*:	 500
689
		TLA7P*:	 500
690
		TLA7Q*:  500
691
		TLA7A**: 125
692
		TLA7NA*: 125
693
		TLA6**:  500
694
		TLA520*: 125
695

    
696

    
697
------------------------
698
16. EXPANSION MAINFRAMES
699
------------------------
700

    
701
An Expansion Mainframe can be simulated by placing simulated Expansion
702
Interface Modules (TLA7XM) in the visastub.ini file.  Unlike LA and DSO
703
modules, which have many lines of data associated with them in the
704
visastub.ini file, the information for an Expansion Interface Module
705
consists of just one line - the VXI Info Line for that module type.
706
The line is "4093 3584 <slot> 255 V", where <slot> is replaced by the
707
slot in the mainframe in which the module resides.
708

    
709
All modules in the visastub.ini file that follow the Expansion
710
Interface Module line will be placed in an Expansion Mainframe.  To
711
build a configuration consisting of a Mainframe containing one LA
712
module and an Expansion Mainframe containing one DSO module, you'd put
713
the module info in the visastub.ini file in the following order:
714

    
715
	Header
716
	LA Module (in the slot of your choice)
717
	XM Module (in, say, slot 12)
718
	DSO Module (in the slot of your choice)
719

    
720
Here's an example with two Expansion Mainframes:
721

    
722
	Header
723
	LA Module in slot 3	(Mainframe)
724
	DSO Module in slot 5	(Mainframe)
725
	XM Module in slot 11	(Mainframe)
726
	LA Module in slot 1	(Expansion #1)
727
	LA Module in slot 7	(Expansion #1)
728
	XM Module in slot 12	(Mainframe)
729
	DSO Module in slot 1	(Expansion #2)
730

    
731
In a real system, there are two Expansion Interface Modules for each
732
Expansion Mainframe.  One resides in the main mainframe, in any slot
733
not occupied by the controller.  The other must reside in slot 0 of the
734
associated Expansion Mainframe.  In a visastub.ini file that simulates
735
expansion mainframes, the Expansion Interface Module that resides in
736
slot 0 of the Expansion mainframe should not be included.
737

    
738
Configurations with more than two Expansion Mainframes are invalid.
739

    
740
-------------------------
741
17. EXTERNAL OSCILLOSCOPE
742
-------------------------
743

    
744
A connection to an external oscilloscope can be simulated with TLA Offline.
745
Unlike internal modules, the external oscilloscope is not added to the
746
system using the visastub.ini file.  Instead, to add a simulated
747
external oscilloscope to TLA, use the Add External Oscilloscope
748
Wizard, just as you would on a real TLA mainframe.  The added scope
749
will persist across invocations of TLA Offline.
750

    
751
-----------------------
752
18. TLA OFFLINE SUPPORT FILES
753
-----------------------
754

    
755
The following TLA support files are installed on your PC as part of
756
TLA Offline:
757

    
758
	C:\Program Files\TLA 700\Documentation\TLAOfflineREADME.TXT
759
		This is the file you are reading right now.
760

    
761
	C:\Program Files\TLA 700\Tools\TLAVu\Fragments\
762
		A subdirectory that contains fragments of the TLA
763
		configuration file (visastub.ini).  There is one file
764
		for each unique type of TLA module.  You can use these
765
		files as building blocks to create your own custom
766
		TLA configuration file (visastub.ini).  Details
767
		above.
768

    
769
		NOTE: You after creating a new visastub.ini file you
770
		must open the TekVISA resource manager and press the 
771
		update button.  The reads the new list of VXI modules
772
		found in the visastub file.
773

    
774
	C:\Program Files\TLA 700\Tools\TLAVu\TLAFiles\
775
		A subdirectory that contains a set of saved TLA system
776
		files (.tla files) that can be used to dynamically
777
		change the TLA configuration.  To change the TLA
778
		configuration to use Load System to load one of
779
		these files.  It is best to not disturb
780
		the contents of this directory.
781

    
782
-The End-
(11-11/13)