Are Apple Trying To Patent The Home Computer 45 Years Too Late?

In our recent piece marking the 10th anniversary of the Raspberry Pi, we praised their all-in-one Raspberry Pi 400 computer for having so far succeeded in attracting no competing products. It seems that assessment might be premature, because it emerges that Apple have filed a patent application for “A computer in an input device” that looks very much like the Pi 400. In fact we’d go further than that, it looks very much like any of a number of classic home computers from back in the day, to the extent that we’re left wondering what exactly Apple think is novel enough to patent.

A Raspberry Pi 400 all-in-one keyboard console computer
Looks pretty similar to us.

Reading the patent it appears to be a transparent catch-all for all-in-one computers, with the possible exception of “A singular input/output port“, meaning that the only port on the device would be a single USB-C port that could take power, communicate with peripherals, and drive the display. Either way, this seems an extremely weak claim of novelty, if only because we think that a few of the more recent Android phones with keyboards might constitute prior art.

We’re sure that Apple’s lawyers will have their arguments at the ready, but we can’t help wondering whether they’ve fallen for the old joke about Apple fanboys claiming the company invented something when in fact they’ve finally adopted it years after the competition.

Thinking back to the glory days of 8-bit computers for a moment, we’re curious which was the first to sport a form factor little larger than its keyboard. Apple’s own Apple ][ wouldn’t count because the bulk of the machine is behind the keyboard, but for example machines such as Commodore’s VIC-20 or Sinclair’s ZX Spectrum could be said to be all-in-one keyboard computers. Can anyone provide an all-in-one model that predates those two?

You can read our Raspberry Pi 400 review if the all-in-one interests you.

Via Extreme Tech.

 

Screenshot of Pulseview showing capture and decode of some digital channels

Need A Logic Analyzer? Use Your Pico!

There’s a slew of hardware hacker problems that a logic analyzer is in a perfect position to solve. Whether you’re trying to understand why an SPI LCD screen doesn’t initialize, what’s up with your I2C bus, or determine the speed of an UART connection, you’ll really want to have a logic analyzer on hand. People have been using a Pi Pico as a logic analyzer in a pinch, and now [pico-coder] has shared a sigrok driver that adds proper support for a Pico to beloved tools like Pulseview.

The specs offered are impressive. Compared to the $10 “Saleae” clone analyzers we are so used to, this thing boasts 21 digital channels with up to 120 MHz capture speed, 3 ADC channels at up to 500 KHz, and hardware-based triggers. The GitHub repository linked above stores the driver files out-of-tree, but provides build instructions together with an easily flash-able uf2 firmware. It’s likely that you’ll soon see this driver in a stock Pulseview installation, however, given the submitter-friendly attitude we’ve witnessed on the sigrok mailing list. However, if you need a logic analyzer ASAP, you should follow the caringly offered quickstart guide.

We’ve covered Pulseview being used in combination with cheap accessible analyzers before — a must-watch if you need to get yourself up to speed on the value they provide to a hobbyist. If an oscilloscope is what you need and a smartphone is what you have, perhaps you’ll enjoy the Scoppy firmware for the Pico.

We thank [mip] for sharing this with us!

It’s Official! The Raspberry Pi Is Now 10!

In any given field there are epoch-defining moments, those events after which nothing was quite the same as it had been before. It’s been a decade since the launch of the first Raspberry Pi single board computer. This was by no means the first inexpensive computer board, nor was it the first to support the GNU/Linux operating system, but it was among the first to promise a combination of those two. Coupled with support from a crop of British 8-bit alumni meant that from when it first gained publicity in early 2011 it garnered a huge buildup of interest.

We were first teased with a USB stick style prototype, which morphed into a much larger Raspberry Pi alpha board and finally into pre-production boards much closer to the model launched at the end of February ten years ago.

How To Disappoint Every Single British Geek At 6 AM

An array of Pi prototype boards pictured on display at the Cambridge University Computer Laboratory.
An array of Pi prototype boards pictured on display at the Cambridge University Computer Laboratory.

Pedants will claim that the 10th birthday of the Pi is technically not yet upon us because those first Model B boards went on sale on the 29th of February 2012, a leap day. The two distributors, RS and Farnell, were both putting them on sale with the expectation of selling around 10,000 units — a prediction that proved woefully inadequate, with both websites collapsing under the weight of would-be Pi-purchasers within seconds of opening up at 6 AM.

I was ready to order at 6 AM, and was only able to order mine halfway through the day. That short wait would be just the beginning — because they received so many more orders than anticipated, the bulk of the orders weren’t fulfilled until May. Nobody had imagined how wildly successful the Pi boards would become. Continue reading “It’s Official! The Raspberry Pi Is Now 10!”

A Hombrew Retro Laptop

We feel bad when we see a retrocomputer project and think, “Hey! That’s not that old.” But, usually, when we think about it, it really is. Take the Penkesu. It looks like one of the little organizer computers that were popular — ok — a long time ago.

Inside is a Raspberry Pi Zero 2W, a 7.9 inch 400×1280 screen and a 48-key mechanical keyboard. Unsurprisingly, the case is mostly 3D printed, but it does use Gameboy Advance SP hinges.

Continue reading “A Hombrew Retro Laptop”

Tiny TV Celebrates The Forgotten Tech Of CRTs

For those of us who grew up before the Internet, the center of pretty much every house was the TV. It was the shrine before which we all worshipped, gathering together at the appointed times to receive the shared wisdom of mass entertainment. In retrospect, it really wasn’t that much. But it’s what we had.

Content aside, one thing all these glowing boxes had in common was that which did the glowing — the cathode ray tube (CRT). Celebrating the marvel of engineering that the CRT represents is the idea behind [Matt Evan]’s tiny desktop TV. The design centers around a 1.5″ CRT that once served as a viewfinder on a 1980s-vintage Sony camcorder. [Matt] salvaged the tube and the two PCB assemblies that drive it, mounting everything in a custom-built acrylic case, the better to show off the bulky but beautiful tube.

The viewfinder originally used a mirror to make the optical path more compact; this forced [Matt] to adapt the circuit to un-reverse the image for direct viewing. Rather than receiving analog signals off the air as we did in the old days — and we liked it that way! — the mini monitor gets its video from a Raspberry Pi, which is set to play clips of TV shows from [Matt]’s youth. Rendered in glorious black and white and nearly needing a magnifying glass to see, it almost recaptures the very earliest days of television broadcasting, when TVs all had screens that looked more like oscilloscope CRTs.

This project is a nice homage to a dying technology, and [Matt] says it has spurred more than one conversation from people you grew up knowing only LCD displays. That’s not to say CRTs are totally dead — if you want to build your own old-school TV, there’s a kit for that.

BenAkrin-PlottyBot-TypeWriterMode

PlottyBot: A DrawBot That Plots A Lot

Fire up those 3D printers because if you’re like us, you’ll want your own PlottyBot. Still, have a pile of “thank you notes” to write from recent winter holiday gift exchanges? Hoping to hand letter invitations to a wedding or other significant event? Need some new art to adorn your lock-down shelter or shop? It sounds like [Ben] could help you with that.

Besides being a handsomely designed desktop DrawBot, this project from [Ben] looks to have some solid software to run it, a community of makers who have tested the waters, and very detailed build instructions. Those include everything from a BOM with links for ordering parts to animated GIF assembly for the trickier steps.

If you’d like to graduate from “handwritten” cards and letters to something poster-sized are customization tips for expanded X and Y dimensions. As we’ve included in other recent articles, one caveat to mention is the current scarcity of the Raspberry Pi Zeros that PlottyBots require. But if you have one on hand or think you’ll be able to source one by the time you’ve 3D printed all the parts, it might just be the perfect time to add another bot to your family. As a heads up, this project is self-hosted on a solar-powered server, so maybe take turns reading the complete build log.

A nice bonus if you need help drawing something suitably complex to require a robot’s help, [Ben] also created MandalGaba which looks like an awesome online tool for drawings like the ones shown above.

No ARM Printer Driver? Just Write Your Own

When you think of the small machines that print the sticky labels on packages, you might not expect to find a complex printer with its own programming language (ZPL). However, [Dan Pastusek] was looking around online and found a small label printer on everyone’s favorite online warehouse for a great price that suggested it supported ZPL. Unfortunately, [Dan] had big dreams for creating a Raspberry Pi-based print station and found the drivers packaged for this particular printer were not ARM compatible. Not quite content to leave it there, he began to chip away at the layers until he had a working driver.

ZPL, at its core, is just a language describing ASCII commands transmitted over a serial connection. So while the printer showed up as an endpoint, it wasn’t working as the filters (the part of the driver that knows how to convert from a PNG to ZPL) was x86 only. On Linux, printer drivers also have a PPD file that describes what a printer can handle in paper size and other settings. The PPD file for the little printer gave the first clue. In the ShortNickName field, it identifies itself as HPRT N41, which is a popular HP printer. So this little printer must be a clone of a printer in that family. Notably, they don’t support ZPL. Instead, the HPRT series support TSPL, another printer language developed by TSC.

This presented a problem as the shipping service that provided the labels that [Dan] was using offered labels in three formats: PNG, PDF, and ZPL. Currently, it does seem like there’s a TSPL to ZPL converter out there for use, so rather than write his own, he took a shortcut and wrote a rasterizer instead. Initially, he tried to use some sample code that he found, and while he got something to come out of the printer, it was blank. So the next test was to save the raw TSPL output from a filer and cat directly to the serial port. This worked amazingly. Next, he wrote a converter to take a PNG and convert them into the bitmap format the TSPL has. The converter is in Javascript as it runs as part of the webserver that manages the print station. Could it be faster in a different language? Sure. But a different language wouldn’t make the printer any faster.

With the addition of a wireless barcode scanner, it’s satisfying to see the print station up and running. Here at Hackaday, we’re no stranger to seeing folks take apart printers to peel back the software and physical layers that make them up.