The Prusa i3 MK3 is, for lack of a better word, inescapable. Nearly every hacker or tech event that I’ve attended in 2018 has had dozens of them humming away, and you won’t get long looking up 3D printing on YouTube or discussion forums without somebody singing its praises. Demand for Prusa’s latest i3 printer is so high that there’s a literal waiting list to get one.
At the time of this writing, over a year after the printer was officially put up for sale, there’s still nearly a month lead time on the assembled version. Even longer if you want to wait on the upgraded powder coated bed, which has unfortunately turned out to be a considerable production bottleneck. But the team has finally caught up enough that the kit version of the printer (minus the powder coated bed) is currently in stock and shipping next day.
I thought this was a good a time as any to pull the trigger on the kit and see for myself what all the excitement is about. Now that I’ve had the Prusa i3 MK3 up and running for a couple of weeks, I can say with confidence that it’s not just hype. It isn’t a revolution in desktop 3D printing, but it’s absolutely an evolution, and almost certainly represents the shape of things to come for the next few years.
That said, it isn’t perfect. There’s still a few elements of the design that left me scratching my head a bit, and some parts of the assembly weren’t quite as smooth as the rest. I’ve put together some of those observations below. This isn’t meant to be a review of the Prusa i3 MK3 printer, there’s more than enough of those already, but hopefully these assorted notes may be of use to anyone thinking of jumping on the Prusa bandwagon now that production has started really ramping up.
It was darkest hour for the video game industry following the holiday shopping season of 1982. The torrent of third party developed titles had flooded the home video game console market to the point of saturation. It incited a price war amongst retailers where new releases were dropped to 85% off MSRP after less than a month on the shelves. Mountains of warehouse inventory went unsold leaving a company like Atari choosing to dump the merchandise into the Chihuahuan desert rather than face the looming tax bill. As a result, the whole home video game industry receded seemingly overnight.
One company single-handedly revived video games to mainstream prominence. That company was Nintendo. They’re ostensibly seen as the “savior” of the video games industry, despite the fact that microcomputer games were still thriving (history tends to be written by the victors). Nevertheless their Nintendo Entertainment System (NES) was an innovative console featuring games with scrolling screens, arcade-like sprites. But the tactic they used to avoid repeating the 1983 collapse was to tightly control their market using the Nintendo Seal of Quality.
From the third party developer perspective, Nintendo’s Seal of Quality represented more than just another logo to throw on the box art. It represented what you could and couldn’t do with your business. Those third party licensing agreements dictated the types of games that could be made, the way the games were manufactured, the schedule on which the games shipped to retail, and even the number of games your company could make. From the customer side of things that seal stood for confidence in the product, and Nintendo would go to great lengths to ensure it did just that.
This is the story of how an Atari subsidiary company cracked the hardware security of the original Nintendo and started putting it into their unofficial cartridges.
In a complete surprise, Sony has moved to release the latest version of their robotic dog series, Aibo, in North America. The device is already out in Japan, where there are a number of owner’s clubs that would rival any dedicated kennel club. Thanks to the [Robot Start] team, we now have a glimpse of what goes into making the robotic equivalent of man’s best friend in their teardown of an Aibo ERS-1000.
According to Yoshihiro of Robot Start, Aibo looks to be using a proprietary battery reminiscent of the Handycam camcorders. Those three gold contacts are used for charging on the rug shaped power base that Aibo will periodically return to in order to take a”nap”. There are a couple of square OLED screens behind those puppy dog eyes. They are full-color OLEDs somewhere in the one-inch ballpark. Between the screens is a capacitive touch sensor that wraps around to the top of the head that are also pressure sensitive.
According to Sony’s press release, the fish-eye camera housed in Aibo’s snout is used to identify faces as well as navigating spaces.
Laying out all the major parts out together certainly drives home the complexity of the latest Aibo. It’ll be interesting to see the progression of this device as all of them come equipped with 4G LTE and 802.11 b/g/n WiFi that connect to Sony’s servers for deep learning.
New behaviors are supposed to download automatically as long as the device is under the subscription plan. While Sony has no current plans to integrate with any voice-activated virtual assistant, we can still look forward to the possibility of some expanded functionality from the Hackaday community.
For the rest of the teardown photos make sure to head over to [Yoshihiro]’s write up on Robot Start. Also just in case anybody cared to see what happens when the first generation Aibo ERS-111 from 1999 meets the 2018 Aibo ERS-1000, you’ll find the answer in the video below:
Reader [poipoi] recently wrote into our tip line to tell us about an “amazingly fast” Raspberry Pi display driver with a README file that “is an actual joy to read”. Of course, we had to see for ourselves. The fbcp-ili9341 repo, by [juj], seems to live up to the hype! The software itself appears impressive, and the README is detailed, well-structured, educational, and dare we say entertaining?
The driver’s main goal is to produce high frame rates — up to around 60 frames per second — over an SPI bus, and it runs on various Raspberry Pi devices including the 2, 3 and Zero W. Any video output that goes to the Pi’s HDMI port will be mirrored to a TFT display over the SPI bus. It works with many of the popular displays currently out there, including those that use the ILI9341, ILI9340, and HX8357D chipsets.
The techniques that let [juj] coax such frame rates out of a not-terribly-fast serial bus are explained in detail in the README’s How it Works section, but much of it boils down to the fact that it’s only sending changed pixels for each frame, instead of the full screen. This cuts out the transmission of about 50% of the pixels in each update when you’re playing a game like Quake, claims the author. There are other interesting performance tweaks as well, so be sure to check out the repo for all the details.
There’s a video comparing the performance of fbcp-ili9341 to mainline SPI drivers after the break.
When I started working in a video production house in the early 1980s, it quickly became apparent that there was a lot of snobbery in terms of equipment. These were the days when the home video market was taking off; the Format War had been fought and won by VHS, and consumer-grade VCRs were flying off the shelves and into living rooms. Most of that gear was cheap stuff, built to a price point and destined to fail sooner rather than later, like most consumer gear. In our shop, surrounded by our Ikegami cameras and Sony 3/4″ tape decks, we derided this equipment as “ReggieVision” gear. We were young.
For me, one thing that set pro gear apart from the consumer stuff was the type of connectors it had on the back panel. If a VCR had only the bog-standard F-connectors like those found on cable TV boxes along with RCA jacks for video in and out, I knew it was junk. To impress me, it had to have BNC connectors; that was the hallmark of pro-grade gear.
I may have been snooty, but I wasn’t really wrong. A look at coaxial connectors in general and the design decisions that went into the now-familiar BNC connector offers some insight into why my snobbery was at least partially justified.
When a project has outgrown using a small microcontroller, almost everyone reaches for a single-board computer — with the Raspberry Pi being the poster child. But doing so leaves you stuck with essentially a headless Linux server: a brain in a jar when what you want is a Swiss Army knife.
It would be a lot more fun if it had a screen attached, and of course the market is filled with options on that front. Then there’s the issue of designing a human interface: touch screens are all the rage these days, so why not buy a screen with a touch interface too? Audio in and out would be great, as would other random peripherals like accelerometers, WiFi, and maybe even a cellular radio when out of WiFi range. Maybe Bluetooth? Oh heck, let’s throw in a video camera and high-powered LED just for fun. Sounds like a Raspberry Pi killer!
And this development platform should be cheap, or better yet, free. Free like any one of the old cell phones that sit piled up in my “hack me” box in the closet, instead of getting put to work in projects. While I cobble together projects out of Pi Zeros and lame TFT LCD screens, the advanced functionality of these phones sits gathering dust. And I’m not alone.
Why is this? Why don’t we see a lot more projects based around the use of old cellphones? They’re abundant, cheap, feature-rich, and powerful. For me, there’s two giant hurdles to overcome: the hardware and the software. I’m going to run down what I see as the problems with using cell phones as hacker tools, but I’d love to be proven wrong. Hence the “Ask Hackaday”: why don’t we see more projects that re-use smartphones?
It is mind-boggling when you think about the computing power that fits in the palm of your hand these days. It wasn’t long ago when air-conditioned rooms with raised floors hosted computers far less powerful that filled the whole area. Miniaturization is certainly the order of the day. Things are getting smaller every day, too. We were so impressed with the minuscule entries from the first “Square Inch Project” — a contest challenging designers to use 1 inch2 of PCB or less — that we decided bring it back with the Return of the Square Inch Project. The rules really were simple: build something with a PCB that was a square inch.
Grand Prize
It was hard to pick, but there can only be one grand prize winner. This time around that honor goes to [Danny FR] for a very small smart motor driver for robotics. The little board takes an I2C link to a microcontroller and does PID control with RPM feedback. No need for an H-bridge or any sophisticated control electronics — that’s all onboard.
The board is a great fit for a motor and makes it easy to build moving projects. That was the grand prize, but there were some other great entries that won in specific categories, too.
Best Project
[Drix] likes to know where things are. The Hive Tracker uses laser “lighthouses” that sweep across the room. A special microcontroller with a dedicated hardware block reads the laser light and triangulates its position relative to the lighthouses with a great deal of precision. A picture’s worth a thousand words, so:
The high-speed reading of the lasers uses “Programmable Peripheral Interconnect” — a feature of a Nordic BLE microcontroller that lets the chip read timestamps in hardware without interrupting the processor. The little boards hook up to a hub board which is also pretty small.
We’re hackers, so we think a few bare PCBs connected to another PCB can be artistic. But most people have something different in mind.
Best Artistic Project
If you hang out at Hackaday.io much, you’ll recognize [ꝺeshipu] and his entry was one of those things that you immediately know you could use, but also brings a little smile to your face when you use it. How often do you need to plug some LEDs into a breadboard? Why not do it with a Rainbow Jellyfish?
The circuit operation should be obvious. We really liked the color-coded wiring. You could probably use at least two of these so they could keep each other company. You could probably even use this as part of a badge.
Best Social Media Award
Speaking of badges, [nwmaker] built a badge that looks like another animal — an owl called PurpleSnowy. Again, the circuit is simple enough, but what caught our eye on this project was how well the social media promotion of it was. Maybe cute owls are just easier to go viral, but we liked it.
Best Documentation
[Kris Winer] (remember that name), built a very high-tech spectrometer project. Not only was it small in size, but at $25 it was also small in price. The project used the AMS AS7265X 3-chip set to provide an 18 channel, 20 nm FWHM spectrometer. The documentation was very well done and we were impressed with the fitment of the chips on the board.
Many Runners-Up
We had so many great entries that it was hard to pick so we named several runners-up.
[Greg Davill’s] Bosun frame grabber that uses an FPGA to capture images from a FLIR Boson camera.
[Kris Winer’s] high-tech $25 spectrometer project (from above) was also runner-up, and [Kris] was also recognized for sensors that can smell and hear.
If you want something less science-related, the Rotovis-Mod1 by [zakqwy] makes it easier to build persistence of vision displays. Of course, as hackers, we love an oscilloscope and [Mark Omo’s] 20 msps scope that fits in one inch caught our imagination for making some really cool instrument panels.
You really should look at all the entries — they were amazing. [Kris] really went all out, taking two runner up slots and the best documentation prize.
Recap:
Speaking of prizes, The grand prize was $500, and the other prizes received $100 Tindie gift certificates. Thanks to OSH Park, the runner ups also got $100 OSH Park gift cards — that’s a lot of one inch PCBs.
Will this be our last inch square contest? The magic 8 ball says probably not, so don’t stop thinking small and look for your chance to enter your design in the next contest.
By using our website and services, you expressly agree to the placement of our performance, functionality and advertising cookies. Learn more
