$200 reward for information regarding Tek TDS5000B debug

[Jwalling]

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 time
I'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've
tried 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. For
instance, 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 with
DC 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 causing
the 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 very
difficult 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: [Select]

# 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 MODERATE
debugOn c:\debug.log|*


Contents of debugMsg.log:

Code: [Select]


***************************************

File opened:  Thu May 10 11:54:59 2007



***************************************

May 10 11:54:59 - EnablePowerupDiags = 1, puMode=1
May 10 11:54:59 - DiagPowerUpDiagsEnabled = 1
May 10 11:54:59 - Executing Powerup diags ...
May 10 11:54:59 - Test "111" - Processor-->Memory-->DRAMWalk1  started
May 10 11:54:59 -      Test execution time 0.00019583 sec
May 10 11:54:59 - Test "112" - Processor-->Memory-->DRAMCell started
May 10 11:54:59 -      Test execution time 0.0052359 sec
May 10 11:54:59 - Test "113" - Processor-->Memory-->DRAMMarch  started
May 10 11:54:59 -      Test execution time 0.0029037 sec
May 10 11:54:59 - Factory Mode Only Test "114" - Processor-->Memory-->NVRAM started
May 10 11:55:00 -      Test execution time 1.8826 sec
May 10 11:55:00 - Test "131" - Processor-->Registers-->PAI started
May 10 11:55:00 -      Test execution time 0.00029054 sec
May 10 11:55:00 - Test "211" - Display-->Register-->Display started
May 10 11:55:00 -      Test execution time 0.0034781 sec
May 10 11:55:00 - Test "311" - Acquisition-->Registers-->DAC started
May 10 11:55:01 -      Test execution time 0.99081 sec
May 10 11:55:01 - Test "312" - Acquisition-->Registers-->Demux started
May 10 11:55:01 -      Test execution time 0.0049129 sec
May 10 11:55:01 - Test "313" - Acquisition-->Registers-->Preamp started
May 10 11:55:02 -      Test execution time 0.087866 sec
May 10 11:55:02 - Test "314" - Acquisition-->Registers-->PLL started
May 10 11:55:02 - Reference Locked.
May 10 11:55:02 -      Test execution time 0.059737 sec
May 10 11:55:02 - Test "315" - Acquisition-->Registers-->ADC started
May 10 11:55:02 -      Test execution time 0.01444 sec
May 10 11:55:02 - Test "321" - Acquisition-->Memory-->MemData started
May 10 11:55:02 -      Test execution time 0.059437 sec
May 10 11:55:02 - Test "322" - Acquisition-->Memory-->MemAddr started
May 10 11:55:02 -      Test execution time 0.023141 sec
May 10 11:55:02 - Test "323" - Acquisition-->Memory-->DataFormat started
May 10 11:55:02 -      Test execution time 0.0011619 sec
May 10 11:55:02 - Factory Mode Only Test "324" - Acquisition-->Memory-->MemSpeed started
May 10 11:55:24 -      Test execution time 22.092 sec
May 10 11:55:24 - Test "331" - Acquisition-->Acq Modes-->SubSample started
May 10 11:55:24 -      Test execution time 0.0073277 sec
May 10 11:55:24 - Test "332" - Acquisition-->Acq Modes-->PeakDetect started
May 10 11:55:24 -      Test execution time 0.0080088 sec
May 10 11:55:24 - Test "333" - Acquisition-->Acq Modes-->HiRes started
May 10 11:55:24 -      Test execution time 0.0075876 sec
May 10 11:55:24 - Test "341" - Acquisition-->Interrupt-->Bit Tests  started
May 10 11:55:24 -      Test execution time 0.0028962 sec
May 10 11:55:24 - Test "371" - Acquisition-->Vertical-->50OhmOvld started
May 10 11:55:24 -      Test execution time 0.38756 sec
May 10 11:55:24 - Test "372" - Acquisition-->Vertical-->ADC Connects  started
May 10 11:55:29 -      Test execution time 4.3639 sec
May 10 11:55:29 - Test "381" - Acquisition-->PLL-->Clock Freq started
May 10 11:55:29 -      Test execution time 0.0058706 sec
May 10 11:55:29 - Test "411" - Trigger-->Registers-->GTL started
May 10 11:55:29 -      Test execution time 0.0022995 sec
May 10 11:55:29 - Test "412" - Trigger-->Registers-->HITL started
May 10 11:55:29 -      Test execution time 0.0019983 sec
May 10 11:55:29 - Test "413" - Trigger-->Registers-->ExtTvTrg started
May 10 11:55:29 -      Test execution time 0.0014203 sec
May 10 11:55:29 - Test "421" - Trigger-->TrgLvlComp-->LogicComp1  started
May 10 11:55:29 -      Test execution time 0.074107 sec
May 10 11:55:29 - Test "422" - Trigger-->TrgLvlComp-->LogicComp2  started
May 10 11:55:29 -      Test execution time 0.025555 sec
May 10 11:55:29 - Test "423" - Trigger-->TrgLvlComp-->LogicComp3  started
May 10 11:55:29 -      Test execution time 0.025423 sec
May 10 11:55:29 - Test "424" - Trigger-->TrgLvlComp-->LogicComp4  started
May 10 11:55:29 -      Test execution time 0.025503 sec
May 10 11:55:29 - Test "431" - Trigger-->GTL-->TICounters started
May 10 11:55:29 -      Test execution time 0.0097596 sec
May 10 11:55:29 - Test "432" - Trigger-->GTL-->GTLBigCntrs  started
May 10 11:55:29 -      Test execution time 0.010079 sec
May 10 11:55:29 - Test "441" - Trigger-->HITL-->Ch1Edge started
May 10 11:55:29 -      Test execution time 0.013537 sec
May 10 11:55:29 - Test "442" - Trigger-->HITL-->AfterDBE started
May 10 11:55:29 -      Test execution time 0.073323 sec
May 10 11:55:29 - Test "443" - Trigger-->HITL-->AfterDBT started
May 10 11:55:29 -      Test execution time 0.11942 sec
May 10 11:55:29 - Test "444" - Trigger-->HITL-->Slewrate started
May 10 11:55:29 -      Test execution time 0.030582 sec
May 10 11:55:29 - Test "445" - Trigger-->HITL-->LineTrig started
May 10 11:55:29 -      Test execution time 0.076672 sec
May 10 11:55:29 - Test "446" - Trigger-->HITL-->HITL started
May 10 11:55:29 -      Test execution time 0.013548 sec
May 10 11:55:29 - Test "451" - Trigger-->Extended-->Glitch started
May 10 11:55:29 -      Test execution time 0.020193 sec
May 10 11:55:29 - Test "452" - Trigger-->Extended-->PulseWidth started
May 10 11:55:30 -      Test execution time 0.21821 sec
May 10 11:55:30 - Test "461" - Trigger-->Nibble-->Bus started
May 10 11:55:30 -      Test execution time 0.21462 sec
May 10 11:55:30 - Test "511" - Misc-->GPIB-->Interface started
May 10 11:55:30 -      Test execution time 0.029952 sec
May 10 11:55:31 - POWERUP DIAGNOSTICS RESULTS:  ALL TESTS PASSED
May 10 11:55:31 - Powerup diags finished in 32.404 sec
May 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=0x28000300
May 10 11:55:31 - gpibAddSetToBatch: No command processors in registry! ParamId=0x28000306
May 10 11:55:31 - GpibStartRunning() COMPLETE
May 10 11:55:31 - CALLING AppsInterfaceStartup()
May 10 11:55:32 - CPipeFile::CPipeFile(ControlPipe1): Error duplicating source process handle for read pipe: GetLastError=0
May 10 11:55:32 - CPipeFile::CPipeFile(ResultsPipe1): Error duplicating source process handle for read pipe: GetLastError=0
May 10 11:55:32 - AppsInterfaceStartup() COMPLETE
May 10 11:55:32 - Init probe change stuff.
================================================================
SYSTEM INFORMATION:
    Model: TDS5104B
    Serial No: B022424
    Scope.exe Version: 2.0.11; PRODUCTION
    Operating System Info:
        Windows 2000, build #2195
        Other info: Service Pack 4
    DEBUG OUTPUT CHANNELS:
        TRACE: ON
        MFG PORT: ON
        TCPIP: OFF
        FILE: ON; C:\debugMsg.log (overwrite open mode)
              Size Limit: 1024000 bytes
    GPIB: Address: 1; DEVICE MODE: On-Line
    Event Log: 25 entries
    Diagnostics:
        Powerup mode: FACTORY
        Powerups Count: 33
    Options:
        App 67 Avail
         not installed.
    Hardware Configuration:
        CPU Timer Interval: 1000
        ACQ NVMEM: 2000
        ACQ MEM: 8388608
        CPU MEM: 8388608
        DSY ASIC REV: 0
        ACQ PROC VER: 11
        ACQ BRD ID: 13
        ACQ BW: 1000
        ACQ SAMPLE RATE: 2500
        WFM MEM: 488636416
        DEMUX ASIC REV: 439b
        PAI ASIC REV: 5.10
        Communications Capability:
            Comm Option Enabled: 0
            Serial Trigger:      0
            Clock Recovery:      0
            Optical 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 step
