Language Selection

English French German Italian Portuguese Spanish

Open Hardware: Spaghetti Detective (TSD), OnStep and RISC-V in Barcelona Supercomputing Center (BSC)

Filed under
  • Spaghetti Detective: Open Source AI Software Detects Prints Gone Wrong

    Desktop 3D printer users are quite familiar with the mishaps of some print job going wrong and extruders spilling material all over their machine while they’re out at the store or soundly sleeping in bed. Being confronted with a printer full of plastic spaghetti when you next go to check on it is one of the most disheartening and frustrating experiences a user can face.

    Attempting to address this issue is the Spaghetti Detective (TSD), a piece of open source artificial intelligence software that automatically interrupts failed prints. The software runs continuously on a computer server and uses a computer or printer’s webcam to monitor the printing process. If it detects a print failure, it automatically pauses the print and alerts the user via text or email. You can then choose to cancel the print and prevent not only a plate of inedible spaghetti from forming, but also the possibility of equipment damage or fire hazard. The Spaghetti Detective can run on an old PC connected to the web or, if you prefer not to rely on the cloud, it’s possible to host the TSD server on a Jetson Nano card from NVIDIA.

  • Open Source Telescope Controller Puts Smart Features In Old Telescopes

    In times like these, we all need to look beyond ourselves. This project might help: OnStep is an open-source telescope controller, a device that controls a telescope to point at something interesting in the sky. Want to take a look at M31? Use an app on a PC or smartphone, select the object and the OnStep will pan and tilt your telescope until the Andromeda Galaxy pops into view.


    It is pretty hardware agnostic: the controller can be an Arduino, a Teensy 3 or even an ESP32. The PCB design can work with any of these controllers. The same is true of the motors that move the telescope, so you can build the device from parts that you might have lying around. Many of those who have built OnStep controllers have adapted older telescope mounts that are motorized but aren’t smart. Others have used older mounts and replaced the slow, inaccurate motors with more precise ones that make the telescope more accurate and smooth. The gallery of telescope builds on the OnStep wiki is a great place to start and see examples like this 30-year old Celestron telescope that was brought into the 21st century with a OnStep conversion, or this conversion of a 1960s telescope that adds a smart mount.

  • BSC-Led DRAC Project to Manufacture New Chip, Open Source Accelerators in Barcelona

    If Lagarto, the first open source processor developed in Spain and Mexico, was introduced in December, now DRAC is presented. It is a project to develop a new processor and several open source accelerators. DRAC (Designing RISC-V-based Accelerators for next generation Computers) is a new step in research led by the Barcelona Supercomputing Center (BSC) to manufacture open source chips from Europe. The project has the collaboration of the Polytechnic University of Catalonia (UPC), the University of Barcelona (UB), the Autonomous University of Barcelona (UAB) and the Rovira i Virgili University (URV).

    The objective of DRAC is to manufacture a processor and several accelerators to be used in security tasks (encryption or protection from attacks against hardware, for example), personalized medicine (especially genomic analysis) and autonomous navigation (cars and other vehicles).

More in Tux Machines

today's howtos

Open Usage Commons

  • Introducing the Open Usage Commons

    Open source maintainers don’t often spend time thinking about their project’s trademarks, and with good reason: between code contribution, documentation, crafting the technical direction, and creating a healthy contributor community, there’s plenty to do without spending time considering how your project’s name or logo will be used. But trademarks – whether a name, logo, or badge – are an extension of a project’s decision to be open source. Just as your project’s open source license demonstrates that your codebase is for free and fair use, an open source project trademark policy in keeping with the Open Source Definition gives everyone – upstream contributors and downstream consumers – comfort that they are using your project’s marks in a fair and accurate way.

  • Open Usage Commons Is Google-Backed Organization For Helping With Open-Source Project Trademarks

    Open Usage Commons is a new organization announced today that is backed by Google for helping open-source projects in managing their trademarks. Open Usage Commons was started by Google in conjunction with academia, independent contributors, and others for helping to assert and manage project identities through trademark management and conformance testing.

  • The "Open Usage Commons" launches

    Google has announced the creation of the Open Usage Commons, which is intended to help open-source projects manage their trademarks.

  • Announcing a new kind of open source organization

    Google has deep roots in open source. We're proud of our 20 years of contributions and community collaboration. The scale and tenure of Google’s open source participation has taught us what works well, what doesn’t, and where the corner cases are that challenge projects.

Android Leftovers

GNOME, Linux, Qt and Git Programming

  • Philip Withnall: URI parsing and building in GLib

    Marc-André Lureau has landed GUri support in GLib, and it’ll be available in GLib 2.65.1 (due out in the next few days). GUri is a new API for parsing and building URIs, roughly equivalent to SoupURI already provided by libsoup — but since URIs are so pervasive, and used even if you’re not actually doing HTTP conversations, it makes sense to have a structured representation for them in GLib.

  • Sandboxing in Linux with zero lines of code

    Modern Linux operating systems provide many tools to run code more securely. There are namespaces (the basic building blocks for containers), Linux Security Modules, Integrity Measurement Architecture etc. In this post we will review Linux seccomp and learn how to sandbox any (even a proprietary) application without writing a single line of code.

  • Mario Sanchez Prada: ​Chromium now migrated to the new C++ Mojo types

    At the end of the last year I wrote a long blog post summarizing the main work I was involved with as part of Igalia’s Chromium team. In it I mentioned that a big chunk of my time was spent working on the migration to the new C++ Mojo types across the entire codebase of Chromium, in the context of the Onion Soup 2.0 project. For those of you who don’t know what Mojo is about, there is extensive information about it in Chromium’s documentation, but for the sake of this post, let’s simplify things and say that Mojo is a modern replacement to Chromium’s legacy IPC APIs which enables a better, simpler and more direct way of communication among all of Chromium’s different processes.

  • 6 best practices for teams using Git

    Everyone should follow standard conventions for branch naming, tagging, and coding. Every organization has standards or best practices, and many recommendations are freely available on the internet. What's important is to pick a suitable convention early on and follow it as a team. Also, different team members will have different levels of expertise with Git. You should create and maintain a basic set of instructions for performing common Git operations that follow the project's conventions.

  • Qt for MCUs 1.3 released

    Qt for MCUs 1.3 is now available in the Qt installer. Download it to get the latest improvements and create stunning GUIs with the newly available timeline animation system. Since the initial release of Qt for MCUs 1.0 back in December last year, we've been hard at work to bring new features to MCUs with the 1.1 and 1.2 releases. Efforts haven't slowed down and it's already time to bring you another batch of improvements. Besides the new features, One of the goals has been to make Qt Quick Ultralite a true subset of Qt Quick and align their QML APIs to ensure both code and skills can be reused from traditional Qt platforms to microcontrollers. With Qt for MCUs 1.3, QML code written for Qt Quick Ultralite is now source-compatible with Qt 5.15 LTS.