Meridian Unplugged - Powered by MrTechGuy.co.uk Forums Discussion Meridian - Systems HD621 Odd LEDs behaviour after firmware update

I just finished updating the firmware on my HD621 and noticed a change in the display - Whereas earlier the active input LED was alone on, now the active input alone is off and all others are on.

Is this something peculiar to me or is it the new normal?

Hi,

This is not normal, when Rick (AudioImages) was installing my updates he mentioned exactly your scenario, and I cannot recall exactly what caused it so perhaps you could contact him for the proper explanation.

Rod

I had the same problem. Meridian had to email a firmware update.

HD621 ? Is there something more recent than 1.08 available ? (Sorry for the hijack!)

Yes, and no.

This a prime example of why dealers are handling the firmware updates now, rather than it being freely available on the website.

The HD621 over time has changed the hardware controlling its front panel LEDs
Different hardware revisions require specific firmware, to operate the LEDs correctly.

Very new HD621 will be running 1.09, earlier ones run 1.08.
Both these versions have the same performance, but pair their specific hardware to control the LEDs on the front panel correctly.

So both 1.09 and 1.08 are 'current', but put 1.08 in a current hardware version and you'll get the LEDs all on, apart from the source selected, which will be off.

Hope that clears that one up!

Rick

Hi Rick,

Thanks for the information and keeping us all informed.

However, I think this a prime example of Meridian not keeping their firmware release notes up to date and not communicating with its customers.
Only v1.08 is listed, there is no mention of v1.09 or hardware differences. IMHO it should list the HD621 S/N cutover where v1.09 should be used.

However, I do concede that users should check what version of firmware is loaded before blindly updating it.

Regard,
Carl

Thank you Rick, for this comprehensive answer/statement

Yes, this confusion must have caused lots of extra phone calls by dealers to Meridian so as to obtain the correct firmware, whereas Meridian axed phone calls by customers so as to reduce phone call demands: all a bit contradictory.

And thanks Rick for the clarification.

Rick:

I appreciate your passing along the knowledge... however I'm going to politely disagree with you.

As someone that has written a line or two of code for a living I can say that this type of decision tree isn't particularly difficult to code in the software. Assuming that the mothership has figured out how to either code a definitive hardware model and/or a serial number into a location that is programatically addressable it's childs play. We'll assume it's serial number and that serial number X of the product is the first serial of the new hardware type.

Here's what it would look like in pseudocode
set version=v1.09

if serial < X
set version=v1.08
endif

install version

Want to make it easier for later releases, give them the same base version numbers (such as v1.08) and append an A for baseline hardware and B for second rev of hardware. This becomes extensible through many versions of hardware.

The real world code would be a bit more complex depending on language etc, but not unduly so.

I also respect that the mothership is well within their rights to change their business model. I can't say that I am pleased, but I'm okay with that.

But the ability to programmatically resolve the versioning quandary on the HD621 makes your argument not a particularly robust one.

+1 John

Duncan

Let's all say it together: "Internet-enabled updating"

I think Meridian would face a significant degree of push back from dealers if they developed Internet enabled updating. The current model offers dealers a genuine foothold with the existing user base, and does provide a new, undoubtedly useful, revenue stream for them. A good example of M supporting it's dealerships where it counts. Albeit, in some respects, a relationship of inversely proportional desirability for ourselves.

Cheers

George