May 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 step
May 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 step
May 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 step
May 10 11:57:30 - dsyTXPerformTile: BlitEvent timeout or error
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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 step
May 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:51
May 10 12:06:59 - SHOWTIME: SPC step : Signal test 00:00:08
May 10 12:06:59 - SHOWTIME: SPC step : Et Cal 00:00:00
May 10 12:07:10 - SHOWTIME: SPC step : A2D offset and gain 00:00:11
May 10 12:07:35 - SHOWTIME: SPC step : A2D interleave 00:00:25
May 10 12:07:45 - SHOWTIME: SPC step : A2D pass two offset and gain 00:00:10
May 10 12:07:56 - SHOWTIME: SPC step : cfRatio computation 00:00:11
May 10 12:08:51 - SHOWTIME: SPC step : M859 offset 00:00:55
May 10 12:08:59 - SHOWTIME: SPC step : M859 stepgain 00:00:08
May 10 12:09:12 - <IOP>  Fan Control Initialization Complete.
May 10 12:09:12 - <IOP>  FAN CALIBRATION COMPLETE.  Acq Sensor offset = 139.45
May 10 12:09:22 - SHOWTIME: SPC step : M859 coarse/fine offset DACs 00:00:23
May 10 12:10:22 - SHOWTIME: SPC step : M859 varigain DAC 00:01:00
May 10 12:10:23 - SHOWTIME: SPC step : M859 Bandwidth limit gain 00:00:01
May 10 12:10:46 - SHOWTIME: SPC step : M859 Ground offset 00:00:23
May 10 12:10:46 - SHOWTIME: SPC step : Get Temperature 00:00:00
May 10 12:11:20 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:34
May 10 12:11:40 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:20
May 10 12:12:30 - SHOWTIME: SPC step : Hfd117 offset 00:00:50
May 10 12:12:34 - SHOWTIME: SPC step : Hfd117 stepgain 00:00:04
May 10 12:13:35 - SHOWTIME: SPC step : Hfd117 coarse/fine offset DACs 00:01:01
May 10 12:16:06 - SHOWTIME: SPC step : Hfd117 varigain offset correction 00:02:31
May 10 12:16:54 - SHOWTIME: SPC step : Trigger Hysteresis 00:00:48
May 10 12:17:58 - SHOWTIME: SPC step : Trigger gain and offset 00:01:04
May 10 12:18:17 - SHOWTIME: SPC step : Trigger TQ 00:00:19
May 10 12:18:45 - SHOWTIME: SPC step : Trigger Sliver 00:00:28
May 10 12:18:59 - SHOWTIME: SPC step : overload DAC 00:00:14
May 10 12:18:59 - SHOWTIME: SPC: finished  00:00:00
May 10 12:18:59 - total time 00:12:08
May 10 12:18:59 - Apply External ground or open all channels for the next step
May 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 step
May 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-011
May 10 12:21:16 - deSkew 1 is for channel 0 measured for mode 1
May 10 12:21:17 - deSkew -1.649e-010
May 10 12:21:17 - deSkew 2 is for channel 1 measured for mode 1
May 10 12:21:19 - deSkew -1.28679e-010
May 10 12:21:19 - deSkew 3 is for channel 2 measured for mode 2
May 10 12:21:21 - deSkew -1.27828e-010
May 10 12:21:21 - deSkew 4 is for channel 3 measured for mode 3
May 10 12:21:23 - deSkew -1.08252e-010
May 10 12:21:23 - deSkew 5 is for channel 1 measured for mode 4
May 10 12:21:25 - deSkew -1.29901e-010
May 10 12:21:25 - deSkew 6 is for channel 2 measured for mode 4
May 10 12:21:27 - deSkew -1.26912e-010
May 10 12:21:27 - deSkew 7 is for channel 2 measured for mode 5
May 10 12:21:28 - deSkew -1.29958e-010
May 10 12:21:28 - deSkew 8 is for channel 3 measured for mode 5
May 10 12:21:30 - deSkew -1.11788e-010
May 10 12:21:30 - deSkew 9 is for channel 3 measured for mode 6
May 10 12:21:32 - deSkew -1.09281e-010
May 10 12:21:32 - deSkew 10 is for channel 0 measured for mode 7
May 10 12:21:37 - deSkew -2.59846e-010
May 10 12:21:37 - deSkew 11 is for channel 1 measured for mode 8
May 10 12:21:41 - deSkew -2.26499e-010
May 10 12:21:41 - deSkew 12 is for channel 2 measured for mode 9
May 10 12:21:45 - deSkew -2.24596e-010
May 10 12:21:45 - deSkew 13 is for channel 3 measured for mode 10
May 10 12:21:50 - deSkew -2.09098e-010
May 10 12:21:50 - deSkew 14 is for channel 0 measured for mode 11
May 10 12:22:02 - deSkew -3.5314e-010
May 10 12:22:02 - deSkew 15 is for channel 1 measured for mode 12
May 10 12:22:15 - deSkew -3.2856e-010
May 10 12:22:15 - deSkew 16 is for channel 2 measured for mode 13
May 10 12:22:27 - deSkew -3.1808e-010
May 10 12:22:28 - deSkew 17 is for channel 3 measured for mode 14
May 10 12:22:40 - deSkew -3.1968e-010
May 10 12:22:45 - Trigger deSkew base channel 1 is -2.57297e-010
May 10 12:22:49 - Trigger deSkew channel 1 is 3.09697e-011
May 10 12:22:54 - Trigger deSkew channel 2 is 9.55612e-011
May 10 12:22:58 - Trigger deSkew channel 3 is -1.53785e-011
May 10 12:22:58 - Trigger deSkew Aux in is -3e-010
May 10 12:23:08 - SHOWTIME: SPC: starting 12:23:08
May 10 12:23:16 - SHOWTIME: SPC step : Signal test 00:00:08
May 10 12:23:16 - SHOWTIME: SPC step : Et Cal 00:00:00
May 10 12:23:27 - SHOWTIME: SPC step : A2D offset and gain 00:00:11
May 10 12:23:52 - SHOWTIME: SPC step : A2D interleave 00:00:25
May 10 12:24:02 - SHOWTIME: SPC step : A2D pass two offset and gain 00:00:10
May 10 12:24:13 - SHOWTIME: SPC step : cfRatio computation 00:00:11
May 10 12:25:09 - SHOWTIME: SPC step : M859 offset 00:00:56
May 10 12:25:17 - SHOWTIME: SPC step : M859 stepgain 00:00:08
May 10 12:25:38 - SHOWTIME: SPC step : M859 coarse/fine offset DACs 00:00:21
May 10 12:26:38 - SHOWTIME: SPC step : M859 varigain DAC 00:01:00
May 10 12:26:39 - SHOWTIME: SPC step : M859 Bandwidth limit gain 00:00:01
May 10 12:27:02 - SHOWTIME: SPC step : M859 Ground offset 00:00:23
May 10 12:27:02 - SHOWTIME: SPC step : Get Temperature 00:00:00
May 10 12:27:36 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:34
May 10 12:27:56 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:20
May 10 12:28:46 - SHOWTIME: SPC step : Hfd117 offset 00:00:50
May 10 12:28:50 - SHOWTIME: SPC step : Hfd117 stepgain 00:00:04
May 10 12:29:51 - SHOWTIME: SPC step : Hfd117 coarse/fine offset DACs 00:01:01
May 10 12:32:23 - SHOWTIME: SPC step : Hfd117 varigain offset correction 00:02:32
May 10 12:33:10 - SHOWTIME: SPC step : Trigger Hysteresis 00:00:47
May 10 12:34:15 - SHOWTIME: SPC step : Trigger gain and offset 00:01:05
May 10 12:34:32 - SHOWTIME: SPC step : Trigger TQ 00:00:17
May 10 12:34:56 - SHOWTIME: SPC step : Trigger Sliver 00:00:24
May 10 12:35:10 - SHOWTIME: SPC step : overload DAC 00:00:14
May 10 12:35:10 - SHOWTIME: SPC: finished  00:00:00
May 10 12:35:10 - total time 00:12:02
May 10 12:47:56 - deUpdatePlaneState: TIMEOUT WAITING FOR RASTER DONE
May 10 12:57:52 - deUpdatePlaneState: TIMEOUT WAITING FOR RASTER DONE
May 10 13:37:20 - deUpdatePlaneState: TIMEOUT WAITING FOR RASTER DONE
May 10 14:21:58 - THREAD ID: 0X00000410  mathMainThread - Started in .\sdt\mathexecutor.cpp at 1379.
May 10 14:24:18 - Exiting tWinMain
May 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() COMPLETE
May 10 14:24:19 - CALLING AppsInterfaceShutdown()
May 10 14:24:19 - AppsInterfaceShutdown() COMPLETE
May 10 14:24:19 - Calling AutosetRtlShutdown()
May 10 14:24:19 - AutosetRtlShutdown() COMPLETE
May 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 = 10004
May 10 14:24:21 - tcpipHandleConnections(): Exiting connection thread...


