[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
Settings Mobile Home
/k/ - Weapons


Thread archived.
You cannot reply anymore.


[Advertise on 4chan]


File: ABX00021_SPL.jpg (71 KB, 600x450)
71 KB
71 KB JPG
Entry-level microcontrollers are cheap, plentiful, and extremely versatile.

How do you weaponize them?
>>
I guess if you throw them really hard it can kill a person
>>
>>64342630
Cheap commercial-grade microcontrollers are already in pretty common use as guidance computers in ATGMs.
Shockingly, this violates the TOS for Arduino and Raspberry, not that the weapons manufacturers give any fucks about that.
>>
>microcontroller
A full computer with enough computing power for image recognition, signal processing, etc. can fit on a board like that these days. Might not even cost that much more.
>>
>>64342647
What is Raspberry going to do, march to China and file a lawsuit?
>>
>>64342630
how do you not? everything has them.
>>64342648
a full computer on a chip still typically has a couple of micros to do various things. and if your device has sensors, actuators, motors, etc all those things typically also have micros to drive them

any robot will generally have at least one proper computer running a proper OS capable of task scheduling to handle complex tasks like motion planning, but a number of microcontrollers to drive high frequency feedback loops such as controlling individual motors - be it a UGV, UAV or something else
>>
Control weapons, microscopically.
>>
File: 0009850_0.jpg (101 KB, 1200x1200)
101 KB
101 KB JPG
>>64342630
Attach a sword bayonet. I'm sure you can figure out the rest.
>>
File: ardupilot.jpg (258 KB, 1920x1080)
258 KB
258 KB JPG
>>64342630
>>64342747
>a full computer on a chip still typically has a couple of micros to do various things. and if your device has sensors, actuators, motors, etc all those things typically also have micros to drive them
Yup. I'm not sure what exact hardware this drone used, but I've seen a few pictures of custom drones being disassembled, and they're typically made of a simple single-board computer like a Raspberry Pi, with separate boards for flight/motor control, nav/comms, power supply, etc. wired into the SBC.
All of those could be on the same custom board, but I suppose this hobby style construction has its advantages if they want to iterate quickly and use parts that may not be available consistently.
>>
>>64342825
basic raspberries are not good enough for image recognition, but jetson boards are, and they are still pretty cheap
>>
>>64342630
What is with all of these low-effort fed-tier threads this week?
>what's the best 3D printer to print full auto lowers
>how do I weaponize arduinos
How about just try fucking reading about what they do instead of getting people to spoonfeed you ideas you can present to menopausal female politicians who will point to shit they don't understand and say "SEE, microcontrollers bad" the same way dumb cunts complain about heat shields and other random technology.

I know it's more likely that these are very low-effort slide threads, beacuse I hate to be schizo over every post, but for fucks sake, man. Put a little bit of effort, make the conversation interesting.
>>
>>64342630
I made a few flight sim cockpit contraptions with these. In my mind you could use them as a way to not blow yourself up with a homemade rocket/missle launcher of some sort using proximity sensors.
>>
>>64342648
niche example, but in 3d printing it actually became more expensive to use 8-bit controllers like the ATmega2560 or 128P for a time, because 32-bit were more available. It was a big part of why the old cheap CE3 knockoffs with 8-bit controllers and bare bones firmware died off all at once and klipper became more common; you had the processing power, may as well use it.
>>
>>64342904
You can run quantized MobileNet on high performance micros nowadays, like the STM32H7 line. They're like $10-20 a pop. Also, cheap chinesium FPGAs exist now.
>>
>>64342904
>image recognition
You can run some old-school algorithms even on a Raspberry Pi. More recent "AI" shit might not work, though.

>>64342961
I'm starting to think 8-bit controllers are slowly dying outside of the extremely low power niche (e.g. energy harvesting or chips that use less power than their battery's self discharge rate), or weird scenarios that require the most robust dumb chip possible. Silicon just isn't expensive enough.
They're already starting to sell 32-bit RISC-V microcontrollers with a standardized open instruction set and good compiler support with no effort from the manufacturer. Some past 8-bit microcontrollers like PIC were notorious for their fucked up snowflake tools that couldn't even digest dumb C code properly; that shouldn't be a problem with these.
>>
>>64342990
>More recent "AI" shit might not work, though.
You can run most CNNs on pretty much any CPU so long as you've got the patience and RAM. The problem is doing it at high frame rates. But nowadays you can get several FPS for decent models even on really constrained hardware, see >>64342985

