Thing

The last image wasn't wired correctly plus points to whoever recognizes what im doing

It took me all day because I had the most ridiculous brain fog I couldn't even read charts or even numbers without making a mistake It felt like the mental equivalent of a drunk person trying to pass a sobriety test after getting pulled over

Like the shit went right through my head

And his name is JAN CENASKI DAH DAH DAH DAH 🗣🗣🔊🔊

Taking people back to 2015 with this one

I wanna go there so fucking much 😭😭🙏🙏
[Ukraine, Lviv city, Stryiska 202]

i was making umbrellas for them

Добра тьотка на проводніку дала
[Ukrainian Railway Sugar collectible]

It is almost done

I just need the

-endstops installed
-gt2 belt to arrive for y axis
-print and install the spacers for z axis stepper motor
-remake mounting mechanisms for PSU and controller
-redo the sketchy crammed kinked wiring I did in the psu

Yayy

So another thing. I have a lot of extra misc electronics i keep around, usually when something breaks/is no longer used and handed down to me if I don't have a use for it I will take it apart and see what I think is salvageable. Stuff includes old laptops, tool batteries, misc stuff like an electric self guided lawnmower that barely worked that was gifted to us by my grandpa, a very old GoPro, anything with a screen in it, 4g lte modems that were gonna be thrown out, and many more.

Now if I am going to get realll technical with some of the stuff in the future I need to learn how to reverse engineer protocols from standard ones like CAN, SPI, I2C, to proprietary ones. The proprietary ones im worried about. Like what about rhe GoPro camera chip or the mini 640p led screen from a 40 dollar NIR camera (or that camera sensor), some of the microcontrollers those companies use the data sheets aren't available for and it'd take a long time to figure out what's going on.

One of the first big issues with reverse engineering signals is the frequency in which the device operates. However I've learned that most devices besides CPUs and GPUs used in computers run in the 10-800mhz range, which for anything below like 400mhz is totally able to be captured and sniffed out. When/if I do do this im going to need to get very comfortable with the process. Sure it might take a while but it is 1)vital knowledge that can be applied to other places and 2) necessary to make future wants feasible. The future wants is some sort of machine learning system that can take my analyzed signal data and point me in the right direction/ identify the protocol. There's a limited number of ways to transfer data on devices that are mass manufactured to be cheap. Given that and a decent amount of training it might be possible to even reverse engineer signals of higher frequencies than what im sampling ( only reverse engineer the structure not capture the data, but still crucial if data sniffing is desired). Machine learning would only be part of the solution tho and I'd imagine it'd be a multi year process to even do that let alone learn everything related to that to do it while understanding what im actually doing. A major part of the program would just be plan logical analysis of inputs, by organizing and categorizing directly against known patterns. This would make taking random devices and using them a much more economical option than just raw dogging figuring everything out, every time. Even better if I document and make the software publicly available for free. Granted all this effort probably wouldn't be needed because there's probably something already out there though.