fruchti/haxmark
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Adjust timing to 1200dpi

Browse source 
At first I was using the 2400dpi mode of the printer. I now switched to
the native resolution of 1200dpi because the results are way better. The
2400dpi mode can still be used if a #define in config.h is changed.
This commit is contained in:
fruchti 2015-09-20 19:36:26 +02:00
parent ca25cfb38a
commit 8ac4d886e5
3 changed files with 40 additions and 29 deletions
Download patch file Download diff file Expand all files Collapse all files

8
README.md
View file

@ -6,9 +6,7 @@ It is based on [this](http://www.instructables.com/id/Modification-of-the-Lexmar
## Project status and performance
The project is in a "beta" state, meaning I can successfully print on PCBs with good quality but occasionally, my printer doesn't quite like the signals generated by my controller board and stops with a paper jam error until it is hard-rebooted. This seems to be unpredictable and the behavior even differs from time to time. The actual cause of these problems is unknown to me at this point (needless to say, the MCU software is quite beta, too).
The results are quite good: A minimal trace width of 5mil and a minimal clearance of 10mil are no big deal.
The printer behaves reasonably predictable and the way it should. The results are quite good: A minimal trace width of 5mil and a minimal clearance of 10mil are no big deal.
![MCU Board](https://raw.githubusercontent.com/fruchti/haxmark/master/samples/001.jpg)
@ -16,11 +14,11 @@ The results are quite good: A minimal trace width of 5mil and a minimal clearanc
### Some notes before you modify your printer
I strongly recommend that you test your printer in an unmodified state with exactly the driver and printer settings you intend to use it with to print on PCBs. I found out the hard way that the behavior and the timing differ from driver to driver. It is definitely a good idea to make a dump of the interesting signals (operator panel line, manual paper feed sensor, paper in sensor, exit sensor) with a logic analyzer to get the exact timing of your printing setup so you can adjust the timing settings in the MCU board's source code. I included a dump made with logic_sniffer and my settings. I use the printer with linux and [this](http://www.openprinting.org/printer/Lexmark/Lexmark-E360d) PPD file with 2400dpi image resolution. I have not used it with Windows, so if you plan to do that, better check the printer's behavior in detail before making any modification.
I strongly recommend that you test your printer in an unmodified state with exactly the driver and printer settings you intend to use it with to print on PCBs. I found out the hard way that the behavior and the timing differ from driver to driver. It is definitely a good idea to make a dump of the interesting signals (operator panel line, manual paper feed sensor, paper in sensor, exit sensor) with a logic analyzer to get the exact timing of your printing setup so you can adjust the timing settings in the MCU board's source code. I included a dump made with logic_sniffer and my settings. I use the printer with linux and [this](http://www.openprinting.org/printer/Lexmark/Lexmark-E360d) PPD file with 1200dpi native resolution. I have not used it with Windows, so if you plan to do that, better check the printer's behavior in detail before making any modification.
### Differences to the E260d
The main hardware difference between E260d and E360d is the use of a different operator's panel. But in the software there seem to be quite some:
The main hardware difference between E260d and E360d is the use of a different operator's panel. But in the software there seem to be quite some more:
- The E360d does not, unlike the E260d, pull in a piece of paper stuck into its front. Instead, it stops with a paper jam message.
- When starting a print, the printers motor runs for a while before it is stopped and the user has to confirm he has inserted a piece of paper into the manual feeder by pressing the tick button. Then, the motor starts running again and a few seconds later, a clutch is activated and the paper is finally pulled in. If the paper is inserted significantly before the clutch is activated, the printer reports a paper jam. Note that some drivers seem to omit the first motor running phase (this modification should work with both variants)