It is. I just confirmed on the physical box itself.
-ls-




"Albert" <aodiversen@...> wrote:

just outta curiosity, how good are those scopes?

how does the 549 compare to the 564 storage scope? I see from tekwiki that it has a greater BW. and is the 543 similar to the the 545 or 547?

-Robby

No, it doesn't look right. I have the same scope (also NOS, maybe
from the same MOD source ?) and mine looks like the first image.

IIRC, the character generator has 2 sets of adjustments, some on
the board itself (position, hight , width etc) and more adjustments
on the V-output amp where the vector is summed (and possibly on
H-output as well). I bet the lead routes make a difference too . I
also have a 7603 with a similar looking defect (it resisted my
attempts to adjust it / fix it - but it's a spare so I didn't look too hard)

You will need the serial numbers as there are serveral different versions ...

dc

17/07/2012 21:54

Thanks David, mine came from a charming lady re seller in Somerset,
one of a pair she was selling. I'm going to get David Partridge to
cast his expert eye over it shortly, it's a shame not to set it to
rights, being such an otherwise mint example. It's perfectly usable as
is, but things like that frankly bug the hell out of me ;)

--
Best Regards,
Chris Wilson.

On 17/07/2012 19:56, ROLYNN PRECHTL K7DFW wrote:

Note: There is no difference among the sockets 499-P44-10 (REV.B), 499-P44-20 (REV.A) and
499-P44-00, it is the same socket which marked "499-044-00".

Thanks, missed that.

Gordon

Hi John,
At Kurt's Tekwiki you will find a 10 MB text-searchable pdf:

You can even search for U722 in the pictures!
Albert

What made you choose REV-B? REV-A is the most recent (2/10/06) according to the drawings. REV-B has
4/11/01 as the drawn date.

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


From the web site.

Note: There is no difference among the sockets 499-P44-10 (REV.B), 499-P44-20 (REV.A) and
499-P44-00, it is the same socket which marked "499-044-00".

Hi John,
I'm not at home where I have a paper manual, but I could download the BAMA manual here. It looks like we are talking about different things. At page 102, figure 8-11, all 3 ICs are shown, U722, U842 and U416. The A1 board layout is shown 3 times in the pdf and all 3 occurences show those 3 ICs. I didn't check traces, so I don't know whether the FP control is really connected to the IC which is labeled U722 at the board.
Albert

I made my own out of copper tape and a proto-board. The commercial socket does look just a tad more professional.

Thank you.

Mine are all above S/N B069999, so I guess I don't get to play !!

73, Dick, W1KSZ

I have no affiliation with the seller.

-Kurt

The tunnel diode based 7B92A is serial number B069999 and below.

Physically if you look inside at the two trigger circuit boards, the
ones with tunnel diodes have 3 DIP packages in a row while the newer
ones without tunnel diodes have a DIP package next to an X shaped IC
or hybrid mount.

On Tue, 17 Jul 2012 09:09:01 -0700, Richard Solomon
<dickw1ksz@...> wrote:

I have a few 7B92's here. How do I tell which ones have TD's in them. Is
there
a particular place on the board to look for them ?

Tnx, Dick, W1KSZ

On Mon, Jul 16, 2012 at 2:15 PM, Albert <aodiversen@...> wrote:

**

Hi Raymond,

Tried a tunnel diode based 7B92 in a 7904A/7A29, with input from a TG501
and internal triggering. At 2 ns and 1 ns the TG501 "pulse" stream is
nearly a sine wave. At 2 ns (500 MHz) the 7B92 triggers well in Norm mode
with signal less than 0.5 div. At 1 ns (1 GHz) it fails in Norm mode but
syncs in HF Sync mode (and signal far below 0.5 div). But a 7B15 performed
far better with a much sharper trace, so with much less jitter. Even at 1
GHz the 7B15 would trigger in Norm mode.
Checking TB performance this way in a 7904(A) is somewhat undefined since
it's not clear what trigger amplitude arrives at the TB. Testing in a 7104
would give better information.
The 7B92 was "as is", so other units might perform better.

Albert

Tried my newly acquired SG504 (with leveling head) and saw this 7B92A

triggering happily at around 1.05 GHz on my 7904 + 7A19... Of course,
amplitude isn't shown anywhere near correctly. 7B92A is specified to
trigger "above 500MHz".

Raymond

--- In TekScopes@..., "Dennis Tillman" <dennis@...> wrote:

For those of you that want to make one yourself the test and burn-in socket
came from WaveShare in China (sales@...). Their part number is
499-P44-10 (REV.B). The price is $27 plus $14 to mail it via USPS. I have no
affiliation with the manufacturer etc. Better pictures of the socket than I
can take can be seen at

Hi Dennis. What made you choose REV-B? REV-A is the most recent (2/10/06) according to the drawings. REV-B has 4/11/01 as the drawn date.

Cheers

Gordon

开云体育

...and I was tempted by the 7704 stuff...until I found out about the 549? ;)

Bernd

?

