One-handed PS-OHK Keyboard Doesn’t Need Chording Or Modifier Keys

Most one-handed keyboards rely on modifier keys or chording (pressing multiple keys in patterns) to stretch the functionality of a single hand’s worth of buttons. [Dylan Turner]’s PS-OHK takes an entirely different approach, instead putting 75 individual keys within reach of a single hand, with a layout designed to be practical as well as easy to get used to.

We can’t help but notice Backspace isn’t obvious in the prototype, but it’s also a work in progress.

The main use case of the PS-OHK is for one hand to comfortably rest at the keyboard while the other hand manipulates a mouse in equal comfort. There is a full complement of familiar special keys (Home, End, Insert, Delete, PgUp, PgDn) as well as function keys F1 to F12 which helps keep things familiar.

As for the rest of the layout, we like the way that [Dylan] clearly aimed to maintain some of the spatial relationship of  “landmark” keys such as ESC, which is positioned at the top-left corner of its group. Similarly, arrow keys are grouped together in the expected pattern.

One-handed keyboards usually rely on modifier keys or multi-key chording and it’s interesting to see work put into a different approach that doesn’t require memorizing strange layouts or input patterns.

Want to make your own? The GitHub repository has everything you need. Accommodating the 75 physical keys requires a large PCB, but it’s a fairly straightforward shape and doesn’t have any oddball manufacturing requirements, which means getting it made should be a snap.

Watch SLS 3D Printed Parts Become Printed Circuits

[Ben Krasnow] of the Applied Science channel recently released a video demonstrating his process for getting copper-plated traces reliably embedded into sintered nylon powder (SLS) 3D printed parts, and shows off a variety of small test boards with traces for functional circuits embedded directly into them.

Here’s how it works: The SLS 3D printer uses a laser to fuse powdered nylon together layer by layer to make a plastic part. But to the nylon powder, [Ben] has added a small amount of a specific catalyst (copper chromite), so that prints contains this catalyst. Copper chromite is pretty much inert until it gets hit by a laser, but not the same kind of laser that sinters the nylon powder. That means after the object is 3D printed, the object is mostly nylon with a small amount of (inert) copper chromite mixed in. That sets the stage for what comes next.

Continue reading “Watch SLS 3D Printed Parts Become Printed Circuits”

A Closer Peek At The Frame AR Glasses

The Frame AR glasses by Brilliant Labs, which contain a small display, are an entirely different approach to hacker-accessible and affordable AR glasses. [Karl Guttag] has shared his thoughts and analysis of how the Frame glasses work and are constructed, as usual leveraging his long years of industry experience as he analyzes consumer display devices.

It’s often said that in engineering, everything is a tradeoff. This is especially apparent in products like near-eye displays, and [Karl] discusses the Frame glasses’ tradeoffs while comparing and contrasting them with the choices other designs have made. He delves into the optical architecture, explaining its impact on the user experience and the different challenges of different optical designs.

The Frame glasses are Brilliant Labs’ second product with their first being the Monocle, an unusual and inventive sort of self-contained clip-on unit. Monocle’s hacker-accessible design and documentation really impressed us, and there’s a pretty clear lineage from Monocle to Frame as products. Frame are essentially a pair of glasses that incorporate a Monocle into one of the lenses, aiming to be able to act as a set of AI-empowered prescription glasses that include a small display.

We recommend reading the entire article for a full roundup, but the short version is that it looks like many of Frame’s design choices prioritize a functional device with low cost, low weight, using non-specialized and economical hardware and parts. This brings some disadvantages, such as a visible “eye glow” from the front due to display architecture, a visible seam between optical elements, and limited display brightness due to the optical setup. That being said, they aim to be hacker-accessible and open source, and are reasonably priced at 349 USD. If Monocle intrigued you, Frame seems to have many of the same bones.

Programming Robots Is Hard, Figuring Out How To Make It Easier Is Harder

[Benjie Holson] is an experienced roboticist and wrote an interesting article published on IEEE Spectrum about how the idea most people have of non-roboticists is a myth, and efforts to target this group with simplified robotic frameworks tend to be doomed.

Now, let’s make a couple things absolutely clear right up front: He is not saying robots shouldn’t be easier to program, nor is he saying that non-roboticists literally do not exist (of course they do.) The issues he’s highlighting really come down to product design.

[Benjie] points out that programming robots is super hard, but it’s also hard in more than one way and for more than one reason. And when people try to create a product to make it easier, they tend to commit two big product design no-no’s: they focus on the wrong hard parts, and they design their product for a vaguely-defined audience that doesn’t really exist. That group is the mythical non-roboticist.

These are actually very solid points to make in terms of product design in general. Designing a product that solves the wrong problems for a poorly-defined group isn’t exactly a recipe for success. [Benjie]’s advice on making a truly effective and useful API framework that genuinely lowers the bar of complexity in a useful way is similarly applicable to product design in general.