[darkstar49]

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 like

debugLevel SEVERE
debugOn *

[Jwalling]

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 like

debugLevel SEVERE
debugOn *

Nope, that didn't work, thanks.

[Jwalling]

I've posted the 2 executables here: http://global-files.net/hesst3

[abyrvalg]

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

[abyrvalg]

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 logging

Edit: looks like there is a "help" cmd that dumps all commands. "help somecmd" should work too, showing detailed cmd help.

[Jwalling]

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

That 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 with
clear text username and password

Server allows NTLM authentication only
Server has closed connection

[Jwalling]

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

This 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.

[abyrvalg]

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 global
debugLevel critical

[Jwalling]

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 global
debugLevel critical

No difference, only the diagnostics are logged, not SPC failures. Thanks!

[abyrvalg]

Could you tell the exact spelling of that error message? I'll try to look for it's source and inspect the surroundings.

[Jwalling]

Could you tell the exact spelling of that error message? I'll try to look for it's source and inspect the surroundings.

Here's two screen captures.

[Jwalling]

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.

[smaultre]

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.

[Jwalling]

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.

I'm increasing the reward to $200.

[yearz]

 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.log

here is tds5054 with firmware ver 1.1.2 debug message

Code: [Select]



***************************************

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 processor
Jan 08 15:37:46 - CExeModule::Unlock: 4
Jan 08 15:37:46 - CExeModule::Unlock: 5
Jan 08 15:37:46 - CExeModule::Unlock: 4
Jan 08 15:37:46 - CExeModule::Unlock: 3
Jan 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 = BUS
Jan 08 15:37:46 - Item 1:
Jan 08 15:37:46 - Sharable.:
Jan 08 15:37:46 - ID 1 = INTERRUPT
Jan 08 15:37:46 - IRQ = 11
Jan 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 = MEMORY
Jan 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 = MEMORY
Jan 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 Interface
Jan 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 = BUS
Jan 08 15:37:46 - Item 1:
Jan 08 15:37:46 - Sharable.:
Jan 08 15:37:46 - ID 1 = INTERRUPT
Jan 08 15:37:46 - IRQ = 11
Jan 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 = MEMORY
Jan 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) 2002
Jan 08 15:37:46 - Querying board id.
Jan 08 15:37:46 - &theGTL.regs[GTL_BRDID_KEY] = 0X006AE4DC
Jan 08 15:37:46 - Board id from gtl = 0x0000000b
Jan 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 = 0x80026844
Jan 08 15:37:47 - Fan control constants are up to date.
Jan 08 15:37:48 - ----------------------------------------------
Jan 08 15:37:48 - IOP Init State: 9500
Jan 08 15:37:48 - IOP Init State: 1000
Jan 08 15:37:48 - IOP Init State: 1800
Jan 08 15:37:49 - IOP Init State: 1900
Jan 08 15:37:49 - IOP Init State: 2300
Jan 08 15:37:49 - IOP Init State: 9001
Jan 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:49
Jan 08 15:37:57 - IOP diagnostics finished 15:37:57 - 15:37:49 = 00:08
Jan 08 15:37:59 - <IOP>  rebootMonitorTask started.
Jan 08 15:37:59 - AVR communications OK.
Jan 08 15:37:59 - Initializing: ATOD
Jan 08 15:37:59 - Initializing: DAC
Jan 08 15:37:59 - Initializing: DEMUX
Jan 08 15:37:59 - Initializing: Dsy338
Jan 08 15:37:59 - Initializing: ExtTvTrigControl
Jan 08 15:37:59 - Initializing: GTL
Jan 08 15:37:59 - Initializing: HITL
Jan 08 15:37:59 - Initializing: PLL
Jan 08 15:37:59 - Initializing: PaiBase
Jan 08 15:37:59 - Initializing: Preamp
Jan 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 OVERRIDE

