Posted on Leave a comment

RaceCapture/Pro – hardware testing is painful

Oh, complexity

When you’ve designed something with this many features- the demons of complexity come home to roost. And, when it comes to comprehensive testing it’s especially painful.

Here’s a naked yet fully tested – manually tested –  RaceCapture/Pro board with GPS and accelerometer modules installed.  When I finished the spreadsheet identifying over 100 individual hardware test cases cases I reminded myself how important an automated test rig will be for this project.

RaceCapturePro_RevD_withGPS
RaceCapture/Pro - naked and fully tested

Oh, Lua

What we have going for ourselves is with the embedded Lua scripting interperter – aside from providing a way to easily control almost all controller behaviors (much more on this soon) it provides an easy way to poke at the hardware for testing purposes. Check out the console screen shot (click to see full version) for an idea on what’s possible:

RaceCaptureProTestingConsole
RaceCapture/Pro console (click for full view)

Race Cars + Lua Scripting?

Lua is proving to be a great embedded scripting language- on an upcoming post we’ll describe just how much control you will have over your race car 🙂

Leave a Reply

Your email address will not be published. Required fields are marked *