Inputs Of Interest: The OrbiTouch Keyless Keyboard And Mouse

I can’t remember how exactly I came across the OrbiTouch keyboard, but it’s been on my list to clack about for a long time. Launched in 2003, the OrbiTouch is a keyboard and mouse in one. It’s designed for people who can’t keyboard regularly, or simply want a different kind of experience.

The OrbiTouch was conceived of by a PhD student who started to experience carpal tunnel while writing papers. He spent fifteen years developing the OrbiTouch and found that it could assist many people who have various upper body deficiencies. So, how does it work?

It’s Like Playing Air Hockey with Both Hands

To use this keyboard, you put both hands on the sliders and move them around. They are identical eight-way joysticks or D-pads, essentially. The grips sort of resemble a mouse and have what looks like a special resting place for your pinky.

One slider points to groups of letters, numbers, and special characters, and the other chooses a color from a special OrbiTouch rainbow. Pink includes things like parentheses and their cousins along with tilde, colon and semi-colon. Black is for the modifiers like Tab, Alt, Ctrl, Shift, and Backspace. These special characters and modifiers aren’t shown on the hieroglyphs slider, you just have to keep the guide handy until you memorize the placement of everything around the circle.

You’re gonna need a decent amount of desk space for this. Image via OrbiTouch

The alphabet is divided up into groups of five letters which are color-coded in rainbow order that starts with orange, because red is reserved for the F keys. So for instance, A is orange, B is yellow, C is green, D is blue, E is purple, then it starts back over with F at orange. If you wanted to type cab, for instance, you would start by moving the hieroglyph slider to the first alphabet group and the color slider to green.

Continue reading “Inputs Of Interest: The OrbiTouch Keyless Keyboard And Mouse”

Add Creativity To Your BOM: Hack Chat

Join us on Wednesday, October 14th at noon Pacific for the Harnessing Your Creativity Hack Chat with Leo Fernekes!

You’re sitting at your bench, surrounded by the tools of the trade — meters and scopes, power supplies and hand tools, and a well-stocked parts bin. Your breadboard is ready, your fingers are itching to build, and you’ve got everything you need to get started, but — nothing happens. Something is missing, and if you’re like many of us, it’s the one thing you can’t get from eBay or Amazon: the creative spark that makes innovation happen.

Creativity is one of those things that’s difficult to describe, and is often noticed most when it’s absent. Hardware hacking requires great buckets of creativity, and it’s not always possible to count on it being there exactly when it’s called for. It would be great if you could somehow reduce creativity to practice and making it something as easy to source for every project as any other commodity.

While Leo Fernekes hasn’t exactly commoditized creativity, judging from the breadth of projects on his YouTube channel, he’s got a pretty good system for turning ideas into creations. We’ve featured a few of his builds on our pages, like a discrete transistor digital clock, the last continuity tester you’ll ever need, and his somewhat unconventional breadboarding techniques. Leo’s not afraid to fail and share the lessons learned, either.

His projects, though, aren’t the whole story here: it’s his process that we’re going to discuss. Leo joins us for this Hack Chat to poke at the creative process and see what can be done to remain rigorous and systematic in your approach but still make the process creative and flexible. Join us with your questions about finding the inspiration you need to turn parts and skills into finished projects that really innovate.

join-hack-chatOur Hack Chats are live community events in the Hackaday.io Hack Chat group messaging. This week we’ll be sitting down on Wednesday, October 14 at 12:00 PM Pacific time. If time zones baffle you as much as us, we have a handy time zone converter.

Click that speech bubble to the right, and you’ll be taken directly to the Hack Chat group on Hackaday.io. You don’t have to wait until Wednesday; join whenever you want and you can see what the community is talking about.

Continue reading “Add Creativity To Your BOM: Hack Chat”

Ask Hackaday: With Landline Use In Decline, What’s To Be Done With The Local Loop?

Walking is great exercise, but it’s good for the mind too: it gives one time to observe and to think. At least that’s what I do on my daily walks, and being me, what I usually observe and think about is the local infrastructure along my route. Recently, I was surprised to see a number of telephone company cabinets lying open next to the sidewalk. Usually when you see an open box, there’s a telephone tech right there, working on the system. But these were wide open and unattended, which I thought was unusual.

