Good to see ya around these partsmy friend.

 

driftbox devices are extremely precise as long as they have enought sats to receive. that's a fact. Robert, try an external antenna, that will improve quality alot.

 

I will be impressed if he gets a 9.0 60-130 clean run.

 

That is my point. Either it records the run or it can not. These guys make this junk up as they go along. I have come to expect it.

 

I also sent you an 8.0 run from a different file. Is that one also BAD?

 

Where have you posted that you only tolerate a certain number of drop outs before you conclude that the run can not be posted? I see slope as a criteria but not the drop outs.

 

Are you serious?

Quote:

Originally Posted by Divexxtreme

…all submitted data must be reviewed for accuracy and approved by a Subject Matter Expert (SME) before the time is posted.

If there are dropouts in the run, I can not confirm the accuracy. You had 668 dropouts on the .dbn file you sent…558 of which are totally unaccounted for! What part of that do you not understand?

Normally, when someone sends me a run that’s been corrupted (either by sat drops or something else), I immediately let the person know and then they go out and get some new runs in. You're the only person that has ever whined about it.

But then, you're also one of the only people that consistently posts your runs on the forum before they've been verified. When you do that before I've had a chance to review them, you're taking the chance that they won't be approved. So that's on you...not me.

Let me explain something one more thing to you. I created the ¼ mile and 60-130 list so we forum members could compare our car's performance. I do it, not because I'm required to, but because I'm trying to do something nice for my fellow 6speed members. Everyone else seems to appreciate it but you (as seen by your sarcastic comments below).

You consistently run downhill (trying to game the numbers), and now your crying that I won’t approve a run file that literally has 10 times more sat dropouts (at least!) than any file I have ever seen!

Quote:

Originally Posted by robertp

I know that some people on this board do not like the fact that I get more out of less car, but that facts speak for themselves.

 

I just spoke with the guys at Vbox USA about satellite drop outs and this is there take on my file. You can call VBOX USA at 248-655-0557 and talk to John to be educated on satellites and the Vbox if you are going to manage this section of the forum with any integrity.

If you open a file and it states that the file has satellite drop outs you can repair the file with the repair tool. If you do so, the integrity of the file is intact. Since the Vbox and the satellites it communicated with are in a time code sequence any drop outs will be extrapolated into the file during a file repair.

During a 60 to 130 run, if the satellite gets a good start time (sets the time code when you hit 60MPH) and end time (sets the time code when 130 MPH is achieved) it doesn’t matter how many times the satellite drops out during the run, the time is VALID. It only needs to know the start and stop time.

Another example is if you are on a track and logging lap times, the Vbox does not need to be in constant contact with the satelight during the entire lap. If you go under a bridge or in a tunnel, the time will still be VALID. It only cares about the start/finish portion of the track. Same rules applies to 60 to 130 times.

Stop the bull and post the time!

 

Robert,

I think your car is just getting faster and faster on its own...

MK

 

I see, this is why you do not like my times. So I can not post any performance related stuff unless you approve it first?

 

Ouch, that hurt more than my weekly chemo.

 

Quote:

Originally Posted by robertp

I just spoke with the guys at Vbox USA about satellite drop outs and this is there take on my file. You can call 248-655-0557 and talk to John to be educated on satellites and the Vbox if you are going to manage this section of the forum with any integrity.

First off his name is Jim. Not John. And yes, I've spoken with Jim about the VBOX numerous times in the past. I also just sent him your file, and he agreed that you had multiple satellite dropouts on your 7.x runs (the first two).

We exported your runs to Google Earth and it looks you were on 261 during your first 2 and went under 4 overpasses (I won’t post the names of the roads here). The 3rd run you were on a different road (begins with an ‘I’) and it was clear. You ran an 8.38 on that run.

Quote:

If you open a file and it states that the file has satellite drop outs you can repair the file with the repair tool. If you do so, the integrity of the file is intact. Since the Vbox and the satellites it communicated with are in a time code sequence any drop outs will be extrapolated into the file during a file repair.

Wrong. When I opened the file it stated there were 13 dropouts. I repaired them (like I always do) but the other 600 or so still remained in the summary section. Even after the 3 runs were trimmed from the rest of the file, there were 150+ dropouts remaining in the first 2.

You are not telling me anything I do not already know.

Quote:

During a 60 to 130 run, if the satellite gets a good start time (sets the time code when you hit 60MPH) and end time (sets the time code when 130 MPH is achieved) it doesn’t matter how many times the satellite drops out during the run, the time is VALID. It only needs to know the start and stop time.

When your graphs show your G’s spiking straight up in the air in-between shifts (like your first two runs did), that does NOT qualify as a VALID run. G’s go down between shifts on a clean graph, not up. Sorry.

Quote:

Stop the bull and post the time!

The bull has now been now stopped. I’m done reviewing your runs and they will no longer be posted on the 60-130 list. I do this for fun and to be helpful to members, and I don’t appreciate having my integrity questioned by someone who doesn’t get his way.

Quote:

I see, this is why you do not like my times. So I can not post any performance related stuff unless you approve it first?

LOL…I couldn’t care less about your times. They’re only times, just like anyone else’s. The problem is you post them as if they’re already verified and then when they don’t get approved…you get upset and start *****ing.

It simply would have been better for you to wait until they were officially approved before posting them in order to prevent possible disappointment.

 

there are roughly three states of quality your data can have: useless, poor or good. If there are any dropouts within or at the borders of the single run, the run is usually useless.
then you can have a poor signal with only 4-5 Sats which is acceptable and I would say valid but not preferable, and in most times the result is not for your advantage. especially if distances are taken into account, they can appear longer than they are.
third would be sat count averages above 6.5 which means there isn't any doubt your data is extremely precise and valid.

why do you complain? get an external antenna for a few bucks and do the runs again. nothing easier than that.

 

Robert
You to do these runs every week just go get another one already.

 

Yes, that is what I posted above.

"During a 60 to 130 run, if the satellite gets a good start time (sets the time code when you hit 60MPH) and end time (sets the time code when 130 MPH is achieved) it doesn’t matter how many times the satellite drops out during the run, the time is VALID. It only needs to know the start and stop time."