My Advanced Realistic Humanoid Robots Project

[artbyrobot]

also in the last thread that got locked, I already made my case about interrupts being total trash and something to avoid at all costs and it was affirmed by another forum member with more knowledge than the others who were skeptical about my claims and suddenly the room got all quiet about it and I was vindicated and everyone was silenced.  Go relearn your lesson with the search feature noobs.

[Leiothrix]

"Total trash" just seems to be code for "don't understand it".

[xrunner]

also in the last thread that got locked, I already made my case about interrupts being total trash and something to avoid at all costs and it was affirmed by another forum member with more knowledge than the others who were skeptical about my claims and suddenly the room got all quiet about it and I was vindicated and everyone was silenced.  Go relearn your lesson with the search feature noobs.

ChatGPT: "Yes, computer interrupts are incredibly important! They play a critical role in the efficient functioning of a computer system.

[Andy Chee]

I already made my case about interrupts being total trash and something to avoid at all costs

In that case, stop using your internet browser, keyboard, mouse and PC right now.  None of it could function without interrupts.

[vk6zgo]

Read about SAR ADC theory yourself. Then read about clock limitations of ADC in AVR. Modern ARM MCU ADC peripherals are way faster, but analog sampling is still quite a slow process (compared to digital IO).

terrible advice nobody do this unless you want to waste time.  You just pick a popular microcontroller, follow some getting started tutorials, code it and project works or not.  that simple.  Don't read all that garbage time wasting stuff.  Let it be a black box.  Not everything has to be unblack boxed that is how you end up in development hell of never any progress

You have made little progress in the last 10 years, anyway!

[artbyrobot]

I already made my case about interrupts being total trash and something to avoid at all costs

In that case, stop using your internet browser, keyboard, mouse and PC right now.  None of it could function without interrupts.

that's a huge lie.  i could EASILY make a mouse that polls for clicks rather than clicks triggering an interrupt.  It is trivial and superior coding practice

[artbyrobot]

You have made little progress in the last 10 years, anyway!

Correction: you have made MONUMENTAL EPIC and MASSIVE progress in the last 10 years.

Why?

I spent 3 or so months carefully hand making a fiberglass rendition of the frame before I had access to a 3d printer or other potential options. I was going from scratch with clay bone sculpting. I then had a viable arm and chest to begin electronics work on. Then I began iterating through possible actuators to use and ruling them out one by one over the course of 8 years while also studying during those 8 years electrical engineering, mechanical engineering, AI, and every other related field and getting significant progress in those areas and doing some preliminary work on those fronts here and there with either related projects or some prototyping for this project series. I also spent alot of time on unrelated projects, establishing a financial foundation, some other business ventures, a family, and various other stability in my life. You pretending I just literally locked myself in a room for 10 years building the frame and only coming out to eat once in a while is a joke and completely untrue. I probably spent 95% of my time those 10 years not even working on the robot.

Would you say the same thing if someone cleaned half of a messy bedroom for 5 minutes then went to the military for 10 years, came back home and cleaned the other half of the bedroom for 5 minutes? He spent 10 minutes cleaning the bedroom in total actual time spent but you could say it took him 10 years to finish cleaning the bedroom. The latter phrasing is misleading even if in some sense it can be said. That is what you are doing to me right now.

So when someone is doing something highly experimental and highly unconventional, without any guidance to just follow along a proven path, when they are trail blazing, things can take way longer to get done. It is like one step forward two steps back. I found myself making actuator after actuator, mounting it, testing it, and removing it from the robot realizing somewhere along the way that it is not viable for my use case. This repetitive process of elimination, ruling out failed ideas and trial and error can go on and on until you find the correct choice or a valid choice and are able to step forward from there. It almost feels like Odysseus' wife weaving and unweaving that piece of textile over and over day by day where it wasn't ever getting finished. Yet these little experiments are critical to enable one to find the best path or at least a viable path. Ideas can prove wrong over and over. Consider Edison with the lightbulb, how many times he tried and failed before landing on a viable lightbulb construction. It was 99% perspiration and 1% inspiration the saying goes. This is sometimes the nature of inventing. It is not alway so easy. You can't always one shot things. But if you press through these blocks you can find something the field desperately needed. So you press on, confident you will find a way. Seeing the progress in such cases might seem like hmmm... seems like he did nothing. But all the trial and errors are not nothing. I found many ways it cannot be done. That is something. That knowledge was not obtainable any other way. And if I'm correct, I am now landing on a way things can be done that is game changing. I think I am arriving now. That was not insignificant. And the time taken to reach that cannot be diminished or ignored like this. It is not just.

