Skip to main content

Hey guys,

For some time, my 02R96V2 in v2.4 have bugs. Error message "ASSERT File sed1330s.c. Line 397" Everything is frozen and all I have to do is reboot..
From time to time, it also freezes on the FLASH UPDATE menu "Waiting data ..." without any particular action, at boot or in use. In short, the situation becomes critical.

After a hard reset, I launched the check program (display + AUX4) to make a diag, everything is ok except 9: SIO CONNECTION ATSC-> DSP7

Can't find informations on the subject, on these error codes, so I don't know where to locate the problem precisely or if it's serious and especially if it's related to freezes.
Strangely, I never had any worries except since I flashed the firmware 3 months ago.
Coincidence ? In any case I can't longer downgrade to v2.33 to check.

Here, all the repairers are closed with Covid 's containment measures.
If anyone has an idea about this diag or other manipulations, I am interested. For now, I have checked the power supply, the capacitors and the internal cables. I took a look at the diagrams but without interpretation of the error codes or other information, difficult to advance in research.

Is anyone could make a diag of dsp7 to see result on another table ? It would allow us to see the differences.

Any help will be welcome, thanks.

Elias

Comments

Boswell Fri, 05/15/2020 - 09:30

Tricky one, Elias. I have never had to service an 02R96, but I did have a similar problem on my old 01V96, which turned out to be a dry solder joint on one of the DSP pins on the main board. I found that fault by very slightly flexing the boards one by one.

I know the approved Yamaha service agents have full diagnostic capabilities, so it may be a matter of taking it for repair once the lockdown finishes. The service manual for the 01V96 has screen pictures of diagnostic steps that I have never been able to get to appear on the actual mixer screen. I can believe that the same would be true of the 02R96.

Elias Bergam Fri, 05/15/2020 - 21:20

Hi Boswell, thanks for your answer !

Yes, it could be a dry solder joint. I could try to use my hot air soldering station on IC602 and ICB06,7,8.
The service manual is easy to find on the web. The pages that relate to my problem are : part 1 -> 57,60, 155, 156, part 2 -> 29, 33.



I think I've understood the error codes of screen diag about SI29 to 31 and SI44 to 47 of ICB06/07/08.
On page 57, it correspond to ICB07,8,9's pins 100,101,102,119,10,121,122 (CI AUX 1->12 and CIBUS 1->8 + CISM/SL).


So by deduction, on page 60, the 6 pins corresponding on IC602 are 77, 79, 103, 105, 132, 134 (Port B, C, D audio data output SO0 and SO2).

