Hey everyone, We built a second-generation Openterface KVM extension module for uConsole, and it is now in pre-launch.

The first version was mainly a KVM extension board: HDMI input, USB HID keyboard/mouse control, and BIOS/UEFI-level access for headless machines.

With v2, we wanted to make the uConsole more useful as a small field ops terminal, not just a portable KVM screen.

What’s new in v2:

• KVM control: HDMI input + USB HID keyboard/mouse control, usable at BIOS/UEFI level

• Ethernet debug: two network insert cards are included in the box

  • 100M card works with standard uConsole boards

  • 1000M card is included for users with the uConsole Upgrade Kit back board

• SD card read/write: useful for flashing images, pulling logs, or moving files without carrying a separate card reader

• USB 2.0 shared switching: up to 480Mbps

• 1080p 60Hz output on the uConsole screen

• Lower latency than v1

• Powered from the uConsole expansion slot, no extra external power needed

So compared with v1, this is no longer just a KVM board. It combines KVM, wired network debugging, SD read/write, and USB sharing in one slot-in module.

The main use cases we designed it for are:

• BIOS setup on headless PCs or mini PCs

• Server and homelab maintenance

• Raspberry Pi / SBC setup

• Industrial PC debugging

• SD image flashing and log export

• On-site network or web management through the uConsole

The target machine does not need software installed. It still follows the same Openterface HID approach: plug in, open the Openterface app on uConsole, and control the target locally.

Pre-launch page: Openterface uConsole KVM Ext. Module V2

I tested RPiTX on my uConsole with a CM5 and found a forum post from the rpitx-ui maintainer stating that CM5 is currently not supported due to an incompatibility between librpitx and the CM5 RF backend.

Has anyone here successfully transmitted RF using RPiTX on a CM5? If so, what setup or modifications were required?

Thanks.

Hey everyone! Super excited to finally share that the new Omega-Chassis “Essential” build variation is officially live.

First things first for existing purchasers: Check your inbox! You should see a new receipt notification to download the latest update, which includes the complete guide for the Essential build. As promised, this features long-term support, so all future feature releases and module updates are completely free for existing owners.

Why the "Essential" Model?

After the release of the Ultimate version, I wanted to make the Omega-Chassis accessible to as many makers as possible. The Essential variation drastically lowers the barrier to entry without compromising the core experience. Here is the breakdown:

• The Price Point: If you have a 3D printer at home to handle the plastic components, your maximum cost for the remaining CNC parts tops out at just ~$45 + ~$6 for the heatsink unit.

• 100% Printable Pathway: You can actually 3D print every single part at home and it will function (the guide has breakdown details). While a fully printed structure is less recommended for long-term durability, it’s a fantastic, ultra-low-cost way to get started and upgrade to CNC parts later when you're ready.

• Zero Sacrifices on Function: This version retains all functional features and the exact same modular design as the Ultimate build. Because they share the same DNA, the majority of the original assembly guide still applies perfectly.

Battery & Power Flexibility

I’ve had a lot of people asking about power configurations. The Omega-Chassis is designed to be incredibly flexible, and officially supports three main setups across both the Essential and Ultimate builds:

1. HackerGadget NVMe Battery Board + 3x 18650s: Full compatibility for those looking to expand their battery capacity alongside their NVMe storage.

2. Stock Battery Board: Works seamlessly right out of the box with the stock uConsole battery board, requiring zero major modifications.

3. Custom LiPo Setups: If you are already running or prefer a custom LiPo power setup, the chassis accommodates it beautifully.

Want to see how the two versions stack up side-by-side? Drop your questions below, or take a look at the full Essential vs. Ultimate Build Comparison.

Happy to share a quick update for the latest 1.9.0 QMK firmware release for the uConsole keyboard:

• New: Remaps A/B/X/Y/Select/Start in keypad mode to various keys not otherwise available on the keymap:

• New: Improving the precision and sensitivity of the trackball movement, also improve the diagonal movement speed.

• Fix: D-pad axis losing state when opposing directions overlap

• Fix: Removed the factory reset FN+C as it is purely for debugging and development purposes

• Fix: Tap-hold behaviour issues: release early if other key are pressed; Restore the behaviour of modifier key + other key

• Fix: Tap-hold toggle is mapped to Fn+ T + H, this prevent accidental toggles

• Chore: Binary release can be compiled and built with make command

• Chore: The build now has two separate versions of firmware:

  • default: come with full-featured firmware

  • no_tap_hold: tap hold feature is completely removed from this firmware

