$200 reward for information regarding Tek TDS5000B debug - Page 1
Forum section: electronics / testgear

author: Jwalling
author_rank: Unknown
timestamp: October 08, 2020, 09:45:03 am
content: On a TDS5104B I was working on a month ago or so, I noticed a file in the root of the disk drive named debugMsg.log. This is the first timeI've seen a TDS5000B scope with this file; it's normally not generated. It was dated 5/10/2007, so it might have been generated when the scope was in for service at Tek.There's also a file named debugMsg.ini in the calibration folder. I'm unsure if modifications to this file will enable debug logging. I'vetried modifying it a number of ways, but none worked. I'm probably doing something wrong...You'd think you could just do some further testing on each channel to determine where the problem might lie, but this is not the case. Forinstance, if I force an SPC failure on CH1 on a good scope by applying an AC signal to it during test, all the channels will be screwed up withDC offsets when SPC is complete. I suppose the time to debug would be before an SPC is run when the constants were correct, but you don't know there's a problem until you actually run it.I currently have a TDS5104B that fails SPC, but since all the channels have large DC offsets, I'm unable to figure out which channel is causingthe problem. I'm hoping it's one of the attenuators as I have a parts donor board that doesn't initialize properly, but these are verydifficult to remove and I don't want to shot-gun it, I want to be sure I replace the right one.If someone could figure out how to enable logging to generate the file, I'll pay $200 (USD) via paypal to the first person who posts the correct info to this thread.I have the executables scope.exe and Tekscope.exe from the scope if that would help. Looking through scope.exe, there's a lot of references to debug.FYI: On a TDS5000 (no suffix) there is a console port. The box header next to the printer connector on the PPC board is the console port. Pin 1 is closest to the printer connector.Baud rate 38400,8,n,1 The only thing that seems to come out is "WDB READY" after about 3 seconds of the scope app launching,which appears to be a VXWorks thing. Was not able to communicate with port; nothing happens.Contents of debugMsg.ini:Code:# Sample debugMsg.ini file# comments start with the '#' symbol# available commands follow:# debugControl LOCAL|GLOBAL# debugLevel MINOR|MODERATE|SEVERE|CRITICAL# debugOn 'subsystem_name'|*# debugOff 'subsystem_name'|*# ## The debugOn and debugOff commands '*' means all subsystems# ## The defaults without changes from this file are:# debugControl GLOBAL# debugLevel MODERATEdebugOn c:\debug.log|*Contents of debugMsg.log:Code:***************************************File opened: Thu May 10 11:54:59 2007***************************************May 10 11:54:59 - EnablePowerupDiags = 1, puMode=1May 10 11:54:59 - DiagPowerUpDiagsEnabled = 1May 10 11:54:59 - Executing Powerup diags ...May 10 11:54:59 - Test "111" - Processor-->Memory-->DRAMWalk1 startedMay 10 11:54:59 - Test execution time 0.00019583 secMay 10 11:54:59 - Test "112" - Processor-->Memory-->DRAMCell startedMay 10 11:54:59 - Test execution time 0.0052359 secMay 10 11:54:59 - Test "113" - Processor-->Memory-->DRAMMarch startedMay 10 11:54:59 - Test execution time 0.0029037 secMay 10 11:54:59 - Factory Mode Only Test "114" - Processor-->Memory-->NVRAM startedMay 10 11:55:00 - Test execution time 1.8826 secMay 10 11:55:00 - Test "131" - Processor-->Registers-->PAI startedMay 10 11:55:00 - Test execution time 0.00029054 secMay 10 11:55:00 - Test "211" - Display-->Register-->Display startedMay 10 11:55:00 - Test execution time 0.0034781 secMay 10 11:55:00 - Test "311" - Acquisition-->Registers-->DAC startedMay 10 11:55:01 - Test execution time 0.99081 secMay 10 11:55:01 - Test "312" - Acquisition-->Registers-->Demux startedMay 10 11:55:01 - Test execution time 0.0049129 secMay 10 11:55:01 - Test "313" - Acquisition-->Registers-->Preamp startedMay 10 11:55:02 - Test execution time 0.087866 secMay 10 11:55:02 - Test "314" - Acquisition-->Registers-->PLL startedMay 10 11:55:02 - Reference Locked.May 10 11:55:02 - Test execution time 0.059737 secMay 10 11:55:02 - Test "315" - Acquisition-->Registers-->ADC startedMay 10 11:55:02 - Test execution time 0.01444 secMay 10 11:55:02 - Test "321" - Acquisition-->Memory-->MemData startedMay 10 11:55:02 - Test execution time 0.059437 secMay 10 11:55:02 - Test "322" - Acquisition-->Memory-->MemAddr startedMay 10 11:55:02 - Test execution time 0.023141 secMay 10 11:55:02 - Test "323" - Acquisition-->Memory-->DataFormat startedMay 10 11:55:02 - Test execution time 0.0011619 secMay 10 11:55:02 - Factory Mode Only Test "324" - Acquisition-->Memory-->MemSpeed startedMay 10 11:55:24 - Test execution time 22.092 secMay 10 11:55:24 - Test "331" - Acquisition-->Acq Modes-->SubSample startedMay 10 11:55:24 - Test execution time 0.0073277 secMay 10 11:55:24 - Test "332" - Acquisition-->Acq Modes-->PeakDetect startedMay 10 11:55:24 - Test execution time 0.0080088 secMay 10 11:55:24 - Test "333" - Acquisition-->Acq Modes-->HiRes startedMay 10 11:55:24 - Test execution time 0.0075876 secMay 10 11:55:24 - Test "341" - Acquisition-->Interrupt-->Bit Tests startedMay 10 11:55:24 - Test execution time 0.0028962 secMay 10 11:55:24 - Test "371" - Acquisition-->Vertical-->50OhmOvld startedMay 10 11:55:24 - Test execution time 0.38756 secMay 10 11:55:24 - Test "372" - Acquisition-->Vertical-->ADC Connects startedMay 10 11:55:29 - Test execution time 4.3639 secMay 10 11:55:29 - Test "381" - Acquisition-->PLL-->Clock Freq startedMay 10 11:55:29 - Test execution time 0.0058706 secMay 10 11:55:29 - Test "411" - Trigger-->Registers-->GTL startedMay 10 11:55:29 - Test execution time 0.0022995 secMay 10 11:55:29 - Test "412" - Trigger-->Registers-->HITL startedMay 10 11:55:29 - Test execution time 0.0019983 secMay 10 11:55:29 - Test "413" - Trigger-->Registers-->ExtTvTrg startedMay 10 11:55:29 - Test execution time 0.0014203 secMay 10 11:55:29 - Test "421" - Trigger-->TrgLvlComp-->LogicComp1 startedMay 10 11:55:29 - Test execution time 0.074107 secMay 10 11:55:29 - Test "422" - Trigger-->TrgLvlComp-->LogicComp2 startedMay 10 11:55:29 - Test execution time 0.025555 secMay 10 11:55:29 - Test "423" - Trigger-->TrgLvlComp-->LogicComp3 startedMay 10 11:55:29 - Test execution time 0.025423 secMay 10 11:55:29 - Test "424" - Trigger-->TrgLvlComp-->LogicComp4 startedMay 10 11:55:29 - Test execution time 0.025503 secMay 10 11:55:29 - Test "431" - Trigger-->GTL-->TICounters startedMay 10 11:55:29 - Test execution time 0.0097596 secMay 10 11:55:29 - Test "432" - Trigger-->GTL-->GTLBigCntrs startedMay 10 11:55:29 - Test execution time 0.010079 secMay 10 11:55:29 - Test "441" - Trigger-->HITL-->Ch1Edge startedMay 10 11:55:29 - Test execution time 0.013537 secMay 10 11:55:29 - Test "442" - Trigger-->HITL-->AfterDBE startedMay 10 11:55:29 - Test execution time 0.073323 secMay 10 11:55:29 - Test "443" - Trigger-->HITL-->AfterDBT startedMay 10 11:55:29 - Test execution time 0.11942 secMay 10 11:55:29 - Test "444" - Trigger-->HITL-->Slewrate startedMay 10 11:55:29 - Test execution time 0.030582 secMay 10 11:55:29 - Test "445" - Trigger-->HITL-->LineTrig startedMay 10 11:55:29 - Test execution time 0.076672 secMay 10 11:55:29 - Test "446" - Trigger-->HITL-->HITL startedMay 10 11:55:29 - Test execution time 0.013548 secMay 10 11:55:29 - Test "451" - Trigger-->Extended-->Glitch startedMay 10 11:55:29 - Test execution time 0.020193 secMay 10 11:55:29 - Test "452" - Trigger-->Extended-->PulseWidth startedMay 10 11:55:30 - Test execution time 0.21821 secMay 10 11:55:30 - Test "461" - Trigger-->Nibble-->Bus startedMay 10 11:55:30 - Test execution time 0.21462 secMay 10 11:55:30 - Test "511" - Misc-->GPIB-->Interface startedMay 10 11:55:30 - Test execution time 0.029952 secMay 10 11:55:31 - POWERUP DIAGNOSTICS RESULTS: ALL TESTS PASSEDMay 10 11:55:31 - Powerup diags finished in 32.404 secMay 10 11:55:31 - << POWERUP DIAGS FINISHED >>May 10 11:55:31 - THREAD ID: 0X000005A0 hoDither - Started in .\horizDpoMode.cpp at 936.May 10 11:55:31 - THREAD ID: 0X000005C0 acqExecutor - Started in .\acqMsgsToAcqExe.cpp at 57.May 10 11:55:31 - THREAD ID: 0X0000040C acqDsyUpStatsTimerHandler - Started in .\acqUpStatsTimer.cpp at 81.May 10 11:55:31 - Warning, WfmMemMgr::WfmMemAlloc called with 0 byte size. Adjusting.. all hands prepare for combat!May 10 11:55:31 - Warning, WfmMemMgr::WfmMemAlloc called with 0 byte size. Adjusting.. all hands prepare for combat!May 10 11:55:31 - Warning, WfmMemMgr::WfmMemAlloc called with 0 byte size. Adjusting.. all hands prepare for combat!May 10 11:55:31 - THREAD ID: 0X000003FC dsyExecutor - Started in .\dsyExeToDsy.cpp at 50.May 10 11:55:31 - THREAD ID: 0X00000160 dsyBlitFixupFunc - Started in .\dsyDrIntr.cpp at 231.May 10 11:55:31 - Calling upLoadInitialIsdbState.May 10 11:55:31 - THREAD ID: 0X000005D4 calWarmUpThread - Started in .\calPublic.cpp at 1744.May 10 11:55:31 - THREAD ID: 0X000005CC calOverloadThread - Started in .\calPublic.cpp at 1765.May 10 11:55:31 - CALLING GpibStartRunning()May 10 11:55:31 - gpibAddSetToBatch: No command processors in registry! ParamId=0x28000300May 10 11:55:31 - gpibAddSetToBatch: No command processors in registry! ParamId=0x28000306May 10 11:55:31 - GpibStartRunning() COMPLETEMay 10 11:55:31 - CALLING AppsInterfaceStartup()May 10 11:55:32 - CPipeFile::CPipeFile(ControlPipe1): Error duplicating source process handle for read pipe: GetLastError=0May 10 11:55:32 - CPipeFile::CPipeFile(ResultsPipe1): Error duplicating source process handle for read pipe: GetLastError=0May 10 11:55:32 - AppsInterfaceStartup() COMPLETEMay 10 11:55:32 - Init probe change stuff.================================================================SYSTEM INFORMATION:Model: TDS5104BSerial No: B022424Scope.exe Version: 2.0.11; PRODUCTIONOperating System Info:Windows 2000, build #2195Other info: Service Pack 4DEBUG OUTPUT CHANNELS:TRACE: ONMFG PORT: ONTCPIP: OFFFILE: ON; C:\debugMsg.log (overwrite open mode)Size Limit: 1024000 bytesGPIB: Address: 1; DEVICE MODE: On-LineEvent Log: 25 entriesDiagnostics:Powerup mode: FACTORYPowerups Count: 33Options:App 67 Availnot installed.Hardware Configuration:CPU Timer Interval: 1000ACQ NVMEM: 2000ACQ MEM: 8388608CPU MEM: 8388608DSY ASIC REV: 0ACQ PROC VER: 11ACQ BRD ID: 13ACQ BW: 1000ACQ SAMPLE RATE: 2500WFM MEM: 488636416DEMUX ASIC REV: 439bPAI ASIC REV: 5.10Communications Capability:Comm Option Enabled: 0Serial Trigger: 0Clock Recovery: 0Optical Rcvrs: 0================================================================May 10 11:55:56 - <IOP> Fan Control Initialization Complete.May 10 11:56:53 - Apply External +0.300 volts - 50ohms channel 1 for the next stepMay 10 11:57:00 - CAL: Start Factory step External +0.300 volts - 50ohms channel 1.May 10 11:57:05 - Apply External +0.300 volts - 50ohms channel 2 for the next stepMay 10 11:57:10 - CAL: Start Factory step External +0.300 volts - 50ohms channel 2.May 10 11:57:15 - Apply External +0.300 volts - 50ohms channel 3 for the next stepMay 10 11:57:20 - CAL: Start Factory step External +0.300 volts - 50ohms channel 3.May 10 11:57:26 - Apply External +0.300 volts - 50ohms channel 4 for the next stepMay 10 11:57:30 - dsyTXPerformTile: BlitEvent timeout or errorMay 10 11:57:31 - CAL: Start Factory step External +0.300 volts - 50ohms channel 4.May 10 11:57:36 - Apply External +8 volts channel 1 for the next stepMay 10 11:57:42 - CAL: Start Factory step External +8 volts channel 1.May 10 11:57:44 - Apply External -8 volts channel 1 for the next stepMay 10 11:57:49 - CAL: Start Factory step External -8 volts channel 1.May 10 11:57:52 - Apply External +0.8 volts channel 1 for the next stepMay 10 11:57:56 - CAL: Start Factory step External +0.8 volts channel 1.May 10 11:57:59 - Apply External -0.8 volts channel 1 for the next stepMay 10 11:58:04 - CAL: Start Factory step External -0.8 volts channel 1.May 10 11:58:06 - Apply External +0.08 volts channel 1 for the next stepMay 10 11:58:11 - CAL: Start Factory step External +0.08 volts channel 1.May 10 11:58:13 - Apply External -0.08 volts channel 1 for the next stepMay 10 11:58:18 - CAL: Start Factory step External -0.08 volts channel 1.May 10 11:58:20 - Apply External +2 volts channel 1 for the next stepMay 10 11:58:25 - CAL: Start Factory step External +2 volts channel 1.May 10 11:58:28 - Apply External -2 volts channel 1 for the next stepMay 10 11:58:33 - CAL: Start Factory step External -2 volts channel 1.May 10 11:58:36 - Apply External +0.2 volts channel 1 for the next stepMay 10 11:58:41 - CAL: Start Factory step External +0.2 volts channel 1.May 10 11:58:44 - Apply External -0.2 volts channel 1 for the next stepMay 10 11:58:49 - CAL: Start Factory step External -0.2 volts channel 1.May 10 11:58:51 - Apply External +0.02 volts channel 1 for the next stepMay 10 11:58:56 - CAL: Start Factory step External +0.02 volts channel 1.May 10 11:58:59 - Apply External -0.02 volts channel 1 for the next stepMay 10 11:59:04 - CAL: Start Factory step External -0.02 volts channel 1.May 10 11:59:06 - Apply External +99.9 volts - channel 1 for the next stepMay 10 11:59:11 - CAL: Start Factory step External +99.9 volts - channel 1.May 10 11:59:12 - Apply External +9.99 volts - channel 1 for the next stepMay 10 11:59:17 - CAL: Start Factory step External +9.99 volts - channel 1.May 10 11:59:18 - Apply External -9.99 volts - channel 1 for the next stepMay 10 11:59:23 - CAL: Start Factory step External -9.99 volts - channel 1.May 10 11:59:24 - Apply External -99.9 volts - channel 1 for the next stepMay 10 11:59:28 - CAL: Start Factory step External -99.9 volts - channel 1.May 10 11:59:29 - Apply External +99.9 volts - channel 2 for the next stepMay 10 11:59:35 - CAL: Start Factory step External +99.9 volts - channel 2.May 10 11:59:36 - Apply External +9.99 volts - channel 2 for the next stepMay 10 11:59:41 - CAL: Start Factory step External +9.99 volts - channel 2.May 10 11:59:41 - Apply External -9.99 volts - channel 2 for the next stepMay 10 11:59:46 - CAL: Start Factory step External -9.99 volts - channel 2.May 10 11:59:47 - Apply External -99.9 volts - channel 2 for the next stepMay 10 11:59:52 - CAL: Start Factory step External -99.9 volts - channel 2.May 10 11:59:53 - Apply External +99.9 volts - channel 3 for the next stepMay 10 11:59:59 - CAL: Start Factory step External +99.9 volts - channel 3.May 10 11:59:59 - Apply External +9.99 volts - channel 3 for the next stepMay 10 12:00:04 - CAL: Start Factory step External +9.99 volts - channel 3.May 10 12:00:05 - Apply External -9.99 volts - channel 3 for the next stepMay 10 12:00:10 - CAL: Start Factory step External -9.99 volts - channel 3.May 10 12:00:11 - Apply External -99.9 volts - channel 3 for the next stepMay 10 12:00:16 - CAL: Start Factory step External -99.9 volts - channel 3.May 10 12:00:17 - Apply External +99.9 volts - channel 4 for the next stepMay 10 12:00:22 - CAL: Start Factory step External +99.9 volts - channel 4.May 10 12:00:23 - Apply External +9.99 volts - channel 4 for the next stepMay 10 12:00:28 - CAL: Start Factory step External +9.99 volts - channel 4.May 10 12:00:29 - Apply External -9.99 volts - channel 4 for the next stepMay 10 12:00:34 - CAL: Start Factory step External -9.99 volts - channel 4.May 10 12:00:35 - Apply External -99.9 volts - channel 4 for the next stepMay 10 12:00:40 - CAL: Start Factory step External -99.9 volts - channel 4.May 10 12:00:41 - Apply External ground or open all channels for the next stepMay 10 12:00:46 - CAL: Start Factory step External ground or open all channels.May 10 12:01:23 - Apply External +5.0 volts - 50ohms channel 1 for the next stepMay 10 12:01:28 - CAL: Start Factory step External +5.0 volts - 50ohms channel 1.May 10 12:01:29 - Apply External +1.60 volts - 50ohms channel 1 for the next stepMay 10 12:01:34 - CAL: Start Factory step External +1.60 volts - 50ohms channel 1.May 10 12:01:36 - Apply External -1.60 volts - 50ohms channel 1 for the next stepMay 10 12:01:40 - CAL: Start Factory step External -1.60 volts - 50ohms channel 1.May 10 12:01:41 - Apply External -5.0 volts - 50ohms channel 1 for the next stepMay 10 12:01:46 - CAL: Start Factory step External -5.0 volts - 50ohms channel 1.May 10 12:01:47 - Apply External +5.0 volts - 50ohms channel 2 for the next stepMay 10 12:01:53 - CAL: Start Factory step External +5.0 volts - 50ohms channel 2.May 10 12:01:54 - Apply External +1.60 volts - 50ohms channel 2 for the next stepMay 10 12:01:59 - CAL: Start Factory step External +1.60 volts - 50ohms channel 2.May 10 12:02:00 - Apply External -1.60 volts - 50ohms channel 2 for the next stepMay 10 12:02:05 - CAL: Start Factory step External -1.60 volts - 50ohms channel 2.May 10 12:02:06 - Apply External -5.0 volts - 50ohms channel 2 for the next stepMay 10 12:02:11 - CAL: Start Factory step External -5.0 volts - 50ohms channel 2.May 10 12:02:12 - Apply External +5.0 volts - 50ohms channel 3 for the next stepMay 10 12:02:17 - CAL: Start Factory step External +5.0 volts - 50ohms channel 3.May 10 12:02:18 - Apply External +1.60 volts - 50ohms channel 3 for the next stepMay 10 12:02:23 - CAL: Start Factory step External +1.60 volts - 50ohms channel 3.May 10 12:02:25 - Apply External -1.60 volts - 50ohms channel 3 for the next stepMay 10 12:02:30 - CAL: Start Factory step External -1.60 volts - 50ohms channel 3.May 10 12:02:31 - Apply External -5.0 volts - 50ohms channel 3 for the next stepMay 10 12:02:36 - CAL: Start Factory step External -5.0 volts - 50ohms channel 3.May 10 12:02:37 - Apply External +5.0 volts - 50ohms channel 4 for the next stepMay 10 12:02:42 - CAL: Start Factory step External +5.0 volts - 50ohms channel 4.May 10 12:02:43 - Apply External +1.60 volts - 50ohms channel 4 for the next stepMay 10 12:02:48 - CAL: Start Factory step External +1.60 volts - 50ohms channel 4.May 10 12:02:49 - Apply External -1.60 volts - 50ohms channel 4 for the next stepMay 10 12:02:54 - CAL: Start Factory step External -1.60 volts - 50ohms channel 4.May 10 12:02:55 - Apply External -5.0 volts - 50ohms channel 4 for the next stepMay 10 12:03:00 - CAL: Start Factory step External -5.0 volts - 50ohms channel 4.May 10 12:03:01 - Apply External +0.200 volts - 50ohms channel 1 for the next stepMay 10 12:03:07 - CAL: Start Factory step External +0.200 volts - 50ohms channel 1.May 10 12:03:09 - Apply External -0.200 volts - 50ohms channel 1 for the next stepMay 10 12:03:14 - CAL: Start Factory step External -0.200 volts - 50ohms channel 1.May 10 12:03:16 - Apply External +0.200 volts - 50ohms channel 2 for the next stepMay 10 12:03:21 - CAL: Start Factory step External +0.200 volts - 50ohms channel 2.May 10 12:03:23 - Apply External -0.200 volts - 50ohms channel 2 for the next stepMay 10 12:03:28 - CAL: Start Factory step External -0.200 volts - 50ohms channel 2.May 10 12:03:30 - Apply External +0.200 volts - 50ohms channel 3 for the next stepMay 10 12:03:36 - CAL: Start Factory step External +0.200 volts - 50ohms channel 3.May 10 12:03:38 - Apply External -0.200 volts - 50ohms channel 3 for the next stepMay 10 12:03:43 - CAL: Start Factory step External -0.200 volts - 50ohms channel 3.May 10 12:03:46 - Apply External +0.200 volts - 50ohms channel 4 for the next stepMay 10 12:03:51 - CAL: Start Factory step External +0.200 volts - 50ohms channel 4.May 10 12:03:54 - Apply External -0.200 volts - 50ohms channel 4 for the next stepMay 10 12:03:59 - CAL: Start Factory step External -0.200 volts - 50ohms channel 4.May 10 12:04:01 - Apply External +1.50 volts - 50ohms channel 1 for the next stepMay 10 12:04:06 - CAL: Start Factory step External +1.50 volts - 50ohms channel 1.May 10 12:04:09 - Apply External -1.50 volts - 50ohms channel 1 for the next stepMay 10 12:04:14 - CAL: Start Factory step External -1.50 volts - 50ohms channel 1.May 10 12:04:16 - Apply External +1.50 volts - 50ohms channel 2 for the next stepMay 10 12:04:22 - CAL: Start Factory step External +1.50 volts - 50ohms channel 2.May 10 12:04:24 - Apply External -1.50 volts - 50ohms channel 2 for the next stepMay 10 12:04:29 - CAL: Start Factory step External -1.50 volts - 50ohms channel 2.May 10 12:04:31 - Apply External +1.50 volts - 50ohms channel 3 for the next stepMay 10 12:04:37 - CAL: Start Factory step External +1.50 volts - 50ohms channel 3.May 10 12:04:39 - Apply External -1.50 volts - 50ohms channel 3 for the next stepMay 10 12:04:44 - CAL: Start Factory step External -1.50 volts - 50ohms channel 3.May 10 12:04:47 - Apply External +1.50 volts - 50ohms channel 4 for the next stepMay 10 12:04:53 - CAL: Start Factory step External +1.50 volts - 50ohms channel 4.May 10 12:04:55 - Apply External -1.50 volts - 50ohms channel 4 for the next stepMay 10 12:05:00 - CAL: Start Factory step External -1.50 volts - 50ohms channel 4.May 10 12:05:02 - Apply External ground or open all channels for the next stepMay 10 12:05:08 - CAL: Start Factory step External ground or open all channels.May 10 12:05:12 - Apply External 6 Mhz .3 volt - 50ohms channel 1 for the next stepMay 10 12:05:17 - CAL: Start Factory step External 6 Mhz .3 volt - 50ohms channel 1.May 10 12:05:18 - Apply External 6 Mhz .3 volt - 50ohms channel 2 for the next stepMay 10 12:05:23 - CAL: Start Factory step External 6 Mhz .3 volt - 50ohms channel 2.May 10 12:05:25 - Apply External 6 Mhz .3 volt - 50ohms channel 3 for the next stepMay 10 12:05:30 - CAL: Start Factory step External 6 Mhz .3 volt - 50ohms channel 3.May 10 12:05:31 - Apply External 6 Mhz .3 volt - 50ohms channel 4 for the next stepMay 10 12:05:36 - CAL: Start Factory step External 6 Mhz .3 volt - 50ohms channel 4.May 10 12:05:38 - Apply External 505 Mhz .3 volt - 50ohms channel 1 for the next stepMay 10 12:05:43 - CAL: Start Factory step External 505 Mhz .3 volt - 50ohms channel 1.May 10 12:05:54 - Apply External 505 Mhz .3 volt - 50ohms channel 2 for the next stepMay 10 12:05:59 - CAL: Start Factory step External 505 Mhz .3 volt - 50ohms channel 2.May 10 12:06:09 - Apply External 505 Mhz .3 volt - 50ohms channel 3 for the next stepMay 10 12:06:15 - CAL: Start Factory step External 505 Mhz .3 volt - 50ohms channel 3.May 10 12:06:25 - Apply External 505 Mhz .3 volt - 50ohms channel 4 for the next stepMay 10 12:06:31 - CAL: Start Factory step External 505 Mhz .3 volt - 50ohms channel 4.May 10 12:06:41 - Apply External ground or open all channels for the next stepMay 10 12:06:46 - CAL: Start Factory step External ground or open all channels.May 10 12:06:46 - Apply External SPC ground or open all channels for the next stepMay 10 12:06:51 - CAL: Start Factory step External SPC ground or open all channels.May 10 12:06:51 - SHOWTIME: SPC: starting 12:06:51May 10 12:06:59 - SHOWTIME: SPC step : Signal test 00:00:08May 10 12:06:59 - SHOWTIME: SPC step : Et Cal 00:00:00May 10 12:07:10 - SHOWTIME: SPC step : A2D offset and gain 00:00:11May 10 12:07:35 - SHOWTIME: SPC step : A2D interleave 00:00:25May 10 12:07:45 - SHOWTIME: SPC step : A2D pass two offset and gain 00:00:10May 10 12:07:56 - SHOWTIME: SPC step : cfRatio computation 00:00:11May 10 12:08:51 - SHOWTIME: SPC step : M859 offset 00:00:55May 10 12:08:59 - SHOWTIME: SPC step : M859 stepgain 00:00:08May 10 12:09:12 - <IOP> Fan Control Initialization Complete.May 10 12:09:12 - <IOP> FAN CALIBRATION COMPLETE. Acq Sensor offset = 139.45May 10 12:09:22 - SHOWTIME: SPC step : M859 coarse/fine offset DACs 00:00:23May 10 12:10:22 - SHOWTIME: SPC step : M859 varigain DAC 00:01:00May 10 12:10:23 - SHOWTIME: SPC step : M859 Bandwidth limit gain 00:00:01May 10 12:10:46 - SHOWTIME: SPC step : M859 Ground offset 00:00:23May 10 12:10:46 - SHOWTIME: SPC step : Get Temperature 00:00:00May 10 12:11:20 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:34May 10 12:11:40 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:20May 10 12:12:30 - SHOWTIME: SPC step : Hfd117 offset 00:00:50May 10 12:12:34 - SHOWTIME: SPC step : Hfd117 stepgain 00:00:04May 10 12:13:35 - SHOWTIME: SPC step : Hfd117 coarse/fine offset DACs 00:01:01May 10 12:16:06 - SHOWTIME: SPC step : Hfd117 varigain offset correction 00:02:31May 10 12:16:54 - SHOWTIME: SPC step : Trigger Hysteresis 00:00:48May 10 12:17:58 - SHOWTIME: SPC step : Trigger gain and offset 00:01:04May 10 12:18:17 - SHOWTIME: SPC step : Trigger TQ 00:00:19May 10 12:18:45 - SHOWTIME: SPC step : Trigger Sliver 00:00:28May 10 12:18:59 - SHOWTIME: SPC step : overload DAC 00:00:14May 10 12:18:59 - SHOWTIME: SPC: finished 00:00:00May 10 12:18:59 - total time 00:12:08May 10 12:18:59 - Apply External ground or open all channels for the next stepMay 10 12:19:04 - CAL: Start Factory step External ground or open all channels.May 10 12:19:42 - Apply External Deskew 1Mhz signal on all channels for the next stepMay 10 12:19:45 - CAL: Start Factory step External Deskew 1Mhz signal on all channels.May 10 12:21:15 - deSkew chop is for channel 1 measured 6.95397e-011May 10 12:21:16 - deSkew 1 is for channel 0 measured for mode 1May 10 12:21:17 - deSkew -1.649e-010May 10 12:21:17 - deSkew 2 is for channel 1 measured for mode 1May 10 12:21:19 - deSkew -1.28679e-010May 10 12:21:19 - deSkew 3 is for channel 2 measured for mode 2May 10 12:21:21 - deSkew -1.27828e-010May 10 12:21:21 - deSkew 4 is for channel 3 measured for mode 3May 10 12:21:23 - deSkew -1.08252e-010May 10 12:21:23 - deSkew 5 is for channel 1 measured for mode 4May 10 12:21:25 - deSkew -1.29901e-010May 10 12:21:25 - deSkew 6 is for channel 2 measured for mode 4May 10 12:21:27 - deSkew -1.26912e-010May 10 12:21:27 - deSkew 7 is for channel 2 measured for mode 5May 10 12:21:28 - deSkew -1.29958e-010May 10 12:21:28 - deSkew 8 is for channel 3 measured for mode 5May 10 12:21:30 - deSkew -1.11788e-010May 10 12:21:30 - deSkew 9 is for channel 3 measured for mode 6May 10 12:21:32 - deSkew -1.09281e-010May 10 12:21:32 - deSkew 10 is for channel 0 measured for mode 7May 10 12:21:37 - deSkew -2.59846e-010May 10 12:21:37 - deSkew 11 is for channel 1 measured for mode 8May 10 12:21:41 - deSkew -2.26499e-010May 10 12:21:41 - deSkew 12 is for channel 2 measured for mode 9May 10 12:21:45 - deSkew -2.24596e-010May 10 12:21:45 - deSkew 13 is for channel 3 measured for mode 10May 10 12:21:50 - deSkew -2.09098e-010May 10 12:21:50 - deSkew 14 is for channel 0 measured for mode 11May 10 12:22:02 - deSkew -3.5314e-010May 10 12:22:02 - deSkew 15 is for channel 1 measured for mode 12May 10 12:22:15 - deSkew -3.2856e-010May 10 12:22:15 - deSkew 16 is for channel 2 measured for mode 13May 10 12:22:27 - deSkew -3.1808e-010May 10 12:22:28 - deSkew 17 is for channel 3 measured for mode 14May 10 12:22:40 - deSkew -3.1968e-010May 10 12:22:45 - Trigger deSkew base channel 1 is -2.57297e-010May 10 12:22:49 - Trigger deSkew channel 1 is 3.09697e-011May 10 12:22:54 - Trigger deSkew channel 2 is 9.55612e-011May 10 12:22:58 - Trigger deSkew channel 3 is -1.53785e-011May 10 12:22:58 - Trigger deSkew Aux in is -3e-010May 10 12:23:08 - SHOWTIME: SPC: starting 12:23:08May 10 12:23:16 - SHOWTIME: SPC step : Signal test 00:00:08May 10 12:23:16 - SHOWTIME: SPC step : Et Cal 00:00:00May 10 12:23:27 - SHOWTIME: SPC step : A2D offset and gain 00:00:11May 10 12:23:52 - SHOWTIME: SPC step : A2D interleave 00:00:25May 10 12:24:02 - SHOWTIME: SPC step : A2D pass two offset and gain 00:00:10May 10 12:24:13 - SHOWTIME: SPC step : cfRatio computation 00:00:11May 10 12:25:09 - SHOWTIME: SPC step : M859 offset 00:00:56May 10 12:25:17 - SHOWTIME: SPC step : M859 stepgain 00:00:08May 10 12:25:38 - SHOWTIME: SPC step : M859 coarse/fine offset DACs 00:00:21May 10 12:26:38 - SHOWTIME: SPC step : M859 varigain DAC 00:01:00May 10 12:26:39 - SHOWTIME: SPC step : M859 Bandwidth limit gain 00:00:01May 10 12:27:02 - SHOWTIME: SPC step : M859 Ground offset 00:00:23May 10 12:27:02 - SHOWTIME: SPC step : Get Temperature 00:00:00May 10 12:27:36 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:34May 10 12:27:56 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:20May 10 12:28:46 - SHOWTIME: SPC step : Hfd117 offset 00:00:50May 10 12:28:50 - SHOWTIME: SPC step : Hfd117 stepgain 00:00:04May 10 12:29:51 - SHOWTIME: SPC step : Hfd117 coarse/fine offset DACs 00:01:01May 10 12:32:23 - SHOWTIME: SPC step : Hfd117 varigain offset correction 00:02:32May 10 12:33:10 - SHOWTIME: SPC step : Trigger Hysteresis 00:00:47May 10 12:34:15 - SHOWTIME: SPC step : Trigger gain and offset 00:01:05May 10 12:34:32 - SHOWTIME: SPC step : Trigger TQ 00:00:17May 10 12:34:56 - SHOWTIME: SPC step : Trigger Sliver 00:00:24May 10 12:35:10 - SHOWTIME: SPC step : overload DAC 00:00:14May 10 12:35:10 - SHOWTIME: SPC: finished 00:00:00May 10 12:35:10 - total time 00:12:02May 10 12:47:56 - deUpdatePlaneState: TIMEOUT WAITING FOR RASTER DONEMay 10 12:57:52 - deUpdatePlaneState: TIMEOUT WAITING FOR RASTER DONEMay 10 13:37:20 - deUpdatePlaneState: TIMEOUT WAITING FOR RASTER DONEMay 10 14:21:58 - THREAD ID: 0X00000410 mathMainThread - Started in .\sdt\mathexecutor.cpp at 1379.May 10 14:24:18 - Exiting tWinMainMay 10 14:24:18 - CComModule::Unlock() returned 0 -- Setting hEventShutdown.May 10 14:24:19 -SHUTTING DOWN HOUNDDOG APPLICATION.If you don't see a shutdown complete message, something is broken!!May 10 14:24:19 - CALLING GpibShutdown()May 10 14:24:19 - GpibShutdown() COMPLETEMay 10 14:24:19 - CALLING AppsInterfaceShutdown()May 10 14:24:19 - AppsInterfaceShutdown() COMPLETEMay 10 14:24:19 - Calling AutosetRtlShutdown()May 10 14:24:19 - AutosetRtlShutdown() COMPLETEMay 10 14:24:20 - raxClose in progress.May 10 14:24:20 -IOP successfully taken offline.May 10 14:24:21 -Disabling pai interrupt thread.May 10 14:24:21 -Closing pai kernel plugin.May 10 14:24:21 -Disabling iop interrupt thread.May 10 14:24:21 -Closing iop kernel plugin.May 10 14:24:21 - WINDRIVER EXIT COMPLETE.May 10 14:24:21 - tcpipHandleConnections(): Received a bad connection!May 10 14:24:21 - WSAGetLastError = 10004May 10 14:24:21 - tcpipHandleConnections(): Exiting connection thread...

