"Soundscape X: unit communication error!
DSP FUNCTION ERROR CODE: XXX
(The semaphore timeout period has expired, (121))"

This message is displayed when the ssEditor program lost communication with the SSHDR1/R.Ed/SS32 unit.
The function error code number is only intended for us to find potential software bugs. The number can't help to trace a potential hardware error. It only tells us during which command the communication got out of sync, e.g. "DSP FUNCTION ERROR CODE: 110" means that this happened while ssEditor was asking the unit for the current locator position. In general, it does not say a lot, unless it is always the same number that shows up, as a result of a specific user action that was done. In that case, it could lead us to a potential software bug. Let us know if this is the situation.

In most cases, however, users get different function codes at random times, which means that it is not a software bug, but a hardware or system configuration failure.
If you experience different function error codes, then the actual meaning of the code is irrelevant since it means that there is something wrong with the SS hardware, connections or system configuration.

There are a lot of possible reasons for this error message to show up. In most cases, this is the cause & remedy, in no particular order:-

Note: If you have change nothing in your setup, & these error messages suddenly appear, and points 6b...9 are most likely remedy (*).

Note: The easiest way to determine whether the error is caused by the SSHR1/R.Ed/SS32 hardware or PC setup is to temporary run the unit on a different PC if possible.
If that works ok, then the likely cause is one of points 1…3 described below.
If it does not work reliable on a different PC either, then most probably the cause is as described in points 4...9.

1. The selected unit PC i/o address range for ISA Host interface card (default 250-257 hex) is also used by other PC hardware.
Note that this is not always notified by Windows' Device Manager. Note: does not apply to PCI or EPP Host Interface.

Select a different base address (e.g. 240 hex, 260 hex or 270 hex). Make sure that the DIP switches on the SS host interface ISA card are matching the new selected address.

2. Other software on the PC is accessing the unit i/o address range for ISA Host interface card (default 250-257 hex).
This causes the ssEditor/SS hardware communication to become out of sync. Note: does not apply to PCI or EPP Host Interface.

1: Try to remove other software (programs/drivers) until the problem goes.
2: Select a different base address (e.g. 240 hex, 260 hex or 270 hex). Make sure that the DIP switches on the host interface card are matching the new selected address.

3. The SS host interface ISA or PCI card is not fitted properly in the PC slot.

Refit the card in the slot.

4. The SS host interface ISA card DIP switches that select the i/o base address have bad contacts. Note: does not apply to PCI or EPP Host Interface.

Move the switches a couple of times back and forth, and then reselect the i/o address.

5. The SS host interface ISA card jumper settings for IRQ and DMA are conflicting with other PC hardware. Note: does not apply to PCI or EPP Host Interface.

Since SSHDR1/R.Ed does not use IRQ and DMA, remove all jumpers on the ISA card.

6.a The host cable to the unit picks up mains power spikes or surges (especially ribbon type cable).

Move the cable away from any potential source that can cause radiation into the cable.

6.b The host cable to the unit is not fitted properly, or has bad contacts. (*)

Fit properly, or clean contacts both ends with a good electronic contact cleaner.

7. The Unit 1-2 selection switch at the rear panel has bad contacts. (*)

Move the switch a couple of times back and forth, and then reselect the proper setting.

8. The unit has bad contacts somewhere inside. (*)

Pull the power lead out. Take cover off the unit and clean/re-fit ALL connectors. – clean with a good electronic contact cleaner - don't spray with crap stuff - use rags around where you spray to stop it spreading all over the place ..... Clean EVERY internal connector (including DC Power connectors and HDD jumpers) by carefully unplugging, spraying sparingly, and re-plugging a few times each, which should remove any residues.

For Red/SS32: You may have to remove Sync Board, Host Board, & Analog Board to gain access to all connectors.

For HDR1+: You may have to remove the Analog Option (which can be tricky) & SSAC1 Accelerator Card; clean SSAC1 pin connector to motherboard and connector to 'spidery wiring', careful not to break wires ....

 

9. The SDisk is faulty, or not compatible, or has bad contacts to the removable drive carrier. (*)

- To find out whether this is the problem, remove all SDisks and launch the SSEditor program, build a mixer, press play, do whatever is possible within the program without an SDisk, and see whether the error message still shows up.
Clean the removable carrier contacts, renew the drive carrier and/or frame, or change the SDisk. If you suspect the drive carrier or drive carrier frame, temporary connect the SDisk directly to the motherboard, and see whether the problem goes.

Informative Case August 2004:

3 x SS32 Unit, 3 x Mixpander9 setup: Problem started with irregular "Mixpander 3 communication error"s, maybe every day or so, becoming more annoying.

 

Then the other day these became common, either at Startup, or soon after within a few hours.

 

Mixpanders removed from ini file, and disconnected cables.

 

Then things got worse and almost everytime I received messages at startup, or soon after...

 

"Soundscape Unit3 hardware properties are not compatible (DSP MASK=002301 SIMMS=000003)" or "Soundscape 3 communications error DSP FUNCTION ERROR CODE 130 (The semaphore timeout period has expired (121))"

 

so tried Unit3 as single instance, without  Mixpander: same messages appeared. Having 2 other good units on hand for comparison and guts, I set about tracing the source step-by-step:

 

Removed SDisks - same problem.

Swapped units host cable. - same problem, and other Unit worked fine.

Swapped units PCI host - same problem, and other Unit worked fine.

Removed Analog Option Board - same problem.

Removed TDIF Board  - same problem.

Removed Sdisk Carrier Cables - same problem.

Swapped units internal host Board - same problem, and other Unit worked fine.

Swapped units RAM - same problem, and other Unit worked fine.

Compared Board DC Voltages around Regulator and PSU connections - same as good unit.

Jiggled Lead Digital Power Supply >>> Motherboard - bingo! problem fixed. Inspected pins on PSU - there were some yukky marks visible halfway up 0V pins. Scraped with fingernail, cleaned with good cleaner/lubricant and worked plug on/off a few times, + other end of cable checked as well.

 

So, although all the voltages looked good on a good dig voltmeter, it would appear that a 'noisy' connection to the power supply was the cause of grief.

 

Return to index.