tds5052 system error repair help - Page 1
Forum section: electronics / repair

author: pasta2018
author_rank: Regular Contributor
timestamp: February 11, 2022, 02:18:49 am
content: Recently I have got a tds5052, after power on it display a system error and can not run the tekscope.app correctly.After reinstall the OS and drivers, there is no change.I also try the reset button on the PPC board, still the same.Then I add Dword para in the regedit, following this link：https://www.eevblog.com/forum/testgear/$200-reward-for-information-regarding-tek-tds5000b-debug/，after restart, the scope shows a runtime error that could not locate acquisition hardware.In the root disk I got a debugMsg file,the codes are as follow:Code:***************************************File opened: Fri Feb 11 09:45:55 2022***************************************Feb 11 09:45:55 -Scope.exe RELEASE build.Feb 11 09:45:55 - Initializing KrfTech WinDriver.Feb 11 09:45:55 - CExeModule::Unlock: 4Feb 11 09:45:55 - CExeModule::Unlock: 5Feb 11 09:45:55 - CExeModule::Unlock: 4Feb 11 09:45:55 - CExeModule::Unlock: 3Feb 11 09:45:55 - WinDriver open was successful.Feb 11 09:45:55 - Expected WinDriver version 505 is correct.Feb 11 09:45:55 - Opening Hounddog IO processorFeb 11 09:45:55 - One card with desired ids on bus 2 in slot 13 with function 0.Feb 11 09:45:55 - Successfully fetched PCI card information.Feb 11 09:45:55 - There are 4 items in the card information.Feb 11 09:45:55 - IOP card register was successful.Feb 11 09:45:55 - Item 0:Feb 11 09:45:55 -Sharable.:Feb 11 09:45:55 -ID 5 = BUSFeb 11 09:45:55 - Item 1:Feb 11 09:45:55 -Sharable.:Feb 11 09:45:55 -ID 1 = INTERRUPTFeb 11 09:45:55 -IRQ = 18Feb 11 09:45:55 -LEVEL SENSITIVE INTERRUPT.Feb 11 09:45:55 - Item 2:Feb 11 09:45:55 -NOT Sharable.:Feb 11 09:45:55 -ID 2 = MEMORYFeb 11 09:45:55 -Base Address = 0xf3800000.Feb 11 09:45:55 -Length = 0x00800000 (8388608) bytes.Feb 11 09:45:55 -WD_Transfer Base Address = 0xba0a0000.Feb 11 09:45:55 -Direct user memory transfer base address = 0x01cf0000.Feb 11 09:45:55 -CPU physical address = 0xf3800000.Feb 11 09:45:55 - Item 3:Feb 11 09:45:55 -NOT Sharable.:Feb 11 09:45:55 -ID 2 = MEMORYFeb 11 09:45:55 -Base Address = 0xf43e0000.Feb 11 09:45:55 -Length = 0x00020000 (131072) bytes.Feb 11 09:45:55 -WD_Transfer Base Address = 0xba080000.Feb 11 09:45:55 -Direct user memory transfer base address = 0x024f0000.Feb 11 09:45:55 -CPU physical address = 0xf43e0000.Feb 11 09:45:55 - Opening TDS5000 PCI Aquisition InterfaceFeb 11 09:45:55 - Opening TDS5000 PCI Aquisition InterfaceFeb 11 09:45:55 - D:\view_storage\TDS5000_Version_1.2.1\hounddog\Win\hardwareAccess\winDriver.cpp at 357: Could not locate acquisition hardware.Feb 11 09:45:55 - CExeModule::Unlock: 7Feb 11 09:45:55 - CExeModule::Unlock: 8Feb 11 09:45:55 - CExeModule::Unlock: 7Feb 11 09:45:55 - CExeModule::Unlock: 6Feb 11 09:45:55 - CExeModule::Unlock: 5Feb 11 09:45:56 - THREAD ID: 0X00000000 TreadFunc started here using _beginthread which does not give you a thread id.- Started in D:\view_storage\TDS5000_Version_1.2.1\hounddog\Win\scope\trmgrif.cpp at 261.Feb 11 09:45:56 - THREAD ID: 0X77E876A1 Started ThreadFunc - Started in D:\view_storage\TDS5000_Version_1.2.1\hounddog\Win\scope\trmgrif.cpp at 2228.Feb 11 09:45:56 - THREAD ID: 0X77E876A1 Started ThreadFunc - Started in D:\view_storage\TDS5000_Version_1.2.1\hounddog\Win\scope\trmgrif.cpp at 3254.Feb 11 09:50:01 - THREAD ID: 0X00000188 Monitor External Reference. - Started in D:\view_storage\TDS5000_Version_1.2.1\hounddog\Win\hardwareAccess\raxRefMonitor.cpp at 37.Feb 11 09:50:01 - Skipping Apps Interface Startup due to GPIB startup failureFeb 11 09:50:01 - Send message to IOP called with message length that exceeds maximum allowed.Feb 11 09:50:01 - CExeModule::Unlock: 8Feb 11 09:50:01 - CExeModule::Unlock: 7Feb 11 09:50:01 - CExeModule::Unlock: 6Feb 11 09:50:01 - CExeModule::Unlock: 5Feb 11 09:50:01 - CExeModule::Unlock: 4Feb 11 09:50:01 - CExeModule::Unlock: 3Feb 11 09:50:01 - CExeModule::Unlock: 2Feb 11 09:50:01 - CExeModule::Unlock: 1Feb 11 09:50:01 - CExeModule::Unlock: 0Feb 11 09:50:01 - CComModule::Unlock() returned 0 -- Setting hEventShutdown.Feb 11 09:50:02 - Send message to IOP called with message length that exceeds maximum allowed.Feb 11 09:50:02 - Got shutdown request from windows message broadcast.Feb 11 09:50:02 - Exiting tWinMainFeb 11 09:50:02 - Error attempting to force any apps to exit.Feb 11 09:50:02 -SHUTTING DOWN HOUNDDOG APPLICATION.If you don't see a shutdown complete message, something is broken!!Feb 11 09:50:02 - raxClose in progress.Feb 11 09:50:03 -Closing interrupt.Feb 11 09:50:03 -Pai nterrupt thread was not active.Feb 11 09:50:03 -Pai kernel plugin was not active.Feb 11 09:50:03 -Iop interrupt thread was not active.Feb 11 09:50:03 -Iop kernel plugin was not active.Feb 11 09:50:03 -PAI was not registered.Feb 11 09:50:03 -Unregistering IOP.Feb 11 09:50:03 -Closing WinDriver.Feb 11 09:50:03 - WINDRIVER EXIT COMPLETE.Feb 11 09:50:04 - CExeModule::Unlock: 1Feb 11 09:50:04 - CExeModule::Unlock: 0Feb 11 09:50:04 - CComModule::Unlock() returned 0 -- Setting hEventShutdown.Now I am not sure whether I have installed a right acquisition driver，My scope serial number is B04XXXX, can someone share a suitable driver for a try. And if you have any suggestion please let me know, many thanks.