Jan 08 15:38:02 - tcpipHandleConnections(): Thread ID 0xFFFA95C3 initialized to handle incoming connections
Jan 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() COMPLETE
Jan 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 NVram
Jan 08 15:38:02 - EnablePowerupDiags = 1, puMode=0
Jan 08 15:38:02 - DiagPowerUpDiagsEnabled = 1
Jan 08 15:38:02 - Executing Powerup diags ...
Jan 08 15:38:02 - Test "111" - Processor-->Memory-->DRAMWalk1
Jan 08 15:38:02 - Test "112" - Processor-->Memory-->DRAMCell
Jan 08 15:38:02 - Test "113" - Processor-->Memory-->DRAMMarch
Jan 08 15:38:02 - Test "131" - Processor-->Registers-->PAI
Jan 08 15:38:02 - Test "211" - Display-->Register-->Display
Jan 08 15:38:02 - Test "311" - Acquisition-->Registers-->DAC
Jan 08 15:38:03 - Test "312" - Acquisition-->Registers-->Demux
Jan 08 15:38:03 - Test "313" - Acquisition-->Registers-->Preamp
Jan 08 15:38:04 - Test "314" - Acquisition-->Registers-->PLL
Jan 08 15:38:04 - Test "315" - Acquisition-->Registers-->ADC
Jan 08 15:38:04 - Test "321" - Acquisition-->Memory-->MemData
Jan 08 15:38:04 - Test "322" - Acquisition-->Memory-->MemAddr
Jan 08 15:38:04 - Test "323" - Acquisition-->Memory-->DataFormat
Jan 08 15:38:04 - Test "331" - Acquisition-->Acq Modes-->SubSample
Jan 08 15:38:04 - Test "332" - Acquisition-->Acq Modes-->PeakDetect
Jan 08 15:38:04 - Test "333" - Acquisition-->Acq Modes-->HiRes
Jan 08 15:38:04 - Test "341" - Acquisition-->Interrupt-->Bit Tests
Jan 08 15:38:04 - Test "371" - Acquisition-->Vertical-->50OhmOvld
Jan 08 15:38:04 - Test "372" - Acquisition-->Vertical-->ADC Connects
Jan 08 15:38:04 - Reference Locked.
Jan 08 15:38:05 - Test "381" - Acquisition-->PLL-->Clock Freq
Jan 08 15:38:05 - Test "411" - Trigger-->Registers-->GTL
Jan 08 15:38:05 - Test "412" - Trigger-->Registers-->HITL
Jan 08 15:38:05 - Test "413" - Trigger-->Registers-->ExtTvTrg
Jan 08 15:38:05 - Test "421" - Trigger-->TrgLvlComp-->LogicComp1
Jan 08 15:38:05 - Test "422" - Trigger-->TrgLvlComp-->LogicComp2
Jan 08 15:38:05 - Test "423" - Trigger-->TrgLvlComp-->LogicComp3
Jan 08 15:38:05 - Test "424" - Trigger-->TrgLvlComp-->LogicComp4
Jan 08 15:38:05 - Test "431" - Trigger-->GTL-->TICounters
Jan 08 15:38:05 - Test "432" - Trigger-->GTL-->GTLBigCntrs
Jan 08 15:38:05 - Test "441" - Trigger-->HITL-->Ch1Edge
Jan 08 15:38:05 - Test "442" - Trigger-->HITL-->AfterDBE
Jan 08 15:38:05 - Test "443" - Trigger-->HITL-->AfterDBT
Jan 08 15:38:05 - Test "444" - Trigger-->HITL-->Slewrate
Jan 08 15:38:05 - Test "445" - Trigger-->HITL-->LineTrig
Jan 08 15:38:05 - Test "446" - Trigger-->HITL-->HITL
Jan 08 15:38:05 - Test "451" - Trigger-->Extended-->Glitch
Jan 08 15:38:05 - Test "452" - Trigger-->Extended-->PulseWidth
Jan 08 15:38:06 - Test "461" - Trigger-->Nibble-->Bus
Jan 08 15:38:06 - Test "511" - Misc-->GPIB-->Interface
Jan 08 15:38:07 - HF step remainder = 145<145<145ps, 0/1 fail/pass ratio
Jan 08 15:38:07 - POWERUP DIAGNOSTICS RESULTS:  ALL TESTS PASSED
Jan 08 15:38:07 - Powerup diags finished in 00:05 minutes:seconds
Jan 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: TDS5054
    Serial No: B020432
    Scope.exe Version: 1.1.2; PRODUCTION
    Operating System Info:
        Windows Me, build #3000
        Other info: 
    DEBUG OUTPUT CHANNELS:
        TRACE: ON
        MFG PORT: ON
        TCPIP: OFF
        FILE: ON; C:\debugMsg.log (overwrite open mode)
              Size Limit: 1024000 bytes
    GPIB: Address: 3;  (On-Line)
    Event Log: 107 entries
    Diagnostics:
        Powerup mode: USER
        Powerups Count: 491
    Options:
        2A:Advanced Analysis Software
       
    Hardware Configuration:
        CPU Timer Interval: 1000
        ACQ NVMEM: 2000
        ACQ MEM: 4194304
        CPU MEM: 8388608
        DSY ASIC REV: 0
        ACQ PROC VER: 11
        ACQ BRD ID: 13
        ACQ BW: 500
        ACQ SAMPLE RATE: 2500
        WFM MEM: 85983232
        DEMUX ASIC REV: 17307
        PAI ASIC REV: 3.25
        Communications Capability:
            Comm Option Enabled: 0
            Serial Trigger:      0
            Clock Recovery:      0
            Optical 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-->DRAMWalk1
