Tektronix Field Adjustment Software for TDS oscilloscopes

[charlyd]

Hi i have a TDS754D which has to be calibrated.  All went ok until the HF_CAL.  while doing this i get a domain error.

see pictures.  what can this error mean?

i use a fluke 6062A for the HF_cal and the Dm1 and my Ps1 both are in the G_config but not connected to my GPIB.
for dm1 i have a Fluke 8842A. and for the Ps1 i have a DP8200. 
Both have onboard GPIB but making an automated setup i get a Ps1 error everytime. i only have 1 PCIIA card and strugling with the GPIB so....

i decide to go for a manual setup, to get it over with..

so i was told to go for the manual calibration and no problem the CVR_cal is finished succesfully. but i go stuck in the HF_cal.

my TMode = MC    ( in the automated mode it was C )

what do i do wrong, i didn t interrupt any thing. the programm sort of crashed   can this be because of my router  file ?  r_config?


R_CONFIG:
----------------------------------------------------------------

################################################################
# $Header: build_file.c,v 1.1 91/05/21 15:44:23 miked Exp $
# $Revision: 1.1 $
#
# Section 1: Port Definitions
# <ref> <Port ID> <Port Description>
28  DMM         Digital Multi-Meter
27  PROBE_COMP      Front Panel Probe Compensation Output
26  PG_OUT      PG506 Fast Rise + Output
25  PS_OUT      Voltage Reference Output
24  CH4_CH3      DUT Channel 4 and 3 Input
23  CH4_CH2      DUT Channel 4 and 2 Input
22  CH4_CH1      DUT Channel 4 and 1 Input
21  CH3_CH4      DUT Channel 3 and 4 Input
20  CH3_CH2      DUT Channel 3 and 2 Input
19  CH3_CH1      DUT Channel 3 and 1 Input
18  CH2_CH4      DUT Channel 2 and 4 Input
17  CH2_CH3      DUT Channel 2 and 3 Input
16  CH2_CH1      DUT Channel 2 and 1 Input
15  CH1_CH4      DUT Channel 1 and 4 Input
14  CH1_CH3      DUT Channel 1 and 3 Input
13  CH1_CH2      DUT Channel 1 and 2 Input
12  CH4         DUT Channel 4 Input
11  CH3         DUT Channel 3 Input
10  CH2         DUT Channel 2 Input
9   CH1         DUT Channel 1 Input
8   CH4_WDM      DUT Channel 4 and DMM
7   CH3_WDM      DUT Channel 3 and DMM
6   CH2_WDM      DUT Channel 2 and DMM
5   CH1_WDM      DUT Channel 1 and DMM
4   DP8200      DC Voltage Reference Output
3   SG5030      SG5030 Output Head
2   SG504      Sinewave Generator (SG504) Output
1   SG503      Sinewave Generator (SG503) Output
################################################################
# Section 2: Connection definitions
# <ref> <C>   <openlist>      <port1> <port2> <Cable Desc>
57  C 56,55,54,53,49,42,26,10,2        26  9 BNC CABLE
56  C 57,55,54,52,48,41,25,9        26 10 BNC CABLE
55  C 57,56,54,51,47,40,24,8        26 11 BNC CABLE
54  C 57,56,55,50,46,39,23,7        26 12 BNC CABLE
53  C 57,52,51,50,49,42,26,10,2        25  9 BNC CABLE
52  C 56,53,51,50,48,41,25,9        25 10 BNC CABLE
51  C 55,53,52,50,47,40,24,8        25 11 BNC CABLE
50  C 54,53,52,51,46,39,23,7        25 12 BNC CABLE
49  C 57,53,48,47,46,45,44,43,42,26,10,2  1  9 PN 012-0482-00 BNC CABLE
48  C 56,52,49,47,46,45,44,43,41,25,9     1 10 PN 012-0482-00 BNC CABLE
47  C 55,51,49,48,46,45,44,43,40,24,8     1 11 PN 012-0482-00 BNC CABLE
46  C 54,50,49,48,47,45,44,43,39,23,7     1 12 PN 012-0482-00 BNC CABLE
45  C 49,48,47,46,44,43,38,22        1 13 PN 067-0525-02 DUAL BNC CONN
44  C 49,48,47,46,45,43,37,21        1 14 PN 067-0525-02 DUAL BNC CONN
43  C 49,48,47,46,45,44,36,20        1 15 PN 067-0525-02 DUAL BNC CONN
42  C 57,53,49,41,40,39,38,37,36,35,34,33,32,31,30,29,28,27,26,10,2  2   9 DIRECT
41  C 56,52,48,42,40,39,38,37,36,35,34,33,32,31,30,29,28,27,25,9     2 10 DIRECT
40  C 55,51,47,42,41,39,38,37,36,35,34,33,32,31,30,29,28,27,24,8     2 11 DIRECT
39  C 54,50,46,42,41,40,38,37,36,35,34,33,32,31,30,29,28,27,23,7     2 12 DIRECT
38  C 45,42,41,40,39,37,36,35,34,33,32,31,30,29,28,27,22        2 13 PN 067-0525-02 DUAL BNC CONN
37  C 44,42,41,40,39,38,36,35,34,33,32,31,30,29,28,27,21        2 14 PN 067-0525-02 DUAL BNC CONN
36  C 43,42,41,40,39,38,37,35,34,33,32,31,30,29,28,27,20        2 15 PN 067-0525-02 DUAL BNC CONN
35  C 42,41,40,39,38,37,36,34,33,32,31,30,29,28,27,19           2 16 PN 067-0525-02 DUAL BNC CONN
34  C 42,41,40,39,38,37,36,35,33,32,31,30,29,28,27,18           2 17 PN 067-0525-02 DUAL BNC CONN
33  C 42,41,40,39,38,37,36,35,34,32,31,30,29,28,27,17           2 18 PN 067-0525-02 DUAL BNC CONN
32  C 42,41,40,39,38,37,36,35,34,33,31,30,29,28,27,16           2 19 PN 067-0525-02 DUAL BNC CONN
31  C 42,41,40,39,38,37,36,35,34,33,32,30,29,28,27,15           2 20 PN 067-0525-02 DUAL BNC CONN
30  C 42,41,40,39,38,37,36,35,34,33,32,31,29,28,27,14           2 21 PN 067-0525-02 DUAL BNC CONN
29  C 42,41,40,39,38,37,36,35,34,33,32,31,30,28,27,13           2 22 PN 067-0525-02 DUAL BNC CONN
28  C 42,41,40,39,38,37,36,35,34,33,32,31,30,29,27,12           2 23 PN 067-0525-02 DUAL BNC CONN
27  C 42,41,40,39,38,37,36,35,34,33,32,31,30,29,28,11           2 24 PN 067-0525-02 DUAL BNC CONN
26  C 57,53,49,42,25,24,23,22,21,20,19,18,17,16,15,14,13,12,11,10,2  3   9 DIRECT
25  C 56,52,48,41,26,24,23,22,21,20,19,18,17,16,15,14,13,12,11,9     3 10 DIRECT
24  C 55,51,47,40,26,25,23,22,21,20,19,18,17,16,15,14,13,12,11,8     3 11 DIRECT
23  C 54,50,46,39,26,25,24,22,21,20,19,18,17,16,15,14,13,12,11,7     3 12 DIRECT
22  C 45,38,26,25,24,23,21,20,19,18,17,16,15,14,13,12,11        3 13 PN 067-0525-02 DUAL BNC CONN
21  C 44,37,26,25,24,23,22,20,19,18,17,16,15,14,13,12,11        3 14 PN 067-0525-02 DUAL BNC CONN
20  C 43,36,26,25,24,23,22,21,19,18,17,16,15,14,13,12,11        3 15 PN 067-0525-02 DUAL BNC CONN
19  C 35,26,25,24,23,22,21,20,18,17,16,15,14,13,12,11           3 16 PN 067-0525-02 DUAL BNC CONN
18  C 34,26,25,24,23,22,21,20,19,17,16,15,14,13,12,11           3 17 PN 067-0525-02 DUAL BNC CONN
17  C 33,26,25,24,23,22,21,20,19,18,16,15,14,13,12,11           3 18 PN 067-0525-02 DUAL BNC CONN
16  C 32,26,25,24,23,22,21,20,19,18,17,15,14,13,12,11           3 19 PN 067-0525-02 DUAL BNC CONN
15  C 31,26,25,24,23,22,21,20,19,18,17,16,14,13,12,11           3 20 PN 067-0525-02 DUAL BNC CONN
14  C 30,26,25,24,23,22,21,20,19,18,17,16,15,13,12,11           3 21 PN 067-0525-02 DUAL BNC CONN
13  C 29,26,25,24,23,22,21,20,19,18,17,16,15,14,12,11           3 22 PN 067-0525-02 DUAL BNC CONN
12  C 28,26,25,24,23,22,21,20,19,18,17,16,15,14,13,11           3 23 PN 067-0525-02 DUAL BNC CONN
11  C 27,26,25,24,23,22,21,20,19,18,17,16,15,14,13,12           3 24 PN 067-0525-02 DUAL BNC CONN
10  C 57,53,49,42,26,9,8,7,6,5,4,3,2      4  9 BNC CABLE
9   C 56,52,48,41,25,10,8,7,6,5,4,3      4 10 BNC CABLE
8   C 55,51,47,40,24,10,9,7,6,5,4,3      4 11 BNC CABLE
7   C 54,50,46,39,23,10,9,8,6,5,4,3      4 12 BNC CABLE
6   C 10,9,8,7,5,4,3            4  5 BNC CABLE AND BNC TEE
5   C 10,9,8,7,6,4,3            4  6 BNC CABLE AND BNC TEE
4   C 10,9,8,7,6,5,3            4  7 BNC CABLE AND BNC TEE
3   C 10,9,8,7,6,5,4            4  8 BNC CABLE AND BNC TEE
2   C 57,53,49,42,26,10,1        27  9 BNC CABLE WITH 013-0076-00 Y-CONNECTOR
1   C 2                 27 28 BNC CABLE WITH 013-0076-00 Y-CONNECTOR
#
################################################################
# Section 3: Path Definitions
#
#            < auto close>    <  manual >
#<output> <input>     < c   o >    <close open>  <reset>
PG_OUT      CH1      X   X   57   X   O
PG_OUT      CH2      X   X   56   X   O
PG_OUT      CH3      X   X   55   X   O
PG_OUT      CH4      X   X   54   X   O
PS_OUT      CH1      X   X   53   X   O
PS_OUT      CH2      X   X   52   X   O
PS_OUT      CH3      X   X   51   X   O
PS_OUT      CH4      X   X   50   X   O
SG503      CH1      X   X   49   X   O
SG503      CH2      X   X   48   X   O
SG503      CH3      X   X   47   X   O
SG503      CH4      X   X   46   X   O
SG503      CH1_CH2   X   X   45   X   O
SG503      CH1_CH3   X   X   44   X   O
SG503      CH1_CH4   X   X   43   X   O
SG504      CH1      X   X   42   X   O
SG504      CH2      X   X   41   X   O
SG504      CH3      X   X   40   X   O
SG504      CH4      X   X   39   X   O
SG504      CH1_CH2   X   X   38   X   O
SG504      CH1_CH3   X   X   37   X   O
SG504      CH1_CH4   X   X   36   X   O
SG504      CH2_CH1   X   X   35   X   O
SG504      CH2_CH3   X   X   34   X   O
SG504      CH2_CH4   X   X   33   X   O
SG504      CH3_CH1   X   X   32   X   O
SG504      CH3_CH2   X   X   31   X   O
SG504      CH3_CH4   X   X   30   X   O
SG504      CH4_CH1   X   X   29   X   O
SG504      CH4_CH2   X   X   28   X   O
SG504      CH4_CH3   X   X   27   X   O
SG5030      CH1      X   X   26   X   O
SG5030      CH2      X   X   25   X   O
SG5030      CH3      X   X   24   X   O
SG5030      CH4      X   X   23   X   O
SG5030      CH1_CH2   X   X   22   X   O
SG5030      CH1_CH3   X   X   21   X   O
SG5030      CH1_CH4   X   X   20   X   O
SG5030      CH2_CH1   X   X   19   X   O
SG5030      CH2_CH3   X   X   18   X   O
SG5030      CH2_CH4   X   X   17   X   O
SG5030      CH3_CH1   X   X   16   X   O
SG5030      CH3_CH2   X   X   15   X   O
SG5030      CH3_CH4   X   X   14   X   O
SG5030      CH4_CH1   X   X   13   X   O
SG5030      CH4_CH2   X   X   12   X   O
SG5030      CH4_CH3   X   X   11   X   O
DP8200      CH1      X   X   10   X   O
DP8200      CH2      X   X   9   X   O
DP8200      CH3      X   X   8   X   O
DP8200      CH4      X   X   7   X   O
DP8200      CH1_WDM   X   X   6   X   O
DP8200      CH2_WDM   X   X   5   X   O
DP8200      CH3_WDM   X   X   4   X   O
DP8200      CH4_WDM   X   X   3   X   O
PROBE_COMP CH1      X   X   2   X   O
PROBE_COMP DMM      X   X   1   X   O
################################################################
# Section 4: auto switching commands
# NONE for fully manual systems
# <ref> <unit>:<C | O><relay list><_><unit>:<....>


