When faxing, I keep getting the same error code of: NG: POOR LINE CONDITION / OUT OF MEMORY
Hi,
I can advise you on the 'memory full' problem, mate.
If
you get a MEMORY FULL message while scanning the first page of a fax,
press Stop to cancel the scan. If you get a MEMORY FULL message while
scanning in a subsequent page, you’ll have the option to press Start to
transmit the pages scanned
so far, or to press Stop to cancel the operation. In this case, send the fax by the Manual Transmission.
Depending
on your typical faxes, MEMORY FULL errors can occur frequently. If this
happens, change the Memory Transmission setting back to OFF.
To do this:
Press Function/Set, 3, 9.
This should take you to MEMORY TX
and MEMORY TX: ON?
Then press either the left or the right arrow (< or >) to switch on or off, and press Function/Set.
For the next fax transmission only, press < or > to select
NEXT FAX ONLY and press Function/Set.
This
will mean you don't add any more to the memory and may be able to send
faxes. There is a possibility that you will only be able to fax using
manual transmission, but at least you should be able to use the machine
to fax at all!
I apologise if the jargon is confusing, just try to go through the process one step at a time and you should be fine.
Hope this helps :)
Chris (ziraffa)
If that still doesn't work, you could manually delete the jobs from the memory by doing the following:
1. Press Function/Set, 4. Any waiting jobs appear on the display. If
there are no jobs waiting, the screen displays NO JOB WAITING.
2. If you have more than 2 jobs waiting, press < or > to select the job you want to cancel and press Function/Set.
3. Press 1 to cancel, or 2 to exit without cancelling.
4. Press Stop to exit.
Might take a while but it will clear the memory!
Season's Greetings!
CHris (ziraffa)
×
None of you "experts" discussed the question which is SPECIFICALLY "NG" error code. Thanks.
6,404 views
Usually answered in minutes!
I know it is not Memory full. I've sent out other faxes and did not get the NG problem. Maybe it is a line problem on the other end? Isn't there a code for busy?
×