This is how the tick farmhouse has looked since May:
As you can see, the exterior is completely finished, complete with gutters and a rebuilt porch deck. The interior walls were also all framed in, giving a skeletal sense of the final configuration.
By mid-June, the external electrical work was all finished, with the new service lines to the house buried, and new sub-panels in the yard, well-house, and along the driveway put in. Plus an extra conduit for low-voltage stuff and plumbing!
As I write this, the interior electrical work is slowly progressing. Although I intend to put in gas for cooking, water, and drying, I'm having the place wired for both just in case. Plenty of outlets inside and out, the kitchen layout more or less sorted, and my current fun involves planning the (many) ethernet drops. Oh, what fun!
I'm hoping by the end of the summer I'll be able to drywall off the HVAC closet, get an air condiditioner installed, and maybe even close off the ceiling! Then it's just the new water heater (and natural gas piping for the kitchen and dryer) before the place is techically habitable again -- so I can take it easy and let my finances recover before moving onto the next phases -- namely the kitchen, bathrooms, and closing off the interior walls.
...And so it goes. :)
Back in March, my reverse-engineered processing library for the Mitsubishi CP-D70DW family of printers reached quality pairity with the official Windows/OSX drivers and their SDK. This was a huge milestone; it's now possible to drive these printers using entirely Free Software, with no quality compromises, on non-x86 CPU architectures. To do this, you will need Gutenprint 5.2.13-pre1 or newer, along with an up-to-date lib70x snapshot.
Here are the happy models:
- Mitsubishi CP-D70DW
- Mitsubishi CP-D707DW
- Mitsubishi CP-D80DW
- Mitsubishi CP-K60DW-S
- Kodak 305
- Fujifilm ASK-300 [completely untested]
I held off on announcing this achivement due to one rather annoying problem. It seems most folks interested in using this family of printers wanted to do so using the popular Raspberry Pi systems. Unfortunately, for (at the time) unknown reasons, the CP-D70DW spectacularly failed to print with RPi systems, with the image data failing to transfer to the printer.
To further complicate things, I was unable to recreate the problem on the Kodak 305 (aka a rebadged CP-K60DW-S) and an RPi2. Software-based sniffs were useless, and things stayed at this impasse for quite some time.
What finally broke the logjam was one particularly motivated user running into a similar problem with an RPi3 and a CP-D80DW model -- but only when there was nothing plugged into the ethernet controller. This was a bizarre development, and a working theory that there was something funky going on with the RPi's onboard SMSC USB hub/ethernet chip began to develop.
He convinced Mitsubishi/Europe that it was in their interests to help figure this problem out, and I soon found myself with a CP-D80DW and several boxes of media on my doorstep and a backchannel to their technical team.
Try as I might, I was unable to recreate the problem on a RPi1 or RPi2, but on an RPi3, I was finally able to trigger the failure. Armed with a true USB sniffer and a copy of the USB spec, I was able to rapidly identify what was acutally going on.
The USB2 spec (section 8.5.1) dictates that, when in high-speed mode, a flow control mechanism (NYET/PING/[N]ACK) be used to maximize transfer throughput. NYET is sent by the device after a successful transfer to signal that it can't accept more. The controller then starts polling the device with PING requests, with the printer responding with a NACK until it's ready, at which point it responds with an ACK.
The problem, in a nutshell, is that the RPi's USB controller ends up sending the PING requests so rapidly -- about 400 nanoseconds apart) that it effectively triggers a denial-of-service (DoS) situation in the printer. The funny thing is that the RPi's controller starts with a PING interval of about 1.2 microseconds, and everything is fine until it pulls in the timing, triggering the DoS.
(A regular PC with an xHCI controller demonstrates variable PING timing; it starts at about 400ns, but backs off to about a 4us interval)
If other USB traffic is present, then the bus is too busy to send the PINGs so rapidly, and the printer is fine. Notably, simply establishing a physical link with the onboard (USB-attached) ethernet controller (even if the interface is "down") generates sufficient traffic to mitigate the problem. Plugging in a thumbdrive and dumping data back or forth is also more than adequate.
I've reported this problem to both Mitsubishi and the RPi kernel folks. I don't think one can expect much progress on the root cause of this problem, but the above workarounds are at least adequate to using these printers with RPi systems.
...Enjoy, folks, and happy printing.
In a strange coincidence, this one blew its top 23 months and two weeks after I put it into service, replacing the last one which also blew up after 23 months and two weeks.
This time I wasn't home when it happened. I only discovered it when I noticed the vent caps lying several feet away.
Moral of story: regularly check the water levels of your wet-cell lead-acid batteries!
As of about a week ago, this is how the house looked:
Every exterior opening except for the old front door has been removed, replaced, or otherwise changed. Better framing, proper headers, double-glazed impact windows, and new sheathing all around, wrapped in a spiffy moisture barrier.
As I write this, the "mountain sage" HardiePlank lap siding is going up, then the fascia, trim, and soffits to complete the main structure's exterior. The porch decking, new support posts, and a matching roof will round up the exterior work.
Aside from arranging next rounds of work, my next visit will have me clearing trails -- cutting up and hauling away downed trees in peperation for a proper bush hoggin'.
And so it goes!