New Open Source DeepSeek V3 Language Model Making Waves

In the world of large language models (LLMs) there tend to be relatively few upsets ever since OpenAI barged onto the scene with its transformer-based GPT models a few years ago, yet now it seems that Chinese company DeepSeek has upended the status quo. Its new DeepSeek-V3 model is not only open source, it also claims to have been trained for only a fraction of the effort required by competing models, while performing significantly better.

The full training of DeepSeek-V3’s 671B parameters is claimed to have only taken 2.788 M hours on NVidia H800 (Hopper-based) GPUs, which is almost a factor of ten less than others. Naturally this has the LLM industry somewhat up in a mild panic, but for those who are not investors in LLM companies or NVidia can partake in this new OSS model that has been released under the MIT license, along with the DeepSeek-R1 reasoning model.

Both of these models can be run locally, using both AMD and NVidia GPUs, as well as using the online APIs. If these models do indeed perform as efficiently as claimed, they stand to massively reduce the hardware and power required to not only train but also query LLMs.

The FTC Take Action, Is Time Finally Up For John Deere On Right To Repair?

Over the last decade we have brought you frequent reports not from the coolest of hackerspaces or the most bleeding edge of engineering in California or China, but from the rolling prairies of the American Midwest. Those endless fields of cropland waving in the breeze have been the theatre for an unlikely battle over right to repair, the result of which should affect us all. The case of FEDERAL TRADE COMMISSION, STATE OF ILLINOIS, and STATE OF MINNESOTA, v. DEERE & COMPANY  relates to the machinery manufacturer’s use of DRM to restrict the repair of its products, and holds the promise to end the practice once and for all.

This is being written in Europe, where were an average person asked to name a brand that says “America”, they might reach for the familiar; perhaps Disney, McDonalds, or Coca-Cola. These are the flag-bearers of American culture for outsiders, but it’s fair to say that none of them can claim to have built the country. The green and yellow Deere tractors on the other hand represent the current face of a company with nearly two hundred years of farming history, which by virtue of producing some of the first mass-produced plows, had perhaps the greatest individual role in shaping modern American agriculture and thus indirectly the country itself. To say that Deere is woven into the culture of rural America is something of an understatement, agricultural brands like Deere have an enviable customer base, the most loyal of any industry.

Thus while those green and yellow tractors are far from the only case of DRM protected repairability, they have become the symbolic poster child for the issue as a whole. It’s important to understand then how far-reaching it is beyond the concerns of us technology and open-source enthusiasts, and into something much more fundamental. Continue reading “The FTC Take Action, Is Time Finally Up For John Deere On Right To Repair?”

Contrails Are A Hot Topic, But What Is To Be Done?

Most of us first spot them as children—the white lines in the blue sky that are the telltale sign of a flight overhead. Contrails are an instant visual reminder of air travel, and a source of much controversy in recent decades. Put aside the overblown conspiracies, though, and there are some genuine scientific concerns to explore.

See, those white streaks planes leave in the sky aren’t just eye-catching. It seems they may also be having a notable impact on our climate. Recent research shows their warming effect is comparable to the impact of aviation’s CO2 emissions. The question is then simple—how do we stop these icy lines from heating our precious Earth?

Continue reading “Contrails Are A Hot Topic, But What Is To Be Done?”

Building The Feynman Motor That Fits Through A Sewing Needle’s Eye

The first attempt at replicating William McLellan's miniature motor. (Credit: Chronova Engineering, YouTube)
The first attempt at replicating William McLellan’s miniature motor. (Credit: Chronova Engineering, YouTube)

How small can an electric motor be without resorting to manufacturing methods like lithography? In a recent video, [Chronova Engineering] on YouTube tries to replicate the 1960 McLellan motor that fulfilled [Richard Feynman]’s challenge requirements. This challenge was part of [Feynman]’s 1959 lecture titled There’s Plenty of Room at the Bottom, on the possibilities of miniaturization. A $1,000 reward was offered for anyone who could build an electric motor that was no larger than 1/64th inch cubed (~0.0625 mm3), with the expectation that new manufacturing methods would be required to manufacture a motor this small.

As reported in the December 1960 issue of The Month at Caltech, [William McLellan] walked into [Feynman]’s lab with this tiny marvel that took him 2.5 months of lunch hour breaks to build. Weighing in at 250 micrograms and consisting out of 13 parts, it was constructed using a microscope, a watchmaker’s lathe and a toothpick. Surely replicating this feat would be easy today, right?

