TDS7104 can not pass SPC,need help! - Page 1
Forum section: electronics / testgear

author: scofun
author_rank: Newbie
timestamp: December 11, 2024, 09:18:34 am
content: HI,ALLI just entered the EEV forum, and this is my first time postingI have a TDS7104 scope that was working properly and passing its self-test and SPC at the time it was stored away.But today it can not pass SPCI read the startup information through the RS232 port of the PPC board and obtained the following code:Code:UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUromPost: MPC106 Walking-one passed.romPost: MPC106 configuration passed.romPost: First PCI access passed.romPost: PC87560 Walking-one passed.romPost: PC87560 configuration passed.romPost: DEC21554 configuration passed.romPost: PERFORMING ROM CHECKSUM TEST...romPost: ROM checksum passed.romPost: PERFORMING DRAM CELL TEST...romPost: Enabling data cache...romPost: Data cache enabled.romPost: Enabling instruction cache...romPost: Instruction cache enabled.romPost: DRAM Cell test passed.romPost: Disabling data Cache...romPost: Data cache disabled.romPost: Disabling instruction cache...romPost: Instruction cache disabled.romPost: PERFORMING DRAM MARCH TEST WITH CACHE OFF...romPost: Writing address to each *address...romPost: Reading address from each *address...romPost: DRAM march test passed...romPost: PERFORMING DRAM MARCH TEST WITH CACHE ON...romPost: Enabling data cache...romPost: Data cache enabled.romPost: Enabling instruction cache...romPost: Instruction cache enabled.romPost: Writing address to each *address...romPost: Reading address from each *address...romPost: DRAM march test passed...romPost: PERFORMING DRAM WALKING-ONE TEST...romPost: DRAM Walking-one test passed.romPost: PERFORMING NV-MEMORY WALKING-ONE TEST...romPost: NV-MEMORY Walking-one test passed.romPost: Disabling data Cache...romPost: Data cache disabled.romPost: Disabling instruction cache...romPost: Instruction cache disabled.romPost: Enabling instruction cache...romPost: Instruction cache enabled.romPost: POWER-UP DIAGNOSTIC COMPLETE.HelVxWorks System BootCopyright 1984-1996 Wind River Systems, Inc.CPU: Tektronix HPP - PowerPC 740Version: 5.3.1BSP version: 1.0.3.0Creation date: Jun 28 2000, 16:52:12Press any key to stop auto-boot...0auto-booting...boot device : smprocessor number : 0host name : hostfile name : c:\vxBoot\vxWorks.stinet on ethernet (e) : 192.168.0.2:ffffff00inet on backplane (b): 192.168.0.2:ffffff00host inet (h) : 192.168.0.1gateway inet (g) : 192.168.0.2user (u) : anonymousftp password (pw) : anonymousflags (f) : 0x1008target name (tn) : tds7000startup script (s) : c:\vxBoot\topScript.hwother (o) : nvfs=0x1000Initializing backplane net with anchor at 0x1e80000... done.Backplane anchor at 0x1e80000... Attaching network interface sm0... donedone.Attaching network interface lo0... done.PC1 dio device driver installedAttaching DIO client... done.Loading c:\vxBoot\vxWorks.st...1773516Starting at 0x200000...Initializing backplane net with anchor at 0x16e0000... done.Backplane anchor at 0x16e0000... Attaching network interface sm0... donedone.PC1 dio device driver installedAttaching network interface lo0... done.Adding 6008 symbols for standalone.]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] ]]]] ]]]]]]]]]] ]] ]]]] (R)] ]]]]]]]]] ]]]]]] ]]]]]]]] ]] ]]]]]] ]]]]]]] ]]]]]]]] ]]]]]] ] ]] ]]]]]]] ]]]]] ] ]]] ] ]]]] ]]] ]]]]]]]]] ]]]] ]] ]]]] ]] ]]]]]]]]] ]]] ]] ] ]]] ]] ]]]]] ]]]]]] ]] ]]]]]]] ]]]] ]] ]]]]]]]]] ] ]]]] ]]]]] ]]]]]]]] ]]]] ]] ]]]] ]]]]]]] ]]]]]]]]]] ]]]]] ]]]]]] ] ]]]]] ]]]] ]] ]]]] ]]]]]]]] ]]]]]]]]]]] ]]]]] ] ]]]]]] ] ]]] ]]]] ]] ]]]] ]]]] ]]]] ]]]]]]]]]]]] ]]]]] ]]] ]]]]]]] ] ]]]]]]] ]]]] ]]]] ]]]] ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] Development System]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] VxWorks version 5.3.1]]]]]]]]]]]]]]]]]]]]]]]]]] KERNEL: WIND version 2.5]]]]]]]]]]]]]]]]]]]]]]]]] Copyright Wind River Systems, Inc., 1984-1997CPU: Tektronix HPP - PowerPC 740. Processor #0.Memory Size: 0x2000000. BSP version 1.0.8.1 .WDB: Ready.usrNvFsInit: NAME=/nvram BASE=0xfd0ff100 BPB=512 BPT=8 NB=8 BO=0nvfs: STATUS: Mounting existing NVRAM file systemKERNEL: THERMAL CONTROL INITIATEDExecuting startup script c:\vxBoot\topScript.hw ...dbFsIoctl: invalid code 3################### topScript starts ###############################cd "dbfs:c:/vxBoot"value = 0 = 0x0ld < TekScope.ovalue = 23662048 = 0x1690de0ld < TekScopeSM.ovalue = 23661408 = 0x1690b60pDbDev = ramDevCreate(0, 512, 1152, 1152, 0)new symbol "pDbDev" added to symbol table.pDbDev = 0x1692720: value = 23668544 = 0x1692740 = pDbDev + 0x20pDBfs = dosFsMkfs("/db", pDbDev)new symbol "pDBfs" added to symbol table.pDBfs = 0x16909a0: value = 23661056 = 0x1690a00 = pDBfs + 0x60copy ("TekScope.DBF", "/db/TekScope.DBF")value = 0 = 0x0overrideFPdefaults()value = 0 = 0x0measurePPCtimebasevalue = 0 = 0x0registerMemPartitionSizes ( 0x00000000 )value = 0 = 0x0semInitForQueueCheckLogMsgvalue = 21818112 = 0x14ceb00initSysWaiter()value = 0 = 0x0raxInitvalue = 0 = 0x0paiInitdonevalue = 17770552 = 0x10f2838 = PaiBaseRegisterTable + 0x948verifyAcqBoardIDvalue = 0 = 0x0updateAcqProcFirmware("dbfs:c:/vxBoot/acqProc.hex")0x16975c0 (tShell): AVR FLASH contents match file dbfs:c:/vxBoot/acqProc.hex - no programming needed.value = 1 = 0x1cd "pc:"value = 0 = 0x0raxInitializeDevices0x16975c0 (tShell): >> Setting PLL to 1.25e+09 Hz.done0x16975c0 (tShell): (Re)starting Acq Processorvalue = 23688080 = 0x1697390excHookAdd(stopStressForException)value = 17557980 = 0x10be9dc = stopStressForExceptiondsyInitvalue = 21806728 = 0x14cbe88dsyWPApplyNextRegsvalue = 17760428 = 0x10f00ac = DsyRegisterTable + 0xab0# remove '#' from next line to set powerup scope state to factory default:# NvramClearDb = 1nvram_initFileSys0x16975c0 (tShell): >> Kernel version 1.0.8.1 does not match Boot ROM version 1.0.3.0value = -49409789 = 0xfd0e1103 = pDbDev + 0xfba4e9e3TmgrInit("/db")0x16975c0 (tShell): NO BACKUP SERIAL NUMBER FOUND, RESTORING VALUE FROM DISK...0x16975c0 (tShell): NO BACKUP SERIAL NUMBER FOUND, RESTORING VALUE FROM DISK...value = 0 = 0x0PhxProxyInitvalue = 20819360 = 0x13dada0rtlInitvalue = 0 = 0x0sysExtMemAddToPool memSysPartId,0x02000000,0x06000000value = 0 = 0x0hwAccount_init0x16975c0 (tShell): >> Setting PLL to 1.25e+09 Hz.sysEnetAddrGet: e1:21:aa:24:d7:a0value = 7 = 0x7GpibInitvalue = 133284512 = 0x7f1c2a0wfmMemInit(1)value = 47300320 = 0x2d1bee0vertInstallvalue = 47293284 = 0x2d1a364calConStatus = cc_init(2)0x16975c0 (tShell): Reading 280 bytes of service cal data from EEPROM into 0x2d1a2400x16975c0 (tShell): nvMem_read succeeded0x16975c0 (tShell): Reading 66 bytes of service cal data from EEPROM into 0x2d1a3000x16975c0 (tShell): nvMem_read succeededcalConStatus = 0x1341eec: value = 0 = 0x0updateTrigCalvalue = 0 = 0x0MathMeasCreateTheMathandMeasurementLibrariesvalue = 47120704 = 0x2cf0140initAcqMapper0x16975c0 (tShell): initAcqMapper: Entervalue = 0 = 0x0trigMapInitvalue = 0 = 0x0dsyMapInitvalue = 0 = 0x0mathMapperInitvalue = 0 = 0x0utilMapInitvalue = 47118048 = 0x2cef6e0TmgrHookupvalue = 0 = 0x0PhxProxyHookupvalue = 0 = 0x0hookupAcqMappervalue = 20164752 = 0x133b090 = AcqMapperRtlDataListMathMeasMapHookupvalue = 23687912 = 0x16972e8dsyMapHookupvalue = 23688016 = 0x1697350utilMapHookupvalue = 23688048 = 0x1697370rtlHookupvalue = 0 = 0x0horizMapHookupvalue = 23688008 = 0x1697348fastFrameMapHookupvalue = 23688032 = 0x1697360trigMapHookupvalue = 23688040 = 0x1697368vertMapHookupvalue = 23688032 = 0x1697360spcMapHookupvalue = 23688032 = 0x1697360autosetMapHookupvalue = 23688072 = 0x1697388timeSyncMapHookupvalue = 23688064 = 0x1697380auxTrigMapHookupvalue = 23688048 = 0x1697370dpoMapHookupvalue = 23688040 = 0x1697368TmgrStartupvalue = 46244176 = 0x2c1a150PhxProxyStartupvalue = 46193632 = 0x2c0dbe0taskDelay(2)value = 0 = 0x0gpibHwInitCvalue = 0 = 0x0gpibTaskSpawnvalue = 45993600 = 0x2bdce80gpibIoInit "/dbios/DBIO005","/dbios/DBIO006"value = 45515104 = 0x2b68160enablePowerupDiags = 0enablePowerupDiags = 0x1311330: value = 0 = 0x0runPowerupDiagsdonedipSwitch = 0x0, enablePowerupDiags = 0, puMode=0CalDiagPowerUpDiagsEnabled = 0!! SKIPPING POWERUP DIAGNOSTICS !!0x2bc0c40 (digHFTask): >> Setting PLL to 1.25e+09 Hz.0x2bc0c40 (digHFTask): >> Setting PLL to 1.25e+09 Hz.0x2bc0c40 (digHFTask): >> Setting PLL to 1.25e+09 Hz.value = 17780784 = 0x10f5030 = SoftSwitchesRegisterTable + 0x48rtlStartupvalue = 0 = 0x0tsCompvalue = 0 = 0x0################### topScript ends ###############################Done executing startup script c:\vxBoot\topScript.hwKERNEL: RUNNING TIME SLICED AT 10 TICKS PER SLICE!Then I executed SPC and obtained the following information:-> 0x2c50a90 (CalWatch): Temperature transition into SPC-supporting range.0x2ac28e8 (phaseCalAfterDiags): >> Setting PLL to 1.25e+09 Hz.0x2b158d0 (SPC task): >> Ch3 sanity check gain error at 1010.00 mV/div : 1.000x2b158d0 (SPC task): >> Ch3 sanity check gain error at 2000.00 mV/div : 1.02I performed SPC several times in a row and obtained the same results.I tested the output waveforms of all channels, and only the baseline of CH3 channel was offset by about 25MV, but all operations and measurements were normal.Is there anything I can do to solve this problem? Can someone with repair experience provide assistance? If anyone could help me, I would be extremely grateful!

