I just finished installing a Video VBOX Lite system in my car and am happy be driving my car again! It’s been 3 weeks since I started the project with 3-4 days of actual time spent. The biggest time sink was routing a microphone to the rear bumper which isn’t necessary but should make for a great sound track. I also lost a week to a wrong part being sent. If not for these two factors, install would have easily taken under a day.
Below is a video showing the output of my initial drive with the system recording just after completing the install, so minimal configuration. It’s not intended to be exciting (it’s not), but potentially informative for anybody considering a VBOX or evaluating similar systems.
Edit (07.25.14): The following video shows a VBOX recorded session from a recent lapping day with the system fully customized for my car and configured for the track. There’s an issue with the speed ‘sticking’ that I need to look into and I didn’t have my audio plugged in for this session. I also cooled down the colors in Final Cut for this video.
VBOX is an in-car video and data acquisition system targeted at motorsports enthusiasts and racers who want to improve their driving by analyzing their driving after each session or event. I researched several different systems and opted for Racelogic’s Video VBOX system because it had most of the features I was looking for, was priced competitively, pre-sales support was responsive (which is a gauge for what I can expect post-sale), worldwide distributor network including two distributors in North America, good support site with monitored forums and regular updates, and an impressive product line.
The feature that attracted me to Video VBOX are:
- Multiple video inputs.
- Fully customizable video output.
- External stereo microphone input.
- CAN bus integration for getting at ECU data.
- High-resolution GPS and track mapping feature.
- Data stored to inexpensive, standardized SD card.
- Start/stop recording triggered by speed.
The one feature I wish VBOX had is HD video. There are other systems available with HD I opted for VBOX anyway because HD was a like-to-have for me, not must have. I purchased the VBOX lite, which is Racelogic’s least expensive system, as shown here:
I gave careful consideration to the installation prior to starting and opted as follows:
- VBOX stored inside glove box.
- 1-externally mounted microphone at rear of car (mono).
- 1-internally mounted microphone inside passenger cabin.
- 1 video extension cable routed back to roll bar.
- 1 CAN bus clip-on interface routed to driver-side foot well area.
- All other accessories, incl. power & GPS routed from glove box.
Layout schematic for all of the above is illustrated below.
VBOX Mounting Location
I considered two (2) locations for mounting the VBOX unit: Somewhere in the front trunk area and in the glove box. The biggest advantage of the front trunk is retaining full use of the glove box storage area, which the VBOX and all of its cabling pretty much fully occupy. However, I opted for the glove box for several reasons:
- Status LEDs able to be viewed without needing to get out of car.
- Easy access to record button if manual start / stop desired.
- No need to pop trunk to add / remove SD card.
- Easy to route cables in and out of glove box if needed.
- Close proximity to 12v power outlet (under dash).
- No need to route through wires through front bulkhead.
- Simply remove and store for safekeeping during offseason.
My overall goal was to minimize or eliminate need to make any modifications to the car in order to accommodate the system. By using the 12v power outlet I didn’t need to splice into any wires or tie into the fuse box. Racelogic also makes a clip-on interface that reads signals off of the CAN wires without needing to splice into them so I went this route as well. (More on the CAN interface below.)
The VBOX has a stereo microphone input and includes a splitter and two single channel condenser microphones so that left and right channels can be picked up at different points. I ran wires for mounting as follows:
- Inside cabin facing driver to pick up conversation and sounds hear by driver such as tires working. Also hoping that by pointing at driver from dash, wind buffeting will be kept to a minimum.
- External to car and hidden behind rear license plate facing downward. Not coincidentally, this also happens to be right over the exhaust tips.
I expect (hope) that this should make for some great audio tracks. Will probably require lowering exhaust channel level relative to cabin channel during editing in order to get a good balance.
My system accepts 2 camera inputs (more expensive models accept up to 4). Both are mounted from inside the vehicle:
- A high-resolution camera is attached to the windshield using a suction mount and faces forward across the hood of the car. This will provide an unobstructed view of the track and is the main video displayed.
- A low resolution camera is attached to the roll bar aiming at the driver from behind. This will be shown as an video inlay (picture-in-picture) and will be useful for accessing factors such as driver smoothness.
CAN bus signals are captured using Racelogic’s clip-on interface. This is nice for at least three (3) reasons:
- No need to alter the cars wiring harness.
- I was fairly confident I had the wires but not 100%. With the clip-on interface, no need to worry about hacking-up the electrical in search of the correct pair. Fortunately I got it right the first time thanks in-part to some thoughtful Internet posts.
- Non-physical interface for measuring signals means no chance of measurement affecting the signal and possibly causing CAN bus errors, which could in-turn affect vehicle operation.
The most obvious place to hook into the CAN signal was near the ECU since the pin-out schematic clearly identifies high and low CAN signals. However, it can also be picked-up of these same wires as they route up through the drivers foot well area near the fuse box. I opted for the latter because in the event of issues down the road, less stuff to need to tear into to diagnose and repair. (I apply this philosophy to all wire placement and routing considerations.)
The CAN bus interface is shown in the figure below and will be discussed in more detail with installation.
The bulk of the work involved with the install involved routing a microphone to the rear of the car. It’s a lot of work for just one (1) cable, but worth the effort in my opinion because it’ll return glorious audio tracks as opposed to the all too common wind-buffeting filled tracks heard on the Internet.
This is not a step-by-step guide so I’m only showing the basic flow. If you want to follow similar approach for your specific car, you can get detailed disassembly instructions on the Internet. Installing on a 2011 Porsche 911 GT3RS (997.2) and there was ample amounts of information on forums like Rennlist and Renntech that detailed anything I needed to know. For any Porsche 997 owners reading this, I’ll provide any 997 specific details that are not already amply posted about such as center console removal DIY.
CAN bus interface
A CAN interface is optional. Without it you’ll get the basics like video, audio, vehicle speed, g-forces, track mapping, lap timing. With it you can get a whole lot more data. What you get depends on your car. For my car (997.2 Porsche), I can get at:
- Lights on / off
- Reverse engagement
- Engine RPM
- Throttle position
- Parking brake engagement
- Road speed
- Brake position
- Steering direction
- Steering angle
- Wheel speed (RR)
- Wheel speed (RL)
- Wheel speed (FR)
- Wheel speed (FL)
- Clutch engagement
- Water temperature 1
- Water temperature 2
- Oil pressure
- Oil temperature
- Boost (my car is NA so does not apply)
- Gear selection
The VBOX lite only allows up to 4 CAN channels at a time, with the option to purchase up to 4 more for a total of 8 (purchased individually). I’m going to start with throttle position, steering angle, brake position, and gear selection. I’ll probably also purchase 1 extra for oil pressure.
With the VBOX unit you can get an unterminated CAN cable and wire directly into your system. But they also sell a clip-on interface that eliminates the need for splicing. It also guards against the VBOX system incidentally introducing any CAN signals onto your system’s CAN bus. I opted for the clip-on interface.
CAN bus clip-on interface and installation
If you’re using the CAN bus clip-on interface or if you have a Porsche 997 you may find this section useful if interfacing with your vehicle’s CAN bus.
The clip-on interface came with no instructions and it was immediately ambiguous to me regarding how to position the wires. The correct way in my non-humble opinion is to position the wires so that the surface area labeled CAN_H comes into contact with the CAN high wire when the shell halves are snapped together. However, some companies in an effort to make things easier for people outsmart themselves and just end-up making things more confusing. So I wondered did they mean for the upper half to read like a map for positioning the wires into the bottom as viewed during installation? Certainly, I’m thinking too hard about this but I did some checking after finding no documentation online and came across the promotion video for the interface showing the latter (reads like a map). Turns out the promotion video gets it wrong. (For BMW, which is the car used, CAN high is red-blue, and CAN low is red).
I contacted Racelogic support for clarification and they responded as follows (option1 is having the CAN high wire in contact with the surface area labeled CAN_H):
As for the ambiguity issue you are correct in thinking option 1 is correct. As we have had this question before I have contacted the developers of this and they are aware of this issue and are working on a new version that can be used either way round. Although we will have to make do with sticking to option 1 for now.
Also my opinion, I think they could save themselves some engineering investment and simply include a small piece of paper with the clip-on interface showing proper usage since it’s otherwise self-explanatory.
Also complicating my install was that VBOX sent me a clip-in interface for one of their higher-end (not VBOX Lite) which accepts a different style connector. Shown below is the other end of the cable for the interface I received, where as it should look like a PS2 connector from the outside. This added 1 week to my install while I waited on the part because it needed to be shipped from the UK. (Would have been longer if I didn’t foot the bill for overnight express which VBOXUSA was unwilling to do, so make sure you emphasize having them fulfill the order correctly for your system if ordering a VBOX CAN interface.)
Setup and Configuration
I’ve only just started to play with configuring my VBOX system. Except for reading the CAN data, everything was plug-and-play simple. Getting to where I could read the CAN data for my car took a little help from VBOX. Not getting anything at first begged the question if installation error or software configuration issue. I was very confident I had correct CAN wires and support clarified proper usage of the clip-on interface so either an issue with the clip-on interface itself or software configuration was my thought.
The issue turned out to be software configuration. VBOXUSA sent me a scene file for my car which had VBOX reading the CAN data; something I was unable to do using the CAN database file for the 997.2 Porsche. Different cars differ in how they use CAN to send data so you need model specific information which VBOX provides via their online vehicle CAN database. The database returns a file that gets read into the scene file loaded onto the VBOX telling it how to interpret the CAN signals.
The only other thing I needed to do to get the system ready for my initial (and successful) road test was aim the cameras. I purchased a small display that plugs into the AUX port on the VBOX and shows video in read-time. This makes setting up the cameras super easy. Just hold display in hand while adjusting each camera to desired position. The following figure is a photograph of the display screen:
Video showing trial run of system. This is with only minimal configuration so only minimal data is displayed and the brake pressure gauge needs reconfiguration. Goal of this drive was to simply check out video quality, confirm GPS working, etc. Just the basics.