User talk:Qfissler

Regarding your comments -

File names: For manuals, this was the only practical way we found to make sure we don't end up with a load of duplicates and don't know what's missing at the same time.

ROMs: I'm not surprised there are multiple part numbers with the same content, there was quite a bit of design/code sharing within the series. I still think using the part number is the simplest convention, adding all the other metadata you have to the file description would be helpful of course. And inevitably, we'll sometimes have mistakes of some sort that will need to be fixed over time, or we may even find Tek made mistakes ...

Multiple file uploads: I regularly upload in multiple browser tab simultaneously. If you have a really large pack of stuff to upload, or something really large, please let me know and we can do it via scp as you suggest - but it requires running a separate import job into MediaWiki so I'd like to do it "under controlled circumstances".

Thanks for the detective work! --Peter (talk) 04:02, 30 January 2023 (PST)

Hi Quinn, my suggestion for the level-2 headline section to precede the parts lookup subsections would be simply "Components" (see 7603). Thanks for noticing this! --Peter (talk) 13:30, 14 July 2023 (PDT)

Can we discuss Talk:5000 Series plug-in interface please? --Peter (talk) 15:07, 13 August 2023 (PDT)

Hi Qfissler, if you like tables, have a new one on my talk. I'm open to suggestions :-) --Rubasch (talk) 10:36, 22 September 2023 (PDT)

Excellent stuff!

About your 7704 with a fan, maybe it is a mod by some user? Greetings --Rubasch (talk) 11:38, 22 September 2023 (PDT)

It could be - it's an interesting scope - I have it queued for repair but am holding off as I want to take photos and/or videos to show some amazing things about how well it works, despite being water severely damaged :-)

Have a new table for you;-) Fixed the problem with my empty P6015 probe. Think that could be helpful for others. Can you have a look? Please do not hesitate to correct me.

Also on the time table: I want to improve it by adding the purchase costs. But the cost should be corrected to the year 2023. Is it possible to have a table that can calculate? My idea is, that in the colored part of the table the cost for each year is displayed. And at another place you could choose the year to witch the prices are corrected (don't know if I make myself clear...). Greetings --Rubasch (talk) 12:09, 18 October 2023 (PDT)

The easy and short answer is "no". But I think it's possible if you embed JavaScript [1] and there could well be MediaWiki plugins.Qfissler (talk) 00:56, 19 October 2023 (PDT)

Hi Qfissler, I have some new tables! You can see them in my talk page. It's about the TM500 system. The last table is still under construction. But the counters, power supplys and multimeters should be OK. Have You any idea where to put them? Should I create a new page or put it in an existing page? Greetings --Rubasch (talk) 12:11, 1 October 2024 (PDT)

Beautiful! :-) I might try a new method for editing tables - so maybe I'll copy one here to test... Qfissler (talk) 04:22, 5 October 2024 (PDT)

I am happy that some likes it! :-) the table you copied is still under construction and has to be checked! The others should be ok. What would be helpfull for this big table would be foulding the table. But I have not found the right code. Greetings --Rubasch (talk) 07:22, 14 October 2024 (PDT)

Folding? Like Collapsing? Like an outline view? Qfissler (talk) 09:35, 14 October 2024 (PDT)

Yes collapsing is the word. So that some columns can be collapsed. Like The "Wave Forms" or "on sale" collum. I think, this would make the table smaller and more readable. Greetings --Rubasch (talk) 05:41, 16 October 2024 (PDT)

Testing table editor

• Tried WikiMedia plugin for LibreOffice - failed for me
• Tried Google Sheets to edit the table then paste to the visual table generator - reworked header rows below for sorting

		on sale			Frequency		Wave Forms							Pulse period		Pulse duration		Symmetry	Rise/Fall		DC-Offset		Output Voltage		Output	Modulation			Sweep							Output		Gate
