Back
[01:02:32] <rue_house> change of direction, I'm gonna ditch the stepper arm and put togethor a force feedback servo demo
[06:56:09] <SpeedEvil> rue_house: You can make a very convincing force feedback demo of a robot that keeps something in the same position using only a concealed nail.
[09:20:48] <rue_house> heh
[09:21:06] <rue_house> I'll just hook up two servos into a force-feedback master-slave
[09:33:32] <rue_house> so, I'm thinking of pulling the controllers out of servos, standardizing a 6 pin connector for the motor/pot, and building a serial control 8 or 16 channel loop controller
[09:35:19] <studious> Hello, I would like to ask are there any good robotics projects for a computer science guy?
[09:35:34] <rue_house> starter projects?
[09:36:32] * rue_house pokes studious
[09:37:11] <rue_house> studious, hey
[09:37:26] <studious> rue_house: I have done quite a few basic projects and have the basic idea about microcontrollers
[09:37:35] <studious> rue_house: t
[09:37:53] <rue_house> did you want to just get into making thigns move?
[09:38:21] <studious> rue_house: *At what level is a maze solver? What do you mean making things move??
[09:39:03] <rue_house> well, what your describing is often the transition between programming things that just sit there and flash, and programming things that move
[09:39:31] <rue_house> so, do you, for now, want to do programming that makes things move?
[09:39:48] <studious> rue_house: I have done that already
[09:40:00] <studious> rue_house: Like I know embedded C
[09:40:31] <studious> rue_house: Ok, can you give me advice about starting from scratch? Sometimes I don't enjoy Robotics projects 'cause the project has already been made, there seems to be no innovation to me unlike my software projects.
[09:40:41] <rue_house> so then you want to have a goal for something that moves?
[09:41:10] <studious> studious: I want something innovative, which will push me to think, suggest what you feel like
[09:41:18] <rue_house> ok
[09:41:24] <rue_house> make a robot that dances
[09:41:31] <rue_house> its harder than you might think
[09:42:06] <rue_house> https://youtu.be/slxOrCXxXOg
[09:42:24] <rue_house> I put out the challnage about 12 years ago, and I'm still the first to pull it off
[09:44:27] <studious> rue_house: That's awesome! You must be very intelligent. And I have another doubt. What have found in my robotics projects is that I have to understand the microcontroller pins and then it all boils down to to joining parts and programming. I don't want that
[09:45:56] <rue_house> well dancing is a pretty good challange
[09:46:05] <studious> rue_house: Although I have no doubt that what you have suggested must indeed be challenging
[09:46:18] <studious> rue_house: Yep, anything else?
[09:47:08] <rue_house> well there is always line following, its a good simple start
[09:48:05] <studious> rue_house: Done that a year ago. Need something more advanced
[09:48:10] <studious> rue_house:
https://www.youtube.com/watch?v=9vwZ5FQEUFg Watch this
[09:50:35] <rue_house> I'm the first hobbyist
[10:32:31] <studious> rue_house: What does that mean
[10:32:44] <studious> rue_house: Wow really?!
[10:38:02] <studious> rue_house: You still there? I need more guidance
[10:41:53] <studious> Anyone else there
[10:52:55] <studious> Uh hello!
[10:53:01] <studious> Anyone still there?
[10:56:39] <deshipu> still?
[10:57:42] <studious> deshipu: Yep
[12:18:11] <veverak> deshipu: what do you use to glue servos together?
[12:29:24] <deshipu> veverak: cyanoacrylic glue
[12:29:41] <deshipu> veverak: I used to use a two-component epoxy, but ran out of it
[12:29:46] <veverak> hmm
[12:29:56] * veverak is using double-sided tape
[12:30:00] <veverak> it fail off, again
[12:34:23] <deshipu> yeah, tape is not too strong
[12:38:16] <robotguy> rue_house: Hey
[12:38:40] <robotguy> rue_house: I got disconnected, I had another username at that time
[12:39:41] <veverak> deshipu: but
[12:39:46] <veverak> deshipu: speaking of 3d printing
[12:40:04] <veverak> deshipu: I am thinking about making "U" shape part to hold femur/coxa servo together
[12:40:17] <deshipu> yeah
[12:40:22] <veverak> with "axis join" on bottom of it
[12:40:31] <veverak> could result in something small and sleek :)
[12:40:34] <deshipu> veverak: would also work for the camera gimbal
[12:40:41] <veverak> deshipu: will see about that
[12:40:47] <veverak> deshipu: I believe gimbal won't need it
[12:41:04] <deshipu> I mean, if you have it already, why not make one more
[12:41:39] * veverak got little fanatic about using less parts as possible on this project
[12:41:41] <veverak> a bit
[12:41:43] <veverak> :)
[12:46:39] <deshipu> well, in place of the 3d-printed parts you already have, of course
[12:46:55] <deshipu> better to have 5 identical parts than 2, 2 and 1
[12:47:30] <veverak> hmm
[12:47:41] <veverak> that U parts won't really replace anythign I allready got
[13:58:14] <mathoguy> Can I get some advice regarding my career?
[13:58:48] <Snert_> ask for a raise.
[13:59:43] <mathoguy> mathoguy: I am a student
[14:06:02] <mathoguy> So I am interested in both robotics and software(the algorithms and data structures part), so I was wondering if doing robotics projects involving heavy algorithm based coding will make me look good for a software company like google
[14:10:08] <Snert_> I think a better blend would be to exhibit mechanical engineering as well as coding skills. Strictly coding is dime-a-dozen.
[14:12:07] <mathoguy> Snert_: I have an electrical and electronics backgroung, made myself strong in software with self study
[14:12:32] <Snert_> show them you can build somethig.
[14:12:37] <Snert_> not just code.
[14:14:26] <mathoguy> Snert_: Yep, that!!!!
[14:14:48] <mathoguy> Snert_: Even if it's not just purely software, right?:
[14:15:12] <Snert_> if code is all you can do then a red dot will show up and take your job for 1/2 the money.
[14:15:49] <mathoguy> Also, I want to know, if they want people who can innovate and build, then why do they ask people lots of questions on algorithms and data structures?
[14:16:32] <Snert_> maybe they want you to not be able to answer it.
[14:16:42] <Snert_> they can be tricky.
[14:17:04] <Snert_> they may be looking for someone that doesn't actually know.
[14:18:14] <mathoguy> Snert_: So tricky lol
[14:18:19] <Snert_> they may ask you about a ficticious algorithm, expecting you to say "never heard of that".
[14:18:32] <Snert_> and if you bluff, they'll know it.
[14:19:11] <mathoguy> Snert_: But they ask actual questions too
[14:19:22] <Snert_> indeed. but not always.
[14:19:41] <Snert_> their motives are gray.
[14:21:18] <mathoguy> Snert_: The people on #algorithms don't think so. Hope you are right and I get selected
[14:21:45] <Snert_> you'll get a job.
[14:21:57] <Snert_> and it won't be working on RoboCop.
[14:22:23] <Snert_> you'll update documentation and asskiss the senior engineers.
[14:23:15] <Snert_> and get coding jobs they don't wanna do.
[14:24:13] <deshipu> there are few research positions that involve actually inventing stuff
[14:24:24] <deshipu> and then there is everyday work
[14:24:38] <deshipu> welcome to your adult life
[14:24:51] * DagoRed nods
[14:24:54] <DagoRed> so true deshipu
[14:25:17] <deshipu> solution: a hobby
[14:25:21] <mathoguy> deshipu: I want a research positions
[14:25:39] <Snert_> you will need to start at the bottom, dude.
[14:25:44] <Snert_> not the top.
[14:25:48] <mathoguy> Snert_: Why are you saying that? Did I say anything wrong?
[14:25:51] <deshipu> mathoguy: then study a lot
[14:25:53] <mathoguy> Snert_: What do you mean?
[14:26:11] <Snert_> nobody starts at the top in any profession.
[14:26:27] <deshipu> except for porn stars
[14:26:48] <Snert_> hmmm. good point.
[14:27:30] <mathoguy> Snert_: Yes, nobody starts at the top, right? But when did I say I directly wanna go to the top
[14:28:14] <Snert_> it wasn't personal.
[14:28:43] <mathoguy> Snert_: Ok
[14:31:30] <mathoguy> Snert_: Thanks a lot for your help
[14:31:31] <mathoguy> Bye
[14:32:26] <deshipu> ok, so the user gives me the desired baudrate -- I know the clock speed, and I have to calculate the pre-divider and the tick-count, so that baudrate = clock / (prediv * ticks)
[14:32:33] <deshipu> is there a standard way to do that?
[14:32:52] <deshipu> I know what prediv * ticks should be, but what then?
[14:49:45] <codepython777> is there something I can buy which can tell me where one robot is compared to the other?
[14:56:37] <deshipu> a webcam
[14:56:51] <deshipu> also, didn't you ask that question several times already?
[17:59:30] <rue_house> deshipu, you know there is a baud rate calculator right?
[17:59:39] <rue_house> it'll tell you what to load into the divider
[19:14:29] <Tom_itx> http://wormfood.net/avrbaudcalc.php
[19:59:30] <rue_house> thanks tom
[19:59:35] <rue_house> I had a power outage