Jan 08 15:38:25 - Test "112" - Processor-->Memory-->DRAMCell
Jan 08 15:38:25 - Test "113" - Processor-->Memory-->DRAMMarch
Jan 08 15:38:25 - Test "114" - Processor-->Memory-->NVRAM
Jan 08 15:38:33 - Test "121" - Processor-->PCI Bus-->Scan Test
Jan 08 15:38:33 - Test "131" - Processor-->Registers-->PAI
Jan 08 15:38:33 - Test "211" - Display-->Register-->Display
Jan 08 15:38:33 - Test "311" - Acquisition-->Registers-->DAC
Jan 08 15:38:34 - Test "312" - Acquisition-->Registers-->Demux
Jan 08 15:38:34 - Test "313" - Acquisition-->Registers-->Preamp
Jan 08 15:38:34 - Test "314" - Acquisition-->Registers-->PLL
Jan 08 15:38:34 - Test "315" - Acquisition-->Registers-->ADC
Jan 08 15:38:34 - Test "321" - Acquisition-->Memory-->MemData
Jan 08 15:38:34 - Test "322" - Acquisition-->Memory-->MemAddr
Jan 08 15:38:34 - Test "323" - Acquisition-->Memory-->DataFormat
Jan 08 15:38:34 - Test "324" - Acquisition-->Memory-->MemSpeed
Jan 08 15:38:47 - Test "331" - Acquisition-->Acq Modes-->SubSample
Jan 08 15:38:47 - Test "332" - Acquisition-->Acq Modes-->PeakDetect
Jan 08 15:38:47 - Test "333" - Acquisition-->Acq Modes-->HiRes
Jan 08 15:38:47 - Test "341" - Acquisition-->Interrupt-->Bit Tests
Jan 08 15:38:47 - Test "351" - Acquisition-->HFStep-->PhaseCal
Jan 08 15:38:48 - HF step remainder = 134<134<145ps, 0/2 fail/pass ratio
Jan 08 15:38:48 - Test "361" - Acquisition-->Demuxes-->InstaVuXY
Jan 08 15:38:48 - Test "371" - Acquisition-->Vertical-->50OhmOvld
Jan 08 15:38:48 - Test "372" - Acquisition-->Vertical-->ADC Connects
Jan 08 15:38:49 - Test "381" - Acquisition-->PLL-->Clock Freq
Jan 08 15:38:49 - Test "411" - Trigger-->Registers-->GTL
Jan 08 15:38:49 - Test "412" - Trigger-->Registers-->HITL
Jan 08 15:38:49 - Test "413" - Trigger-->Registers-->ExtTvTrg
Jan 08 15:38:49 - Test "421" - Trigger-->TrgLvlComp-->LogicComp1
Jan 08 15:38:49 - Test "422" - Trigger-->TrgLvlComp-->LogicComp2
Jan 08 15:38:49 - Test "423" - Trigger-->TrgLvlComp-->LogicComp3
Jan 08 15:38:49 - Test "424" - Trigger-->TrgLvlComp-->LogicComp4
Jan 08 15:38:49 - Test "431" - Trigger-->GTL-->TICounters
Jan 08 15:38:49 - Test "432" - Trigger-->GTL-->GTLBigCntrs
Jan 08 15:38:49 - Test "441" - Trigger-->HITL-->Ch1Edge
Jan 08 15:38:49 - Test "442" - Trigger-->HITL-->AfterDBE
Jan 08 15:38:49 - Test "443" - Trigger-->HITL-->AfterDBT
Jan 08 15:38:49 - Test "444" - Trigger-->HITL-->Slewrate
Jan 08 15:38:49 - Test "445" - Trigger-->HITL-->LineTrig
Jan 08 15:38:49 - Test "446" - Trigger-->HITL-->HITL
Jan 08 15:38:49 - Test "451" - Trigger-->Extended-->Glitch
Jan 08 15:38:49 - Test "452" - Trigger-->Extended-->PulseWidth
Jan 08 15:38:49 - Test "461" - Trigger-->Nibble-->Bus
Jan 08 15:38:50 - Test "511" - Misc-->GPIB-->Interface
Jan 08 15:38:50 -        *** TEST SKIPPED ***
Jan 08 15:38:50 - DIAGNOSTIC EXECUTION finished in 00:25 minutes:seconds
Jan 08 15:38:50 - HF step remainder = 134<148<148ps, 0/3 fail/pass ratio
Jan 08 15:39:58 - SHOWTIME: SPC: starting 15:39:58
Jan 08 15:40:03 - SHOWTIME: SPC step : Signal test 00:00:05
Jan 08 15:40:04 - SHOWTIME: SPC step : Et Cal 00:00:01
Jan 08 15:40:11 - SHOWTIME: SPC step : A2D offset and gain 00:00:07
Jan 08 15:41:00 - SHOWTIME: SPC step : A2D interleave 00:00:49
Jan 08 15:41:07 - SHOWTIME: SPC step : A2D pass two offset and gain 00:00:07
Jan 08 15:41:16 - SHOWTIME: SPC step : cfRatio computation 00:00:09
Jan 08 15:41:52 - SHOWTIME: SPC step : M859 offset 00:00:36
Jan 08 15:41:59 - SHOWTIME: SPC step : M859 stepgain 00:00:07
Jan 08 15:42:15 - findDacValue: failed to find good DAC value for HIGH
Jan 08 15:42:17 - SHOWTIME: SPC step : M859 coarse/fine offset DACs 00:00:18
Jan 08 15:42:56 - SHOWTIME: SPC step : M859 varigain DAC 00:00:39
Jan 08 15:42:56 - SHOWTIME: SPC step : M859 Bandwidth limit gain 00:00:00
Jan 08 15:43:17 - SHOWTIME: SPC step : M859 Ground offset 00:00:21
Jan 08 15:43:17 - SHOWTIME: SPC step : Get Temperature 00:00:00
Jan 08 15:43:17 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:00
Jan 08 15:43:17 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:00
Jan 08 15:43:17 - SHOWTIME: SPC step : Hfd117 offset 00:00:00
Jan 08 15:43:17 - SHOWTIME: SPC step : Hfd117 stepgain 00:00:00
Jan 08 15:43:17 - SHOWTIME: SPC step : Hfd117 coarse/fine offset DACs 00:00:00
Jan 08 15:43:17 - SHOWTIME: SPC step : Hfd117 varigain offset correction 00:00:00
Jan 08 15:44:02 - SHOWTIME: SPC step : Trigger Hysteresis 00:00:45
Jan 08 15:45:05 - SHOWTIME: SPC step : Trigger gain and offset 00:01:03
Jan 08 15:45:23 - SHOWTIME: SPC step : Trigger TQ 00:00:18
Jan 08 15:45:51 - SHOWTIME: SPC step : Trigger Sliver 00:00:28
Jan 08 15:45:55 - SHOWTIME: SPC step : overload DAC 00:00:04
Jan 08 15:45:55 - SHOWTIME: SPC: finished  00:00:00
Jan 08 15:45:55 - total time 00:05:57
Jan 08 15:45:56 - HF step remainder = 134<163<163ps, 0/4 fail/pass ratio
Jan 08 15:46:06 - CExeModule::Unlock: 8
Jan 08 15:46:06 - CExeModule::Unlock: 9
Jan 08 15:46:06 - CExeModule::Unlock: 8
Jan 08 15:46:06 - CExeModule::Unlock: 7
Jan 08 15:46:06 - CExeModule::Unlock: 6
Jan 08 15:46:06 - CExeModule::Unlock: 5
Jan 08 15:46:06 - CExeModule::Unlock: 4
Jan 08 15:46:06 - CExeModule::Unlock: 3
Jan 08 15:46:06 - CExeModule::Unlock: 2
Jan 08 15:46:06 - CExeModule::Unlock: 1
Jan 08 15:46:06 - CExeModule::Unlock: 0
Jan 08 15:46:06 - CComModule::Unlock() returned 0 -- Setting hEventShutdown.
Jan 08 15:46:06 - Exiting tWinMain
Jan 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() COMPLETE
Jan 08 15:46:07 - CALLING AppsInterfaceShutdown()
Jan 08 15:46:07 - AppsInterfaceShutdown() COMPLETE
Jan 08 15:46:08 - Calling AutosetRtlShutdown()
Jan 08 15:46:08 - AutosetRtlShutdown() COMPLETE
Jan 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: 1
Jan 08 15:46:13 - CExeModule::Unlock: 0
Jan 08 15:46:13 - CComModule::Unlock() returned 0 -- Setting hEventShutdown.