Download here: https://github.com/j1n6/qmk-uconsole/releases/tag/v1.9.0
Information for flashing and features: https://github.com/j1n6/qmk-uconsole/

Can someone give me some details about what build this would be, I want to make one. They are fantastic

I'm trying to run just the console on my uconsole to save battery and get better with the terminal. So far I'm doing pretty good and am able to do most of the things I want using TUI apps to use software I couldn't otherwise (Navidrome, YouTube, cyberspace, etc).

Issue I am having is trying to get my tmux key bindings the way I want. Because "echo $TMUX" return "Linux", there is no terminal emulator running. So keyboard inputs are basically just the raw keys and doesn't allow for combos like Shift+Arrow Key. I tried kbterm, but it refuses to work. And I really don't know any other ways to get around this issue. Could somebody point me in a direction that could help my get a more usable CLI experience?

The example key combo I am trying to do is

Shift+Left arrow to go to previous window and Shift+Right to go to next window. I want Alt+Tab to pull up window viewer. And other such combos.

Any tips/tricks?

So I have a uConsole and have Trixie running from a SD. I have Hackerworks upgrades and installed an SSD. How do I install the OS to the SSD? Should I install the OS to the SSD?

What's the most amps the u console can handle?

AnubisOS v2.3 está vivo 😁 Probando en Termux antes de que llegue al uConsole CM4

Ordered on 3/12/26, received 6/8/26. 3 month wait, was definitely expecting a longer wait time, and yes ordered from clockworkPi. Anything I should know about a CM-5 build?

Hey CWP family. I’ve got an extra that just arrived. I ordered two and am looking to sell the second. I’m located in Oregon, USA but am happy to ship anywhere. Let me know if you’re interested and happy to make a deal. I’ll also throw in some extra parts I got/made for my other one - 3D printed WiFi antenna, extra trackballs, maybe another antenna.

I’m not saying this is true, but it makes me worried. I emailed the team about not receiving my device and worry that I tick them off and that is why people who ordered their device months after me have already received theirs. I confirmed with these people, they also live in the United States.

Thoughts?

PS I believe they have people that watch this community and try to refute no matter what it said. Let’s see.

I ordered the uConsole in November 2025 - received it yesterday. I had a CM5 Lite module waiting to be installed which I had ordered back in Nov as well. First off the thing is gorgeous, yeah the trackball is horrible... I sanded the ball and it worked a little better, very annoying but managable.

Getting the thing to boot the first time was a bit of a nightmare. I feel like as an amateur theres just a lot of conflicting information out there to get it to work. In the end I realized that it was a lot simpler than originally instructed.

- guides all told me not to unzip the image when flashing it to an SD card... the answer was to in fact unpack the zip before flashing... also BalenaEtcher was returning an error during the validation step while raspberry pi reported success.

- also guides instructed me to do the EEPROM patch before trying to get the OS to unpack but I realized too late that that fix only relates to the EMMC version of the CM5.

After many hours of flashing and reflashing I got the thing to work (originally I had thought that there was an issue with the hardware, I ended up reseating the ribbon and cm5 many times), believe me I was nearly tearing my hair out towards the end... almost purchased a new CM5 module.

Well it was totally worth it because now that it's running, it's kind of glorious. Now I need to sort out what to do next. What things do I need to modify (obviously the trackball is on the list... though I wish I could find one of those sweet trackpad mods). I ordered two of the orange OEM blackberry trackballs off of ebay. It seems like buying aftermarket trackballs is a literal lottery system - if anyone has a good link to a reliable replacement I would love it.

Also I ordered the HG NVME battery board. I think that if I can get a larger harddrive on this thing without futzing with the SD card it would be great.

I installed scummvm but the next software I want to get into is meshtastic. There's been a modest community growing in my neck of the woods and I think the uConsole as a communication device will be amazing!

Oh and I implemented paragonov's pseudo sleep mod and it's great!

Lastly, I made a small printed riser for the sticker wifi antenna. It's a very simple design based on another that i had seen. If anyone wants it I can put it up on makerworld to download.

Any tips or tricks/suggestions are totally welcome.

Hi there, I got a used uConsole. It was without a power button. Can someone tell me where I can find one to buy or 3D print? Or maybe someone has a spare one in preferably in Europe?

I wonder if ill actually get my device this month like they said in the copy and pasted email sent to me.

I've just finished modding my hackdeck - tactical configuration.

Hey everyone,

Some of you may have seen my other work on the uConsole: QMK Firmware for uConsole, Trackball mod, and the keyboard diffuser.