Ultimately there's not that much of a difference between a "traditional" computer vision algorithm (e.g. oldschool face detection) and a CNN, they're both a sequence of convolution filters with some additional bells and whistles. The real difference is in how you obtain the parameters for the kernel functions.
>>
>>64342904
>basic raspberries are not good enough for image recognition
Negro, they could do basic terrain-scanning and target silhouette recognition with hardware small enough to fit into missiles in the 1970s.
Even the most basic bitch raspberry is thousands of times more powerful than any of those computers.
Your code is just extremely clunky, poorly written, and intensive to run compared to the extremely optimized machine-specific raw machine code and assembly languages old school missiles computers were programmed with.
>>
>>64343008
>basic terrain-scanning and target silhouette recognition
>in the 1970s
please stfu you don't understand what you're talking about

the methods used in the 70s (contrast seeking for EO guidance, 1-d linear convolution for TERCOM) are rudimentary and you need to repeat them thousands of times to perform even "classic" computer vision tasks such as face detection

a modern convolutional neural network essentially requires you to run contrast seeking for every pixel in the image, dozens or hundreds of times - in addition to various other computations - for every single frame
>>
>>64343008
1000%... Everyone complaining that raspberries are not powerful enough is writing Python code that uses a single thread. The Pi 4s have four cores and 4 MB of CPU cache. You get some old school programmers who write code directly onto the hardware; they can do some amazing things.
>>
>>64343064
not as much as you think. even MCUs are starting to come with integrated GPU/TPU because you need a lot more parallelism than that to get decent framerates. See for example:
>https://www.st.com/en/microcontrollers-microprocessors/stm32n6-series.html
these are micros in the $20 range and they come with IGPUs nowadays.

No amount of cache will overcome the fact that you need to perform an obscene number of additions and multiplications.
>>
>>64343082
Cool... so my point still stands, just they use different hardware
>>
>>64342990
>I'm starting to think 8-bit controllers are slowly dying outside of the extremely low power niche (e.g. energy harvesting or chips that use less power than their battery's self discharge rate), or weird scenarios that require the most robust dumb chip possible.
I don't think they're dying, but I think it was always the case that the chips were made to order. When the arduino happened it was "the prototyping board" and there was a period where everyone was ordering the chips to make them- then the pi happened, and there was a period of time where the two coexisted, but as time went on I think more people started using the pi as "the prototyping board." I think 8-bit controllers only persisted in widespread use because of inertia in design, and the fact that a lot of them were stockpiled.

Basically people realized that the STM32s could do everything you wanted and more, and once the surplus of AT128s and 2560s was eaten up the cost justification for keeping things dumb was no longer there.
>>
>>64343105
People keep using arduinos for everything simple low-level task, because that's all they know about. I just joined a project that has something like 8 separate arduino nanos running shit like LEDs and valves and the team came up with a brilliant idea of replacing them all with a single custom PCB board with the same Arduino circuit replicated 8 times and integrated USB hub. The next revision they are planning? A new board with single ARM running 8 emulated Arduino cores in parallel.
>>
>>64343059
>>basic terrain-scanning and target silhouette recognition
>>in the 1970s
>please stfu you don't understand what you're talking about
>>
>>64343153
This probably is all fault of Arduino's tools being just good enough that more or less anyone can pick them up and make the board blink an LED or control a servo, or something.
Before platforms like that, coding for microcontrollers consisted of weird custom toolchains that accepted "C" code that no C standard body had ever dreamed of, programming tools connected to the computer via serial port (requires 32-bit Windows XP or older) and command line incantations only documented in the giant door-stopper arcane tomes of PSDF8643758347F (documentation does not apply to ZXCV2343256734OMGWTFBBQ/4 or newer).

