Devialet Chat

Full Version: D Premier refuses to function as companion / slave
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
Hoping that someone here can help me sort this out.  I recently bought a pair of D Premier units which were configured as dual mono, running firmware 4.1.  The two units have 1 remote.  They are connected by a SPDIF cable.  Both units are running the latest Expert firmware (10.whatever).

One unit absolutely will not function as a slave.  When I download the configurator file and update the unit, it registers as a slave (S1 CONFIG) on the display.  However immediately after displaying "S1 CONFIG" the screen turns off and never turns on.  There is no audio ouput from the right channel.  The unit gets hotter than the main Master unit despite seemingly doing nothing.

I have tried making new configuration files, adding and removing a trigger cable, re-doing the firmware updates, and nothing works.  One time it did work - for about 5 minutes - and I had real stereo output, and then I tried changing the source and the Slave turned off and never turned back on.  And yes, before it is mentioned, I do have the speaker cables plugged into the positive terminals only.

I can configure the Slave successfully as a standalone D Premier and it works fine.  I can reverse the Slave/Master units, and then both units work in their respective roles, however my single remote is only paired with the one unit and will not function with the units role-reversed.

Do you think that this is a problem with the non-functioning Slave unit, or is this a problem with the digital output from the Master unit?  Would a SPDIF to AES cable be worth a shot?  Alternatively, how can I "switch" my remote pairing so that I can just reverse the Master/Slave relationships and still have a working remote?  I cannot find this anywhere in the configurator app.

Thanks!
If the problem is with the digital output of the 'master' , I can't see how changing the cable can make a difference. It could however be the input on the 'slave' that is the problem so in that case it might work.

To connect a remote to a unit you need to put it on top of the unit in the centre at the back and turn the unit on. I would do this first with the 'slave' as a stand alone unit. You might also want to configure the 'master' to have no remote connected first. It might confuse things when they can both receive input from the same remote.
Just a thought - I wonder whether your S/P-DIF cable might not be working well? Do you have any chance to try a different cable? Maybe a combination of the length of the cable and the sample rate you're using is making the signal at the companion amp a bit marginal... If it's a short cable (less than a couple of metres) and you're using low-ish sample rates (44.1 or 48 kHz) that shouldn't be a problem, but for longer cables and higher sample rates, maybe it is.
Did these 2 units work as dual mono before EXACTLY like this (so using the same spdif cable)? So the only difference is that you loaded fresh configuration files?

Rodney Gold, who was a member here (sadly passed away earlier this year) ran D-premiers as dual mono but had to use a XLR to RCA cable to connect the two. I was always under the impression (maybe mistakenly so) that the RCA to RCA dual mono connection was something only introduced in the newer Devialet models.

The reason why your slave does not work is because the master must send a signal to it to wake it up. The signal is sent via the connecting cable. There is therefore nothing wrong with the slave itself.

Also remember that the spdif cable must be a 75ohm digital cable (and not just a single length of a normal RCA interconnect).
I don’t think the remote will work on the slave alone. This was only possible when amps were upgraded to Pro CI status, whereby the Master and Slave were exactly the same, interchangeable and therefore the remote would work with both.
@Zedeff, you say that the amps were running firmware 4.1 and, if I understand correctly, you upgraded to firmware 10.  Have you tried reverting to 4.1?
Alex is right with remoting the slave unit
Hey everyone thanks! Sorry for my late return as I had an unexpected family disaster that kept me away from the audio system for a bit.

The cable I’m using is a 75 ohm spdif cable and not a bog standard rca.

The two units previously ran in 4.1. I don’t see old firmware on the configurator website. Is it possible to downgrade from 10 to 4? How do I access that? Would really like to try the fabled version 7.

I do have a second spdif cable connected to my CD player. I can borrow that one to try, but would then defunction the CDP. At least it would give an answer.

I will play with it tonight by changing:

1). The physical spdif cable
Then
2). Trying to swap units and re-pair the remote with the slave.

If that works then great, I’m done. If it doesn’t work I will purchase a spdif to Xlr cable to try. If that doesn’t work... anyone have old firmware they can share?

Thanks for the tips!
(28-Oct-2018, 01:40)Zedeff Wrote: [ -> ]Hey everyone thanks!  Sorry for my late return as I had an unexpected family disaster that kept me away from the audio system for a bit.

The cable I’m using is a 75 ohm spdif cable and not a bog standard rca.

The two units previously ran in 4.1. I don’t see old firmware on the configurator website. Is it possible to downgrade from 10 to 4?  How do I access that?  Would really like to try the fabled version 7.

I do have a second spdif cable connected to my CD player. I can borrow that one to try, but would then defunction the CDP. At least it would give an answer.

I will play with it tonight by changing:

1). The physical spdif cable
Then
2). Trying to swap units and re-pair the remote with the slave.

If that works then great, I’m done. If it doesn’t work I will purchase a spdif to Xlr cable to try. If that doesn’t work... anyone have old firmware they can share?

Thanks for the tips!

PM me your email address and I'll email you my firmware versions I've kept over the years.
There’s this too. https://devialetchat.com/Thread-Devialet...re-Archive

The community should really try and keep an up to date archive of all releases, just incase Devialet disappear or stop providing them.

Since they’ve abandoned EVO development for everything preceding CI, they should really open source it to at least partly keep their promise - there would at least be a chance of continued development.
Any other tips on pairing a remote? I can leave the remote on my "Slave" unit (re-config'd as Master) all day long and it doesn't pair. Power on/off with the button, power cable removed and re-plugged... no remote function with the slave.

It was suggested that I "unpair" the former Master unit first, but no instruction was provided for how.

There's no configurator tool for remote pairing that I can see and an email to Devialet's support last week has gone unanswered.

So far it looks like I've got 1 good D Premier and 1 brick.
Pages: 1 2