Products > Test Equipment
Tektronix TDS754C not communicating over GPIB in unprotected mode
amaschas:
I've got a TDS754C that I'm working on repairing, and I'm trying to get a backup of the firmware before I pull the two NVRAM ICs. I'm using an AR488 (arduino USB to GPIB) to talk to the scope, and I can communicate fine when the scope is booted normally. I can send `*IDN?` and get back:
TEKTRONIX,TDS 754C,0,CF:91.1CT FV:v5.3e
However once I switch the scope to unprotected mode it stops responding over GPIB at all. Does unprotected mode use some pre-set address that I'm not aware of, or is there something else going on here?
44kgk1lkf6u:
Unprotected mode should use whatever address is configured. Maybe you have selected the off bus option in the menu under SHIFT ➞ UTILITY ➞ System (main) ➞ I/O (pop-up) ➞ Port (main) ➞ GPIB (pop-up) ➞ Configure (main).
amaschas:
--- Quote from: 44kgk1lkf6u on October 23, 2024, 01:48:01 pm ---Unprotected mode should use whatever address is configured. Maybe you have selected the off bus option in the menu under SHIFT ➞ UTILITY ➞ System (main) ➞ I/O (pop-up) ➞ Port (main) ➞ GPIB (pop-up) ➞ Configure (main).
--- End quote ---
I've confirmed that the GPIB address is 1, and that I can talk to the device in protected mode. I haven't touched the GPIB settings aside from verifying the address, and since I can communicate with the device in protected mode I assume the GPIB interface is on. I'm kind of baffled. I assume that the scope should at least respond to *IDN? in unprotected mode, right?
TERRA Operative:
Try doing a full factory reset.
I have had similar issues in the past occasionally, but somehow I eventually got the scope to resopnd.
I can't exactly remember how I got it to work, but try the reset and also make sure the time is set correctly too. It doesn't matter what[/] the time is set to, but I have noticed if that is corrupted then the scope can do some weird stuff.
Maybe a couple reboots in unprotected mode until it responds will work too.
amaschas:
--- Quote from: TERRA Operative on October 23, 2024, 10:44:34 pm ---Try doing a full factory reset.
I have had similar issues in the past occasionally, but somehow I eventually got the scope to resopnd.
I can't exactly remember how I got it to work, but try the reset and also make sure the time is set correctly too. It doesn't matter what[/] the time is set to, but I have noticed if that is corrupted then the scope can do some weird stuff.
Maybe a couple reboots in unprotected mode until it responds will work too.
--- End quote ---
Thanks for the suggestions! Unfortunately I still haven't gotten the scope to respond in unprotected mode. I've tried the following:
• Factory reset the device with this procedure:
Delete all "secure" files on the scope - so waveforms stored etc.
(TDS: "Utility" --> "Config" --> "Tek Secure Erase Memory" --> "OK Erase Setup & Ref Memory")
Perform a factory reset (TDS: "Setup" --> "RECALL Factory Setup" --> "OK Confirm Factory init")
• Cleared the error log using `error clear` and then `*cls`.
• Setting the time (the time seemed ok, but I reset each of the values just to be sure).
• Plugging the AR488 into the GPIB port a few seconds after starting the scope in unprotected mode.
• Rebooting the device several times in unprotected mode.
I'm wondering if there are any other debugging steps I could take here. Would the unprotected mode bootloader produce any output on the RS232 port that might be of help? I've been trying commands on GPIB channel 1 and 29. Are there other channels I should attempt?
Navigation
[0] Message Index
[#] Next page
Go to full version