iR4570 E240 when loading system software
Collapse
X
-
OK, well registering the files in that method made them appear in the list without any error messages...but I'm still getting the SST E240 code in reference to the HDFormat.ift file stating: "Module : SendFile() - 5"
Still waiting on an XP laptop, will try that next.
when u format in SST U NEED TO SELECT SINGLE/ FIRST
and set up for connection
SST3.JPG**Knowledge is time consuming, exhausting and costly for a trained Tech.**Comment
-
OK, well registering the files in that method made them appear in the list without any error messages...but I'm still getting the SST E240 code in reference to the HDFormat.ift file stating: "Module : SendFile() - 5"
Still waiting on an XP laptop, will try that next.
HDD Not Found
When attempting to format a hard drive in a Canon
ImageRUNNER and you receive a message from the
SST advising that the HDD
cannot be found in the drives file.
Steps to Modify the File
1. Find the Correct HDD Descriptor File
2. Disable Read-Only protection
3. Locate Similar HDD Descriptor
4. Create Copy of Descriptor and Modify
5. Increment Supported HDD Counter
6. Save Modified File
7. Re-Enable Read-Only Protection
READ PDF BELOW
SST_-_HDD_Not_Found.pdf**Knowledge is time consuming, exhausting and costly for a trained Tech.**Comment
-
Yes, I'm downloading the files straight from the Canon support site.
I tried clicking Single first, it still asks if I've installed a new HDD, then prompts me to initialize it, at which point it fails again on the HDFormat.ift file.Comment
-
IMO it is either a bad HDD, loose connection between the HDD and the MN-CON or a bad ift file. I am not sure that another laptop is going to get you anywhere unless it has another version of the ift file on it.
Does anyone keep copies of the older versions of firmware at your office? I would almost try a lower version just to see what happens.Accidents don't just happen. They must be carelessly planned.Comment
-
**Knowledge is time consuming, exhausting and costly for a trained Tech.**Comment
-
Accidents don't just happen. They must be carelessly planned.Comment
-
IMO it is either a bad HDD, loose connection between the HDD and the MN-CON or a bad ift file. I am not sure that another laptop is going to get you anywhere unless it has another version of the ift file on it.
Does anyone keep copies of the older versions of firmware at your office? I would almost try a lower version just to see what happens.
Unfortunately, this is the first iR4570 I've come across in several years, so I don't have any older versions of system software.
I guess I might try replacing MN-CON next?Comment
-
Well, I've tried two brand-new HDDs, one straight from Canon. I've re-downloaded the system software several times, so if the .ift is bad I'd presume there would be hundreds of other techs having problems with it. I know I've got a good connection between the HHD and MN-CON, and I've reseated the Boot Rom and DIMM.
Unfortunately, this is the first iR4570 I've come across in several years, so I don't have any older versions of system software.
I guess I might try replacing MN-CON next?
just a note on the imageRUNNER 4570 / 3570 / 2870 / 2270
***If a new HDD is installed with a BootRom version lower than v6.36, the system software cannot be installed, and the BootRom cannot be upgraded.
1. Carry and use a copier BootRom v6.36 or higher to format and install the System Software to the new HDD. The original Bootrom [C or N] now can be upgraded, after flashing the System Software. Be sure the BootRom is model specific.
2. Bring the original BootRom that is lower than v6.36 to a known working machine and flash it to v6.36 or higher. Install the BootRom back into the original machine, format and install the System software.
Bottom line >>>>BOOT ROM IS NO GOOD**Knowledge is time consuming, exhausting and costly for a trained Tech.**Comment
-
Even though it was working intermittently as the HDD was failing, you think the Boot Rom could be bad now?Comment
-
No, Teckat is referring to a glitch in the normal upgrade process, if your bootrom was lower than v6.36, it had to be upgraded first, before the rest of the process could take place. That always occurred for me on a working copier, I never fought a dead hard drive below the 6.36 version, so I don't know if that is your issue or not. I believe the bootrom software is first loaded onto the hard drive, then pushed to the rom during bootup. If your hard drive is fubar'd, I don;t know how that process can take place.
If you could find another working 4570, that is above v6.36, you could get your drive up to speed on the surrogate, and then bring it back to the corpse.
Just a thought..."Once a King, always a King, but once a Knight is enough!"
Comment
-
Hmm...well, I don't have one with a higher version, but I do have another working iR4570 - would it be possible to drop the good machine's HDD into a PC and capture an image of it, then copy that image onto the new HDD???Comment
-
take your boot rom that is below 6.36 and put it into your working machine then upgrade it using assist mode. After you have successfully flashed the boot rom and you know that it is working drop it back into your dead machine and fire away. Of course you could always try and load one of the HDD's in the working machine as well.Accidents don't just happen. They must be carelessly planned.Comment
-
Both our suggestions are viable, bootrom or hard drive surrogacy. Personally, I would avoid the "ghosting" idea, since you would capture all the settings from the donor, and they may not apply to you."Once a King, always a King, but once a Knight is enough!"
Comment
-
Well I took the boot rom & HDD out of the down machine & installed them in the good one. Everything worked flawlessly! I'll try the others in the bad machine tomorrow & report back...Comment
Comment