Hackaday gets results! Reader [John] saw our recent Fail of the Week post about a “sand matrix printer” and decided to share his own version, a sand-dispensing dot matrix printer he built last year.
Granted, [John]’s version is almost the exact opposite of [Vjie Miller]’s failed build, which sought to make depressions in the sand to print characters. [John]’s Sandscript takes a hopper full of dry, clean sand and dispenses small piles from six small servo-controlled nozzles. The hopper is mounted on a wheeled frame, and an optical encoder on one wheel senses forward motion to determine when to open each nozzle. As [John] slowly walks behind and to the side of the cart, a line of verse is slowly drizzled out onto the pavement. See it in action in the video below.
More performance art piece than anything else, we can see how this would be really engaging, with people following along like kids after the [Pied Piper], waiting to find out what the full message is. There’s probably a statement in there about the impermanence of art and the fleeting nature of existence, but we just think it’s a really cool build.
No lab in almost any discipline was complete in the 70s and 80s without an X-Y plotter. The height of data acquisition chic, these simple devices were connected to almost anything that produced an analog output worth saving. Digital data acquisition pushed these devices to the curb, but they’re easily found, cheap, and it’s worth a look under the hood to see what made these things tick.
The HP-7044A that [Kerry Wong] scored off eBay is in remarkably good shape four decades after leaving the factory. While the accessory pack that came with it shows its age with dried up pens and disintegrating foam, the plotter betrays itself only by the yellowish cast to its original beige case. Inside, the plotter looks pristine. Completely analog with the only chips being some op-amps in TO-5 cans, everything is in great shape, even the high-voltage power supply used to electrostatically hold the paper to the plotter’s bed. Anyone hoping for at least a re-capping will be disappointed; H-P built things to last back in the day.
[Kerry] puts the plotter through its paces by programming an Arduino to generate a Lorenz attractor, a set of differential equations with chaotic solutions that’s perfect for an X-Y plotter. The video below shows the mesmerizing butterfly taking shape. Given the plotter’s similarity to an oscilloscope, we wonder if some SDR-based Lissajous patterns might be a fun test as well, or how it would handle musical mushrooms.
You’ll all remember my grand adventure in acquiring a photocopier. Well, it’s been a rollercoaster, I tell ya. While I still haven’t found a modification worthy enough to attempt, I have become increasingly frustrated. From time to time, I like to invite my friends and family over for dinner, and conversation naturally turns to things like the art on the walls, the fish in the aquarium, or perhaps the photocopier in the living room. Now, I dearly love to share my passions with others, so it’s pretty darned disappointing when I go to fire off a few copies only to have the machine fail to boot! It was time to tackle this problem once and for all.
When powered up, the photocopier would sit at a “Please Wait…” screen for a very long time, before eventually coughing up an error code — SC990 — and an instruction to call for service. A bunch of other messages would flash up as well; Address Book Data Error, Hard Drive Data Error, and so on. In the end I realized they all centered around data storage.
Pictured: the author, in his happy place, at peace with the copier.
Now, I’d already tried diving into the service menu once before, and selected the option to format the hard drive. That had led to the problem disappearing for a short period, but now it was back. No amount of mashing away at the keypad would work this time. The format commands simply returned “Failed” every time. What to do next? You guessed it, it was time for a teardown!
Thankfully, photocopiers are designed for easy servicing — someone’s paying for all those service calls. A few screws and large panels were simply popping off with ease; completely the opposite of working on cars. Spotting the hard drive was easy, it looked like some sort of laptop IDE unit. With only SATA laptops around the house to salvage parts from, I wasn’t able to come up with something to swap in.
A bit of research (and reading the label) taught me that the drive was a Toshiba MK2023GAS/HDD2187. Replacements were available on eBay, but if I waited two weeks I’d probably be wrist deep in some other abandoned equipment. It had to be sorted on the night. In the words of [AvE], if you can’t fix it… well, you know how it goes. I yanked the drive and, lo and behold – the copier booted straight up! Just to be sure I wasn’t hallucinating, I churned out a few copies, and other than the continued jamming on all-black pages, everything was fine. Literally all it took to get the copier to boot was to remove the ailing drive. Suffice to say, I was kind of dumbfounded.
The hard drive a.k.a. the villain of the piece.
I’m happy to chalk up the win, but I have to draw issue with Ricoh’s design here. The copier is clearly capable of operating perfectly well without a hard drive. It will give up its document server and address book abilities, but it will still make copies and print without a problem.
Yet, when the copier’s drive fails, the unit fails completely and refuses to work. This necessitates a service call for the average user to get anything at all happening again — causing much lost work and productivity. A better design in my eyes would have the copier notify users of the lost functionality due to the failed drive and the need to call service, but let them copy! Any IT administrator will know the value of a bodged work around that keeps the company limping along for the day versus having a room of forty agitated workers with nothing to do. It’s a shame Ricoh chose to have the photocopier shut down completely rather than valiantly fight on.
Feel free to chime in with your own stories of minor failures that caused total shutdowns in the comments. Video below the break.
For all their applications, 3D printers can be finicky machines. From extruder problems, misaligned or missing layers, to finding an overnight print turned into a tangled mess, and that’s all assuming your printer bed is perfectly leveled. [Ricardo de Azambuja’s] new linear delta printer was frustrating him. No matter what he did, it wouldn’t retain the bed leveling calibration, so he had to improvise — Blu-Tack to the rescue.
It turns out [Azambuja]’s problem was so bad that the filament wouldn’t even attempt to adhere to the printing bed. So, he turned to Printrun Pronterface and a combination of its homing feature and the piece-of-paper method to get a rough estimate of how much the bed needed to be adjusted — and a similar estimate of how big of a gob of Blu-Tack was needed.
Pressing the bed into place, he re-ran Pronterface to make sure he was on the level. [Azambuja] notes that you would have to redo this for every print, but it was good enough to print off a trio of bed leveling gears he designed so he doesn’t have to go through this headache again for some time.
These days, if you want to start learning about FPGAs, it can be a daunting experience. There’s a huge variety of different platforms and devboards and it can be difficult to know where to start. [RoGeorge] decided to take a different tack. Like a 16-year-old drag racer, he decided to run what he brung – a printer control panel cum FPGA development board (Romanian, get your Google Translate on).
[RoGeorge] was lucky enough to score a couple of seemingly defective control panels from HP Laserjets discarded by his workplace. Seeing potentially good parts going to waste, like keypads and LCDs, he decided to investigate them further – finding a 50,000 gate Xilinx Spartan IIE running the show. Never one to say no to opportunity, [RoGeorge] dived in to learning how to work with FPGAs.
The forum posts are a great crash course in working with this sort of embedded FPGA platform. [RoGeorge] covers initial mapping of the peripherals on the board & finding a JTAG connector and programming solution, before moving on to basic FPGA programming and even covers the differences between sequential programming on microcontrollers and the parallel operation of FPGAs. Even if you don’t intend to get down and dirty with the technology, spend half an hour reading these posts and you’ll be far more knowledgeable about how they work!
In the end, [RoGeorge] showed how to teach yourself to work with FPGAs for the price of a couple of programming cables – not a mean feat by any means. It’s a testament to the hacker spirit, and reminds us of [SpriteTM]’s efforts in hacking hard drive controllers.
Here at Hackaday, we love clever 3D prints. This amazing lion statue remixed by [ _primoz_], makes us feel no different. It is no secret that FDM 3D printers have come a long way, propelled by the enthusiastic support from the open source community.
However, FDM 3D printers have some inherent limitations; some of which arise from a finite print nozzle diameter, tracing out the 3D object layer by layer. Simply put, some print geometries and dimensions are just unattainable. We discussed the solution to traditional FDM techniques being confined to Planer layers only in a previous article.
The case in point here is a 3D printed lion whose original version did not fully capture its majestic mane. [_primoz_] solution was to construct a support cylinder around the head and form the actual hair as a series of planar bristles, which were one extrusion wide.
This was followed by some simple post processing, where a heat gun was used to form the bristles into a dapper mane.
The result is rather glorious and we can’t wait for someone to fire up a dual extruder and bring out the flexible filament for this print!
Recently ZDNet and Gizmodo published articles outlining a critical flaw in a large array of personal printers. While the number of printers with this flaw is staggering, the ramifications are even more impressive. Ultimately, any of these printers could have documents sent to them stolen even if the document was only intended to be printed as a hard copy.
Luckily the people responsible for this discovery are white-hat in nature, and the release of this information has been made public so the responsible parties can fix the security flaws. Whether or not the “responsible party” is the manufacturer of the printer, though, is still somewhat unclear because part of the exploit takes advantage of a standard that is part of almost all consumer-grade printers. The standard itself may need to be patched.
Right now, however, it doesn’t seem clear exactly how deep the rabbit hole goes. We all remember the DDoS attack that was caused by Internet of Things devices that were poorly secured, and it seems feasible that networked printers could take some part in a similar botnet if a dedicated user really needed them. At the very least, however, your printed documents might not be secure at all, and you may be seeing a patch for your printer’s firmware in the near future.
