Thursday, July 30, 2009

Escort Redline versus Valentine One Reviews: End to a Long Debate?

veilguy's escort redline vs. valentine one debate

Escort Redline vs Valentine One Review: Both Stellar Performers

 Updated: 07-08-13:

Escort Redline versus Valentine One Review

Updated Escort Redline Gets Advanced Feature Set visit Escort Redline Review.

Escort Redline Raw Sensitivity versus Potentially "Higher" False Rates

I think it is going to be very interesting to see how the new Escort Redline ($499) is going to look to some [other] reviewers when historically the Valentine One ($399)—which also has possessed high sensitivity levels (and coupled with very quick response times) but [came with] higher "false" alerts as a consequence—has been historically hammered [by] some reviewers for its uber-sensitive behavior(s).

If, as I expect, the new Escort Redline will perform in the same vein ("vain") as the venerable Valentine One (but with potentially even higher sheer [radar detection] performance), it will mean that the Escort Redline will most certainly be a very significant and exciting product (a departure, really) from Escort, however, I believe the Passport Redline has the potential to create a sort of a conundrum for some of these [same] reviewers who have historically been critical of the Valentine One for the same type of performance (although to its credit, Escort has been very clear about its intended behavior and purpose).

I believe this is going to be very interesting to see how this plays out online, will there be moral clarity/consistency, or not?

If the Escort Passport Redline, is praised for its high raw performance even while it comes with a higher level of potential "falsing" then what does it mean for all the historical reviews of the Valentine One which have historically criticized the V1 for possessing the same type (or similar) behavior to radar sources (from bonafide police radar and not)?

I, for one, have always appreciated what the Valentine One is/has been and its design approach philosophically and I welcome Escort's decision to offer a windshield-mount radar detector possessing potentially the same philosophical design elements while remaining (myself) entirely consistent on this matter.

Here's are just two examples of the inconsistencies that have existed with some other reviews.

For a long-time, the Valentine One was the most expensive windshield-mount radar detector (although its price point has stayed unchanged at $399). Reviewers have always hammered the V1 on its high price...that was until Escort and Beltronics started introducing products that were priced even higher. Do you recall reading any reviews about those products being excessively priced? I don't recall seeing them.

Remember the review calling the V1 the "chicken-little" of radar detectors and the subsequent references to that review from Automobile Magazine? Are you catching my drift? How about the notions of the V1 as being a "noisy" and "old" radar detector compared to the "latest" [quiet] model like the Passport 9500ix.

Having journalistic integrity is more important to me than winning any popularity contest from my readers or from the manufacturers (whose products) I review, no matter what price I may have paid for having that conviction.

