Stucked in the middle of production: -38/-50/-51 Error Codes caused by my Twin X MKII QUAD TB3

[derselenit]

Hi all
May be there's a quick win here for my problem here. i contacted support 2 days ago, but it seems that i have to wait. maybe someone can help here ? Got following chain Mac->UAD PCI-e Quad in a Sonnet Case->X6->X8->Twin X MKII all TB 3. Everything was working super tight and fine 'til 2 days ago. I got permanently the -38/-50 Pop-ups on starting the system and then (cause of Authorization error on console control panel and trying to authoroze the plugins) the error -51 on my TWIN X saying that there is a dsp communication error. What i did:
1) Hardware reset as indicated on the homepage -> afgter 2 restart of my mac it worked again, but a the next start same issues came back
2) I Changed TB Cable in the WHOLE System with new ones -> no success
3) Canged chaining order of the systems -> after one restart the system worked, but at the next startup issue came back again.
4) i rechecked ALL security system file access for UAD
5) i rechecked starup-items
6) and yes i did the proposed Power Cycle (Mac First then apollos)

The only thing i've done in the past week was the UAD Software Upgrade to 11.0.1

Is my Twin X dying ? Any help is very appreciated, thank you !

 

[UniversalAudio]

Hi all
May be there's a quick win here for my problem here. i contacted support 2 days ago, but it seems that i have to wait. maybe someone can help here ? Got following chain Mac->UAD PCI-e Quad in a Sonnet Case->X6->X8->Twin X MKII all TB 3. Everything was working super tight and fine 'til 2 days ago. I got permanently the -38/-50 Pop-ups on starting the system and then (cause of Authorization error on console control panel and trying to authoroze the plugins) the error -51 on my TWIN X saying that there is a dsp communication error. What i did:
1) Hardware reset as indicated on the homepage -> afgter 2 restart of my mac it worked again, but a the next start same issues came back
2) I Changed TB Cable in the WHOLE System with new ones -> no success
3) Canged chaining order of the systems -> after one restart the system worked, but at the next startup issue came back again.
4) i rechecked ALL security system file access for UAD
5) i rechecked starup-items
6) and yes i did the proposed Power Cycle (Mac First then apollos)

The only thing i've done in the past week was the UAD Software Upgrade to 11.0.1

Is my Twin X dying ? Any help is very appreciated, thank you !

While you wait for Support.

I'd start by using just one unit at a time, then add another and see when/if it breaks.

 

[derselenit]

Twin breaks when connected as single unit

 

[derselenit]

so this is interesting: After getting the error messages and then let the Apollo powered on for about an hour or more the dsp error communication disappears and it'll stay connected. as if it has to heat up for ... when doing a restart of the system in this "heated" state it connectes well. But if i'm doing this after a night powered off the issue is back...