Deep sleep (long press standby button) - network discovery is off & the unit can only be woken with the standby button.
Low power standby (short press standby button) - network discovery is on & the unit can be woken via the app.
Low power standby plus (server mode is enabled or USB device is attached) - main transformer is on, display is off.
Active - full power.
When the unit is at power level 2, it will automatically elevate to level 3 if a USB device is attached. I suspect your unit(s) are erroneously triggering a device connect.
You can confirm this by checking the web interface using the IP address. On the diagnostic page, the āWake up Reasonā field will change to āUSB power neededā when the relays click.
Thanks for this @NeilS . I donāt connect any USB devices to my NSC 222. I do use an audio server on my NAS. I have Bluetooth and Google cast switched off as well. I use an Ethernet connection not WiFi. So Iām not sure why itās being triggered. Iāll check out the web interface as suggested
Thanks Neil, I would have to check when I bought it. The 552 has been back to naim with the wire around the volume pot causing sticking, new rcaās were installed, WBT, but not sure when. The thing is that it all worked perfectly with the ND5XS2??
So if it is at power level 3, and nothing requiring power is connected, will it retry to power up a device that it thinks is attached?
Reason I ask is when setting the unit up for the first time, it asks if it is to be used as a server. I cant remember if I said yes or no, but Im thinking this incorrect choice on my behalf is causing the problem. Either way, its not doing it any more with server mode enabled.
Having said all this, I have also disabled system automation as it was not working correctly with the 552, where my previous ND5XS was fine.
Mabye Chris is right about an issue with the 333ās RC5, and the two problems are related.
Hi Neil, thanks for your response.
Yes I will get Gareth Weller from Westan (Australian naim distributor) to forward you my 552 serial number. Its an early one, but it has been back to the factory at some point and had the rcaās changed to the WBT ones. Just cant remember when, so it may be before 2012.
The ND5XS that the nss333 replaced had no problem driving the volume pot in my 552. Also, mute and source selection work fine from the 333ās remote out, it just doesnt seem to have the grunt to drive the pot, I have sent Gareth a video of the volume dials slow movement.
I have a nait XS in a second system, it has a remote in via 3.5mm socket. Can I use this to check the health of the 333ās rc5 output? Its alot newer than my 552 so I assume it would have full compatibility.
I really appreciate you looking at this for me.
Regards
Mario.
The modification addresses a variation in the base capacitance of the opto-isolator in the preamp. The circuit that drives the RC5 outputs on the ND5xs & 333 are different, so that may explain why one works better than the other.
The Naitxs will include this modification, so worth testing the 333 with it.
OK, I have tested the NSS333 with the nait XS and the same problem/s persist. The volume pot moves ever so slowly up and down, you can hear the pot ticking as it tries to move but it is struggling. Mute and source select work as before. Exactly the same result with the 552.
The clicking problem is still there and I understand that putting the streamer into server mode is just masking the fault. Your last post on that has made this clear, so has ChrisSUās explanations. Iāve only had the unit set up since last Saturday so Iāll be having some more talks with naim dealer and distributor.
I wonder if the volume pot needs a higher power than that provided by the system automation connection. The combined electrical/optical connection is going to be a bit different to the electrical only connection used in Classic and 500 series boxes, so perhaps there is a compatibility issue. Thatās just speculation, though.
Hi Chris, you would have thought naim would have tested this. The 333 is considered better than a NDX2 and will be its replacement, so for those who canāt stretch to an ND555 (me) a NSS333-NPX300 would have been a reasonable place to land. Making it compatible with the still current, and not yet replaced 500 series would surely have been a consideration.
The 333 system automation issue has been identified as a bug & will be addressed in a future update.
It seems like a long volume press is being interpreted as a series of sequential short button presses.
@NeilS Are you saying the clicking in Standby is a hardware fault or can be fixed in firmware? If a hardware fault, will I need to send my NSC 222 to Salisbury?
@NeilS I have just checked these fields. When I put the NSC 222 into Standby the Standby State field switches back and forth every few seconds between LoNa and LoNa+ with a LoNa+ Reason of USB needs power. I donāt have any USB devices connected.
I have discussed another thing that is somewhat similar with support.
When a nd555 is connected to a 332 the auto shutdown stops working. Support says this is normal, but i see this as another fault ssince there is no reason why a connected nd555 should change the shut ddown when no music is playing from the 300 series components, but it does prevent the 20 minute shutdown that works as soon as I remove the analog cable to the 555.
Currently I have inserted the trigger cable again but system automation is disabled in the 555 settings in the app. interestingly this did not change anything all the 300 units still goes into standby after 20 minutes. It seems that iit is the system automation that will break it.
With the 555 being the only source when I played around with system automation I had to lie and tell the streamer that it wis connected to a statement preamp on input 5. This meant that I could use the 555 remote also for volume and mute and the rest of the 555 functions. but this unfortunately stop the 300 standby working automatically. Using the 332 remote or the buttons on the 300s still worked.
Hi Claus, Iāve had a look over the helpdesk ticket you raised & Iām not 100%, but I think the agent may have misinterpreted what you were saying.
Iāve managed to recreate the issue today & I agree, it doesnāt seem right.
Iāve lodged a query with the software test department to assertain whether itās a legitimate limitation, or an overlooked bug.
Iāll report back.