author: Jwalling
author_rank: Unknown
timestamp: February 11, 2022, 10:02:30 am
content: Check in the Windows device manager that the Tektronix hardware is not in an error state.

author: pasta2018
author_rank: Regular Contributor
timestamp: February 11, 2022, 12:01:24 pm
content: Yes, there is no error for all devices.

author: mikehank
author_rank: Regular Contributor
timestamp: March 18, 2022, 03:49:49 pm
content: Try reseating the acq board. Be careful its kind of a pain. Make sure all the pins on the interface are not bent.

author: Wahyueko
author_rank: Contributor
timestamp: August 09, 2022, 09:58:16 pm
content: How to resetting Acq board?

author: coromonadalix
author_rank: Super Contributor
timestamp: August 09, 2022, 10:19:47 pm
content: not resetting, reseating sometimes means disconnecting and reconnecting connectors / plugs etc ... transfert boards bridge boards etc ... the contacts may oxydize overtime, and sometimes moving them may help ...but m not native english loll

author: charlyd
author_rank: Frequent Contributor
timestamp: January 17, 2025, 10:39:18 pm
content: This is not an hardware error this has something to do with the software i have two SSD installed in the same scope when i boot from one it all works ok , and from.the other i get this error.i struggled installing the GPIB on that one.i have a post on evvblog about this

author: coromonadalix
author_rank: Super Contributor
timestamp: January 17, 2025, 10:47:23 pm
content: any errors in windows device manager ?

author: charlyd
author_rank: Frequent Contributor
timestamp: January 20, 2025, 06:42:28 pm
content: this not a hardware error because i have exactly the same read!!https://www.eevblog.com/forum/testgear/tds7000b-instrument-id-in-windows-xp/in my case i have a working image, (installed on a clean winXP pro. on a second SSD in the same system) so i can toggle between both drives to compare. When i install exactly the same clean winXP it fails as above .... everything i read here i recognize. my unit is a VM5000 was originally installed with tds5104B w2k. so let bundle the forces.

author: charlyd
author_rank: Frequent Contributor
timestamp: January 20, 2025, 06:48:06 pm
content: ahh to answer on the post from @coromonadalix no hardware errors found in the device manager.

author: charlyd
author_rank: Frequent Contributor
timestamp: January 29, 2025, 08:37:11 pm
content: to complete my story which can be relevante for Pasta2018.i missed installing the batch files in the tektronix custom drivers folders.if you run tekscope then you get the windrv.cpp error.and upgrade "PCI standard CPU host bridge" entry with the iop.inf