MAX 360 updated to v1.12/1.9

[Heywood]

Yea, I get that. However, I did not place/post Jon’s number two reason as first choice (crush/hurt Escort) like you did. Why are you doing the testing and work? Trying to get to the bottom of things, or are you trying to do you part to hurt Escort (which taints any results)? My goal.. Get to the bottom of all this, no added agenda.

I haven’t had to put too much work into it. It didn’t take too long to see the issues with the amount of threats and RF pollution I see daily.

Everything I’ve run into with the 360C I’ve actually documented and video’d. I’m not doing anything to hurt Escort. The 360 is doing that on it’s own.

You don’t see me complaining about the R-EX do you? I’m only commenting on this last 360 FW which I believe is the culprit to its instability/ unpredictability.

I’d like to get to the bottom of it. It’s a $1000.00 detector here. That’s 3/4 of someone’s paycheque making $25.00/hr over 2 weeks.

 

[Brainstorm69]

Ah, it is the arrogant, non communicating (except on forums), greasy hair, pony tail cubicle punk, software folks ruining things for another company. ER must have also promoted some in executive positions charge, or oblivious biz management running things?

@DrHow - I must be slow today or something. I've read your post multiple times, but the encrypted message isn't coming though. lol

All I was trying to say is that IMO Escort is much too eager to tell people that the problem they are experiencing is a) something they never heard of before (even when it's been seen by multiple folks on RDF, who have probably also mentioned it on ERF) and b) somehow hardware related (and therefor specific to their unit, which btw needs to be serviced), rather than an issue with the fw (and therefor affects all units). How many times did they say they fixed the lock-up problem on the Max 360 S#79? They started saying that with fw 1.7, and I still had the problem through fw 1.11 (that's 5 fw revisions if you're counting). The jury is still out on 1.12, but I was able to run it for 2 weeks without one (although I did have one weird semi-lockup).

I could be wrong. Maybe ER is a great software company that is plagued by hardware manufacturing QC problems. I just doubt it, and the evidence suggests otherwise when multiple members here have had to send their units into ER multiple times to fix problems that Escort said would be fixed by servicing, but somehow don't seem to be fixed when they get them back.

 

[Vancity23]

Ya..... I had a variety of issues with it.

1. MRCD false’s.
2. It did pretty poor on the MRCD test.
3. Missed active MRCD trap
4. Ka lock up/ sleeping.
5. Threat navigation wouldn’t countdown and freeze until another alert finally came on.
6. It was giving me live mobile radar alerts even though it wasn’t connected to wifi/BT/ or Escort live. It was in its own.
7. Hit and miss on actual K band lockouts. It was like “Forest Gump“ and his “Box of Chocolates” analogy. “Ya Never Know What Your Gonna Get”.

This was all in about a week and sparingly used. It’s on the shelf. I can’t trust it right now....... but hey! No laser falsing.

So other than items 1-7 it’s a pretty good RD?

 

[Dodgediesel]

Sure would be nice to have a update to fix these concerns. Everytime I see a response I'm hoping it is an update.... LOL

 

[timark251]

@DrHow - I must be slow today or something. I've read your post multiple times, but the encrypted message isn't coming though. lol

All I was trying to say is that IMO Escort is much too eager to tell people that the problem they are experiencing is a) something they never heard of before (even when it's been seen by multiple folks on RDF, who have probably also mentioned it on ERF) and b) somehow hardware related (and therefor specific to their unit, which btw needs to be serviced), rather than an issue with the fw (and therefor affects all units). How many times did they say they fixed the lock-up problem on the Max 360 S#79? They started saying that with fw 1.7, and I still had the problem through fw 1.11 (that's 5 fw revisions if you're counting). The jury is still out on 1.12, but I was able to run it for 2 weeks without one (although I did have one weird semi-lockup).

I could be wrong. Maybe ER is a great software company that is plagued by hardware manufacturing QC problems. I just doubt it, and the evidence suggests otherwise when multiple members here have had to send their units into ER multiple times to fix problems that Escort said would be fixed by servicing, but somehow don't seem to be fixed when they get them back.

My gripe is that it's somehow always a hardware issue. Just like my first 360c, a capacitor was bad. DIdn't you test it before wrapping it up and boxing it? Manufactured in Oct, bought end of November. That part blows my mind.

 

[DrHow]

@DrHow - I must be slow today or something. I've read your post multiple times, but the encrypted message isn't coming though. lol

All I was trying to say is that IMO Escort is much too eager to tell people that the problem they are experiencing is a) something they never heard of before (even when it's been seen by multiple folks on RDF, who have probably also mentioned it on ERF) and b) somehow hardware related (and therefor specific to their unit, which btw needs to be serviced), rather than an issue with the fw (and therefor affects all units). How many times did they say they fixed the lock-up problem on the Max 360 S#79? They started saying that with fw 1.7, and I still had the problem through fw 1.11 (that's 5 fw revisions if you're counting). The jury is still out on 1.12, but I was able to run it for 2 weeks without one (although I did have one weird semi-lockup).

I could be wrong. Maybe ER is a great software company that is plagued by hardware manufacturing QC problems. I just doubt it, and the evidence suggests otherwise when multiple members here have had to send their units into ER multiple times to fix problems that Escort said would be fixed by servicing, but somehow don't seem to be fixed when they get them back.

I was not sticking up for them.. Assuming software is the issue (no issue with that theory), software folks are killing them. I was using fun wording to describe some of the typical #epicfail type software engineers/programmers around.

 

[eric15178]

Installed 1.9 and noticed that KA-POP is gone as a band preference and replaced with MRCD. I don't know of anyone using POP, but if you are you may want to stay at the previous FW. I drove 70 miles today on 1.9 with MRCD off - nothing out of the ordinary noticed.

View attachment 136248

Good to know about the lack of pop. I leave it on and have seen it used multiple times. Yes, know they can't ticket you for just that, but good to know they're trying to be sneaky and get you and beat them to the punch. Sure they think everyone disables it

 

[Heywood]

Good to know about the lack of pop. I leave it on and have seen it used multiple times. Yes, know they can't ticket you for just that, but good to know they're trying to be sneaky and get you and beat them to the punch. Sure they think everyone disables it

I’m not sure “Pop” is even an option on the guns to use? Not that I’ve looked too hard at the guns I own to see if it’s an available option?

Are you sure you might be mistaking “Instant On” for pop? That’s a pretty common tactic.

Have the gun on “Hold”. Press the hold button to release, get the reading of the potential target, then put the gun in “Hold” (standby mode) again till the next potential customer comes into sight.

You could be right. There could be some, but it’s rarer than hens teeth, and that’s why most turn it off.

 

[eric15178]

I’m not sure “Pop” is even an option on the guns to use? Not that I’ve looked too hard at the guns I own to see if it’s an available option?

Are you sure you might be mistaking “Instant On” for pop? That’s a pretty common tactic.

Have the gun on “Hold”. Press the hold button to release, get the reading of the potential target, then put the gun in “Hold” (standby mode) again till the next potential customer comes into sight.

You could be right. There could be some, but it’s rarer than hens teeth, and that’s why most turn it off.

Showed pop on the detector. At least 2 or 3 times for sure but been awhile. Had it happen a couple more times but those may have been falses, never seen the car.

Remember the one hit thou. Was just about to take off and the detector went nuts. Then few seconds later he came cruising down the 1 way st behind me and watched him go by in the mirror. I was parked on the side of a side street with my back to the one way. He went by then detector went silent.

Post automatically merged: Jan 5, 2020

Remembered the other for sure. Was parked in the driveway facing through the yard to a busier town street. The way the apartment is you can only see straight in front of you because the building blocks the corner and traffic comes from the right. Pop alert, one comes flying by then got a maybe 33.8 hit? not 100% on that. Thought it was the same hit just showed 33.8 or false of some kind. Then a second car came right by and signal dropped out. Be nice to have a touch of a bigger screen for the rare occasion like that with spec mode and bogey counter

 

[ViperTX]

The only thing on is RLC and RLC+speed cameras. (Speed on Green Cameras).

There’s no RLC in that direction at that distance.

The “M” stands for meters. If it’s MRCD, the “M” is white and it’s in the upper left hand corner like this picture. I’ve included.

Post automatically merged: Dec 9, 2019

I have a ton of false signal things like speed signs, door openers, and maintenance signs.

I find the reaction to these a crap shoot. If you go by them multiple times, you would think how it alerts would be constant, but it’s not.

It’ll show Locked out 24.151 going one way, then 20 mins later going the other way.... totally oblivious as if it doesn’t exist.

The FW is buggy and needs some work. It’s untrustworthy. Doesn’t matter if your linked to “Live” or not. It’s not filtering either.

If it can’t be consistent, you can’t depend on it. I don’t even have TSF activated

@Heywood - Thank you for clarifying the "M" designation. Purchased a 360 today New In-Box; updated the firmware with DTP; was sitting at a light in Houston when ALL arrows started flashing and "M" appeared on the display. I've been checking on Escort's site along with multiple searches. Guess I can go ahead and disable MCD since it appears to be false.

 

[Heywood]

@Heywood - Thank you for clarifying the "M" designation. Purchased a 360 today New In-Box; updated the firmware with DTP; was sitting at a light in Houston when ALL arrows started flashing and "M" appeared on the display. I've been checking on Escort's site along with multiple searches. Guess I can go ahead and disable MCD since it appears to be false.

Your welcome and yes I would disable MRCD to see how it reacts.

The 360 isn’t alone with MRCD problems or other issues when MRCD is turned on.

The R3 had issues leading up to FW1.46. The R7 still does. Doesn’t mean they’re bad detectors, but it does some funky stuff when you turn on MRCD. The 360’s are having the same growing pains.

There’s lots of people quite happy with their 360’s. Hopefully your one of them as well.

 

[timark251]

well, someone on the Escort forums found this in the 360c FAQ:
Q: Can I force a firmware or database update?
A: No. You can only update if there is software available that is newer than what you have installed.
Escort I need answers as to why!!!!! That's the only issue I'm having...sigh

 

[PHILBERT]

I updated a few weeks ago, and have run it in my work vehicle with MRCD on for a while. Yes, it falses MRCD for BSM's with multiple carriers, but I almost expect that. How does it work on the real thing? I'll take it to MD next time I go down. BTW, my R7 runs with MRCD turned on all the time, and maybe one false in several months. I like to leave that on.

The GOOD NEWS is my "lockup" and "sleeping" issues have been cured. I did the "full" update instead of the "quick" green icon update. I was having lockups and sleeping issues almost every day prior to the update, so at least something worked out ok. Now, with MRCD off, it seems to work well. Still getting more BSM than I was after that first IVT update, but maybe the BSM systems in new cars have "spread out" to other parts of the band.

Phil

 

[Brainstorm69]

well, someone on the Escort forums found this in the 360c FAQ:
Q: Can I force a firmware or database update?
A: No. You can only update if there is software available that is newer than what you have installed.
Escort I need answers as to why!!!!! That's the only issue I'm having...sigh

So you can no longer tell detector tools to update the fw with the same fw?

 

[timark251]

So you can no longer tell detector tools to update the fw with the same fw?

Apparently not...here's said post that quote is from.

MAX 360c FAQ - Escort Radar Forum

MAX 360c FAQ MAX 360c

www.escortradarforum.com

 

[poolmon]

Apparently not...here's said post that quote is from.

MAX 360c FAQ - Escort Radar Forum

MAX 360c FAQ MAX 360c

www.escortradarforum.com

The definitive answer to that question is pending a response on ERF.
It is currently not clear from the ERF Q&A if it was only referring to a wireless update or if it also refers to a PC update via DT Pro. If it also applies to DT Pro "update all software" then there would be an issue as how could you ever overwrite a corrupted firmware update.

 

[Dodgediesel]

Decided to put the 360c back into action today. My Compustar remote starter still sets off k band. Also, random MRCD alerts all over town where there are no MRCD cameras??? Had to turn off the MRCD. Also noticed it doesn't pick up those "your speed" camera but the Redline Ex does??? Maybe needs to be sent in to Escort??

 

[Heywood]

Decided to put the 360c back into action today. My Compustar remote starter still sets off k band. Also, random MRCD alerts all over town where there are no MRCD cameras??? Had to turn off the MRCD. Also noticed it doesn't pick up those "your speed" camera but the Redline Ex does??? Maybe needs to be sent in to Escort??

It’s going to cost you $23.00 to ship it. Escort doesn’t pay for international shipping.... and Canada is international.

 

[Dodgediesel]

It’s going to cost you $23.00 to ship it. Escort doesn’t pay for international shipping.... and Canada is international.

Of course.... LOL

 

[Heywood]

Of course.... LOL

Don’t feel bad. I had to send my R-EX in 4 times. Starting December 2018 till May 2019.

What started as a Check FR alert ended up not working right as soon as I got it back. 4 freaking times.

Then they shipped my detector to some post office box in Ontario, (which I had to go find on my own as they don’t look for missing items until 30 days had past.) They're the shippers and they had already sent it to me 3 previous times in a matter of months..... and they screwed it’s up, then told me they weren’t going to do anything for a month?

That was the last straw.

It’s all documented here on RDF. It spent more miles with the postal service than it did on my windshield.

No reimbursement for the $92.00 out of my pocket because they couldn’t fix it right once and kept sending it back issue after issue. Always different issues. It would spend 1 day with me. I’d bench test it, find another problem .... like a failed LNA on the 3rd return, not picking up K band unless it was in highway mode, wouldn’t detect Ka band and it would go back.

They even sent me a barely legible note on the repair. You should try to read it.

I’ll find a link to that thread.

Here. Post 26 and onward.

I found an error log feature on the Max 360 and 360c

Lol. If it makes you feel any better, I never lost the GPS function. It seems to be the only thing that worked right. Lol. Like I said. I had the “Check FR” message a few times in a couple of days, then I never seen it again. Could be because it stopped working. I had to hit it with all my...

www.rdforum.org

This from a company that says not to try testing with a Bushnell, but uses one in their own videos for the Max detector.

Post automatically merged: Jan 9, 2020

Check this out. 0:59 lol.