author: darkstar49
author_rank: Frequent Contributor
timestamp: October 08, 2020, 10:20:58 am
content: strange that the sample file somehow contradicts itself...debugOn c:\debug.log|*(it's either subsystem name or '*', but certainly not the log destination)Did you try something likedebugLevel SEVEREdebugOn *

author: Jwalling
author_rank: Unknown
timestamp: October 08, 2020, 12:31:52 pm
content: Quote from: darkstar49 on October 08, 2020, 10:20:58 amNope, that didn't work, thanks.

author: Jwalling
author_rank: Unknown
timestamp: October 08, 2020, 12:35:11 pm
content: I've posted the 2 executables here:http://global-files.net/hesst3

author: abyrvalg
author_rank: Frequent Contributor
timestamp: October 08, 2020, 04:05:55 pm
content: Do you have registry access on the scope? If yes, create a DWORD param named DebugOutToFile with value 1 under HKEY_LOCAL_MACHINE\Software\Tektronix\TekScope\Internal

author: abyrvalg
author_rank: Frequent Contributor
timestamp: October 08, 2020, 04:48:53 pm
content: There is some TCP console on port 1072 also, try telnet there, try this command: password:taurus:rsiMonitor - this should get you to some "repair system monitor" menu with lots of fun.activateDebugFileOutput command to that console should enable debug file loggingEdit: looks like there is a "help" cmd that dumps all commands. "help somecmd" should work too, showing detailed cmd help.

author: Jwalling
author_rank: Unknown
timestamp: October 09, 2020, 09:28:50 am
content: Quote from: abyrvalg on October 08, 2020, 04:05:55 pmThat worked, thanks a million!PM me with your Paypal email and I'll send you the $.With regards to Telnet, the scope is refusing connections on 1072. It accepts connections on 22 and 23, but I get this:NTLM Authentication failed due to insufficient credentials. Please login withclear text username and passwordServer allows NTLM authentication onlyServer has closed connection

author: Jwalling
author_rank: Unknown
timestamp: October 09, 2020, 03:22:35 pm
content: Quote from: abyrvalg on October 08, 2020, 04:05:55 pmThis registry entry also works on the non-suffixed scopes.The one thing I noticed is that debug messages aren't logged when an error occurs during signal path compensation. All you get is a "signal compensation failed" message to the UI, which is no help at all...Don't know if there may be a setting for this.

author: abyrvalg
author_rank: Frequent Contributor
timestamp: October 10, 2020, 08:58:04 am
content: I see that some types of debug messages are output only when debugControl = global. Try these settings in debugMsg.ini (ini is processed and used when DebugOutToFile=1 is set in registry):debugControl globaldebugLevel critical

author: Jwalling
author_rank: Unknown
timestamp: October 10, 2020, 01:10:00 pm
content: Quote from: abyrvalg on October 10, 2020, 08:58:04 amNo difference, only the diagnostics are logged, not SPC failures. Thanks!

author: abyrvalg
author_rank: Frequent Contributor
timestamp: October 10, 2020, 02:47:44 pm
content: Could you tell the exact spelling of that error message? I'll try to look for it's source and inspect the surroundings.

author: Jwalling
author_rank: Unknown
timestamp: October 10, 2020, 04:52:31 pm
content: Quote from: abyrvalg on October 10, 2020, 02:47:44 pmHere's two screen captures.

author: Jwalling
author_rank: Unknown
timestamp: October 28, 2020, 08:49:16 am
content: Although he didn't have to do so, abyrvalg has refunded $100 of the $200 I sent him. That was very nice of him!So, I'm putting up the $100 for anyone who can figure out how to get the SPC log from these scopes.

author: smaultre
author_rank: Regular Contributor
timestamp: November 03, 2020, 01:47:04 pm
content: The control interface board works with their own OS. On the early TDS7000 series there is VxWorks, that used the same HDD to operate.On don't clearly know (i do not repair thisones) only reassemble. But there-is no any other "embeded" OS information on HDD.Maybe you can try to find the diagnostic interface on the control board.Or you can try another way -there is a windows programs that spying about any changes of windows filesystem.You can install them and run prior to the SPC procedure is running, and "spy" about any file systems changes after "faill"-ing.

author: Jwalling
author_rank: Unknown
timestamp: December 13, 2020, 09:08:44 am
content: Quote from: Jwalling on October 28, 2020, 08:49:16 amI'm increasing the reward to $200.

author: yearz
author_rank: Newbie
timestamp: December 16, 2020, 02:02:07 pm
content: you also need to create a DWORD param named "DebugOverride" and set value 1 under "HKEY_LOCAL_MACHINE\Software\Tektronix\TekScope\Internal". it will records messages to c:\debugMsg.log during power on diagnostic,instrument calibration(SPC),instrument diagnostics,maybe included the factory calibration.there are some factory calibration log in your debugmsg.loghere is tds5054 with firmware ver 1.1.2 debug messageCode:***************************************File opened: Tue Jan 08 15:37:46 2019***************************************Jan 08 15:37:46 -Scope.exe RELEASE build.Jan 08 15:37:46 - Initializing KrfTech WinDriver.Jan 08 15:37:46 - WinDriver open was successful.Jan 08 15:37:46 - Expected WinDriver version 505 is correct.Jan 08 15:37:46 - Opening Hounddog IO processorJan 08 15:37:46 - CExeModule::Unlock: 4Jan 08 15:37:46 - CExeModule::Unlock: 5Jan 08 15:37:46 - CExeModule::Unlock: 4Jan 08 15:37:46 - CExeModule::Unlock: 3Jan 08 15:37:46 - One card with desired ids on bus 2 in slot 13 with function 0.Jan 08 15:37:46 - Successfully fetched PCI card information.Jan 08 15:37:46 - There are 4 items in the card information.Jan 08 15:37:46 - IOP card register was successful.Jan 08 15:37:46 - Item 0:Jan 08 15:37:46 -Sharable.:Jan 08 15:37:46 -ID 5 = BUSJan 08 15:37:46 - Item 1:Jan 08 15:37:46 -Sharable.:Jan 08 15:37:46 -ID 1 = INTERRUPTJan 08 15:37:46 -IRQ = 11Jan 08 15:37:46 -LEVEL SENSITIVE INTERRUPT.Jan 08 15:37:46 - Item 2:Jan 08 15:37:46 -NOT Sharable.:Jan 08 15:37:46 -ID 2 = MEMORYJan 08 15:37:46 -Base Address = 0xf3800000.Jan 08 15:37:46 -Length = 0x00800000 (8388608) bytes.Jan 08 15:37:46 -WD_Transfer Base Address = 0xd1688000.Jan 08 15:37:46 -Direct user memory transfer base address = 0xd1688000.Jan 08 15:37:46 -CPU physical address = 0xf3800000.Jan 08 15:37:46 - Item 3:Jan 08 15:37:46 -NOT Sharable.:Jan 08 15:37:46 -ID 2 = MEMORYJan 08 15:37:46 -Base Address = 0xf43e0000.Jan 08 15:37:46 -Length = 0x00020000 (131072) bytes.Jan 08 15:37:46 -WD_Transfer Base Address = 0xd1e88000.Jan 08 15:37:46 -Direct user memory transfer base address = 0xd1e88000.Jan 08 15:37:46 -CPU physical address = 0xf43e0000.Jan 08 15:37:46 - Opening TDS5000 PCI Aquisition InterfaceJan 08 15:37:46 - One card with desired ids on bus 2 in slot 14 with function 0.Jan 08 15:37:46 - Successfully fetched PCI card information.Jan 08 15:37:46 - There are 3 items in the card information.Jan 08 15:37:46 - PAI card register was successful.Jan 08 15:37:46 - Item 0:Jan 08 15:37:46 -Sharable.:Jan 08 15:37:46 -ID 5 = BUSJan 08 15:37:46 - Item 1:Jan 08 15:37:46 -Sharable.:Jan 08 15:37:46 -ID 1 = INTERRUPTJan 08 15:37:46 -IRQ = 11Jan 08 15:37:46 -LEVEL SENSITIVE INTERRUPT.Jan 08 15:37:46 - Item 2:Jan 08 15:37:46 -NOT Sharable.:Jan 08 15:37:46 -ID 2 = MEMORYJan 08 15:37:46 -Base Address = 0xfc700000.Jan 08 15:37:46 -Length = 0x00100000 (1048576) bytes.Jan 08 15:37:46 -WD_Transfer Base Address = 0xd1ea8000.Jan 08 15:37:46 -Direct user memory transfer base address = 0xd1ea8000.Jan 08 15:37:46 -CPU physical address = 0xfc700000.Jan 08 15:37:46 -TDS5000 PCI Aquisition Interface V3.25 Tektronix (c) 2002Jan 08 15:37:46 - Querying board id.Jan 08 15:37:46 - &theGTL.regs = 0X006AE4DCJan 08 15:37:46 - Board id from gtl = 0x0000000bJan 08 15:37:46 - Bandwidth option is 500 MHz.Jan 08 15:37:46 - Four channel option selected.Jan 08 15:37:46 - THREAD ID: 0X00000000 TreadFunc started here using _beginthread which does not give you a thread id.- Started in D:\view_storage\TDS5000_Version_1.1\hounddog\Win\scope\trmgrif.cpp at 261.Jan 08 15:37:46 - Hardware-Software interface specification 4.0 selected.Jan 08 15:37:46 - THREAD ID: 0XBFF71585 Started ThreadFunc - Started in D:\view_storage\TDS5000_Version_1.1\hounddog\Win\scope\trmgrif.cpp at 2228.Jan 08 15:37:46 - THREAD ID: 0XBFF71585 Started ThreadFunc - Started in D:\view_storage\TDS5000_Version_1.1\hounddog\Win\scope\trmgrif.cpp at 3254.Jan 08 15:37:47 - Verified 1296 bytes of avr code.Jan 08 15:37:47 - AVR processor code OK.Jan 08 15:37:47 - IOP Kernel plugin open OK.Jan 08 15:37:47 - IOP IRQ clear address = 0x80026844Jan 08 15:37:47 - Fan control constants are up to date.Jan 08 15:37:48 - ----------------------------------------------Jan 08 15:37:48 - IOP Init State: 9500Jan 08 15:37:48 - IOP Init State: 1000Jan 08 15:37:48 - IOP Init State: 1800Jan 08 15:37:49 - IOP Init State: 1900Jan 08 15:37:49 - IOP Init State: 2300Jan 08 15:37:49 - IOP Init State: 9001Jan 08 15:37:49 - ----------------------------------------------Jan 08 15:37:49 - <IOP> IopInterruptTask started.Jan 08 15:37:49 - Windows and IOP message IDs compatible.Jan 08 15:37:49 - Received handshake from send message to IOP.Jan 08 15:37:49 - IOP diagnostics started at 15:37:49Jan 08 15:37:57 - IOP diagnostics finished 15:37:57 - 15:37:49 = 00:08Jan 08 15:37:59 - <IOP> rebootMonitorTask started.Jan 08 15:37:59 - AVR communications OK.Jan 08 15:37:59 - Initializing: ATODJan 08 15:37:59 - Initializing: DACJan 08 15:37:59 - Initializing: DEMUXJan 08 15:37:59 - Initializing: Dsy338Jan 08 15:37:59 - Initializing: ExtTvTrigControlJan 08 15:37:59 - Initializing: GTLJan 08 15:37:59 - Initializing: HITLJan 08 15:37:59 - Initializing: PLLJan 08 15:37:59 - Initializing: PaiBaseJan 08 15:37:59 - Initializing: PreampJan 08 15:37:59 - Pai kernel plugin open OK.Jan 08 15:37:59 - Correct kernel driver TDS5000 V1.00.02.000.Jan 08 15:37:59 - Correct kernel driver KP_IOP V1.00.02.000.Jan 08 15:37:59 - THREAD ID: 0XFFFA8973 Monitor External Reference. - Started in D:\view_storage\TDS5000_Version_1.1\hounddog\Win\hardwareAccess\raxRefMonitor.cpp at 37.Jan 08 15:38:02 -systemInitOnCreate: DEBUG OUTPUT IS ENABLED BY REGISTRY KEY OVERRIDEJan 08 15:38:02 - tcpipHandleConnections(): Thread ID 0xFFFA95C3 initialized to handle incoming connectionsJan 08 15:38:02 - THREAD ID: 0XFFFA990B slotMgrMsgHandler - Started in D:\view_storage\TDS5000_Version_1.1\hounddog\Win\slotMgr\slotMgrPublic.cpp at 70.Jan 08 15:38:02 - THREAD ID: 0XFFFA9C3F saveRecallWfmMsgHandler - Started in D:\view_storage\TDS5000_Version_1.1\hounddog\Win\saveRecallWfm\saveRecallWfmPublic.cpp at 219.Jan 08 15:38:02 - THREAD ID: 0XFFFB7EA3 mathUpMapperHndlr - Started in D:\view_storage\TDS5000_Version_1.1\hounddog\Win\mathMeas\sdt\mathUpMapper.cpp at 183.Jan 08 15:38:02 - THREAD ID: 0XFFFAA0EF mathNetMgrHandler - Started in D:\view_storage\TDS5000_Version_1.1\hounddog\Win\mathMeas\sdt\mathNetMgr.cpp at 144.Jan 08 15:38:02 - GpibInitialize() COMPLETEJan 08 15:38:02 - Calling TmgrStartup.Jan 08 15:38:02 - THREAD ID: 0XFFFB04B3 tmgrTaskInit - Started in D:\view_storage\TDS5000_Version_1.1\hounddog\Win\transMgr\src\tmgrClass.cpp at 1682.Jan 08 15:38:02 - THREAD ID: 0XFFFB0AE7 TimerHandler - Started in D:\view_storage\TDS5000_Version_1.1\hounddog\Win\utility\timerPkg.cpp at 67.Jan 08 15:38:02 - THREAD ID: 0XFFFB0CD3 tmgrStartDbSaveProcess - Started in D:\view_storage\TDS5000_Version_1.1\hounddog\Win\transMgr\src\tmgrClass.cpp at 1700.Jan 08 15:38:02 - THREAD ID: 0XFFFB0F0F rtlPMsgReceiver - Started in D:\view_storage\TDS5000_Version_1.1\hounddog\Win\acqDsyNetMgr\acqDsyNetMgrPublic.cpp at 275.Jan 08 15:38:02 - CAL: Error reading constants from NVramJan 08 15:38:02 - EnablePowerupDiags = 1, puMode=0Jan 08 15:38:02 - DiagPowerUpDiagsEnabled = 1Jan 08 15:38:02 - Executing Powerup diags ...Jan 08 15:38:02 - Test "111" - Processor-->Memory-->DRAMWalk1Jan 08 15:38:02 - Test "112" - Processor-->Memory-->DRAMCellJan 08 15:38:02 - Test "113" - Processor-->Memory-->DRAMMarchJan 08 15:38:02 - Test "131" - Processor-->Registers-->PAIJan 08 15:38:02 - Test "211" - Display-->Register-->DisplayJan 08 15:38:02 - Test "311" - Acquisition-->Registers-->DACJan 08 15:38:03 - Test "312" - Acquisition-->Registers-->DemuxJan 08 15:38:03 - Test "313" - Acquisition-->Registers-->PreampJan 08 15:38:04 - Test "314" - Acquisition-->Registers-->PLLJan 08 15:38:04 - Test "315" - Acquisition-->Registers-->ADCJan 08 15:38:04 - Test "321" - Acquisition-->Memory-->MemDataJan 08 15:38:04 - Test "322" - Acquisition-->Memory-->MemAddrJan 08 15:38:04 - Test "323" - Acquisition-->Memory-->DataFormatJan 08 15:38:04 - Test "331" - Acquisition-->Acq Modes-->SubSampleJan 08 15:38:04 - Test "332" - Acquisition-->Acq Modes-->PeakDetectJan 08 15:38:04 - Test "333" - Acquisition-->Acq Modes-->HiResJan 08 15:38:04 - Test "341" - Acquisition-->Interrupt-->Bit TestsJan 08 15:38:04 - Test "371" - Acquisition-->Vertical-->50OhmOvldJan 08 15:38:04 - Test "372" - Acquisition-->Vertical-->ADC ConnectsJan 08 15:38:04 - Reference Locked.Jan 08 15:38:05 - Test "381" - Acquisition-->PLL-->Clock FreqJan 08 15:38:05 - Test "411" - Trigger-->Registers-->GTLJan 08 15:38:05 - Test "412" - Trigger-->Registers-->HITLJan 08 15:38:05 - Test "413" - Trigger-->Registers-->ExtTvTrgJan 08 15:38:05 - Test "421" - Trigger-->TrgLvlComp-->LogicComp1Jan 08 15:38:05 - Test "422" - Trigger-->TrgLvlComp-->LogicComp2Jan 08 15:38:05 - Test "423" - Trigger-->TrgLvlComp-->LogicComp3Jan 08 15:38:05 - Test "424" - Trigger-->TrgLvlComp-->LogicComp4Jan 08 15:38:05 - Test "431" - Trigger-->GTL-->TICountersJan 08 15:38:05 - Test "432" - Trigger-->GTL-->GTLBigCntrsJan 08 15:38:05 - Test "441" - Trigger-->HITL-->Ch1EdgeJan 08 15:38:05 - Test "442" - Trigger-->HITL-->AfterDBEJan 08 15:38:05 - Test "443" - Trigger-->HITL-->AfterDBTJan 08 15:38:05 - Test "444" - Trigger-->HITL-->SlewrateJan 08 15:38:05 - Test "445" - Trigger-->HITL-->LineTrigJan 08 15:38:05 - Test "446" - Trigger-->HITL-->HITLJan 08 15:38:05 - Test "451" - Trigger-->Extended-->GlitchJan 08 15:38:05 - Test "452" - Trigger-->Extended-->PulseWidthJan 08 15:38:06 - Test "461" - Trigger-->Nibble-->BusJan 08 15:38:06 - Test "511" - Misc-->GPIB-->InterfaceJan 08 15:38:07 - HF step remainder = 145<145<145ps, 0/1 fail/pass ratioJan 08 15:38:07 - POWERUP DIAGNOSTICS RESULTS: ALL TESTS PASSEDJan 08 15:38:07 - Powerup diags finished in 00:05 minutes:secondsJan 08 15:38:07 - << POWERUP DIAGS FINISHED >>Jan 08 15:38:07 - THREAD ID: 0XFFFB117B rtlHelper - Started in D:\view_storage\TDS5000_Version_1.1\hounddog\Win\acqDsyNetMgr\rtlHelper.cpp at 132.Jan 08 15:38:07 - THREAD ID: 0XFFFB1357 hoDither - Started in D:\view_storage\TDS5000_Version_1.1\hounddog\Win\acq\HorizDpoMode.cpp at 924.Jan 08 15:38:07 - THREAD ID: 0X00000000 acqExecutor - Started in D:\view_storage\TDS5000_Version_1.1\hounddog\Win\acq\acqMsgsToAcqExe.cpp at 64.Jan 08 15:38:07 - THREAD ID: 0XFFFB1623 deHelper - Started in D:\view_storage\TDS5000_Version_1.1\hounddog\Win\dsy\deHelper.cpp at 177.Jan 08 15:38:07 - CALLING GpibStartRunning()Jan 08 15:38:07 - GpibStartRunning() COMPLETE================================================================SYSTEM INFORMATION:Model: TDS5054Serial No: B020432Scope.exe Version: 1.1.2; PRODUCTIONOperating System Info:Windows Me, build #3000Other info:DEBUG OUTPUT CHANNELS:TRACE: ONMFG PORT: ONTCPIP: OFFFILE: ON; C:\debugMsg.log (overwrite open mode)Size Limit: 1024000 bytesGPIB: Address: 3; (On-Line)Event Log: 107 entriesDiagnostics:Powerup mode: USERPowerups Count: 491Options:2A:Advanced Analysis SoftwareHardware Configuration:CPU Timer Interval: 1000ACQ NVMEM: 2000ACQ MEM: 4194304CPU MEM: 8388608DSY ASIC REV: 0ACQ PROC VER: 11ACQ BRD ID: 13ACQ BW: 500ACQ SAMPLE RATE: 2500WFM MEM: 85983232DEMUX ASIC REV: 17307PAI ASIC REV: 3.25Communications Capability:Comm Option Enabled: 0Serial Trigger: 0Clock Recovery: 0Optical Rcvrs: 0================================================================Jan 08 15:38:19 - <IOP> Fan Control Initialization Complete.Jan 08 15:38:25 - DIAGNOSTIC EXECUTION starting ...Jan 08 15:38:25 - Test "111" - Processor-->Memory-->DRAMWalk1Jan 08 15:38:25 - Test "112" - Processor-->Memory-->DRAMCellJan 08 15:38:25 - Test "113" - Processor-->Memory-->DRAMMarchJan 08 15:38:25 - Test "114" - Processor-->Memory-->NVRAMJan 08 15:38:33 - Test "121" - Processor-->PCI Bus-->Scan TestJan 08 15:38:33 - Test "131" - Processor-->Registers-->PAIJan 08 15:38:33 - Test "211" - Display-->Register-->DisplayJan 08 15:38:33 - Test "311" - Acquisition-->Registers-->DACJan 08 15:38:34 - Test "312" - Acquisition-->Registers-->DemuxJan 08 15:38:34 - Test "313" - Acquisition-->Registers-->PreampJan 08 15:38:34 - Test "314" - Acquisition-->Registers-->PLLJan 08 15:38:34 - Test "315" - Acquisition-->Registers-->ADCJan 08 15:38:34 - Test "321" - Acquisition-->Memory-->MemDataJan 08 15:38:34 - Test "322" - Acquisition-->Memory-->MemAddrJan 08 15:38:34 - Test "323" - Acquisition-->Memory-->DataFormatJan 08 15:38:34 - Test "324" - Acquisition-->Memory-->MemSpeedJan 08 15:38:47 - Test "331" - Acquisition-->Acq Modes-->SubSampleJan 08 15:38:47 - Test "332" - Acquisition-->Acq Modes-->PeakDetectJan 08 15:38:47 - Test "333" - Acquisition-->Acq Modes-->HiResJan 08 15:38:47 - Test "341" - Acquisition-->Interrupt-->Bit TestsJan 08 15:38:47 - Test "351" - Acquisition-->HFStep-->PhaseCalJan 08 15:38:48 - HF step remainder = 134<134<145ps, 0/2 fail/pass ratioJan 08 15:38:48 - Test "361" - Acquisition-->Demuxes-->InstaVuXYJan 08 15:38:48 - Test "371" - Acquisition-->Vertical-->50OhmOvldJan 08 15:38:48 - Test "372" - Acquisition-->Vertical-->ADC ConnectsJan 08 15:38:49 - Test "381" - Acquisition-->PLL-->Clock FreqJan 08 15:38:49 - Test "411" - Trigger-->Registers-->GTLJan 08 15:38:49 - Test "412" - Trigger-->Registers-->HITLJan 08 15:38:49 - Test "413" - Trigger-->Registers-->ExtTvTrgJan 08 15:38:49 - Test "421" - Trigger-->TrgLvlComp-->LogicComp1Jan 08 15:38:49 - Test "422" - Trigger-->TrgLvlComp-->LogicComp2Jan 08 15:38:49 - Test "423" - Trigger-->TrgLvlComp-->LogicComp3Jan 08 15:38:49 - Test "424" - Trigger-->TrgLvlComp-->LogicComp4Jan 08 15:38:49 - Test "431" - Trigger-->GTL-->TICountersJan 08 15:38:49 - Test "432" - Trigger-->GTL-->GTLBigCntrsJan 08 15:38:49 - Test "441" - Trigger-->HITL-->Ch1EdgeJan 08 15:38:49 - Test "442" - Trigger-->HITL-->AfterDBEJan 08 15:38:49 - Test "443" - Trigger-->HITL-->AfterDBTJan 08 15:38:49 - Test "444" - Trigger-->HITL-->SlewrateJan 08 15:38:49 - Test "445" - Trigger-->HITL-->LineTrigJan 08 15:38:49 - Test "446" - Trigger-->HITL-->HITLJan 08 15:38:49 - Test "451" - Trigger-->Extended-->GlitchJan 08 15:38:49 - Test "452" - Trigger-->Extended-->PulseWidthJan 08 15:38:49 - Test "461" - Trigger-->Nibble-->BusJan 08 15:38:50 - Test "511" - Misc-->GPIB-->InterfaceJan 08 15:38:50 - *** TEST SKIPPED ***Jan 08 15:38:50 - DIAGNOSTIC EXECUTION finished in 00:25 minutes:secondsJan 08 15:38:50 - HF step remainder = 134<148<148ps, 0/3 fail/pass ratioJan 08 15:39:58 - SHOWTIME: SPC: starting 15:39:58Jan 08 15:40:03 - SHOWTIME: SPC step : Signal test 00:00:05Jan 08 15:40:04 - SHOWTIME: SPC step : Et Cal 00:00:01Jan 08 15:40:11 - SHOWTIME: SPC step : A2D offset and gain 00:00:07Jan 08 15:41:00 - SHOWTIME: SPC step : A2D interleave 00:00:49Jan 08 15:41:07 - SHOWTIME: SPC step : A2D pass two offset and gain 00:00:07Jan 08 15:41:16 - SHOWTIME: SPC step : cfRatio computation 00:00:09Jan 08 15:41:52 - SHOWTIME: SPC step : M859 offset 00:00:36Jan 08 15:41:59 - SHOWTIME: SPC step : M859 stepgain 00:00:07Jan 08 15:42:15 - findDacValue: failed to find good DAC value for HIGHJan 08 15:42:17 - SHOWTIME: SPC step : M859 coarse/fine offset DACs 00:00:18Jan 08 15:42:56 - SHOWTIME: SPC step : M859 varigain DAC 00:00:39Jan 08 15:42:56 - SHOWTIME: SPC step : M859 Bandwidth limit gain 00:00:00Jan 08 15:43:17 - SHOWTIME: SPC step : M859 Ground offset 00:00:21Jan 08 15:43:17 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 08 15:43:17 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:00Jan 08 15:43:17 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:00Jan 08 15:43:17 - SHOWTIME: SPC step : Hfd117 offset 00:00:00Jan 08 15:43:17 - SHOWTIME: SPC step : Hfd117 stepgain 00:00:00Jan 08 15:43:17 - SHOWTIME: SPC step : Hfd117 coarse/fine offset DACs 00:00:00Jan 08 15:43:17 - SHOWTIME: SPC step : Hfd117 varigain offset correction 00:00:00Jan 08 15:44:02 - SHOWTIME: SPC step : Trigger Hysteresis 00:00:45Jan 08 15:45:05 - SHOWTIME: SPC step : Trigger gain and offset 00:01:03Jan 08 15:45:23 - SHOWTIME: SPC step : Trigger TQ 00:00:18Jan 08 15:45:51 - SHOWTIME: SPC step : Trigger Sliver 00:00:28Jan 08 15:45:55 - SHOWTIME: SPC step : overload DAC 00:00:04Jan 08 15:45:55 - SHOWTIME: SPC: finished 00:00:00Jan 08 15:45:55 - total time 00:05:57Jan 08 15:45:56 - HF step remainder = 134<163<163ps, 0/4 fail/pass ratioJan 08 15:46:06 - CExeModule::Unlock: 8Jan 08 15:46:06 - CExeModule::Unlock: 9Jan 08 15:46:06 - CExeModule::Unlock: 8Jan 08 15:46:06 - CExeModule::Unlock: 7Jan 08 15:46:06 - CExeModule::Unlock: 6Jan 08 15:46:06 - CExeModule::Unlock: 5Jan 08 15:46:06 - CExeModule::Unlock: 4Jan 08 15:46:06 - CExeModule::Unlock: 3Jan 08 15:46:06 - CExeModule::Unlock: 2Jan 08 15:46:06 - CExeModule::Unlock: 1Jan 08 15:46:06 - CExeModule::Unlock: 0Jan 08 15:46:06 - CComModule::Unlock() returned 0 -- Setting hEventShutdown.Jan 08 15:46:06 - Exiting tWinMainJan 08 15:46:07 -SHUTTING DOWN HOUNDDOG APPLICATION.If you don't see a shutdown complete message, something is broken!!Jan 08 15:46:07 - CALLING GpibShutdown()Jan 08 15:46:07 - GpibShutdown() COMPLETEJan 08 15:46:07 - CALLING AppsInterfaceShutdown()Jan 08 15:46:07 - AppsInterfaceShutdown() COMPLETEJan 08 15:46:08 - Calling AutosetRtlShutdown()Jan 08 15:46:08 - AutosetRtlShutdown() COMPLETEJan 08 15:46:10 - raxClose in progress.Jan 08 15:46:10 -IOP successfully taken offline.Jan 08 15:46:11 -Closing interrupt.Jan 08 15:46:11 -Disabling pai interrupt thread.Jan 08 15:46:11 -Closing pai kernel plugin.Jan 08 15:46:11 -Disabling iop interrupt thread.Jan 08 15:46:11 -Closing iop kernel plugin.Jan 08 15:46:11 -Unregistering PAI.Jan 08 15:46:11 -Unregistering IOP.Jan 08 15:46:11 -Closing WinDriver.Jan 08 15:46:11 - WINDRIVER EXIT COMPLETE.Jan 08 15:46:13 - CExeModule::Unlock: 1Jan 08 15:46:13 - CExeModule::Unlock: 0Jan 08 15:46:13 - CComModule::Unlock() returned 0 -- Setting hEventShutdown.

author: Jwalling
author_rank: Unknown
timestamp: December 17, 2020, 11:02:06 am
content: Quote from: yearz on December 16, 2020, 02:02:07 pmHi yearz,This didn't work on a TDS5104B with 2.0.11 firmware.A screen capture of the registry. Thanks!

author: Jwalling
author_rank: Unknown
timestamp: December 18, 2020, 11:11:11 am
content: I tried yearz's registry entry on a VM5000 which is identical to a TDS5104 (not a B suffix), and it works.Nice work, yearz!Since this was a working scope, I forced SPC failures by applying 1VDC to each channel in turn.Near as I can see, there is no real information that would pinpoint which channel is actually failing, unless I'm missing something...SPC debugMsg 1VDC applied to CH1:Dec 18 05:39:36 - SHOWTIME: SPC: starting 05:39:36Dec 18 05:39:43 - CAL: SPC returned an error in step Signal testDec 18 05:39:43 - CAL: SPC failedDec 18 05:39:43 - HF step - goal = -7<+14/+14<+14ps min<xer_ps/xer_ps<max, 0/8 fail/total ratioDec 18 05:39:46 - <IOP> Fan Control Initialization Complete.SPC debugMsg 1VDC applied to CH2:Dec 18 05:41:22 - SHOWTIME: SPC: starting 05:41:22Dec 18 05:41:29 - CAL: SPC returned an error in step Signal testDec 18 05:41:29 - CAL: SPC failedDec 18 05:41:29 - HF step - goal = -2<+23/+39<+39ps min<xer_ps/xer_ps<max, 0/8 fail/total ratioDec 18 05:41:31 - <IOP> Fan Control Initialization Complete.SPC debugMsg 1VDC applied to CH3:Dec 18 05:44:06 - SHOWTIME: SPC: starting 05:44:06Dec 18 05:44:14 - CAL: SPC returned an error in step Signal testDec 18 05:44:14 - CAL: SPC failedDec 18 05:44:14 - HF step - goal = -11<-7/-7<+13ps min<xer_ps/xer_ps<max, 0/8 fail/total ratioDec 18 05:44:16 - <IOP> Fan Control Initialization Complete.SPC debugMsg 1VDC applied to CH4:Dec 18 05:45:23 - SHOWTIME: SPC: starting 05:45:23Dec 18 05:45:30 - CAL: SPC returned an error in step Signal testDec 18 05:45:30 - CAL: SPC failedDec 18 05:45:30 - HF step - goal = -21<-5/+18<+18ps min<xer_ps/xer_ps<max, 0/8 fail/total ratioDec 18 05:45:33 - <IOP> Fan Control Initialization Complete.SPC debugMsg 1VDC applied to CH1 AND CH2:Dec 18 05:57:22 - SHOWTIME: SPC: starting 05:57:22Dec 18 05:57:30 - CAL: SPC returned an error in step Signal testDec 18 05:57:30 - CAL: SPC failedDec 18 05:57:30 - HF step - goal = -18<+13/+0<+28ps min<xer_ps/xer_ps<max, 0/8 fail/total ratioDec 18 05:57:34 - <IOP> Fan Control Initialization Complete.EDIT: WTF didn't the programmers just spit out the failing channel?

author: Jwalling
author_rank: Unknown
timestamp: January 03, 2021, 05:00:13 pm
content: Quote from: Jwalling on December 17, 2020, 11:02:06 amI am in the process of repairing a TDS5054B with the same firmware version, and I tried yearz's registry entry on it. It worked!I then cloned the drive and booted it on my failing scope. It also worked. So there is something different on the disk drive...Anyway, I owe you $200 yearz. I'm sending a PM to you so I can get you paid.Now the SPC failure is getting logged:QuoteDoesn't seem to really point to which channel is failing though...

author: voltsandjolts
author_rank: Unknown
timestamp: January 03, 2021, 05:42:21 pm
content: If a channel fails SPC, does it skip some tests for that channel, such that SPC completes in a shorter time?If so, you could apply 1V to each channel in turn during SPC, to force failure on that channel. Four SPCs in total.Applying 1V to the failing channel should not shorten the current SPC time, while for others it would?Just a thought.

author: abyrvalg
author_rank: Frequent Contributor
timestamp: January 03, 2021, 09:48:48 pm
content: Looks like the logging subsystem limits the message length. Guess what is that "is under 6 on c"? - the full message reads as "is under X on ch Y."Could you send me the scope.exe running on your scope now? I'll patch it to shorten the text so the channel number will be visible.

author: Jwalling
author_rank: Unknown
timestamp: January 04, 2021, 09:53:26 am
content: Quote from: abyrvalg on January 03, 2021, 09:48:48 pmWow, I didn't see that. Good spot!Here's the scope.exe. Thanks!

author: DC1MC
author_rank: Super Contributor
timestamp: January 04, 2021, 12:39:48 pm
content: Quote from: abyrvalg on January 03, 2021, 09:48:48 pmI've also seen serial terminal programs behaving like this, when they are not configured to wrap the line, minicom is one of the offenders. It's worth having a look into this as well.Cheers,DC1MC

author: abyrvalg
author_rank: Frequent Contributor
timestamp: January 04, 2021, 02:48:41 pm
content: Done! It will say "is <" instead of "is under".

author: DC1MC
author_rank: Super Contributor
timestamp: January 04, 2021, 03:10:27 pm
content: Quote from: tv84 on January 04, 2021, 02:56:01 pmIt depends, what if the particular terminal window is even smaller?

author: tv84
author_rank: Super Contributor
timestamp: January 04, 2021, 03:16:20 pm
content: Quote from: DC1MC on January 04, 2021, 03:10:27 pmHow so? Unless the scope has more than several million channels, with the change that @abyrvalg did, the channel number will be visible.

author: abyrvalg
author_rank: Frequent Contributor
timestamp: January 04, 2021, 09:04:20 pm
content: As far as I understood this log goes to a file on the scope, not serial port. But lines cut to 80 chars (a typical number for terminal width) look suspicious anyway.In any case, I'm not hunting for additional reward, the subject doesn't feel like a "find the right single bit" task anymore, the final solution will be a combination of many smaller ideas I guess.

author: DC1MC
author_rank: Super Contributor
timestamp: January 04, 2021, 09:49:38 pm
content: Quote from: abyrvalg on January 04, 2021, 09:04:20 pmThanks for your work, I may get a non-starting DSO9000 next week, maybe we'll be able to use your expertise there as well.Cheers,DC1MC

author: Jwalling
author_rank: Unknown
timestamp: January 07, 2021, 10:28:07 am
content: Quote from: abyrvalg on January 04, 2021, 02:48:41 pmThat worked. Many thanks for that!So I did some testing and rework. 21 passes of SPC. I removed all the extra output in the log and just concentrated on the failures.Code:Jan 05 04:35:41 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 05 04:35:52 - findVibnullDac: failed to find good DAC value for HIGHJan 05 04:36:22 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:41Jan 05 04:36:43 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:21Jan 05 04:37:55 - SHOWTIME: SPC step : Hfd117 offset 00:01:12CAL: Gain error samples (5.119844 : 1.388271) OOR for hfd at 2mV on ch 2CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 05 05:24:28 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 05 05:24:39 - findVibnullDac: failed to find good DAC value for HIGHJan 05 05:25:09 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:41Jan 05 05:25:29 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:20Jan 05 05:26:40 - SHOWTIME: SPC step : Hfd117 offset 00:01:11CAL: Gain error samples for hfd at 2mV : (0.899248 : -1.069323) is < 6 on ch 1CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 05 05:49:55 - findVibnullDac: failed to find good DAC value for HIGHJan 05 05:50:26 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:42Jan 05 05:50:47 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:21Jan 05 05:51:59 - SHOWTIME: SPC step : Hfd117 offset 00:01:12CAL: Gain error samples (5.119844 : 0.878797) OOR for hfd at 2mV on ch 2CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 05 05:58:33 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 05 05:58:44 - findVibnullDac: failed to find good DAC value for HIGHJan 05 05:59:13 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:40Jan 05 05:59:33 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:20Jan 05 06:00:45 - SHOWTIME: SPC step : Hfd117 offset 00:01:12CAL: Gain error samples for hfd at 2mV : (0.903158 : -1.073383) is < 6 on ch 1CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 05 06:16:34 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 05 06:16:47 - findVibnullDac: failed to find good DAC value for HIGHJan 05 06:17:20 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:46Jan 05 06:17:44 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:24Jan 05 06:19:07 - SHOWTIME: SPC step : Hfd117 offset 00:01:23CAL: Gain error samples (5.119844 : 0.906090) OOR for hfd at 2mV on ch 2CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 05 06:25:44 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 05 06:25:57 - findVibnullDac: failed to find good DAC value for HIGHJan 05 06:26:31 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:47Jan 05 06:26:54 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:23Jan 05 06:28:15 - SHOWTIME: SPC step : Hfd117 offset 00:01:21CAL: Gain error samples for hfd at 2mV : (1.496541 : -1.594211) is < 6 on ch 1CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 05 06:35:40 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 05 06:35:53 - findVibnullDac: failed to find good DAC value for HIGHJan 05 06:36:28 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:48Jan 05 06:36:51 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:23Jan 05 06:38:16 - SHOWTIME: SPC step : Hfd117 offset 00:01:25CAL: Gain error samples (5.119844 : 1.518271) OOR for hfd at 2mV on ch 2CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 05 06:47:33 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 05 06:47:45 - findVibnullDac: failed to find good DAC value for HIGHJan 05 06:48:21 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:48Jan 05 06:48:44 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:23Jan 05 06:50:05 - SHOWTIME: SPC step : Hfd117 offset 00:01:21CAL: Gain error samples (5.119844 : 0.898196) OOR for hfd at 2mV on ch 2CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 05 07:01:18 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 05 07:01:30 - findVibnullDac: failed to find good DAC value for HIGHJan 05 07:02:05 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:47Jan 05 07:02:28 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:23Jan 05 07:03:52 - SHOWTIME: SPC step : Hfd117 offset 00:01:24CAL: Gain error samples (5.119844 : 1.305113) OOR for hfd at 2mV on ch 2CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 05 08:42:55 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 05 08:43:07 - findVibnullDac: failed to find good DAC value for HIGHJan 05 08:43:37 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:42Jan 05 08:43:57 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:20Jan 05 08:45:08 - SHOWTIME: SPC step : Hfd117 offset 00:01:11CAL: Gain error samples (5.119844 : 1.417218) OOR for hfd at 2mV on ch 2CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 05 08:51:09 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 05 08:51:20 - findVibnullDac: failed to find good DAC value for HIGHJan 05 08:51:50 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:41Jan 05 08:52:09 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:19Jan 05 08:53:21 - SHOWTIME: SPC step : Hfd117 offset 00:01:12CAL: Gain error samples (5.119844 : 0.752105) OOR for hfd at 2mV on ch 2CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 05 08:59:10 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 05 08:59:21 - findVibnullDac: failed to find good DAC value for HIGHJan 05 08:59:50 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:40Jan 05 09:00:10 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:20Jan 05 09:01:21 - SHOWTIME: SPC step : Hfd117 offset 00:01:11CAL: Gain error samples for hfd at 2mV : (0.940827 : -1.103083) is < 6 on ch 1CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 05 09:14:36 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 05 09:14:47 - findVibnullDac: failed to find good DAC value for HIGHJan 05 09:15:18 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:42Jan 05 09:15:38 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:20Jan 05 09:16:48 - SHOWTIME: SPC step : Hfd117 offset 00:01:10CAL: Gain error samples for hfd at 2mV : (2.211353 : -2.640000) is < 6 on ch 1CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 05 09:23:51 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 05 09:24:04 - findVibnullDac: failed to find good DAC value for HIGHJan 05 09:24:40 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:49Jan 05 09:25:04 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:24Jan 05 09:26:26 - SHOWTIME: SPC step : Hfd117 offset 00:01:22CAL: Gain error samples for hfd at 2mV : (1.736241 : -1.793985) is < 6 on ch 1CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 05 11:22:35 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 05 11:22:49 - findVibnullDac: failed to find good DAC value for HIGHJan 05 11:23:24 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:49Jan 05 11:23:48 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:24Jan 05 11:24:19 - findDacValue: failed to find good DAC value after 20 tries.CAL: Offset error in hfd117 10mv Fine dac value on channel 2CAL: SPC returned an error in step Hfd117 offsetCAL: SPC failedJan 05 12:44:37 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 05 12:44:51 - findVibnullDac: failed to find good DAC value for HIGHJan 05 12:45:25 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:48Jan 05 12:45:49 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:24Jan 05 12:47:14 - SHOWTIME: SPC step : Hfd117 offset 00:01:25CAL: Gain error samples (5.119844 : 0.388571) OOR for hfd at 2mV on ch 2CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 05 12:55:10 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 05 12:55:23 - findVibnullDac: failed to find good DAC value for HIGHJan 05 12:55:58 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:48Jan 05 12:56:23 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:25Jan 05 12:57:47 - SHOWTIME: SPC step : Hfd117 offset 00:01:24CAL: Gain error samples (5.119844 : 1.613008) OOR for hfd at 2mV on ch 2CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 05 13:09:16 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 05 13:09:29 - findVibnullDac: failed to find good DAC value for HIGHJan 05 13:10:04 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:48Jan 05 13:10:28 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:24Jan 05 13:11:53 - SHOWTIME: SPC step : Hfd117 offset 00:01:25CAL: Gain error samples (4.231654 : -5.113316) OOR for hfd at 2mV on ch 1CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 05 14:05:38 - SHOWTIME: SPC step : M859 offset 00:01:56CAL: Gain error samples (5.119844 : -2.490827) OOR on ch 2CAL: Gain error samples for M859 1mV channel 2 failed.CAL: SPC returned an error in step M859 stepgainCAL: SPC failedJan 05 14:25:46 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 05 14:26:00 - findVibnullDac: failed to find good DAC value for HIGHJan 05 14:26:36 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:50Jan 05 14:27:00 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:24Jan 05 14:28:24 - SHOWTIME: SPC step : Hfd117 offset 00:01:24CAL: Gain error samples for hfd at 2mV : (1.631880 : -2.031955) is < 6 on ch 1CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 05 14:45:26 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 05 14:45:40 - findVibnullDac: failed to find good DAC value for HIGHJan 05 14:46:16 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:50Jan 05 14:46:41 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:25Jan 05 14:48:07 - SHOWTIME: SPC step : Hfd117 offset 00:01:26CAL: Gain error samples (5.119844 : 2.060000) OOR for hfd at 2mV on ch 2CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failed13 failures on CH2, 8 failures on CH1. Ugh, why couldn't it just be one channel?Since there were more failures on Ch2, I replaced that attenuator.21 more passes:Code:Jan 06 05:55:54 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 06 05:56:06 - findVibnullDac: failed to find good DAC value for HIGHJan 06 05:56:35 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:41Jan 06 05:56:55 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:20Jan 06 05:58:07 - SHOWTIME: SPC step : Hfd117 offset 00:01:12CAL: Gain error samples for hfd at 2mV : (0.999774 : -1.135940) is < 6 on ch 1CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 06 06:06:07 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 06 06:06:19 - findVibnullDac: failed to find good DAC value for HIGHJan 06 06:06:48 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:41Jan 06 06:07:07 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:19Jan 06 06:08:21 - SHOWTIME: SPC step : Hfd117 offset 00:01:14CAL: Gain error samples (5.119844 : 0.887444) OOR for hfd at 2mV on ch 2CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 06 06:21:24 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 06 06:21:37 - findVibnullDac: failed to find good DAC value for HIGHJan 06 06:22:10 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:46Jan 06 06:22:34 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:24Jan 06 06:23:59 - SHOWTIME: SPC step : Hfd117 offset 00:01:25CAL: Gain error samples for hfd at 2mV : (2.519098 : -2.956617) is < 6 on ch 1CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 06 06:39:46 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 06 06:39:59 - findVibnullDac: failed to find good DAC value for HIGHJan 06 06:40:34 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:48Jan 06 06:40:58 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:24Jan 06 06:42:20 - SHOWTIME: SPC step : Hfd117 offset 00:01:22CAL: Gain error samples (5.119844 : 1.608496) OOR for hfd at 2mV on ch 2CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 06 06:49:54 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 06 06:50:07 - findVibnullDac: failed to find good DAC value for HIGHJan 06 06:50:42 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:48Jan 06 06:51:05 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:23Jan 06 06:52:29 - SHOWTIME: SPC step : Hfd117 offset 00:01:24CAL: Gain error samples for hfd at 2mV : (2.338421 : -2.741128) is < 6 on ch 1CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 06 07:03:03 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 06 07:03:16 - findVibnullDac: failed to find good DAC value for HIGHJan 06 07:03:50 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:47Jan 06 07:04:14 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:24Jan 06 07:05:38 - SHOWTIME: SPC step : Hfd117 offset 00:01:24CAL: Gain error samples (5.119844 : 1.264962) OOR for hfd at 2mV on ch 2CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 06 07:12:35 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 06 07:12:47 - findVibnullDac: failed to find good DAC value for HIGHJan 06 07:13:22 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:47Jan 06 07:13:45 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:23Jan 06 07:15:09 - SHOWTIME: SPC step : Hfd117 offset 00:01:24CAL: Gain error samples for hfd at 2mV : (0.974060 : -1.127368) is < 6 on ch 1CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 06 07:24:15 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 06 07:24:28 - findVibnullDac: failed to find good DAC value for HIGHJan 06 07:25:02 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:47Jan 06 07:25:26 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:24Jan 06 07:26:49 - SHOWTIME: SPC step : Hfd117 offset 00:01:23CAL: Gain error samples for hfd at 2mV : (1.639549 : -2.052256) is < 6 on ch 1CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 06 07:33:50 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 06 07:34:03 - findVibnullDac: failed to find good DAC value for HIGHJan 06 07:34:39 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:49Jan 06 07:35:02 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:23Jan 06 07:36:25 - SHOWTIME: SPC step : Hfd117 offset 00:01:23CAL: Gain error samples for hfd at 2mV : (1.395038 : -1.494511) is < 6 on ch 1CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 06 07:43:41 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 06 07:43:54 - findVibnullDac: failed to find good DAC value for HIGHJan 06 07:44:28 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:47Jan 06 07:44:51 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:23Jan 06 07:46:16 - SHOWTIME: SPC step : Hfd117 offset 00:01:25CAL: Gain error samples for hfd at 2mV : (2.530075 : -2.965564) is < 6 on ch 1CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 06 07:59:08 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 06 07:59:22 - findVibnullDac: failed to find good DAC value for HIGHJan 06 07:59:56 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:48Jan 06 08:00:20 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:24Jan 06 08:00:57 - findDacValue: failed to find good DAC value after 20 tries.CAL: Offset error in hfd117 10mv Fine dac value on channel 4CAL: SPC returned an error in step Hfd117 offsetCAL: SPC failedJan 06 08:08:23 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 06 08:08:37 - findVibnullDac: failed to find good DAC value for HIGHJan 06 08:09:11 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:48Jan 06 08:09:34 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:23Jan 06 08:10:57 - SHOWTIME: SPC step : Hfd117 offset 00:01:23CAL: Gain error samples for hfd at 2mV : (2.632707 : -3.078947) is < 6 on ch 1CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 06 08:22:42 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 06 08:22:55 - findVibnullDac: failed to find good DAC value for HIGHJan 06 08:23:31 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:49Jan 06 08:23:54 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:23Jan 06 08:25:20 - SHOWTIME: SPC step : Hfd117 offset 00:01:26CAL: Gain error samples for hfd at 2mV : (0.911128 : -1.067444) is < 6 on ch 1CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 06 08:37:11 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 06 08:37:25 - findVibnullDac: failed to find good DAC value for HIGHJan 06 08:38:01 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:50Jan 06 08:38:25 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:24Jan 06 08:39:47 - SHOWTIME: SPC step : Hfd117 offset 00:01:22CAL: Gain error samples for hfd at 2mV : (2.092406 : -2.495940) is < 6 on ch 1CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 06 08:56:57 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 06 08:57:10 - findVibnullDac: failed to find good DAC value for HIGHJan 06 08:57:44 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:47Jan 06 08:58:08 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:24Jan 06 08:59:32 - SHOWTIME: SPC step : Hfd117 offset 00:01:24CAL: Gain error samples for hfd at 2mV : (1.431504 : -1.530602) is < 6 on ch 1CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 06 09:27:58 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 06 09:28:12 - findVibnullDac: failed to find good DAC value for HIGHJan 06 09:28:47 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:49Jan 06 09:29:11 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:24Jan 06 09:30:33 - SHOWTIME: SPC step : Hfd117 offset 00:01:22CAL: Gain error samples (5.119844 : 1.120902) OOR for hfd at 2mV on ch 2CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 06 09:49:07 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 06 09:49:20 - findVibnullDac: failed to find good DAC value for HIGHJan 06 09:49:54 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:47Jan 06 09:50:19 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:25Jan 06 09:51:42 - SHOWTIME: SPC step : Hfd117 offset 00:01:23CAL: Gain error samples (4.223684 : -5.113691) OOR for hfd at 2mV on ch 1CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 06 09:59:29 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 06 09:59:40 - findVibnullDac: failed to find good DAC value for HIGHJan 06 10:00:09 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:40Jan 06 10:00:30 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:21Jan 06 10:01:39 - SHOWTIME: SPC step : Hfd117 offset 00:01:09CAL: Gain error samples for hfd at 2mV : (1.846090 : -2.258120) is < 6 on ch 1CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 06 10:17:13 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 06 10:17:24 - findVibnullDac: failed to find good DAC value for HIGHJan 06 10:17:54 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:41Jan 06 10:18:14 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:20Jan 06 10:18:46 - findDacValue: failed to find good DAC value after 20 tries.CAL: Offset error in hfd117 10mv Fine dac value on channel 4CAL: SPC returned an error in step Hfd117 offsetCAL: SPC failedJan 06 10:58:36 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 06 10:58:50 - findVibnullDac: failed to find good DAC value for HIGHJan 06 10:59:25 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:49Jan 06 10:59:49 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:24Jan 06 11:01:14 - SHOWTIME: SPC step : Hfd117 offset 00:01:25CAL: Gain error samples for hfd at 2mV : (2.055789 : -2.482556) is < 6 on ch 1CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failedJan 06 11:13:45 - SHOWTIME: SPC step : Get Temperature 00:00:00Jan 06 11:13:58 - findVibnullDac: failed to find good DAC value for HIGHJan 06 11:14:33 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:48Jan 06 11:14:57 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:24Jan 06 11:16:20 - SHOWTIME: SPC step : Hfd117 offset 00:01:23CAL: Gain error samples (5.119844 : 1.144511) OOR for hfd at 2mV on ch 2CAL: SPC returned an error in step Hfd117 stepgainCAL: SPC failed21 passes, 5 failures on CH2, 14 failures on CH1, 2 failures on CH4. Ch4 now too, eh?Not very conclusive, but the bulk of the failures shifted to CH1.I'm beginning to think that one of the DACs may be at fault. The one thing that sticks out are theQuoteWhich pretty much happens on every SPC run. They are 74 ball AD5516 16 channel DAC BGA devices, which I don't have the capability to replace.The non-B suffix TDS5104 used IMP I10412-01 gull-wing DACs (Tek referred to them as daculators) which were also used in the TDS700 series scopes.That would have been easy...I'm debating about whether to replace the attenuator on CH1 now. I don't think it will fix the scope, but it might be interesting to see how the failures distribute themselves on a 3rd run. If it were an easy replacement, I'd do it. But these things are abitchto remove without breaking them. The ground and power planes are tough to clear. Also, on the component side of the board, the pins flare out and get soldered on the top of the pad itself. I had to use a small probe to break the pins free of the solder after clearing the hole with my Pace.F*ck me...I'll think about doing CH1 for a day or two.Some pics:

author: abyrvalg
author_rank: Frequent Contributor
timestamp: January 07, 2021, 08:00:21 pm
content: "OOR" in the other kind of error is my edit too, that's "out of range".

author: Jwalling
author_rank: Unknown
timestamp: January 10, 2021, 11:08:22 am
content: Quote from: Jwalling on January 07, 2021, 10:28:07 amI did it. Not much change, 14 failures on CH1, 7 on CH2, 1 on CH4 (22 passes this time). Not a complete loss I suppose, I have two attenuators that I think are OK should I ever need them. I'll use this scope as a parts unit.

author: Jwalling
author_rank: Unknown
timestamp: January 10, 2021, 11:09:13 am
content: Quote from: abyrvalg on January 07, 2021, 08:00:21 pmI knew that.Thanks for your help once again.EDIT: I never heard back from yearz so I couldn't pay him. yearz, where are youz!?

author: jbruneaux
author_rank: Newbie
timestamp: February 12, 2021, 08:28:25 am
content: Hi,Thank you all for the debug help given here. Although this didn't solve my problem, at least now I can get some logs from this scope.Just a note for others DPO5000/DPO7000 users (mine is a DPO7104, but the software seems the same), if the application crashed during startup (the tektronix application TekScope.exe starts, the startup-logo is displayed, then after a few clicks from the relays (but not the tons of furious clicks that should normally be heard at each boot), the application crashes and wan't to send a report to microsoft), then check the date. Mine was somehow (probably a dead rtc battery) set to 2040, and it seems like it make the application crash. I found this thanks to the log messages in the hidden c:\tekscope\calibration folder. The scope was able to boot one time during my attemps to make it work, and by looking at the logs, I saw it was crashing when trying to output the date after the serial number of the product.Setting back the date to the current date has fixed it.Regards,