Name	Type	from	to	Channels	from [Hz]	to [MHz]	Sine	Square	Triangle	Ramp	Pulse	Arbitrary	Noise	[ns]	[s]	[ns]	[s]	Duty Cycle %	min [ns]	max [ms]	50 𝛀 [V]	Open [V]	50 Ohm	Open	Current	AM	FM	VCF	Trig.	min [ms]	max [s]	Decades	lin	log	Ramp o/p	Trigger	Rear	in
FG501	Function generator	1972	?	1	0.01	1	YES	YES	YES	1/10	1/10	-	-	1000	100	500	50	-	100	-	±5	±7.5	10pp	20pp	?	-		X	-			(3)	(X)	(X)	-	X	-	X
FG501A	Function generator	?	1993	1	0.002	2	YES	YES	YES	1/10	1/10	-	-	500	500	25	25	5-95	25	-	?	?	?	30pp	?	-		X	-			(3)	(X)	(X)	-	X	-	X
FG502	Function generator	1974	1993	1	0.1	11	YES	YES	YES	1/10	1/10	-	-	909	100	45.5	5	5; 50; 95	20	-	±2.5	±5	5pp	10pp	?	-		X	-	-	-	-	-	-	-	X	-	X
FG503	Function generator	1974	1993	1	1 (0.01)	3 (5)	YES	YES	YES	-	-	-	-	-	-	-	-	50	60	-	±3.75	±7.5	10pp	20pp	?	-		X	-	-	-	-	-	-	-	X	-	-
FG504	Function generator	1976	1993	1	0.001	40	YES	YES	YES	1/10	1/10	-	-	250	1000	17.5	930	7-97	6	100	±3.75	±7.5	15pp	30pp	?	X		X	X	0.1	10	4	X	X	X	X	-	X
FG507	Function generator	1980	1989	1	0.002	2	YES	YES	YES	YES	YES	-	-					5-95	25	-	?	±13	±15	±30		-		X	X	0.1	10	3	X	X	X	X	-	X
RG501	Ramp Generator	1972	1982	1	-	-	-	-	-	YES	-	-	-	-	-	-	-	-	10000	10000	-	-		±10		-		-	-	-	-	-	-	-	-	-
AFG5101	Function generator	1988	1991	1	1µ	12	YES	YES	YES			YES	-					YES	15		4.49	8.98	±9.99	±19.98		X	X	X		0.1	999.9	4	X	X	X		GPIB
AFG5102	Function generator	1993	1994	1	0.02	20	YES	YES	YES	YES	YES	YES	-					10-90	12		YES	YES	±15	±30		X		X		YES	YES	YES	X	X			GPIB
AWG5102	Waveform generator	1992	?	1	0.001	1	YES	YES	YES	YES	YES	YES	-					10-90	20		YES	YES	9.99	?		X		X		-	-	-	-	-			GPIB
AWG5105	Waveform generator	1993	1995	1/2	1µ	25	YES	YES	YES	YES	YES	YES	YES					10-90	15		?	±7.5	±15	±30		X											GPIB
FG5010	Function generator	1982	1991	1	2m	20	YES	YES	YES	YES	YES	-	-					10-91	10					±20		X	X	X	-	-	-	-	-	-
PFG5105	Pulse Function generator		?	1	0.012	12	YES	YES	YES	YES	YES	-	-	83	83.3	10	10	<99	15		4.49	8.98	9.99	19.98		X	X	X					x	x			GPIB
PG501	Pulse Generator	1972	1993	Double	5	50	-	-	-	-	YES	-	-	20	0.2	10	0.1	< 70	3.5				5
PG502	Pulse Generator	1974	1993	1	10	250	-	-	-	-	YES	-	-	4	0.1	2	0.05	< 50	1		±5		5
PG503	Pulse Generator	1990	?	Double	10	250	-	-	-	-	YES	-	-	4	0.1	2	0.05	< 50	0.2		±2.5		2.5
PG504	Pulse Generator	?	?	Double	1000	0.1	-	-	-	-	YES
PG505	Pulse Generator	1974	?	1	1	0.1	-	-	-	-	YES			10	0.1	5000	0.05		1000	1		80
PG506	Calibration Generator	1974	1993	1	?	1								1000	0.01			50	1			100	±5	±100
PG507	Pulse Generator	1981	?	Double	5	50	-	-	-	-	YES	-	-	20	0.2	10	0.1	<70	3.5				±7.5	±15
PG508	Pulse Generator	?	?	Double	5	50	-	-	-	-	YES	-	-	20	0.2	10	0.1	< 70	5.5	50	±10		10			-	-	-	-	-	-	-	-	-	-		-
PG509	Pulse Generator	?	?	1		0.05	-	-	-	-		-	-			44	-		0.35				25			-	-	-	-	-	-	-	-	-	-		-
TG501	Time Mark Generator	1974	1990	1			-	-	-	-		-	-	1	5						-	-	1			-	-	-	-	-	-	-	-	-	-		-
TG501A	Time Mark Generator	1990	1995	1			-	-	-	-		-	-	1	5						-	-	1			-	-	-	-	-	-	-	-	-	-		-
PG5110	Pulse Generator	1991	?	2	0.1	50	-	-	-	-	YES			20	10	10	10	1-99	6	100	±10		10	±20		-	-	-	-	-	-	-	-	-	-		GPIB
067-1094-99	Pulse Generator	1983	?	1		0.05	-	-	-	-						40			0.4				25			-	-	-	-	-	-	-	-	-	-		-
High Amplitude Pulse Generator		?	?
067-1046-01		?	?
CG551AP		1980	?
SG502		1972	1993	1	5	0.5	YES	YES	-	-	-	-	-	-	-	-	-		50		-	-		5 rms		-	-	-	-	-	-	-	-	-	-		-
SG503		1974	1993	1	50000	250	YES	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	5pp			-	-	-	-	-	-	-	-	-	-	-	-
SG504		1974	1993	1	50000	1050	YES	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	4pp			-	-	-	-	-	-	-	-	-	-	-	-
SG505		1980	1993	2	10	0.1	YES	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-				-	-	-	-	-	-	-	-	-	-	-	-
SW503		1976	1978	1	1	400	YES	-	-	-	-	-	-	-	-	-	-				-	-				X	X			10	10
CG5001	Calibration Generator	1983	?	1	10	1					YES								1.3				5	200	100
CG5010	Calibration Generator	?	?								YES
CG5011	Calibration Generator	?	?								YES
SG5010		?	?	1	10	0.1638	YES	YES					-						1500					21.2 rms
SG5030		1991	?	1	0.1	550	YES	-	-	-	-	-	-	-	-	-	-	-	-	-			5.5			-	-	-	-	-	-	-	-	-	-	-	GPIB
SG5050		?	?	1	10000	2500	YES	-	-	-	-	-	-	-	-	-	-	-	-	-						-	-	-	-	-	-	-	-	-	-	-	GPIB

