333 552 system automation

Just wondering if the new 300 series streamer speaks to a 552 to select source and control volume. The 333 has two remote outs that I read are optical. The 552 has an rca control input. Can a 3.5mm to rca still work to allow system automation between 333 and 552, and are both the remote outs on the 333 both optical?
Thanks in advance, Mario.

The New Classic system automation uses dual purpose 3.5mm sockets which can accept either optical or wire cables. Use a standard wire cable as you would for the old Classic series system automation and it should work for volume and input selection.

3 Likes

Great that makes sense, thank you.

I suppose you want to use the 555 remote. As said this is possible but if you have a 332/350 setup there is a cost. The auto shutdown after 20 minutes will not work if you have an old streamer attached. Then you will have to enter standby manually from the front of one of the 300 devices or the remote.
On the other hand you get the possibbility to only use one remote when the system is playing.
Claus

So I have the 333 and 552 now set up and there is still a glitch. Mute and source selection works as it did with the nd5xs2, but the volume is very slow to move up and down, really slow, and it even keeps going slowly for a few seconds after youve stopped pressing either the up or down key. Both the app and the supplied 333 remote make the volume act this way.
Is there some setting in the app, or could it be that the 3.5 optical sensor is not compatible with the 552? Would appreciate some help, not much info in the supplied manual. Maybe @NeilS can help with the compatibility between 552 and 333. Thanks, regards Mario.

You’ll need to bring me up to speed Mario - you had an ND5xs2 previously, that worked fine with the 552, including the volume?

Regards
Neil.

Hi Neil, yes exactly right, I had an ND5XS2 and it was connected to the 552 with a 3.5mm to rca cable. All worked well via the app with the volume on the 552 moving smootly up and down.
Upgraded to the 333, used the same cable between it and the 552 and the volume control is extreamy slow up and down, so slow that you bearly see it moving but it does. It also keeps moving at its very slow rate after you stop pressing the vol up or down button for a couple of seconds where the ND5XS2 stopped immediately.
I’ve currently disconnected the cable in fear of something being wrong and dont want some volume malfunction causing damage but Im concerned my new steamer has a fault. Im also assuming both the 3.5mm remote sockets are the same and have only tried one.
Thanks

Ok, thanks for the extra info.
I don’t have any direct experience of using the RC5 link between those two units, but leave it with me & I’ll ask some questions.

Regards
Neil.

And to answer your question - yes, both 3.5mm remote out sockets perform the same function, wired & optical.

1 Like

Thanks Neil, sadly I seem to have another problem. For some reason, after I turn the 333 off via the front standby button or the app standby, the unit keeps clicking every 10 seconds instead of powering down and remaining quiet. It sounds like some relay attempts to power back on. I have a 40 second video but I can’t upload it. I’m a little concerned that my new streamer may have some issues. Sorry to give you another issue before you’ve even had a chance to look at the first one, but it’s all a little worrying. Regards. Mario.

OK, I have a bit more info on the ticking thing. If anyone else has a 333, I’d really like to hear from you.
So if I hold the power button for about 3 seconds to power it off, it powers down fully and is totally silent leaving only the standby button lit. If I just touch the button for a second, it powers down, but clicks even 10 seconds which does seem peculiar. If I just walk away, it powers down by itself in 20 minutes and is also silent.
Now with the “3 second hold” power down, it reboots the whole thing when you restart, but with the self power down after 20 mins, it powers back up with the opening of the app. I just don’t get why it is clicking constantly with the quick press of the standby button. There is mention of 4 power levels in the manual, but no mention of the clicking sound.

Hopefully someone can shed some light on this and the RC5 thing with the 552.

Thanks, Mario.

Sounds to me like you may have a faulty relay. Obviously there should be no repeated clicking, just a single click as the unit switches on or off.
Other than that, I think your streamer is functioning as intended in terms of switching. The different standby modes can be a little confusing, and do not, of course, apply to the 552, although they would if you had a 332.

Ok I have figured out the clicking thing. In the app there is a setting that says “server mode” when I activate this, the clicking stops when powering off. I remember in the set up, I was asked if I want to set up the 333 as a server and I can’t remember what I chose. Any way, this must refer to the power mode that is called “standby mode with additional power requirement” so any way, all seems fine now.

Sorry for the diversion, now just need to work on the slow volume with the 552. I wonder if the pin on the 3.5mm plug may be too long or short? It did work very well with the ND5XS2 though.

Thanks again so far. Over to you NeilS.

You still shouldn’t get that clicking just because server mode is enabled, so a solution to that would be good.

Hi Chris, no the clicking has gone with server mode enabled. Problem solved.

Now just need to resolve why the 552 volume moves so slowly when the remote cable is connected between both.

Ah, yes, so server mode prevents the streamer from going into network standby mode as it requires the use of the main transformer, so it’s just hiding the clicking problem.

My NSC 222 behaves much the same. I’m not sure if it’s a fault or intended behaviour. Maybe I’ll call my dealer about it.

Hi Chris, it’s not a fault. It is looking for something else to power and can’t find it, so it attempts to do so again. Thats why one of the power modes is described as “standby with additional power requirement” in the manual.

How old is your 552? There was a modification introduced in April 2012 to address wired RC5 stabilty.
It should have been implemented on all units manufactured after that date & retro fitted to all units returned to Naim for repair/service.

Regards
Neil.

1 Like

Hi, I’m not sure I understand what you mean by this.
When the streamer is in standby mode, it normally has the main power supply turned off (largely to comply with EU rules on energy efficiency) and a small SMPS takes over to keep it discoverable by the app and remote control. What’s meant by “standby with additional power requirement” is that if server mode is enabled, or if a USB drive is attached, the streamer keeps the main power supply on, otherwise there would be insufficient power to run the UPnP server and USB drive.
If you’re hearing a repeated clicking sound of (presumably) a relay I don’t believe it is due to the device searching for something to power. If it was, surely enabling server mode would not silence it.
Anyway, I’m sure Neil will be best placed to diagnose this. My money is on either a faulty relay, or an RC5 (system automation) problem.

That is my understanding too, although I don’t have server mode enabled.

A longer press on the standby button of the remote appears to put my NSC 222 into Network Standby. It can be woken from the Naim app or remote instantly (no boot up).

A short press on the standby button of the remote appears to put my NSC 222 into Standby. It cannot be woken up from the Naim app, only from the remote. In this power state I get a lot of clicking (of relays?) which is disconcerting and may be a fault.

If I just leave it after playing eventually it appears to go into Standby (I’ve not timed it) and then clicks periodically.

Should I raise a support ticket @NeilS ?

None of this (short and long press) is explained in any of the NC manuals. It does detail the various power modes but not explain how to select them.