the accurate data will be from satnta pod! George!!!!!! do we also get a 0-60 ? I seem to recall some "strips" just give 1/4 miles... some include 0-60.....

Any metric times (i.e. to 100kph)? I'm guessing it's an extra 0.2 or so.

http://briskoda.net/forums/topic/209657-14tsi-14mile-leaderboard

Reaction Time.

 60 foot.

 1/8 mile .

 1/4 mile

Terminal Speed.

 

Very good times with Air Intake & Tuning box and inexpensive mods.

(very good How to on Mods.)

http://briskoda.net/forums/topic/221248-vrs-powereds-skoda-fabia-vrs-tsi-tmc-itg-2116-bhp

See for ELM327 post '30

Edited 26 January, 201511 yr by goneoffSKi

See the Video & the 0-100km (62.14 mph) time they give for an estate.

*TC is Off, and it is a good surface for traction.*

http://performancedrive.com.au/2012-skoda-fabia-rs-wagon-review-video-1703

Edited 26 January, 201511 yr by goneoffSKi

Just another word on those adapters' accuracy: The way you do read the speed does affect the result in different ways. If you select Speed (OBD) it may read quicker but then the 60 mph is not really 60 but more like 56-57mph. This is enough to trim 0.2-0.3s off the time already. On the other hand, if you select Speed (GPS) it is more accurate in terms of speed but slower in terms of measuring intervals so it may lose a bit on the beginning and/or ending. Both options have inherent flaws so it's not really as if you've got yourself a proper v-box. They are indeed useful to get a good idea of how fast is the car but I wouldn't really compare times measured with them against official/v-box confirmed times as from my experience they include a +/- 0.5s uncertainty.

Yep, wanted to mention that as well, if you hold a stopwatch and hit stop when you think you see 60 mph on the speedo you are probably some way off. They're a great comparison tool, useful for fault and general obd reading that is not crucial to be precise down to the tenth of second.

Just to throw a contrast. I know someone that works as a race engineer for a motorsport team. He thinks the obd adapters on things like timings are pretty damn accurate outside of natural spedo tolerances. It's simply a register of first speed to a preset end speed, there is very little to go wrong.

Personally, I think everything needs to be taken with a pinch of salt, but the adjustment required on something like this will be so minimal that it can be ignored.

When you put different size tyres on a Fabia, say 215/40 R 17 instead of 205/40 R17 you might find the Speedo reading can be pretty accurate when the Total Diameter / Rolling Circumference is actually greater.

But measuring the 2 sizes side by side is required because some 215/40 R17 are not taller (greater Rolling Circumference).

 

You might also notice if you set the Trip,  

and set Trip Maxidot, that after a bit of a trip they do not turn over to a Full mile at the same time.

The Maxidot rolls over to a full Mile after the Trip has possibly.

 

http://kouki.co.uk/utilities/visual-tyre-size-calculator

 

& for official VWG Manufacturers times.

the Skodas come standard on 205 & the sister cars on 215's,

even the Seat Ibiza 1.4TSI 150 ps FR came on 215's

Edited 26 January, 201511 yr by goneoffSKi

Any metric times (i.e. to 100kph)? I'm guessing it's an extra 0.2 or so.

 

Yes that's about right from what I've measured.

 

 

Just to throw a contrast. I know someone that works as a race engineer for a motorsport team. He thinks the obd adapters on things like timings are pretty damn accurate outside of natural spedo tolerances. It's simply a register of first speed to a preset end speed, there is very little to go wrong.

Personally, I think everything needs to be taken with a pinch of salt, but the adjustment required on something like this will be so minimal that it can be ignored.

 

Well don't get me wrong, I'd love this to be as accurate as it can be because after my remap I'm getting some amazing in-gear acceleration times that easily compare to stock cars around the 300bhp mark. But I'm only saying this because once, out of curiosity I had a look at the actual recording log (timestamp+value) and I saw that the speed was not updating as quickly as I would like. Basically you would see something like:

 

Time - Speed:

00:01:000''   -  60.5 km/h

00:01:200'' -  60.5 km/h

00:01:800"   -  63 km/h

00:02:000"   -  63 km/h

 

and that was on full throttle so it's not possible that speed was "jumping" like this.

 

As I said they're probably pretty close to the truth but I would still think they may be off a few tenths of a second. Agreed that's a small deviation not far off from reality but when you're trying to see whether it's 6.5 or 6.3 or 6.0 it makes a difference I think.

Edited 26 January, 201511 yr by newbie69

I have one and dash command. Was messing around in my cthe the other day and managed 6.1. Still didn't get 1st gear launch 100% right either

Hi,great it saves me doing it now. (still might buy it out of curiosity)

I have one and dash command. Was messing around in my cthe the other day and managed 6.1. Still didn't get 1st gear launch 100% right either

have you got a link please to the one you have got and (dash command)is this an android app thanks I want to see if I can beat your 6.1 time ha ha.

Dash command is both android and ios. Just search for it in the relative app store. All you need after is a bt/wifi odb2 adapter. http://pages.ebay.com/link/?nav=item.view&id=331206015268&alt=web

Make sure the odb2 adapter works with your phone (iOS or android).

I downloaded Rev lite to check the connectivity between them both its good as its free.

Dash command is both android and ios. Just search for it in the relative app store. All you need after is a bt/wifi odb2 adapter. http://pages.ebay.com/link/?nav=item.view&id=331206015268&alt=web

thanks