Hi, I'm little late, but does anyone have this option stuff saved?
Ramppa
Quote from: snoopy on 2017-12-24, 15:50:07>Quote from: PrecisionAnalytic on 2017-12-24, 09:06:03>Quote from: dretay on 2017-12-05, 07:19:04Hey, no idea why the link doesn't work. Happy to send a copy to you if you want to PM me.
I'm not finding either sites up:
https://xdevs.com/guide/tek_key/
https://dev.xdevs.com/projects/rnd/repository/revisions/344cfa743297/raw/Tektronix/TDS7000/
I'd be very thankful for a copy.
Background if you are interested:
I received a few days back a TDS8000B that was stated on eBay as having Power Supply issues where they noted:
"Originally it was working but came back to us with a bad power supply. About once out of 20 times it will power on and light up. Sometimes it turns off by itself while booting. Most times it won't turn on at all then will make faint clicking ticking noise in the right rear of the unit. Screen has some scratching."
I powered on the unit and first time not thinking about having a keyboard plugged in to login and perform more testing as my brain was set to modern day touch screens with keyboards that appear on-screen as factory default. Powered on no issues, though is slow Windows 2000 Pro for sure.
After plugging in a USB keyboard with a USB to PS2 keyboard adapter, I pressed the power button on the front panel and was having no success with being able to use the keyboard to log in. I am guessing something to do with USB keyboard drivers is the reason.
Now, after holding the front panel power button for over 7 seconds, the unit powered off. When I tried to power back on, I heard a mechanical clock ticking sound with nothing happening. When I switched the power switch on the back of the unit the ticking sound slowly went away and all subsequent attempts to power on have failed with nothing happening.
Before I open the case up... any ideas to consider as I am making a giant leap into working on this system as I am still not yet graduated from a TDS-520 repair/restore... though am moving forward on that and learning a lot.
Just reading this page topic summary has bridged the programming firmware and electronics components like NVRAM and microcontroller gaps I've had.
Sounds like caps in the power supply or possibly on the motherboard.
Also if you can't get into the bios setup you need to first check your cmos battery on the NLB motherboard and replace it if it is dead. Likewise for the power PC board. If your scope is anything like the experience I had with a TDS7054 then you probably still won't be able to get into the bios setup so you need to boot up in dos on a floppy and run a program like killCMOS to reset your CMOS memory and then you will, beable to get into the bios setup.
http://www.majorgeeks.com/files/details/killcmos.html
You can create a bootup dos disk from another computer with a floppy using the setup from http://www.allbootdisks.com/download/dos.html
cheers
All the appropriate files are in the c:/vxboot locations the boot parameters direct to, they are just not loading to the PPC. Has anyone run into this before? I even changed out the RAM stick on the PPC with a NOS stick and that did not help either. Could this be a failure on the acquisition board or the connector between the PPC and AQB?
Thanks,
romPost: L2 cache turned on.
romPost: MPC107 Walking-one passed.
romPost: MPC107 configuration passed.
romPost: Intel21555 PCITOPCI bridge configuration passed.
romPost: PERFORMING ROM CHECKSUM TEST...
romPost: ROM checksum failed.
Expected Value: 0x0000E120
Actuall Value: 0x0000E11F
It looks like I've cleared up the hanging application issue with the TDS7404. I was reading through the install notes for the firmware update and came across this:
- Existing Windows 2000 oscilloscopes upgrading to version 2.5.3
can manually fix a problem with saving files (setups, images,
references, etc.) to remote filesystem devices through an
upgrade of the DIO service. Note this problem does not exist on
Windows 98 or factory-shipped 2.5.3 oscilloscopes. You will
need to obtain a copy of the dioservice.exe file from the
software updates section at www.tektronix.com, or your Tektronix
representative.
How to update DIOService on Windows 2000:
1. Click Start->Settings->Control Panel->Administrative Tools->Services
2. In the right pane, right click on "DIO Service"
3. Select "Properties"
4. In the General tab page, click on "Startup type" dropdown list
5. Select "Manual"
6. Click OK
7. Reboot
8. Copy the dioservice.exe file to C:\WINNT
9. Click OK to replace the old dioservice.exe
10. Change "Startup type" to "Automatic" by following procedures 1-4
11. Reboot
I checked and found that the unit's DIO Service was set to "Manual" so when I clicked on "Start" I heard the acq relays start clicking and a few seconds later I had waveforms on the screen. I set DIO to "automatic" and now the scope's Tek application starts up normally on power up.
But since I replaced the NVRAM (probably unnecessarily) I lost the serial number info on that and for some reason the .sn file in c:/vxBoot is empty. So I have lost all the options this scope came with. I copied the .sn file from a 7104 and used a Hex editor to change the serial number to the number that matches the 7404, put that new .sn file in vxBoot, and set the flag in the boot file to "0x1000", but the scope did not take the serial number and still lists the serial number as "-" and no options in the "About this scope" window. Can someone help me create a correct .sn file with my scope's serial number?
Thanks.
I'm completely stuck with the repair of a TDS6804B scope some less honest seller has sold me, as the acquisition board has been stripped in what seems to be an unscrupulous try-and-error repair attempt. A bit of everything is missing: some MCUs, an analog multplexer, some ADCs, two VCOs, a handful of passives. What were they thinking? A total shame, whoever did this to such great piece of equipment.
It's very likely that someone was harvesting parts from your scope to fix another. Even if you were to find all the parts for it, it probably has other issues as well - otherwise, why take parts from a good working scope?
I do not envy your task!
I have two almost working 6804B's, I can send you pictures of the boards. Would be cool to collaborate on repair of these devices. Do you have any info on the architecture of AQ board?
Hi Guys!
Would like to share some repair info back on the TDS7104, in this case the power supply.
I turned on my TDS7104 recently after a long time and it smelled strange and did not turn on. I immediately removed the power supply, inspected it visually.
The effect was:
- strange smell (but no Smoke)
- A clicking noise about 3-4 times per seconds when powered
- the RED LED close to IC310 was blinking with the same frequency as the clicking sound.
Began reverseengineering the schematic based on the PCB and doing lots of measurements.
Capacitor C97 was measured to have an ESR of 2 Ohm. This was unexpected high, allthough not tremendously too high.
I replaced it with another one (only had a 100V type lying arround, so it does not fit mechanically perfectly). This was my luck, because
I had to mount it with a distance to the PCB, and only because of this, I noticed this here:
https://youtu.be/4Kj9WRJPUvI
Note: The smoke is not coming from the cap, it is coming out of the PCB. Furthermore, there are sparks on the PCB.
Microscope inspection showed, that the CAP got incontinent and left it's jam on the PCB, where it etched it partly ways. After removing this, it turned out to have left a 1mms deep hole in the PCB. Likely this dielectricum got conductive too, otherwise there would not have been sparks.
After cleaning + remounting the new cap, the Supply was perfectly working again!
Best regards,
Kai
Still, I think this might happen to other CAPs too. Maybe worth to replace nearly all eletrolythic capacitors?!?
Can anybody help,I did that as change the file sn,key and removed the#in the file,then I restart the instrument,now it seems stuck as the picture shows,should I wait or change the NVRAM battery?
Can anybody help,I did that as change the file sn,key and removed the#in the file,then I restart the instrument,now it seems stuck as the picture shows,should I wait or change the NVRAM battery?