author: squadchannel
author_rank: Frequent Contributor
timestamp: December 11, 2024, 09:20:00 am
content: gain error is 99% a bad contact in the front end attenuator relay.(guess. guess......)It can be repaired by replacing it.my repair log:Code:SPC実行時のログ0x2ad16b0 (Ch1 Balance Cal): >> Error at step ChanCalPart1.40014: FineOffset DAC Nonconvergent during Scaling measurement of Fine DAC0x2ae3df0 (Digitizer 1 Cal): >> Error at step A2DBiasPass1.442: Nonconvergent0x2b027b0 (SPC task): >> Ch1 sanity check gain error at→アッテネータ内のリレー故障H2462J(TDS7xxx? TDS5xx、6xx、7xxのアッテネータと同等。)1ch分BOMDS1E-M-DC12V x4TN2-12V-H11 x1(廃盤のため、AGN200S12に交換。問題なし。)Code:log of perform SPC0x2ad16b0 (Ch1 Balance Cal): >> Error at step ChanCalPart1.40014: FineOffset DAC Nonconvergent during Scaling measurement of Fine DAC0x2ae3df0 (Digitizer 1 Cal): >> Error at step A2DBiasPass1.442: Nonconvergent0x2b027b0 (SPC task): >> Ch1 sanity check gain error at→bad relay in attenuator units.H2462J(same attenuator unit? of TDS7xxx TDS5xx, 6xx, 7xx)BOM(single channel)DS1E-M-DC12V x4TN2-12V-H11 x1(but discotinued、replace to AGN200S12. no problem.)