In a message dated 7/17/2012 12:40:05 A.M. Pacific Daylight Time, d.seiter@... writes:

I have a few 7B92's here. How do I tell which ones have TD's in them. Is there
a particular place on the board to look for them ?

Tnx, Dick, W1KSZ

开云体育

Hello,

Here's how to do it:

- Compile the code below (you know what to change in the code for various memories)

- Get your NI GPIB adapter and attach it to the scope
- Put NVRAM protection switch (S1002) to forward position
- Turn the scope on

- Run the PC program


Hopefully the result of this is loads and loads of firmware and NVRAM backups uploaded somewhere safe like ko4bb-site.

Have fun.

...

#include <windows.h>
#include <stdio.h>
#include <stdlib.h>
#include "ni488.h"

void GpibError(const char * msg); /* Error function declaration */

int Device = 0; /* Device unit descriptor */
int BoardIndex = 0; /* Interface Index (GPIB0=0,GPIB1=1,etc.) */

int main(int argc, char *argv[])
{
FILE *outfile;

int f;

unsigned long addr, straddr, endaddr, data;
unsigned short lenght;
unsigned char checksum;
unsigned char str[0x100];

int PrimaryAddress = 29; /* Primary address of the device */
int SecondaryAddress = 0x7E; /* Secondary address of the device */
unsigned char Buffer1[0x500]; /* Read buffer */


Device = ibdev( /* Create a unit descriptor handle */
BoardIndex, /* Board Index (GPIB0 = 0, GPIB1 = 1, ...) */
PrimaryAddress, /* Device primary address */
SecondaryAddress, /* Device secondary address */
T3s, /* Timeout setting (T10s = 10 seconds) */
1, /* Assert EOI line at end of write */
0); /* EOS termination mode */

if (ibsta & ERR) { /* Check for GPIB Error */
GpibError("ibdev Error");
}

ibclr(Device); /* Clear the device */
if (ibsta & ERR) {
GpibError("ibclr Error");
}

/* Attempt to read TDS544A flash ROM contents */

outfile = fopen("KRNLdump.bin","wb");
printf("&#92;n");

// straddr = 0x01000000L; /* Start of flash ROM */
// endaddr = 0x01FFFFFFL; /* End of flash ROM */

// straddr = 0x04000000L; /* Start of TDS544A NVRAM */
// endaddr = 0x0407FFFFL; /* End of TDS544A NVRAM */

straddr = 0x00000000L; /* Start of Kernel ROM */
endaddr = 0x0003FFFFL; /* End of Kernel ROM */

addr = straddr;

do {
/* Read memory message */

str[0] = 'm'; /* m - read memory command */
str[1] = 0x00; /* checksum - fill later */
str[2] = 0x00; /* message lenght MSB */
str[3] = 0x08; /* message lenght LSB */

str[4] = (unsigned char)(addr >> 24 & 0xFF);
str[5] = (unsigned char)(addr >> 16 & 0xFF);
str[6] = (unsigned char)(addr >> 8 & 0xFF);
str[7] = (unsigned char)(addr & 0xFF);

str[8] = 0x00; /* data lenght - try 16 bytes first */
str[9] = 0x00;
str[10] = 0x04;
str[11] = 0x00;

checksum = str[0] + str[2] + str[3];
for(f = 4; f < 12; f++) checksum += str[f];
str[1] = (unsigned char) checksum;

//printf("&#92;nSending:&#92;n");
//for(f = 0; f < 12; f++) printf("%02X ", str[f]);
ibwrt(Device, str, 12); /* Send */
if (ibsta & ERR) GpibError("ibwrt Error");

/* Read Acknowledge (plus-sign msg) */
ibrd(Device, Buffer1, 1); /* Read up to x bytes from the device */
if (ibsta & ERR) GpibError("ibrd Error");
//printf("&#92;nAck reveiced:&#92;n");
//for(f = 0; f < 1; f++) printf("%02X ", Buffer1[f]);

/* Read reply message */
ibrd(Device, Buffer1, 0x404); /* Read up to x bytes from the device */
if (ibsta & ERR) GpibError("ibrd Error");
//printf("&#92;nReceived:&#92;n");
//for(f = 0; f < 0x404; f++) printf("%02X ", Buffer1[f]);

/* Save buffer contents */
for(f = 4; f < 0x404; f++)
{
fputc(Buffer1[f], outfile);
}

/* Send Acknowledgement (plus-sign msg) */
str[0] = '+';
ibwrt(Device, str, 1); /* Send */
if (ibsta & ERR) GpibError("ibwrt Error");

addr += 0x400;

} while(addr <= endaddr);

fclose(outfile);

ibonl(Device, 0); /* Take the device offline */
if (ibsta & ERR) GpibError("ibonl Error");

system("PAUSE");
}


