Didn't get in

 

Failed to get into PiWars 2024, guess there's lots of strong advanced entries, but we've been put on the reserve list which will be a bit odd. If we were a school team it would be easier as it would be a project, but creating a blog and video for a competition you probably won't be in will be a bit different.

Anyway, we may continue for a while. 

Three of us met to discuss Sidmouth Science week and inevitably we started discussing PiWars. Much fun was had experimenting with arms for sorting toxic waste barrels and a Nerf gun for shooting Zombies. Despite not getting in, we're already doing well at having solutions to the challenges and even measured out an area of kitchen for a test arena, though we have to move the table and chairs out first!

An analysis of the challenges has already been done, so they'll be written up over the next few days and published in the hope they're useful to everyone else.

PiWars 2024 Entry

 

We're entering PiWars 2024!

So our entry submission is done, we're the 377th submission apparently but we did come 4th in the Advanced category in 2022 so hope that stands us in good stead this time round. 

We aren't going to reinvent our working and constructed robots, they were a good all round design last time but we've learnt a lot about control and solving challenges so are looking forward to getting stuck into these. 

These are are two prototypes and probably won't change much.

These have been modified since the end of PiWars 2022 to change to a standard RC controller, we'll retain the mounting system, and the electronics for now.

So we'll have to wait to see if we get a place in the competition, here's hoping.

And our certificate!!!!

Doesn't say 'could do better' but next time!!!!

 

All bar one

 Final blog entry for this year. We got four videos created, and the blog, but failed on the Natures Bounty video.

Most of a sophisticated apple picker was built, but not enough to be ready for using in a videoed challenge.

We did try to rustle up an alternative in the last few hours which basically knocked the apples off but time just ran out, and we concentrated on delivering what we could do. Disappointing, but our first try at the competition and we've learnt a bit in the process. 

It'll be fun seeing what everyone else has done, but not sure we'll get away with doing it again, just a bit to much time.

Still, next up is Sidmouth Science festival, when we'll have a lot more robots wandering about. Think that's where we came in!!!!

East Devon Pirates

Videos

 Just a brief post to show our video recording area....it's actually a bedroom with the arena laid on top of the bed.

We moved here from the kitchen floor due to other people needing to use the kitchen for space and we can use this all day without being trodden on!!!

The camera is mounted on a tripod to the right and to the left is a table to sit with laptop for robot set up, in this case with the next variation on out sheep herder, in this case a very much more 'beefed up' version made up from recycled robot arms.....and Lego!

A farmyard tour

 From the beginning we'd had lots of ideas, but the practicality of most of them, while not beyond us, meant that just getting on and making a video was more time important. The venue was to be a garden, giving us three different surfaces very quickly, grass gravel and paving. Obstacles are easy to find, but they have to be ones which the robot can negotiate, so small steps are ok, garden tools etc. 

One thing we didn't have was something which would mean the robot would be able to climb higher than itself, so as the garden was hosting us, we decided to make something for the garden and constructed a bridge over the garden pond, "The Bridge of Pi's" out of reclaimed pallet wood. 

Not very 'robot like', but just the practicalities of making an interesting course. :)

Similarly, we needed a obstacle which the robot would have to manipulate before continuing, so for our video, we made a 'kissing gate', something which is very common on farmland to provide a pedestrian gate which can't be negotiated by animals but doesn't require closing. 

Again, reclaimed wood is used to build a simple and portable obstacle.

The robot enters via one side, moves the 'gate' to the other and then drives out. In practice the driving in proved to be the biggest problem!!!!

The rest of the challenge is populated with farm characters/animals and a few signs to give a 'tour' feel. The following pictures just give an idea of what it looked like and some of the features.

This is a view of the garden we were fortunate to use, driving round it twice used up our 5 minute video allowance! It had gravel, grass and paving to give us the required three surfaces, though in the end it had several more!!!

The video is linked here......East Devon PIrates

Starting from the beginning.....

The ticket office....

Mine host....sings Old MacDonald....

The Sheep Dip Seesaw....

Robot Restaurant...and for anyone who might recognise it, Hitchhikers Guide references.

Hungry Cattle Cafe.....most of the rice eaten

The Troll Bridge......

...and a better view

The Lamb Joint......

 Wolf Hall......

The World's Simplest Maze....

And for Indiana Jones fans.....see the video for how this worked out!!!!

Finally, a picture of the gardens owner sunbathing !!!!!

Zyderbot Architecture

 Zyderbot is very modular and the parts have been assembled to work together around ideas put in place early on in the competition. This is a brief overview of what it comprises. 

The central chassis, as described in previous blogs. houses the controller Raspberry Pi and it is this which forms the central control and communication hub of the robot. 

A VNC connection to this Pi is used to connect to it from a laptop and programming is done using the Python IDE or Thonny. The controller Pi also runs the camera, support for which is built into the Pi.

The rest of the robot platform is modularised to provide dedicated functions, there are two groups, the main chassis controllers and the attachment controllers. As this is our first entry into PiWars, we've designed something which is reusable and the design and code is on Github. 

The main controller runs a command queue, onto which commands can be placed, either from an onboard file, as running a script, from the command line as direct input, or as a response from a separate controller, which in this case is either a Pico or an ESP32.

For autonomous processing, the controller reads a script file and runs commands to either take actions or invoke further autonomous actions, such as running a trough filling hopper or picking an apple. 

A motion command will be sent to the Motor Controller Pico which measures distance and actuates the four chassis motors. 

For Remote Control operation, an ESP32 is used with a PS3 handheld controller to submit commands to the controller, which are passed onto the Motor Controller, providing the necessary control.

For audio input, a separate Pico is used to listen on a microphone, interpret the audio signals it receives, and then pass these on to the command queue.

The Camera is invoked by commands to enable seeking and following operations, itself issuing commands back to the queue to act on received information.

The attachment controllers are there to enable easy integration between the chassis and the attachments, running all the attachment motors, servos and sensors so relieving the main controller of that burden and providing a division of labour.

For each PiWars challenge, an attachment is provided, to a standard mounting specification, power supplied from the batteries as a nominal 12V and communication to the Pi controller is over USB, which also supplies controller power an enables coding on the attachment controller from the central Pi.

There's a lot of code around this, as well as some direct handshake signals to get the timing right, but it's a good platform to take forward into future projects and competitions.

Toot Toot

 There's a bit of Shepherds Pi and the Farmyard Tour that gives points for audio control, so this is our take on it. This doesn't do much, listens for a whistle and then provides basic interpretation into commands. One whistle 'toot' is a command, as well as two and three, and after a brief interlude, the last command is cancelled. 

For this, a Pi pico is paired with a microphone....and a whistle...feeding the ADC of the pico with the audio signal, and then running an FFT against the signal to pick out the whistles' frequency, 2k7Hz in this case and converts blasts it into a logic signal.

As with the other attachments, this supports the WHOU enquiry, GPIO handshake and returns the info of TOOT, TOO2 and TOO3 as commands.  Power and serial comms are via USB for easy attachment.

Seems a bit of a small post, but it's a complete sub-project that contributes.

Using the remote

 With lots of challenging challenges, it has felt easy to ignore that the Farmyard Tours was to be remote control and not autonomous, so we needed a solution which was a bit more dextrous than a keyboard. Using a full RC set with adapters was always an option, but a more personal system was preferred and an almost universal games controller format was chosen. 

Could have been any brand, but it turned out as a low cost PS3 controller from a no-name Chinese source. As the main Pi controller just wanted a data feed it could translate, the interface chosen to the controller was Bluetooth run by a small ESP32 module dedicated to the communication. This was a lot less bother than direct comms and meant that the controller Pi wasn't cluttered with noisy code. Here is a larger dev board for testing, and mounted on a test chassis. The communication is via serial over USB and a simple handshaking option is used to request data from the PS3. 

One of the issues with this configuration is that when the controller times out and disconnects, the ESP32 code can't reconnect, so an extra pin was dedicated to reboot the ESP32 into connection mode again. 

Here's a brief video of the test chassis twirling in the arena..........and negotiating a bit of garden.

....and negotiating a bit of garden.

A new chassis

So after lots of testing....well a bit anyway...we needed to build a new chassis, if only because we'd drilled so many holes in the old one! 

First make the battery holder which is also part of the suspension. Here it is.

Well that's spectacular isn't it. It's very basic, is made from a piece of acrylic tube, one end has a fixed plastic plug with a battery contact permanently attached and the other has a plastic spring holding the other contact in, which is held in place with a screw. The tube itself forms the central pivot of the suspension.

The two halves of the chassis were updated to accommodate the positioning of the camera as well as the main controller and attachment processors.

This is the rear subframe from below, the motors fixed in place either side of a tunnel which houses the battery tube. 

And a picture of the front subframe, housing motors, a camera and illumination LEDs, with the second half of the battery tunnel shown.

Putting them together, with an empty tube in the middle. The two subframes can rotate independently of each other around the battery tube. This isn't of much use in the arena challenges, but when negotiating the farm tour obstacle course it's expected to come into its own to keep the chassis stable and in contact with the ground.

As mentioned previously, part of the rebuild was to accommodate a camera.

The camera is mounted below the attachment deck of the chassis, the bolt holes for attachments can be see top left and right, and faces down and forward, looking at the arena surface ahead of the robot. The LEDs are there to ensure it has plenty of illumination for the camera and isn't dependent on ambient light, eliminating an uncertain variable.

Close-up of the two subframes partly rotated against each other to show the suspension in operation. Already, with only the motor, LEDs and camera fitted there are a lot of wires in this robot and cable management is important, hence the prepared holes in the subframes.

From the outset we wanted interchangeable wheels to adapt to the different challenges. These are 'arena' wheels with their adapters. The adapters were always part of the design as with so many different motor shaft attachments available we needed to be able to switch them without having to remake whole wheels.

Now it looks a lot more like something with the wheels attached and wires routed. The front chassis  mounts for attachments can be seen, and that growing wiring is getting some management..

And suddenly there's a wire explosion!!! At the rear (right) is the main power switch, and just ahead is the controller pi board mounted vertically. At the far side is the power regulator. Raw power from the batteries is delivered at around 11V and used by the attachments, the regulator ensures the pi is supplied with a healthy 5V. 

Nearest the camera is the motor control pico which receives commands from the controller and incorporates a LED to provide a simple status display. This connects to the controller via USB. 

And here is the assembled new chassis with the Hungry Cattle hopper attachment. 

There's a lot of parts to this but it does work very well. Only a short video of this chassis working but it gives an idea of the basics.

Next up a  blog giving a description of the architecture of these robots.