author: scofun
author_rank: Newbie
timestamp: December 11, 2024, 09:30:49 am
content: Thank you for your reply!I searched the forum for information related to SPC maintenance of TDS series oscilloscopes, and it seems that this issue can be fixed by exchanging attenuator modules from other channels.Should I give it a try? Or just replace it directly? I have an old TDS784D oscilloscope, I wonder if the attenuator can be used universally?

author: squadchannel
author_rank: Frequent Contributor
timestamp: December 11, 2024, 09:34:34 am
content: Yes, to confirm that this problem is related to the attenuator, I have replaced it with a TDS754D attenuator unit and have confirmed that it also works with the TDS7104.Therefore, I assume it is the same attenuator unit.When replacing a relay, replace it carefully because ceramic circuit boards are very fragile and easily damaged.The relay was removed by cutting off the legs.Solder was used that contained silver. This is because Tek in the tube era used ceramic terminal blocks, which had to be silver-contained.In any case, it would be a good idea to replace the attenuator unit to see if the problem is caused by the attenuator.

author: scofun
author_rank: Newbie
timestamp: December 11, 2024, 02:39:51 pm
content: To my knowledge, there are different versions of attenuators used for TDS series oscilloscopes, such as H2462H, H2462J, etc., I don't know which version TDS7104 is using? Because I haven't dismantled it yet

author: charlyd
author_rank: Frequent Contributor
timestamp: February 11, 2025, 06:26:02 pm
content: Hello i saw more what needs to be looked after and the can point to your NVram replacement. your serial is restored from disk then point to not a good init after replacement or still needs to be replaced.