7A18

Hi Qfissler, out of curiosity: were is the broken bond on this photo? --Rubasch (talk) 12:02, 9 October 2023 (PDT)

• 

It's between the two pots. I updated the page. Very busy, I think a video would demonstrate... I'll see what I can do...

Qfissler (talk) 14:50, 9 October 2023 (PDT)

don't worry! It just felt like a search image for me, and I could not find it :-) So I asked. You could add an arrow to the image. But it is not necessary! Greetings --Rubasch (talk) 01:33, 10 October 2023 (PDT)

Heh - I might take a photo of the intact gain control pots in a properly working 7A18 for comparison - but, honestly, it's so obvious, an arrow would be insulting. You'll kick yourself, I'm sure, if you look again and see it. I'd been careful to crop the photo so that it was exactly in the centre and easy to spot. Maybe I could add those hints on the page... and maybe I could further describe it: It's the point at which the two pots meet.Qfissler (talk) 08:28, 10 October 2023 (PDT)

Hey, Rubasch - I added a photo of an intact one - also a zoomed copy of the photo you cited :-) - see 7A18 Qfissler (talk) 09:30, 12 October 2023 (PDT)

Now I get it ;-) Was looking at the wrong part. greetings --Rubasch (talk) 12:01, 18 October 2023 (PDT)

