1

(3 replies, posted in Aspen Platform)

Treesa,

Sorry for the late reply on this, I've just now had the chance to get pictures taken and write out this little tutorial.

First things first: Open up the Left side panel (facing monitor, panel on left) by removing the air vent as seen in the picture.
http://i49.tinypic.com/34fb33n.jpg

Loosen the screw that is holding the side panel in place, but don't remove it - it just needs the washer part to go past the plastic, refer to picture.
http://i45.tinypic.com/28srdhv.jpg

Pull the side panel away from the system, it will swing out like a door, don't be afraid to pull on it fairly aggressively.
http://i50.tinypic.com/ke6vt4.jpg

Set the side panel out of the way, then loosen all of the screws holding the metal panel on.
http://i48.tinypic.com/2hpj5oy.jpg

Remove the cable at the bottom using a small flat-tip screwdriver.
http://i45.tinypic.com/2z8wwn5.jpg

Once the cable is out, and the screws holding the panel are loose, grab the two handles on the panel and lift up until the circles on the panel line up with the screws then pull it away from the system. With the panel out of the way, you should see the Scanner card cage - these are the boards we want to work with to determine what is causing your issue.
http://i49.tinypic.com/rm0hag.jpg
http://i47.tinypic.com/oky63m.jpg

In the first picture above there is a red arrow pointing to a large power connector. That can be removed to isolate the Scanner card cage from the system entirely. This will allow you to determine whether a board is causing the main problem or not. While the system is OFF, and unplugged from the wall, remove this power connector from the Scanner motherboard. Turn the system on again, and see if it stays on for more than a few seconds.

If it does, turn it OFF, unplug it from the wall, etc. Plug the main Scanner motherboard power connector back in, and unseat all of the RCV, XMT and SDL boards. Those will be found in the 2nd picture above. They are the Red, Black and Green tab boards. To unseat them, you will need to pull the tabs away from the board (one on each side of the board) until it is pulled loose from the motherboard (connected through large amounts of pins). You don't need to remove them fully from the system, just as long as they aren't in contact with the motherboard.

Once this is completed, turn the system ON and see how far it gets. If it stays on for a while and boots up to Imaging, turn it OFF and put all of the RCV boards back in. Repeat this process with the XMT and SDL boards until you see a failure. If you have a failure during one of these trials, take out half of the board types you put back in (if it was SDL's causing the failure, take out half of the SDL's, etc). Keep narrowing it down until you find the culprit.

Now.. if NONE of that works, it is more than likely the main power supply. You can find this on the Right side of the system while facing the monitor. The panel comes off just like on the left hand side. In the picture it is the large metal case with all of the wires going into it.
http://i45.tinypic.com/6qv3a0.jpg

There isn't a whole lot you can do to fix it, unless you have someone who works on component level (ie, finding dead capacitors, burnt resistors). We offer hero kits, along with repaired (warrantied for a year) Aspen power supplies.

Let me know if any of this helps.

2

(3 replies, posted in Aspen Platform)

Treesa,

When you get an error code #2 after the system shuts down, it is usually the main power supply. However, without additional troubleshooting it is hard to tell for sure, because it could be a scanner board or the IOB causing the problem.

Do you have anyone at the facility that would be comfortable with opening up the system, pulling out a few boards and troubleshooting it down to either a main power supply, or a board?

Tung,

You can bypass the boot-up process (power on diagnostics) by holding down the " i " key on the keyboard.

The FEB 06/ FEC 02 errors don't sound like they would result from dead CVC batteries, but the tests associated with those two error codes deal with RAM and pathing.. so it's possible.

However, every time I've seen the battery problem, CVC 08 has been one of the main errors, along with a bunch of INTRNL ERR numbers, and a few of the FEB/FEC/DAQ test failures. I don't recall seeing 06 or 02 amongst those though.

As for sending the board to us, I can help with batteries and soldering, but you seem to know how to do that anyway. Reprogramming isn't something we can do here, unfortunately. I still think your best bet is to get the information from Siemens/Acuson, especially if you're located within the US. If you don't have their number already it's 800 888 7436 - option 2 for technical support.

5

(4 replies, posted in HDI 3000 Platform)

How far does the system boot before the error comes up? Does it get to the normal imaging screen, or does it stop on the screen with all of the color bars, or the gray background?

Are there any board names associated with the BootupTest error code, for instance "CPU MOP reported error" or "FEC reported error"?

Have you had any power issues with the system recently? (system randomly powering down, etc)

The BCX85/3B50 is a three-prong battery, whereas the CR2025 is your standard nickel sized mobo battery.

Tung, did you solder a battery mount for the CR2025? Only curious as I wanted to try something like that for our CVC boards.

I'm currently looking into the OC3 07 issue, but I wanted to find out if you were able to bypass the error and boot to imaging.

As for your questions, Marty - once the batteries are depleted fully, the battery backed RAM clears out. Everything that was "user defined" (this includes the encryption strings that unlock all of the system features) is lost and will need to be re-entered. My recommendation would be to search the system for a piece of paper with a list of system options, and the encryption strings required to re-enable all of your features. If you have that, it's a fairly simple process of replacing batteries and entering strings - then there's the more labor intensive setup for all the presets/applications, etc.

If you don't have the encryption strings, my recommendation would be to call up whoever donated the system, and have them get in contact with Siemens/Acuson - you may get lucky and get in touch with someone who is able to contact a service engineer who will have these strings on file.

Wish I had better news for you. =/

You would need to alter the encryption strings in order to license the c366.

Color doppler not working might be a battery problem... if the batteries are dead and it's not retaining any encryption information.

That might also explain why the c366 isn't working. However.. if you didn't have encryption strings, the configuration page should say something like "Invalid Encryption".