[Leiothrix]

Of course you could, it would just be dumb.  That is why no one has done it in the last 40 years or so that we have had hardware interrupts.

A busy wait for every peripheral would make your main event loop more bloated, less reliable, slower and very power hungry.

Asynchronous programming can be difficult to get your head around, but you haven't even tried.

To be totally fair you haven't tried synchronous programming either.

Try actually using a microcontroller before you state that any aspect of it is dumb.

Correction: you have made MONUMENTAL EPIC and MASSIVE progress in the last 10 years.

What you have is a non-functional art project of cobbled together literal garbage that a 10-year-old would be ashamed to show to the world. 

Have a look around YouTube for the things that people have accomplished with a 3D printer and some hand tools and then look at your mess, no clue how you could even compare them.

[artbyrobot]

Also, don't misdefine my usage of the word trash.  My definition for calling something trash is:  not prudent, unskilled, poor in taste or quality, mistaken, poor execution, ugly, laughable, shaking my head at it, disapproval of it.  So basically my definition describes myself and my projects in the eyes of my haters.  I am trash and my project is trash by this definition according to the haters.  But as mentioned before, the haters will be very ashamed and humbled when I prove them wrong epicly so.  So much so that I imagine their knees will wobble when they walk for weeks just feeling so feeble in body and mind after being struck so firmly by how in error they were in their smug dismissal of myself and my project.  It will be a great time for me when that begins taking place.

[themadhippy]

Consider Edison with the lightbulb, how many times he tried and failed before landing on a viable lightbulb construction

About 5 minutes,the time taken to read and "borrow" swans work and pass it off as his own

[artbyrobot]

Try actually using a microcontroller before you...

try watching the many youtube videos I already posted where I demonstrated mastery in use of microcontrollers with extensive development with them before assuming I haven't used them in total ignorance.

[Leiothrix]

Also, don't misdefine my usage of the word trash.  My definition for calling something trash is:  not prudent, unskilled, poor in taste or quality, mistaken, poor execution, ugly, laughable, shaking my head at it, disapproval of it. 

Don't worry, we are all using the same definition here.

humbled when I prove them wrong epicly so

Go on then, hook a motor up to a finger, a microcontroller up to the motor and make it twitch.  I double dare you.

try watching the many youtube videos I already posted where I demonstrated mastery in use of microcontrollers with extensive development with them before assuming I haven't used them in total ignorance.

Well you don't know how to use interrupts, don't even know what DMA is, think Arduino is useful for something complex and high-speed, don't consider datasheets to be worth reading, think ADC should happen before you even ask for it, and think that a microcontroller can reliably and precisely directly control ten BLDCs and provide sensory feedback at the same time.

I can only go by your words and your output.  You haven't demonstrated even a basic understanding frankly.

[artbyrobot]

don't consider datasheets to be worth reading

I never said that.  I recommend skimming for any critical info which should be like 5-6 things tops when you are buying a mosfet or w/e.  Nothing more than that though don't spend much time on that nonsense.

[Leiothrix]

I never said that.

Read about SAR ADC theory yourself. Then read about clock limitations of ADC in AVR. Modern ARM MCU ADC peripherals are way faster, but analog sampling is still quite a slow process (compared to digital IO).

terrible advice nobody do this unless you want to waste time.  You just pick a popular microcontroller, follow some getting started tutorials, code it and project works or not.  that simple.  Don't read all that garbage time wasting stuff.  Let it be a black box.  Not everything has to be unblack boxed that is how you end up in development hell of never any progress

