Mbailey, here are my two Vipers to add, for your nice reference list.

2014 Viper TA (100% stock)
7.32 60-130 (2 shifts)


2006 Viper Coupe (Supercharged, N2O, 1200 rwhp)
4.61 60-130


Thanks,
Tony

 

shifts one the N/A car are seriously QUICK !!

 

plus the time of 7.32 for a stock car is bloody quick

 

Here's my 2015 Audi RS7 bone stock with approximately 1900 miles on the odometer.

9 runs total so far with the best run at 11.47 @ 121.8 mph. Half tank of 93 octane and weight with driver at 4765 lbs...

Here's the timeslip



Here's me weighting the car



And here's a pov video of the pass

https://youtu.be/9V8vI__FLrU

My 11.47 is backed by an other 11.48



I think this makes me the quickest stock RS7 currently!

The passes were made on Wednesday at Raceway Park in NJ.

Now I have a good baseline for when I decide to tune...

 

4765 lbs gulp

 

Anyone know about the internal workings of the vbox? I have a World record worthy 60-130 time, but this file is giving off errors. its the only file Ive ever seen give off errors using the Vboxverify website.

Im assuming the run would be invalid since it has too many faults.

A normal run looks like this:
VBox Storage ID = ID002042-1430289868-ANON
VBox MD5Sum = eccef96af6b254cd183b24058e51abd0
VBox optionFlags = 0
VBox File Type = DBN
VBox Sample Rate = 10.00 Hz.
VBox #-Records = 534.
Number of tests: 21
Number of potential performance runs: 4

And here is the WR run that looks like it was tampered with:

Date Conversion Error.
Filename = 'GreatAir.dbn'
vbHWID = ''
vbType = 2
fwVersion = '01.01'
fwBuild = '0008'
serNum = '05012448'
vbRaw = 'File created on 20/3/201x at 9:19:48 �� '
Warning[0000] = 'The parsed date was invalid'
Error[0000] = 'A meridian could not be found'
Error[0001] = 'Trailing data'
Date Conversion Error.
Filename = 'GreatAir.dbn'
vbHWID = ''
vbType = 2
fwVersion = '01.01'
fwBuild = '0008'
serNum = '05012448'
vbRaw = 'File created on 20/3/201x at 9:19:48 �� '
Warning[0000] = 'The parsed date was invalid'
Error[0000] = 'A meridian could not be found'
Error[0001] = 'Trailing data'

 

Try first to fix errors using racelogic app - circuit tools

 

Lost Marine - did you try just using the normal racelogic software and see if you can extract the run that way. I have done about 10 great runs over time that were unofficial because my louse of a vbox was playing up

 

Guys,
Neil from Switzer sent me some data a while back from their Goliath X GTR. Neil says the car gets 1700 whp on ethanol! These numbers seem to bear that out! 60-130 3.01s and 100-150 2.39s!!
Congrats to Switzer!!

 

Guys,
Member Prodigymb sent a very quick 60-130 of 5.80s in his AMS Alpha9 997.1
with a stock motor, 93 octane pump gas only (no meth), undercover performance tuned on a cobb. Congrats Mark!! That is really good for 93 oct!!!!!

 

I might know something about it.

I looked up this run, and everything seems fine to me. No errors in the logs. Can you be more specific about the errors you saw?

http://www.perfdb.org/vBoxFiles/ID00...N/summary.html


This happens due to a date conversion error. It happened because of those extra characters after the date in "vbRaw" message above. I didn't know I had left those error messages enabled.

It gets a little ugly when you're trying to figure out if tampering occurred. So here's what I did. I checked the logs of a bunch of different files from that device, from a bunch of different submissions. They all showed this same error. So I'd be inclined to say it's not tampering. Until...

I also checked the logs of a bunch of different devices that have the same firmware and build numbers as this device. None of those had this error. So that might lead me to think there might have been tampering involved. But why would anybody modify the date field?

Here's the date fields of other devices with the same firmware version and build numbers:
File created on 4/30/2011 at 8:53:08 AM
File created on 23/11/2010 @ 05:50
File created on 12/25/2010 at 7:09:58 PM
File created on 17/09/2011 @ 03:27

Here's the date field from the device in question. You can see the trailing characters after the date.
File created on 20/3/2012 at 9:19:48 ìì

But it's a tricky thing to call it tampered because there are so many different date formats by so many vBox devices. They even change date format based on firmware version in the same device (ugh). Here's example of different date formats even with the same firmware and build numbers.

So I don't really have an answer to this one. I'm not convinced it's tampering, and I'm not convinced it's not. I think I'll ask my contacts at RaceLogic to see if they can explain it.

 

sweeeeet, was that on the alpha 2871 turbos?

 

Mike, Here are a couple graphs from recent races.


0-186 14.97


100-150 3.75


60-130 4.37


This is my PB 1/4 trap 158.5mph



PB 1/4 ET's

 

30-130 mph in 6.7 secs is pretty incredible in a 6MT

 

Here's a 3.6 100-150 that I pulled tonight rolling up some bikes.