author: madao
author_rank: Frequent Contributor
timestamp: June 11, 2025, 06:42:02 pm
content: I wanna make notice.U1320 on PC-IO Interface card.163-1584-00.zip(5.98 kB - downloaded 8 times.)They store also failure message, my TDS5104B has issuses with SPC EPROM error and SPC failed..Excatly same as likeQuote from: Jwalling on October 10, 2020, 04:52:31 pmMy case: Error 372EPROM on U1320 told me. U814 is not OK. (SRAM )

author: harrimansat
author_rank: Regular Contributor
timestamp: October 06, 2025, 08:57:52 am
content: Working non B 5054 log***************************************File opened: Mon Oct 06 10:46:23 2025***************************************Oct 06 10:46:33 - EnablePowerupDiags = 1, puMode=0Oct 06 10:46:33 - DiagPowerUpDiagsEnabled = 1Oct 06 10:46:33 - Executing Powerup diags ...Oct 06 10:46:33 - Test "111" - Processor-->Memory-->DRAMWalk1Oct 06 10:46:33 - Test "112" - Processor-->Memory-->DRAMCellOct 06 10:46:33 - Test "113" - Processor-->Memory-->DRAMMarchOct 06 10:46:33 - Test "131" - Processor-->Registers-->PAIOct 06 10:46:33 - Test "211" - Display-->Register-->DisplayOct 06 10:46:33 - Test "311" - Acquisition-->Registers-->DACOct 06 10:46:34 - Test "312" - Acquisition-->Registers-->DemuxOct 06 10:46:34 - Test "313" - Acquisition-->Registers-->PreampOct 06 10:46:35 - Test "314" - Acquisition-->Registers-->PLLOct 06 10:46:35 - Test "315" - Acquisition-->Registers-->ADCOct 06 10:46:35 - Test "321" - Acquisition-->Memory-->MemDataOct 06 10:46:35 - Test "322" - Acquisition-->Memory-->MemAddrOct 06 10:46:35 - Test "323" - Acquisition-->Memory-->DataFormatOct 06 10:46:35 - Test "331" - Acquisition-->Acq Modes-->SubSampleOct 06 10:46:35 - Test "332" - Acquisition-->Acq Modes-->PeakDetectOct 06 10:46:35 - Test "333" - Acquisition-->Acq Modes-->HiResOct 06 10:46:35 - Test "341" - Acquisition-->Interrupt-->Bit TestsOct 06 10:46:35 - Test "371" - Acquisition-->Vertical-->50OhmOvldOct 06 10:46:35 - Test "372" - Acquisition-->Vertical-->ADC ConnectsOct 06 10:46:36 - Test "381" - Acquisition-->PLL-->Clock FreqOct 06 10:46:36 - Test "411" - Trigger-->Registers-->GTLOct 06 10:46:36 - Test "412" - Trigger-->Registers-->HITLOct 06 10:46:36 - Test "413" - Trigger-->Registers-->ExtTvTrgOct 06 10:46:36 - Test "421" - Trigger-->TrgLvlComp-->LogicComp1Oct 06 10:46:36 - Test "422" - Trigger-->TrgLvlComp-->LogicComp2Oct 06 10:46:36 - Test "423" - Trigger-->TrgLvlComp-->LogicComp3Oct 06 10:46:36 - Test "424" - Trigger-->TrgLvlComp-->LogicComp4Oct 06 10:46:36 - Test "431" - Trigger-->GTL-->TICountersOct 06 10:46:36 - Test "432" - Trigger-->GTL-->GTLBigCntrsOct 06 10:46:36 - Test "441" - Trigger-->HITL-->Ch1EdgeOct 06 10:46:36 - Test "442" - Trigger-->HITL-->AfterDBEOct 06 10:46:36 - Test "443" - Trigger-->HITL-->AfterDBTOct 06 10:46:36 - Test "444" - Trigger-->HITL-->SlewrateOct 06 10:46:36 - Test "445" - Trigger-->HITL-->LineTrigOct 06 10:46:36 - Test "446" - Trigger-->HITL-->HITLOct 06 10:46:36 - Test "451" - Trigger-->Extended-->GlitchOct 06 10:46:36 - Test "452" - Trigger-->Extended-->PulseWidthOct 06 10:46:36 - Test "461" - Trigger-->Nibble-->BusOct 06 10:46:37 - Test "511" - Misc-->GPIB-->InterfaceOct 06 10:46:37 - POWERUP DIAGNOSTICS RESULTS: ALL TESTS PASSEDOct 06 10:46:37 - Powerup diags finished in 00:04 minutes:secondsOct 06 10:46:37 - << POWERUP DIAGS FINISHED >>