GOL help clear up.

**hookem202** · 05-14-2007, 11:49 AM

Ok well im looking in the differences between the Rx-65 and STi. Anyways I know that the STi had problems with the 33.8 ka-band in march 2007 test. Anyways looking back i see in August 2006 that the STi had the same problem with 33.8 on the STRAIGHT LINE area and averaged around 151 ft, but in the OVER THE HILL TEST it averaged at 1573 ft.

Why is the over the hill have almost 10x the range?

**jimbonzzz** · 05-14-2007, 12:06 PM

The reason why the over-hill test had 10x the range is that the straight line test was a special test using using radar absorbent foam to intentionally reduce the radar signal, and was meant only to see how the detectors might compare with each other sensitivity-wise.

**Toronto-radar-chopper** · 05-14-2007, 01:34 PM

I called Bel today because my STi need's to go in for repair and buddy says "GOL like to find loopholes in our product and spread rumours about it. Their is no bug against 33.8Ka"

I got pretty pi$$ed off and asked again if I send my unit for repair, will it get the bug fix or when will the bug fix come out.

I never had a problem with my STi, but hey I paid top dollar so I expect a top product.

Curious to here from V1 users, when their was bug fixes or upgrades. Is it a big secret or do they fix it. I will even pay the $59.95usd.

**jimbonzzz** · 05-14-2007, 02:34 PM

Originally Posted by Toronto-radar-chopper

I called Bel today because my STi need's to go in for repair and buddy says "GOL like to find loopholes in our product and spread rumours about it. Their is no bug against 33.8Ka"

:roll:

Just to be clear for anyone reading this: the goal of GOL isn't to "find loopholes in products and spread rumors". We test products under a specific set of conditions, and then report what we did, how we did it, and what happened.

We didn't set out to find a "loophole" in the STi or any other product. Were we surprised with the STi's results on 33.8 GHz? YES, and I'm sure that many people were. But that is what happened, and that is what we reported.

I can understand people at BEL not being happy about the results. And it is unfortunate that some customer service reps at BEL might think that GOL enjoys "finding loopholes and spreading rumors". But I would like to hope that many of the people at Beltronics, at least people in engineering, instead view our tests as helpful feedback on their products.

**happya$$** · 05-14-2007, 02:45 PM

Originally Posted by jimbonzzz

Originally Posted by Toronto-radar-chopper

I called Bel today because my STi need's to go in for repair and buddy says "GOL like to find loopholes in our product and spread rumours about it. Their is no bug against 33.8Ka"

:roll:

Just to be clear for anyone reading this: the goal of GOL isn't to "find loopholes in products and spread rumors". We test products under a specific set of conditions, and then report what we did, how we did it, and what happened.

We didn't set out to find a "loophole" in the STi or any other product. Were we surprised with the STi's results on 33.8 GHz? YES, and I'm sure that many people were. But that is what happened, and that is what we reported.

I can understand people at BEL not being happy about the results. And it is unfortunate that some customer service reps at BEL might think that GOL enjoys "finding loopholes and spreading rumors". But I would like to hope that many of the people at Beltronics, at least people in engineering, instead view our tests as helpful feedback on their products.

I hate to break the news to Bel but GOL reports results as is. There is no fluffing and no favoritism. Let the chips fall where they may.I can not believe they would make an unprofessional comment like that :cry: :cry:

**carboncopy** · 05-14-2007, 02:47 PM

Hmm and I guess the rest of us are also spreading rumors and finding loopholes with the poor ramp up on the STi? (lol) Come on Bel stop the games already and address the issues that your customers tell you about! Whatever happened to the customer is always right?

I am afraid the days of taking out multiple page reviews **COUGH** ads in car magazines and blindly telling people whatever sounds good is over. Now we have a forum to voice issues/bugs we find and it gives us, the customers a real voice!

**Toronto-radar-chopper** · 05-14-2007, 02:50 PM

Exactly, the CSR "Naeem Myles" knew exactly who the GOL are and all about the 33.8 Ka bug. His answer was so smooth that is almost seemed scripted.....

I asked him: "So when I send in my unit will it also get the latest firmware when the bug fixes" CSR: "Their are no bugs/issues with the STI to date." Me: "What about the 33.8 Ka band poor detection range by the GOL?
" CSR: "GOL look for loopholes and to spread rumous.."

Pete at V1 said they are working to combat the spectre and after pushing him, said to check back in about 3 months on their website. V1 users, do you have to deal with this crap when you spend $400+++ on a RD and you have an issue or bug fix?

**carboncopy** · 05-14-2007, 03:02 PM

Originally Posted by Toronto-radar-chopper

Pete at V1 said they are working to combat the spectre and after pushing him, said to check back in about 3 months on their website.

Check back in 3 months... **auto repeat CSR soundtrack**

**hookem202** · 05-14-2007, 03:10 PM

Originally Posted by Toronto-radar-chopper

I called Bel today because my STi need's to go in for repair and buddy says "GOL like to find loopholes in our product and spread rumours about it. Their is no bug against 33.8Ka"

I got pretty pi$$ed off and asked again if I send my unit for repair, will it get the bug fix or when will the bug fix come out.

I never had a problem with my STi, but hey I paid top dollar so I expect a top product.

Curious to here from V1 users, when their was bug fixes or upgrades. Is it a big secret or do they fix it. I will even pay the $59.95usd.

Well Roy PM me and said that someone gave hime word that bel was working on a 33.8 bug fix. I dont want to spoil this valuable information which he was kind enough to give to me, but he said that he expected maybe by late july there would be a new revison with the new fix. Please do not spread this information and make it an issue.