----------------------------------------------------------------------------------------------------------------------------

G_config:  -->>> only used for HF_CAL


----------------------------------------------------------------------------------------------------------------------------

GVER   "$Revision: 1.1 $"
CEDAT (
   ISYSTEMNO   "1"
   INAME      "Dut1"
   IDDRIVER   "Dut1"
   IUNIT      "1"
   IIDNO      "n/a"
   ICALDATE   "n/a"
   IDUEDATE   "n/a"
   IADDRESS   "1"
)
CEDAT (
   ISYSTEMNO   "1"
        INAME           "Sg1"
        IDDRIVER        "fl6060a"
   IUNIT      "1"
   IIDNO      "n/a"
   ICALDATE   "n/a"
   IDUEDATE   "n/a"
        IADDRESS        "2"
)
CEDAT (
   ISYSTEMNO   "1"
        INAME           "Sg2"
        IDDRIVER        "fl6060a"
   IUNIT      "2"
   IIDNO      "n/a"
   ICALDATE   "n/a"
   IDUEDATE   "n/a"
        IADDRESS        "2"
)
CEDAT (
   ISYSTEMNO   "1"
        INAME           "Ps1"
   IDDRIVER   "dp8200"
   IUNIT      "1"
   IIDNO      "n/a"
   ICALDATE   "n/a"
   IDUEDATE   "n/a"
        IADDRESS        "2"
)
CEDAT (
   ISYSTEMNO   "1"
        INAME           "Dm1"
   IDDRIVER   "dm5110"
   IUNIT      "1"
   IIDNO      "n/a"
   ICALDATE   "n/a"
   IDUEDATE   "n/a"
        IADDRESS        "2"
)
CEDAT (
   ISYSTEMNO   "1"
   INAME      "*Oa1"
   IDDRIVER   "oa5022"
   IMODELOPTION   "Tektronix OA5022"
   IUNIT      "1"
   IIDNO      "n/a"
   ICALDATE   "n/a"
   IDUEDATE   "n/a"
   IADDRESS   "21"
)
CEDAT (
   ISYSTEMNO   "1"
   INAME      "*Oa2"
   IDDRIVER   "oa5022"
   IMODELOPTION   "Tektronix OA5022"
   IUNIT      "2"
   IIDNO      "n/a"
   ICALDATE   "n/a"
   IDUEDATE   "n/a"
   IADDRESS   "22"
)
CEDAT (
   ISYSTEMNO   "1"
   INAME      "*Oi1"
   IDDRIVER   "oig501"
   IMODELOPTION   "Tektronix OIG501"
   IUNIT      "1"
   IIDNO      "n/a"
   ICALDATE   "n/a"
   IDUEDATE   "n/a"
   IADDRESS   "n/a"
)
CEDAT (
   ISYSTEMNO   "1"
   INAME      "*Oi2"
   IDDRIVER   "oig502"
   IMODELOPTION   "Tektronix OIG502"
   IUNIT      "2"
   IIDNO      "n/a"
   ICALDATE   "n/a"
   IDUEDATE   "n/a"
   IADDRESS   "n/a"
)

 

[rf+tech]

charlyd,

The TDS FAS expects *TWO* gpib cards, for fully automated calibration.

https://www.eevblog.com/forum/testgear/automating-tektronix-field-adjustment-software-for-tds-oscilloscopes/

The scope is expected to be connected to one PCIIA at address 02e1, without other devices.

All other test equipment, including the router, is expected to be connected to a second PCIIA card at address 22e1.

Reference https://forum.tek.com/viewtopic.php?f=568&t=138106&p=279082&hilit=tds+calibration#p283920

As for the domain error, how far into the HF_CAL procedure does the script go? Or does this message appear immediately upon entry to the procedure?

File TDS754D.CON can be opened in a text editor. HF_CAL is the fifth test, defined on line 19. HF_CAL procedure starts at line 384. SIGNAL NUMBER->8 may point to STEP 85, line number 560.

Code: [Select]

556 STEP = 85 (
557 NAME " 200mV 500MHz   Adj"
558 TEXT = VALID_CH( "ALL")
559 TEXT = STEP_INFO("1" "3" "1")
560 TEXT = PTABLE("200e-3" "505e6" "8" "-1.9" "0")
561 TEXT = DIPFREQTABLE("0" "0" "0" "0" "0")
562 SPEC = ADJ(UNIT "" ABS 500, 4095)
563 )

