Last before Cambridge

So this is possibly our last blog entry before we're off to Cambridge with Zyderbot, ready or not. I'm sure we'll take part in everything anyway but this is where we're at right now. 

So we had to make a video, I suppose we could have done it weeks ago but even though it's one of the challenges, somehow it doesn't feel like it. This blog has been going since last September, but even so, it still feels more real. 

Two of us got together in the kitchen with an old camera (well, old for modern times, it was still digital!!!)  and with a basic script took turns to operate the camera and do some impromptu words about Zyderbot. We aren't natural publicists so we're a bit awkward, but it's done.

The video became an explanation of some of the key points, with added picture within picture to provide voice over explanations of key points, this picture showing the emergency fuse to prevent magic smoke emissions.

While it's a competition and we want to compete in all the challenges, we have to enjoy doing it, and the real competition is solving the puzzles we're given. The rest of the pictures here are all from the video of some things we've learnt.

Nerf guns and Stepper motors

Being geeks we had nerf guns, but adapting the mechanism for use in PiWars turned out to have a range of issues. But here it is in all its chaos. Eventually all that is used from the gun is the flywheel acceleration module, and the dart magazine.

We had some fun with the aim of the gun, and have fitted a recycled barrel to increase accuracy. The barrel was originally a croquet mallet handle, which then became a battery holder in a previous Zyderbot iteration, and now a nerf gun barrel. You can just see a cat toy laser clipped on underneath.

The flywheel module of the original gun was easily unscrewed and was easy to remount.

The trigger mechanism wasn't so easily recreated and we ended up using a stepper motor to push the darts into the flywheels. 

Lesson learnt, do not power stepper motors continuously when not in use. So it was left powered on, heated up and shortly the plastic mount for it melted. Replaced with a metal mount and a change to code in a float state when not actually in use.

Magnets

We use a lot of magnets for quick assembly and disassembly of Zyderbot between challenges. Here is the main arm which is reused between the Eco-Disaster and Zombie Apocalypse challenges. The base is attached to the robot rear using a pair of magnets at each corner which gives a very secure base.

 

Four magnets on the arm allow for holding the zombie gun and barrel handling attachments

Four on the attachment line up 

And fully assembled with four matching magnets it's a secure joint.

The nerf gun similarly has four matching magnets

And so has a very secure platform.

Lesson learnt. You don't need four matching magnets for everything. The magnets are strong enough to hold using just a metal washer on one side and magnet on the other. We fitted four pairs to the battery box and now need a crowbar to get it open. They're also not always cheap so it costs twice as much!

Barrel Handler

One of the things we want to avoid in Eco-Disaster is to have barrels rolling around the arena. Partly because they'll be difficult to get into the end zones, and also because they'll potentially get caught under Zyderbot and need a rescue. 

Consequently, last minute mods to the barrel handler to add a plough to push barrels away that accidentally get in the way. This means not lifting the barrels very high, but then also not having to worry about dropping them on another barrel, though stacking them would be an interesting challenge (a la toys). We've also fitted a rear bumper to do the same thing.

Configuration

Zyderbot has a set of 8 dip switches on the rear which allow easy configuration between challenges.

Also shown in the picture is the battery monitor display, the rear light and the stop/start button. The rear light also doubles as an information display. For the Pi-Noon challenge we'll be covering this with a magnetically attached plate to protect the settings!!!!

Ultrasonic sensor

Lots of us will recognise a HC-SR04 ultrasonic sensor, so we couldn't miss one off, it's very easy to use and adds a bit more of a feature than a 5mm square laser sensor on pcb, though we're using one of those as well!!! Might come in for barrel detection as well.

Lighting

We have very little idea of what the lighting will be like on the actual day and most of our testing has been done in very variable conditions, so having a pair of headlights on the robot helps a lot in colour and line detection.

It's also part of the robots image, we can't have a lightbar because of the attachments but these will work well.

Might actually do a blog of the weekend but we'll see how excited we are :) 

Well that's this bit done, just the competition itself, then back to building and demonstrating other robots, but I'm sure we'll find a place for Zyderbot!

Tuning!

 Tuning!

So we build solutions, they should work, and then the real world gets in the way. 

Lava Palaver progress

We'd gone for a camera sensor for the Lava Palaver challenge, not because it was a better option for following a line, but because it was automatically immune to the hump in the course. However, this threw up new issues. The competition course is 7m long and painted black, the only surface available for testing is a light wooden floor which makes for very poor contrast.

 Early testing was plagued with phantom readings from reflections which confused the robot, so testing moved to using a black line instead, with the intention of switching over to white for the competition day. This was much more successful, but space is a limit again. To make a test worthwhile, we're going to have to go for a bigger course outside, using a long roll of black art paper with white electrical tape down the middle and hope for dull days!

