If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
We cleared out all the memory on the RIP, rebooted the machine and copier, restored configuration backup and still no go. Is there any memory in the copier that should be cleared out? We couldn't find any option to do that on the copier, just the RIP.
We cleared out all the memory on the RIP, rebooted the machine and copier, restored configuration backup and still no go. Is there any memory in the copier that should be cleared out? We couldn't find any option to do that on the copier, just the RIP.
press and hold 'power save' + 'stop' + '6' buttons while turning on the machine. This should clear any outstanding/ spooled jobs in memory.
Now we are getting error code 016-781 and we no longer have internet access thru the network and we cannot scan from copier to creo. Network card bad? Software conflict? Bad RAM?
We pinged the TCP/IP and it was GOOD
We pinged the Gateway and it was BAD
We pinged the TCP/IP for Downloads and it was BAD
016-781 is error for scan, net connection error during scan.
do you have bustled fiery controller on machine,
did you tried to connect machine to that controller to see do you have problem with machine dc 3535 or with Creo.
If your problem is with Creo you will have to reload system software on it.
Now we are getting error code 016-781 and we no longer have internet access thru the network and we cannot scan from copier to creo. Network card bad? Software conflict? Bad RAM?
We pinged the TCP/IP and it was GOOD
We pinged the Gateway and it was BAD
We pinged the TCP/IP for Downloads and it was BAD
From your previous post, ec103-372 is an IOT software controller failure which means you will need to reload the system software on the CREO rip. The rip may also have a faulty network card.
ec016-781 is a SCAN related error which might have been caused by a faulty rip or an NVM corruption on the ESS. That's probably why you're getting some ping errors.
I suggest the best way to fix the problem to isolate each component and deal with it separately starting with the rip.
Comment