Low cost printing on the Samsung CLP-315 Laser Printer


I enjoyed this article on resetting the print count stored in the 24C64WP 2-Wire Serial EEPROM chip of the Samsung CLP-315 Laser Printer.

It works by tying pin 5 SDA to ground during boot up, causing 0 page counts to be read from the chip, then releasing pin 5, printing a color page test if you want to reset color counts or a black page if you want to reset black page counts.  The 0 is then made a 1 and written back to the EEPROM.   When you power cycle again, reset is saved.

Cool.  Thanks Brian

Brian's video:
http://youtu.be/077GLsEMV2E

How to open / disassemble Samsung clp-315 color laser printer:
http://youtu.be/zNiSua7yTnE



http://rumburg.org/printerhack/#reset-procedure
Reset Procedure

After printing a few more pages (and giggling like a child to the wife), I was able to refine the reset process a bit. Here are the steps to perform the reset:

Open the printer and solder a wire to the SDA pin of the EEPROM (see video below)
Power up the printer with this line held to ground until it finishes initializing
You can use chassis near the USB port is an easy spot to ground to.
The printer will take longer than normal to initialize; don’t be alarmed
Disconnect the SDA line from ground
Print the demo page by pushing The Button until you see a slowly blinking green light (about 2 seconds)
Print the configuration page by pushing The Button until you see a rapidly blinking green light (about 6 seconds)
Turn off the power
Turn on the power, and wait for it to initialize
Print the configuration report again
All your base are belong to us
Notes

One thing worth noting; my printer still has its original toner cartridges which are “chipless”. Retail replacement cartridges have a chip with its own EEPROM that has a unique identifier and stores its own count. Since I don’t have toner cartridges with these chips, I don’t know (but I suspect) that a different approach or additional steps may be necessary to reset the counts.

You may be able to tape off the exposed pads on the toner chips before performing this procedure and get the same effect, but I haven’t got the chipped cartridges to test with. (nor will I be buying any for $150!) YMMV.

Demo Time!

Conclusion
It took some time to get there, but I think it was worth the effort. This printer is now happily kicking out full-color pages for 2¢ versus a whopping 15¢ (ouch).  Life is good. Enjoy!

dig +trace

So DNS is a distributed database with many different people controlling various parts.  Your DNS or RDNS is having problems and you want to see where the delegation is breaking. dig +trace to the rescue!

This and many other dig examples at: http://www.madboa.com/geek/dig/


$ dig -x 8.8.8.8 +trace

; <<>> DiG 9.7.0-P1 <<>> -x 8.8.8.8 +trace
;; global options: +cmd
. 518400 IN NS g.root-servers.net.
. 518400 IN NS a.root-servers.net.
. 518400 IN NS l.root-servers.net.
. 518400 IN NS i.root-servers.net.
. 518400 IN NS c.root-servers.net.
. 518400 IN NS d.root-servers.net.
. 518400 IN NS j.root-servers.net.
. 518400 IN NS e.root-servers.net.
. 518400 IN NS b.root-servers.net.
. 518400 IN NS m.root-servers.net.
. 518400 IN NS h.root-servers.net.
. 518400 IN NS f.root-servers.net.
. 518400 IN NS k.root-servers.net.
;; Received 228 bytes from 127.0.0.1#53(127.0.0.1) in 150 ms

in-addr.arpa. 172800 IN NS c.in-addr-servers.arpa.
in-addr.arpa. 172800 IN NS e.in-addr-servers.arpa.
in-addr.arpa. 172800 IN NS f.in-addr-servers.arpa.
in-addr.arpa. 172800 IN NS d.in-addr-servers.arpa.
in-addr.arpa. 172800 IN NS a.in-addr-servers.arpa.
in-addr.arpa. 172800 IN NS b.in-addr-servers.arpa.
;; Received 414 bytes from 192.58.128.30#53(j.root-servers.net) in 104 ms

8.in-addr.arpa. 86400 IN NS ns1.level3.net.
8.in-addr.arpa. 86400 IN NS ns2.level3.net.
;; Received 84 bytes from 196.216.169.10#53(c.in-addr-servers.arpa) in 360 ms

8.8.8.in-addr.arpa. 3600 IN NS ns2.google.com.
8.8.8.in-addr.arpa. 3600 IN NS ns4.google.com.
8.8.8.in-addr.arpa. 3600 IN NS ns3.google.com.
8.8.8.in-addr.arpa. 3600 IN NS ns1.google.com.
;; Received 120 bytes from 209.244.0.1#53(ns1.level3.net) in 84 ms

8.8.8.8.in-addr.arpa. 86400 IN PTR google-public-dns-a.google.com.
;; Received 82 bytes from 216.239.32.10#53(ns1.google.com) in 99 ms



$ dig google-public-dns-a.google.com +trace

; <<>> DiG 9.7.0-P1 <<>> google-public-dns-a.google.com +trace
;; global options: +cmd
. 518400 IN NS c.root-servers.net.
. 518400 IN NS e.root-servers.net.
. 518400 IN NS i.root-servers.net.
. 518400 IN NS k.root-servers.net.
. 518400 IN NS g.root-servers.net.
. 518400 IN NS b.root-servers.net.
. 518400 IN NS h.root-servers.net.
. 518400 IN NS l.root-servers.net.
. 518400 IN NS a.root-servers.net.
. 518400 IN NS j.root-servers.net.
. 518400 IN NS d.root-servers.net.
. 518400 IN NS f.root-servers.net.
. 518400 IN NS m.root-servers.net.
;; Received 228 bytes from 127.0.0.1#53(127.0.0.1) in 170 ms

com. 172800 IN NS i.gtld-servers.net.
com. 172800 IN NS g.gtld-servers.net.
com. 172800 IN NS d.gtld-servers.net.
com. 172800 IN NS m.gtld-servers.net.
com. 172800 IN NS c.gtld-servers.net.
com. 172800 IN NS b.gtld-servers.net.
com. 172800 IN NS e.gtld-servers.net.
com. 172800 IN NS k.gtld-servers.net.
com. 172800 IN NS l.gtld-servers.net.
com. 172800 IN NS a.gtld-servers.net.
com. 172800 IN NS j.gtld-servers.net.
com. 172800 IN NS h.gtld-servers.net.
com. 172800 IN NS f.gtld-servers.net.
;; Received 504 bytes from 198.41.0.4#53(a.root-servers.net) in 129 ms

google.com. 172800 IN NS ns2.google.com.
google.com. 172800 IN NS ns1.google.com.
google.com. 172800 IN NS ns3.google.com.
google.com. 172800 IN NS ns4.google.com.
;; Received 184 bytes from 192.43.172.30#53(i.gtld-servers.net) in 202 ms

google-public-dns-a.google.com. 86400 IN A 8.8.8.8
;; Received 64 bytes from 216.239.38.10#53(ns4.google.com) in 84 ms