Our team, 404 Not Found, is led by Kartik, and our builders and programmers: Jerimiah, Aryan, Keshav, Aditya, and I (Robin). With a second place finish for the Term 2 In-House competition, we are aiming for first place at the next Robocup competition. I would like to acknoledge @denyahnov and his team for the IR seeker framework and giving us lots of inspiration throughout the term.

• simulation.py: simulates the environment of a robot, includes indivdual motor movement.
• ./remote/
  • client.py is what runs on the robot, which controls client-sided movement + receiving controller values
  • server.py is what you run on your laptop, so the robot can connect to it and an external controller communicates with it.
• ./src/
  • code written before and during nationals competition.
• ./newremote/
  • client.py* runs on both robots
  • controller.py runs on the laptop, connects both robots through bluetooth
• ./themes/
  • generate_random_theme.py creates a theme template with random colours. No practical purpose, just for fun.
  • Colour themes in .json files
• ./other/ (for testing, debugging, and previous versions)
  • car ball visualisation.py - Pygame application for determining the angle at which the robot must move to position itself in terms of the ball.
  • Car movement visualiser.py - Pygame application for visualing the holonomic wheel system.
  • localhost_client.py - Connects to src/controller.py through localhost instead of bluetooth. Now ported to client.py
  • The rest of the files are variations to the main files which were used for debugging.
• ./assets/
  • Flowcharts and pseudocode on the Github.

Currently working on a simulator for the robot, ball, and field. Press m to cycle through different movement modes. Individual motors is the most useful as it includes rotation and you can program the individual motors to turn. Automatic mode reuses my automated code from the EV3 robot, and uses 'virtual IR sensors' to detect the ball. Click to move the ball around.

Demonstration code which simultaneous takes rotation and translation as inputs and sets the speed of all four motors.

I had issues at Nationals involving the compass sensor spazzing out, and I have no idea if it was interference from the motors or just the earth being weird. Much of the code in ./src is follow-ball or hastily written for our games.

1. Go to "Wireless and Networks" on the EV3 and connect to the laptop through bluetooth. It should be connected if there is an address at the top of the display.
2. Search "cmd" on the laptop, enter ipconfig /all and scroll down until you see Ethernet adapter Bluetooth Network Connection. Copy the physical address, replacing the hyphens with colons. e.g. 6C-A1-00-05-72-DE -> 6C:A1:00:05:72:DE. Paste this into the "host_address" of the options.json file.
3. Run controller.py. It should say "Server is listening on addr:port".
4. Run client.py on the EV3. After 10-15 seconds, the window on the laptop should update to show a user interface.

• Capable of connecting one or two robots.
• On the UI, change the slider and press the set speed button to change the speed of the respective robot.
• Activating the switch will turn on/off the automatic gameplay.
• The reset orientation button allows for reorientating the robot such as between rounds, on damaged callouts.
• The joystick acts as a remote control*. It will override automatic gameplay if the switch is activated.

1. connect the ev3 brick via bluetooth

• scan for devices and connect to the laptop
• make sure it says status: connected

2. open command prompt (cmd)

• type in ipconfig /all
• find the one that says bluetooth connection
• copy the physical address

3. paste this into the options.json file, as host_address.

• replace the - with : just like the one already in the file
• save file

4. run server.py, make sure that it says Server listening on address:port.

• make sure tkinter is installed
• this can be done by entering pip install tkinter in terminal

5. once server is listening, run ROBIN.py on the ev3.

• if all goes well, after around 10 seconds the gui should open on the laptop and you can control it with the joystick on the top right

• Joystick remote control
• Remote activation and speed variability
• Reset orientation button for easier robot reset sequence.
• Holonomic wheel system
• Capable of scoring consistently

• Communication between both robots
• Possibility for only one robot attacking?
• Making a robot which can travel around the field at top speed and accuracy.