Jun 27, 2023 at 12:30 PM Post #15,032 of 16,946
Just tried to update my firmware to 2.15 and received the below error message. Re-downloaded from the Smyth website but the same problem recurred. I haven't had any firmware problems in the past, and am currently on 2.12. However, I have an original early (89) hardware version of the A16 (16 channel rather than 24) with the DTSX and Auto software upgrades. Has anyone else had problems with the new firmware? Any advice?

error message.jpg
This might be a silly question, but have you unzipped and copied the FIRMA001.SVS file into the Realiser directory of your micro-SD card? Also, if another file of this type was already present, have you deleted it?
 
Jun 27, 2023 at 11:46 PM Post #15,035 of 16,946
I have a brand new (received 1 week ago) A16 that was running great until 2 nights ago. It’s now throwing “Error Code 003” whenever I attempt to reload either Preset A or B. I see “wait” for quite a few seconds, then a blank, then eventually the red error screen.

I’ve reloaded the firmware (2.15 is required since it has the new ARM processor motherboard), as well as done the full system reset. Lots of power cycles, etc.

Any clues? I have mail into James so waiting on advice from Smyth. I know Error Code 002 requires factory service (“simple soldering fix”) but haven’t found a description for Error Code 003.
 
Jun 28, 2023 at 12:25 AM Post #15,036 of 16,946
I have a brand new (received 1 week ago) A16 that was running great until 2 nights ago. It’s now throwing “Error Code 003” whenever I attempt to reload either Preset A or B. I see “wait” for quite a few seconds, then a blank, then eventually the red error screen.

I’ve reloaded the firmware (2.15 is required since it has the new ARM processor motherboard), as well as done the full system reset. Lots of power cycles, etc.

Any clues? I have mail into James so waiting on advice from Smyth. I know Error Code 002 requires factory service (“simple soldering fix”) but haven’t found a description for Error Code 003.
I vaguely remember a case where someone could not load the presets anymore and the cause was that somewhere a PRIR or HPEQ was missing or a somehow invalid or corrupted PRIR or HPEQ was used. Can you try to select 2 presets for A and B that have not been changed yet by you, that use listening rooms that have not been changed yet by you? And maybe check that indeed facory HPEQs are selected in those presets, and in the selected listening rooms that virtual speakers (from factory PRIRs) have been selected for all required channels? If those presets work then carefully check your own presets and listening rooms for anything missing.
Beware: even if you don't use the B part, it must be setup properly or things won't work as they should!
 
Jun 28, 2023 at 10:33 AM Post #15,038 of 16,946
I vaguely remember a case where someone could not load the presets anymore and the cause was that somewhere a PRIR or HPEQ was missing or a somehow invalid or corrupted PRIR or HPEQ was used. Can you try to select 2 presets for A and B that have not been changed yet by you, that use listening rooms that have not been changed yet by you? And maybe check that indeed facory HPEQs are selected in those presets, and in the selected listening rooms that virtual speakers (from factory PRIRs) have been selected for all required channels? If those presets work then carefully check your own presets and listening rooms for anything missing.
Beware: even if you don't use the B part, it must be setup properly or things won't work as they should!
Thanks - your suggestion was worth a try, but unfortunately no luck. I also did the full factory reset and watched as it rebuilt all of the listening rooms from the BBC factory PRIR, and I made sure to use the factory HPEQ, but same result.

I heard from James this morning: “Unfortunately this is a problem with the DSP soldering, and your unit will need to be returned.”

It seems repeated/unfixable Error Code 003, like 002, needs a resolder of one or more components.
 
Jun 28, 2023 at 10:47 AM Post #15,039 of 16,946
Another question on the new firmware. The Auro and other upmixer options now appear in the second page of the presets menu - but not for the “B” headphones. Anyone else seen this? Is it a feature or a new software bug?
That is not a bug. The Dolby and DTS upmixer options likewise were always only in the user A preset menu. It is common sense that both the user A and B part always work in the same listening mode and use the same upmixing options. There is one part of the A16 that does decoding (if applicable, that is for bitstreamed audio formats) and upmixing (if wanted) and delivers a number of channels of audio to the next part: the speaker virtualisation. Only that latter part is implemented completely double, for each of the two user A and B parts. It has to be, otherwise you can not support both users with an independently personalised speaker virtualisation.
 
Jun 28, 2023 at 11:25 AM Post #15,041 of 16,946
..................... I heard from James this morning: “Unfortunately this is a problem with the DSP soldering, and your unit will need to be returned.”

It seems repeated/unfixable Error Code 003, like 002, needs a resolder of one or more components.
If somehow this can be a consolation, your trouble has brought a new piece of information to Realiser A16 owners, that Error Code 003 also means a problem with the DSP soldering.
 
Jun 28, 2023 at 11:26 AM Post #15,042 of 16,946
That is not a bug. The Dolby and DTS upmixer options likewise were always only in the user A preset menu. It is common sense that both the user A and B part always work in the same listening mode and use the same upmixing options. There is one part of the A16 that does decoding (if applicable, that is for bitstreamed audio formats) and upmixing (if wanted) and delivers a number of channels of audio to the next part: the speaker virtualisation. Only that latter part is implemented completely double, for each of the two user A and B parts. It has to be, otherwise you can not support both users with an independently personalised speaker virtualisation.
Thanks for such a clear explanation - makes sense.
 
Jun 28, 2023 at 11:35 AM Post #15,043 of 16,946
Another question on the new firmware. The Auro and other upmixer options now appear in the second page of the presets menu - but not for the “B” headphones. Anyone else seen this? Is it a feature or a new software bug?
In addition to the clarifications posted by @sander99, you can read at the beginning of page #4 of the latest update instructions that “Auro‐3D is enabled and configured within the A16 User‐A PRESETS”.
 
Jun 28, 2023 at 12:24 PM Post #15,044 of 16,946
If somehow this can be a consolation, your trouble has brought a new piece of information to Realiser A16 owners, that Error Code 003 also means a problem with the DSP soldering.
Happy to help, but I may be in a different mood after paying for shipping :relaxed:.

Lead time was really fast - 20 days from when I gave the OK to James to when the new unit arrived. I would have been happier if the unit had gone through an extra 10 days of burnin to catch this.
 
Jun 28, 2023 at 1:07 PM Post #15,045 of 16,946
Happy to help, but I may be in a different mood after paying for shipping :relaxed:.

Lead time was really fast - 20 days from when I gave the OK to James to when the new unit arrived. I would have been happier if the unit had gone through an extra 10 days of burnin to catch this.
I’m aware that the inconvenience comes from the need to send the device back, which means complications when going through customs.
 

Users who are viewing this thread

Back
Top