I've just flashed a new MR3020 and I thought I'd pass on my experience... it may save others time.
My model was a MR3020 V3.2.
I followed the instructions provided which included downloading the Win10 TFTP server from Solar Winds but simply couldn't get the flash process to work. The server just didn't seem to see the flash request. Nothing happened.
My first problem was that I didn't understand that the MR3020 only requests its load from ONE of the provided server addresses. It's doesn't try both. I had allocated 192.168.0.66 but it actually needed 192.168.0.255.
To avoid complications with the network I used my Win10 laptop to host the TFTP server, I disabled the firewall, disabled wifi, allocated the ethernet port the fixed address (192.168.0.255) and ran a UTP cable directly between the laptop and MR3020 so they were on their own 2 device physical network albeit without a dhcp server or any internet access.
And that worked. Lights flashed quickly for a period. All over in 60 seconds or so.
Then I connected the MR3020 to the local LAN and powered up. All the lights came on and almost immediately they all went out except one which remained steady. This can't be right. There's supposed to be flashing at the start. Have I bricked it??? So I re-flashed with the same result. And again.
Then with no expectation I checked if it had actually loaded. And there is was on the network ready to go! On re-boot the network load phase was lightening fast (literally seconds) I'm sure helped by my 100Mb FTH but perhaps also by Boris's new server. Network loads can be very fast.
This new MR3020 is replacing a faulty unit. I reloaded a saved configuration from the old device and all my settings came back like a charm. It certainly made things easier having that to apply.
Hope this is useful to someone.
Regards
Flashing a new MR3020
Moderator: Mattk
Re: Flashing a new MR3020
Hi,
A further update…
Today I implemented the replacement MR3020. Fortunately the unreliable unit was still actually running at the time.
With the new unit powered up and attached to the same network as the old unit it picked up the weather station and started generating its outbound data. I had previously reloaded the old configuration. The current data pages of both units were identical and operating in parallel.
I then initiated the license transfer function from the old device. It recognised the new unit, the license was transferred, and then a message was displayed requesting a reboot on both devices to complete the process. The reboot completed and the license page of the new device confirmed the trial license had been replaced.
To my surprise the new device max/min data page confirmed that all values had come across in the transfer together with the dates on which these records occurred. There was no need to manually enter these values as the documentation I had read suggested. Perhaps I missed one of the later documentation updates.
It’s worth noting that the light pattern on the new v3.2 MR3020 is different to the replaced V1. The lights on the old unit flashed when the software was loading and operating. On the new unit a single light, the one furtherest from the button, remains steady after an initial power on flash of all lights. Don’t be fooled into thinking there is a problem because there is no light activity.
All in all this was a very painless process and a credit to the developers.
Regards Steve
A further update…
Today I implemented the replacement MR3020. Fortunately the unreliable unit was still actually running at the time.
With the new unit powered up and attached to the same network as the old unit it picked up the weather station and started generating its outbound data. I had previously reloaded the old configuration. The current data pages of both units were identical and operating in parallel.
I then initiated the license transfer function from the old device. It recognised the new unit, the license was transferred, and then a message was displayed requesting a reboot on both devices to complete the process. The reboot completed and the license page of the new device confirmed the trial license had been replaced.
To my surprise the new device max/min data page confirmed that all values had come across in the transfer together with the dates on which these records occurred. There was no need to manually enter these values as the documentation I had read suggested. Perhaps I missed one of the later documentation updates.
It’s worth noting that the light pattern on the new v3.2 MR3020 is different to the replaced V1. The lights on the old unit flashed when the software was loading and operating. On the new unit a single light, the one furtherest from the button, remains steady after an initial power on flash of all lights. Don’t be fooled into thinking there is a problem because there is no light activity.
All in all this was a very painless process and a credit to the developers.
Regards Steve