Illumination was oddly a very important feature. Off the shelf line follower attachments tend to be IR sensor based and have built in illumination which tends not to be noticed, but for the camera, even illumination is essential to get good contrast for the line, so the robots headlights have to be used to light up the track ahead, together with an overhead light illuminating from above. 

The result is a fairly simple bit of code at the end, but beneath it is a lot background code doing the heavy lifting and interfacing. 

One of the items outdoor testing might help with is coping with bright sunlight and shadow. Watching the competition from previous years, it's obvious that this can have a detrimental impact on robots using optical sensors so we'll be looking at that. It's hasn't been done yet but we'll be experimenting with a sunshade for the robot to give more even lighting for the camera and hopefully reduce errors.

Zombie Shooting

For the Zombie Apocalypse, we've had an idea to use a butchered standard nerf gun which looked very promising out in bits on a table, see an earlier blog post, but we discovered a weakness. Using the servo method of pushing the nerf pellet into the gun worked a lot of the time, but then would jam the gun requiring it to be dismantled to clear the jam, it wasn't suitable for the competition. This held us up for quite a while but an obtuse solution using a stepper motor and a rotating cam came to the rescue, so now we're back in business.

The video shows the cam operating and firing off a magazine of pellets. We then got a cat laser toy and pressed it into service to help with aiming, now how many competitors will be aiming at butterflies?

As the video shows, the gun fires to the left, a bit more work to do but on our way.:) 

Minesweeper

Again, this is one we had a solution to some time ago, but when we come to use it, there's a surprise for us. We're using an overhead camera, but processing the image in memory leaves off a lot of the arena, a 'feature' of the camera.

 The image was always going to be distorted but missing bits is a problem we haven't time to overcome, we'll just have to code round it. This means that the robot will have to search for the red square sometimes instead of just being able to see it and move to it. 

The algorithm for this will be basic, something like the following.

Just how accurate the movement will be isn't known, we were expecting to just move to the red square wherever it was, but this now requires some idea of where the centre of the arena is. Only testing will tell. We're doing this challenge on mecanum wheels. As the arena is 4 x 4 matrix, all red squares will be within it and so a map can be built of the arena based on squares that have already been red. Will this be good enough for the minimum 20 moves required we'll have to see. Anyway, signing off with an errant robot which finds it's square, and then ignores it, ho hum.

 

Days tick by......

 With less than a month to go it seems we have lots of solutions which are all but ready to go. Line followers that can see lines but can they drive seven metres in a straight line? Square finders that can see the squares, but can they drive to one and then the next? All will be revealed on the 21st April in Cambridge but for now here's some progress.

The Lava Palaver line detector works well but instead of a fixed mount, needed a bit of adjustment so has now been given an articulated mount.

This has been 3D printed to be integral with the magnet attached battery box cover. More magnets have been deployed to the rear part of the robot for quick change attachments for shooting zombies and collecting barrels.

It's great to see the layout before dozens of wires obscure the view!!!! More uses for magnets has been found in adjusting the barrel handler. 

This also makes it quicker and easier to change the types of attachment to see which works best. 

This is our barrel handler in serious searchlight mode. It obviously works but needs a bit more software behind it to get barrels to their destination. 

More on this to come. 

The Escape Route challenge still needs a bit of work, but we're working from an old formula so it's more tidying up than new development. To get cleaner lines on the robot we've hidden a VL53 laser range finder inside one of the cab windows, along with IR sensors on the sides and an ultrasonic sensor on the front of the robot.

When not in use we'll be closing the window with bluetack!!!!

First experiments with the sensors aren't perfect, as the following video shows.

But after a bit of tuning and building a test course, it's starting to look the part.

 

This is our goth themed video selection but we just need to get this running a bit more smoothly.

 We've had a solution for Minesweeper for sometime, but we've only just now got round to fitting it to the robot. 

It's an overhead gantry mounted camera which reports an XY co-ordinate of the red illuminated square on demand from the robot. The robot will be running on mecanum wheels for this challenge and the gantry is adjustable to keep the robot within the height limit of 450mm. Navigation is all relative to the red square, so, see a red square and drive to it!! To reduce the impact of the gantry on the image, 4mm black carbon fibre rods have been used for support. Also in the picture is the carry handle for the robot, to make handling easier and safer. A better view here.

With a variety of configurations needed for the competition day, a new control panel is being created for the rear of the robot which will allow the robots Pi to be quickly switched between challenge modes, as well as a battery monitor and a start/stop button. To make sure we've got everything covered for each challenge configuration, we've started a checklist, I'm sure it'll get longer soon!!! Here's where it is now.

Challenge: Lava Palaver

• Wheels: 105mm
• Bonnet: Line Detector
• Back cover: Plain
• Attachment name: LINES

Challenge: Zombie Apocalypse

