Firmware without SD card

[anothertech]

Re: Firmware without SD card

That doesn't work so hot if the machine doesn't have Internet access, which is all too common.

He says he wants to remote into the machine, so I figured it has internet.

[KenB]

Re: Firmware without SD card

He says he wants to remote into the machine, so I figured it has internet.

Not necessarily.

He may be accessing the WIM using the customer's intranet, meaning he could get on a remote session with a user's PC, then get to the machine from there; it's something I do all the time.

[copier tech]

Re: Firmware without SD card

Hi all,
I have a customer who I may need to update firmware on their IMC 4500A. Problem is I'd rather not got there because of current lockdown, if I can do this remotely.
I was thinking, remote into customers PC using trusty AnyDesk (It is like team viewer) then, browse to copiers IP address, then use remote operation panel to control their touch screen as I enabled it before installation. My question is, if I go into service mode and Firmware, will it update if it is not installed on @remote? As we do not use @remote.
If not, is there another way I can do the whole thing remotely? The only way I have ever done firmware is via mod/packages on an SD card in slot 2, never needed to do this before.
Thanks

You can update the firmware using the package .pkg file remotely via the WIM.

1.jpg

Then simply choose the .pkg location on your PC.

2.jpg

[marvin-vegan]

Re: Firmware without SD card

[B]You can update the firmware using the package .pkg file remotely via WIM

This procedure is not recommended, it will take more than hour to push pkg file via HTTP. From my own experience, this procedure will likely even fail, not complete or stall. And if eventually after hour of uploading, machine will restart and do nothing. If you then visit the firmware section in WIM, there will be red warning at the top of the page stating that fw. upload has failed. Happened to me few times so I completely abandoned this http pushing of 600megabytes.. no way.

Only working efficient way is to push locally through ftp, takes only a moment and does it right (my previous guide)


Sent from my iPhone using Tapatalk

[copier tech]

Re: Firmware without SD card

This procedure is not recommended, it will take more than hour to push pkg file via HTTP. From my own experience, this procedure will likely even fail, not complete or stall. And if eventually after hour of uploading, machine will restart and do nothing. If you then visit the firmware section in WIM, there will be red warning at the top of the page stating that fw. upload has failed. Happened to me few times so I completely abandoned this http pushing of 600megabytes.. no way.

Only working efficient way is to push locally through ftp, takes only a moment and does it right (my previous guide)


Sent from my iPhone using Tapatalk

I agree the .pkg file is rather large so takes ages, fasted & safest way is to update at the device via SD card or USB (on the IMC models)

On the older models updating using the individual .rfu files took longer but each file was small in size but all grouped as one file as they are now.

[KenB]

Re: Firmware without SD card

A little off topic, but I think it may be worth mentioning.

Some years back, I had a customer with several hundred MP201s that all needed an update, I think it was for PCL. They were scattered all over the country, as it was a major retail chain. I don’t remember what the update fixed, but it was crucial to their daily operations. An update they had made to their internal servers (not Windows severs) caused the issue, and it could not be reversed. It was a “forest fire drill”, if you will.

There was no @Remote in the picture, as they wouldn’t allow it. Besides, you don’t argue with a major customer, especially of that size.


We set up their Planet Press server to FTP the .rfu version of the update. We fed it lists of the IP addresses of the 201s, and setting it to a run overnight. We ran about 100 each night for 5 or 6 nights. Planet Press would keep track of the successful uploads, so we could re-run any that had failed. Fortunately, we had very few failures.