Please see User talk:Qfissler/475-parts-test-page. Thanks! --Peter (talk) 06:35, 12 December 2023 (PST)

"Sampler" and "Chopper"

In the context of sampling, I think Tek used "chopper" to refer to instruments like the P6038 Signal Chopper, which is separate from the sampling head itself. In this context, the chopper is performing a function similar to a chopper in a chopper-stabilized op amp, i.e., allowing for accurate measurements down to DC despite the unwanted presence of DC drift in various parts of the measurement instrument. Kurt (talk) 04:58, 7 July 2024 (PDT)

Thanks, Kurt - I was running on limited info - just the markings on the 010-0367-00 10X attenuator I found in a bunch of parts I acquired. I'll aim to search part refs in OCRd manuals to confirm I've not slipped up - but the two places I added it were P6038 and S-3 pages - and was more confused when I saw the P6038 / S3S refs on the P6038 Signal Chopper page - my tiredness mixing up S-3 and S3S. I think I understand now, but sorry if I messed up! Qfissler (talk) 07:11, 7 July 2024 (PDT)

---

Regarding the User:Qfissler#OCR commands, one additional thing to watch out for is preserving original page sizes. For example, the T940-letter-June-1983.pdf PDF metadata claims a page size of 15.63 × 20.84 inches but the original document is presumably 8.5 x 11 inches.

The page size can be obtained in various ways. One way to get the page size in inches is invoke pdfinfo on the file and then divide the "points" dimensions by 72. Note that page size is a per-page attribute in a PDF. So pdfinfo needs to be given the -f and -l flags to get it to output the page sizes of all pages.

Many PDFs that I made over the years were done incorrectly in regard to page size. They can be fixed losslessly but it would have been better to have gotten it right from the beginning. Since the original physical size info was lost, it's not something that can be trivially fixed in an automated fashion. I have a script that normalizes page sizes to a height of 11 inches, which works for a lot of PDFs. But it is not correct in cases where some pages were letter-sized, but scanned in landscape orientation.

If a document is scanned to PDF, it usually starts with the correct page size because the scanner knows the physical size of the page it's scanning. If the scan stays in PDF through whatever processing is done (e.g., OCR), the page size info is generally preserved. Scanned to an image format or converting to an image format as part of processing are the most common ways for page size info to be lost. Of course the page size or DPI info can be passed out-of-band to the program that generates PDF files from the image files. It's just easy to forget to do that. Also, if some pages (e.g., schematics) are scanned at higher DPI than other pages, it's easy to for the page size info to get messed up, mainly due to human error. I've gotten tangled up in that many times.

Some image formats support metadata tags that convey information about the physical size. I don't know how widely (and correctly) those tags are supported.

The VintageTek Museum's microfiche scans have PDF page sizes of 8.5 x 11 inches despite the physical size of the page of microfiche being very small. That behavior seems appropriate to me.

Kurt (talk) 15:18, 26 December 2024 (PST)

Thanks, Kurt - I was using pdfinfo yesterday - I've been thinking about how I might do it all better, including understanding what some of the scans already have by way of bookmarks and TOC links so that I can achieve same if I force red of the OCR. eg I found that the 2335 service manual has invalid bookmarks and pdfinfo didn't tell me anything useful. I can open in Master PDF Editor and see the links, but that was hanging at 27% when I tried OCR... so I need to try more tools to find a useful combination.

Author:          http://www.aa4df.com
Creator:         Acrobat 5.0 Scan Plug-in for Windows
Producer:        Acrobat 5.0 Scan Plug-in for Windows
CreationDate:    Tue Nov  2 00:25:47 2004 GMT
ModDate:         Sun Jun 24 19:52:51 2007 BST
Custom Metadata: no
Metadata Stream: yes
Tagged:          no
UserProperties:  no
Suspects:        no
Form:            AcroForm
JavaScript:      no
Pages:           229
Encrypted:       no
Page size:       611.28 x 802.08 pts
Page rot:        0
File size:       89452430 bytes
Optimized:       no
PDF version:     1.6

Qfissler (talk) 07:09, 27 December 2024 (PST)