Skip to main content

Blog 2

Blog 2
The motors and the wheels have shipped, however, there is a big problem. The current width of our robot is 300mm but it has to be at a maximum of 225mm as stated in the rules of the competition. Possible ways of adjustments could include, but are not limited to, getting smaller motors, getting smaller wheels, removing gearbox off the motor (but I would rather not do this) or make a slightly complicated gear system that was recommended to me by a friend. The current motors I have run at about 450 rpm and have a lot of torque, so I like them a lot and would prefer not to change them. The wheels are also great and have a large amount of grip, perfect for the obstacle course. 
An image of my motors and wheels

Some basic code has already been written and has been tested. I am using the L298n dual H-bridge DC stepper motor controller as my motor controller right now during this 'test' stage of my robot. 

Comments

Post a Comment

Popular posts from this blog

Code Update!

Code Update! After a while of working on writing code, I have finally done it! This script below is adapted from the MonsterJoy code by PiBorg, yet it has a number of important changes. I will probably also tweak the code slightly (ie turn magnitude). #!/usr/bin/env python # coding: Latin-1 # Load library functions we want import time import os import sys import pygame import ThunderBorg import UltraBorg # Re-direct our output to standard error, we need to ignore standard out to hide some nasty print statements from pygame sys . stdout = sys . stderr # Setup the ThunderBorg TB = ThunderBorg . ThunderBorg () TB . i2cAddress = 0xA # Uncomment and change the value if you have changed the board address TB . Init () if not TB . foundChip : boards = ThunderBorg . ScanForThunderBorg () if len ( boards ) == 0 : print 'No ThunderBorg found, check you are attached :)' else : print 'No...
Post a Comment
Read more

Coronavirus update

Coronavirus update  Today we got some really sad news as PiWars was decided to be postponed to a later date. Despite this being unfortunate, it was definitely a well thought out choice and was made for good reasons.  However...... This could also be pretty useful as well because this means that I get (a lot) more time to work on my robot and further develop it. Below is a to-do list of my new ideas: - Get the flywheel mechanism working ASAP - Tweak all my code and do further testing - Work on further autonomous code (to gain more points) I am very excited to accomplish these goals!
Post a Comment
Read more

Robot Chassis

Robot Chassis Below is an image of my finished robot chassis (a proper blog-post will follow shortly): (This is also the image that will be in the actual program)
Post a Comment
Read more