Hi all!
I've been a lurker for a while and finally found a need to post.
We have a Colorado 1650 which is allowing us to RIP jobs and send them to the UI queue but will not start the jobs. It displays no error message and just sits with jobs in the queue not printing. We recently had a technician in because our maintenance door was not registering as "closed" and it caused the machine to throw a "winding" code for the take up shaft. After the service we have not been able to print. I am wondering if the tech may have inadvertently switched off an "auto-print" setting with his maintenance screens? Currently the tech is attempting upgrade our firmware/OS to the 2.6.1 version from the 2.3.1 version.
Has anyone else encountered this issue? If the OS upgrade was performed did that fix the issue? Is there something else I might check to fix the issue? Any feedback is appreciated.
Thanks
I've been a lurker for a while and finally found a need to post.
We have a Colorado 1650 which is allowing us to RIP jobs and send them to the UI queue but will not start the jobs. It displays no error message and just sits with jobs in the queue not printing. We recently had a technician in because our maintenance door was not registering as "closed" and it caused the machine to throw a "winding" code for the take up shaft. After the service we have not been able to print. I am wondering if the tech may have inadvertently switched off an "auto-print" setting with his maintenance screens? Currently the tech is attempting upgrade our firmware/OS to the 2.6.1 version from the 2.3.1 version.
Has anyone else encountered this issue? If the OS upgrade was performed did that fix the issue? Is there something else I might check to fix the issue? Any feedback is appreciated.
Thanks