diff --git a/.build/imageSizes.js b/.build/imageSizes.js index 72779c6..0ce7617 100644 --- a/.build/imageSizes.js +++ b/.build/imageSizes.js @@ -127,7 +127,7 @@ function walkDir(root) { }, body: { operation: "download", - objects: objectsToRequest, + objects: objectsToRequest.slice(0,999), ref: { name: "refs/heads/master", }, @@ -137,7 +137,16 @@ function walkDir(root) { console.log( `info: requesting lfs info for ${objectsToRequest.length} images...` ); - const lfsRes = await request(lfsReq); + + var lfsRes; + try { + lfsRes = await request(lfsReq);} + catch {console.log("errored")}; + console.log(lfsRes); + for(let i = 0; i< objectsToRequest.length() / 7; i++ ){ + + } + console.log(lfsRes); const objectsLength = lfsRes.objects.length; for (let i = 0; i < objectsLength; i++) { const object = lfsRes.objects[i]; diff --git a/.vuepress/config.js b/.vuepress/config.js index 42ba89b..9ae0c8a 100644 --- a/.vuepress/config.js +++ b/.vuepress/config.js @@ -65,21 +65,21 @@ const imageSizes = JSON.parse( ); const galleryZipSizes = {}; - const zipsPath = path.resolve(__dirname, "..", ".non-vuepress-public", "galleryzips"); - for (const zip of fs.readdirSync(zipsPath)) { - const zipPath = path.join(zipsPath, zip); + // const zipsPath = path.resolve(__dirname, "..", ".non-vuepress-public", "galleryzips"); + // for (const zip of fs.readdirSync(zipsPath)) { + // const zipPath = path.join(zipsPath, zip); - let size = fs.statSync(zipPath).size; - if (size <= 2147483647) { // If the file is bigger than a buffer it isn't a lfs pointer -const data = fs.readFileSync(zipPath, { encoding: "utf8" }); - if (data.startsWith("version https://git-lfs.github.com/spec/v1")) { - const lines = data.split("\n"); - size = parseInt(lines[2].split(" ")[1]); - } - } + // let size = fs.statSync(zipPath).size; + // if (size <= 2147483647) { // If the file is bigger than a buffer it isn't a lfs pointer + // const data = fs.readFileSync(zipPath, { encoding: "utf8" }); + // if (data.startsWith("version https://git-lfs.github.com/spec/v1")) { + // const lines = data.split("\n"); + // size = parseInt(lines[2].split(" ")[1]); + // } + // } - galleryZipSizes[zip.substring(0, zip.length - 4)] = size; - } + // galleryZipSizes[zip.substring(0, zip.length - 4)] = size; + // } function makeGallerySidebar() { const galleries = fm( diff --git a/.vuepress/public/images/BrainBox lego attachment side profile photo.png b/.vuepress/public/images/BrainBox lego attachment side profile photo.png new file mode 100644 index 0000000..0511dde --- /dev/null +++ b/.vuepress/public/images/BrainBox lego attachment side profile photo.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0e4751a08669380659167516672c1543db17beac9492d4a8027e07ffcf03be6 +size 753591 diff --git a/.vuepress/public/images/BrainBox motor connector side profile photo.png b/.vuepress/public/images/BrainBox motor connector side profile photo.png new file mode 100644 index 0000000..d80bfc3 --- /dev/null +++ b/.vuepress/public/images/BrainBox motor connector side profile photo.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88bcce3a6579c79b6e62300740fa61f6e1dd808968392801991033f2f0addd41 +size 555682 diff --git a/.vuepress/public/images/BrainBox power connector side profile photo.png b/.vuepress/public/images/BrainBox power connector side profile photo.png new file mode 100644 index 0000000..de181d3 --- /dev/null +++ b/.vuepress/public/images/BrainBox power connector side profile photo.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ad89c1a940550ca01e9896084ebd4e3e655d908b86a7d916036fb8e7c496563 +size 696781 diff --git a/.vuepress/public/images/BrainBox red pannel photo.png b/.vuepress/public/images/BrainBox red pannel photo.png new file mode 100644 index 0000000..271550e --- /dev/null +++ b/.vuepress/public/images/BrainBox red pannel photo.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2fd57e980cb1e6cae4d5d629baa5662567352105cf906779ef62cd6e5e8e6569 +size 2528295 diff --git a/.vuepress/public/images/BrainBox servo connector side profile photo.png b/.vuepress/public/images/BrainBox servo connector side profile photo.png new file mode 100644 index 0000000..995df68 --- /dev/null +++ b/.vuepress/public/images/BrainBox servo connector side profile photo.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dfea576b1409303e2c7fd0bc34ed1f16719bd3d24e9544afa828110ce2605889 +size 565381 diff --git a/.vuepress/public/CytronBoardDocs.pdf b/.vuepress/public/images/CytronBoardDocs.pdf similarity index 100% rename from .vuepress/public/CytronBoardDocs.pdf rename to .vuepress/public/images/CytronBoardDocs.pdf diff --git a/.vuepress/public/images/Landscape RC24 image.jpg b/.vuepress/public/images/Landscape RC24 image.jpg new file mode 100644 index 0000000..5d8f8cc --- /dev/null +++ b/.vuepress/public/images/Landscape RC24 image.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:778425a6921464a5dc88fb71f4bd950d8318cb4f54e1fa67129ce6d10a267444 +size 858257 diff --git a/.vuepress/public/images/MiniBot assembly instruction manual .pdf b/.vuepress/public/images/MiniBot assembly instruction manual .pdf new file mode 100644 index 0000000..e42b5e0 Binary files /dev/null and b/.vuepress/public/images/MiniBot assembly instruction manual .pdf differ diff --git a/.vuepress/public/images/RC logo.png b/.vuepress/public/images/RC logo.png new file mode 100644 index 0000000..5d0f334 --- /dev/null +++ b/.vuepress/public/images/RC logo.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d6d74466ee005e84f8d98cfca0738b6fe744bbeb31a4105ad90ba5a094b1ef3 +size 205920 diff --git a/.vuepress/public/images/RC24 Laptop background 1600x900.jpg b/.vuepress/public/images/RC24 Laptop background 1600x900.jpg new file mode 100644 index 0000000..ba6afdc --- /dev/null +++ b/.vuepress/public/images/RC24 Laptop background 1600x900.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49f1275c452be3ed0f5e629d1fa527c90c1df2ae28d535704429262c3bca24b7 +size 219954 diff --git a/.vuepress/public/images/RoboCon 2024 game image.png b/.vuepress/public/images/RoboCon 2024 game image.png new file mode 100644 index 0000000..98087a5 --- /dev/null +++ b/.vuepress/public/images/RoboCon 2024 game image.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e250c975af79419329993a2365d9abb6c613b1512bc1a7c8f0c2ad97539112e8 +size 1317337 diff --git a/.vuepress/public/images/RoboCon 2024 title image.jpg b/.vuepress/public/images/RoboCon 2024 title image.jpg new file mode 100644 index 0000000..81f86dd --- /dev/null +++ b/.vuepress/public/images/RoboCon 2024 title image.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ec8acac4e689f609feab8f9c3a4c6d45b4ec195d80a05b81c818196cb5628c0 +size 357062 diff --git a/.vuepress/public/images/Robocon recruitment poster.png b/.vuepress/public/images/Robocon recruitment poster.png new file mode 100644 index 0000000..0f47acd --- /dev/null +++ b/.vuepress/public/images/Robocon recruitment poster.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b1d8de09950e5b0d664de7a3e025bb17e5551a27dd7a9ff33ebeddc975a1f87 +size 3127682 diff --git a/.vuepress/public/images/angled.png b/.vuepress/public/images/angled.png new file mode 100644 index 0000000..6daab6a --- /dev/null +++ b/.vuepress/public/images/angled.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:71a8b020632ba076257fc76c720343c8a814f17a3ab3d8d12018a2f368f8cbab +size 1784231 diff --git a/.vuepress/public/images/brainboxmotors.png b/.vuepress/public/images/brainboxmotors.png new file mode 100644 index 0000000..d80bfc3 --- /dev/null +++ b/.vuepress/public/images/brainboxmotors.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88bcce3a6579c79b6e62300740fa61f6e1dd808968392801991033f2f0addd41 +size 555682 diff --git a/.vuepress/public/images/powerconnector.png b/.vuepress/public/images/powerconnector.png new file mode 100644 index 0000000..de181d3 --- /dev/null +++ b/.vuepress/public/images/powerconnector.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ad89c1a940550ca01e9896084ebd4e3e655d908b86a7d916036fb8e7c496563 +size 696781 diff --git a/.vuepress/public/images/redpanel.png b/.vuepress/public/images/redpanel.png new file mode 100644 index 0000000..271550e --- /dev/null +++ b/.vuepress/public/images/redpanel.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2fd57e980cb1e6cae4d5d629baa5662567352105cf906779ef62cd6e5e8e6569 +size 2528295 diff --git a/.vuepress/public/images/roboconHeader.jpg b/.vuepress/public/images/roboconHeader.jpg new file mode 100644 index 0000000..5d8f8cc --- /dev/null +++ b/.vuepress/public/images/roboconHeader.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:778425a6921464a5dc88fb71f4bd950d8318cb4f54e1fa67129ce6d10a267444 +size 858257 diff --git a/.vuepress/public/images/run-button.jpg b/.vuepress/public/images/run-button.jpg new file mode 100644 index 0000000..75f4105 --- /dev/null +++ b/.vuepress/public/images/run-button.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f09ff9d604203cf32bfed69b72318d06abb96569f4b1a19dd200ab21e759ea6b +size 14903 diff --git a/README.md b/README.md index f3512bd..32ad9c5 100644 --- a/README.md +++ b/README.md @@ -19,7 +19,7 @@ No previous experience is required, and we provide support throughout the year t

-

The RoboCon 2023 finals were held on the 12th and 13th of April 2023, Robocon 2024 Kickoff is live on the 28th of October!

+

Robocon 2024 Kickoff has Finished on the 28th of October, 2024 Comptetition Expected on the 13th of April 2024


diff --git a/docs/README.md b/docs/README.md index c4f0493..10772e6 100644 --- a/docs/README.md +++ b/docs/README.md @@ -8,14 +8,13 @@ position: 1 Welcome to the docs for **Robocon 2024**! We suggest you first grasp the idea of the [rules](/rulebook.pdf). - :::tip If you are viewing this page on your BrainBox then please check the website for the latest revision. ::: -![Game logo](/images/roboconHeader.png) +![Game logo](/images/roboconHeader.jpg) Once you've done that, you'll need to turn your robot on. To begin, get familiar with the kit provided. It includes : @@ -29,17 +28,19 @@ To begin, get familiar with the kit provided. It includes : | 2 | Motor | | 2 | Wheels | | 1 | Caster Wheel | -| 1 | Chassis Kit | +| 1 | Chassis | | 2 | Servo Motor | | 1 | Start Button | | 1 | Power Switch | -::: caution- Handling batteries incorrectly can be dangerous. Make sure you follow these [safety guidelines](/docs/charging.html) at all times. ::: +:::warning + Handling batteries incorrectly can be dangerous. Make sure you follow these [safety guidelines](/docs/charging.html) at all times. +::: :::tip You can also access these docs from your robot. Go to when you're connected to your robot. ::: -It might also be a good idea to sign up for the [forum](/forum/). You can do this using the registration code provided in your kit. This is a great place to ask questions on anything related to the competition, the kit, or robot programming. +It might also be a good idea to sign up for the [forum](/forum/). This is a great place to ask questions on anything related to the competition, the kit, or robot programming. \ No newline at end of file diff --git a/docs/gpio.md b/docs/gpio.md index 26203d3..f8c1609 100644 --- a/docs/gpio.md +++ b/docs/gpio.md @@ -87,33 +87,3 @@ However, the built-in pull-up resistor alleviates this need. It essentially wire ![An example weak pull up](/images/capture.png) -## Setting multiple pins - -When you set multiple pins, you'll need to set them in order. This is due to how the brainbox internally sets pins - -For example...
-This won't work: -```python -# Wrong -import robot - -R = robot.Robot() - -R.gpio[1].mode = robot.INPUT -R.gpio[3].mode = robot.INPUT_PULLUP -R.gpio[2].mode = robot.OUTPUT - -# Pin 3 is set before pin 2, which won't work -``` -But this will: -```python -# Right -import robot - -R = robot.Robot() - -R.gpio[1].mode = robot.INPUT -R.gpio[2].mode = robot.OUTPUT -R.gpio[3].mode = robot.INPUT_PULLUP -# As all the GPIO pins are set in order, this is fine -``` diff --git a/docs/hello-gpio.md b/docs/hello-gpio.md index fcc4ad6..21f80c6 100644 --- a/docs/hello-gpio.md +++ b/docs/hello-gpio.md @@ -68,3 +68,5 @@ R.gpio[POT_PIN].mode = robot.INPUT_ANALOG while True: print(R.gpio[POT_PIN].analog) ``` + +## Using distance sensors with retroreflective tape diff --git a/docs/hello-motors.md b/docs/hello-motors.md index e996df4..326e166 100644 --- a/docs/hello-motors.md +++ b/docs/hello-motors.md @@ -22,7 +22,7 @@ R = robot.Robot() Motor power is automatically scaled for the 3-6V motors included in the kit, if you are sourcing your own motors then see https://hr-robocon.org/docs/motors.html for how to allow faster speeds. ::: -Now that everything is set up, it's time to set the motors. All the motors are stored in a list inside the Robot variable - to access the first motor, you can use `R.motors[1]`, the second motor is found with `R.motors[2]`. +Now that everything is set up, it's time to set the motors. All the motors are stored in a list inside the Robot variable - to access the first motor, you can use `R.motors[0]`, the second motor is found with `R.motors[1]`. Changing the speed of the motor is easy - just set the motor to a number from -100 to 100. Immediately setting the power to 100 can have unwanted side effects, so we'll start by setting them to half power: ```python @@ -30,8 +30,8 @@ import time import robot R = robot.Robot() +R.motors[0] = 50 R.motors[1] = 50 -R.motors[2] = 50 ``` Running this program will make your robot move forwards. Unfortunately, it will never tell it to stop moving forwards, so hopefully you put it on the floor and it hasn't driven off the table.
To fix this we can set the power of the motors to 0 after a couple seconds: @@ -40,40 +40,40 @@ import time import robot R = robot.Robot() +R.motors[0] = 50 R.motors[1] = 50 -R.motors[2] = 50 time.sleep(2) -R.motors[1] = 0 -R.motors[2] = 0 +R.motors[0] = 0 +R.moto1s[1] = 0 ``` To turn the robot, you just need to set one motor going forwards and the second motor going backwards. The following program makes the robot do a little dance - try it out! ```python speed = 50 +R.motors[0] = speed R.motors[1] = speed -R.motors[2] = speed time.sleep(2) -R.motors[1] = speed -R.motors[2] = -speed +R.motors[0] = speed +R.motors[1] = -speed time.sleep(2) +R.motors[0] = -speed R.motors[1] = -speed -R.motors[2] = -speed time.sleep(2) -R.motors[1] = -speed -R.motors[2] = speed +R.motors[0] = -speed +R.motors[1] = speed time.sleep(2) +R.motors[0] = 0 R.motors[1] = 0 -R.motors[2] = 0 ``` A final note, even if you set both motors to the same power, your robot probably won't drive in a perfectly straight line. This is due to defects in the motors, and unless you get specialised motors, no two motors will have the same offset. How your robot deals with this is up to you! diff --git a/docs/init-robot.md b/docs/init-robot.md index ba502f6..6d952d4 100644 --- a/docs/init-robot.md +++ b/docs/init-robot.md @@ -15,4 +15,4 @@ import robot R = robot.Robot() ``` -When you initialise the robot with `robot.Robot()`, your code will be paused until the hardware start button or Shepherd run button is pressed. When the Robot is waiting for either of these buttons to be pressed, the blue status LED will flash on and off. +When you initialise the robot with `robot.Robot()`, your code will be paused until the hardware start button or Shepherd run button is pressed. When the Robot is waiting for either of these buttons to be pressed, the blue user LED will flash on and off. diff --git a/docs/minibot-assembly.md b/docs/minibot-assembly.md new file mode 100644 index 0000000..07d1f71 --- /dev/null +++ b/docs/minibot-assembly.md @@ -0,0 +1,10 @@ +--- +title: Minibot Assembly +category: Hardware +position: 6 +--- +# Minibot Assembly + +You can download instructions on how to make your minibot [here](/minibot.pdf). + + diff --git a/docs/motors.md b/docs/motors.md index d5e6b76..7945884 100644 --- a/docs/motors.md +++ b/docs/motors.md @@ -20,7 +20,7 @@ If you want to spin your motors in reverse, just stick a negative sign in front You can control motors using the `motors` property of the `Robot` object. To set the power of the first motor to 60% use: ```python -R.motors[1] = 60 +R.motors[0] = 60 ``` To control the second motor instead, replace `motors[1]` with `motors[2]`. @@ -28,8 +28,8 @@ To control the second motor instead, replace `motors[1]` with `motors[2]`. To stop both motors: ```python +R.motors[0] = 0 R.motors[1] = 0 -R.motors[2] = 0 ``` Here's a more complete example: @@ -40,14 +40,14 @@ import robot R = robot.Robot() # set motor 1 to 60% power -R.motors[1] = 60 +R.motors[0] = 60 # set motor 2 to 60% power in the backwards direction -R.motors[2] = -60 +R.motors[1] = -60 # turn both motors off +R.motors[0] = 0 R.motors[1] = 0 -R.motors[2] = 0 ``` :::tip diff --git a/docs/patching-the-robot.md b/docs/patching-the-robot.md index 3e015df..8f9aafd 100644 --- a/docs/patching-the-robot.md +++ b/docs/patching-the-robot.md @@ -19,7 +19,7 @@ An important part of looking after your robot is making sure its software is up 6. Select the patch file in the left-hand panel. The patch will show on the code view as Base64 encoded data (random-looking text).  7. Click the "Run" button (green arrow on the right-hand panel).  - ![](/images/run-button.png) + ![](/images/run-button.jpg) 8. After a few moments, your BrainBox should reboot, and the LED will either turn off or remain on. You will lose connection with it while it does this. Do not turn off your BrainBox - the LED may stay off for up to a minute. 9. The BrainBox LED will eventually start flashing again to show it has rebooted successfully.  10. If your PC has not automatically connected, connect to it using the WiFi. Once reconnected, refresh your browser and open a project from the left-hand side of the editor. Check that the patch version is correct in the right-hand panel.   diff --git a/docs/servos.md b/docs/servos.md index c18a458..770faf7 100644 --- a/docs/servos.md +++ b/docs/servos.md @@ -16,10 +16,10 @@ Servos are plugged into the **PWM** ports on the BrainBox. **PWM 1** represents You can control servos using the `servos` property of the `Robot` object. To set the first servo to the 50% position use: ```python -R.servos[1] = 50 +R.servos[0] = 50 ``` -To control the fourth servo instead, replace `servos[1]` with `servos[4]`. +To control the fourth servo instead, replace `servos[0]` with `servos[3]`. Here's a more complete example: @@ -29,14 +29,14 @@ import robot R = robot.Robot() # set servo 1 to the 50% position -R.servos[1] = 50 +R.servos[0] = 50 # set servo 3 to the -100% position -R.servos[3] = -100 +R.servos[2] = -100 # set servos 1 & 3 to the default positions -R.servos[1] = 0 -R.servos[3] = 0 +R.servos[0] = 0 +R.servos[2] = 0 ``` ## Blockly @@ -52,9 +52,9 @@ E.g. to set PWM1 to `100%` and PWM3 to `50%` use import robot servo_values = { - 1: 100, - 2: 50, - 3: -100 + 0: 100, + 1: 50, + 2: -100 } R = robot.Robot(servo_defaults=servo_values) diff --git a/docs/the-brainbox.md b/docs/the-brainbox.md index ec7fae6..6a679b0 100644 --- a/docs/the-brainbox.md +++ b/docs/the-brainbox.md @@ -5,15 +5,15 @@ position: 2 --- # The BrainBox -The BrainBox is the center of the kit, it controls power, provides you with useful electronics and is where your code runs. Do **NOT** open the BrainBox unless given written permission by Hills Road RoboCon. - -![The brain box](/images/brainbox.jpg) - +The BrainBox is the core of the kit which we provide. In it is all of the electronics and software you need to power a robot. Lets start by turning it on. Take a battery from the kit and plug it into the yellow socket labelled battery, then take a red "power button" and connect that to the black connector along the side of the BrainBox. The battery and start button are both labelled on the red surface of the BrainBox. +![The brain box](/images/angled.png) +## How to turn everything on +Pressing the start button will cause the battery status LEDs on the front of the BrainBox flash in an upwards direction and the power LED turns green. When the user light starts flashing blue your BrainBox is ready to run code. You can now turn connect to your robot. The user LED will go solid while code is running. ## Power The BrainBox distributes power to the robot from the battery. It provides both 12V and 5V power out. All power must go through the BrainBox and the fuse should never be replaced. -The On|Off switch also plugs into the BrainBox as well as the Start button which is used to start your robot code running. +The On/Off switch also plugs into the BrainBox as well as the Start button which is used to start your robot code running. @@ -62,6 +62,12 @@ The specifications for the motor board can be found [here](/CytronBoardDocs.pdf) You can toggle the 12V which allows you to turn 12V devices on and off easily. However, this will also cut power to the motor board. ::: +## How to turn everything off +When you are done for the day, press the power button, the user LED will flash rapidly, when this turns off you may unplug the battery. + +## USB's +On the new brainBox, there is only one USB port. If you want to use something that requires a USB port such as a USB camera, you will need to get your own USB hub. + ## GPIO ### GPIO - Out @@ -100,21 +106,18 @@ The PWM pins ranges: ## Pin Out -### USB's +### IO -![USB's](/images/brainboxdocsusb.png) +![USB's](/images/powerconnector.png) ### Motors -![Motors](/images/brainboxdocsmotors.png) - -### GPIO +![Motors](/images/brainboxmotors.png) -![GPIO](/images/brainboxdocsgpio.png) ### Front -![Front](/images/brainboxdocfront.png) +![Front](/images/redpanel.png) ## Expansion I2C, UART & USB diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 9f7b97a..af64eaf 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -19,6 +19,9 @@ This can happen if erroneous code which does not start with `R = robot.Robot()` Using this file will overwrite the current robot code. It will not touch any files you have stored in the editor. ::: +## I've connected a battery and the power switch to the black connector but never get any lights on the Brainbox +If the battery is fresh, it's possible that the switch has failed or become internally disconnected. For testing purposes, you can swap the power switch for a single piece of wire. NOTE: at the competition, you must have a red power switch to control your robot as per the rules. Finally - in exceptional circumstances the fuse in the cable may have failed, if this has happened then there must have been some terminal problem internal to the BrainBox - Contact us on robotics@hillsroad.ac.uk for instructions. + ## The BrainBox appears to power up, the blue LED light flashes but I cannot connect to it using the WiFi. We apologise for the poor choice of font, zeroes and capital-o's can be confused as can capital-i's and number ones. Try swapping these. @@ -47,35 +50,6 @@ print(R.see()) ``` If this prints out the markers then the issue is probably with your code, please see the [vision docs](https://hr-robocon.org/docs/vision.html) -## My GPIO input doesn't seem to work. -When you set multiple pins, you'll need to set them in order.
-This won't work: -```python -# Wrong -import robot - -R = robot.Robot() - -R.gpio[1].mode = robot.INPUT -R.gpio[3].mode = robot.INPUT_PULLUP -R.gpio[2].mode = robot.OUTPUT - -# Pin 3 is set before pin 2, which won't work -``` -But this will: -```python -# Right -import robot - -R = robot.Robot() - -R.gpio[1].mode = robot.INPUT -R.gpio[2].mode = robot.OUTPUT -R.gpio[3].mode = robot.INPUT_PULLUP -# As all the GPIO pins are set in order, this is fine -``` - -This is due to how the brianboix internally sets pins. ## Can you post a kit to or from Hills Road @@ -89,8 +63,3 @@ The patch is an update which improve your BrainBox, by adding more docs, more bl The Raspberry Pi does not keep time when it is off and so has no way of knowing how much time has passed since it was turned off. -## Can't fit the 12v socket because of the case design - -I can't fit in the 12v socket because of the case design - -Sorry about that, the studs are positioned and sized to take lego, you can slim down the offending stud using a hot blade or a Dremmel tool. diff --git a/docs/vision.md b/docs/vision.md index ad3a518..30fa485 100644 --- a/docs/vision.md +++ b/docs/vision.md @@ -55,12 +55,14 @@ Every april tag has a code: - April tags 100+ will around the arena on the walls. See the rules for specifics on where around the rules they will be placed -| Code | Team | +| Codes | Team | | -------- | ----- | -| 0 to 9 | Leon | -| 10 to 19 | Zhora | -| 20 to 29 | Pris | -| 30 to 39 | Roy | +| 100-123 | Arena Marker | +| 00,20 | Russet jacket potatoes | +| 01,21 | Sweet potatoes jacket potatoes | +| 02,22 | Maris piper jacket potatoes | +|03,23| Purple potato jacket potatoes| +|04-19, 24-39| Arena owned hot potatoes | ## Blockly