void GpibError(const char *msg) {

printf("%s&#92;n", msg);

printf("ibsta = 0x%x <", ibsta);
if (ibsta & ERR ) printf(" ERR");
if (ibsta & TIMO) printf(" TIMO");
if (ibsta & END ) printf(" END");
if (ibsta & SRQI) printf(" SRQI");
if (ibsta & RQS ) printf(" RQS");
if (ibsta & CMPL) printf(" CMPL");
if (ibsta & LOK ) printf(" LOK");
if (ibsta & REM ) printf(" REM");
if (ibsta & CIC ) printf(" CIC");
if (ibsta & ATN ) printf(" ATN");
if (ibsta & TACS) printf(" TACS");
if (ibsta & LACS) printf(" LACS");
if (ibsta & DTAS) printf(" DTAS");
if (ibsta & DCAS) printf(" DCAS");
printf (" >&#92;n");

printf ("Iberr() = %d", iberr);
if (iberr == EDVR) printf(" EDVR <Driver error>&#92;n");
if (iberr == ECIC) printf(" ECIC <Not Controller-In-Charge>&#92;n");
if (iberr == ENOL) printf(" ENOL <No Listener>&#92;n");
if (iberr == EADR) printf(" EADR <Address error>&#92;n");
if (iberr == EARG) printf(" EARG <Invalid argument>&#92;n");
if (iberr == ESAC) printf(" ESAC <Not System Controller>&#92;n");
if (iberr == EABO) printf(" EABO <Operation aborted>&#92;n");
if (iberr == ENEB) printf(" ENEB <No GPIB board>&#92;n");
if (iberr == EOIP) printf(" EOIP <Async I/O in progress>&#92;n");
if (iberr == ECAP) printf(" ECAP <No capability>&#92;n");
if (iberr == EFSO) printf(" EFSO <File system error>&#92;n");
if (iberr == EBUS) printf(" EBUS <Command error>&#92;n");
if (iberr == ESTB) printf(" ESTB <Status byte lost>&#92;n");
if (iberr == ESRQ) printf(" ESRQ <SRQ stuck on>&#92;n");
if (iberr == ETAB) printf(" ETAB <Table Overflow>&#92;n");
if (iberr == ELCK) printf(" ELCK <Lock error>&#92;n");
if (iberr == EARM) printf(" EARM <Ibnotify rearm error>&#92;n");
if (iberr == EHDL) printf(" EHDL <Invalid Handle>&#92;n");
if (iberr == EWIP) printf(" EWIP <Wait already in progress>&#92;n");
if (iberr == ERST) printf(" ERST <Notification cancelled due to reset>&#92;n");
if (iberr == EPWR) printf(" EPWR <Power error>&#92;n");

printf("Ibcnt() = %u&#92;n", ibcnt);
printf("&#92;n");

/* Call ibonl to take the device and interface offline */
//ibonl(Device, 0);

//system("PAUSE");
//exit(1);
}

On further examination, I think I found the reason.

The negative pulse edge of the high amplitude output develops
considerable bowing above about 65 volts. When it is trimmed for a
maximum output of 5.2 volts into 50 ohms, the maximum output is 64
volts into a high impedance load. The specifications require an
output of 60 volts or greater unterminated and 5 volts or greater into
50 ohms.

On Tue, 17 Jul 2012 03:43:22 -0000, "Patrick Wong" <patwong3@...>
wrote:

Hi David,

Congratulations on restoring proper operation to your unit.

Since a spec is the high amplitude output is adjustable up to > 5V into 50 ohms, I suppose that is the reason that the adjustment procedure has you setting the max output at 5.2V, giving you 4% over-range.

If you are asking what is the utility of the high amplitude output, there are at least a couple of uses in the analog 24xx scope calibration procedure:

1. CAL 06 - Vertical Transient Response, where the high amplitude output powers a tunnel diode pulser. A maximum voltage setting is required from the high amplitude output here.

2. Adjustment of CH1 and CH2 input capacitance, although in this case it looks like only 300 - 600 mV signal is required.

Patrick Wong AK6C

--- In TekScopes@..., David <davidwhess@...> wrote:

...My question concerns the high amplitude output calibration. Why is it
even adjustable via R790? The output level has no important
application that I can see so why bother adjusting it to 5.2 volts
into a 50 ohm load?

No, it doesn't look right. I have the same scope (also NOS, maybe from the same MOD source ?) and mine looks like the first image.

IIRC, the character generator has 2 sets of adjustments, some on the board itself (position, hight , width etc) and more adjustments on the V-output amp where the vector is summed (and possibly on H-output as well). I bet the lead routes make a difference too :-) . I also have a 7603 with a similar looking defect (it resisted my attempts to adjust it / fix it - but it's a spare so I didn't look too hard)

You will need the serial numbers as there are serveral different versions ...

dc

Jerry,

I'm thinking along those lines too. Also, I noticed a bad zener diode, VR1490. Forward voltage curve looks good, but no reverse voltage curve? Wonder if someone previous to me put in a regular diode. Very strange. This thing was hacked on quite a bit before I got it, so it's definitely got it's issues. Not the first component on this guy I've had to replace because it was the wrong part.

Definitely the SC504 from hell... ;-)

Mark