I, of course, took the opportunity to check out the contents of these pedestals in detail. Looking at the hundreds of pairs of brightly colored wire all neatly terminated and obviously installed and maintained at great expense, I was left wondering why someone would leave such a valuable asset exposed to the elements. With traditional POTS, or plain old telephone service, on the decline, the world may no longer have much use for the millions of miles of copper cable feeding back to telco central offices (COs) anymore. But there’s got to be something this once-vital infrastructure is still good for, leading me to ask: what’s to be done with the local loop?

Continue reading “Ask Hackaday: With Landline Use In Decline, What’s To Be Done With The Local Loop?”

Hackaday Links Column Banner

Hackaday Links: October 11, 2020

If you’re interested in SDR and digital signal processing but don’t know where to start, you’re in luck. Ben Hillburn, president of the GNU Radio Project, recently tweeted about an online curriculum for learning SDR and DSP using Python. The course was developed by Dr. Mark Lichtman, who was a lead on GNU Radio, and from the look of it, this is the place to go to learn about putting SDRs to use doing cool things. The course is chock full of animations that make the concepts clear, and explain what all the equations mean in a way that’s sure to appeal to practical learners.

It’s not much of a secret that the Hackaday community loves clocks. We build clocks out of everything and anything, and any unique way of telling time is rightly applauded and celebrated on our pages. But does the clock motif make a good basis for a video game? Perhaps not, but that didn’t stop Clock Simulator from becoming a thing. To “play” Clock Simulator, you advance the hands of an on-screen clock by pressing a button once per second. Now, thanks to Michael Dwyer, you don’t even have to do that one simple thing. He developed a hardware cheat for Clock Simulator that takes the 1PPS output from a GPS module and wires it into a mouse. The pulse stream clicks the mouse once per second with atomic precision, rendering the player irrelevant and making the whole thing even more pointless. Or perhaps that is the point.

Maybe we were a little hard on Clock Simulator, though — we can see how it would help achieve a Zen-like state with its requirement for steady rhythm, at least when not cheating. Another source of Zen for some is watching precision machining, and more precise, the better. We ran into this mesmerizing video of a CNC micro-coil winder and found it fascinating to watch, despite the vertical format. The winder is built from a CNC lathe, to the carriage of which a wire dispenser and tensioning attachment have been added. The wire is hair-fine and passes through a ruby nozzle with a 0.6 mm bore, and LinuxCNC controls the tiny back and forth motion of the wire as it winds onto the form. We don’t know what the coil will be used for, but we respect the precision of winding something smaller than a matchhead.

Dave Jones over at EEVblog posted a teardown video this week that goes to a place few of us have ever seen: inside a processor module for an IBM System/390 server. These servers earned the name “Big Iron” for a reason, as everything about them was engineered to perform. The processor module Dave found in his mailbag was worth $250,000 in 1991, and from the look of it was worth every penny. From the 64-layer ceramic substrate supporting up to 121 individual dies to the stout oil-filled aluminum enclosure, everything about this module is impressive. We were particularly intrigued by the spring-loaded copper pistons used to transfer heat away from each die; the 2,772 pins on the other side were pretty neat too.

Here’s an interesting question: what happens if an earthquake occurs in the middle of a 3D printing run? It’s probably not something you’ve given much thought, but it’s something that regular reader Marius Taciuc experienced recently. As he relates, the magnitude 6.7 quake that struck near Kainatu in Papua New Guinea (later adjusted to a 6.3 magnitude) resulted in a solid 15 seconds of shaking at his location, where he was printing a part on his modified Mendel/Prusa i2. The shaking showed up clearly in the part as the machine started swaying with the room. It’s probably not a practical way to make a seismograph, but it’s still an interesting artifact.

Hardware Vs Software: Fight!