The main challenge is that everything is incredibly small. The rotor shaft is 90 micrometers in diameter, and the four coils require winding incredibly thin wire at scales where typical manufacturing methods do not apply. Suffice it to say that it takes massive amounts of patience, creativity and the best (stereo) microscope you can get, yet even with modern optics and materials this first attempt mostly failed.

At the end we’re left with SEM shots of this replication attempt and an immense amount of respect for the skills of [William McLellan] who made a working version in 1960 using much more basic tools during his lunch breaks.

Thanks to [J. Peterson] for the tip.

Continue reading “Building The Feynman Motor That Fits Through A Sewing Needle’s Eye”

3D Print Stamps, And Ink Stuff To Your Heart’s Content With These Tips

Ink stamps can be fun to make and use, and 3D printers are uniquely positioned to create quality stamps of all kinds with just a little care. As with most things, the devil is in the details and the best results will require some extra work. Luckily, [Prusa] has a blog post that goes through how to 3D print the best stamps and includes concrete recommendations and tips to get the most out of the process.

Resin printers can create stamps too, just ensure a flexible material is used.

What makes a good 3D-printed stamp? It should be easy to use, transfer an image cleanly, and retain ink reasonably well. To hit these bases, printing the stamp face out of a flexible material is probably the most important, but a flat and smooth stamp surface is equally crucial. Satin-finish build plates will give a weathered look to the stamp, but textured build plates in general are no good.

As for the design, turning an image into a 3D object can be a bit challenging for novices, but there are tools that make that much easier now than it used to be. Some slicers allow importing .svg files (scalable vector graphics) with which to emboss or deboss objects, and online tools as well as free software like Inkscape will let folks covert images into .svg format.

Flexible filaments tend to be stringy so they should be dried before use, especially if the stamp design has a lot of separate elements that invite stringing. Any flex filament should do the job, but of course some specific filament brands perform better than others. Check out the full blog post for specific recommendations.

Pausing a print and inserting a pre-printed support piece (removed after the print completes) helps form big overhangs.

The remaining tricky element is that flexible filaments also tend to be poor at bridging, and if one is printing a stamp face-down on the build plate (to get that important, ultra-flat face) then the upper inside of the stamp may need some support for it to come out right. As [Prusa] suggests, this is a good place to use a manual, drop-in pre-printed support piece. Or if one has the ability to print in multiple materials, perhaps print the support structure in PLA since it is just about the only material that won’t completely weld itself to flex filaments. Of course, if one is designing the stamp entirely in CAD, then the best option would be to chamfer the stamp elements so supports aren’t necessary in the first place. Finally, don’t overlook the value of a physical design that makes handling easy and attractive.

Since 3D printing makes iteration so fast and easy, maybe it would be worth using this to revisit using rubber stamps to help create PCBs?

Making A Mini AM Transmitter Better

The chances are that many of you will have made an FM “bug” style transmitter, a simple one-transistor oscillator usually driven by a small electret microphone. It’s also relatively straightforward to do the same for AM, and if you take a look through AliExpress you’ll find some modules which do just that. [Doz Television Workshop] has one, and he’s treated us to a thorough run-down of its design before addressing some of its shortcomings.

An AM transmitter is simple enough, in this case an oscillator and buffer driving a class C power amplifier. The modulation is applied by a transistor in series with the power amp, driven from an audio amplifier. Some attention has gone into the design of this one, with a proper output filter and plenty of room for tweaking to achieve proper levels and modulation density. There are some problems though — The modulator transistor is mounted upside down for the heatsink, and the frequency stability leaves something to be desired. [Doz] fixes the heatsink mounting and incorporates a DDS frequency synthesizer with an Arduino for control.

More after the break…

Continue reading “Making A Mini AM Transmitter Better”

Hackaday Links Column Banner

Hackaday Links: January 26, 2025

Disappointing news this week for those longing for same-hour Amazon delivery as the retail giant tapped the brakes on its Prime Air drone deliveries. The pause is partially blamed on a December incident at the company’s Pendleton, Oregon test facility, where two MK30 delivery drones collided in midair during light rain conditions. A Bloomberg report states that the crash, which resulted in one of the drones catching fire on the ground, was due to a software error related to the weather. As a result, they decided to ground their entire fleet, which provides 60-minute delivery to test markets in Arizona and Texas, until a software update can be issued.

Continue reading “Hackaday Links: January 26, 2025”