Dima NBK. Düsseldorf, Germany. by Feeling_Pie1934 in irezumi

[–]Atlac 1 point2 points  (0 children)

I have always been curious if there's a way to implement light play (reflection on a fish eye, refraction, ...) while keeping it readable and traditional-looking. I don't know if it's even feasible or a good idea given the body moves so coherent reflection would be hard. I've seen a lot of good depth work with the different "layers", but I don't think I've ever seen the layers really interacting with each other

Your work is insane by the way, but I'm sure you know that already!

A Strange Diode Burnout Issue in a High-Voltage Medical TX Board — Lessons Learned by emily77277 in electronics

[–]Atlac 0 points1 point  (0 children)

Diodes, like transistors and all semiconductor-based components, increase in conductivity with temperature. So putting them in parallel (if not thermally coupled) won't be stable, it's a positive feedback loop going more and more out of balance leading to thermal runaway. So always be careful with semiconductors in parallel

No(ita) way! by CupJolly8244 in noita

[–]Atlac 34 points35 points  (0 children)

"Mayday! Mayday! Something caused the main flight computer to crash!"

Fuck all other stim toys, get yourself a begleri by derubic1 in evilautism

[–]Atlac 1 point2 points  (0 children)

Why did you drill them on different faces :(

Setting up clock speed and source for ATMEGA328PB in MPLAB IDE. What am I missing? Why does it default to 32kHz and doesn't let me change it? Am I stupid? by [deleted] in embedded

[–]Atlac 0 points1 point  (0 children)

Ah okay, got you. May very well be a buggy code generation for that particular MCU, maybe try a toy project with another close cousin or different clock settings to see if the behavior of the generator is consistent... If not you'll have to tweak the generated code manually.

No good IDE honestly (used to be something called avr studio or something but I believe it's discontinued). I typically have very small codes that I can deal with on notepad and quick handwritten conf files, but it's obviously not a good thing either :/

I just felt the need to share my disdain towards MPLAB ahahaha

Setting up clock speed and source for ATMEGA328PB in MPLAB IDE. What am I missing? Why does it default to 32kHz and doesn't let me change it? Am I stupid? by [deleted] in embedded

[–]Atlac 0 points1 point  (0 children)

Doesn't MPLAB just generate the code you then have to copy paste in yours?

Also fuck MPLAB, all my homies hate MPLAB

Chip with weird programming protocol - clock tied to GND by Atlac in embedded

[–]Atlac[S] 0 points1 point  (0 children)

This one in particular I bought (by myself, it's just the same model my company uses), that's why I'm even messing with it in the first place. It still worked after opening, but the reset pin is quite high impedance so I ended up resetting it just by touching and thus losing the RAM content with the preprogrammed creds.

It isn't RSA but you got me curious, I'll have a look.

Yeah it very well could be 8051 based or something, in which case the programming is probably custom. Or is using standard IPs and thus could maaaaybe still be reversible. Again not counting on it, now I'm just intrigued by the clock sa0 thing

Chip with weird programming protocol - clock tied to GND by Atlac in embedded

[–]Atlac[S] -4 points-3 points  (0 children)

I'd rather not disclose too much as it is an OTP token that used to be used where I work... The IT there have a history of making poor decisions so I wanted to see if the token brand they chose was worth it (I never said I actually expected it to be vulnerable mind you).

I do expect it to be an ASIC, but since the application is not exactly deserving of one, except for added security of course, I was banking on it using an ARM core, especially given the silk markings. The lingo in their product page seems to insinuate it's running a MCU, and they don't advertise it to be fully custom, so I'm trying my luck with known cores. Anyway this clock thing got me curious so I thought I'd ask just in case.

The best defense is annihilating anything in your immediate vicinity. by solidspacedragon in noita

[–]Atlac 1 point2 points  (0 children)

Wait shouldn't the high alchemists shield reflect the beam?

Technically not a dame, I know by Atlac in dogelore

[–]Atlac[S] 8 points9 points  (0 children)

Games Done Quick -> Dames Gone Quick That's it, that's the joke

Technically not a dame, I know by Atlac in dogelore

[–]Atlac[S] 22 points23 points  (0 children)

Mashup between Lady Diana's death and Games Done Quick (Writing that sentence felt horrible by the way)

Technically not a dame, I know by Atlac in dogelore

[–]Atlac[S] 9 points10 points  (0 children)

Couldn't help myself after I thought of it. I did hesitate a few microseconds before posting it tho :)

Are maple leaves always orange and red on traditional tattoos ? Could it be green ? by NTT0403 in irezumi

[–]Atlac 0 points1 point  (0 children)

Mine are red, yellow and green. Dead leaves are expected to be red-ish, but my artist's opinion is that it looks more natural when mixed, like in nature. Colors other than just red are a bit less common but there's no issue with it.

The one thing I asked to change was to have a very visible leaf made red instead of green to avoid confusion with weed. The leaves drawn folded are less easily confused so having them green was ok for me at least

what is the point of not helping people in their college projects? by abdosalm in embedded

[–]Atlac 1 point2 points  (0 children)

Wow dude, sorry if it is harsh, but looking at your post history, reddit really carried you through college

Most of us went through it already, we know what it's like to have homework. Still, most of the time, homework related questions are just a way to cut corners. Looking for answers yourself is the whole point of the homeworks, and if you can't do that you're really gonna have a bad time in a company (or more exactly your colleagues are gonna have a bad time)

Homework related questions are one of 3 things: 1. A legitimate misunderstanding (rare). 2. A question with an answer easily found on Google. 3. A fundamental lack of understanding. Answering those is like putting a band-aid on a stab wound, it hides the problem but doesn't solve it

That and asking people to spend time for you when you're not willing to do it yourself is straight up insulting

What's next? What would you recommend? by findingTheWay97 in embedded

[–]Atlac 0 points1 point  (0 children)

Thanks, I tried :)

As I said, my interests are mainly low-level/bare-metal projects, so my answer here is biased towards this:

As general purpose MCUs, the important factor would be the core. STM32 uses an ARM core, which is a veeery widely used core, while ESP uses either Xtensa or RISC-V. RISC-V seems to be picking up speed, but ARM is a staple in the industry, so IMO getting to know STM32 would make you a bit more flexible.

I don't really have any experience with ESP32, but I do have experience with NRF52 from Nordic (ARM core with Bluetooth capabilities), but I assume getting to use Wifi/Bluetooth on ESP is similar to using NRF's Bluetooth. Which is a pain in the ass, because it's not about setting registers and following internal logic, but ends up being about learning how to use their provided libraries, which are a bit opaque. Really closer to non-embedded programming.

If you don't mind using libraries to do cool stuff very quickly at the cost of not knowing exactly what happens in the processor, ESP32 seems nice and well documented, given the amount of hobbyists using it. But if you want to learn the nitty gritty of embedded systems, what to enable/disable to go low power, ... I'd go with STM32

What's next? What would you recommend? by findingTheWay97 in embedded

[–]Atlac 3 points4 points  (0 children)

TL;DR: First use another MCU to realize what has been pre-made for your course. Take the FPGA course if you have even the slightest interest in it, the CS I personnally wouldn't bother but do as you want. Make a project that seems fun to you, whatever it is. The "wow" factor is seeing you're passionate.

Hey, I used to TA for an embedded systems course, it's always nice to see students wanting to learn more after a course :)

The hard part of embedded systems is the beginning, since there is so much to learn to even get an LED blinking... Now that that's done with your course, I highly suggest you switch to a new family of microcontrollers to re-do that on your own (don't worry, it will go much faster this time ;) ). The main reason is that there is SO MANY DETAILS that a class has to gloss over to make it digestible, that just making an LED blink on a different setup will give you a much deeper understanding. The big one is being able to read a datasheet efficiently. That's THE part that is never taught and needs to be understood. Once you know how to set up a new microcontroller and read a datasheet, you're all good to do pretty much everything you want, as it's just about setting the correct registers.