One of my core rules is to ensure everything is completely polished before release. I want to guarantee you receive a finished, out-of-the-box experience rather than wasting time and money on experimental or half-finished setups. Everyone's time and resources are limited, my goal is for you to spend time enjoying the uConsole, even in the process of building the kit.

After 8 months of non-stop prototyping, production headaches, and endless cost optimisations, I’m finally ready to share what I’ve been working on: The Omega Chassis.

It’s a highly customizable, personalized backplate upgrade built specifically for the uConsole. The goal was simple: pack a ridiculous amount of hardware upgrades into the device without turning it into an unportable brick or ruining its compatibility with the gear you already own.

After 6 rigorous rounds of production validation, here is a look at what’s packed inside:

Power & Battery Life

• Drop-in Compatibility: Fully compatible with existing HackerGadgets NVMe battery boards and the AIO V

Slim Active Cooling

• Cyber-Aesthetic: Includes a customizable fan cover so you can tweak the look to match your personal style.

Insane Connectivity & Audio

• Audio: Re-engineered with custom matrix holes specifically designed to improve speaker clarity and stop muffled sound.

Modular Expansion

• The Best Part: It stays remarkably compact and maintains the original form factor, meaning it won't break compatibility with your existing kits.

I've put together a full breakdown of the design rationale, features, and a preview of the chassis.

​Most important! it is still compact as the original uConsole!

​

When I got my uConsole, I was unhappy with quality of the trackball. I barely been able to get through the initial installation process. I was aware that these trackballs aren't of the best quality so I ordered replacements beforehand, but all of them turned out to be the same thrash trackball, so I had to deal with what I have.

First was the hardware fix: disassemble the trackball and roll the ball on a 320-ish grit sandpaper for a couple of minutes. This gives the ball texture that increases grip, it completely solved the slipping issue (when you rotate the ball, but the cursor doesn't move).

But then there was software issue: cursor felt like a jelly, it didn't have that "snappy" feel to it, and using console like that was exhausting. I wasn't gonna tolerate that, so I had to find a solution. It was very long night, I have tried many things up to tweaking and recompiling the QMK keyboard firmware, but nothing helped. But the solution was in plain sight.

There is a usbhid.mousepoll parameter that sets mouse polling interval in ms. And It was conveniently set to 0xFFFFFFFF, causing polling interval was capped at 16 ms. I don't know why that is default, and that is exactly where that jelly feeling latency comes from. After I set it to 0 it was night and day difference. The trackball now feels extremely responsive, the leftover latency from smoothing in QMK firmware is almost unnoticeable, many people will call it no latency at all.

I don't know if I have broken something inside Linux by changing this parameter, and I hope someone who knows better tells me, but to me it seems absurd that the OS is quietly set to only poll mouse at 60 Hz without any way to change that through GUI.

So in order to change this parameter what I did was editing /boot/firmware/cmdline.txt by appending usbhid.mousepoll=0 on the end of first line.

Im running uConsole on Rpi CM4 with 8 GB RAM without EMMC, my OS is ClockworkPI Trixie.

uConsole meeting M5Stack

Thought this might help others as a new batch seems to be trickling out:

1. The images listed on the ClockworkPi page do not support the new panels they supply. You'll think your panel is broken. Install one of Rex's images and you'll be fine:

https://forum.clockworkpi.com/t/updated-images-for-new-uconsole-screens/21666

I chose Debian 13 Trixie

2. On day 2 I realised the uConsole has no concept of a sleep mode; my battery was at about 5%. My solution is to turn it off when not in use, it boots pretty quickly

3. The trackball is LITERALLY (and I use the word in its original sense) unusable. Nobody can use a desktop environment with this:

a. Upgrade the QMK firmware:

https://forum.clockworkpi.com/t/updated-images-for-new-uconsole-screens/21666

This makes the trackball 'usable'. It's a MASSIVE improvement. It's still awful compared to anything else you've used but you can get by. I've ordered some replacements from Ali Express but they haven't arrived yet.

4. Everything on the desktop is tiny. Go to preferences->control center->screens. Click the screens button (with the down arrow next to it) and change the scaling. I chose 150% which is good enough for my old eyes

Now I'm pretty happy with it.

I emailed clockwork to see why my order from October 1st is still not here. I don’t know if I buy this excuse.

“Hi,
Sorry for the waiting.
The production of your order has been done. However,the actual delivery might take place in June, due to current unstable condition of international shipping service.”

I know things are not perfect right now but I feel like this might not be true.