835 karma · joined November 12, 2016
F(f_1(x_1), f_2(x_2), …, f_n(x_n))
The root function is a collection of projections acting on (x_1, x_2, …).
And the components receive the right set of coordinates to act on.
I’m not sure if it’s clearer that way though.
The root node can intercept all messages but its main responsibility (TEA) is to dispatch the messages to the right component(s).
I got this impression on my own self while studying math in college.
I noticed it when I made the connection about the studied subject, wondering why didn’t the professor say it that way to begin with. Because everything made sense now…
After few likely moments I asked myself the question: was the last explanation really better or did I just happen to understand the thing at that particular moment?
Later on, you get the “better” explanation while practicing the art…
We’re usually not aware of the process of understanding itself.
You gotta be kidding. No one asked you for your new costly features btw.
People wanted a decent search engine, not a Swiss army knife.
Eg. https://historyandwar.org/2015/09/11/dassault-rafale-vs-f-35...
Proper servos with high torque are quite expensive. I wanted to keep the project under a certain amount to scale it.
With the springs to compensate the static loads (gravity) I can use weaker servos but I didn’t yet completed the “sensitivity table” of the generated angular momentums.
Yes indeed, the ~10arcmin should represent something like 5mm at about 1m distance. Plus the ~30mm of the 1.8deg/step again at 1m or 3mm with 10:1 gearbox.
I thought I could tackle it by using more expensive parts (but weaker) at the end part of the arm for instance and write a software to orchestrate all the 6motors together.
I didn’t know about the harmonic drive I’ll look into it.
Thank you again for the references.
I did the drawings of several drones and robot arms, and accurately computed the needed torque. I target specific precisions for several applications.
I’m a mathematician so the math is straightforward to me though as you said, it’s super easy to overlook something without the appropriate experience, especially since it’s cross disciplinary (ME, EE, SE… etc. All at once yeah!)
I found these for instance on eBay:
* https://www.ebay.com/itm/393967889048
* https://www.ebay.com/itm/275442630163
I can get from them more than 120Nm with the appropriate planetary gearbox without sacrificing too much speed and even more with gas springs compensating the static loads… theoretically… but I’m a bit skeptic about the announced 12Nm and the 51200microsteps/rev resolution for instance.
I think it’s better (in my case) to have access to maximum IO on the encoder side.
I’ll double check the electrical installation with a pro for sure, I already did a mistake in the past that almost destroyed the house boiler in the middle of the winter… lesson learned.
I hardly can find something worth looking at outside of ebay.
A lot of websites don't have public price lists but ask you to fill forms and receive quotes, but I don't want to order thousands of these (yet?)...
Successful implementations were made in several languages now.
Eg. Most of European countries have fixed amount working hours. Your contract will be for 40h or 35h a week.
Meaning that if you did work your specified time as you say, then what?
The tutorials try to teach a soup of functional programming, build systems, configurations, nix language and nix framework, and that’s somewhat difficult to disentangle and tell what’s what.
Anyway I use it as my daily driver now, and overcame almost all the difficulties, but one still remains: the lack of static type checking. It’s hard to build and validate modules without having this built in the language itself.
I’m hoping that you’d accelerate the work on nickel and try to automatically translate the current nixpkgs/nixos.
This document is incredible!