His first piece of advice is not to design for poorly-defined amorphous groups. Your product should serve actual needs of actual users. If you cannot name three people you have actually spoken to who would be helped by your product, you are designing for an amorphous (and possibly imaginary) group.

The second is to design as though your users are just as smart as you are, just less tolerant of problems stemming from rough edges like compatibility and configuration issues. Remove those so that your users can get useful work done without having to re-invent the wheel, or resort to workarounds.

Robotic frameworks like ROS are useful and extensible, but whenever someone attempts to focus on creating a simplified framework, [Benjie] says they tend to step on the same rakes. It’s a mistake [Benjie] has committed himself, and see repeated by others. We think his advice is good product design advice in general, whether for designing APIs or something else.

The Guinness Brewery Invented One Of Science’s Most Important Statistical Tools

The Guinness brewery has a long history of innovation, but did you know that it was the birthplace of the t-test? A t-test is usually what underpins a declaration of results being “statistically significant”. Scientific American has a fascinating article all about how the Guinness brewery (and one experimental brewer in particular) brought it into being, with ramifications far beyond that of brewing better beer.

William Sealy Gosset (aka ‘Student’), self-trained statistician. [source: user Wujaszek, wikipedia]
Head brewer William Sealy Gosset developed the technique in the early 1900s as a way to more effectively monitor and control the quality of stout beer. At Guinness, Gosset and other brilliant researchers measured everything they could in their quest to optimize and refine large-scale brewing, but there was a repeated problem. Time and again, existing techniques of analysis were simply not applicable to their gathered data, because sample sizes were too small to work with.

While the concept of statistical significance was not new at the time, Gosset’s significant contribution was finding a way to effectively and economically interpret data in the face of small sample sizes. That contribution was the t-test; a practical and logical approach to dealing with uncertainty.

As mentioned, t-testing had ramifications and applications far beyond that of brewing beer. The basic question of whether to consider one population of results significantly different from another population of results is one that underlies nearly all purposeful scientific inquiry. (If you’re unclear on how exactly the t-test is applied and how it is meaningful, the article in the first link walks through some excellent and practical examples.)

Dublin’s Guinness brewery has a rich heritage of innovation so maybe spare them a thought the next time you indulge in statistical inquiry, or in a modern “nitro brew” style beverage. But if you prefer to keep things ultra-classic, there’s always beer from 1574, Dublin castle-style.

Intentionally Overly-Complex Clock Is Off To A Good Start

[Kelton] from Build Some Stuff decided to create a clock that not only had kinetic elements, but a healthy dose of Rube Goldberg inspiration. The result is a work in progress, but one that looks awfully promising.

The main elements of the design are rotating pieces that indicate the hours and minutes, but each hour is advanced solely by the satisfying physical culmination of multiple interacting systems. Those systems also completely reset themselves every hour.

Each hour, a marble run kicks off a short chain reaction that culminates in advancing the hour.

At the top of the hour, a marble starts down a track and eventually tips over a series of hinged “dominoes”, which culminate in triggering a spring-loaded ratchet that advances the hour. The marble then gets carried back to the top of the device, ready for next time. Meanwhile, the domino slats and spring-loaded ratchets all get reset by a pulley system.

There’s still some work to do in mounting the motor, pulley system, and marble run. Also, a few bugs have surfaced, like a slight overshoot in the hour display. All par for the course for a device with such a large number of moving parts, we suppose.

[Kelton] has a pretty good sense how it will all work in the end, and it looks promising. We can’t wait to see it in its final form, but the tour of clock so far is pretty neat. Check it out in the video, embedded just under the page break.

As for the clock’s inspiration, Rube Goldberg’s cultural impact is hard to overstate and our own Kristina Panos has an excellent article about the man that might just teach you something you didn’t know.

Continue reading “Intentionally Overly-Complex Clock Is Off To A Good Start”

Make A Super Cute LiDAR Measurement Module

This ultra-cute tiny LiDAR rangefinder project by [gokux] can be thought of as a love letter to the incredible resources and components hobbyists and hackers of all types have access to nowadays. In fact, it all stemmed from coming across a miniscule half-inch 64×32 OLED display module that was simply too slick to pass up.

USB connector for charging on the bottom, hole for distance sensor out the top.

To use it, one simply powers it on and the display will read out the distance in millimeters. The VL53L0X time-of-flight sensor inside works by sending out a laser pulse and measuring how long it takes for the pulse to bounce back. We hope you’re curious about what such a sensor looks like on the inside, because here’s a nifty teardown of these fantastic devices. The device can technically measure distances of up to 2 m, but [gokux] says accuracy drops off after 1 m.

The main components besides the OLED display and VL53L0X sensor are an ESP32-C3 board (which handily integrates battery charging circuitry), 3D-printed enclosure, tiny rechargeable battery, and power switch. The whole thing is under one cubic inch. Not bad, and it even makes a passable keychain. Parts list, code, and 3D model files, including STEP format, are all available if you’d like to spend an afternoon making your own.