RF+ Tech

/edited to add card address reference/

[charlyd]

hello understand from many people that it is possible to do the calivration just with one card.  ( in manual mode.)
and i even understand that they finished it with one card.

ok for automated setup i need two cards but is there a way to work arround this error having 1 card installed in manual mode.

is it that the router is excepted on card to that i have to change the router file to point it to the other cards?

are there people here that can help me by responding here..... doing the calibration of a TDS754D with 1 card ?

[rf+tech]

charlyd,

Yes, it is possible to complete a manual calibration with one GPIB card. One must switch the voltage standard or signal generators to each channel by hand. A router is of no use in a manual calibration.

The simple answer to the domain error is that you have edited a file and inserted invalid information.

Ignoring questions asked by those attempting to assist you is a bit discourteous. 

I specifically pasted a portion of the TDS754D.CON with the expectation that you would compare this with the file on your computer.

Please confirm this portion of your TDS754D.CON matches exactly, so that I know this has not been modified and eliminate this possibility from suspicion.   

Looking closer at your G-config, I see you have Sg1, Sg2, Ps1 and Dm1 all assigned IADDRESS 2.   

Hint: IADDRESS is the device GPIB address. Change these back to n/a.

It is very likely that your attempt to change files to perform an automated calibration with only one GPIB card, is the source of problems. Undo all of those changes.

RF+ Tech

[charlyd]

hello rf+tech, first of all i think i missed something or miss understood you because you tell me:  Ignoring questions asked by those attempting to assist you is a bit discourteous.

