chris6343782
New Member
I've seen forum posts in the past on the Error 16 issue but haven't seen any resolutions. Has anyone heard of any good fixes for this issue, or a through understanding of the actual error code?
Been struggling with sporadic intermittent error 16 issues for a little while now. I'll get like 98% through a print, and the machine stops, beeps, gives the code, and then my expletives come out.
I'm running the "Special Firmware" version 3.20,
Rasterlink Pro5 SG v 4.30
and the latest printer driver.
Windows 7 64bit, with plenty of memory.
I've tried uninstalling and reinstalling with no change.
I tried changing to new and shorter USB cables.
Checked the circuit boards for dust.
Added a grounding wire to help alleviate static issues.
still getting the error.
The manual is less than helpful in explaining with this MRL command issue is and how to fix it.
I know I have an old firmware here, and I am about ready to update that but have heard some horror stories about fried print heads after a firmware update is done and I'm a bit freaked out by that. Have you heard if this error code gets resolved with any of the firmware updates?
Been struggling with sporadic intermittent error 16 issues for a little while now. I'll get like 98% through a print, and the machine stops, beeps, gives the code, and then my expletives come out.
I'm running the "Special Firmware" version 3.20,
Rasterlink Pro5 SG v 4.30
and the latest printer driver.
Windows 7 64bit, with plenty of memory.
I've tried uninstalling and reinstalling with no change.
I tried changing to new and shorter USB cables.
Checked the circuit boards for dust.
Added a grounding wire to help alleviate static issues.
still getting the error.
The manual is less than helpful in explaining with this MRL command issue is and how to fix it.
I know I have an old firmware here, and I am about ready to update that but have heard some horror stories about fried print heads after a firmware update is done and I'm a bit freaked out by that. Have you heard if this error code gets resolved with any of the firmware updates?