This is an amazing content . i wish there was a quick way to calculate the pid values and tune them quickly since as an engineer you have dead lines to meet

Have you ever considered micromouse? I came across the UKMARS yt channel and am now hooked! I'll be building my own soon but thought it might be up your alley as well. I've watched your videos a lot, I like your problem solving style!

Do a Julia set with rust now and sweep thru the imaginary plane :) it is awesome project to learn.

if ((alive | population ) == 3){ // set next iteration to alive } this weirdly handles all cases

Fun fact: For keeping the state of active cells you can use a hash set of touples that represent coordinates. and then use a matcher to progress the game. It's incredibly fast.

This is awesome, I am teaching myself C++ and OpenGL and conway's game of life is my first project. I would love to learn Rust one day. Keep up the great content!

Was the rust code removed from the repository as a matter of interest? I only see a ruby version now. Many thanks

The optimization to only check live / neighboring dead cells is interesting, but depending on the state is short-lived, no? It's never removing entries, so a single glider going across the grid would end up leaving a ton of dead cells with no live neighbors in the HashMap. Is there also a reason you initialize to a default hashmap in main, then immediately reassign? It seems like `seed_grid` should just be the initializer, or take the `grid` as an `&mut` so you don't need to reassign the value

Do not pass go

Not too rusty … heh heh

YAYYYYYY A NEW VIDEO

Lots of fun writing this super simple simulation of Conway's Game of Life! Check out the full video for more!

I have been crazy busy recently and haven't had as much time as I'd like to work on my projects. I plan to jump back into my recent robotics project soon, but this was a welcome for me to just code up something fun and I hope you guys learn something from it! Edit: Thanks for all the comments folks, between your comments here and some comments on Reddit I have refactored some of the code which you can see in the GitHub link in the description. The main thing I changed was swapping from string keys in the hash to tuple keys for the coords, it's much cleaner this way! The string keys came from my previous experience building larger hash keys with more params while doing advent of code in Ruby. It can be handy to easily print for visually debug them. For this project, the tuple keys are much better. I also added my Ruby solution there too. Thanks for the comments folks!!

That's a great explanation; however, I think we should consider making the PID gains more adaptive to enhance the code's generality and accuracy. Would this improvement be beneficial or will it add unnecessary overhead to the code?

The robot turned out to be cool, don't you have a visual connection diagram?

So beautiful

Rumour has it, you couldn’t locate your black tape…

Lots of ambient light

Comment for the algo 🤖 This reminds me of a project we did back in college, except it was using Lego/Technic and a light sensor - had to build a robot that would go looking for lit candles and try to extinguish them 🔥 Looking forward to part 2!

Woop, lots of fun building this! Check out the full video for more!

Pretty impressed with how well this thing worked. Had no idea if it would, nice to surprise yourself sometimes!

Brother … ew

PID have three values. "P" ,"I" and "D". It's very confusing when you call all of them "gain". I've watched it three times and still got confused what is what:/

Why 32k and not the 32.768k(?) one? Internal crystal for most the STM32's I've seen are already tuned for the inferior 32k clocks. And Do you mean to say that on the low speed pins, your original board had the wrong clocks at 16MHz? Finally, with such low volume, just get an active circuit, single clock oscillator. Dealing with caps and impedance tuning on such low volume made in china boards is just annoying at best and a waste of time at worst. Also if you fuck up and put the wrong speed, you can easily just pop off that oscillator and put the right one on. Regardless, doing your own board and messing up like 20 times really is the best way to learn.

One thing I’ve had to come to accept is that if it works, don’t touch it

LSE apparently means "Low Speed External".... oscillator.

The hanky janky

Learning the hard way, nothing like it!! 😂

hey, cool video. saw your post on reddit, and was interested because ive been thinking of getting into embedded programming using rust. do you have an idea of where i could start to learn the basics?

I’m working laaaaaate…with my electronics 🎉

IT LIVES!!!

neat vid! stumbled on this, and while the video is great, I feel it could be amazing if there was a short and basic intro to what an STM32 even is, and what you plan to use it for Anyhow, great vid! Cheers!

howx the encoder measures the tilt angle

please help am doing project just like this...

JLCPCB: 48-Hour Turnaround for 6 Layer PCBs! jlcpcb.com/?from=IanCarey Sign Up to Get $60 New User Coupons

Had lots of fun with this one and learned loads doing it! Big shout out to JLCPCB for sponsoring this video!

one thing that confuses me is when the actual goes above the set point, won't the proportional and derivative terms become negative , so couldnt there be a case where the output is negative and you try and write a negative voltage to the pin?

one of the most through explanations ive seen, so refreshing to see behind the scenes instead of someone just using a library that makes everything into a black box

GREAT SUCCESS

Oh, remembered one more nice to do trick. Don't do GND, VIN, VOUT. Do VIN, GND, VOUT. That way if you short out two pins with solder bridge or by corrosion due to moisture, you get input or output short to GND thus putting your lab power supply in CC mode. If you do the first order, you short in to out and burn the load with +12 instead of +5. This is actual issue in LCD cable of some MacBooks. If smallest moisture gets in, it shorts logic voltage to 57V backlight voltage burning CPU.

One more thing - You want an input and output cap on each LDO and you want to have them as close as possible to your LDOs. The whole idea is to get as low trace and VIA inductance as you can. Lesser trace inductance is achieved by the proximity to pin, the VIA proximity is achieved by using 2 or more in parallel.

Few ideas form experience. 1. You want to add large copper array and about 1mm hole vias around it to cool down the LDOs better. 2. You might want to have LEDs on output rails not input. That way you immediately see if anything is pulling the rail down. 3. You might want to make that front supply SMPS so you can run it form higher voltage with higher power. I like AP63301 for that - super simple, cheap and stable little thing. I use them with WE LQS series inductors to keep on the cheap side while still being industrial quality.

Be gentle with that board. Those little AMS-1117 style LDO's can get quite hot. Also, while the "legitimate" ams-1117's datasheet tout a heafty 1A output, i feel it's misleading, as that should "peak" current. sustaining anything above 500mA and those little buggers get hot, and at 1A, they literally cook themselves. If you need higher current output, you'll want to go with a beefier packaged LDO.

Yes it worked! Still have to test it under load, but really it's never going to be running much, so I'm counting this as a success!!

PCB layout wise, I'd be tempted to put the three connectors in a row. I'm also surprised to see Vin and the two provided rails on the same connector? Wouldn't you put power in on one side and take the gnd/5v/3.3v on the other side? I'd consider switching the pin headers for JST headers given the risk of reversing the connectors and reverse-powering your targets. I don't understand why you picked a mosfet-and-transistor setup to conduct power? Is that to avoid arcing inside the switch? It looks like it debounces the input and it reduces current through the switch. I think your 100u capacitor doesn't match the footprints I tend to see for them; usually they're the electrolytic can versions and your footprint seems to match a ceramic capacitor. For circuit design I always use Kicad; similar to what you can do in Eagle/Fusion except free, and it has separated circuit design, component footprint selection and PCB layout subprograms. It has a couple tens thousand components by default, which covers nearly all things you'd want to typically use. It has the usual components under their short names - so if you search for R, C or L you get a resistor, capacitor or inductor, but if you prefer the American style symbols you can select R_american and it'll give you the squiggly line resistor and American style capacitor drawings. Those regulators really like it if you put a capacitor on their output. Something like a 10uF and a 100nF combined usually. Not for ripple filtering, but to catch variations in your load.

Led

Hello, can you tell me the size and mass of the ball you are using in this project, I 3D printed your model and ran it and as a result it did not run correctly with the value I set, I think it's because I used a different ball in this project. Thanks.

Zap zap ⚡️

doing 3rd year mechanical, and wanted to see actual application of such, this video is great.

Oh boy, this has a fun one! Super excited to see how this one turns out when I get it back from the manufacturer!!