this is serious NOT my intenstion, but ok what did i miss i compared the TDS754.con file with mine but doesn t see any difference if you mean that.

the files i editted are the G_Config file and the adj700d.bat file ( as far as i can see ). 

But maybe it is a much easier idea if you are willing to send me ( with http://www.wetransfer.com) the set of your files which definitely should work and which i could copy in place, that would be the easiest way  or else a set of files after you editted my equiptment in.

please send me a PM for my email adress.

of course all is depending on my equiptment: (and that is)

1 National Instruments GPIB-PCIIA GPIB Interface Card for ISA Bus (181065)

1 Data Precision 8200
1 Fluke 6062A
1 Fluke 8842A  ( but also have a 34401 & keithley 2010 if one of those is compatible with the calibration config)


i think by starting with autoexec.bat/config.sys/ADJ700d.bat   ( the whole software is all memory management sensitive )
other file could be  G_config R_config , TDS754D.con.

my way of handling is :  boot with a floppy into the c: and run in the TDS754D.ADJ folder the adj700d.bat

my bootfiles on the floppy is win98se.

if it is then still not working we made the problem much smaller...

thanks in advance and i really appreciate it.!
 

[rf+tech]

charlyd,

Thank you for your detailed reply. Sometimes overlooked details can cause much wasted time. Now I have a clearer understanding about your problem.

Since your setup has only one GPIB card, and FAS must run manually, the state of your config files are now inconsistent with what is required for manual adjustment. The FAS “knows” that SG503 and SG504 are manual devices and will prompt for the user to make settings as needed. Changing G_CONFIG entries to GPIB controllable equipment tells FAS to run automated. FAS tries to command these devices over a non-existing bus and gets no replies. This is the most likely cause of the domain error.

Next problem I see: Windows 98 runs on DOS 7. A DOS boot floppy made from Windows 98 is DOS 7. FAS must run on a version of DOS no higher than DOS 6.22. Attempting to run FAS with a DOS 7 boot floppy made from Windows 98 cannot be expected to work correctly.

Third, you have not listed a signal router in your equipment. R_CONFIG does nothing unless entries are added below section 4, where it states “NONE for fully manual systems.” You cannot edit G_CONFIG with GPIB controlled equipment and leave out router entries from R_CONFIG section 4.

From my understanding of the supplied details, all of your problems are a result of failing to follow the FAS requirements to the letter. Attempting to hack the FAS configuration to run automatic with only one GPIB card, no signal router, and on the wrong version of DOS, should not be expected to work correctly.

My setup is an old ISA box with a full installation of DOS 6.22 (installed from a three floppy set) on the internal hard drive. No Windows. FAS installed on and runs from the internal hard drive. One NI PCIIA card, same as yours. Stock FAS installation, no modifications to any files. FAS runs manually, without any problems.

Since I do not have all of the equipment required to run automated FAS, I have not attempted to run FAS any other way than manually. And this was for TDS600A.ADJ. I have not run TDS700D.ADJ.

I’ll say this once more, just to be clear: your problems appear to be self-created by not following all of the FAS requirements. It is possible to perform a calibration of your TDS754D manually with one GPIB card - however - G_CONFIG and R_CONFIG must not be modified. Even though you are not using SG503, SG504, DM8200, etc. and are using other equipment, do not change any G_CONFIG entries, if you really expect to run FAS manually.

Unfortunately, all of the requirements cannot be found in one place. These are found by carefully reading every thread on Tek forum about FAS calibration and carefully reading various FAS files.

* Reinstall a clean copy of TDS700D FAS
* Read the files README.TXT and RELEASE.NTS for more information
* With TMODE=M, it is no longer possible to skip tests or select channels
* If you want to skip tests or select channels, change TMODE=MC in ADJ700D.BAT
* Do not edit anything in G_CONFIG or R_CONFIG
* The FAS as installed is configured to run manually

If you want to run automated FAS, satisfy all of the requirements, not just a few of them. There are no shortcuts.

RF+ Tech

[charlyd]

HI RF+ tech,
i am going to reply in parts ok.
------------------------------------------------------
Since your setup has only one GPIB card, and FAS must run manually, the state of your config files are now inconsistent with what is required for manual adjustment. The FAS “knows” that SG503 and SG504 are manual devices and will prompt for the user to make settings as needed. Changing G_CONFIG entries to GPIB controllable equipment tells FAS to run automated. FAS tries to command these devices over a non-existing bus and gets no replies. This is the most likely cause of the domain error.
-----
a good friend of mine told me he does many cals with FAS in manual mode with changing the G_config to a different one halfway and he succesfully finishes this cals.  but he could n t help me with my error.   one difference between our test is he has a fl6061A and i have a fl6062A.
--------------------------------------------------------
--------------------------------------------------------
Next problem I see: Windows 98 runs on DOS 7. A DOS boot floppy made from Windows 98 is DOS 7. FAS must run on a version of DOS no higher than DOS 6.22. Attempting to run FAS with a DOS 7 boot floppy made from Windows 98 cannot be expected to work correctly
-----
This is possible i will try older boot next week
--------------------------------------------------------
--------------------------------------------------------
Third, you have not listed a signal router in your equipment. R_CONFIG does nothing unless entries are added below section 4, where it states “NONE for fully manual systems.” You cannot edit G_CONFIG with GPIB controlled equipment and leave out router entries from R_CONFIG section 4.
-----
knowing my equiptment what should i put there.??   can you attach a correct one for me here
--------------------------------------------------------
--------------------------------------------------------
I’ll say this once more, just to be clear: your problems appear to be self-created by not following all of the FAS requirements. It is possible to perform a calibration of your TDS754D manually with one GPIB card - however - G_CONFIG and R_CONFIG must not be modified. Even though you are not using SG503, SG504, DM8200, etc. and are using other equipment, do not change any G_CONFIG entries, if you really expect to run FAS manually.
My setup is an old ISA box with a full installation of DOS 6.22 (installed from a three floppy set) on the internal hard drive. No Windows. FAS installed on and runs from the internal hard drive. One NI PCIIA card, same as yours. Stock FAS installation, no modifications to any files. FAS runs manually, without any problems.
-------
Can you send me your most important files i mean the setup is not that complicated, so it is easy to change some inplace files with others.
i did the installation many times already.
what as a last thing could be is that i change the G_config from FL6060a to FL6062A which i found in the exe files with a hexeditor.

i will thry things and come back with the result and hope you send me your config to test.

thanks in advance

[rf+tech]

charlyd,

We seem to be having a communication problem, so I shall make this reply simple.

Your attempts to edit files is the cause of your failures. Why make this more difficult?

If you want to have success, follow these simple instructions:

Install fresh copy of FAS
Do NOT edit G_CONFIG
Do NOT edit R_CONFIG
Do NOT edit ADJ700.BAT
Do NOT hexedit the exe
Run FAS on DOS6.22

The FAS will run manually. Whenever the FAS says SG503 or SG504, set your FL6062A as requested.

There is no need for anyone to send you their files.

Why?

Installing a fresh copy of the FAS gives you the required files. Do NOT edit anything.

One more thing. Please learn to use the forum quote function. This makes your replies much easier for everyone to read.

RF+ Tech

[charlyd]

Hi rf+tech,
Thanks for you reply. I will try and let you know….but i think it is not that simple.

[rf+tech]

charlyd,

Hi rf+tech,
Thanks for you reply. I will try and let you know….but i think it is not that simple.

Obviously, still have not read, or do not believe the instructions. 

Please read the instructions attached below (RELEASE.TXT) and pay attention to the title TDS700D/TDS500D/TDS714L MANUAL CALIBRATION NOTES.

If the TDS754S does not have option 3C or 4C, the section Option 3C & 4C Instruments does not apply.

Nothing to edit. 

Simple. 

Also attached is the installation README.TXT file.

RF+ Tech

[charlyd]

hi R+f  which equiptment do i connect to the gpib and on what moment do i need them Connected or not...
today i tested with no change in the files....but got an error ...DUT I/O error....can t read string from DUT1

[rf+tech]

DUT1 is the TDS754D being calibrated and must be the only device connected to GPIB, so the FAS can set the scope for each calibration step.

For manual calibration, other equipment must not be connected to GPIB.

For the HFcal, the FAS will request what frequency to set on the SG503 or SG504. Set your Fluke 6062 accordingly. Output level typically gets set for six divisions on the scope display. When the FAS says to use an attenuator (10x or 20 dB), just set the 6062 output 20 dB lower. What really matters is to ensure six divisions of signal level on the scope, when requested.

I'll challenge you to beat my time of 3 hours to perform a complete calibration on my four-channel TDS640.   

Good luck,

RF+ Tech

[charlyd]

Hi RF+tech,
ok i will do so… what do you mean exactly with this:   What really matters is to ensure six divisions of signal level on the scope, when requested.

i never came that far so maybe it will explain itself but...but when i see it took you 3 hours ijust ask before i have to end getting stuck at 2:30 hours 
 

[rf+tech]

charlyd,

what do you mean exactly with this:   What really matters is to ensure six divisions of signal level on the scope, when requested.

I have suspected that English may be the cause of your difficulty and this question confirms my suspicion. The statement means exactly what is written. "What really matters", means "this is important."

The TDS640A FAS starts the HF_CAL sequence by setting the scope channel 1 to 2 mV/division and enables 50Ω termination.

A message is displayed on your computer monitor "Set the SG503 to 251 MHz, connect the signal to channel 1 and adjust the output for six divisions of vertical deflection." If the RF level measured by the FAS is not as expected, the FAS will give another opportunity to set the level correctly.

The FAS will set the scope for successively higher vertical deflection ranges, request another frequency and ask that the level again be set for six divisions of vertical deflection.

The FAS requires six divisions of signal at each frequency, except at the last step for each channel. I think this step is four divisions.

When channel 1 is finished, channel 2 goes through the same process, then channel 3 and channel 4.

To save some time, keep a written record of the 6062 RF level and frequency at each calibration step for channel 1. When channels 2, 3, and 4 are calibrated, enter the recorded values into the 6062. By the time channel 2 is finished, you can anticipate what to do next before the FAS displays the next request.

The HF_CAL process is really simple, just very repetitious and tiring. Once the HF_CAL is finished, there will be additional calibration processes to perform: TRIG_POS_CAL, GLITCH_TRIG_CAL, PNP_LATENCY_CAL and PROBE_COMP_CAL. For each step, the FAS will request the actions to be performed.

Of course, SPC and CVR_CAL are performed at the start, before HF_CAL.

RF+ Tech

[charlyd]

ok what did i do:
i disconnected all the equiptment from the GPIB, except the DUT1.
and then i started. i choose the partitial option on the menu .. or should i better take select tests 1by1 ?  ....full cal. isn t an option i assume.

1.  COLD_START                         (Initialization)
SUCCESFULL..!
2.  SPC                                       Signal Path Compensation
SUCCESFULL..!
3.  CVR_CAL                              Voltage Reference
SUCCESFULL..!
4.  POWER_CYCLE                     (Reset)
SUCCESFULL..!

and then after the DUT rebooted i went back in to go to HF_Cal....when starting... (i didnt change anything)....
i need: Tektronix 011-0059-02 10x, 50 Ohm, 2 W, Attenuator ?

i got : test error -> readDutAcq :Expected event 402, Received -1

[charlyd]

this brought me back to the previous config with the domain error.

after some investigation i found out that when i power off my Fl6062 and then turn it on and do every channel one by one..
so start with CH1 and then power off the fl6062..after 5min. power back on and continue to CH2.....power off.....wait ...power on and CH3.
in CH 4 of went wrong...

first it when wrong on CH2 later not.
so it depends on something but what.

let say it crashes sometimes on CH1 sometimes not and then later on CH2 or CH3...but other times it passes those channels ok.   

so domain error.  -> signal number 8  what is that exactly

[rf+tech]

i got : test error -> readDutAcq :Expected event 402, Received -1

This means the acquisition board in the TDS754D may have a defect - or - the RF output from your FL6062 is failing and the acquisition board cannot see the expected signal. Which of these conditions is true?

If the FL6062 output is unreliable, fix this first. It must work reliably or else you will continue 

let say it crashes sometimes on CH1 sometimes not and then later on CH2 or CH3...but other times it passes those channels ok.

No, the FAS is not crashing. The FAS is reading garbage data from the scope. This points to the acquisition board, or perhaps the processor board. One of the two is corrupting data intermittently.

so domain error.  -> signal number 8  what is that exactly

No one knows what this means. The best guess is the acquisition board still has an intermittent defect. Is this TDS754D the same scope you posted about on Tektronix forum two years ago?

My TDS5640 required very intensive repair. Multiple open data bus lines were discovered under four surface mount ICs on the processor board, all caused by electrolyte leakage. Additional electrolyte damage was repaired on the acquisition board and front panel board. All calibration steps passed but there is still one startup self-test failure to be resolved. Someday.

RF+ Tech

[charlyd]

hi yes is the TDS754D which i repaired long time ago.
i also have a working TDS784D with same boards Inside the latest FW. version. they have the same firmware 7.4e after i update the 784D to 7.4e.
the only error i have still got is this one...
see attachment
they told me this is a matter of calibration.

and i still have:  voltage initialize, Frequency initialize, probe initialize  after a NVram ram chips had corruption part.  ( later it is swapped and putted on a socket. )
and the two 24c02 chips are swapped and filled with info from others. because of error 163 see other posts.

[rf+tech]

charlyd,

Yes, it is correct that "nvLibrariansDiag, Libs with crcc failures" in the error log implies calibration is necessary. When calibration is completed successfully, a checksum is calculated from the new calibration constants and written into nvRAM. When nvRAM contents are corrupt, or values reset to defaults, the checksum test fails and the above message is logged.

About the domain error signal 8. The domain consists of the entire GPIB network: computer with GPIB control card, cables and all connected equipment. Since the FAS does not rely on the NI driver, this "signal 8" must originate from the FAS executable. The FAS is encountering an unexpected condition.

Thinking out loud about "Expected event 402, Received -1": the FAS expected to read a value, a string of bits within an expected range of values, and instead read nothing, all zeros. If this interpretation is correct, then the TDS754D still has a defect waiting to be located and repaired.

RF+ Tech

[charlyd]

Hi Rf+Tech, yes what you say: then the TDS754D still has a defect waiting to be located and repaired. could be a thing after this long period of trying to cal. the scope and bumping into errors over and over.

btw i asked many people who have the TDS7xxD family about there calibration skills but lots of them did not yet do it or did not finish or even not start the calibration and sold the unit again as is. 

but ok i don t give up that easy and meanwhoile i fixed a agilent 54845A and was working on some LA boards. so from time to time the TDS754D triggers me again.
Last week a cheap GPIB card came on my way to make things easyier maybe.  i can also swap parts from my TDS784D to check on errors in the TDS754D but i don t want to destroy that calibration also.

let first start to post a new console debug-log today here. From the booting TDS745D. If there are still errors in the unit they should be visible in that log, i would say.

this is how it was....
https://www.eevblog.com/forum/testgear/tektronix-tds754d-fail-processor/msg895300/#msg895300
and doing the test after a long time... i get this dac errors...

I think it is time to investigate my dacs. Is there a simpel way to test them one by one.

but still after rebooting the scope there is NO error except:  ERRORID: 163 diagnostic test failure nvLibrariansDiag
Libs with crcc failures:
        ExtConst

calLibrarianDefaultCk .......... ***FAIL***
..error details:
ERRORID: 163 diagnostic test failure calLibrarianDefaultCk
Libs set to factory defaults:
         IntConst

can this error be a result of a crashed calibration... it crashed during interleave ....and when i stopped the cal.  the scope wouldn t boot anymore to the end.( yesyes even with switch to the rear->in protect) to the start screen the LCD stayed black after the DPO logo nothing.....
at that point i opened the unit and dipped some switches to get it back to live again i remembered from long ago.
Then after powering up the scope worked again.

or is this a new problem?

and after some checking i walking into a other error
Teksecure Failed: nvWfm memory failed to clear

[charlyd]

after the last tries i got a corrupted NVram i think so i started all over again.

i saved the software from my 784D ( same boards 2M versions, same firmware 7.4e) to get a starting point.
i ran the tektool and save the files from the 784D

Tektool_0 -r c:\tektool\nvr400_2.bin -b 0x04000000 -l 0x20000
Tektool_0 -r c:\tektool\nvr408_8.bin -b 0x04080000 -l 0x80000

and with the switch toggled towards the from ( scope looks dead, but listens on adr. 29 ) this is hard coded.
i then :
Tektool_0 -w c:\tektool\nvr400_2.bin -b 0x04000000 -l 0x20000
Tektool_0 -w c:\tektool\nvr408_8.bin -b 0x04080000 -l 0x80000

btw for the firmware upgrade better use tekfwool that is much faster.
and for the U1052 and U1055 export use the so called get-tool. you can run it when scope is in normal mode.
just run and it will export both 24C02 chips to a .bin file.

back to the project, i flashed the above bin files to the TDS754D.
afterwards, i read them again and see if i got out the same as what i flashed in.... a dos FC /B [org]nvr408_8.bin [exp]nvr408_8.bin i got difference.
with lets says empty 24C02 chips.

Then it was time to power on with switch back towards the rear i looked in the errorlog to see what was in there.
this even looked very good.!

so i went for the cal and was advised to first do the voltage ref. to get  so do:
1.  COLD_START                         (Initialization)
2.  SPC                                       Signal Path Compensation
3.  CVR_CAL                                Voltage Reference
4.  POWER_CYCLE                       (Reset)
8.  PROBE_COMP_CAL                  Voltage Reference

i got my Voltage Ref PASS

next step the HF_cal
while doing the HF_cal with the 6062A i walked into the Domain error again.  see picture in Post #1
[this happens after some minutes when the cal is running...]

and i am stuck in that one again....

[rf+tech]

Error messages start at offset 0x0006E2B0 in TDS700CG.exe

"DOMAIN error" is found at offset 0x006E461.

RF+ Tech

[charlyd]

ok and this means?

[rf+tech]

This is a pointer, if you wish to disassemble the exe and discover where this error is being referenced and possibly provide a clue of the cause.

Other steps to be taken would be to replace GPIB card with another, replace the GPIB cable with another, run the same FAS from another computer, or attempt to calibrate another TDS7xxD scope with the existing equipment. All troubleshooting 101 basics – isolate the error down to one item or condition.

Since CVR and SPC pass, some hardware may be failing after an equivalent period of time has elapsed. If CVR and SPC require an hour to complete manually, leave everything sitting powered on for one hour, then begin CVR and SPC. Or try running HF_cal first.

Isolating the condition that causes the failure, is a prerequisite.

RF+ Tech

[charlyd]

as from my tests and thoughts the "domain error" is pointing to the fact that the equiptment is not in range to do the calibration ok. so the 6062A is out of calibration range at a certain moment or not stable enough..i hope i made myself clear