Redline Software Update

[dslrip32]

So is the Damn thing fixed or not

According to Escort it is fixed. But it has not been publicly verified yet.

[kpatz]

Well, I think I just had my first confirmed Redline I/O glitch with mine.

Was coming back to work from lunch, on a 2 lane road. A statey I/Oed me with Ka. The V1 went wild, the Redline stayed silent. This was a 30 mph road with him coming the other way, and he was probably 100 yards away when the V1 went crazy. Being a statey, it was most likely 34.7. Shortly after he passed, I took a right and he probably turned off his radar as the V1 stopped alerting. Redline didn't make a peep.

So let's hope Escort has a fix soon. This could have been deadly if I was speeding and was relying solely on the Redline.

[TSi+WRX]

^ I dunno....

Currently, what's described as the "glitch" is a signal that was picked up, but then "dropped" somewhere through its normal alerting, and then again alerted to.

Your case almost seems like the V1 was interfering with the detection capabilities of the RedLine....or, otherwise, a description fitting a Quick-Trigger "miss."

This is why I've said that the "glitch" may only be capable of being reproduced under "controlled" circumstances - where there is a co-operative party behind the RADAR device, to let us know that it was, indeed, engaged for the full duration of the experiment, but that the RedLine managed to "drop" the signal during that time period.

[kpatz]

Well, then there's two glitches (or they may be related):

1. An alert is sounded, then it is dropped.
2. It doesn't alert at all to an I/O shot, or the alert is delayed for several seconds. IMHO this is far more serious than dropping an alert.

This wasn't a QT shot, as the V1 stayed full scale for several seconds. The Redline had plenty of time to alert, but it never did.

I've had no evidence of the V1 interfering with the Redline to this point, plus others have seen the same thing running the Redline by itself.

[ELVATO]

Yea, there are 2 "glitches" that we've seen, both described by kpatz. That is not including QT, since it seems to affect most of the Belscort line.

[thestaton]

Can I get a cliff notes because this is what I'm taking from the thread after a quick 5 minute scan.

Escort reps told potential customers the issues reported had been resolved in a software update. When in fact there never was a software update?

Is that pretty close?

[CJR238]

Can I get a cliff notes because this is what I'm taking from the thread after a quick 5 minute scan.

Escort reps told potential customers the issues reported had been resolved in a software update. When in fact there never was a software update?

Is that pretty close?

Basically yes. Seems like the CS only told people from RD.net there was a fix.

Basically if its broke they tell us there is a fix.

IMO, there was nothing wide spread, just the first few.

[dslrip32]

Can I get a cliff notes because this is what I'm taking from the thread after a quick 5 minute scan.

Escort reps told potential customers the issues reported had been resolved in a software update. When in fact there never was a software update?

Is that pretty close?

Basically yes. Seems like the CS only told people from RD.net there was a fix.

Basically if its broke they tell us there is a fix.

IMO, there was nothing wide spread, just the first few.

First few what? I would not say "hundred" as the serial number span is large, maybe first few thousand.

[TSi+WRX]

Well, then there's two glitches (or they may be related):

1. An alert is sounded, then it is dropped.
2. It doesn't alert at all to an I/O shot, or the alert is delayed for several seconds. IMHO this is far more serious than dropping an alert.

This wasn't a QT shot, as the V1 stayed full scale for several seconds. The Redline had plenty of time to alert, but it never did.

I've had no evidence of the V1 interfering with the Redline to this point, plus others have seen the same thing running the Redline by itself.

and

Yea, there are 2 "glitches" that we've seen, both described by kpatz. That is not including QT, since it seems to affect most of the Belscort line.

Ah, I was not aware of that, kpatz and ELVATO. Thank you - both - for correcting me and for bringing that to-light.




----

Can I get a cliff notes because this is what I'm taking from the thread after a quick 5 minute scan.

Escort reps told potential customers the issues reported had been resolved in a software update. When in fact there never was a software update?

Is that pretty close?

Basically yes. Seems like the CS only told people from RD.net there was a fix.

Basically if its broke they tell us there is a fix.

^ Not quite.

