| Products > Test Equipment |
| Anritsu MS2721B internal CF card missing |
| << < (4/18) > >> |
| brainstorm:
Awesome news, I'm so happy for you @AnalogRF! :D My instrument needs review on the power rails/capacitors, it was a bit finicky on power-on before and now it doesn't even turn on, just flickers. I tried the MST software before but couldn't get a connection so no firmware update was possible, I'll take your advice into account when the hardware side is back in good health ;) So unfortunately I cannot dump the EEPROM... yet. If you are based in Melbourne we can meet and exchange notes perhaps? Happy to! ;) |
| analogRF:
--- Quote from: brainstorm on May 05, 2020, 10:54:31 am ---Awesome news, I'm so happy for you @AnalogRF! :D My instrument needs review on the power rails/capacitors, it was a bit finicky on power-on before and now it doesn't even turn on, just flickers. I tried the MST software before but couldn't get a connection so no firmware update was possible, I'll take your advice into account when the hardware side is back in good health ;) So unfortunately I cannot dump the EEPROM... yet. If you are based in Melbourne we can meet and exchange notes perhaps? Happy to! ;) --- End quote --- no, ignore when MST says cannot connect to the instrument! Mine said that too. Ignore that. That type of connection can only be established when the instrument is up and running. But when you go to the emergency repair and select Install New OS then IT WILL CONNECT to the instrument although it does not say it explicitly. I guess it must be a sort of ftp connection but FIRST you must put the device in the firmware downloading state as I explained. You will not see anything happening on the instrument screen but it is actually downloading the firmware. I desoldered the EEPROM (there is only one single 32KB SPI EEPROM - AT25256AW - on the entire board) and dumped it. It's all garbled binary. I used every tool I know of to try to extract some meaningful information like the serial number or even model number which the manual says are in the EEPROM or any other meaningful word , but nothing |O I put it back in and of course the instrument works fine . The power rails are easy to repair, but are you sure it is the power rails? Disconnect the RF deck completely and try it again. Actually you can go though the whole firmware flashing without having the RF deck connected but I recommend having it because it might want to flash the FPGA on the RF board, too. but for troubleshooting you can disconnect it. There are two 12.2V rails that are the mother of all the other voltages. 1.8V, 2V, 4V, 5V and 3.3V the rest of the voltages do not start until the instrument is up and runs the application |
| brainstorm:
Interesting, can you send me that EEPROM dump? What you mention seems like cal data... it'll help me understand as I go through the EEPROM function callgraph as I recover this repair work: brainstorm at nopcode dot org I am not 100% sure the rails are the problem, but what I know is that the SuperH4 CPU has all the clock signals, the READY signal shows up but it seems to be rebooting all the time... I did remove the RF deck entirely during all tests, so only working on the main board + display: it flickers on power up and that's it so far, worked well before... what else do you reckon it could be? Perhaps I should revisit the caps near the RAM chips, I might have knocked them off making the system unstable :/ Any sound way to know if the RAM ICs are fine? |
| analogRF:
one thing I learned is that your power supply must be able to deliver at least 2.5-3A current (at 13V which I used) otherwise the system reboots randomly at various stages. Just during the boot I think it took up to 2.2A and later on during normal operation sometimes based on what operation you do it would take surge currents up to 3A or more. If the power supply cannot deliver it and drops its voltage, it will reboot. This thing draws some surge currents (pulse) for a short time that you will not see it on the power supply display. So I finally ended up using an Agilent supply which could deliver 4A and I used it at 13V. The instrument sticker also shows it needs 12V-15V@4A. The original adapter of this unit is rated 12V@5A. I thought that kind of current is only needed if you have a battery that needs charging but I was wrong, even normal operation with no battery still needs some large currents also if it "flickers", maybe it is the backlight driver or the power supply rail that goes to the backlight driver. The capacitors look high quality and I hardly think they are bad unless they have leaked. Take the power supply shield off and measure at the big inductors. You must have the 12.2V (I think at two of them IIRC), 1.8V,3.3V, 5V, 4V and I think 2V. but 2 or 3 of them do not have anything because they dont come online until later. |
| codex0:
RE what is stored in the EEPROM, the user manual states: EEPROM This memory stores the model number, serial number, and calibration data for the instrument. Also stored here are the user-set operating parameters, such as frequency range. During the master reset process, all operating parameters that are stored in the EEPROM are set to standard factory default values. RAM Memory This is volatile memory that is used to store parameters that are needed for the normal operation of the instrument along with current measurements. This memory is reset whenever the instrument is restarted. External USB Flash Drive This memory may be selected as the destination for saved measurements and setups for the instrument. You can also copy the contents of the internal disk-on-chip memory to the external flash memory for storage or data transfer. The external Flash USB can be reformatted or sanitized using software on a PC. Refer to the Chapter 4, “File Management” for additional information about saving and copying files to the USB flash drive. Compact Flash Card This memory may be selected as the destination for saved measurements and setups for the instrument. The external Compact Flash Card can be reformatted or sanitized using software on a PC. Refer to Chapter 4, “File Management” |
| Navigation |
| Message Index |
| Next page |
| Previous page |