It’s one of the great cliches in the hacker world: the hardware type and the software type. You can tell which of these two you are quite easily. When a project is actually 20% done, but you think it’s 90% done, and you say to yourself “And the rest is a simple matter of software”, you’re a hardware type. Ask anyone who has read my code, and they’ll tell you, I’m a hardware type.

Along with my blindness to the difficulties of getting the code right, I’ve also admittedly got an underappreciation of what powers lie in the dark typing arts. But I am not too proud to tip my hat when I see an awesome application of the soft stuff. Case in point: this Go board sequencer that we ran last week. An overhead webcam parses players’ moves as they put black and white stones down while playing the game of Go, and turns this into music.

The pure software type will be saying “but there’s a webcam and a Go board”. And indeed, that’s true. There are physical elements to this project that anchor it in the shared reality of the two people playing. But a hardware project this isn’t; it’s OpenCV and Max/MSP that make it work.

For comparison, look at the complexity of this similar physical sequencer. It’s got a 16 x 16 array of LEDs and switches and a CNC milled, primed, and painted surface that’s the size of a twin bed. Sawdust and hand-soldering: that’s a hardware project.

What I love about the Go sequencer is that it uses software just right. The piece is still physical. It could have just as easily been a VR world, where the two people would interact with each other only inside their goggles. But somehow that’s not quite as human as putting stones on a wooden board, sitting across from, and maybe even looking at, your opponent. The players aren’t forced to think about the software. They don’t feel like they’re playing a video game.

But at the same time, the software side of things makes all of the horrible hardware problems go away. Nobody is soldering a rat’s nest of 169 switches. There’s a webcam plugged into the USB port of a laptop. There’s a deep simplicity there.

Should you always trade out arcade buttons for OpenCV? Absolutely not! But is it worth considering the soft side when doing it in hardware is just too, well, hard? I’m open.

Hackaday Podcast 088: Flywheel Trebuchet, Thieving Magpies, Hero Engines, And Hypermiling

Hackaday editors Elliot Williams and Mike Szczys riff on the hardware hacks that took the Internet by storm this week. Machining siege weapons out of aluminum? If they can throw a tennis ball at 180 mph, yes please! Welding aficionados will love to see the Hero Engine come together. We dive into the high-efficiency game of hypermiling, and spin up the polarizing topic of the Sun Cycle. The episode wouldn’t be complete without hearing what the game of Go sounds like as a loop sequencer, and how a variable speed cassette player can be abused for the benefit of MIDI lovers the world over.

Take a look at the links below if you want to follow along, and as always, tell us what you think about this episode in the comments!

Take a look at the links below if you want to follow along, and as always, tell us what you think about this episode in the comments!

Direct download (60 MB or so.)

Continue reading “Hackaday Podcast 088: Flywheel Trebuchet, Thieving Magpies, Hero Engines, And Hypermiling”

This Week In Security: Code Scanning, Information Gathering, And Seams In The Cloud

GitHub has enabled free code analysis on public repositories. This is the fruit of the purchase of Semmle, almost exactly one year ago. Anyone with write permissions to a repository can go into the settings, and enable scanning. Beyond the obvious use case of finding vulnerabilities, an exciting option is to automatically analyse pull requests and flag potential security problems automatically. I definitely look forward to seeing this tool in action.

The Code Scanning option is under the Security tab, and the process to enable it only takes a few seconds. I flipped the switch on one of my repos, and it found a handful of issues that are worth looking in to. An important note, anyone can run the tool on a forked repo and see the results. If CodeQL finds an issue, it’s essentially publicly available for anyone who cares to look for it.

Simpler Code Scanning

On the extreme other hand, [Will Butler] wrote a guide to searching for exploits using grep. A simple example, if raw shows up in code, it often signals an unsafe operation. The terms fixme or todo, often in comments, can signal a known security problem that has yet to be fixed. Another example is unsafe, which is an actual keyword in some languages, like Rust. If a Rust project is going to have vulnerabilities, they will likely be in an unsafe block. There are some other language-dependent pointers, and other good tips, so check it out.

Continue reading “This Week In Security: Code Scanning, Information Gathering, And Seams In The Cloud”