thestaton, what happened, chronologically, was this (to anyone involved, first-hand, in the issues, please do chime-in to correct me! I'm going by recall, alone!):

Cbr/ELVATO's tests revealed a potential "giltch" in how the RedLine would "drop" an alert, after having initially reported it, as well as (and it seems as if I totally missed this, earlier ) that, sometimes, it would just plain not alert at all (non-Q/T scenario, for which we all know that there currently exists a weakness).

Cbr sent the unit back, on the promise of a "Priority" repair, "overnight," essentially, on the basis that there was a known "software" problem (which was then "not an issue, but quickly becoming one") and a proper "fix," as disclosed by an Escort representative, over the phone, after said rep. had consulted with his direct supervisor.

The unit sat for over a week, until Cbr again called to ascertain what was going on - only to find out that his unit has not yet been repaired, due to lack of diagnosis/ability to repair. While he was posting the update to us, he noticed that the Escort representative on Escort Radar Forums had maintained that there was no such "software" fault nor was there a pervasive fault found with any RedLines then-to-date. Upon reading this, which is in virtual direct contradiction with what he'd been told, over the phone, Cbr lost faith (I would have, too, to be frank - I don't blame Cbr for his actions, at all), and cancelled his order, outright.

NCSPEEDER, the OP of this thread, then, on 10/28 at around 9AM, posted that he'd conversed via the Live-Agent function, with an Escort representative, to try to resolve his "Service Required" concern on his new RedLine, and mentioned that he'd also read about the Q/T and "signal-drop" concerns to this rep., who then reported that there was now a "software fix" for those issues.

At 2:47 PM, I cross-posted the above to the Escort Radar Forums, to await response by their representatives.

When their representative responded, it was again to say that there was no pervasive indicated by these reported "glitches," underlying issue with the RedLines, and that there was no recognized "software fix," and also that the reps. who had reported such were in-error. Furthermore, that efforts were being undertaken to get their C/S reps to coherently and properly describe efforts undertaken to repair RedLines, so as to not convey that supposedly improper information.

Unfortunatley, as it later appeared by dslrip's contact with Escort, in a logged session, it seemed that within but 4 hours of such a meeting supposedly was called, to caution their representatives to "be more careful with their terminology," Escort's representatives, off-Forum, were still saying that there was a recognized "glitch," and that there was a "software fix" for such.

When confronted (REF: ? RedLine Software Update ? - Page 2 - Escort Radar Forum , posts 19 and 20), Escort's representative on the Escort Radar Forums insists that there is no such concern nor such a fix, but did not address, at all, the still-present problem of lack of consistency in what one aspect of C/S was telling us (i.e. via the Forums) via the other (i.e. off-Forum, be it via electronic or voice communication).

And that's where things stand, to-date.


----

IMO, there was nothing wide spread, just the first few.

^ Again, the statistic can be spun both ways.

What Escort would like us all to think is that the problems were isolated to only a few units - out of hundreds or even thousands sold. And in so far as we, as a community, have been able to see, yes, we've only had a handful of such incidents.

However, the flip side of that equation is to ask a simple, logical, question: what are the odds that the now some half-dozen or so units that are known to be in-circulation in our community, with a couple which have been so lucky as to have been exposed to actual controlled testing scenarios, all have such "glitches." The odds of that happening is pretty astronomical, no?

The statistic can cut both ways - without knowing exactly what's going on, both interpretations are valid.

[EscortRadar]

Well, then there's two glitches (or they may be related):

1. An alert is sounded, then it is dropped.
2. It doesn't alert at all to an I/O shot, or the alert is delayed for several seconds. IMHO this is far more serious than dropping an alert.

This wasn't a QT shot, as the V1 stayed full scale for several seconds. The Redline had plenty of time to alert, but it never did.

I've had no evidence of the V1 interfering with the Redline to this point, plus others have seen the same thing running the Redline by itself.

It is very possible that this was interference caused by operating these detectors together. The RedLine will not interfere with the V1, so the V1 will operate normally, while the RedLine is most probably having to deal with emissions from the V1.

We have not seen a problem with the RedLine not detecting I/O radar. If you like we can take a look at your RedLine. Please contact our customer service department if you would like to set this up.