Intermittant E7-90 codes are driving us crazy. I counted 5 Phoenix II machines in our field that have thrown this code at least once this month. Cycling power off/on clears the code, but customers are getting upset. We've tried MFP and PCU swaps, firmware updates, CN updates, eMMC chips, disabling auto shut off, nothing has eliminated. Hotline is blaming corrupt print jobs that damage the machine somehow. Anyone else having this problem? A fix that I haven't tried?
MX4071 PHOENIX II SERIES E7-90 codes
Collapse
X
-
Re: MX4071 PHOENIX II SERIES E7-90 codes
We've had a couple with the same error code. Also Phoenix2 machines.
All of the machines helped with doing a Firmware update and calibration. 44-02, 46-74 etc
Although you have already tried FW update, there is a new update released couple days ago.Comment
-
Re: MX4071 PHOENIX II SERIES E7-90 codes
technical tipsAttached FilesComment
-
Re: MX4071 PHOENIX II SERIES E7-90 codes
I would recommend replacing the Mini EMMC (smaller MSATA) card. I have seen corruption issues on the new eMMC drives on most of the new models unfortunately and have replaced several. I would also advise making sure a power filter/surge protector is installed on the machine. These will help prevent corruption issues. The other thing I recommend is talking with the client about how they turn off/on the MFP. I did this once and was shocked when I heard how many people just unplug it when something happens...and doing this can also cause issues with the data drives over time.Comment
-
Re: MX4071 PHOENIX II SERIES E7-90 codes
I would recommend replacing the Mini EMMC (smaller MSATA) card. I have seen corruption issues on the new eMMC drives on most of the new models unfortunately and have replaced several. I would also advise making sure a power filter/surge protector is installed on the machine. These will help prevent corruption issues. The other thing I recommend is talking with the client about how they turn off/on the MFP. I did this once and was shocked when I heard how many people just unplug it when something happens...and doing this can also cause issues with the data drives over time.Comment
-
Re: MX4071 PHOENIX II SERIES E7-90 codes
Same toubles here...
a client with a lot of machines changed 4 machines to a different VLAN.
Since then, all of these machines throw E7-90 from time to time. Hard reboot is the only solution.
The machines are 2x MX3071 and 2x MXC304W
Must be something on the network...but we havent found out what yet...Comment
-
Re: MX4071 PHOENIX II SERIES E7-90 codes
Go into the print driver, properties, port settings and change the default off RAW to LPR, check the box for byte counting and name the queue ( I usually use "lp"), apply.
You have 2 options here: pull the print and job logs to find a "pattern" or set up packet capture.
Curious, do these machine have fax kits by chance...?
Failing to plan is planning to fail!!!Comment
-
Re: MX4071 PHOENIX II SERIES E7-90 codes
I was told by our rep that an E7-90 error is the result of poor power conditions. We have only seen it at one location on both of their machines. The previous machines that we had at this location also had E7-90 errors. They definitely have crap power. We have Innovolts installed and the disturbances recorded are constant but to date they will do nothing about it. I am not sure if any of the reported disturbances from the Innovolts are the issue because I have been unable to cross reference a date/time of a disturbance with an E7-90 reported to MICAS. The one thing I cannot know is if there are drops in current. We don't have anything that will record a low current event.
I will say that current drops have been suspected in several issues in the past. Power quality read by our Fluke VR1710 were normal but we were told by Sharp that it didn't matter because it was a low current issue that the Fluke could not record. Filtering the power was pointless. Adding a buck & boost was also pointless. While a B&B might compensate momentarily for a voltage drop it could not increase amperage. If it isn't there it isn't there. In these cases we have been able to get the customer to run a dedicated line with the proper gauge wiring and all the problems went away.Comment
-
Re: MX4071 PHOENIX II SERIES E7-90 codes
Go into the print driver, properties, port settings and change the default off RAW to LPR, check the box for byte counting and name the queue ( I usually use "lp"), apply.
You have 2 options here: pull the print and job logs to find a "pattern" or set up packet capture.
Curious, do these machine have fax kits by chance...?
mx3071 has no fax...mxc304w off course does but isnt beeing used.Comment
-
Re: MX4071 PHOENIX II SERIES E7-90 codes
I was told by our rep that an E7-90 error is the result of poor power conditions. We have only seen it at one location on both of their machines. The previous machines that we had at this location also had E7-90 errors. They definitely have crap power. We have Innovolts installed and the disturbances recorded are constant but to date they will do nothing about it. I am not sure if any of the reported disturbances from the Innovolts are the issue because I have been unable to cross reference a date/time of a disturbance with an E7-90 reported to MICAS. The one thing I cannot know is if there are drops in current. We don't have anything that will record a low current event.
I will say that current drops have been suspected in several issues in the past. Power quality read by our Fluke VR1710 were normal but we were told by Sharp that it didn't matter because it was a low current issue that the Fluke could not record. Filtering the power was pointless. Adding a buck & boost was also pointless. While a B&B might compensate momentarily for a voltage drop it could not increase amperage. If it isn't there it isn't there. In these cases we have been able to get the customer to run a dedicated line with the proper gauge wiring and all the problems went away.
Sharp told us a bunch of stuff too...but most of the time they’re just guessing as usual...
The moment you put them in another VLAN, problems dissapear.
If you put them back, problems come back, so this must be a network issue.
Both cases are big clients with large networks and different sites/locations.Comment
Comment