| Electronics > Repair |
| tds5052 system error repair help |
| (1/2) > >> |
| pasta2018:
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: 4 Feb 11 09:45:55 - CExeModule::Unlock: 5 Feb 11 09:45:55 - CExeModule::Unlock: 4 Feb 11 09:45:55 - CExeModule::Unlock: 3 Feb 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 processor Feb 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 = BUS Feb 11 09:45:55 - Item 1: Feb 11 09:45:55 - Sharable.: Feb 11 09:45:55 - ID 1 = INTERRUPT Feb 11 09:45:55 - IRQ = 18 Feb 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 = MEMORY Feb 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 = MEMORY Feb 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 Interface Feb 11 09:45:55 - Opening TDS5000 PCI Aquisition Interface Feb 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: 7 Feb 11 09:45:55 - CExeModule::Unlock: 8 Feb 11 09:45:55 - CExeModule::Unlock: 7 Feb 11 09:45:55 - CExeModule::Unlock: 6 Feb 11 09:45:55 - CExeModule::Unlock: 5 Feb 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 failure Feb 11 09:50:01 - Send message to IOP called with message length that exceeds maximum allowed. Feb 11 09:50:01 - CExeModule::Unlock: 8 Feb 11 09:50:01 - CExeModule::Unlock: 7 Feb 11 09:50:01 - CExeModule::Unlock: 6 Feb 11 09:50:01 - CExeModule::Unlock: 5 Feb 11 09:50:01 - CExeModule::Unlock: 4 Feb 11 09:50:01 - CExeModule::Unlock: 3 Feb 11 09:50:01 - CExeModule::Unlock: 2 Feb 11 09:50:01 - CExeModule::Unlock: 1 Feb 11 09:50:01 - CExeModule::Unlock: 0 Feb 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 tWinMain Feb 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: 1 Feb 11 09:50:04 - CExeModule::Unlock: 0 Feb 11 09:50:04 - CComModule::Unlock() returned 0 -- Setting hEventShutdown. --- End code --- 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. |
| Jwalling:
Check in the Windows device manager that the Tektronix hardware is not in an error state. |
| pasta2018:
Yes, there is no error for all devices. |
| mikehank:
Try reseating the acq board. Be careful its kind of a pain. Make sure all the pins on the interface are not bent. |
| Wahyueko:
How to resetting Acq board? |
| Navigation |
| Message Index |
| Next page |