• Redline Software Update • Welcome to the RadarDetector.net forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please,!

If you have any problems with the registration process or your account login, please contact. • If this is your first visit, be sure to check out the by clicking the link above. You may have to before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. 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. Tmpgenc Authoring Works 5.1.1.55 Keygen Rar Password. Redline didn't make a peep.

Feb 23, 2015 Redline Firmware Update. So you are saying that Live tried to update your Redline. Relying on Detector Tools to check for updated software only. RedLine partners with the top brands in RFID to provide you with best-in-class RFID software. RedLine has a trained team of experts on hand who are able to solve your specific challenges with RedLine Solutions' software.

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. 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. Well, then there's two glitches (or they may be related): 1.

An alert is sounded, then it is dropped. 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. 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. Well, then there's two glitches (or they may be related): 1. An alert is sounded, then it is dropped.

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.

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.