/diy/ - Do It Yourself » Thread #894545

[19 / 2 / ?]

223KiB, 659x659, PiBot-B.jpg

learning robotics

Anonymous Wed 28 Oct 2015 08:29:28 No.894545 View Reply Report Delete

Quoted By: >>894563 >>894745 >>894793 >>895680

I've always had a fascination with AI.

I have a degree in comsci, and work in the field.
I've always wanted to go back to university and get a 2nd degree in mechatronics engineering, but i simply don't have the time.

I have no experience with electronics, or even more low level programming, directly interfacing with hardware.

I'd love to get something like a raspberry pi, and make a little battery powered robot that rolls around, using a camera for basic collision detection.

I have absolutely no idea where to start.

Any suggestions on where to start?
Any good guides/tutorials/etc?

Anonymous

Anonymous Wed 28 Oct 2015 09:43:27 No.894563 Report Delete

Quoted By: >>894564 >>894565 >>894567

>>894545
>directly interfacing with hardware
>raspberry pi
Raspberry pi is just a small computer that runs Linux. Arduino is the platform for directly interfacing with hardware, but Arduino's programming model is extremely dumbed-down for anyone with a degree in comsci. Your best bet would still be an Arduino, but use AVRdude instead of the Arduino IDE.

Anonymous

Anonymous Wed 28 Oct 2015 09:45:23 No.894564 Report Delete

Quoted By: >>894565

>>894563
Just been watching some youtubes on it;
https://www.youtube.com/watch?v=pbCdNh0TiUo

Looks more up my alley.

But in saying that, i have done a lot of assembly in the past. I'd just prefer to work with a slightly higher level language.

Anonymous

Anonymous Wed 28 Oct 2015 09:46:40 No.894565 Report Delete

Quoted By:

>>894563
>>894564
Scrap that, misread what you wrote. I'll look into Arduino tomorrow. Thanks.

Anonymous

Anonymous Wed 28 Oct 2015 09:51:30 No.894567 Report Delete

Quoted By: >>894727 >>894866

>>894563
Rubbish.

Arduino and R-Pi have pretty-much identical digital I/O. The only difference between the two is that Arduino has built-in analogue pins, whereas the Pi you have to add a USB or I2C DAC.

Anonymous

Anonymous Wed 28 Oct 2015 17:44:57 No.894727 Report Delete

Quoted By: >>894740

>>894567
Which would you recommend i start with?

Arduino seems to be much more standard.

Anonymous

Anonymous Wed 28 Oct 2015 17:59:20 No.894740 Report Delete

Quoted By: >>894743

>>894727
Arduino is easier to do digital I/O with, but you're not going to do camera-based collision detection with it.

Anonymous

Anonymous Wed 28 Oct 2015 18:02:44 No.894743 Report Delete

Quoted By: >>894749 >>894797

>>894740
What about some other forms of collision detection?

I have no idea if these are even real components i can easily add, but rangefingers, sonar, etc?
Moreso for determining distance from an object in a straight line, rather than image processing.

Anonymous

View Same Google ImgOps iqdb SauceNAO ris.jpg, 47KiB, 500x314

Anonymous Wed 28 Oct 2015 18:10:10 No.894745 Report Delete

Quoted By: >>894799

>>894545
>where to start
start here.

takes a lot of bother out of designing and building the chassis and lets you concentrate on mucking about. there are tons of plans for home made sensors and there was a vision command system but it was shit.

Anonymous

Anonymous Wed 28 Oct 2015 18:22:50 No.894749 Report Delete

Quoted By:

>>894743
Both work, and there are pre-made modules you can use. See eg. https://www.arduino.cc/en/Tutorial/RobotRunawayRobot

Anonymous

Anonymous Wed 28 Oct 2015 20:22:19 No.894793 Report Delete

Quoted By:

>>894545
>>894545
learn how to program first. Then fuck around with ROS in robot simulators like gazebo or v-rep. There is no need to actually buy a robot to 'learn robotics' in this day and age.

http://www.ros.org/
http://gazebosim.org/
http://www.coppeliarobotics.com/

Anonymous

Anonymous Wed 28 Oct 2015 20:28:02 No.894797 Report Delete

Quoted By:

>>894743
Look if you want to build something that doesn't just go around bumping into stuff and uses modern robotics approaches build one of these:
http://www.transistor.io/homebuilt-turtlebot.html

it's a roomba with a kinect and laptop on it.

Anonymous

Anonymous Wed 28 Oct 2015 20:36:00 No.894799 Report Delete

Quoted By:

>>894745
Second that.

Not only does it have everything you need to build robots, an easy-to-use IDE and programming language, and a step-by-step course, but when you're ready to move on you can flash the Lejos JVM to the control brick and program it in Java, or any other language that compiles to Java bytecode.

The stuff's sufficiently powerful that it's used in universities.

Yes it's pricey, but you'll have a blast.

Anonymous

Anonymous Wed 28 Oct 2015 22:33:32 No.894866 Report Delete

Quoted By: >>894943

>>894567
It different...

On an arduino or similar MCU, your timers are accurate to the microsecond, and setting a GPIO is literally writing a register. On raspberry pi, your timers are not precise because it's going through an OS, and setting a GPIO involves making calls through layers of drivers and shit. It's behind the scenes, but it affects the timing. You can do things on an MCU, like drive the phases of a brushless motor, that a raspberry pi lacks the precision or finesse to do.

Plus, the PWMs, timers, and interrupts are very powerful. You can write a program, not necessarily in arduino's "baby's first program" IDE, but in the underlying AVR's IDE, where almost all your code in is the various IRQs. You can't chain events like that when half your peripherals are USB or I2C.

Anonymous

Anonymous Thu 29 Oct 2015 03:10:17 No.894943 Report Delete

Quoted By: >>895080

>>894866
Just put your code in the kernel (http://sysprogs.com/VisualKernel/tutorials/raspberry/leddriver/), or stick your process on a realtime core and use a stub driver to map the GPIO device into the process's memory.

You might complain that that's not using the development environment that came with it, but sauce for the goose and all that.

Anonymous

Anonymous Thu 29 Oct 2015 12:53:53 No.895080 Report Delete

Quoted By: >>895086

>>894943
Even with an rt-kernel an AVR can easily outperform an RPi when it comes to latency and especially determinism. Not to mention that the rt-kernels often trigger various driver bugs. But whatever.

Anonymous

Anonymous Thu 29 Oct 2015 13:29:09 No.895086 Report Delete

Quoted By: >>895117

>>895080
But this isn't an rt-kernel: this is process isolation mode.

You name the cores at boot time, and nothing but your process is allowed to run on them.

This means you're dealing with a 700MHz microcontroller, while the other core is still a 700MHz PC for all the boring, non-latency-critical stuff like networking, storage, debugging, etc.

Anonymous

Anonymous Thu 29 Oct 2015 14:14:50 No.895117 Report Delete

Quoted By:

>>895086
How's the real-life jitter, taking bus contention and shared caches into account? For one project I worked on, running Linux on one core and an RTOS on another was considered for a while, but the people with more hard real-time experience all said it wasn't worth the extra complexity, and you wouldn't be able to achieve fully deterministic response times anyway.

Anonymous

Anonymous Fri 30 Oct 2015 15:21:12 No.895680 Report Delete

Quoted By:

>>894545
learn about neural networks there's plenty of good free pdfs online i found starting with a breif overlook like found in university notes then moving into more in depth books. you don't need electronics ect just some programming knowledge, picking up python for this isn't too hard especially if you've already got programming experience.

Subject

Name

E-mail

Password

Capcode	All Only User Posts Only Verified Posts Only Moderator Posts Only Manager Posts Only Admin Posts Only Developer Posts Only Founder Posts
Show Posts	All Only With Images Only Without Images Only Spoiler Images Only Non-Spoiler Images
Deleted Posts	All Only Deleted Posts Only Non-Deleted Posts
Ghost Posts	All Only Ghost Posts Only Non-Ghost Posts
Post Type	All Only Sticky Threads Only Opening Posts Only Reply Posts
Results	All Grouped By Threads
Order	Latest Posts First Oldest Posts First

On these boards

Your latest searches

learning robotics