![]() | ![]() | ![]() |
| | |||||||
| Robotics Chat Specific to discussions about robots and the making of. |
| | Thread Tools | Display Modes |
| | (permalink) |
| Moderator | 3v0 and I were working on IR detection, and after some brainstorming, we came up with creating a IR robot, That could explore a room autonomously, and would be able to be reprogrammed through a 2x5 ICSP port on the side of it. I am currently working on the PCB still, but it will be done very quickly. 18F1320 Brain 2 IR Emitters 2 IR Recievers TBD what they exactly are SN754410 Motor Driver The hardware would be exactly the same through out the design, but it will come with a ICSP header in case you want to change a part of the code. More to come soon!! EDIT: The pic is a VERY early stage in the Board, but the IC's and LED's are likely to stay there.
__________________ MechTronics |
| | |
| | (permalink) |
| Experienced Member | May I humbly suggest a 28pin PIC (the 18F2525) as it has 2 PWM (motor channels), just connect it like the Mongoose schematic. |
| | |
| | (permalink) |
| Experienced Member | Did you select the motor/gearbox for your robot project ? If you want to use the classical 2 motor configuration I'd say Bill is correct that a PIC with 2 PWM would be a better choice. I planned to play with robotics as well, ordered some Tamyia gearboxes and wheels from www.pololu.com and also their robot chassis - it is really quite cheap, but I did not have time to continue with this project ... It would be interesting to hear more about your robot project Petr |
| | |
| | (permalink) | |
| Super Moderator | Quote:
| |
| | |
| | (permalink) | |||
| Moderator | Quote:
Besides, It will as i already said represent the left and right sides better. Quote:
Quote:
__________________ MechTronics | |||
| | |
| | (permalink) | ||
| Super Moderator | Quote:
Quote:
| ||
| | |
| | (permalink) |
| Moderator | Oh i get at what you mean now, just in the software tell when it left side is on and right side is on? That would not work very well (cyclops robot) because, this robot wants to tell if it is going to hit left side or right side at the same time. It would only be a limiting factor. PCB is coming along good
__________________ MechTronics |
| | |
| | (permalink) | |
| Super Moderator | Quote:
By using a separate 8 pin PIC all you need to do is check the L and R pins from it, I even added LED's on the output so you can see what's happening. | |
| | |
| | (permalink) |
| Moderator | We need to build and get your walter class robot working. It will teach you things that will make VERTA better. Walter is also a good test bed for trying new things. You have everything you need to build a walter including the PCBs. The software to drive it is easy and we can walk through it this weekend. Once the robot moves we can work on the wall detection. Bolt the drive unit to the bottom with the motors sticking out the back a bit. It is best to select a location for the holes/screws so they are between card slots. The same goes for the caster. Keep the screws short. The blue tape is to keep lint and pet hair out of the gears. You can get a small pack of 4-40 screws and a pack of nuts at radio shack. Some crimpers have holes to shorten screws. Each motor should have a red and a black wire that will go to the h-bridge. Drill out the short standoffs in the back above the motor and run the motor wires through them into the box. Put the caps on the motors when you add the wires and make sure the motors go into the clips with the wires and caps in place. Bolt the battery boxes to each side of the box above the rear wheels. If you move them too far ahead there will be too much weight on the caster. Drill a small behind each battery holder and run the wires into the body. Use a small rectangle of perf board with a hole in the center for a small toggle switch. Add a 1A resettable fuse if you have one. Wire a battery red wire to one side of the switch, the other side of the switch to the fuse and the fuse to the black wire from the other battery holder. Drill a hole in the center of the back body wall and slip the switch through, add lock washer and nut. You now have a black and a red battery wire. One from each holder. These will power the h-bridge. You also need to power the CPU board so a 4" bit of wire to each and solder them. In this case the twisted together soldered ends will go into the h-bridge screw terminals. Tin the other ends of the wires you just added. Twist each set of motor wires by chucking them into a cordless drill. We will cut them to length and tin them latter. ![]() Drive and switch in place. The batteries and caster still need to be added. The further ahead you place the wheels the easier it will be to do wheelies. Test balance prior to drilling if you want to do this. I can provide more pics if you want/need them.
__________________ search engine for electronic partsJunebug USB PIC programmer kit. USB Bit Wacker Last edited by 3v0; 8th April 2008 at 01:49 PM. |
| | |
| | (permalink) | |
| Moderator | Building Walter and VETRA are 2 completely seprate things, althought both of them seem like they are the same project. VETRA is seprate from our C learning. VETRA is more like a personal project that uses what I learn from C. As for actually learning new C content, that is where Walter is coming in. I learn with Walter and apply it with VETRA. This is what I always do, I learn with one tool and use what i learn with another tool, a good example of this is worksheets/assignments you get in school. Walter will not take long to assemble, and I will use 2.4V with the Motors, since my Gearbox likes that voltage without squeeling too much. I will operate the circuity off a 9V battery (Alkaline to take into affect voltage) or a 8 pack of AAA/AA cells. Quote:
2. A 1 Sensor 2 LED design does not make sense, unless you sent a signal through the LED's, even then it does not make sense. 3. For ease of programming, a 2 sensor design would be superior, because all you have to do is when it detects an input it reverses, when it doesnt drive straight. 4. A "cyclops" robot has a disadvantage over a 2 eye robot. 5. From your description how would the sensor be able to tell what side from what? remember that I am learning C, and I am not going to use Assembly in this robot, and It will just make it more complex.
__________________ MechTronics Last edited by Krumlink; 8th April 2008 at 02:16 PM. | |
| | |
| | (permalink) | |||||
| Super Moderator | Quote:
Quote:
Exactly the same as you do with two receivers, except you only need one. Quote:
Quote:
Quote:
It makes it incredibly easier for you - just use an 8 pin PIC like in my project - this connects via two pins to your 18F PIC, one for left, and one for right - all your C program needs to do is check if the pins are high or low. Like I said previously, I didn't originally write this - but it's fairly complex in operation, because it uses a voting system to reduce false readings - certainly I found it extremely effective. | |||||
| | |
| | (permalink) |
| Moderator | its not looking straight ahead! Both sensors are looking at a 45 degree angle, that way if left detector senses a wall it backs up the opposite side of the H bridge, but if right side does not detect it goes straight, making it turn. With a 1 sensor design it can only look straight ahead without favoring one side.
__________________ MechTronics |
| | |
| | (permalink) | ||
| Super Moderator | Quote:
Quote:
| ||
| | |
| | (permalink) |
| Moderator | I am going to use a 2 sensor design since I have experience with 2 sensors like that. Also because the sensor is actually bulging out of the packaging slightly, it is a very wide angle reciever. I will be able to see in front slightly , and it will most likely be around 30degrees from straight ahead. I could add a switch if I wanted to. if it detects both, it will back up for a few seconds, and advance. The software is still being wrote to, but the actual hardware will be the same, so we could adapt to what we need.
__________________ MechTronics |
| | |
| | (permalink) | ||
| Super Moderator | Quote:
Quote:
Which is why I said earlier, it needs to turn to avoid the wall if it finds an object directly in front. My first solution was to reverse for a certain time, then always turn the same way (can't remember if it was left or right) - but that was a bit boring and meant it could get stuck. So I altered the routine to make it turn a random direction if it found an object if front - this was far more fun, and makes it behave much more 'alive'. | ||
| | |