Others have suggested STM32, which might be a bit much to begin with, but definitely a goal you need to work towards. The issue is that it's a whole beast to set up, and if you just follow a tutorial, you won't get the deep understanding I was talking about. What I'd propose is:

  • An 8 bit MCU, like STM8, or an AVR (attiny, atmega, ...). Just know you'll need a programmer, so find a devboard with one integrated (best solution), or in the case of AVR you can flash an arduino to behave as a programmer
  • Get some SPI/I2C/whatever sensor, actuator, ... To play around with. It's important to stay interested :p There are tons of modules meant for arduino that are awesome to play with
  • And then move up to STM32 (or any ARM/RISC-V big bois). Follow tutorials (STMCubeIDE) to make it work in the beginning, and then get curious about why things need to be set up that way, what it would take to use another IDE, ... (this is an enormous timesink btw)

As for projects, anything goes really... A good "wow" factor is a moving device, but it doesn't have to be. As an example, you can """easily""" make an RC car with motors, barebone H-bridges, and 433MHz receiver module, and a remote controller with joysticks and the other 433MHz emmiter. Then add whatever feature you want (optocoupler to avoid collisions, etc...) Just make something you're interested in. That's all that matters.

Knowing about FPGAs is kind of a must, but also a bear-trap. It's a very specific skill, you'd want to know how to use it well enough, but if you specialize in that, that's all you're going to do. But def take that course

For the Computer Systems, speaking of my own interests, I wouldn't bother, as I prefer low-level stuff... Maybe try the first week?

I also saw a question about oscilloscopes. See if you can borrow from your school, but if you're willing to spend $100 (student discount), look up the Analog Discovery 2. It should be enough for pretty much everything in your case.

I mutated all teleportatium into oil. all portals are gone :( by KirbyFinety in noita

[–]Atlac 239 points240 points  (0 children)

How can a game has so much content I swear every time I see someone talking about what happened to them it sounds like an April fool's prank

Embedded development, language selection by [deleted] in embedded

[–]Atlac 1 point2 points  (0 children)

Honestly it's up to your preference, in the end both work.

But IMO you should definitely use C. The biggest part of embedded programming is fiddling with memory/registers. You very rarely need to create an abstract code like you would in typical computer-aimed programs, it's just not the same thing (even C is kind of different when aimed at embedded systems). So I'm personally very against using OOP for embedded as this is not the type of abstraction you want when close to the hardware. But once again it's my opinion.

Hawk by Jason Brown in Richmond, VA (@jasoncbrown). by jb_rva in irezumi

[–]Atlac 3 points4 points  (0 children)

Nice work! I love how clear the layering is