Electronics > Repair

CMU200 Rohde & Schwarz hangs during BaseDiscoverOptionsBegin

<< < (7/9) > >>

Bicurico:
Update:

Swapped DIGITAL board with a known good unit --> same error message! This is NOT related to the DIGITAL board...
Run scandisk and defrag from Service Menu --> No issues found
Swapped HDD with one of another CRTU --> device booted OK, but with fW 3.x instead of FW 5.x (which was active on that HDD -> because of compatibility with Windows 2000 partition)
Went inside Service Menu and installed "Another FW", selecting an alternative FW5.x version (less options installed) --> device boots OK on the original HDD

Conclusion: I think some file/data got corrupted and reinstalling the FW fixed it?

Strange...

Regards,
Vitor

Bicurico:
Another update:

It is not the HDD or some file corruption.

Activated the original FW5.x with many options and the error comes up again!

So now I come to the conclusion that this error is related to some hardware option that got broken. If the FW does not have support for said option, the unit powers up ok.

Back to FW 5.x with just the GSM option, the device works ok.

Since I swapped the DIGITAL board, it must be some other board/module.

This is a 83 unit. The other broken unit I have is a 82 unit, so I cannot swap all boards, as they are different. I don't want mess with the other working units (CMU200 and CRTU 82).

I don't suspect the RXTX board at this moment.

However, I would be grateful for any idea regarding which board/module might be malfunctioning.

As I really only use this CRTU for spectrum and signal generator, I will leave it as is for now until new ideas come up.

Regards,
Vitor

niconiconi:
I also encountered a similar problem, and the TL;DL version is: Be aware of the bad IDE ribbon cable!

While replacing the HDD with an SSD, I encountered the hang-on-boot issue on my CMU200. If the hard drive bracket was not screwed in, the boot always succeeded. But as soon as I screwed the bracket in, I had a hang-on-boot problem, sometimes with random system error messages!  :wtf: :wtf: :wtf: It turned out that the SSD enclosure was little bit shorter (or longer? I'm not sure) than the equivalent HDD, so when the hard drive bracket was fully mounted, it put a lot of stress on the IDE ribbon cable and bent it to a sharper angle, causing an intermittent electrical connection, creating the random hang-on-boot issue. If anyone else has similar issues, I think it's a good idea to also check the IDE cable - one way to test it - unscrew the hard drive bracket, flip the HDD, and let the HDD sit on top of the screen with the PCB pointing up (be careful not to accidentally hit or short the HDD while it's spinning), and see if the boot succeeds. If so, the IDE cable is bad. If system failure is mysteriously fixed after removing and reinstalling it back, this can be a reason.

Another issue I encountered was a black-screen-of-death problem when entering Version Manager (even with the original disk), it really drove me crazy - I don't have any of the original installation medium! Scandisk didn't help. But my PC intuition told me it was likely a software compatibility problem, and it could be fixed by using the most ancient way to access the disk. First I entered BIOS and tried setting the HDD access mode from Auto to CHS, and set its speed to PIO 0, the slowest configuration possible. But it just led to an error on boot - CHS is too ancient, so I changed CHS to LBA. And the Version Manager came back to life. So, LBA + PIO 0 is also worth trying.  :-+ The side-effect is an extremely slow disk access, but it can always be changed back after troubleshooting.

Radiosonde:
Hello
I now have a CMU200 with a similar problem:
The unit boots up, which it does really slow, if I want to go into "Version Manager" it just shows me a black screen until i turn it off again.
If the unit comes on eventually everything seems to work, altough the cursor sometimes lags, but when I turn on "spectrum analyzer" the CMU shows me a red warning which says:

System Error
....
Filename: tsk.cpp
Line: 2146
....
Add. Info
Str: ISR_C:HWIRQ::get_actual_stack_frame_number()

Can anyone give a hint on what this exactly means?
Help would be very much appreciated.

Ice-Tea:
With such erratic behaviour I would firstly:
- check all ribbon cables. A lot of people have been bitten by badly inserted cables, and there are a lot of them
- the "computer board" (which is right behind the display) sometimes suffers from worn out capacitors. Check them. That would fit rather well with bad boot behaviour.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod