Hey guys,
I got a MXC311 with a F6-21. You have to go into the MXFXX3 SM to get the codes. Code says the LIU board location code differs from the Fax pwb. Over a year ago this copier was throwing this code and i swapped the entire fax kit out. From what i remember i did enter sim 66-2 and checked that the location code was set to USA.
Ive seen this before on a MX2600 and power cycling it fixed the problem. Every now and again it would come back but again a power cycle would get rid of it.
I have not been able to get the customer to power cycle yet as it was a boss that called in looking for the salesman wanting to cancel the contract and he was unwilling to work with me on the phone.
Has anybody ever run into this code before and did they have a fix for it? I imagine a power cycle will reset it for now but it should not be doing this. Is it possible for a outside influence on the machine to cause this problem? The 2600 mentioned above is now being used by my office for the last 3 months and it's never had a issue, however the code had not shown up for over a year before we pulled it from the customers office.
I got a MXC311 with a F6-21. You have to go into the MXFXX3 SM to get the codes. Code says the LIU board location code differs from the Fax pwb. Over a year ago this copier was throwing this code and i swapped the entire fax kit out. From what i remember i did enter sim 66-2 and checked that the location code was set to USA.
Ive seen this before on a MX2600 and power cycling it fixed the problem. Every now and again it would come back but again a power cycle would get rid of it.
I have not been able to get the customer to power cycle yet as it was a boss that called in looking for the salesman wanting to cancel the contract and he was unwilling to work with me on the phone.
Has anybody ever run into this code before and did they have a fix for it? I imagine a power cycle will reset it for now but it should not be doing this. Is it possible for a outside influence on the machine to cause this problem? The 2600 mentioned above is now being used by my office for the last 3 months and it's never had a issue, however the code had not shown up for over a year before we pulled it from the customers office.
Comment