3-17 update

Hi Hook,

This morning I updated my NDX with the version 3.17. As other versions, the version 3.17 has its own tonal signature. If you like the 3.16 with its extra high frequency details and "sparkle", I suggest you not to go to 3.17. The latter is more “polite”, with less details and   higher presence of low/mids. I’m a little bit disappointed, because I realize that the version 3.16 was more convenient for my setup.

So it seems that the sonic 'signature' can be tweeked with firmware. I think it would be rather nice if we were given a choice of different versions so we could try them and see which we prefer. It seems obvious that some people are updating their machines only to find that newer is always better, and with no way to go back.

Allen, like you I discovered these sonic changes very early on in beta code and wrote to Naim about it.

My view was that because certain software modules were recoded it would appear they were  sensitive to changes in the sound presentation. It was not neccessaerily deliberate but I a by product of the code change. All Naim told me was that the software was changed for a particular module. The DSP controller module seems sensitive to coding changes.

I am aware of this phenomenon else ware in a professional capacity.

Therefore changes in sound *may* be beyond Naim's control to do anything about as the mitigation may  be electrical/EMI/RFI decoupling as opposed to software.

Anothenr way of looking at it.. Whilst you can hear differences between FLAC and WAV there is a risk that code changes might affect the sonic presentation albeit subtly.

Simon

Allen.. I have edited my post.. The view was my view as opposed to Naim's view that I might have inferred...

Simon

FWIW I have updated to my NDX -> NDAC/555PS to 3.17. Yes there is a slight difference in presentation. Not worse or better, just different, a slight more lowermid bloom and a little more prominent kick.. Noticeable just now on some live concert tracks of the Clash, which I was listening to just before the update.. But it is subtle and doesn't really bother me as you get used to the new sound quite quickly... The detail, imaging and timing are all the same which are the important bits for me.

Simon

Thanks a lot for the warning Allen!  Given such severe consequences, I wish that Naim had expressed a greater tone of urgency in the post announcing 3.17.  Will get this done today.

ATB.

Hook

Yes, thanks Allen... Your warning prompted me to do the firmware change.

Simon

Anybody tried it on the NDS yet? 

Or is it not advised to do the update on the NDS?

I'm really curious.

Stefan :-)

Guys,

The Fault 36 "error" is simply down to a timing limits change in one portion of the 3.16 code rather than specifically being a fault with the unit itself.

3.17 contains updated code to fix this issue for all devices *EXCEPT* the NDS as the NDS code that has the updated timing limits in it has not yet been passed / approved by our listening panel however rather than delay the update for everyone 3.17 was released so that any units with a fault 36 issue could be sorted out.

We are exchanging NDSs with a fault 36 simply because the updated code to resolve the issue isn't available at this time however we hope that the updated code for the NDS will be quickly approved by the listening panel then any units will be resolved by a simple software update.

The author of the updated 3.16 code that caused the problem initially is - at this time - being tortured on a medieval rack that we keep out back for just such occasions.

Phil

I still don't understand what the Fault 36 "error" is. I'm curious now; can anyone explain? Thanks!

Hi,

you can find information about "fault36" here:

https://forums.naimaudio.com/displayForumTopic/content/18461704839636081

and here:
https://forums.naimaudio.com/displayForumTopic/content/15927322084999896

regards
Thomas

Thank you for the reply, but I couldn't get your links to work.

Please see my post above which should explain *EXACTLY* what the "Fault 36" error was caused by...

Cheers

Phil

Oh, yes, I read that but I didn't understand what you meant by timing limits change. Apologies—can you expand a little for the technically illiterate. Thanks!

All digital circuits have various clocks and other timing circuits that allow the various components to keep in sync with each other. With these clocks there is a point where you have to say "That's too slow" or "that's too fast" and deduce that there is a problem or an issue.

The "Fault 36" error was caused by a test on a timing signal that was overly strict and reported a false "Fault" condition.

Regards

Phil

Anyone else having issues to upgrade (Uniti2) to 3.17?
I get stuck in Analysing Setup Window with
"Product Model: Not communicating".
My PC(Win7 64bit) and Unit2 LAN connectivity to DSL Router is fine.
CP210x Windows Driver installed for USB <--> Mini-USB connection.
Any ideas for troubleshooting?

Thanks

Thomas

Phil thanks .. That makes good sense for the technically literate as well... BTW have you let the culprit off the rack yet.. He/she is probably about 12 inches taller by now.

Simon

*chuckle* Ironically he is in reality 6ft 5 already!

Phil

Hi Thomas,

Have you made sure that you've power cycled the unit immediately before doing the update? We turn off the port 60 seconds after power up unless a firmware update keeps it open.

Also are you sure that you are selecting the correct COM port?

Cheers

Phil 

Hi Phil,

I have to check with another PC. CP210x Windows Driver has not yet been correctly installed.

Thanks
Thomas