Finals: Finally. Not final practice finals. Final finals – the finale. Finally. We rose at 7 AM for breakfast on the final day, after only 4 hours of sleep. Over cups of tea and coffee, we glared at Aaron and Riley, who seemed loud and cheerful as usual thanks to their slightly earlier night (and...Read More
The 29th of July was an opportunity for the S.A.R.T and the four other qualifying teams – Blue Storm, Tupac, Kings Legacy and Magistry – to run practice trials through the final maze configuration before finals. Above: The RMRL team assemble the final maze. Taken on the 29/07/2017 at 12:53 PM. While construction was underway, we...Read More
It was another early morning for the S.A.R.T on Friday the 28th of July. The preliminary or qualifying runs were due to start at 1 PM, however, we wanted to arrive at the venue early to continue practice and work on the sensor software. It seems we didn’t take any photos at all until after...Read More
The 27th of July was the first day of RoboCup 2017. In our division, the Rapidly Manufactured Robot League, the first day was designated a practice day – a time where teams could test various versions of their robots on the final mazes and decide which configuration to use in the preliminary runs on the...Read More
It’s been exactly one month since RoboCup 2017 began, so now is as good a time as any to share the experiences we had. We arrived at the Takeda Teva Ocean Arena early on Wednesday the 26th at 8 AM. With RoboCup yet to officially start, the venue was only open for teams to set...Read More
You’ve read all about Ryan’s “movement.py” script, so now it’s time to learn about “controlscript.php” – the script that collects client keystrokes and sends the movements to the WebSocket server. The script can be accessed at our GitHub repository here. So, let’s break it down! Firstly, “controlscript.php” is a misnomer. It should really say “controlscript.js”,...Read More
We’ve recently been talking about the sensors we want to implement on the robot. We were interested in some sort of mapping or distance detection, so we first considered sonar sensors. However, as these are far too bulky for our small design, we settled on SHARP Infared sensors. Also added was an accelerometer and compass....Read More
I uploaded all the robot’s design files and some renders I made of the mocked up internals in Sketchup. https://www.thingiverse.com/thing:2430783 In other news, the filament we ordered didn’t arrive (again), so we used some spare red ultimaker filament to print the lid, and we’re starting to put the components in the robot’s chassis. It’s...Read More
Welcome to part 3 of Let’s break it down! ‘movement.py’. In the last post we went over two massive functions: ‘bckFwdRun(key, s)’ and ‘leftRightRun(key, s)’. In this post, we’re going to look at the next functions. These two functions play a very important part in the communications between python and client SART Control Panel. Both...Read More
Today we’re back into breaking down the movement.py script. The last post walked through many of the functions needed to run the robot. Now we are going to break down some functions that create the movement. Without further ado, allons y! bckFwdRun(key, s) This function is what we call when we want the robot to go...Read More
