Home AMX User Forum AMX Networked AV (SVSI) Products

Unable to get N1222 decoders to run firmware updates

I can't get a system of N1000 series encoders and decoders to run firmware updates.

I'm personally running Win7 32 bit in a VM on a Mac. I never have problems with other (2000 series) updaters on this platform, but no matter what I try I always get the "Windows Firewall (or something) error when trying to run updates.

I've connected my laptop directly to P1 on the decoder to eliminate any network issues. Still no update.
I've got Windows Firewall and Windows Defender completely disabled. Still no update.
I called AMX and they remoted in and couldn't get it to work, either. They suggested I bring a real Windows laptop running 64 bit version of windows to try. We've done that before and couldn't get it to work like that either, but it's been a few months now, I suppose I need to try that again.

These encoders are on a big (/22) subnet, but I've got my local computer configured on the same class C octet as the encoders.

Has anyone else had problems running firmware updaters for N1000 series, and figured out what was causing it and how to make it work? I'm getting really frustrated.

Comments

  • A real Win10 64 bit laptop didn't make any difference, either. What did make a difference was rebooting the decoders, camping on them, and running the updater on each one as soon as it came back online. If we waited more than a few minutes after decoder reboot, the updater wouldn't run. The wallplate encoder firmware updater ran without a hitch first time, on encoders that hadn't even been rebooted recently.

  • One more quick note on firmware updates for the N1115 Wallplate encoders (and probably the other N1xxx encoders as well):

    The latest firmware update, v1.15.18 (6/6/2018), breaks CPC if it is already set before the update. This causes Macs to not send AV signals into the encoders.

    I had to go into the encoders, turn CPC off, turn it back on, OK the dialog box, then reboot the encoders. After that process, the encoders started working OK again for Macs.

    We brought the real Windows laptop in here to work on getting the firmware updates to run, and ended up using it to test the AV after we got the firmware updates completed. I never re-tested from a Mac after the firmware update. Bad AV tech. BAD!

  • I had some issues early on where I had to manually grant access to the update software through the windows firewall even though the installer initially asked me for permission..

  • Having similar issues with N1122A units. Getting "Firmware successfully loaded but with mismatching dates" message. Found that rebooting POE on all units a must prior to attempting as not doing so caused several to not boot up at all. Had to send to Madison in Brisbane to reflash. I am working with them to try and resolve this issue and will definitely try fogled@mizzou recommendation of rebooting them and camping on them. Sounds like it could be a good suggestion as our system has around 28 units and by the time it gets to those last ones it may cause an issue. if that doesn't work I am going to attempt a bench update to remove any cabling or switch config issues. I'll keep you posted

  • @mtp1964 @aapt.n" said:
    Having similar issues with N1122A units. Getting "Firmware successfully loaded but with mismatching dates" message. Found that rebooting POE on all units a must prior to attempting as not doing so caused several to not boot up at all. Had to send to Madison in Brisbane to reflash. I am working with them to try and resolve this issue and will definitely try fogled@mizzou recommendation of rebooting them and camping on them. Sounds like it could be a good suggestion as our system has around 28 units and by the time it gets to those last ones it may cause an issue. if that doesn't work I am going to attempt a bench update to remove any cabling or switch config issues. I'll keep you posted

    https://help.harmanpro.com/n1x22a-updater
    Just want to bring attention to the notes of the latest update. Updating from <1.5.71 to 1.5.71 or higher may take 30-60 minutes, as PHP will be updated. Don't get confused that they still blink like in normal operation, it needs to be waited until they reboot.

    Second is the note about the maintenance mode that is required to be enabled for the update to 1.5.80. I got told that this maintenance mode thing is only required for this particular update, future updates should not require it again. Might have to do with the update process that gets in trouble...

    And the common workaround of rebooting the units before the update is also a hint from TS. Reboot the unit, and then immediately do the update, before the unit gets too much under load by streaming.

Sign In or Register to comment.