Electronics > Repair
Tektronix TDS754D - acquisition board test fail
<< < (5/8) > >>
Rax:
Anyway, so I'm back at the drawing board and there's just a lot of scratching my head is all.
Rax:
A couple of notes on the rework:

* I think the .3mm solder I have is indeed crap. I switched to my default .8mm good quality solder, and I had to judiciously distribute each load across a few pins. Abundant rosin helped do that relatively easily. So, my solid belief quality tools and materials is everything is reinforced.
* The TT-65 and the SOJ tip made the desolder job very enjoyable. It's not a cheap solution, but I'm certain it cut down my time on that part of the job by a sizable percentage.
Rax:
As I evaluate the next steps here, I am trying to read the entirety of the error message. I am positive I read a while back a thread where this issue was discussed - can't recall if clear directions were presented - but can't find it now for the world.

I'd appreciate pointers on how to read the entire body of the individual errors.
TERRA Operative:
Ok, all good on the soldering, sounds like you got it all sorted. :)

To get the entire error messages, you'll need to read them out via GPIB. I also have no idea why Tektronix couldn't get the text to wrap properly on the scope display... :P


Here's how to read out the errors:

To read the first line of the error log via GPIB, send the command 'errlog:first?'
To read out subsequent lines, send the command 'errlog:next?' per line in sequence.
To clear the error log, send the command 'ERR CLEAR' via GPIB.


I would suggest clearing the error log first, then reboot the scope and manually run a full self test and SPC to generate a fresh set of error logs.
Rax:

--- Quote from: TERRA Operative on May 20, 2024, 12:09:36 am ---To read the first line of the error log via GPIB, send the command 'errlog:first?'
To read out subsequent lines, send the command 'errlog:next?' per line in sequence.
To clear the error log, send the command 'ERR CLEAR' via GPIB.


I would suggest clearing the error log first, then reboot the scope and manually run a full self test and SPC to generate a fresh set of error logs.

--- End quote ---

This is great, thank you. I was able to initially read an error from the dawn of time, but as trying out different things to read the last didn't work, I resorted to what you recommended and reset the error log. Then ran diagnostics again, and got this:

"SUN MAY 19 19:11:48 2024  ERROR: diagnostic test failure, digDataFormatDiag,  ERROR!!BYTE mode, in demux 200 ,i= 7 memBaseAdr 0x7380010=  data = 800, expectedData = 5500"

Looking forward to interpretations from those with experience on this instrument - as for me, I am headed now to do some reading.
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod