eChook Nano v1.2: New Boards, and, Building your board!

We have a new batch of PCBs, issue fixed. The Greenpower teams who ordered the last one have already had the new boards, and we can now send out new kits. To help with the build process I have just posted a video showing how to put together your eChook Nano v1.2 board.

Since the first prototype we’ve answered lots of questions through email and messages, and always wanted these to be more public so they could help others with the same or similar questions – something like a forum! Since the GP forum is unfortunately closing, it seems even more relevant to have somewhere to discuss all thing eChook and help each other out with anything from building the boards to analysing that spreadsheet full of data. So for further discussions, we’ve set up It’s a little empty right now but I’m sure we can start filling it up.

We will also be writing articles for Greenpowers new ‘How To’ section, both eChook specific, and more general ways of using an arduino with your car, so hopefully the eChook forum won’t detract anything from the greenpower site.



eChook Nano – and the disappointing PCB manufacturing

Disappointingly we are having some issues with some of the boards from our first stack of eChook Nano v1.1’s. So far the quality of boards (v1 and other projects I have worked on) from has been great, their cheap and fast service always delivering good quality boards without issue for my needs.

I was initially a little displeased when I received this latest batch, 12 eChook Nano boards, the first kit board we would send out for schools to test. I had hoped the schools would mostly be testing our documentation not our board quality!

The registration of the silk screen is quite poor. This means that the silk (black lettering/numbering) was not nicely centred on around the components. While this is annoying and leads to a less professional looking product I didn’t think of this as a major concern as it would not impact functionality and the board that was put together showed no signs of any issues and passed all of our tests.

Looking in more detail at some of the other boards received (work have recently purchased a microscope for my lab) I noticed that it wasn’t just the silkscreen that wasn’t on centre. The pictures below show the extent of the problem quite well, with the plated pad area (shiny metal) clearly not centred in the area where the solder resist should be removed (the black area). The solder resist on these boards is the white stuff on top, this resists solder and makes a PCB much easier to solder together as it will stop the solder flowing, in our case down the tracks and potentially in to other components. Specifically here, because the board has a large ground plane pour, it will prevent a solder bridge of the PCB pad to the ground plane as the ground plane is hidden below this protective white layer of resist.  This is important as (for all track apart from the ground pads), a short to ground will result in either incorrect readings of the sensor data, or worse, a damaged PCB.



Unfortunately…this hasn’t happened in this case. You can see in this lower image the tip of my multimeter probe, just skirting the edge of the solder resist. In this case I am checking around the 12V battery pin. Around the very edge of the white region I was finding my multimeter continuity test was  showing this region as connected to ground, not good. This means that the ground plane is slightly showing through the solder resist. If I were to solder this pin it is likely that this would be bridged and cause a short between the 12V input and ground.

Can this all be blamed on the manufacturer of the PCB? Simple answer, no! Although the offset here has resulted in an issue I (as the PCB designer) could have taken steps to reduce the likelihood of this occurring. What I now realised I should have done is reduce the size of the area that is removed for the solder mask, effectively making the solder mask (white stuff) bigger and closer to the plated pad (a smaller black area). Doing this without changing the clearance of the pad area to the ground plan, this would have the effect of covering up a larger amount of the ground plane so even when the registration is poor between these parts of the PCB it is less likely to leave exposed ground plane showing.

An annoying blog post to have to write but a valuable lesson either way and certainly something that has added to my learning of the finer details of PCB design. The team will be modifying the gerbers and getting some new boards in to rectify this issue as soon as possible so we can get the kits out there!

eChook Nano Kits are finally here!

We’ve finally got our (hopefully) final prototype boards together! The eChook Nano v1.1


These boards have a different layout, different DC-DC Voltage regulator with short circuit protection and reverse polarity protection, a lower component count and design changes to make them easier to solder. We have also differentiated the power connector to all the rest so that it is far harder to accidentally fry the Arduino! The functionality remains the same as the original prototype boards.

Thank you very much to the teams who gave us feedback on the initial boards 🙂

We are also re-organising and re-writing a lot of the documentation to make it easier to follow. The build instructions for the eChook board are complete, I’m currently writing up the section on connecting the board to the car and instrumenting the car.

We are providing these eChook boards in kit form, for students to build and program. All instructions are provided in the documentation. We’re still selling them for £25 posted for the kit shown below. You will need to purchase the LEM HAIS 50-p current sensor(~£18) separately. This is cost price – we’re not aiming to make a profit.

*Kit Photo missing a diode and length or ribbon cable that are also included.

Alternatively if you are lucky enough to have PCB making facilities, all the files are hosted at and you can make your own 🙂

weChook Racing: Electric 3Galoo Build Log – Lessons Learnt

In case you haven’t worked out from the lack of us being at races so far this year, 3galoo has not been progressing smoothly.

We’ve had numerous problems with the wheels and driveshafts at the rear of the car, and I thought it’d be a good idea to record what we’ve learnt so that other teams out there don’t repeat the same mistakes.

Without further ado:

Bearing Fits

We had the hubs and bearing spacers for the wheels machined by a local engineering shop. Having checked my drawings with one of the technical specialists at work, I had good confidence that the drawings were correct, and most importantly, correctly toleranced.

Sadly, the parts we received back were not up to scratch. The recesses within the hubs for the bearings were too small for us to fit the bearing, although not by an amount that we could measure with a set of calipers. It wasn’t until I sent the parts to my friendly technical specialist that we realised that they were less than 1/10th of a mm too small – this was enough to completely prevent us from fitting the bearing.

Foolishly, we wrecked one hub by trying to turn out the extra hundredths of a mm with our bench lathe which really was not up to the job – we went from not being able to fit the bearing, to it falling immediately back out.

This all put a massive damper on progress, and enthusiasm – as the first thing that we’ve not done ourselves, for it to go this poorly was a bit of an eye opener. We know for next time – make sure our tolerancing is documented properly, make sure the person doing the machining understands and agrees what is required of them, and if possible, get the bearings to them that you want to fit!

Shaft diameters

Our next problem was with the shaft that we bought to use as the rear axles. To our calipers, the shaft we bought was a constant 18mm diameter the whole way along, so we couldn’t understand why it would only fit part of the way through the holes that we needed it to, and why it slopped around at other points.

Again, a measurement with a higher resolution tool showed us that the shaft was definitely not a constant diameter along its entire length. We were advised to instead purchase Cold rolled bright mild steel, which has a much more consistent outer diameter, and has really reduced the amount of wobbliness at the back of the car.

From this we learnt how much difference an imperceptible change in diameter can make, and therefore the importance of using the right materials.

Tolerance Stack up

The design we came up with introduced a lot more ‘critical tolerances’ than it needed to, meaning that many dimensions on many parts needed to be machined perfectly for the design as a whole to work.

The redesign at the rear end used a shaft that we knew would fit well into the I/D of the bearing with no further work, reducing the number of ‘critical characteristics’ by two.

This approach of designing to minimise the ‘critical characteristics’ of any given part makes the entire system more robust, and easier to manufacture, which is a big win!

Hopefully this has been of some use to someone who’s looking at building their own car!

Project eChook Nano: First test success!

A fantastic day at Rockingham saw the weChook racing team manage to run an echook nano for 2 hours on our car Electric 2Galoo. Thanks to all who came to speak to us on the day about the car, as always it’s a pleasure to talk to like minded people who just love to build race cars!

We had great success with out 2 hour test using the echook board both as a motor controller driver board as well as a telemetry data logger. The phone screen was used to inform me (the driver) how much current we were drawing and was perfect for testing our race strategy plans. We also managed to collect 2 hours of good data from our sensors, result!

David @cullimoreracing has kindly offered to run an eChook Nano on Jet2 but we will be looking for more test cars to get these boards on to for the start of the season. Before we do do this we need to tidy up our documentation and work out how we are going to fund the project at this point (the boards are cheap but with components the cost is looking to be ~£30 before you add on the £17 current sensor…we aren’t trying to make any money from this project but we are also not trying to lose too much, we have racecars to build!). We have 9 more boards from this initial batch, watch this space for what we plan to do with them….

Here’s a video describing the main board features

weChook Racing: Rockingham Season Opener 2016

Having skipped out on the Goodwood Test this year (for a few reasons really – we hadn’t finished making anything yet, and Goodwood is a less important circuit to get right these days due to the relocation of the final), 2016 opened for weChook Racing with the season opener at Rockingham.

For those that don’t know, the Season Opener has traditionally consisted of an extended test session in the morning (over three hours this year) followed by two F24 format races in the afternoon. This means an 80 minute race with 2 mandatory driver changes – a slight problem for us!

We’d been pretty lazy in the off season – 2galoo had been put in storage after the 2015 International Final, and had barely been touched since. We did a few quick checks on Tuesday evening (we pumped up the tyres!) before tossing it on the roof and strapping it down.

We drove to Rockingham on Wednesday morning, and after bumping into everyone’s favourite commentator on the road, we arrived just in time to join the start of the scruiteneering queue. 2galoo flew through the checks – including the new impact foam regulations that had caught out a number of teams at the Goodwood test –  and received its MOT sticker, giving us plenty of time to get out on circuit.


We had two major objectives for the test – the first was to try out the eChook Nano (read about it here), the bluetooth data logging and telemetry system that we have co-developed with Driven. Our second objective was to extend our understanding on how to use our gearing to maximise race efficiency.

We hit the circuit early in the session and completed 12 laps. Ian drove the first few laps in ‘constant current’ control mode, using the gearing to keep the current as close as possible to 25 Amps. Afterwards, we switched the strategy to run consecutive laps in each gear. The eChook worked admirably, until the phone used to log the collected data fell off the dash into the depths of the car and dropped its connection.


After completing the first planned stint, Ian bought the car back in for a few checks – we were particularly interested in the motor temperature after running a few laps in high gears with high current consumption. Thankfully, the temperature weren’t too high, although this doesn’t mean it wouldn’t start cooking if we ran a whole race at those speeds!

Having realised we weren’t collecting any data from the first stint, we decided to send the car back out in the last 30 minutes of the session. A quick battery change later, and 2galoo was back out on circuit, fitting in another 10 laps. I’ll be writing a separate blog post on the data we collected later on.

 Still DecoratedLined upOn track
After a quick break, it was time for the first of the season opening races. As alluded – we had didn’t have enough drivers to actually compete in an F24 format event, so we used the race as another test session. We followed a similar pattern as we did in the morning, a few constant current laps followed by a lap in each of the gears. This consumed far more current than we would normally do during a race, so Ian retired the car after about 50 minutes and 16 laps when the voltage got a bit low, in order to protect our best set of batteries. We matched the fastest lap that we achieved during the international final weekend and had got up up to 2nd place at one point.

After the first race we’d done all of the testing we needed to do, and collected a lot of good data, so we elected not to run in the second race. We had a great day overall, the weather was great and 2galoo ran smoothly and reliably – a fitting sign off after what is likely to be the car’s final event.

This feels like a return to normality after the end of the 2015 season – Congratulations to Dave (and the newly extended Cullimore Racing team) for a pair of victories – Jet II really is the real deal and the design work that has gone into it is the inspiration behind what we’re doing with 3galoo.

The newly arrived Bluebird looked highly impressive – I’m sure it will be a threat in whichever class it ends up entering! The rebranded Minion/ Scooby Too looked very impressive, and completed a whole lot of laps in practice. Probation IV showed up with a new and dapper set of orange bodywork, that looked just a bit like a boat.

Probation IV

Thanks to the GP staff for another cracking event! We’re looking forward to the next race, and to joining them at STEMtech in June.

Now we just need to finish 3galoo before the Goodwood heat!

weChook Racing: Electric 3Galoo Build Log – Building the ‘mono-coffin’, getting gluey

Now that all our panels were ready we are ready to start gluing the driver cell together. The important part here appears to be ensuring that you get as large a contact area as possible. The tabs on our design increase our contact surface for a start. We can further improve the bond of the chassis by ensuring that the panels pull together as tightly as possible to minimise the gaps between them and ensure the epoxy we are using can do it’s job. To achieve this we have found that ordinary wood screws actually work really well in to the dense Divinycell H80, even better than the Rohacell we had previously used in 2galoo’s design. We put washers (and when I ran out of washers all number of metal spreading plates we could find!) on the heads of the screws which helps spread the load and not crush the foam.

We have used a fast curing epoxy for this so that hopefully we can apply our fibreglass to the outside of the driver cell later in the day.

Matt uses a pound shop paint bursh to apply epoxy to the panels before slotting the jig saw together. While he does this I screw the panels together to squeeze out any gaps. Where I can I use proper clamps to pull the car in to shape.


We had a little spare epoxy left over at the end of the session so rather than wasting it we decided to add some strengthening corner pieces. These were quickly cut on the bandsaw and have been placed in areas of the driver cell where we feel a little more strength may be beneficial but won’t get in the way of the driver. These pieces will increase our bond surface area and for the additional weight of them (tiny!) we think they are worth using.

Next up, glassing the outside of the driver cell.

weChook Racing: Electric 3Galoo Build Log – Building the ‘mono-coffin’ continued

Success, a second blog post about actually building the car, perhaps we are on a roll….

Last night Matt and I got home from work and cracked on prepping our Divinycell panels for gluing. Matt cracked on with a file and some sand paper to neaten some of the edges that we would be bonding to. While he was doing this I got to work building a simple router planer machine.

We needed to be trim the floor pieces down from 20mm thickness to 15mm, and the front panel would need to be 10mm. We have tried in the past using a home made hot wire to cut the foam in large sections however, doing such wide panels results in the wire deflecting a lot inside the foam which means we often end up with a wave like pattern in our foam, not ideal for keeping a nice flat floor! The router planer would remove/destroy more material than the hot wire method, but this wouldn’t matter as we are only removing a small amount.

Hopefully it is obvious how this machine works from the pictures above, it was very simple to make and would be a fantastic DT project in a school. The router sits in a rail which gives us our X axis slide. The Y slide is purely done by manually pushing the panels through the tool. Z axis is set by plunging the router down and setting it’s height stop in order to remove the desired amount of material. The important thing is to not push down on the router too much as it may flex the MDF frame and cause a deeper cut than you want. This unit didn’t take long to make and worked perfectly for our purpose.

Pushing the panel in from one end I then move the router across, removing 1 router bits worth of material per stroke. 10mins and ALOT of foam mess later (have a shop vac and dust mask to hand here!) and the panel is trimmed. A quick pass with some sandpaper and we have a panel that is thinner and ready for bonding to the rest of the chassis.

Now that the panels are the correct size and thickness Matt is able to throw them together as seen here. Next up, gluing the chassis together.

weChook Racing: Electric 3Galoo Build Log – Building the ‘mono-coffin’

Welcome to the ‘build log’ of Electric 3Galoo, Matt and I have always thought about showing the build process of one of our cars but a rushed build has always taken priority over documenting it. Perhaps that will happen this time as well….who knows, we will try to keep this updated as best we can!

One of the things we really liked about 2Galoo’s design was the use of a fibreglass reinforced foam driver cell. Some of the reasons we like this build method are:

  • Strong enough to bolt front and rear subframes to without additional framework
  • Immediately meets the requirements for keeping the driver safe in the event of a crash, without the need for bodywork providing any additional crash protection, this leaves our options open regarding a how we make our bodyshell
  • Lightweight
  • Cheap (the rohacell panels that made up the last car was free from a skip!), we got an incredible deal on the Divinycell we are using for this build
  • Easy! It really is, as long as you don’t mind the possible mess of epoxy resin the foam is easy to cut and shape to your desired form. You can then test and add to it as required to ensure things like your batteries fit in and your driver is comfy before then sealing the structure solid with fibreglass.

We are going to approach this build in a slightly different way. Build the entire drive cell first and fibreglass it then add our subframes and other components afterwards. It was very messy in the last build trying to glass in the steel subframes and we think we ended up with an overall weaker structure. This new method should allow us to add extra glass where needed to strengthen the areas where the most stress will be put in to the driver cell (harness mounts, subframes, etc). It will also mean we can unbolt things if we want to move them in later versions of the car. Realistically this design cannot get any smaller and still fit me in it so the rest of the car (bodywork primarily) will have to be built to this footprint.

Enough babble, on with some build!


Matt uses the CAD drawings (yes we have CAD this time, thanks Solid Edge) to draw out the shapes we need on to some Divinycell H80 foam. In an ideal world we would get this cut by a laser/water jet cutter for absolute accuracy, but we don’t have one of those so we are making do! Once we have the shapes drawn I got to work with a jigsaw to cut out the shapes roughly to size. It doesn’t take long and the foam is great to cut by hand as well, perfect for schools I would think.


While I cut the main shape out my girlfriend Jodie gets to work cutting the detailed lines using the bandsaw. I then finish off some of the more awkward cuts that my small bandsaw can’t quite get in to do. Once we were finished we had a pile of car shaped jig saw pieces. Overall this took around 2 hours with a few people working. Next job is to try and reduce the thickness (currently 20mm) or some of the panels, then glue them all together!

We have also really enjoyed reading the build blog found here, some great ideas for construction and a valuable read to any teams thinking of scratch building a car.

weChook Racing: Electric Boogaloo/2Galoo gearing design

Every race we took the previous 2 cars to we had plenty of people crowding round our rear end to get a look at the gearing system we were using on the car, a system that was successful enough to make it between Boogaloo and 2Galoo almost completely unchanged. Due to slightly different wheel sizing offering up a different set of options for our next car it may not make the cut (design stages still in progress here!) but I thought I best take the opportunity to document the setup here for others to use hopefully with the same success.

Note, this post is by no means a plug for gearing your car, let’s not forget that plenty of fixed gear cars are in the top 10 in F24+! Clearly fixed gear cars can be done very very well (Rotary Racer and Jet to name just a few of our competitors).


Another thing to remember is that geared systems add inefficiency in your drivetrain. This is primarily down to the chain having to curve round gears, each link having to rotate slightly causes wear on the chain and generates a small amount of heat. This is pretty much unavoidable in a green power car as you (almost) always have a chain drive, but imagine in a derailleur system how many bends the chain has to go round vs a single gear ratio system! More bends = more chain link rotations required = more heat generation = less efficiency. There is also the issue that the chain is not always running in a perfectly straight line, this not only wears the chain faster but also causes inefficiency. However, as with all good engineering, this is a compromise that the team has to consider, are these inefficiencies in your drivetrain compensated for by the more efficient running of your motor/batteries/vehicle system?

Why do we like having multiple gears on our cars? The main advantage to having driver selectable gearing the car (over having a single gear ratio that the team determines at the start of the session and has to stick with for the whole race) is the flexibility it offers. You use the gears the same way you would in a combustion engine car, to get the torque or RPM output at the wheels you require for the situation that you are in, while keeping the motor/engine in a sweet spot for torque/RPM out.

Now there is plenty of debate regarding race tactics (constant speed vs constant current draw that I am sure Matt will go in to in another post) but we still feel that gearing offers the flexibility to the driver to get the best out of the car in all situations and, gives the driver something else to do to keep them occupied. With our telemetry system feedback (eChook Nano boards coming soon!) we feel that the gearing offers us a chance to learn a lot about the different strategies a team can use, how you then choose the systems ‘sweet spot’ is then up to the team on the day.

The Gearing

When we built Boogaloo and 2Galoo we only had basic tools and no precision engineering equipment to speak of (lathes, pillar drills, milling machines). The result of this was that I wanted to use as many off the shelf bike parts as I could as it meant that we could guarantee that these would be made concentrically and we would end up with a gearing system that would hopefully be as efficient as possible.  (Unfortunately this does also mean that Matt hasn’t done any of his excellent Solid Edge CAD that I can post up in this blog post, but there will be more of that to come later)

Hopefully this blog post will help other teams who are wanting to build something similar to this design.


The good bits about this design:

  • Easy to make with basic tools
  • Mostly off the shelf bike components, mostly cheap!
  • Very small gear ratio increments between gears (in our eyes this is perfect for a GP car), this is mostly thanks to gearing on one side of the lay shaft before then gearing again (maths bit to come!)

The bad bits:

  • 2 chains = more loses
  • More weight including the dreaded extra rotational mass
  • Lay shaft adds frictional loses
  • High chain speeds (~4x that seen on a push bike) on the derailleur side chain, though we have not had any issues with chain dropping for the whole 2015 season!

The use of a lay shaft in this system allows all of our gear ratios to end up very close together (see the ‘maths’ bit below), far more so than having put the gearing directly on the wheel end. It also allows us to use a derailleur the ‘correct’ way up while getting the advantages of a freewheeling hub (you can push the car backwards without worrying the chain will fall off!). If you look closely realistically you can see the rear end of a bike has been used, though the pedals/crankset have been replaced with the motor and the spokes/wheel have been replaced with the second chain to send drive to the driven wheel.

Parts of the system and tips on how we built them:

  1. The system starts at the motor output shaft. Here we have used a 10T gear that we managed to salvage from an old bicycle cassette I had lying around. It is important to remember that the chain on this side needs to be the correct ‘speed’ to match your cassette, in our case 9sp. By using an old cassette gear I know that it will be around the correct tooth width for 9sp. An old bicycle freehub is cut down to get the neccessary spline fitting to mesh with this gear which allows us to slide the gear off and put a different one on however, I am sure you can get away without this if you expect to change this gear size by simply welding the gear on to a coupler. There are 2 other larger gears shown which were a temporary (still going 1 season later!) measure to act as chain guides should the chain try and jump.  This spline fitting is then fitted to the motor shaft via a steel coupler that we already had in stock, the two parts are welded together. Once I had access to a small lathe this part was later machined in to what you see in these pictures, this was simply to improve our accuracy.
  2. A 9speed chain carrys power from the motor to the rear cassette, an off the shelf part that is mounted on to a disc braked mountain bike hub. The hub is the clever bit of this design. It gives the system a great way of achieving an idler shaft without the need to make your own bearing mounts etc. The freehub built in means that the ‘geared’ side of this setup doesn’t rotate when your car is freewheeling.  You can see the slotted piece of steel we used to mount the hub in as well as the conventional bike ‘skewer’ that is still used to clamp the hub in place. This allows you to easily tension the ‘fixed gear’ side of the gearing, putting the correct amount of tension in to the chain on the left side of the car, the derailleur takes up the slack on the right had side chain.
  3. Over the other side of the idler shaft the disc brake mount is used to fix a 20tooth ‘single speed’ gear to. These are cheap but are made of very hard steel, very hard to drill! It can be done at home but I had a friend with a decent drill setup drill 6 holes in this gear so it would mount to ths standard disc brake bolt pattern.
  4. A single speed chain carries the power to the driven wheel. Our wheels have disc brake compatible hubs which means we have another opportunity to use this to pass torque in using this simple 6 bolt pattern. We wanted to be able to use normal bicycle chainrings which bolt up to a 5 bolt pattern PCD, this would allow us to change chainrings later if we wanted to change our ratio set.  This part was a little hard for us to sort  but would be easy with the correct access to laser cutting/decent fabrication. We ended up using a spider made from aluminium (link below), this was not the neatest solution as we had to open out the centre diameter to fit our axel as well as drill our own 6bolt pattern on to it.
  5. Gears are selected with an indexed shimano shifter (9speed). Currently we preference having ‘thumb’ shifters MTB style but may try some other options in the new season. With this setup I highly recommend getting the best gear cables you can afford (Jagwire seems quite good) as the length of inner/outer cable you need to run is quite long. Keep kinks to a minimum in order to reduce the friction, otherwise you may have trouble selecting gear.

The maths bit

This is a great exercise to go through in schools and excitingly when you do have a gearing system with telemetry (eChook Nano boards coming soon!) you will actually be able to check your calculations using the wheel speed and motor speed sensors to measure a ratio of gearing between the two!

The facts:

  • Motor gear: 13tooth
  • Lay shaft gear cassette: 14,15, 16, 17, 18, 19, 21, 23, 25
  • Lay shaft fixed gear: 20tooth
  • Wheel gear: 34tooth

The formula for working out your gears (with a lay shaft) in this setup works like this:

Overall Ratio = (Current Selected Lay shaft Gear / Motor Gear) * (Wheel Gear / Lay shaft Fixed Gear)

For our setup above this gives us a great set of ratios for us in F24+ on our car. The ratios we end up with start at 1.83 (very high wheel speed per motor RPM, a good high speed gear)) and end at 3.27 (very  low wheel speed per motor RPM, a good pullaway and hill climbing gear), the difference between ratios is 0.13 for the single tooth steps on the chain ring and 0.26 for the 2 tooth steps. For our car this set of ratios offers a good range as well as resolution between gears.

We would suggest you have your team make a nice excel document with these calculations in (hopefully using our numbers you will get the same set of results we did!). Although these ratios work well with our car with our wheel sizes in F24+ they will not be optimum for other cars. An excel sheet will allow you to tweak things like the cassette you buy and the other gears in the setup in order to get the best result! It’s an exciting piece of maths to play around with and understand the impact that each gear has on your range (difference in ratio between top and bottom gear) and your resolution (differences between each gear you can select). Every gear in the system plays an important role in the result! You team probably has a good idea of the ratios that your car runs best at already from being on a fixed gear system, make sure these are included in your range of ratios available.

weChook Racing: 3galoo Design: Wheels

The first thing we decided upon for Electric 3galoo was a change to smaller diameter wheels – 16 inch rims down to 14 inch. The main reason we hadn’t done this previously were concerns over the cost and availability of tyres that fit this size rim, but after discussions with Matt from Renishaw ( we decided to take the plunge.

The main advantages of smaller wheels are aerodynamic. The steering envelope is reduced, meaning the total width of the car can be reduced (or the same width can be maintained with less cambering of the front wheels), and the top surface of the car can be lower, reducing the total frontal area.

Plot showing estimated aerodynamic vs rolling drag for 2galoo

Plot showing estimated aerodynamic vs rolling drag for 2galoo

The con of smaller wheels is higher rolling resistance. Rough calculations say that at F24+ speeds, aerodynamic drag exceeds rolling drag by at least a factor of 4, so it shouldn’t be too hard to get a win in the trade off.

As well as reducing the diameter of the wheel, we wanted to make them narrower. The widest point on Electric 2galoo is at the centre of the rear wheel, at 560mm. As well as being well over the minimum track width of 500mm, having the widest point on the car so close to the back is aerodynamically very disadvantageous – we found it impossible to make a smooth curve for the bodywork that came back to point, as seen on Reprobation and Jet.

In order to reduce this width we needed to forego spokes, replacing them with solid carbon disks. We’d also have to replace the standard bike hubs we’d used on our previous cars with something a bit more bespoke.

Our original design (made before we’d actually got our hands on the rims we planned to use) is shown in exploded view below. We planned to fit some foam cored carbon sandwich panels inside the rim, with a hub bonded and bolted around them. We would have had the same wheel design at the front and back of the car – the front wheels would have been bolted through in a similar fashion to 2galoo, whilst the rear wheels would be attached to a brake disc holder to enable driving/braking torque to be transferred to them.

Initial flat wheel design

Initial flat wheel design

Once the rims arrived, we noticed a few problems with this design – the inside of the rim was angled, which would make it very difficult to get a good bonding surface between it and the carbon discs. The outer surface of the rim however was vertical,  making it a perfect bonding surface. This led to our second design iteration – instead of bolting the hub around the carbon discs, the discs would be attached around the hub.

Second flat wheel design iteration

Second flat wheel design iteration

This reduced the complexity of the hub, reduced the number of parts we’d have to turn, and increased the bonding surface area on the rim, hopefully resulting in a stronger final product (in fact, my calculations say that each bond should be able to support 865kg – slightly more than we’re planning for 3galoo to weigh). This still allowed us to keep the front and rear wheels identical – a big benefit when it comes to keeping spares.

If anyone would like a closer look, the drawings for the first hub is here: Hub and the second is here: NewHub

Next up, the chassis!

weChook Racing: 3galoo Design: What’s Different, What’s the Same?

As we came to the decision to build a new car for the 2016 season, the first question was ‘What do we keep the same, and what do we change from 2Galoo?’.

There was an easy answer for this when we started designing and building 2Galoo: Change everything! Boogaloo was huge, bendy, impossible to drive in the pit lane and slow. Only two things made it intact from our first to second cars – the layshaft gearing system, and the electrical system (and even that was directly carried over from C-XeVolution / Project-E).

Electric Boogaloo at its last event - vast compared to its competitors

Electric Boogaloo at its last event – vast compared to its competitors

So change everything we did! In order to reduce our aerodynamic profile we lowered the driver’s seating position, cambered the wheels and replaced the steering wheel with a lever – all in all reducing our frontal area by more than 30%. To increase stiffness we replaced the steel space frame / plywood construction with a tub made from Rohacell (with the added benefit of a ~4kg weight saving).The steering was redesigned from scratch, using trail rather than caster to maintain high speed stability, without the awful dry steering – it mostly went to plan apart from breaking at half the races 2galoo attended.

All in all, I’d say it worked! 2galoo competed in the second half of the 2015 season, achieving 2 podiums and finishing in 8th place in the final championship standings. Ahead of us were a car each from JLR and Renishaw, two cars from Silesian University (regular corporate challenge winners), Rotary Racer (many times F24 champion) and Jet (2013 and 2014 F24+ champion).

With that in mind, what next? Having analysed the competition (aka: poked around in the garages after everyone else went to bed at the International Final) we picked up on a few areas in which we were lagging behind the cars beating us:

  • Bodywork – In both form and surface quality 2galoo lagged far behind the cars that finished the season ahead of it.

  • Wheels – Most of the cars that were ahead of us had created a flat wheel in one way or another, meaning it wouldn’t have to be trued, and that the total width of the car could be reduced. Also, Renishaw were using lower diameter wheels than we had used, allowing the whole car to be shorter in height, and therefore have a lower frontal area.

Based on this, and having carefully inspected the new wheels on Jet 2, we decided to start with smaller, flatter wheels. This decision drove changes along the rest of the car, meaning we could make the chassis shorter in both height and length, and reducing overall width of the car. It also buys a precious extra cm of width for Ian’s knees, the discomfort of which is his biggest gripe with 2galoo. Smaller wheels also force a change to the gearing, as they effectively act as a different final drive ratio.

In the next post I’ll go into the design iterations we’ve gone through with the wheels, and our final intended design.

weChook Racing: How we use data in the pits

Having covered how Ian uses our measured data whilst out on circuit in the last post (read it here: ), I’m now going to cover what we can do with it when we’re not racing – be it in the pit lane or once we’re back home.

The first step is getting the information from the car to my laptop. As long as we remember to put it in, the telemetry board will record all measurements to a text file on an SD card, which can then be easily transferred across to a computer. The system also transmits data live wirelessly during a race, but this is of little use when the car goes out of range or behind a tree – pretty much everywhere apart from Merryfield and Dunsfold Park.

For the information to be valuable during the constraints of a race day, all the information has to be pulled together quickly – there’s not a lot of time to make changes in between the end of practice and the start of the race so every second counts. In order to maximise the utility of our data logging, I wrote some code in MATLAB that will read the data files, and generate a report with useful plots and calculations. I’ve uploaded two of these reports, from two different races at Rockingham to the website:

As an aside – I heartily recommend that any aspiring young engineer go out there and get some experience using MATLAB – it is easy to pick up and there is a huge wealth of help and support available online. As a data analysis and visualisation tool it far exceeds Excel, and will make a piece of work look far more professional! I use it extensively at work to perform simulations, automatically generate reports (automating a task that used to take hours keeps my manager very happy) and design control algorithms. From experience, I can also say that if I’d learnt to use it whilst at university, it would have made my dissertation project a whole lot more manageable, due to the Gigabytes of data that I was dealing with from incredibly high resolution measurements of impact data.

Sales pitch over! Once I’ve worked my magic with MATLAB and generated a report we can work out how much current and power we were using at any given point, and how fast we were running the motor. Using this approach with data from a run in practice, we can determine whether we can complete a full race distance at that pace without flattening our batteries (I’ve done plenty of battery testing, so I have a good understanding of how much energy the batteries have available).

Based on the data from the Rockingham heat, we were able to plan our power usage for the Lap Race – we estimated how much shorter it would be than the standard hour and then determined how much more quickly we could discharge the battery. If you look at the two reports linked above, you can see that we drew just under 25Ah from the batteries in both events, but at a higher average rate in the lap race.

Also shown in the reports are traces of throttle position and motor speed. Comparing the throttle trace from the Lap Race to that from the heat earlier in the year, it can be seen that Ian is performing fewer gear changes, and spending less time at part throttle. It can also be seen that motor speed tailed off much more quickly at the end of the Lap Race – we’re putting this down to the fact that we were using our best batteries in the Rockingham heat, but we saved them for the F24+ decider on the International Final weekend.

We’re planning to extend our data collection next year to include wheel RPM (from which we can calculate vehicle speed, and determine which gear we were in) as well as motor temperature, to avoid the risk of cooking another one! With this data we plan to be able to run an improved race strategy in the 2016 season – instead of targeting a constant rate of discharge from the batteries, we will be looking at how we can most effectively convert each unit of energy into speed.

Which brings me nicely onto the subject for my next post: Constant Current vs Constant Speed control!

weChook Racing: How we use data on circuit

Seeing as we’ve been espousing the virtues of data collection of late, I’ve decided I’d best write at least a bit about some of the things we do with our data.

I’m going to split this into two posts – the first covering how the driver uses the information during the race, and the second discussing what we do with the logged data in between sessions and race days, as well as what we’re hoping to achieve in the future.

From the Rockingham heat onwards, our cars were fitted with a screen that showed the driver a live readout of battery voltage, motor current and motor speed. Voltage isn’t much use on a moment to moment basis – it fluctuates with the current that is being drawn, meaning there’s no simple way to estimate the charge left in the battery

Motor RPM is also tricky to use – we know we need to keep the motor in its ‘happy range’ in order to keep power consumption low and stop the temperature from getting too high, but it’s difficult to plan a race using motor speed – without a good model of the motor, we don’t really know whether we need to hit 1750 rpm or 1800 rpm to make it to the end of the race!

That leaves battery current as the most useful resource to the driver. We’ve done plenty of testing, which shows that our best batteries have a capacity of roughly 25 Amp-hours, when discharged at a high current. For comparison, our worst batteries have a capacity of 22Ah, which can make a big difference when trying to reach the end of a race.

With 25Ah at our disposal, and an hours worth of racing to complete, the maths isn’t too hard; we need to hit an average of 25A over the course of the race to make sure we get to the end – simples!

With a single speed, relay controlled car, this is achieved through selecting the right gear ratio – get it wrong and you won’t reach the end of the race, or you will get there but at a slow pace. Choosing that gear ratio can be tricky – for me it came down to experience and voltage measurements. I’ll discuss more on this in the next post though!

Electric 2galoo had the luxury of a wide range of gear ratios, and a speed controller. By shifting up and down the gears and by varying the throttle input, Ian was able to target a constant rate of power consumption. At the International Final, this allowed us to control the rate that the battery went flat very nicely – gaining us a place on the last lap as the competition ran out of juice!

2galoo's current consumption from the international final

2galoo’s current consumption from the international final

We’re currently developing a data logging product that will be available for sale to all greenpower competitors – read more about it here – . If you’re interested in investing in one, get in touch with us on twitter (@Ramjet_gpt) or on the greenpower forum here:


Introducing Project eChook Nano

Hello all!

The weChook Racing and Driven teams have recently launched a joint project (Project eChook Nano) to develop a standalone system capable of logging important telemetry data from a Greenpower car. Both of our teams feel like we learn a lot from our current telemetry setups and that making this type of information more easily available for other team’s vehicles would be incredibly beneficial and would really help with the engineering and learning aspects of Greenpower racing.

Our aim in developing this hardware is create something simple and affordable that will allow those teams without electronics experience to collect live data from their car for analysis during races, and as something to study in between events. It will be based around an ArduinoNano, and be provided with the base software to perform standard logging functions, whilst giving the students the opportunity to implement their own code to customise the functionality as they see fit.

The hardware is designed to interface with an android app that Rowan has posted about on the greenpower forum here: The hardware on the car communicates with the app via bluetooth, and can provide instantaneous readouts to the driver, as well as logging the information for later analysis. The app will also use the phone’s sensors to supplement the information gathered from the hardware.

A further aim of the project is to provide the ability to live stream the information to web interface via the phone’s 3g connection, allowing information to be viewed live from the pit wall. An exciting prospect to try to understand why a competitor car is accelerating past yours but consuming less amps….perhaps time to get the chain oil out during that next pit stop 😉

We’re designing with the following I/O (and some of our suggestions on what they can be used for):

• 2 x Voltage (12V, 24V)
• 2 x RPM (Motor, Wheel)
• 3 x Temperature (Different bits of the motor, battery)
• 1 x Current (Motor)
• Throttle Position
• Brake
• Cycle View & Launch buttons (for use with the app)
• LED x 3 (visual status indication)
• Bluetooth Output (interface to the app)
• 2 x PWM output (Fan, Motor controller)

Our primary intention is for this to be a passive component, that can be added to a car with minimal disruption, and will not affect the actual running of the car – we don’t want to be responsible for taking someone out of a race! The pins are there however to receive a throttle position input, and output a PWM signal to a motor controller. Teams can pick and choose what sensors they feel are necessary for their learning, though we would suggest current consumption is the most interesting!

We’re are currently working hard to get the base system cost less than £40 to make this accessible to as many teams as possible. Sensors are not included in this figure but most are cheap components (bar the LEM current sensor which can be found for ~£18). Due to the open source nature of this project we aim to provide teams with all the information required to source and put together the hardware themselves, but initially we will provide a ‘build kit’ so we can get some hardware out there in the field and get keen teams testing it as soon as possible.

At the very least, we’ll be running the system on Electric TubeOfGlue (the weChook racing team’s development vehicle) for the season if no other teams are interested!

Please get in touch with us on the greenpower forum ( or on Twitter (@Ramjet_gpt) if this is something your team would be interested in having or even being involved with. We have captured our ideas here but it would be great to hear from others on what is most important to their team.

Best Regards from the team, Matt, Ian, Rowan and Ben!

eChook Nano Schematic

eChook Nano Schematic

weChook Racing: International Final Day 2

Day 2 started with a nice lie in. The car was pretty much ready .to roll, and with all the running on day 1, we had no real need to go out in practice, giving us plenty of time until 1 o’clock when the F24+ International Final & Corporate Challenge would start.

With the transponder fitted and the batteries nicely charged, we had a good look around the car for last minute improvements to be made – we ended up settling on redoing the tracking (again) and making wheel covers out of duct tape. On of the hardest things in Greenpower is quantifying improvements, but we think the wheel covers must have made a difference – despite being a longer race, our average speed in the F24+ Final was greater than it was in the lap race, and our fastest lap was 2 seconds quicker, despite using a lower amount of power per lap.

We used the ample spare time available to us to watch the F24 race – a particular highlight was Viper dashing of the line and overtaking the pace car before the exit of the first corner – I suspect that driver wasn’t really listening at the driver briefing. A cleverer strategy would have been to hang and get up to race speed over the last quarter of the formation lap, ensuring the race proper was started at top speed.

Seeing as we’re planning a new version of 2galoo’s bodywork before the 2016 season we  decided to give the current edition a bit of a send off, by giving it some additional decoration… with help from my sister who was visiting, and from some of the JLR guys as well. We’d like to hope that Gav appreciated our support!

We <3 Gav (we also <3 Nash)

After another precarious trip up the banking, and a failed attempt to goad Dave Senior into a pushing race to the grid, we lined up in 6th place, behind Jet, Reprobation, F-eV, Bullet and Rotary Racer – all big names! After rather rudely snubbing Nash in our on grid interview (sorry again about that!), the grid was lined up and ready to go.

2galoo shot off the line when the flag dropped, just about reaching 2nd place before the first corner. When the car next came into view from the pit lane, it had been overtaken by Jet 1 and 2, along with Reprobation, and was in close formation with Rotary Racer. We managed to hold them off for the first 3rd of the race, but their lap times held strong when we hit the same mid race dip that we experienced in the Lap Race on day 1.

Probation and REC-349 had both dropped back a fair distance at the start of the race, but began to drag us back in in the last 15 minutes. With time for only 3 laps remaining, both of them caught and overtook Ian up the hill (we really need to look into some lightweighting for the driver) and began to pull away.

We crossed the line with only 4 seconds to spare before the flag dropped, which pushed us into the longest race that 2galoo had completed. It appears that Probation had pushed just a bit too hard to get ahead of us before the end, as its speed dropped significantly as the hour mark passed, and we retook the position – unfortunately REC-349 was just a bit too fast for us.

Across the line!

Across the line!

We finished the race in 11th place overall, and 9th of the cars competing in F24+ rather than the corporate challenge. It was a bit disappointing to finish outside of the points, but we were very happy with 2galoo’s performance, and had a lot of ideas on how to improve our performance for 2016 – both in the car and in race strategy. We also made some good contacts over the weekend, with whom we’re hoping to push on to greater success next season.

The F24+ championship concluded with Reprobation 2 points ahead of Jet, an almighty effort from the Renishaw team to beat a car that still looked untouchable at the start of this season. Driven bettered their previous best ever season performance by finishing the championship in 3rd place, just ahead of the two Bullet cars from Silesian.

Electric 2galoo finished the season in 8th place overall, just behind Minion and ahead of Project E. It was the 3rd highest place new car, and weCHOOK Racing was the highest place all new team. Thanks to building a new car mid season, we also managed to finish 25th with Electric Boogaloo!

Next stop: I’m not sure really…. Goodwood maybe?

An important message

An important message

weChook Racing: International Final Day 1

The end of our first season came up quickly. It was less than a month since Electric 2galoo had been finished, and we’d already taken part in 4 races and finished on the podium twice, leaving us sitting in equal 5th in the F24+ championship, with Rotary Racer.

We arrived at the circuit in good time, and were directed to our garage. We had  great location, in between the Portuguese University, Silesian University and the two teams that had travelled over from America – the now established Team USA with ARES, and the new team from the University of Alabama with Shock.

It didn’t take long for us to get through scruiteneering – we got there just before the queue got too mad! With our final sticker off the season on the car, we were ready for a few laps in practice. After our numerous calamities and failures at previous races, we were keen to put as few miles on the car as possible, so we only completed 6 laps in practice to make sure everything was running smoothly.

We ran the stint as planned, and had minimal drop off, but were not overly happy with the pace of the car, being no faster than Electric Boogaloo had been the last time we had visited Rockingham. In between practice and the race we did some serious fettling – specifically retruing the wheels. Just pushing the car along the ground, it was possible to feel an improvement in how the car was running.

Current log from our stint in practice

Current log from our stint in practice

Once we’d worked on the wheels, we downloaded the onboard logs from the practice laps, to check our current consumption was in a good range. Everything looked good – once the number of laps was announced we did a few quick sums, and realised we could up our power consumption by a couple of amps for the race.

After all that, we still had plenty of time to go for a wander and and chat to the other teams in attendance. The story of Shock, from the University of Alabama, rang true for us – the two guys had built their car in the shed in two months. They’d also got it shipped across to the UK from America, so they were just slightly outdoing us there! The car looked very well made, if not a little large (just like our first car… but Boogaloo wasn’t really well made). We had a good chat about how they’d designed their car, and how to make sure they get to the end of the race.

I accidentally posed in front of the American flag

I accidentally posed in front of the American flag

It got to 30 minutes before the race, so we strapped in the race batteries (not quite our best pair – we were saving them for the International Final on Day 2) and taped on the bodywork. Ian strapped himself in and we wheeled ourselves out to the circuit. Our ridiculously huge turning circle meant we took a bit of an awkward route out to the grid, but we made it eventually.

Ian was very excited for the start of the race

Ian was very excited for the start of the race

2galoo was lined up near the back of the grid for the lap race – only the corporate entries were behind us, but we made a good start and overtook a good number of cars from the flag dropping to the first corner.

The first 20 minutes went smoothly, we were 15s a lap faster than in practice, and we had a very gradual drop in lap time. Half an hour in, we experienced a sudden (and still unexplained) lap time drop of 10 seconds, then spent the rest of the race back at our gradual drop off of about a second per lap. This phenomenon would return to haunt us on day 2, in the F24+ final proper. Regardless, we were reasonably happy with our performance, finishing ahead of cars from Renishaw, JLR and Lockheed Martin, and overtaking Minion on the final lap, as their batteries just gave up before the end. Jet 2, driven this time by Dave, beat Reprobation to the line, but only just, having run very low on remaining power at the end of the race!


PSEM had a difficult time – they spent their last lap going at less than walking pace, eventually making it into the pits after being lapped a number of times. It turned out they’d hit the batteries way too hard, and in doing so had overheated the motor – it was at 80 degrees when i got to it with a laser thermometer, and it had been off for a good while by that point! We had a good discussion about race strategy and using gearing to manage current, before they set off on a marathon upgrade session – they were still in the garage long into the evening when we had cracked on with the beers!

With the end of the F24+ Lap Race, day 1 of the International final was pretty much done for us, so we prepped what we could on the car (That car has been tracked so many times now that we’ve got it down to a fine art) and made sure day 2’s batteries were on charge, before retiring to the campsite, for some beers, food and sleep!

weChook Racing: Castle Combe Heat 2015

This came around quickly – it’s already the final heat of the 2015 season! It barely feels like last week that we started out building Electric Boogaloo, and here we are 7 races and a whole new car later, with only the International Final to go!

We managed a few tweaks to Electric 2galoo in the couple of days since Aintree – one of the wheels had a solarfilm cover added, along with a sharper knife edge at the tail of the car and some flaps to extend the bodywork down around the wheels. No massive improvements in pace were expected from these changes, but every little helps, and we hoped this would give us an idea what would help before the final.

Castle Combe is only 70 miles from home for us (and no one from Driven wanted to camp) so we set off early in the morning for the track. We ended up following a Citroen Saxo with a suspiciously large box on the roof, which turned out to be Nathaniel of Stealth Racing, who was also travelling to the track having recently started at university near to us.

Some faffing

We did some faffing in the paddock, which meant that by the time we were ready, the scruiteneering queue was all the way around the car park. Thankfully, Josh gave us a bit of special treatment (I’m sure he was just looking for more things to get us to change before the final), giving us a bit of time to prep the car before practice.

As ever, practice proved to be stressful. Ian headed off onto the track, and never came back into view. I eventually got a report from the recovery driver that he had pulled off the circuit somewhere around the Esses, and was playing with something at the back of the car. 18 minutes after he left, Ian returned to the pit lane, with the news that there was a loose connection in the motor controller, that he had ‘fixed’ with some of the duct tape that was previously holding the body on.

Almost as soon as we headed back onto, the red flag came out for an incident that was out of view from the pit lane. 2galoo was the first car past once the red flag came out, and began drifting towards the marshall when applying the brakes heavily, due to a slight imbalance. Another trip to the pits followed to sort that problem, before we finally got a proper lap in. The batteries had taken a battering before we actually managed a timed lap, but we ended practice with the 6th fastest time.

In between practice and the race we made a few more tweaks – thankfully, we didn’t have to hunt down a welder this time. We could tell from the tyre wear that the front wheels were in need of tracking, and some more tape was needed, but otherwise the car seemed in fine fettle.

We spent the rest of the break investigating some of the new additions to the field; it was the first event for Jet II (Scramjet?), and everybody wants a look. It was pretty obviously only just finished – we wandered across as the cockpit opening was being cut into the bodywork, and the car was still covered in carbon dust when it was wheeled to the grid – and the team were playing down their chances, but we all had high expectations nonetheless! Jet II and Electric 2galoo are race numbers 561 and 562, so we would be starting next to each other on the grid!

Also in attendance was the heavily upgraded Stealth – with smaller wheels and a completely new set of bodywork, they were hoping for a similar step to that which we had over the summer break, if not more. The team is new to F24+, and I see I see big things if they stick with it.

The time for chatting quickly evaporated, so we installed our race batteries and set off for the grid. After a slight altercation with the recovery vehicle, which was coming the other way, we were the first in line to be wheeled out, which would have ensured us a first row start in the olden days… all it meant this race was that we were really in the way! It wasn’t too bad of a spot, we could admire Jet II (Turbojet?) whilst Sandbach to make their way to the track.

On the grid

On the grid

Eventually, the grid was formed, and we were ready to go racing! Ian got a lightning start, managing to pull up alongside F-eV, which started a couple of rows ahead, by the time the first corner was reached.

Lightning Start!

Lightning Start!

There was no settling into this race – Ian spent the first 40 minutes of the race of the race fighting for position with Stealth and REC-349, the ever improving car from the Renishaw apprentices. After changing position nearly every lap for three quarters of the race, Ian eventually began to pull away from Stealth; which was showing the first signs of battery degradation, and closing down the small buffer that REC-349 had built.

At this point I was a nervous wreck on the pit wall – I couldn’t tell if Ian was abusing the batteries too hard to race the cars around him, or whether he was taking it at our pace, and the cars around had been too aggressive. With 5 minutes of the race left, Ian unleashed the reserve amps, and increased speed to overhaul a 15 second gap and overtake REC-349 within a lap. It seemed he had power to spare, pulling out a 36 gap on the last lap of the race, as REC-349’s batteries dropped over the edge, having been pushed too hard trying to hold onto the position. We finished  in 5th – our original target position – in what we both agree was one of our best races yet, even if we weren’t fighting for a podium.

We made it!

We made it!

Elsewhere, Project E put in a cracking performance, with a massive improvement in pace since Aintree, beating us fair and square despite suffering a puncture on the last lap. F-eV suffered a ‘chain off’ early in the event, and used to opportunity to gear up significantly, presumably as a test for the high speeds expected at the International Final.

At the front, Reprobation took the win, but massive credit has to go to Cullimore Racing for taking a 2nd place only 10 seconds off the lead, with a car still missing most of its aerodynamic devices, and that had only performed a lone installation lap before the start of the race.

After the race, we had a quick pow-wow with some of the other F24+ competitors, before talking through our electronics and data logging package with the judges for the Siemen Digital Award. After all the nattering, it was only a few minutes until the prize giving ceremony, at which we were very happy to have been given the aforementioned award! I shall certainly endeavour to write a full blog post over the winter break on our telemetry, logging and data analysis methods, along with publishing some of our reports to give other teams an idea of what we’re doing.

Next Stop… The International Final at Rockingham

Greenpower even organised some good weather for us!

Greenpower even organised some good weather for us!

weChook Racing: Aintree Heat 2015

Maybe I should just copy and paste the race report from Dunsfold for this one…

We set off soon after work on Tuesday, and hit a remarkably low amount of traffic on the way to the track. This time, we met Driven at the circuit, having been allowed to camp for the night within the track limits. After wolfing down a KFC and a beer, we hit the sack early to be well rested for the race day ahead. Camping at the circuit gave us a nice lie in as well!

We were woken up by the heavenly sound of a track sweeper – with many punctures in the last two races at Aintree, I was hopeful that this would make everyone’s race a bit safer. Our pit box was set up before 8:00 am, and through scruiteneering by 8:30 – our quickest ever start to the day, giving us plenty of time to get ready for practice.

The brake light definitely worked

The brake light definitely worked

Looking at the competition, JLR were represented by Project E and F-eV, whilst Renishaw were represented by a comparatively small contingent – only Reprobation was in attendance. Cummins had a new car – Mach 1 – with a very tidy set of bodywork but little running time so far, and Sandbach had Dylan, their newest car, seemingly ready to roll. I would have liked to have had a closer look at Dylan – Sandback have come up with plenty of interesting ideas before, and I’m sure there are plenty on Dylan as well. I expect there’s still a bit of work to be done though, as it was beaten reasonably soundly by Dougal.

Sadly, there was no sign of Jet II this time around – we await Castle Combe with baited breath.

Practice started poorly for us. Ian completed 5 laps well off the pace, behind F-eV and Reprobation, which was to be expected, but also a long way behind Project E and Mach 1, both of which we were expecting to beat. Unfortunately, the 6th lap never came – 2galoo had pulled off to the side of the track with yet another steering failure.

This time around there was no panic – one of the marshalls pointed us towards a local garage, who quickly had the offending part welded back together. What’s more, we’d finally isolated the root cause of our problems. As long as we’re correct in our analysis, we don’t expect to see any repeats.

The car was reassembled and ready to go with an hour left before our race, so we used to opportunity to fraternise with the enemy –  we were particularly impressed with Cummins’ heat sink. After discussions with the team however, we had the impression that they would be running too hard in the race, and would likely run out of batteries well before the end. This was a valuable insight – we ended up behind them at the start of the race, but knew not to wreck our batteries in the first 20 minutes getting past them.

The Driven/weCHOOK fleet

The Driven/weCHOOK fleet

We lined up on the front row with F-eV and Project E, with Reprobation starting from the pit lane after detecting some bodywork rubbing. The start went well for us (despite a massive jump start from Project E) and we led into the first corner, where the cars went out of sight. Once they’d come back into view on the back straight, we were down in 5th place, behind the 4 cars that were ahead of us in practice, with only a few seconds between us and Mach 1. Fortunately, after the repairs, we’d gained about 20 seconds a lap, which put us right back in the mix.

With the long climb up the back straight, we’d agreed to take a conservative strategy, to we had the battery voltage left near the end of the race to pull ourselves up the hill. With this in mind, we sat behind Mach 1 for the first 5 laps, trying to extract a tow and managing our current. Cummins’ new car quickly began to drop of the pace, and we moved up to 4th. We immediately started to close on Project E, and were past a few laps later.

Racing with Project E

Racing with Project E

At that point, the race looked to be settled – Reprobation were pulling away from F-eV at a good rate, and F-eV was still pulling away from us about a second per lap, with neither car looking to run out of power any time soon – but as ever, Renishaw spiced things up. This time, Reprobation skipped a chain, just in sight off the pits on the back straight, but out of range for support.

Matt pulled off a heroic fix at the side of the track, and had the car running again 3 minutes later. By this point he was down in 4th place, but really put the hammer down – at one point he was 20 seconds a lap faster than anyone else out there – and had the lead back with a plenty of time left.

After that drama, we sat in 3rd place, reasonably unthreatened, but without much chance of catching F-eV ahead of us. We were happy to see the end of the race without issue – the championship points were very much appreciated. Maybe breaking steering components is a sign of good luck for us!

And across the line!

And across the line!

We were very pleased to receive the IET Engineering award for Electric 2galoo, it’s great to see that our version of engineering is just as appreciated as the heavily CAE influenced design ethos espoused by JLR and the like.

We’re off to Combe next, hope to see you there!

weChook Racing: Dunsfold Heat 2015

We were back on the camping for Dunsfold, and Saturday was unprecedented – we were packed and ready to go 2 hours ahead of schedule, leaving us with absolutely no idea on what to do with ourselves. As we I would soon find out, checking that I’d remembered all the bits of my tent would have been a fine start.

The run down to Dunsfold went smoothly, with Electric 2Galoo successfully remaining on the roof of the SAAB. The ‘low slung sports wagon’ didn’t enjoy the road into the campsite, but it managed all the same. Having assembled my poleless tent using some cable ties, a van and my ingenuity, the campsite was set up, and we headed off to the local pub for some well earned grubs and a pint or three.

After a thankfully windless night, we left the campsite miraculously on time, and headed off for the circuit. We (nearly literally) bumped into the greenpower wombles towing a selection of portaloos when we got to the track – the rest of the world had been covered by a thick blanket of fog, which managed to lift itself just in time for practice.

Our first puncture of the day somehow managed to occur getting 2galoo off the roof of the wagon, causing some early morning consternation before scruiteneering. A quick change from Ian saw us get in the queue to have the car checked in plenty of time, and we had passed with plenty of time to go before practice started – in fact we even had time to walk the track, spotting the large landing lights that really needed to be avoided.

The second puncture of the day occurred almost immediately upon leaving the pitlane for our first practice lap. Somehow, even with a puncture, Ian set what would turn out to be the 13th fastest practice lap! We got the car back in, and changed the tyre for a second time, before getting getting back to the pitlane, hoping to collect some useful data before the end of the session.

Unfortunately, on the second corner, the jolt of running over a landing light caused a steering component to shear (having probably been overstressed after running around for 5 laps with a puncture). On getting the car back on the recovery wagon, we discovered that the failure was not something we would be able to fix without a welder.

A frantic dash up and down the paddock revealed that no one had bought any welding gear with them – the best offer we had was a soldering iron, which probably would not have done the trick! There’s no way we could go racing without getting that component fixed, so it was beginning to look like we’d be going home early. We were just about to give up and offer our assistance to Driven, when Jeremy pointed out that we had driven past an industrial estate on the way into the circuit. With 90 minutes to go before the race, if we could find someone who would lend us a welder, we could feasibly get the car fixed up and ready in time for the start.

In the end it took us about 30 seconds of searching before we bumped into Andy, who was doing a bit of catch up work installing a new clutch to a Golf in his workshop. He kindly offered to weld our bracket back together, and even added a very tidy (and much stronger) reinforcement, which would hopefully prevent any recurrence of the failure. Many thank yous and a dash back to the paddock, and Electric 2Galoo was back on 4 wheels.

We were the last car that made it to the grid in time for the start, having taped the bodywork down and wedged Ian in as quickly as possible. Ian didn’t really know the racing lines, neither of us knew if the car would survive mechanically, and we had no idea how much power we’d be using over the course of a lap. It was a stab in the dark (thankfully not in the fog as well though)!

With a few steady laps to get the lay of the land, 2galoo settled into 4th place, behind Jet, Reprobation and F-eV, but ahead of Rotary Racer and (most importantly) Project E. If someone had offered to the finish the race then, I would probably have taken their arm off!

The first 30 minutes of the race saw brilliant consistence from car and driver, managing 17 consecutive laps within a 2 second window. It was towards the end of this stint that F-eV began to start slowing down, and the gap between us and 3rd started to decrease. With 20 minutes to go, we were right behind them, and it was obvious from the noises at the rear end of F-eV that they’d developed a slight issue, but not one that was dramatically slowing them down.

Frantic discussions were in progress in the JLR Driven camp about retiring the car to save it for Aintree and Castle Combe, when Reprobation pulled off into the pit lane from the lead. (I haven’t even mentioned the excitement at the front! Reprobation had had the pace to overtake Jet, and looked like it might be able to hold on for the rest of the hour). This promoted F-eV to 2nd place – a position that would move them 2 points clear of Reprobation and Silesian in the overall championship if they could hold onto it. This made the decision for the team – take the risk and try to make it to the end of the race.

A few laps later, Electric 2galoo sailed past the ailing F-eV, into 2nd place. Ian wisely reduced the pace at this point to conserve power – there was little chance of catching Dave, so all we had to do was stay ahead of F-eV… or so we thought. Rotary Race began to catch up, having barely suffered any speed drop off at all – overtaking first F-eV and then Electric 2galoo.

A podium finish would have been plenty after the morning we’d had (and with all the bits of the car that really hadn’t been optimised yet), but fate intervened again, and with time for only a couple of laps left on the clock, Rotary Racer also pulled off the track with a puncture, promoting us back into 2nd place.

The final bit of icing on the cake was managing to unlap ourselves with a few minutes remaining! I don’t care how easy Dave was taking it, it’s still pretty satisfying to see your car go past the dominant force for the last few years. What’s more, it saw us finish the race on the same lap as Jet (and at one of the shortest circuits), something that I don’t remember having achieved before.

We were delighted also to receive the ‘Spirit of Greenpower’ award in the prize giving ceremony, it really did top off the day for us! Many thanks to everyone that gave us a hand, advice or just some kind words when all looked to be going wrong, we wouldn’t have managed without it!

Elsewhere in the field, REC-349 really got into its stride, finishing in a season’s best of 4th, and beating both of its big brothers. Its lap times were super consistent, showing good aerodynamic efficiency and power management – maybe it could/should have been going even faster and threatening F-eV.

There was great news also for EMF Racing, scoring their first points of the season, after we had some close racing with them at Bedford, where they just missed out in 9th.

A massive well done to the Arthur Terry School for a cracking performance to win the kit car race in F24 – they managed a 90 minute race with driver changes at a high average speed than the kit cars competing in F24+ did! I’ve supported Greenpower at a couple of events in the NEC where both the pupils and supervisors have been in attendance – the kids really know their stuff, and it’s a pleasure to talk to them about the hard work they put into their car, so I love seeing them do well!

Congratulations to Rotary Racer for winning both F24 races, I hope it makes up a small amount for the puncture in F24+, and of course, well done to Dave for a well managed victory in F24+. Now please stop keeping me on tenterhooks and get Jet 2.0 finished!

Next Stop for us is Aintree… and I think we’re meant to be leaving right about now!