[Jwalling]

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.log

here is tds5054 with firmware ver 1.1.2 debug message

Hi yearz,

This didn't work on a TDS5104B with 2.0.11 firmware.
A screen capture of the registry. Thanks!

[Jwalling]

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:36
Dec 18 05:39:43 - CAL: SPC returned an error in step Signal test
Dec 18 05:39:43 - CAL: SPC failed
Dec 18 05:39:43 - HF step - goal = -7<+14/+14<+14ps min<xer_ps[0]/xer_ps[1]<max, 0/8 fail/total ratio
Dec 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:22
Dec 18 05:41:29 - CAL: SPC returned an error in step Signal test
Dec 18 05:41:29 - CAL: SPC failed
Dec 18 05:41:29 - HF step - goal = -2<+23/+39<+39ps min<xer_ps[0]/xer_ps[1]<max, 0/8 fail/total ratio
Dec 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:06
Dec 18 05:44:14 - CAL: SPC returned an error in step Signal test
Dec 18 05:44:14 - CAL: SPC failed
Dec 18 05:44:14 - HF step - goal = -11<-7/-7<+13ps min<xer_ps[0]/xer_ps[1]<max, 0/8 fail/total ratio
Dec 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:23
Dec 18 05:45:30 - CAL: SPC returned an error in step Signal test
Dec 18 05:45:30 - CAL: SPC failed
Dec 18 05:45:30 - HF step - goal = -21<-5/+18<+18ps min<xer_ps[0]/xer_ps[1]<max, 0/8 fail/total ratio
Dec 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:22
Dec 18 05:57:30 - CAL: SPC returned an error in step Signal test
Dec 18 05:57:30 - CAL: SPC failed
Dec 18 05:57:30 - HF step - goal = -18<+13/+0<+28ps min<xer_ps[0]/xer_ps[1]<max, 0/8 fail/total ratio
Dec 18 05:57:34 - <IOP>  Fan Control Initialization Complete.