Some weird Chinese $0.005 chips are still a bit like that, with bizarre custom IDEs and sort of C-like languages that aren't quite C (possibly unintentionally), even offering convenient buttons that paste often-repeated voodoo code into the program.
>>
>>64343153
>A new board with single ARM running 8 emulated Arduino cores in parallel.
lol, lmao
see my point about inertia, though I am surprised that they wouldn't use a fucking Pi if they needed a fucking ARM. It has digital and analogue pins, and shields, last I checked.

What the fuck were they doing that needed 8 fucking arduinos, if I might ask? Do they know that shields exist?
>>
>>64342647
it's easy to get cheap fake aruino boards anyway, it's probably what they are using
>>
>>64345531
>cheap fake arduino boards
Anon the specs are fucking open source
anyone with the components and capability to solder them to a PCB can make one.
>>
>>64342904
>>64342985
>>64342990
There's a dedicated addon HAT AI board for RPi now for like $70 which is going to make everything even easier as it is specifically made for RPi.
>>
>>64345610
Sure, but I think the logo's still someone's property.
Not that these chink companies care. If you order an "Arduino compatible" board, there's a good chance it's got the Arduino logo crudely silkscreened on it somewhere, even if the product pics didn't show it. It's the same fake they sell as a "real" Arduino somewhere.