If, indeed, the Escort Passport Redline may finally put to rest this long-raging (longest and most passionate?) debate in our very small industry (although laser detection performance will very likely remain a decided win in Valentine's favor) with both the manufacturers and their [very] passionate group of consumers, it will still not detract from my appreciation and respect for what I believe has been one of the most purely designed pieces of consumer electronics for nearly two decades, the V1.

Cool Runnings, Peace be da Journey...

Please support those that support this blog:

Recommended Purchasing Sources for the Redline:

Related Reading:
Related Online Discussion:
Veil Guy

Tuesday, July 28, 2009

Escort Redline: Extreme Escort Redline Performance in a Windshield-Mount

escort redlineEscort Redline Windshield-Mount Radar Detector

New Escort Redline Radar Detector Officially Announced Today by Escort

Escort Redline Radar Detector

Updated: 06/01/2013


Update: Escort has recently released an improved version of the Escort Redline.

Given Escort's public announcement of the up-and-coming Escort Redline radar detector, I am heartened to report that the Escort Redline radar detector will be all about performance with an emphasis on no-holds-barred sensitivity and (I hope) quickness to alerting and a de-emphasis on being heavily filtered (to reduce falses).

It sounds like the new Escort Redline model will finally unlock the potential of the RDD-undetectable M3 platform (the same used in the Beltronics STi Driver, Passport 9500ci, and Beltronics STi-R models) in a windshield-mount.

But, beware, this is not your father's Escort.

While the Escort brand (with the exception of their blistering $1600 Escort Passport 9500ci custom installed remote) has historically placed an emphasis on being the quietest (but still highly sensitive) radar detectors (as most recently manifested in the Escort Passport 9500ix), Escort appears to have finally given the "red-meat" to those asking for Passport 9500ci-like performance, but in a windshield-mount with the Escort Redline.

Generally, this is something that has been historically accomplished by the sister company Beltronics brand with the models like the venerable Beltronics STi Driver and, of course, the Beltronics STi-R custom remote radar detectors.

I am pleased that with the Escort Redline, Escort customers will now have a viable alternative to the otherwise Escort Passport 9500ix (a radar detector with an emphasis on filtering and being quiet).

Now I am waiting for the addition of two things, GPS capability (for photo detection and variable sensitivity) and Shifter ZR4 interfacing capability.

I still believe that model would be the ultimate windshield-mount radar detector.

I trust, in time, we'll see that model, as well.

Once we get our hands on a production version of this new Redline detector, we'll follow-up with a detailed and thorough review, as always.

In the meantime, it appears that with the Escort Redline, extreme performance appears to be finally coming in a small package...but again, this radar detector won't be for everyone. You have received your warning.

Gentlemen (and ladies), start your engines, the REDLINE is coming, the REDLINE is coming!

Related Topic:
Related Online Discussion:
Veil Guy

Monday, July 27, 2009

Photo Enforcement Safety Benefits: Separating Fact from Fiction

Speed Camera Photo Enforcement

Photo Enforcement Safety Benefits: Distinguishing Fact from Fiction (Part II)

Evaluation of the Executive Summary of the Report Entitled, Evaluation of the City of Scottsdale's Loop 101 Photo Enforcement Program, Draft Summary.

Updated: 28 JUL 09, 1840EST

In my previous blog post, I laid the groundwork and context for this series of related posts.

In this part, I look at the Executive Summary of the preliminary analysis results of the fixed speed-enforcement camera demonstration program (SEP) that was "conducted" on Arizona State Route 101 (a.k.a. Loop 101) during the period of January 2006 through October 2006 (a duration of approximately 10 months).

The stated purpose of this "evaluation "program was to quantify the following five elements:
  • The impact of the SEP (photo enforcement program) on speeding detections (76mph or faster)
  • The impact of the SEP (photo enforcement program) on average speeds
  • The effect of the SEP (photo enforcement program) on traffic safety (ie; motor vehicle crashes)
  • The expected economic costs and benefits of the SEP (photo enforcement program)
  • The financial public perception impacts of the program
The "evaluation" was administered (but not conducted) by the Arizona Department of Transportation (ADOT) and utilized data from a variety of sources, namely the Arizona Department of Public Safety (for crash report data), ADOT itself (for data, traffic volume, and speed data), the Arizona Crash Outcome Data Evaluation Systems (for crash data and crash costs), the National Highway [Traffic] Safety Administration (NHTSA) and Redflex (for detection rates and traffic speeds).

In essence, the vendor standing to benefit most from a "favorable" outcome of this "evaluation" program, was Redflex itself. Does this sound a bit like asking the proverbial fox to guard the hen house?


OK. Here is where the fun begins.

The evaluation program was to look at four key time periods:
  • The before SEP (photo enforcement program) period
  • The SEP (photo enforcement program) warning period, only warnings issued to drivers
  • The SEP (photo enforcement program) violation period, actual citations issued to drivers
  • The after SEP (photo enforcement program) period, system no longer utilized during evaluation study
The Scottsdale SEP program employed 6 speed cameras on a 6.5 mile section of Loop 101 within the city limits of Scottsdale.

Now keep in mind the primary objective of the SEP program was to assess potential safety and cost benefits (of reduced speeding detections) in terms of an assumed consequence of overall reduction of crash and injury rates.

The very periods likely to have the highest rates of crashes (particularly multi-vehicle accidents or MVAs) or associated injuries are periods of high vehicle density, like those during morning and evening rush-hours, for obvious reasons.

Would you be surprised if I told you that those periods were specifically left out of the speed detection portion of the program?

The reason? Simple.

The report itself stated that during peak-hour traffic, speeds were constrained by congestion, and therefore it was highly unlikely that high speeds (defined as an excess of 11mph over the PSL of 65) were even possible!

For this "reason" speed data were discarded or not measured. In other words, the times when crashes were potentially at their highest rates, speeding could have not be a direct causation factor, but other dynamics were more likely to be, such as excessive traffic density, driver inattentiveness, poor vehicle maintenance, and/or inadequate highway engineering designs.

I find this a remarkable admission.

I suspect had that data been included, the overall "beneficial effects" of "reduced crash rates" as a they were related to speed (ie; the positive effects of the SEP program) would be have been futher marginalized.

For convenience and for the sake of Redflex being able to call their program a "success," speed data from the most dangerous periods were completely ignored! Furthermore, the report stated that empirical data sets were either extremely limited or completely non-existent.

To make up for these deficits of real empirical and concrete (independently generated) data, the "authors" instead relied upon limited data (from another section of the highway and not even in the city limits of Scottsdale!) and the reliance on complex statistical models, instead, the kind that only individuals with Ph.Ds would use.

By using data from an entirely different portion of the highway and with a reliance on "hocus-pocus" math, the underlying integrity of the report's conclusions was severely undermined.

As if this wasn't enough...

Even with the limited data and the massaged statistical analyses, their findings suggested an increase (33%) of rear-end type multi-vehicle (MVA) crash-rates (not at all surprising considering the unsafe dynamics these photo enforcement systems create, such as "traffic porpoising"), though the report also suggested a somewhat paradoxical finding that the related injuries were reduced (by 12.57%).

In reality, one would expect injuries associated with such crash-type (along with offset or head-on collisions) to be of the most serious nature (ie; spinal/neck).

The executive summary also suggested that increases in these rear-end crash types were swapped for decreases in other types (ie; potentially less severe ones). In plain english, this meant the crash reductions did not necessarily occur, but different (ie; more severe) crash types, did.

I find this an even more remarkable admission.

However, the report did indicate that this comparison of the program evaluation periods to the "before program periods" did not consider other factors that could have or would have accounted for the varying accident rates observed or calculated, such as weather or other roadway conditions (like construction zones or lane restrictions).

Even with its limited amount of concrete empirical data, the report basically concluded that the SEP program reduced average speeds by approximately 9.5 mph, during its implementation.

Now that may sound like a lot until one one considers that highway posted limits should be set to the 85th percentile of speed (according to ITE engineering standards).

Therefore, if Loop 101 had a more appropriate posted limit of 70mph or 75mph (again, only obtainable during non-peak times), then these "speed detection reductions" would have be entirely irrelevant.

Stated another way, it appears to me that the SEP program only confirmed that the appropriate PSL (posted speed limit) should be raised in accordance with normal traffic flow rates (and that it remains 5mph to 10mph too low).

The report's executive summary of the SEP report does "come clean" in certain respects:
  • The "results" were based on small and incomplete [data] samples. (ie; insufficient data)
  • The "results" were based upon incomplete time (ie; insufficient time where random fluctuations of crash were common and could have influenced the results substantially)
  • Crash result trends were made at another site and crash data was used from high-peak periods (ie; rush-hour) even though speed detections were ignored for same periods.
Another interesting golden nugget suggested in the executive summary of this preliminary report of the 101 Loop SEP evaluation program was the admission that the highway of Scottsdale 101 (Loop 101) was already statistically safer to drive than other highways throughout the country!

Perhaps, this was the report's most remarkable admission for several reasons.

This acknowledgment, suggests the obvious: that speed, in-and-of-itself, is/was not a major contributor to highway crash or injury rates or has a limited adverse impact on overall highway safety.

Why would a city that was being actively lobbied at the time by Redflex and/or ATS conduct such a test [for/with] these very same companies who were (at the same time) forecasting huge potential profits from 'exploitation' of the marketplace?

Why would the findings (ie; conclusions) from this preliminary report be used to drive legislative policy nearly two years before the final report was to see the light of day?

Answer (to both questions): Follow the money.

How the SEP could be described as an "unqualified" success (by others not financially connected to its findings) would be a bit of a stretch.

How the report concluded (as it did later) that an increase of 33% in rear-end crashes as a result of the SEP was a "negligible" increase and an "equitable" exchange for less-severe accidents, would be a bit more than a bit of stretch.

That's enough analysis for now, because if you are like me, your head may dizzy from all the spin.

Related Reading:
Related Online Discussion:
©2009, all rights reserved. no portion of this article may be reproduced without expressed consent of the author.