8

(22 replies, posted in 128 XP/10 Platform)

Pacifico,

Go to this part of the UDS forums to remove the "gibberish text" you see when your system boots: Removing text

In regards to the other commands you tried - none of these will work unless you are able to get into the diagnostics menu's. What the Reset-Test does is bring you to a manufacturing command line/shell prompt. If the proper code isn't entered, the system will not respond with the information you want.

The system is probably restore-able,  you just need to replace the batteries on the CVC board, and enter the encryption strings. The batteries are non-rechargeable, so plugging the system in for 24 hours won't do anything. The system needs to either be on ALL the time, or the batteries need to be replaced.

Are you able to access the Configuration Report to see what transducers the system is capable of running?

If not... I honestly don't recall where you would find out on the system. I haven't seen a Rev. 8 system for at least 8 years, and even the Rev. 30 ones are being phased out.

10

(1 replies, posted in Cypress Platform)

David,

You will need to use a USB keyboard in order to press F2. My recommendation would be to turn the system off, hook up the USB keyboard, boot it back on and try pressing F2.

I also want to apologize for the extremely late reply.

As far as I'm aware, the probe changes frequency depending upon the "Depth" it's at. For instance, if you're at 30mm it should be at it's highest frequency, 160mm would put it at it a lower frequency.

Any idea what version of software it is? If you don't have Encryption Strings on the list of options, my guess is it's probably below 20.XXX rev.

13

(1 replies, posted in Sequoia Platform)

Does the disk say anything about revision? 9.51, 12.22, etc.

If it just has the system serial number, it is probably only a back-up of the system configuration/presets/feature control, etc.

This will not work for a software reload.

Chances are it's a dead hard disk, or you may need a software reload.

15

(4 replies, posted in HDI 5000 Platform)

Joe,

I've been asking around with some other techs in the industry, just waiting to hear back. My first guess would be a channel board issue, or the AIM.

Will update more tomorrow.

To everyone who's posted so far.. I apologize for my lack of replies, or for anyone else replying for that matter. Currently I am the main technician for the forums, and until I get some additional help it will take me some time in replying to everyone.

Tito, I will respond to you via email to see if there is something we can do to help you in regards to your issue.

17

(4 replies, posted in HDI 5000 Platform)

Joe,

You can upload the picture to most picture hosting sites (tinypic for example) and copy the "image for forums". Or, if you want to use the image tags (looks like a picture of some mountains with the sun over it, in the line just above the message box when replying).

Honestly, I haven't seen them in the onboard diagnostics menu, but it may be at a deeper level of service than I have access to.

19

(2 replies, posted in HDI 3000 Platform)

My apologies for the late reply.

I will email you the documentation I have for this ultrasound system either later today or tomorrow morning.

20

(1 replies, posted in Sequoia Platform)

Do you have access to the Administrator manual for the Sequoia?

I would recommend going into the Setup menu, and checking through the Cardiac calc options to make sure EF is enabled in A2C and A4C.

21

(1 replies, posted in Sequoia Platform)

The boards are backwards compatible for the most part. Generally speaking you want to match part numbers and board revision levels when doing any part replacing.

22

(2 replies, posted in Sequoia Platform)

Sorry for the late reply again, I have sent you an email in response to your forum PM.

Dr. Stegen,

I saw your emails as well, and apologize for not replying sooner. The end of 4th quarter is always overly busy.

As for the ultrasound system, remove the probes from the system to ensure that they aren't causing any issues with the front end board. Turn the system on and let it run the power-on diagnostics test (the blinking "welcome" bar). If nothing happens after 10-15 minutes, then there could be a failure in one of the EPROMs that holds the system software.

Unfortunately, without having an EPROM reader it will not be possible for you to check the SYSCON chips on the OC3 board to verify that their checksums are all correct.

Basically, EPROMs are integrated circuit devices that retain electronic information on a silicon chip. Over time and continuous use, they degrade, and some sectors of information are corrupted. They will at some time need to be "flashed" or reprogrammed with the original information. An EPROM reader is a device that interfaces with the chip via pin sockets and a computer program designed to make reading/writing information to chips considerably easier. A checksum is similar to a checklist, only it's in hexadecimal format. The checksum will be listed on the top of the EPROM, usually on the Acuson sticker that was first put on the chip. They're 4 digits, alphanumeric.. for example: C6A5. If the checksum of the chip does not match the checksum on the sticker, then there are errors in the chips programming and it will need to be erased and reprogrammed. Most of these EPROMs are erasable, however you will need to remove the sticker and place them under UV light for roughly 30-40 minutes - sometimes this does not erase them entirely, or it damages them permanently.

The OC3 (output controller) is a PCB (printed circuit board) located in the Scan Converter card cage (upper region of the ultrasound system) that houses the 4 SYSCON (I'm assuming this stands for system configuration) chips as well as a few other controlling EPROMs. If any one of these chips fails the system will behave erratically.

Unfortunately... without having more information, I can't tell you for a certainty that the board is the cause of the issue.

If you have a chance to try what I've recommended in the first paragraph, please let me know the outcome and we can go from there.

24

(22 replies, posted in 128 XP/10 Platform)

Of course. We are located in Oceanside, CA. I also work with service engineers in Diamond Bar, and Brea.

Our main number is 800 416 7567 -- I will be in the office today around 8:30.

25

(2 replies, posted in Sequoia Platform)

You wouldn't by chance happen to have a physical/digital copy of the user/admin manuals would you? If not, I can send them to you via email.

Unfortunately, none of us are applications specialists and without doing a bit of research I wouldn't be able to get you an answer until the end of the week. Hopefully that isn't a huge issue.