There's no component between IC602 and the 3 ICB so I've tested the 6 connections and everything is ok, no dry solder joint :(



I could try to invert IC601 and IC602 and make another diag but perharps the problem could be before IC602. I'm going to think about all this and try your method by flexing the boards one by one.

Thanks and to be continued...

Elias

SKULL Fri, 06/05/2020 - 00:54

I own a Yamaha DM2000VCM and get similar errors.

However, during actual usage, I find no problems with the board. It doesn't freeze and everything seems to be working perfectly.

I'm thinking that perhaps in order to pass the test, I have to connect the necessary cables for the test bench, according to the service manual.

I think that, because in the service manual of the 01v96 it states that:
1-5. DSP7, SIO, and ATSC2 tests
Contents: Read/Write the register of each DSP6
and DSP7 and check whether the Data
Bus and Address Bus are good or bad.
Read/Write the DRAM and SDRAM of
each DSP6 and DSP7 via the registers
and compare and check.
Check the SIO connection between each
DSP and between the ATSC by the Send/
Receive signal.
If the ADAT cable is not connected during
the DSP7, SIO, and ATSC2 tests, NG is
displayed.

Therefore, I think that the freezes that you experience have a different cause.

Attached files

Elias Bergam Mon, 06/29/2020 - 08:10

Hello Skull,
Thank you for your message and sorry for the late response.
I took the time to redo all the diagnoses.
I have carefully looked at the technical documentation, it's not specified to link the ADAT outputs / inputs to do the tests but...
I think you're right. So I still tried to plug ADAT I/O without much result.

Also, I listened to your advice and I focused on the CPU board. I've decided to do the exchange by a new CPU board. By the way, I recovered the VCM effects :) and since I have no bug or freeze ! Yes !!!

Everything is in order. The SIO ATSC / DSP7 is still NG. There's surely a manipulation to do side wiring but I have'nt found. No problem, I can work again and that's the most important for me.

Anyway thank you very much because your advice allowed me to solve the problem.

Best Regards

Fred

SKULL Tue, 06/30/2020 - 23:21

I'm glad I could help in a small way.

I will still try to fix our common error and let you know if I'm successful or not, even though I do not expect to try before the winter.

My best option would be to replace the DSP board, but I haven't been able to find a reasonably priced used one (or unreasonably for that matter...)

However since both me and my technician like to tinker, we will probably try to fix it ourselves.

Anyway, I'm glad your 02v96 is still kicking!

matteopomeo Thu, 03/24/2022 - 17:09

SKULL wrote: I'm glad I could help in a small way.

I will still try to fix our common error and let you know if I'm successful or not, even though I do not expect to try before the winter.

My best option would be to replace the DSP board, but I haven't been able to find a reasonably priced used one (or unreasonably for that matter...)

However since both me and

I’ve just bought a dm2000 that works perfectly but it shows me that same error. Did anyone of you have found the cause of that fail? And have you noticed any problems because of that error? Many thanks

DM-2020 Fri, 07/22/2022 - 01:32

matteopomeo wrote:

SKULL wrote: I'm glad I could help in a small way.

I will still try to fix our common error and let you know if I'm successful or not, even though I do not expect to try before the winter.

My best option would be to replace the DSP board, but I haven't been able to find a reasonably priced used one (or unreasonably for that matter...)

However since both me and

I’ve just bought a dm2000 that works perfectly but it shows me that same error. Did anyone of you have found the cause of that fail? And have you noticed any problems because of that error? Many thanks

I have the exact same error log as SKULL with :

9) sio. Connection ATSC -> DSP7. On a DM2000 v2. Shortly after the test the console froze and with some advice from others online pointed to CPU. I was able to check and do a quick test using a donor cpu from another DM, which proved correct. I didn’t run the DM’s diagnostics again encase it bricked another cpu. I now have a VCM-cpu on order. Further inspection did not highlight any dry solder connection with DSP7 IC’s or the ATSC2 IC. In the service manual for the DM it does state that digital audio, midi tc and cascade cables need to be connected up to loop back in to make I/O tests function, which makes sense. This DM is getting taken completely apart to service some of the panel encoders, switches and LED’s. When it’s all back together with the new CPU board, I will rerun the diagnostics this time with the cables connected up and post back what I see. Also if I get a chance to take the other two DM’s out of service to run these diagnostics too to compare. It is odd that these errors/NG are the same in the case of SKULL and I and very close with Elias with 02R96 (very similar). So it is either  the test/cables not being carried out properly, DSP7 is out until VCM plugs are unlocked or some kind of production fault with the ATSC IC or with the PCB or a combo of the two. On a side track to this, on two of three DM2000 consoles, there’s a track repair exactly the same between two  small IC’s on the DSP board in the back corner very near to the dsp7 IC’s in question. If the two consoles with this both fail at that diagnostic (9) and the other without repair doesn’t,  then is this connected to the issue? I’ve seen others online with the same track repair, so it must be a production fault. Be great to speak with Yamaha engineer, put us all right on this. Or is it just a corrupt CPU board playing tomfoolery with everything! Does anyone know why the CPU boards fail? Mine looks fine, I was considering resoldering everything, but it’s all good, so does an eprom corrupt or another IC that can be replaced maybe and re flashed with firmware somehow? Parts are getting very scarce for these now, how to keep them living on!