EDIT: WTF didn't the programmers just spit out the failing channel?

[Jwalling]

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.log

here is tds5054 with firmware ver 1.1.2 debug message

Hi yearz,

This didn't work on a TDS5104B with 2.0.11 firmware.
A screen capture of the registry. Thanks!

I 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:

Jan 03 09:32:50 - <IOP>  Fan Control Initialization Complete.
Jan 03 10:16:36 - SHOWTIME: SPC: starting 10:16:36
Jan 03 10:16:46 - SHOWTIME: SPC step : Signal test 00:00:10
Jan 03 10:16:47 - SHOWTIME: SPC step : Et Cal 00:00:01
Jan 03 10:17:00 - SHOWTIME: SPC step : A2D offset and gain 00:00:13
Jan 03 10:17:27 - SHOWTIME: SPC step : A2D interleave 00:00:27
Jan 03 10:17:40 - SHOWTIME: SPC step : A2D pass two offset and gain 00:00:13
Jan 03 10:17:53 - SHOWTIME: SPC step : cfRatio computation 00:00:13
Jan 03 10:19:29 - SHOWTIME: SPC step : M859 offset 00:01:36
Jan 03 10:19:37 - SHOWTIME: SPC step : M859 stepgain 00:00:08
Jan 03 10:20:23 - SHOWTIME: SPC step : M859 coarse/fine offset DACs 00:00:46
Jan 03 10:21:37 - SHOWTIME: SPC step : M859 varigain DAC 00:01:14
Jan 03 10:21:38 - SHOWTIME: SPC step : M859 Bandwidth limit gain 00:00:01
Jan 03 10:22:18 - SHOWTIME: SPC step : M859 Ground offset 00:00:40
Jan 03 10:22:18 - SHOWTIME: SPC step : Get Temperature 00:00:00
Jan 03 10:22:29 - findVibnullDac: failed to find good DAC value for HIGH
Jan 03 10:22:58 - SHOWTIME: SPC step : Hfd117 Null input current 00:00:40
Jan 03 10:23:19 - SHOWTIME: SPC step : Hfd117 varigain DAC 00:00:21
Jan 03 10:24:30 - SHOWTIME: SPC step : Hfd117 offset 00:01:11
CAL: Gain error samples for hfd at 2mV : (1.560752 : -1.650075) is under 6 on c
CAL: SPC returned an error in step Hfd117 stepgain
CAL: SPC failed

Doesn't seem to really point to which channel is failing though...

[voltsandjolts]

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.

[abyrvalg]

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.

[Jwalling]

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.

Wow, I didn't see that. Good spot!
Here's the scope.exe. Thanks!

[DC1MC]

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.

I'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

[abyrvalg]

Done! It will say "is <" instead of "is under".

[tv84]

I'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.

Agree. 

But, @abyrvalg nuked this particular case.