Here is part 2 where I admit defeat and I don't have a next step due to lack of information. The NVRAM file is located here 1drv.ms/u/s!Amqar8_XQ9Uzj-gRW...
I cut the old leads around the chip with razor blade carefully then remove the defective SRAM chip on channel 1, almost gaved up on thay scope as well. But fixed it and desolder the leads. It works best as pretty much no risk of lifting trace. Had same issue and found a used SRAM chip that was same batch as China recycler pulls them from damaged scope and cost me 6 bucks with shipping, as wanted same SRAM, so no timing issues and it worked, no more errors and finally pass self hardware test. Just now have to resolve SPC issue, which is relay as measured over 1 ohm. But channel does work fine otherwise. I used a Chinese gq 4×4 programmer to program dallas SRAM .
If you lift a pad while soldering and there's a hole next to it, you can place some new copper down to replace it. Gently scrape the hole conformal coating off, tin it then place the new run/pad over the hole for fit. Drill a hole in the new run/pad then run a small copper wire through both. Solder them together, let cool then use some PCB run glue and glue the new run/pad down and clamp it. After the glue cures reinstall the component and your board is repaired. I do repairs like this for a living as an electronics technician repairing Aircraft Test Sets. It's funny I just repaired a board with the same problem last week and thought I should do a video on this and post it. OOPs the customer was in a hurry so I didn't do it, bummer. I have some videos on how to repair badly burned boards with pads and eyelets ripped out, but I haven't finished editing them for posting. Cleaning your board should be done with an acid brush cut down to about a 1/4". Wire brushes tend to remove the conformal protective coating. I love KemTeks too. As far as the NAVRAM goes, Wow, scared me when you ran the test and it wiped your NAVRAM chip. You were a lot more calm than I would have been. Good thing you had already read and saved it. It was nice to see that it did write it back to the chip, PHEW that was a close one eh? I need to do this with my scopes for protection, as I know the batteries will die.
Thanks - It was a tad harrowing - Should really have read the manual on that one. I'd love to see a good video on repairing a lifted pad on a simple board and a multi-layer one. Let me know if you do post one.
Back for a 2nd suck of the sav.. Couldn't resist and (just) picked up the same model. You must have had a positive impact or me or I'm a glutton for abuse. It's like I know what I'm up against but then think... I just keep doubling down until I win my self respect back 😁 Cheers!
hello i have this same TDS754D scope with this error nvLibrariansDiag ............... ***FAIL*** ..error details: ERRORID: 163 diagnostic test failure nvLibrariansDiag Libs with crcc failures: ExtConst ERRORID: 358 nv storage too small more bytes requested than availabledo you have any idea? i change both chips NVRAM and timekeeper on the processor board.maybe we can get in touch to work things out?
Unfortunately I don't have any ideas - You might want to try the Tek Forums (forum.tek.com/) - I ended up selling the unit and the person that I sold it to reflowed the acquisition chips and that seemed to solve the problem.
Thanks for letting me know - I finally sold the unit as I didn't really need it - The person I sold it to reflowed the acquisition ICs and that seemed to address the issue.
It was InTeReStiNg. Thank you for the work, insights, and sacrifices. Cheers
I cut the old leads around the chip with razor blade carefully then remove the defective SRAM chip on channel 1, almost gaved up on thay scope as well. But fixed it and desolder the leads. It works best as pretty much no risk of lifting trace. Had same issue and found a used SRAM chip that was same batch as China recycler pulls them from damaged scope and cost me 6 bucks with shipping, as wanted same SRAM, so no timing issues and it worked, no more errors and finally pass self hardware test. Just now have to resolve SPC issue, which is relay as measured over 1 ohm. But channel does work fine otherwise. I used a Chinese gq 4×4 programmer to program dallas SRAM .
Thanks - Interesting on the timing, that didn't occur to me.
If you lift a pad while soldering and there's a hole next to it, you can place some new copper down to replace it. Gently scrape the hole conformal coating off, tin it then place the new run/pad over the hole for fit. Drill a hole in the new run/pad then run a small copper wire through both. Solder them together, let cool then use some PCB run glue and glue the new run/pad down and clamp it. After the glue cures reinstall the component and your board is repaired. I do repairs like this for a living as an electronics technician repairing Aircraft Test Sets. It's funny I just repaired a board with the same problem last week and thought I should do a video on this and post it. OOPs the customer was in a hurry so I didn't do it, bummer. I have some videos on how to repair badly burned boards with pads and eyelets ripped out, but I haven't finished editing them for posting. Cleaning your board should be done with an acid brush cut down to about a 1/4". Wire brushes tend to remove the conformal protective coating. I love KemTeks too. As far as the NAVRAM goes, Wow, scared me when you ran the test and it wiped your NAVRAM chip. You were a lot more calm than I would have been. Good thing you had already read and saved it. It was nice to see that it did write it back to the chip, PHEW that was a close one eh? I need to do this with my scopes for protection, as I know the batteries will die.
Thanks - It was a tad harrowing - Should really have read the manual on that one.
I'd love to see a good video on repairing a lifted pad on a simple board and a multi-layer one. Let me know if you do post one.
How did you trace the bits in the error message to these two memory chips?
From memory I got the information from the Tek forums. They've moved over to groups.io now so you might want to look ther.
Back for a 2nd suck of the sav.. Couldn't resist and (just) picked up the same model. You must have had a positive impact or me or I'm a glutton for abuse. It's like I know what I'm up against but then think... I just keep doubling down until I win my self respect back 😁 Cheers!
Good luck with it - Be careful as I lifted the pads on this one I think.
I watched your video and really liked it, but I don't remember if you actually said which of the 4 resistors to remove or populate for 1GHZ.
Here is a post on the EEVBlog with all the info needed - www.eevblog.com/forum/testgear/tek-tds-3054b-vs-tds-744a/msg539818/#msg539818
hello i have this same TDS754D scope with this error nvLibrariansDiag ............... ***FAIL***
..error details:
ERRORID: 163 diagnostic test failure nvLibrariansDiag
Libs with crcc failures:
ExtConst
ERRORID: 358 nv storage too small more bytes requested than availabledo you have any idea? i change both chips NVRAM and timekeeper on the processor board.maybe we can get in touch to work things out?
Unfortunately I don't have any ideas - You might want to try the Tek Forums (forum.tek.com/) - I ended up selling the unit and the person that I sold it to reflowed the acquisition chips and that seemed to solve the problem.
please get in contact i know a schematic for this one
Thanks for letting me know - I finally sold the unit as I didn't really need it - The person I sold it to reflowed the acquisition ICs and that seemed to address the issue.
Charly Marina, hi, maybe you know a schematic for tds684a? 5538048@gmail.com
I have burned a couple of traces under opamp in acquisition board :(
Tooooooooooooooooooooooooooooooo long video, what did you do and what you achieved? Gsa?