Trigger cable lowers temperatures & power consumption

[Fairvsfree]

Fairvsfree
[*]Nearly there! Just to get it right: should the settings for the digital cable remain untouched totally at all times? In the settings the option 'Chaining Input' is switched off standard. Should this stay this way?


Yes, don't change it. To be sure, don't open it at all.

Also, make sure you do all the settings before first file save. Based on my experience, after leaving configurator and come back to the same configuration, companion configuration file is broken (even without changing anything!). So, you must start from zero every time...

[*]
Thanks! Did like you told. After coming back in the configurator and trying it out I noticed that the behaviour is kind of odd. I also wasn't able to uncheck the 'Chaining Input' once it has was switched to 'checked'...

[mdconnelly]

I just receive Devialet confirmation for stand by / power off behavior:

"The use of trigger cable affects companion temperature in standby and power off modes; does not affect the master temperature:

• Without trigger cable, companion is substantially hotter than master.
  
• With trigger cable, companion has the same temperature as master.
  

This is the expected behavior indeed.
The trigger cable allow for deeper sleep mode of the companion (on top of allowing for the use of its inputs)"

Wow, that is really interesting information.  I'll give it a try soon.   Given this, why would you not always just use a trigger cable?

I'm amazed that after owning my 440 Pro for over 3 years, this is the first time I've heard the lower Companion temperature issue acknowledged by Devialet (although it has been brought up many times before).   I truly do not understand why Devialet doesn't share information like this.  It would be great fodder for that Newsletter they've promised for ages but never delivered.

And, regarding the issues with the online Configurator... has Devialet acknowledged this?  Have they hinted at getting it resolved?    I've also experienced these problems and have found myself tip-toeing through all config changes hoping it'll work.  I do start with a new config, but invariably I'll forget one setting or another.  Sometimes going back in to add/update a setting works.  But often, it fails such that I have to start all over again.   I have a feeling it is all about what order settings are changed but damned if I know what it is.   There must be a better way.

[daniel.avasilichioaei]

And, regarding the issues with the online Configurator... has Devialet acknowledged this?

Yes, Devialet is aware about this issue. Also, it is aware about multiple other issues about configurator. Still, nothing changed till now.
Configurator works fine for single unit (as far as I know). But, it has multiple issues for dual mono, on companion configuration file.

In fact, the problems are in a larger area than the configurator: I suppose that the ideal way would be master send the setting to companion in real time (via communication channel - digital or trigger). But this is also not working properly (some settings only are sent), so...
Check this post: https://devialetchat.com/Thread-Bug-for-...-dual-mono

[Axel]

I just receive Devialet confirmation for stand by / power off behavior:

"The use of trigger cable affects companion temperature in standby and power off modes; does not affect the master temperature:

• Without trigger cable, companion is substantially hotter than master.
  
• With trigger cable, companion has the same temperature as master.
  

This is the expected behavior indeed.
The trigger cable allow for deeper sleep mode of the companion (on top of allowing for the use of its inputs)"

Wow, that is really interesting information.  I'll give it a try soon.   Given this, why would you not always just use a trigger cable?

I'm amazed that after owning my 440 Pro for over 3 years, this is the first time I've heard the lower Companion temperature issue acknowledged by Devialet (although it has been brought up many times before).   I truly do not understand why Devialet doesn't share information like this.  It would be great fodder for that Newsletter they've promised for ages but never delivered.

And, regarding the issues with the online Configurator... has Devialet acknowledged this?  Have they hinted at getting it resolved?    I've also experienced these problems and have found myself tip-toeing through all config changes hoping it'll work.  I do start with a new config, but invariably I'll forget one setting or another.  Sometimes going back in to add/update a setting works.  But often, it fails such that I have to start all over again.   I have a feeling it is all about what order settings are changed but damned if I know what it is.   There must be a better way.

I also had problems making changes to an existing configuration, and had to start from scratch with an “anonymous” setup. I took screenshots of each stage for future reference. Luckily, I haven’t had to change config for quite some time as I haven’t made any changes to my system, but I’ve still got all of my screenshots, just in case. 

[flohmann]

OK, I've read the entire thread, and figured it might be nice to digest our collective wisdom for others so they don't have to read the whole thing. Near as I can tell, here's where we are: 

1. Devialet has now confirmed that use of the trigger cable, if properly set up in the Configurator, will result in the Companion running cooler

2. The difference is a few watts and a few degrees C when Companion is in standby or "off" (do we have consensus about when "on"?)

3. The use of the trigger cable makes very little or no impact on sound quality

4. Getting the Configurator to do this can be tricky, see instructions from daniel.avasilichioaei in post #94. You need to enable at least one input on the slave unit to activate the trigger function. The cable goes between “Trig” on the master, and “Optical” on the slave/companion, NOT trig to trig.

5. If you connect your units via RCA-to-AES, then you can't activate the trigger cable in Configurator, so none of this applies to you. 

Did I get it right?

[flohmann]

Thanks @alaw, I updated my summary to reflect these additional nuances.

Can anyone out there confirm whether the temperature change applies to 1000/Od'A units?

[thumb5]

I'll try it as soon as I can and will report back here.

[deviousalet]

The temperatures bounce around a bit. Maybe I should leave them on for a while to stabilize, but here's what I saw quickly switching configurations from a cold start:

Triggered: Master 22/20/28, Slave 21/19/27
no trigger: Master    22/21/29, Slave 23/21/29

So you can see that, on my 1000, the trigger reduces the temperature of both master and slave.

[daniel.avasilichioaei]

The temperatures bounce around a bit. Maybe I should leave them on for a while to stabilize, but here's what I saw quickly switching configurations from a cold start:

Triggered: Master 22/20/28, Slave 21/19/27
no trigger: Master    22/21/29, Slave 23/21/29

So you can see that, on my 1000, the trigger reduces the temperature of both master and slave.

You must wait for a pretty long time, in order both units to reach room temperature. A few hours are enough.
I made the test leaving the units in stand by all night long, and I checked temperature in the morning.
You don't need to measure the temperature: the difference is so big that you feel it with your hand (on the bottom side of amplifier).

I'm sure that trigger cable is doing the job on all dual mono models. It is just "better" then RCA-RCA for sending commands to companion. I don't know if this is a hardware limitation, or it is a software limitation (it can be implemented also for RCA-RCA cable, but it isn't implemented at this moment).

[deviousalet]

After playing music for about an hour (via AirPlay at -40dB), my triggered master is at 30/28/36 and slave at 29/27/35. After a few more hours the master got up to 35/33/42 and the slave to 33/32/40.