• Wheels: 70mm
• Bonnet: Plain
• Back cover: Nerf Gun
• Attachment name: ZOMBI

Challenge: Eco-Disaster

• Wheels: 70mm
• Bonnet: ???Not yet determined???
• Back cover: Barrel Picker
• Attachment name: ECODI

Challenge: Minesweeper

• Wheels: Mecanum
• Bonnet: Plain
• Back cover: Camera Gantry
• Attachment name: MINES

Challenge: Escape Route

• Wheels: 70mm
• Bonnet: Ultrasonic detector
• Back cover: Plain
• Attachment name: None

Challenge: Pi Noon

• Wheels: Mecanum
• Bonnet: Balloon attachment
• Back cover: Plain
• Attachment name: RC

Challenge: Temple of Doom

• Wheels: 105mm
• Bonnet: Plain
• Back cover: Plain
• Attachment name: RC

Next time we hope to have more demonstration videos of being fully ready for all challenges.....but then again maybe not!!!!

Escape Route - PiWars 2024

    This challenge is a zig zag course through coloured barriers described here Escape Route – Pi Wars.

    It's described as a maze but really there aren't any alternative routes other than to the end so it isn't really. The picture above is a mock up just to test general algorithms of following a similar course made of blocks that just happened to be made up for our robot workshop this year. The course can be run up to three times in five minutes with points for each run and fastest run.

    There are three methods allowed, fully autonomous, which I'm certain we'll be aiming at (a basic video of this in a later blog), blind remote control (with again a video later) and remote control with relayed commands, where the 'driver' can't see the robot or route and has the necessary directions given to them by someone else who can, and 'call and response', where the robot is remote controlled by a person being given instructions from a second person, only the second person being able to see the course and robot position.

    Autonomous is what it is, but for remote control then the communications must be rock solid in what will otherwise be a very noisy environment electrically. This may also adversely affect the video link which most likely will be over wi-fi. As the remote control and 'call and response' both require good communications be essential for control, using a dedicated RC system or a Bluetooth controller might be the best option. Video streaming over Wi-Fi is well supported, but if not practical or reliable on the day, then at least the RC will be. Video is the described navigation choice for 'Remote Control', but a feed of data from, say, a collision detector might help enormously.

    From a points perspective, completing the run scores 200 each time, or 600 for 3 completions. Not touching the walls scores an additional 100 points per run, so 900 in total for thee clean runs. For just taking on the course autonomously, 350 points are awarded, so even if your robot isn't up to it, entering autonomously and just crashing without completing any runs should be fine for some points!!! Remote control entrants get 250 points extra and 'call and response' entrants an extra 100 points. There are no points penalties for crashing/recovery etc, but the fastest robots are awarded points based on the formula system described here Formula Scoring System – Pi Wars. Thus, three clean complete runs autonomously scores 1250 with a potential extra 150 for fastest meaning a total of 1400 available. Competently doing call and response will earn a team 1000 points, plus any formula points for speed, but at least 70%. Getting this right means that a robot can do very well and any attempt at autonomous operation or 'remote control' could be abandoned closer to the day with good results. 

    There are coloured walls, but their colour won't be of much use to a robot unless someone is determined to be fastest. As with lava palaver, a fixed set of navigation routines could be coded to do the basic steering with additional collision avoidance added. A basic routine set might be:

• Drive_forward_until_wall_10cm_away
• Turn_90degrees_Right 
• Drive_forward_until_wall_10cm_away
• Turn_90degrees_Right
• Drive_forward_until_wall_10cm_away
• Turn_90degrees_Left
• Drive_forward_until_wall_10cm_away 
• Turn_90degrees_Left
• Drive_forward_until_wall_10cm_away
• Turn_90degrees_Right
• Drive_forward _until_wall_10cm_away  (a hand placed in front when collecting robot at end)
• Stop

This would give the following route.

    Driving forward in a straight line might be the bigger challenge, and putting a limit at 10cm is just an example guess, any robot needs to be tested to verify it's turning capability and as the measurements of the course are known, the turning trigger distance might be much more on horizontal runs. This is also reliant on dead reckoning but the course isn't complex so fine tuning a robots steering should get close.

    The above might get  a reliable result, but to get the fastest time will require a more irregular route. The obstacles on the course have a different width as well as colour, so a determined robot could steer a course based on knowing and using this information, as well as using some additional wall following sensors, possibly already installed for lava palaver.

    Only a team can decide how much they want to be fastest, but getting the basics right will do very well and this example route above might be close to the route of the fastest robot and 1400 points. Getting the scripted run right would be 1250 points, almost 90% of the max.

    Finally, a robot recording it's successful runs could replay them at a faster pace to get that extra speed and points. 

    So now there's a few routines to write and videos to make, as well as looking at the Minesweeper challenge.