At least with these open boards you can check relatively easily if they actually followed the spec, or cheaped out on little details like ESD protection or power filtering.
>>
>>64343153
Is the project run by Artbyrobot, /diy/'s mostest elitest robotocist?
>>
File: 1738342580617125.jpg (25 KB, 396x396)
25 KB
25 KB JPG
>>64343213
>>Some weird Chinese $0.005 chips are still a bit like that, with bizarre custom IDEs and sort of C-like languages that aren't quite C (possibly unintentionally), even offering convenient buttons that paste often-repeated voodoo code into the program.
But enough about STM32CubeIDE
>>
File: images.jpg (12 KB, 168x300)
12 KB
12 KB JPG
>>64342630
>>
>>64346028
>or cheaped out on little details like ESD protection or power filtering.
Nanos don't have those in the first place
>>
>>64342630
Tape a gun to it.
>>
File: batcomputer.jpg (601 KB, 2615x1960)
601 KB
601 KB JPG
When i was a kid, in movies and comics there were always these cool computers that could do wonderous things (in my childhood personal computers weren't really a thing. There was like one kid in the neighbourhood that had a Commodore 64, so they were kinda exotic).

And I thought "Man, in the future computers are going to be everywhere and we can do all sorts of cool things with them! I am going to have like an automated house full of gizmos!".
But now, when we DO have miniature computers that can fit into your pocket and have access to all information in the world... I can't really think of what would I do with them. Even my old smartphones gather dust in the desk drawer and i can't think of anything smart to do with them.

like... what should I do with them? Have one as a weather forecast display? I can check that on my phone in a second, so why bother? I am not into stock market stuff, so I don't need market data either. Security camera? I live in a flat and I have an optical door peephole, I can use that.

Sadly, I cant think of any real smart use for them. Computers are for surfing the net or just working with word or excell. I have very little "exciting and cool" use for them.
This future is boring.
>>
File: Utility_belt.jpg (478 KB, 2048x1271)
478 KB
478 KB JPG
>>64347140
And why would I even want an automated house? Nowdays when the internet of things is reality, I don't even want it. I try to avoid adding unnecessary computers in my home appliances, stealing my personal data and analysing my consumer habits just so they could target me for more ads or sell that info for some megacorp.

So Why would I even want computers if I do not have a work-related need for them?
>>
It seems like it would be pretty easy to build DIY attack drones in most countries these days. How long until we get some unibomber-type guy that carries out attacks with them? How quick are governments going to crack down on the sale of microcontrollers?
>>
>>64345531
>>64346028
if you're building weapons in bulk you're not gonna be using prototyping boards anyway. ordering PCBs is dirt cheap nowadays. you use dev boards (probably not straight arduinos unless you've got those on hand) to hash out the basic concept, then you order PCBs with the specific crap you need by the thousands.
>>
>>64343198
what exactly are you trying to say here? do you understand how TERCOM works? though the early ones I think were analog
>>
>>64348104
>>64343198
now that I've tried to parse your retarded attempt at a reply I think I understood what you failed to understand

I wasn't saying they didn't have TERCOM or contrast seekers in the 1970s, I am saying that these things are orders of magnitudes removed from a CNN and I explicitly mentioned both TERCOM and electro-optical contrast seeking as examples of 1970s technology. Fucking illiterate monkey.
>>
>>64347140
>we can do all sorts of cool things with them! I am going to have like an automated house full of gizmos!".
>But now, when we DO have miniature computers that can fit into your pocket and have access to all information in the world... I can't really think of what would I do with them.
That's because you're fucking retarded. Every single electronic device in your life has digital computers that automatically do shit.
>>
>>64348104
>the early ones I think were analog
Yes and no.
The very earliest ones (fucking 1950s) were fully analog.
By the late 60s and early 70s the systems were a fucked up quasi-digital abominations which used crude digital computers to compare analog live data readings to a set of recorded analog maps, and issue corrective guidance commands accordingly.
There's very little data available to the public on the details, but supposedly some of these systems also had terminal guidance systems with visual-spectrum video cameras which could recognize the general shapes and silhouettes of expected targets and guide the missiles accordingly.
>>
>>64347001
>STM32CubeIDE
>Eclipse
>GNU C/C++ tools
That doesn't look so bad. If you want true 90s proprietary shitware jank, try an old version of PIC MPLAB, or the "tools" for some of those mystery Chinese chips that don't even say what architecture they're using and render the UI in a mix of a Chinese character font and FIXEDSYS.FON from Windows 2.

The Chinese seem to be moving toward cheap RISC-V microcontrollers now, so maybe that will be a thing of the past soon.
>>
>>64348204
>If you want true 90s proprietary shitware jank, try an old version of PIC MPLAB
God fuck bad memories of college
The majority of time spent working on labs was to unfuck the project file and get it reliably talking to the debugger instead of actually doing the lab

IIRC whatever the current version at the time was happened to be straight up broken for some things and the solution was install an older version
>>
>>64348204
>RISC-V microcontrollers
QRD on these? Saw one for piss cheap on Aliexpress
>>
teensy 4.0 with a MLX90640 IR sensor, and a Kalman Filter with a Bosch BMI088 to do INS tracking. strap it to an untethered robot that hops via kow-voltage electrohydraulic pogostick and piezoelectric wings. the whole system should operate using minimal power requirements and for an extended period of time. it could travel undetected and process visual data to confirm high-value targets in secure areas.
>>
File: 513MSY92hHS._SL500_.jpg (61 KB, 500x476)
61 KB
61 KB JPG
>>64348302
>kills your million dollar spy bug with a 15$ electric fly swatter off Amazon/Alibaba
Nothing personal
>>
>>64348387
>absorbs the electricity and fully recharges battery
thanks for the assist *hops away*
>>
>>64347140
>like... what should I do with them?
Most people have smart doorbells that they can access live video of their doorstep and communicate with anyone at their door as well as video recordings.
>>
>>64348276
RISC-V is a new-ish open standard instruction set architecture that's supposed to be able to scale from microcontrollers to supercomputers (an instruction set architecture basically specifies a machine language and how it should be executed by a compliant core implementation).

The simplest standard subset of RISC-V, RV32I (32-bit with basic integer math and logic) is simple enough that it can be implemented by a cheap microcontroller, kind of like those basic 32-bit ARM cores.
It seems to be slowly replacing some other 32-bit architectures in small embedded electronics, probably helped by the lack of intellectual property baggage and the many open core designs available on GitHub.

What's attractive about this for hobbyists (besides the cheap chips) is that with a standard instruction set, devs should be able to use common tools instead of some proprietary bullshit to compile code for RISC-V chips.



[Advertise on 4chan]

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.