EEVblog Electronics Community Forum
Electronics => Repair => Topic started by: chick0n on September 06, 2022, 08:13:53 pm
-
This first problem is solved, or where non existant.
Scroll down for more problems. :)
-
Some Pictures: https://ibb.co/album/xqNvf6 (https://ibb.co/album/xqNvf6)
Some stuff I found out: (With help of other people on the Forum)
- After you Disconnect / Change the NVRAM Lithium battery, the trace wents to the top of the LCD in full span mode.
Solution: You have to turn off the analyzer and hold the "." dot key, while turning on, during the whole bootup process. This initializes the NVRAM, and everything is back to normal.
- When you want to use a new CF card, you need a 8 or 16MB card, and format it with this tool:
https://www.sdcard.org/downloads/formatter/ (https://www.sdcard.org/downloads/formatter/)
Then copy the files on it. Nothing else worked for me.
- After pressing: "Shift + Format + 882323 + Hz", you can reset "ATT switch count" and "Power ON switch count".
- After pressing: "SHIFT + WINDOW + 882323 + Hz", you enter the calibration menu, where you can read/write/tweak every calibration value. So you dont need some unobtainium PC Software like with R&S Machines. (Thank you Advantest :)
When you want to save the changes to the EEPROM, you need to remove the small backplate assembly, with the 4 screws. There is a DIP Switch, where you can turn EEPROMWRITE on.
- Pressing SHIFT + TRANSIENT will also ask for a password, but it is not known yet. I think this is the access to the debug mode. I found some interesting strings in the firmware:
DFM.txt: --- Read memory ----------------
DFM.txt:
DFM.txt: DEBUG MODE
DFM.txt: TBC SEND 595
DFM.txt: TBC SEND DAC
DFM.txt: TBC SEND DAC 500
DFM.txt: TBC SEND CXD
DFM.txt: TBC SEND 87086/16
DFM.txt: TBC SEND 87086/20
DFM.txt: TBC SEND AD7008
DFM.txt: TBC READ 0831
DFM.txt: TBC EEPROM WRITE
DFM.txt: TBC EEPROM READ
DFM.txt: TBC SRAM WRITE
DFM.txt: TBC SRAM READ
DFM.txt: DEBUG MODE
DFM.txt: Standard
DFM.txt: TBC|Send xxx
DFM.txt: TBC|Read 0831
DFM.txt: TBC|EEPROM xxx
DFM.txt: TBC|D.P.M xxx
DFM.txt: return
DFM.txt: STANDARD
DFM.txt: ACTIVE
DFM.txt: address| write
DFM.txt: FORMAT
DFM.txt: Hex|Dec
DFM.txt: SIZE TYPE
DFM.txt: 8|16|32
DFM.txt: Read Loop
DFM.txt: Write Loop
DFM.txt: return
DFM.txt: SEND 1/2
DFM.txt: TBC|Send 595
DFM.txt: TBC|Send DAC
DFM.txt: TBC|Send DAC5
DFM.txt: TBC|Send CXD
DFM.txt: TBC|Send 7008
DFM.txt: next menu
DFM.txt: return
DFM.txt: SEND 2/2
DFM.txt: TBC|Send 87086|/16
DFM.txt: TBC|Send 87086|/20
DFM.txt: prev menu
DFM.txt: TBC EEPROM
DFM.txt: TBC|EP Write
DFM.txt: TBC|EP Read
DFM.txt: return
DFM.txt: LOCAL BUS
DFM.txt: TBC|SRAM Write
DFM.txt: TBC|SRAM Read
DFM.txt: return
DFM.txt: DEBUG TBC
DFM.txt: ACTIVE
DFM.txt: address| write
DFM.txt: Write Loop
DFM.txt: return
DFM.txt: DEBUG TBC
DFM.txt: ACTIVE
DFM.txt: address| write
DFM.txt: Read Loop
DFM.txt: return
DFM.txt: DEBUG TBC
DFM.txt: ACTIVE
DFM.txt: ID |sorc|dest|size
DFM.txt: Execute
DFM.txt: return
I searched all firmware files for the passwords, but could not even find "882323", which is the same as for the R3131A.
I wonder how they are encoded?
- There even exist a tool on the cf card (TBC.X), to read/write the calibration values as .csv files. But I dont know how to execute it. (Maybe through Debug Mode)
I attached my CF-Card content, and I even Read out the TSOP Flash-EPROM on the CPU Board. Maybe anyone can find the Debug mode password.
The Operating System is called VRTX-32 from Mentor Graphics. I think the kernel runs on the Flash-Eprom, and the executables are on the CF-Card.
Also VRTX runs the Hubble Space Telescope. :)
CF Card Content: https://drive.google.com/file/d/1XZMoc3Zd86UlXWMjUhN6VH5KTtQ_qpTr/view (https://drive.google.com/file/d/1XZMoc3Zd86UlXWMjUhN6VH5KTtQ_qpTr/view)
Also: Broken TG Fix: https://www.youtube.com/watch?v=UoeYxC_UBrM (https://www.youtube.com/watch?v=UoeYxC_UBrM) Oh Boy.... |O
-
Other Problems:
The -10dbm 30MHz Calibration Signal is OK. But when I connect it to the input, the analyzer reads it as 0dbm. This is only in the first minutes of operation, when the analyzer is still cold.
When the analyzer is warming up for a few minutes, suddenly the noisefloor drops a little bit, and the 30MHz signals then gets read as about -37dbm.
Both readings are either too high or too low, to be recognized in the calibration routine or selftest.
Sometimes the calibration routine catches the signal, and tries to calibrate for a few seconds. But then it freezes. and I have to press preset to reset the analyzer.
When the selftest catches the signal, everything fails, except the CPU and Synthe Block test.
When I look in the maintenance menu, at the system status, it complains about the RF and IF Output level. (See Photo)
Ignore the "Reference PLL" failure, I got that fixed already...
Also the Option 01 DSP Board doesnt get detected. But maybe it is really broken, and this isnt a bus communication error. I will try to deactivate this option, since its "only" a Signal Analyzer for old Mobile Standarts like cdma2000 and stuff....
-
I investigated a little bit further today, and tested the IF / Mixer stages.
I set the analyzer to zero span, and injected a 21.4MHz signal (3rd IF) into the IF Card. The dbm level reads about right.
Then I injected 421MHz (2nd IF Signal) into the 3rd Mixer. The level reads ok too.
Then I injected 4231.4MHz (1st IF Signal) into the second mixer. And there the strange behaviour begins to show. The signal level degrades over the course of a few seconds.
So the problems seems to lay in the 2nd Mixer. I treated the area with cooler spray and heat, but nothing changed.
Maybe the problem lays in the steering of the mixer on the underside of the RF block.
The PLL seems to work...
Maybe its a digital problem...
-
Also the last owner soldered around Q100. This is the amplifier stage for the 1st IF Signal.
The gaasfet looks like a NE32584C, so I ordered a new one.
-
That is some poor soldering technique the previous technician used!
Great Posts, I have a 3267 here that has a sick TG. Need to see what is going on with it. Keep up providing this information, it’s very useful!
Rich
-
That is some poor soldering technique the previous technician used!
Great Posts, I have a 3267 here that has a sick TG. Need to see what is going on with it. Keep up providing this information, it’s very useful!
Rich
Thanks.
Maybe you could take the measurements i mentioned in the first post for me?
The Cpu Boards of R3267 / 73 are the same.
-
WOW...I got a BIG Problem solved today.
It seems the "Filter Board" is broken. (See Picture)
While checking the analyzer, and whiggling around the connectors, I accidentally short-circuited the filter board, which completely destroyed it. (The 30MHz peak was very small now, around -70dbm instead of -10)
First I thought, this is game over for this analyzer now...
Then I found out, you can bridge the filter board completely. I think the Board filters the supply voltages and some signals to the RF Block, I think. The RF-Block has two 10Pin connectors for the filter, which are the same. So you can put in a jumper cable.
I turned the Analyzer on, and:
30MHz Signal is strong now.
- CAL-Routine passes completely, without freezing.
- Selftest passes completely, without errors.
- DSP-MOD Board gets detected.
3 problems solved.
The 30MHz -10dbm cal signal reads as -6dbm, after calibration. Which is a highly accurate reading for this mess of an analyzer... :)
Tomorrow I will make further tests.
I dont know how, and what this Filter actually Filters.
It consists of 4 AD822AR OP Amps, 3 2sd1584 NPN Transistors, and 3 2sa1615 PNP Transistors.
One 2sd1584 is broken, and some ADs too, because they get hot.
You can still buy the ADs, but the Transistors are almost unobtainium.
-
WOW...I got a BIG Problem solved today.
It seems the "Filter Board" is broken. (See Picture)
I dont know how, and what this Filter actually Filters.
It consists of 4 AD822AR OP Amps, 3 2sd1584 NPN Transistors, and 3 2sa1615 PNP Transistors.
Maybe this is just a voltage regulator board? At least the combination OPAMP - (bigger) Transistors and Caps make me suspect that.
-
Maybe it regulates the voltages slightly, to keep it constant and precise for the RF-Block.
Also the PCB is mountet behind the front panel. Away from heat sources.
-
I played a little bit more today.
I first thought, the High Band Mixer (TOP2301) is completely toast. This little block is responsible for the 3.5 to 26.5GHz range.
It is a combined YIG Filter and Harmonics Mixer. It can also pass through the low band (100HZ to 3.5GHz). It mixes the High Band right down to 421MHz.
I got very low readings from 4 to 8GHz, and nothing beyond that, at first. After twiddling around in the maintenance menu, I now get strong peaks from 3.5 to 26.5GHz. Not correct readings, but I can "see" up to 26GHz now. :)
It seems, the mixer was a little bit out of calibration, or some previous owner swapped it.
Non the less, a good calibration manual for the R3273 would be nice to have...
-
I examined the "Filter" board some more.
Its really are "just" 6 Voltage Regulators.
It takes +12.6V and -12.6V at the Input, splits it to 3x +12.6V and 3x -12.6V, to each Regulator.
At the Output, I get 6 times +-11.7 Volts. :P
One 12V Voltage is missing, because the Transistor is broken. And one AD822 gets really hot. I will try to repair it. Or maybe build a new one?
Maybe Advantest calls it Filter-Board, because the Voltage stays about the same, but the output is more clean and stable.
Also, I fine-tuned the YTF. I get constant readings now, on the full range to 26.5GHz. 8)
The Amplitude still reads too high, but hey... :-//
-
Also, I fine-tuned the YTF. I get constant readings now, on the full range to 26.5GHz. 8)
I would have tried to repair the board first before doing any adjustments - are you sure that the YTF adjustment is wrong? Maybe the values it depend on the addtional voltage drop from the regulator? Do you still have the original values?
-
Also, I fine-tuned the YTF. I get constant readings now, on the full range to 26.5GHz. 8)
I would have tried to repair the board first before doing any adjustments - are you sure that the YTF adjustment is wrong? Maybe the values it depend on the addtional voltage drop from the regulator? Do you still have the original values?
Yes...I made photos of almost all calibration values.
With the password for the Debug Mode, one could save calibration values as .csv files. And save as backup, or edit in excel. That would be really cool...
-
Yesterday the CPU-Board died again. :palm: I guess it has been Resoldered too often.
So I need to wait till someone sells me an R3267 / 73 CPU-Board. Or wait till a parts Machine pops up.
-
After some Reflowing, the CPU-Board is Booting again. :P
But now, the Amplitude problem is showing again.
When the Analyzer is cold, it shows the -10dbm cal signal as +2dbm, thats too much for the cal routine.
After warm up, the whole Trace on the LCD drops (Not just the Peak getting smaller), and shows the signal as -22dbm.
Whats really weird is, that the drop only shows after preset, or reboot. Which makes debugging extra hard...
I measured the converter stage outputs again, after cold and warm (preset) state.
1st converter cold: -21dbm, warm: -20dbm
2nd converter cold: -18dbm, warm: -15.4dbm
3rd converter cold: +6,2dbm, warm: -21.8dbm (wow)
-
Further investigation:
I dont think, the 3rd converter is broken. (Would be too easy)
Theres some gain control voltage for the 3rd output transistor, that looks fishy.
Voltage Cold: -5V (Shows +2dbm on analyzer)
Voltage Warm (after Preset) -1,6~V (Shows -22dbm on analyzer)
When I disconnect cable to the transistor, Voltage is -12V
When I put in about -3.3V, from external power supply, analyzer shows -10dbm. The Cal Routine almost passes, but fails at the end. (She wants to adjust the control voltage herself?)
The control voltage comes from the underside of the RF-Block, which makes debugging extra hard....
-
I have the sneaking suspicion, my attenuator is crimped wrong.
The Owner before me replaced it, and it works. But hmm...
Does anyone have a picture from the underside of the R3273 RF-Deck?
-
No photos. Calibration guide is available.
https://cloud.mail.ru/public/gG8r/DzJXmPxig
-
Ok..false alarm. The attenuator is connected correctly.
And I have working CPU-Board now.
The fix for "-10dbm CAL Signal showing as -40dbm on the analyzer", is bridging the Voltage Regulator, for now. (The RF Block gets 12.7V instead of 11.7V). Something seems to have degraded in the RF-Block over the years. And its not the Electrolytics, I changed every one of them. Made no difference.
For me the Signal was still a little bit too low, to start calibration. Theres a 2db Attenuator in the RF input path (before the 3,6GHz Low Pass Filter), that I replaced with a 1db one. Now everything seems works fine.
I have to let the analyzer heat up for at least 30min before doing calibration or measurements.
-
Hi! Glad to see I'm not the only one to experience the BROKEN tracking generator ;D
As for the underside of the RF deck, I do have pictures, because that's where the frequency response calibration EEPROM is. I also have a python class that knows how to read and write frequency response calibration values. Here:
https://www.dropbox.com/sh/duiwlludrlxyala/AACnrKwy0W6_VMswptNcmWIVa?dl=0 (https://www.dropbox.com/sh/duiwlludrlxyala/AACnrKwy0W6_VMswptNcmWIVa?dl=0)
The RF deck EEPROM is in a really obnoxious location, so it would be nice if you figured out how to do it through GPIB instead. The most promising lead I know on that front is the $R/$W GPIB commands from the older R3371. The Advantest mailing list figured them out after I did things the hard way, of course -- but maybe they can help you!
# $R is READ
# $W is WRITE [url]https://groups.io/g/advantestinstrument/message/1545[/url]
allData = b''
print('Start reading %s words' % n)
for a in range(0, n):
address = str(format(start_adr+(a * 2), '02x'))
data = Device.query('$R%s' % address).strip("\n")
print(address, '\t', data)
allData = allData + binascii.unhexlify(data.strip())
Program to concatenate:
[url]https://groups.io/g/advantestinstrument/message/1526[/url]
EDIT: fix link
-
Hi! Glad to see I'm not the only one to experience the BROKEN tracking generator ;D
As for the underside of the RF deck, I do have pictures, because that's where the frequency response calibration EEPROM is. I also have a python class that knows how to read and write frequency response calibration values. Here:
https://www.dropbox.com/sh/duiwlludrlxyala/AACnrKwy0W6_VMswptNcmWIVa?dl=0 (https://www.dropbox.com/sh/duiwlludrlxyala/AACnrKwy0W6_VMswptNcmWIVa?dl=0)
The RF deck EEPROM is in a really obnoxious location, so it would be nice if you figured out how to do it through GPIB instead. The most promising lead I know on that front is the $R/$W GPIB commands from the older R3371. The Advantest mailing list figured them out after I did things the hard way, of course -- but maybe they can help you!
# $R is READ
# $W is WRITE [url]https://groups.io/g/advantestinstrument/message/1545[/url]
allData = b''
print('Start reading %s words' % n)
for a in range(0, n):
address = str(format(start_adr+(a * 2), '02x'))
data = Device.query('$R%s' % address).strip("\n")
print(address, '\t', data)
allData = allData + binascii.unhexlify(data.strip())
Program to concatenate:
[url]https://groups.io/g/advantestinstrument/message/1526[/url]
EDIT: fix link
For the R3273, its little bit different.
There are two Hidden Menus. In one menu, you can tweak the calibration values directly from the front panel. For this menu, the Password is known.
The other one is the Debug Menu, with this you can read and write the whole memory map. And you can save the Calibration Values as .csv files on the CF-Card. (every module in R3273, has its own eeprom with cal values). Unfortunately, the Password for the Debug Menu is not known yet, so no one was able to test this yet.
"csv" sounds like, the analyzer converts the eeprom content directly into human readable form.
The passwords for the menus are not stored in ASCII form, but encoded with alghoritm? Decoding this exceeds my skills....
-
I never figured out the second password, but I did calibrate the frequency response on two R3273s with r3273.py. It works.
-
I never figured out the second password, but I did calibrate the frequency response on two R3273s with r3273.py. It works.
Sorry... i didnt see the dropbox link first.
That looks very helpful. My r3273 could use a Step Attenuator calibration too. But I have to figure out how to get this running...
Also, the Attenuator crimping looks identical to mine. Thanks.
-
Hi folks,
I sketched some time ago the schematic of the BLC024864, I attached it as a pdf file. It is not looking very nice, but at that time it was good enough for me to repair mine. It si a simple voltage filter, which makes silent power supply lines for the RF part. In my unit, one 39 kOhm divider resistor was simply interrupted. It is not exposed to high voltages or currents, it simply gives up. After replacement all my RF voltages were fine. But as it was stated above, I also skipped the filter board as a first step, and looped the voltages back to the RF module. Just after that I started to find the problem on the module itself.
My R3267 units have flash ROMs, and no CF cards inside. The main CPU boards are different from the R3273, which indeed has the firmware on a CF card (pictures of the two sides of one of my R3267 attached).
@Chick0n: if you need some measurements on the main CPU boards connectors/interfaces, please let me know. I will try to do them in one of the following weekends.
BR,
Gyorgy
-
Hi folks,
I sketched some time ago the schematic of the BLC024864, I attached it as a pdf file. It is not looking very nice, but at that time it was good enough for me to repair mine. It si a simple voltage filter, which makes silent power supply lines for the RF part. In my unit, one 39 kOhm divider resistor was simply interrupted. It is not exposed to high voltages or currents, it simply gives up. After replacement all my RF voltages were fine. But as it was stated above, I also skipped the filter board as a first step, and looped the voltages back to the RF module. Just after that I started to find the problem on the module itself.
My R3267 units have flash ROMs, and no CF cards inside. The main CPU boards are different from the R3273, which indeed has the firmware on a CF card (pictures of the two sides of one of my R3267 attached).
@Chick0n: if you need some measurements on the main CPU boards connectors/interfaces, please let me know. I will try to do them in one of the following weekends.
BR,
Gyorgy
Thanks for the Schematic!
Do you Measure the same Voltages as me on the Voltage Filter? About 12.7V Input and 11.7V Output?
-
After Disassembling the MAINTE.X, I found 3 ocurrences of "882323":
ROM:0000D016 cmpi.l #882323,0(a0)
ROM:0000D0C0 cmpi.l #882323,0(a0)
ROM:0000D184 cmpi.l #882323,0(a0)
One for each hidden menu? Except, for "SHIFT + Transient", nothing happens.
So maybe the Password is Correct, and something is missing for triggering the debug menu, or the menu gets triggered somewhere else?
-
Maybe a dipswitch setting is required ( under the backplate). The eeprom write must be also enabled by a dipswitch, so this could be similar. You have a Write protection in the software menus, but it will work only if the dipswitch is set. It worth a try using the unknown dipswitch items. Some are already identified, if I remember, one or two are used to route different signals to the backpanel BNC socket. So the remaining could be what we are looking for.
-
Maybe a dipswitch setting is required ( under the backplate). The eeprom write must be also enabled by a dipswitch, so this could be similar. You have a Write protection in the software menus, but it will work only if the dipswitch is set. It worth a try using the unknown dipswitch items. Some are already identified, if I remember, one or two are used to route different signals to the backpanel BNC socket. So the remaining could be what we are looking for.
Already tried the dip switches on cpu board and backpanel. :-//
-
Maybe a floppy disk must be inserted and detected by the system. Just a thought. ???
-
Maybe a floppy disk must be inserted and detected by the system. Just a thought. ???
yep...I thought that too...
Also, when you switch dip switch 1 on the cpu board on, it asks for a boot disk.
-
I double checked the backpanel dipswitch. Only 1,5 and 6 are used, the others are not connected. So there is nothing else to look for here, we know the functions of these settings ( it is marked in fact on the silkscreen of the printed circuit board BLC-024514). The conditional access to the special menu is hidden somewhere else. Maybe a floppy disk with some special content is needed ( not a boot disk, since we are looking for some software option settings, and maybe the disk should contain some option files, which should be transferred in this menu to the compact flash, or flash memory in the case of analyzers without compact flash).
In one of the other topics related to the R3273, someone wrote about a serial port available on the main CPU board( some messages were listed during the ooer up). Maybe this can be used as a terminal, and there you can send special maintenance commands. However, all these should work also over GPIB.
-
I connected to the J12 connector on cpu board. Pin1 is TX, 2 maybe RX?, 3 GND, rest is GND and 5V.
I was never able to send commands.
I received some boot messages, and when the analyzer is bootet up it writes SD:/SD:/SD:/SD:/SD:/SD:/SD:/SD:/ over and over again...
When I type "shift + window + 882323 + hz", it sends "CW KEY SET" over rs232.
When I type wrong password, nothing...
In the MAINTE.X, I found Strings:
CW KEY SET
CW KEY DEL
DFM KEY is Invalid.
DFM KEY is not Delete.
-
The serial port will be good for monitoring/debugging. Whe you try the hidden menu SHIFT + TRANSIENT +882323+Hz, does it report anything on the serial? I have to connect my analyzer to a serial port in the weekend and play a bit. Are there any other operations ( for example in the maintenance menues) reported over the serial?
-
I also found, the DSP-Board has a own Maintenance Mode. But I dont know how to access.
-
I checked on the low signal problem again.
Everything is back to stock...Voltage Regulator is in...
I applied -10dbm CAL Signal to analyzer input, set analyzer to zero span... shows as -50dbm on analyzer.
I disconnected the connection between 1st mixer output and 2nd mixer input. Then I connected Power Sensor to 1st mixer output. Shows about -13dbm at 4,3GHz....
Then I set microwave source to 4,3GHz -13dbm, and injected to 2nd mixer input. Analyzer Shows -13dbm correctly. :wtf:
Then I reconnected 1st mixer to 2nd mixer. Analyzer shows -50dbm again... :-//
I dont know whats right or wrong in this world anymore...
-
Your power meter is a broadband device, I mean it is not a selective receiver. You can measure the -13 dBm level, but it does not mean that the carrier frequency which cames out from the 1st IF it is there where it should be (a relatively small frequency deviation could be enough, to measure a low level. Of course all these will also depend on the selected RBW). Try to feed from the external generator (which preferably is connected to the same reference clock as the analyzer) a 30 MHz -10dBm signal to the input of the analyzer. If this works, and you will measure a correct level, it means that your 30 MHz CAL signal is out of sync, and it is not at 30 MHz (which would be a bit strange). If this doesn't work either, than you might have a shift in the frequency of the first local oscillator. Which is possible, even if it seems locked. The phase lock of the YIG is a multi loop PLL, with several conversions, and if you change some settings in the maintenance mode, you can easily detune it (and will be locked to a shifted frequency. But if you have not changed the settings in the maintenance mode, this should not be the case). So you have to find out 2 things: if your CAL signal is sharply 30 MHz, and if your 1st LO is spot on the right frequency. They both are locked to the 10 MHz reference frequency.
Also please note: The 4.1 GHz IF is used only for the low frequency band (if I am right below 3.5 GHz). For higher frequencies it is skipped, and the IF is directly 421 MHz. Eventually, check the RF path measured level, with some RF signal in the higher bands (above 4 GHz). Just to be sure, that this path which does not use the 4.1GHz IF is working or not.
-
Youre right, with Power Meter I measure all "Peaks" in the Spectrum at the same time... Also I "misused" the Scalar Detector of my Marconi 6203 as Power Sensor, because it is more Sensitive.
I checked the cal signal with a good analyzer. Its OK.
My freq. Counter and Microwave source are synched to the R3273 Ref.
I connected the 1st mixer IF out to the counter, it measures exactly 4.23154GHz. So the strongest Peak on the 1st mixer output seems about correct. (Service Manual says 1st IF is 4.2314GHz)
Also, the "torque" of the screws on the 1st mixer lid make a difference in output power. All screws tight = -23dbm. Loosing some screws = -13dbm. Lid open = -27dbm. ;)
-
Ok...I measured again with the 4.5Ghz Low Pass Filter in place at the IF Out.
I think, what happens is, sometimes the counter catches the YTO-LO frequency at the IF Out (~4.26142GHz), and sometimes it catches the IF frequency (4,23154GHz).
The Power Sensor measures both, and maybe more Mixer Products...
The IF gets filtered better at a later stage, with a Bandpass Filter.
-
Today I found out, SHIFT + TRANSIENT + 882323 + Hz, does indeed Trigger a hidden menu.
Its the Maintenance mode of the DSP-Card. You can acces under CONFIG - Comm Sys. - Maintenance.
Smacks on forehead... :palm:
So we finally got that sorted out...and we know definately, the Debug Menu gets triggered somewhere else...
-
I think the culprit is in the 2nd Mixer Stage.
When I Power the whole RF-Block with the Voltage Filter (11.5Volt), EXCEPT for the Blue Cable over the 91Ohm Resistor (Where I inject 12.5V). The Analyzer shows me the -10dBm Cal Signal as -21dBm (Uncalibrated).
This is the same, as if I Power the whole block with 12.5V. With this, I can get the Analyzer to Self Calibrate...
This is the BIAS voltage for the "E5" IC (I think this is a Minicircuits ERA-5 MMIC. Is it?)
The Problem is, the ERA-5 Datasheet says, it needs about 5V BIAS Voltage. So with 11 to 12V over the 91Ohm Resistor, it should be about 5V at Pin3 of ERA-5.
BUT I measure between 9.7 to 10.4 Volts at Pin3. So ERA-5 is toast?
The resistor measures OK.
-
@jjoonathan
I am not mastering python, but what I understand that you have identified the eeprom structure, which holds the frequency calibration data. Can you detail a bit, how did you find that?
And what I concluded: you removed the eeprom from the RF deck, and read out the content. After your RF path (attenuator) measurements, you wrote the corrected coefficients to the eeprom. I am right in this matter?
I am very interested in this topic, since I would like to calibrate mine too, but I am looking to find an easyer way, to read it out through GPIB (no good results yet, but I am still working on it), and avoid the disassembly of the RF deck, and unsolder the eeprom. Probably the $R and $W GPIB commands, as I figured out, will help doing this
I would really appreciate your help.
Thanks,
Gyorgy
-
I disconnected the digitizer IF input coming from the frequency converters and instead applied a constant tone from a signal generator. Then I used GPIB to read the measured amplitude at 10,000 points or something -- effectively this gave me the calibration trace. It used linear interpolation, so the high resolution trace clearly indicated both the frequencies and amplitudes of the correction table (inflection points). Now that I had the correction table, I created a script to try all "origin/offset/encoding" triples and look for strong correlation. I didn't find anything on the CF card, so I looked harder for EEPROMs and eventually found the EEPROM on the RF deck. The search script found (IIRC) 8 hits corresponding to 8 settings of the input attenuator.
With luck, you might be able to use the EEPROM dumps in my dropbox to locate EEPROM in the memory map with $R and then use $W to update the calibration values. Please let us know how it goes! :-+
-
I think the culprit is in the 2nd Mixer Stage.
When I Power the whole RF-Block with the Voltage Filter (11.5Volt), EXCEPT for the Blue Cable over the 91Ohm Resistor (Where I inject 12.5V). The Analyzer shows me the -10dBm Cal Signal as -21dBm (Uncalibrated).
This is the same, as if I Power the whole block with 12.5V. With this, I can get the Analyzer to Self Calibrate...
This is the BIAS voltage for the "E5" IC (I think this is a Minicircuits ERA-5 MMIC. Is it?)
The Problem is, the ERA-5 Datasheet says, it needs about 5V BIAS Voltage. So with 11 to 12V over the 91Ohm Resistor, it should be about 5V at Pin3 of ERA-5.
BUT I measure between 9.7 to 10.4 Volts at Pin3. So ERA-5 is toast?
The resistor measures OK.
I replaced the ERA-5. (BIAS Voltage of 4.8V seems perfect) And its working now. Frequency Response from 10MHz to 3.5GHz is very good now. Over 3.5GHz its a bit over the place, maybe because the YTF Calibration is wrong, but seems solvable with a little tweaking. Also the the Step Attenuator was replaced, so the Frequency Correction is wrong.
But for the Price I got the analyzer for, im pretty pleased.
Another little problem is the BIAS Voltage for the first mixer Diode (See Picture). When I connect it, the input Signal degrades. Disconnected everything seems fine.
I have 2 RF-Decks with this same problem here, and I heard from others who have this problem.
The Diode marked "D2V", seems to be a HSMP-3802 double PIN Diode, where just one Diode is used. It measures OK in the component tester.
Mixer Diode seems OK too.
-
I made Firmware with all software options, for R3267/73. You need hardware option 01, to use the software options.
Just delete the old files from your cf card, and copy the new ones.
Dont format your CF-Card with Windows!!
Should work for R3273, R3267 with CF-Card and maybe R3264.
Im still looking for Firmwares higher than I08. Im especially looking for firmware from analyzer with "OPT.05 Audio Demodulation Output Option", to check if this is hardware or software option.
Maybe some Options are useful for Hobby use.. Especially with the AMPS Option, you can measure FM-Deviation and SINAD.
Options:
OPT61: IS-95 [A08] Aug 08 2001
OPT62: 3GPP [J02] Nov 08 2004
OPT63: GSM/DECT [D01] Jul 08 2003
OPT64: PDC/PHS/IS-136 [B04] Jul 25 2000
OPT65: cdma2000 [D00] Jan 24 2003
OPT66: Bluetooth [C02] Jul 08 2003
OPT67: HDR [E00] Jun 28 2004
OPT69: HDR(MS)[B00] Jun 28 2004
OPT73: AMPS/JTACS/NTACS [A05] Aug 08 2001
-
It seems to me, or is there a crack from the fastening of the plate, and down to the right diagonally?
-
It seems to me, or is there a crack from the fastening of the plate, and down to the right diagonally?
Thanks..I checked it...and this picture is not from my analyzer. I borrowed it from "3g57", on the forum. :)
I found another picture, from a R3267. There the BIAS Circuit was never connected... Weird...
As I understand, the RF deck of the R3267 is the same as the R3273. Especially the first mixer for the low band. Only the High Band mixer goes up to to 8GHz, instead of 26GHz.
I have 2 assumptions about this circuit:
1. BIAS Voltage for the mixer diode, to compensate for the LO output power fluctuations.
2. In the R3271 Service Manual, a similar circuit is described. There a BIAS TEE is used to prevent the IF from the High Band mixer (421MHz) leaking to the low band. How this works I dont know...
-
Im trying to tune the YTF / High Band Mixer in the cal menu, with my Marconi 6203 Microwave Source. Looks promising.
This is YTF Band 1 from 3.7 to 7.4 GHz, sweeped at -10dBm. Before and after coarse tuning attempts.
The traces are looking crappy, because the Marconi isnt synched to the R3273.
-
Dear chic0n
Thanks to this blog, I was able to repair my R3267, thank you very much.
After investigating the cause, it turned out that there was a problem with the 1st IF or the 2nd IF. When the SSG signal was applied to the 2nd IFin of 421.4MHz, the level was normal.
After looking at this blog, I measured the voltage at pin 3 of the ERA-5 and it was 11.2V, so I knew the ERA-5 was dead.
I ordered ERA-5SM, and I got it cheaply at ¥210/piece.
I installed the ERA-5SM and it was a perfect repair.
The voltage after installation is 4.7V.
Thank you very much.
ginji
-
Added, low level problem of R3267.
-
In search for the DEBUG MENU Access, I extracted some undocumented GPIB Commands from the DFM file.
No Luck so far.
Maybe someone else wants to try.
Especially interesting ones:
$AR
$AW
$DDS
$EPR
$EPW
$FBFIX
$FCRD
$FR10
$FR5
$FSK
$FW10
$FW5
$R
$RAMP
$RF
$SR
$SW
$W
$WF
$YSWP
I think RAM / ROM Read and Write is possible. So be careful...
-
Have you checked the module in the red frame?
-
Look here.
Advantest R3273 and R3267 blocks are different.#
#10 its from Advantest R3273
3g57
-
Added, low level problem of R3267.
Hello Ginji!
Question: did you solve the problem with the signal level?
-
jjoonathan Uploaded a Calibration tool to Github. Maybe its helpful to someone:
"Hi! I went and uploaded my R3273 code here: https://github.com/jjoonathan/R3273-calibration (https://github.com/jjoonathan/R3273-calibration) . This should help with level correction, but I'm afraid I never figured out YIG correction due to the existing YIG calibration being quite satisfactory in contrast to the HP8565E in the video. I pointed out my best lead, though: there is a suspicious unknown "field5" in the cal data that might just hold the yig cal. Good luck!"
His youtube channel: https://www.youtube.com/watch?v=dygVTmiumYU (https://www.youtube.com/watch?v=dygVTmiumYU)