Yeah you did.

Microcontrollers can have several thousand pages of datasheets.  They didn't write all of that stuff just for fun.

[artbyrobot]

nothing about that post said read a datasheet.  it spoke about reading on theory and other various stuff that has naught to do with skimming a datasheet before buying a component

[Leiothrix]

You mean the theory that tells you how a part works that you can use to determine if a device is suitable for your purpose?

Like the length of an ADC conversion cycle for instance.  Or the number of converters vs the number of channels, the time to switch channels, the time for a first conversion vs subsequent conversion. 

And generally you want them will fire an interrupt when complete, otherwise you are just going to be in a loop spinning and wasting cycles.

You could easily spend a week going through datasheets for different microcontrollers and doing a bunch of math to figure suitability.  And after all that figure that maybe that isn't the best way of going about it.

Sorry, but engineering is complicated.

[artbyrobot]

goodness you plug the darn thing in, run your code, and if its too slow drop a couple motors from the code or do one microcontroller per motor worst case.  you don't have to figure out any of that nonsense beforehand I just explained the easiest and fastest way to go about seeing how fast it all is.  This is not rocket science folks.

[Leiothrix]

That is pretty easy to say before you have actually tried it 

[Andy Chee]

I already made my case about interrupts being total trash and something to avoid at all costs

In that case, stop using your internet browser, keyboard, mouse and PC right now.  None of it could function without interrupts.

that's a huge lie.  i could EASILY make a mouse that polls for clicks rather than clicks triggering an interrupt.  It is trivial and superior coding practice

You're a huge hypocrite.  You continue to use interrupt enabled equipment such as your PC.

[artbyrobot]

You're a huge hypocrite.  You continue to use interrupt enabled equipment such as your PC.

I'm saying using interrupts is a bad coding practice for many reasons.  Using a PC has nothing to do with me refusing to use interrupts in my code so I backup my statements by the coding practices I myself follow.  Hence not a hypocrite.  Better freshen up on your definition of hypocrite lol

[Analog Kid]

So, another aspect of our intrepid killer robot creator emerges, another side to his multi-faceted personality:
Not only is he the world's champion hubrisist (soon to be an Olympic sport), as we know:
He's also an Arduino fanboi! An instructable baby! A student of YouTube! One of those eager beavers who think the whole world is basically plug-n-play, or should be if it isn't: hey, math schmath! who needs all that normie stuff anyway? just find the damn thing on eBay, solder a few wires to it and whammo!

Interrupts are for l0/Er$ ...

[artbyrobot]

Yes that is correct analog kid.  For hardware I support black box treatment as often as possible, letting others do their jobs and not reinventing the wheel or getting overly deep into documentation and knowing every little thing about it.  I want to know as little as possible to do the job I need to do and not spend any more time than necessary to achieve the goal.  There is PLENTY of research to do and understanding to get to achieve my goal without going into every single rabbit hole possible as some people here are suggesting I do.  That would be folly.

[Analog Kid]

I want to know as little as possible to do the job I need to do and not spend any more time than necessary to achieve the goal.

I can see you in your little office/cubicle, with that everlasting nugget of wisdom framed on your wall. Huzzah! Good job! Well done! Attaboy!

[Andy Chee]

You're a huge hypocrite.  You continue to use interrupt enabled equipment such as your PC.

I'm saying using interrupts is a bad coding practice for many reasons.  Using a PC has nothing to do with me refusing to use interrupts in my code so I backup my statements by the coding practices I myself follow.  Hence not a hypocrite.  Better freshen up on your definition of hypocrite lol

A PC uses interrupts in its operation.  You are using a PC.  Therefore you are using interrupts.

[artbyrobot]

A PC uses interrupts in its operation.  You are using a PC.  Therefore you are using interrupts.

You are twisting what I had to say and doing so pretty obviously deliberately.  I never said nobody should use a device whose trash programmers used interrupts.  What I did say was nobody should use interrupts in their code when they are programming.  HUGE difference and you know it.