What is the best Radar Detector for the RedFlex K- band photo radar ?

[GQPRO]

My country is just add a new Redflex k-band photo radar ? My V-1 can only detect it when I arriver the radar. Anyone can help ? Which radar detectors has the best detect range for it ?

[barryswanson]

Try mounting your V1 vertically and let us know how it goes. You'll also have to eliminate any K band filtering through programming options. I don't own a V1 so maybe one of the other guys can chime in here.

[GQPRO]

I have already mount it vertically , it only works little bit better.

[nine_c1]

My country is just add a new Redflex k-band photo radar ? My V-1 can only detect it when I arriver the radar. Anyone can help ? Which radar detectors has the best detect range for it ?

I believe that the Stinger DSI would lay claim to having the best detection range angainst the AGD340 K-Band radar used in the RedFlex. It specializes in K Band and 34.3 Ka radar units that are horizontally polarized. The DSI uses a patch antenna with recommended mounting that would orient it for horizontally polarized signals.

http://www.stinger.com/index.php?lang=en&sec=dsi&pg=applications

Switching off Ka band on the V1 would probably boost performance a bit, but as Barryswanson indicated, turning the V1 on it's side will do more to improve range than anything else.

The folks here in the US that faced this threat also had to contend with conventional radars both on K and Ka bands. In this environment, the best detector would be the STi-R combining the superior range of the M3 with the advantage of turning off a good portion of the Ka band using band seg. Range was pretty good without having to flip the antenna on it's side which would have reduced range to standard mobile radars.

More info.....

http://www.escortradarforum.com/forums/showthread.php?t=1125

http://www.escortradarforum.com/forums/showthread.php?t=1112

[barryswanson]

Does anyone know what parts of the K and Ka band the Stinger DSI sweeps?

[nine_c1]

Does anyone know what parts of the K and Ka band the Stinger DSI sweeps?

I believe the Stinger covers just those frequencies used in certain portions of Europe..........K-Band and 34.3 Ka, not the entire Ka wideband used in the US.

This is as close as I could come to obtaining information on the frequencies covered.

http://www.stinger.com/pdf/Stinger%20DSI%20User%20Manual%20-%20V1.1ENG.pdf


Reference page 11...........it specifies K-Band and Ka 34.3.

[GQPRO]

Do you think the X50e has the good detection ?

[nine_c1]

Do you think the X50e has the good detection ?

I think the X50e has options that would make it better than most Belscort detectors against specific photo radars used in Europe.


Ka bands in 8500 X50 Euro are segmented to several narrow bands for the best possible customization to the country where it is in use.

The Ka narrow band segments allow the user to set the detector up to scan only those specific radar frequencies in the Ka band that are of concern. This essentially allows the detector to Focus and spend more time looking at only those frequencies that are a real threat to the user..........including K-Band. This is why Belscort developed Ka Band segmentation in the first place, to give Folks in Europe a bit more range to the horizontally polarized radars used over there.

The X50 Euro also has the option to turn off Radar Detector Rejection (RDR) filtering which removes many preconditions necessary before alerting to a detected signal. This also has the benefit of improving the radar detectors reaction time as well as allowing it to alert to the weakest possible signal detected.


Operating Bands
X Band: 10.475-10.575 GHz
Ku Band: 13.400-13.500 GHz
K Band: 24.050-24.250 GHz
K Pulsed Band: 24.100-24.250 GHz
Ka (Superwide): 33.400-36.000 GHz
KaN1: 33.900-34.200 GHz
KaN2: 34.200-34.400 GHz
KaN3: 34.600-34.800 GHz
KaN4: 35.400-35.600 GHz
Ka-POP: 33.725-33.875 GHz (60 ms)
Radar Detector Rejection: 11.133GHz-12.000GHz
Laser
SWS (Safety Warning System)

Notice that KaN3 is specifically set up to cover Ka 34.3 (just like the Stinger DSI) which is the specific Ka frequency used in the Multinova photo radars in Europe.

Oh...........BTW............the V1 has a very very similar option that you might consider trying. Euro Mode!

Euro Mode is very similar to Band Seg on the e50..........it again limits the portion of Ka being swept to just the 34.3 used in certain parts of Europe. And again, this also benefits K-Band coverage as the detector spends less overall time sweeping Ka permitting more time for K-Band sweeps.


Euro Mode narrows and intensifies radar coverage, and limits it to K band plus the sections of Ka bands used in Europe and some other countries for photo radar.

Reference information:

http://www.euescortradar.com/escort_8500.html

http://www.valentine1.com/Service/EuroMode.asp

[Hunter]

I have encountered these vans and still trying to figure out what is a good detector for this.

[nano]

The Ka narrow band segments allow the user to set the detector up to scan only those specific radar frequencies in the Ka band that are of concern. This essentially allows the detector to Focus and spend more time looking at only those frequencies that are a real threat to the user..........including K-Band. This is why Belscort developed Ka Band segmentation in the first place, to give Folks in Europe a bit more range to the horizontally polarized radars used over there.

Well, I always thought the same, until I tested the difference between EuroMode ON and OFF. Surprisingly the detection was better or at least the same with Euro OFF.

I made a few testruns with a 3.872 against a fixed Multanova 6F and the results surprised me. Results were better with EURO OFF.

Just a theory: With Euro OFF the V1 sweeps from 33.4 to 36.0 GHz (2600MHz), but with Euro ON the V1 has to scan from 33.70 - 33.90 GHz then 33.96 - 34.04 GHz then 34.16 - 34.44 GHz and then from 34.56 - 34.64 GHz.

Maybe it takes more time to seperate the KA Band into different segments than to scan the complete 2,6 GHz Ka band?
Any thoughts? :confused:

[nine_c1]

The Ka narrow band segments allow the user to set the detector up to scan only those specific radar frequencies in the Ka band that are of concern. This essentially allows the detector to Focus and spend more time looking at only those frequencies that are a real threat to the user..........including K-Band. This is why Belscort developed Ka Band segmentation in the first place, to give Folks in Europe a bit more range to the horizontally polarized radars used over there.

Well, I always thought the same, until I tested the difference between EuroMode ON and OFF. Surprisingly the detection was better or at least the same with Euro OFF.

I made a few testruns with a 3.872 against a fixed Multanova 6F and the results surprised me. Results were better with EURO OFF.

Just a theory: With Euro OFF the V1 sweeps from 33.4 to 36.0 GHz (2600MHz), but with Euro ON the V1 has to scan from 33.70 - 33.90 GHz then 33.96 - 34.04 GHz then 34.16 - 34.44 GHz and then from 34.56 - 34.64 GHz.

Maybe it takes more time to seperate the KA Band into different segments than to scan the complete 2,6 GHz Ka band?
Any thoughts? :confused:

Wow! That does surprise me and is extremely interesting information, thanks for sharing this!

My understanding of the RD universe was once again thrown into chaos after pondering your results. But.......after chewing on this new information...........it occurs to me that I'm forgetting about another feature of the V1 that was available before Euro mode was introduced, and that it too was put there to improve range against the Multanova 6F.

Ka Guard!

Likewise the Escort 8500 X50 has Band seg and RDR.

So maybe our understanding of the real purpose of Euro Mode and Band Seg is not what we think it is?
I've always assumed the point of either was to eliminate scanning portions of the Ka spectrum that was unnecessary, thereby increasing the scan rate on portions of the Ka band that ARE of interest. The assumed benefit was quicker response and improved range.

Well, lets compare your results with some surprising results from a radar detector reaction time test that CJR238, Riptide and I ran earlier this year with an STi-R.

We were very sure that by turning off seven of the ten Ka segments on the STi-R that response time of the STi-R would improve big time on 35.5 Ka. It did not! By reducing the bandwith scanned on Ka by 70 percent we saw a very negligable improvement on response times to 35.5.:eek: HOWEVER, when we switched RDR off the improvement we expected with Band Seg showed up in spades! The STi-R also had phenomenal range against 35.5 compared to the other M3 detectors in that test with Band Seg and RDR turned off. Hmmmmmmm.

Your results, along with ours, might infer that turning off the Ka filtering on either detector is the key
to improving both reaction time andrange on either detector.

We know that Ka guard and RDR were features developed to improve range on radars like the Mutanova 6F used in Europe. We also thought that Band Seg and Euro mode were designed for the same purpose.........but maybe not. Why then would these features exist?

New speculation. Maybe the only real value of Band Seg and Euro mode is to eliminate as much of the Ka spectrum being scanned, not to improve reaction times or sensitivity, but rather to reduce the oppurtunity for false alerts on Ka band with the detectors Ka false filtering turned off!

Figure this, V1 is a false-o-matic with Ka guard off as is the STi-R with RDR switched off. However, I know that most Ka falses are due to leaky Cobras and show up between 33.5-33.6. With segment 1 turned off on the STi-R, it essentially filters out all Cobras by skipping over that frequency in it's scan. So perhaps Band Seg and Euro mode are meant as alternative filtering methods with Ka Guard and RDR turned off.

Or maybe not..........just something else to chew on.

[nano]

New speculation. Maybe the only real value of Band Seg and Euro mode is to eliminate as much of the Ka spectrum being scanned, not to improve reaction times or sensitivity, but rather to reduce the oppurtunity for false alerts on Ka band with the detectors Ka false filtering turned off!

Figure this, V1 is a false-o-matic with Ka guard off as is the STi-R with RDR switched off. However, I know that most Ka falses are due to leaky Cobras and show up between 33.5-33.6. With segment 1 turned off on the STi-R, it essentially filters out all Cobras by skipping over that frequency in it's scan. So perhaps Band Seg and Euro mode are meant as alternative filtering methods with Ka Guard and RDR turned off.

Reducing false alerts on KA Band IS the main advantage of the EURO Mode, I think.

In theory there should be an improvement in reaction times, but that are ms we are talking about.

I should make some tests with the STI-R, with KA wide vs. only 34,3GHz active. RDR OFF makes a huge difference.
With only one Ka Segment turned on and RDR OFF you can push the STI-R to its maximum. This is why the STI-R is so popular in Europe.

Btw. always nice discussing with you, nine_c1.:)

[€]

Reducing false alerts on KA Band IS the main advantage of the EURO Mode, I think.

In theory there should be an improvement in reaction times, but that are ms we are talking about.

It's much more complicated and related to sweep algorithms and filtration methods. For example Whistlers can be so fast because of unique "one step back" sweeping algo after first catch of the signal instead of "sweep the whole again" (sometimes even 4 times - for a weak signals) at Belscorts.

[nano]

It's much more complicated and related to sweep algorithms and filtration methods. For example Whistlers can be so fast because of unique "one step back" sweeping algo after first catch of the signal instead of "sweep the whole again" (sometimes even 4 times - for a weak signals) at Belscorts.
Do you wanna tell us more about this? :)

[€]

But I'm so shy, heheh ;):lol:

Every modern detector before will show you an alarm has to make sure that the detected signal is not accidental. Checks so, whether the signal with the same frequency will occur at the next sweep. If not, the alarm is dropped. If so, depending on further ideas on the detector - or shows an alert, or scans for the same purpose again, once, twice... to be sure.

Unfortunately, a single scan for all bands takes about 150-300ms, and each subsequent confirming scan again the same. It may therefore be that the most conservative algorithm, for example, requires four scans, what means that the detector needs the signal which lasts about 600-1200ms, to show alarm.

Whistler was a better idea to get the same effect and after initial detection of the signal does not scan again (or several times) throughout the whole frequency range from beginning to end, only goes back a small portion, "one step" (perhaps 100MHz - I don't know...), and scans again only the selected, narrow scope. Confirmation of the signal takes several times less and thus Whistler reacts at a much shorter pulses.

I'm not sure which method / methods are used in detectors Valentine, so won't be speculated.

[LouG]

I get around 100 metres warning with my V1 (3.872). It's not enough for open road speeds so I rely on the MK 1 eyeball.
Luckily our camera vans are quite easy to spot and there isn't many if them.

[nine_c1]

But I'm so shy, heheh ;):lol:

Every modern detector before will show you an alarm has to make sure that the detected signal is not accidental. Checks so, whether the signal with the same frequency will occur at the next sweep. If not, the alarm is dropped. If so, depending on further ideas on the detector - or shows an alert, or scans for the same purpose again, once, twice... to be sure.

Unfortunately, a single scan for all bands takes about 150-300ms, and each subsequent confirming scan again the same. It may therefore be that the most conservative algorithm, for example, requires four scans, what means that the detector needs the signal which lasts about 600-1200ms, to show alarm.

Whistler was a better idea to get the same effect and after initial detection of the signal does not scan again (or several times) throughout the whole frequency range from beginning to end, only goes back a small portion, "one step" (perhaps 100MHz - I don't know...), and scans again only the selected, narrow scope. Confirmation of the signal takes several times less and thus Whistler reacts at a much shorter pulses.

I'm not sure which method / methods are used in detectors Valentine, so won't be speculated.

I believe you're correct in that some detectors require a signal to be present on multiple sweeps before alerting due to false filtering algorithms............unless the detector is in POP mode and the signal detected is a POP frequency. I also believe that the power level of the signal detected is certainly a factor in that algorithm..........a stronger signal requires fewer subsequent sweeps before setting an alert.

However, it's apparently not that simple as we saw ALOT of variation in the time required to set an alert on several Belscort detectors during a reaction time test with signals transmitted at a consistent power level.

http://i47.tinypic.com/rj2gxl.jpg

Notice that the 9500ix snagged (1) Ka transmission under 200ms and (1) under 300ms but missed 5 of 5 between 400ms - 500ms!:eek:

Me thinks there is alot going on inside these detectors simultaneously and thats why we can't pin down the exact response times by considering just the sweep rate and power level of the signal.

[€]

Me thinks there is alot going on inside these detectors simultaneously and thats why we can't pin down the exact response times by considering just the sweep rate and power level of the signal.
I agree. This "few sweep algo" which I wrote is just one of the mechanisms of signal processing - however, it's the most important and basic. I believe there are more and may be more complicated (for example - the simultaneous presence of another signal and on which frequency).

It is also true that the signal strength is important. For weak signals at Belscorts is likely to apply a 4 sweeps rule, while probably only 2 for the strong.

The rules also can differ for different bands.

[nine_c1]

"The rules also can differ for different bands......."

Thats an interesting point. I believe all the real junk filtering algos apply only to Ka Band.

Turn off Ka Band on a Belscort and your doing the same thing as turning off RDR. With no Ka segments to sweep and NO Ka filtering rules (multiple sweeps, power level......yadayadaya) the RedLine or 9500ci are greased lightening reacting to K-Band emissions. I mean they consistently catch shots down to .15 seconds in duration!:D

The mystery is.........the Belscorts seem to apply the same rules for K-Band as long as Ka-Band is turned on, but then eliminates the verification sweeps for K-Band when Ka is switched off.

[€]

"The rules also can differ for different bands......."

Thats an interesting point. I believe all the real junk filtering algos apply only to Ka Band.

Turn off Ka Band on a Belscort and your doing the same thing as turning off RDR. With no Ka segments to sweep and NO Ka filtering rules (multiple sweeps, power level......yadayadaya) the RedLine or 9500ci are greased lightening reacting to K-Band emissions. I mean they consistently catch shots down to .15 seconds in duration!:D

The mystery is.........the Belscorts seem to apply the same rules for K-Band as long as Ka-Band is turned on, but then eliminates the verification sweeps for K-Band when Ka is switched off.



Hmm... When Ka is removed from the scan, 150ms may be sufficient time to sweep the entire K band from beginning to end even 4 times.

[nine_c1]

"The rules also can differ for different bands......."

Thats an interesting point. I believe all the real junk filtering algos apply only to Ka Band.

Turn off Ka Band on a Belscort and your doing the same thing as turning off RDR. With no Ka segments to sweep and NO Ka filtering rules (multiple sweeps, power level......yadayadaya) the RedLine or 9500ci are greased lightening reacting to K-Band emissions. I mean they consistently catch shots down to .15 seconds in duration!:D

The mystery is.........the Belscorts seem to apply the same rules for K-Band as long as Ka-Band is turned on, but then eliminates the verification sweeps for K-Band when Ka is switched off.



Hmm... When Ka is removed from the scan, 150ms may be sufficient time to sweep the entire K band from beginning to end even 4 times.

You would think so, but we found that turning off 7 of the 10 Ka segments on the STi-R (70 percent of the Ka Bandwidth being swept) had almost no effect on improving reaction times on the STi-R.:eek:

Turning off RDR made a huge improvement.

I think the filtering algos are the main culprit.

[€]

RDR is just scanning 11.130-12.000 GHz for other detectors LOs. But maybe it's still so much to sweep (K band ~250MHz while RDR ~900MHz), to see the difference. I have 9500ci and to be onest, didn't see a difference for K band with Ka off on that detector.

[barryswanson]

RDR is just scanning 11.130-12.000 GHz for other detectors LOs. But maybe it's still so much to sweep (K band ~250MHz while RDR ~900MHz), to see the difference. I have 9500ci and to be onest, didn't saw a difference for K band with Ka off on that detector.
I wish you could program the sti-r to alert to 11.130-12.000. Then we might actually have a spectre detector.

[€]

But in fact STi-R scans 11.130-12.000 GHz with RDR enabled. Although this happens in the background and this is not to present the alarm for this frequency range, but is one of the mechanisms to reduce false alarms from leaky detectors.

[nine_c1]

RDR is just scanning 11.130-12.000 GHz for other detectors LOs. But maybe it's still so much to sweep (K band ~250MHz while RDR ~900MHz), to see the difference. I have 9500ci and to be onest, didn't see a difference for K band with Ka off on that detector.

We tested both my RedLine and CJR238's 9500ci and had very similar results........with Ka turned off both detectors consistently caught K-band shots under 200 ms. If I remember correctly though, we tested RIPTIDE's STi-R and nothing we did (Band Seg, RDR OFF and switching off Ka Band) could improve the lackluster K-Band response times on his detector. Rip and RadarRob tested another STi-R and turning off RDR again had very positive results on both Ka-Band and K-Band.

After sending in his STi-R to Belscort to have it looked at, they said there was nothing wrong with his unit........and that different hardware/software levels may perform differently.

So it seems not every STi-R or 9500ci (any Belscort for that matter) will perform the same depending on when it was built and what firmware is loaded.

[GQPRO]

Finally I bought the escort X50e to test the Redflex (AGD340) K band (24.075ghz which the X50e show to me ). The result was the X50e worst than the V1, even the ka (Multanova 6).

[nano]

RDR is just scanning 11.130-12.000 GHz for other detectors LOs. But maybe it's still so much to sweep (K band ~250MHz while RDR ~900MHz), to see the difference.
I always wondered how RDR works in detail.

It scans for 11.130-12.000 GHz and then what?

From my point of understandig RDs work by creating an internal signal and then compare this signal to the receiving signal. So when a normal RD detects a LO signal from a leaky Cobra (which should be in the X or Ku Band) it thinks this is the signal from its own LO and through comparison it says Ka-Band. Right?

[nine_c1]

RDR is just scanning 11.130-12.000 GHz for other detectors LOs. But maybe it's still so much to sweep (K band ~250MHz while RDR ~900MHz), to see the difference.
I always wondered how RDR works in detail.

It scans for 11.130-12.000 GHz and then what?

From my point of understandig RDs work by creating an internal signal and then compare this signal to the receiving signal. So when a normal RD detects a LO signal from a leaky Cobra (which should be in the X or Ku Band) it thinks this is the signal from its own LO and through comparison it says Ka-Band. Right?

Superheterodyne detectors work by generating an internal signal and MIXING it with an external signal...........the result being an IF (Intermediate Frequency) which is easier to detect than the raw signal itself.

It's sorta like filling a glass to the very top such that just the smallest drop causes the glass to overflow and trip the alert.

The point of RDR is to find the Fundamental (Primary) frequency of the LO emission of the Cobra so that the detector is not fooled by the 3rd Harmonic of the LO emission into setting a false Ka alert.

http://en.wikipedia.org/wiki/Harmonic

Cobra primary LO emission: 11.133 to 12.000 GHZ

3rd Harmonic of Cobra LO emission: 3 * 11.133 =33.399 GHZ to 3 * 12.00 = 36.0 GHZ

Ka Frequency range: 33.4 GHZ to 36.0 GHZ

So you see that the 3rd Harmonic of another Radar detector can show up anywhere in the legitimate Ka band spectrum. RDR will reject the Ka frequency detected IF it is a direct multiple of a frequency detected in the X-Band oversweep (11.133 to 12.0).

In my experience (and from what I've read) a Cobra false usually registers between 33.5 to 33.6 GHZ on a Belscort in Spec Mode.

http://www.euescortradar.com/escort_8500.html

Their Euro website gives the exact frequency swept by RDR.

[nano]

Thanks for the explanation, nine_c1.

Which leads me to another question. The Stinger (http://www.stinger.com/index.php?sec=index&lang=en) uses a patch antenna, but leaks at 29,2 GHz regarding this video on youtube (http://www.youtube.com/watch?v=xwTVJPhjabI/).

How can the radar detector (Whistler?) detect a Stinger at 29,2 Ghz? Ka-band starts normally in the near of 33.4?

We found out that a STI-R (with RDR off) is able to detect a Stinger up to 20cm (~0.66 feet). But the reported frequency is 34,5 GHz.

Also, does that mean that the Stinger is using a LO?

[nine_c1]

While the Stinger uses a Patch antenna, it's still a Super-heterodyne design and will still leak emissions. Some detectors use an LO centered between 11 - 12 GHZ while others moved their LO up between 14 - 15 GHZ. Thats why the Spectre RDD scans between 11.5 to 12.0 and 14.5 to 15.0 GHZ.

While it's possible that the Stinger uses an LO centered around 14.6 (explaining the 29.2 GHZ signal......2nd harmonic of 14.6) it doesn't make sense that the Whislter would detect it. That frequency, 29.2 GHZ, is way outside of any know Police Radar frequency and I don't think a Whistler (or any other detector) would go there.

The 34.5 reading on the STI-R makes allot more sense. The Stinger DSI more likely has an LO centered at 11.5 as it's main adversary is the 34.3 GHZ Gatso guns.

However, I suppose the Stinger might use more than one LO (One for K-band and the other for Ka) like Belscort's M3 detectors. So it may be able to detect the Stinger on more than one frequency.

In truth, I don't know for certain.........but that would be my suspicion.

[nano]

While it's possible that the Stinger uses an LO centered around 14.6 (explaining the 29.2 GHZ signal......2nd harmonic of 14.6) it doesn't make sense that the Whislter would detect it. That frequency, 29.2 GHZ, is way outside of any know Police Radar frequency and I don't think a Whistler (or any other detector) would go there.
I just read on their blog (http://translate.google.com/translate?hl=es&sl=es&tl=en&u=http%3A%2F%2Fportalvasco.com%2Fblog%2F%3Fp%3D142 3), that he adjusted the Whistler to the 29.2 GHz. ;)

[corkguykev]

Sorry for the bump guys but we have just gotten a load of these Redflex vans here in Ireland...

http://www.radardetector.net/forums/showthread.php?t=66885&p=788835#post788835

:(

.. and I am wondering what the general consensus is on which RD is the best out there at detecting them as I only have a V1 at the moment and it is not up to the task apparently :(.

The Sti-R is no longer available from what I've read but is the new Sti-R plus any good?

I will have to do some research on this myself also but any help would be appreciated.

Cheers in advance :).

I had read about these vans before but I was hoping that we would never get the bloody things :mad:.

[protias]

Is the STi-R+ any good? Let's just say I want one!

[GQPRO]

Finally, I got the "Stinger" in my car, it ate me a lot of money but I am so happy. Only one word to say for Stringer " Best " . It's not only detect the "Redflex" very well. It can detect the 34.3 photo radar much long range than my V1.

[barryswanson]

Finally, I got the "Stringer" in my car, it ate me a lot of money but I am so happy. Only one word to say for Stringer " Best " . It's not only detect the "Redflex" very well. It can detect the 34.3 photo radar much long range than my V1.

Awesome! Do you have any pictures?:)

[GQPRO]

I am looking for how to DIY installing the system through the firewall . Now I put it inside the car for testing.

[GQPRO]

Any idea for this windshield. Do you think it effect the Radar signal ? They say it is a heat-insultating glass and it looks little grey colour.

[spartcus]

Never heard of the Stringer I think that i'm going to have to look into that.

[Hunter]

That is interesting....

also never heard of the stinger...
tell us more..

[nine_c1]

^^^ Fellas.......the Stinger was discussed on page 1 of this post.:p

It's not a viable option for US users as it does not cover the entire Ka wide band. It is also specifically set up with a planar patch antenna that is mounted to match the Horizontal Polarity of the RedFlex and other European photo radars..........ie. it's not going to do so well against the circularly polarized mobile radars over here.

The patch antenna is a very neat idea but does not have as much gain as the horns in most RDs.

[ka34.739]

Is this the radar you are referring to?
http://www.youtube.com/watch?v=lG22uZjgYlw

[ghz1]

My letter to them
In future firmware releases would it be possible to be able programme
the V1 be able to have a "US" Ka 34.70 GHz +-1300 MHz and a Euro K band
24.125 GHz +-100 MHz to run at the same time.. The reason I ask this is
for flexibility. In my country the police run 34.7 stalkers and 35.5
talons, recently they have become very cunning and introduced the
Australian made redflex K band camera. This is the only K band law
enforcement radar in my country. While the V1(.863) has not too much of
a problem detecting this camera in US mode, in testing the Euro mode
really does a much better job and of course while in this mode it misers
34.7 GHz and above. Thank you for your consideration.

best regards one die hard V1 fan forever



Steve




The reply

Dear Sir:

Thanks for your email.

We appreciate your taking the time to write to us regarding potential
modifications to Ka and K bands for European use.

I'll pass this on to our software engineers for future consideration.

Thanks again for writing.

Cordially,



Pete Kaufman
Sales Department
Valentine One Frequency Coverage
Valid for 3.861 and higher

Frequency Coverage in EURO mode:
Ka:
34.60 GHz +-40 MHz [34.56 - 34.64 GHz]
34.30 GHz +-140 MHz [34.16 - 34.44 GHz]
34.00 GHz +-40 MHz [33.96 - 34.04 GHz]
33.80 GHz +-100 MHz [33.70 - 33.90 GHz]
(fast 33.8 GHz(POP) response may be selectively disabled via User
Programming [FEATURE CHARACTER "J"])
K: (may be disabled/enabled via mute knob mode change [UPPERCASE U=ENABLED])
24.125 GHz +-100 MHz [24.025 - 24.225 GHz]
Ku: (may be selectively enabled via User programming [FEATURE CHARACTER "H"])
13.42 GHz +-50 MHz [13.35 - 13.47 GHz]
Laser: (may be selectively disabled via User programming [FEATURE CHARACTER "4"])
820 - 950 nanometers

USA Frequency Coverage:
Ka:
34.70 GHz +-1300 MHz [33.4 - 36.0 GHz]
Ka Pop:
33.80 GHz +-100 MHz [33.70 - 33.90 GHz]
(fast 33.8 GHz(POP) response may be selectively disabled via User
Programming [FEATURE CHARACTER "J"])
K: (may be selectively disabled via User Programming [FEATURE CHARACTER "2"])
24.15 GHz +-100 MHz [24.05 - 24.25 GHz]
X: (may be selectively disabled via User Programming [FEATURE CHARACTER "1"])
10.53 GHz +-40 MHz [10.49 - 10.57 GHz]
Ku: (may be selectively enabled via User programming [FEATURE CHARACTER "H"])
13.42 GHz +-50 MHz [13.35 - 13.47 GHz]
Laser: (may be selectively disabled via User programming [FEATURE CHARACTER "4"])
820 - 950 nanometers

************************************************** **************************

EURO-mode Freq.Coverage in previous Revisions:
ValentineOne rev.3.821 to 3.826
Ka: 33.8GHz +/-100MHz (33.700 to 33.900GHz)
Ka: 34.3GHz +/-100MHz (34.200 to 34.400GHz)

ValentineOne rev. 3.851 to 3.858
Ka: 33.8GHz +/-100MHz (33.700 to 33.900GHz)
Ka: 34.30 GHz +/-140MHz (34.16 - 34.44 GHz)
Ka: 34.60 GHz +/-40MHz (34.56 - 34.64 GHz)
Note: I don't know for sure,if rev. 3.851 to 3.858 also covers 34.0GHz+/-40MHz
When I get VR's reply,I'll edit the post.

[mikeecho]

i wasnt aware that K band was different in euro mode. i asked VR a few years back when i bought my V1 about k band and they told me that there was no differance.




European Frequencies
Ka:
34.60 GHz +- 40 MHz [34.56 - 34.64 GHz]
34.30 GHz +-140 MHz [34.16 - 34.44 GHz]
34.00 GHz +-100 MHz [33.90 - 34.10 GHz]
33.80 GHz +-100 MHz [33.70 - 33.90 GHz]
(fast 33.8 GHz(POP) response may be selectively DISABLED via User Programming (Pop Off)
K: may be ENABLED via mute knob MODE change (K On) (K Off)
24.15 GHz +-100 MHz [24.05 - 24.25 GHz]
Ku: may be selectively ENABLED via User programming (Ku On)
13.42 GHz +-50 MHz [13.35 - 13.47 GHz]
X: may be selectively ENABLED via User programming (X On)
10.53 GHz +-40 MHz [10.49 - 10.57 GHz]
Laser: may be selectively DISABLED via User programming (Laser Off)
820 - 950 nanometers


USA Frequencies
Ka:
34.70 GHz +-1300 MHz [33.4 - 36.0 GHz]
Ka Pop:
33.80 GHz +-100 MHz [33.70 - 33.90 GHz]
fast 33.8 GHz(POP) response may be selectively DISABLED via User Programming (Pop Off)
K: may be selectively DISABLED via User Programming (K Off)
24.15 GHz +-100 MHz [24.05 - 24.25 GHz]
X: may be selectively DISABLED via User Programming (X Off)
10.53 GHz +-40 MHz [10.49 - 10.57 GHz]
Ku: may be selectively ENABLED via User programming (Ku On)
13.42 GHz +-50 MHz [13.35 - 13.47 GHz]
Valentine One Frequency Coverage
version: 3.864 and higher
May 2008

[tonytony]

Does anyone know at this stage which of these gives better protection against these cameras, the valentine1 or the redline? There just in my price range, can't afford anything over that price.
Im seeing these damn vans every second day now.

T

[<<JAZZY>>]

Does anyone know at this stage which of these gives better protection against these cameras, the valentine1 or the redline? There just in my price range, can't afford anything over that price.
Im seeing these damn vans every second day now.

T

Probably the Redline from what I have seen or heard.

[NormSky]

Within 100 feet for K & Ka for both units. The V1 trailing.
http://radartest.com/images/detector_articles/V1-RedLine-Photo-Radar-Test.png

[tonytony]

Thanks, sorry if that question has been asked before. Ill order one at the end of the week and post up my findings when I get it up and running....

Just to check, are those results from the off axis system that gosafe use in Ireland?

T

[NormSky]

Thanks, sorry if that question has been asked before. Ill order one at the end of the week and post up my findings when I get it up and running....

Just to check, are those results from the off axis system that gosafe use in Ireland?

T

That link above was a test done in the US on Redflex K and ATS Ka. Not sure if they sell the cameras with same frequencies in different countries.

[tonytony]

Ok, thanks. does anyone know if the agd modules used in the redflex are on a standardised fixed frequency or is it random or sequenced changing frequency?
T

[GQPRO]

Finally, I installed the Stinger Spectrum Analyzer and the laser jammers on the grill inside the bumper after the few week test on the desk. There are much better on the radar detection , so I am sure my windshief effect the radar signal at lease 20 0/0. Now I detect the Ka (34.3) much longer range and the Redflex (24.100) is no problem any more . In My area all the photo radar is face to the road and take the car's rear photo, so the signal is very weak and hard to detect. I used the V1 for a long time ,I think it is the best if I hadn't used the Stinger and if there are no Redflex here. I know some country is using the Wideband Ka and POP, so the Stinger is useless there. For my long time testing on Redflex ( I tried Bel 65A, 65E, Escort 8500E, Target 966,V1(3.861), V1(3.864) V1(3.872) etc. , I think the v1(3.864) is the 2rd choose for me. I found the best setting for it is : Euro mode and POP on and *Vertical mount* on lower area of the windshief. Why I put it on the lower area of the windshief ? Just after many many times testing. For the Ka (34.3)and the K(old type) there are not so much different whatever I put it upper or lower area, some time upper seems little bit better on Ka. but there are a much different on the Redflex (24.100). I don't know why it happen. The best place is the left or right side lower area and little angle down with the Vertical mount.

[mikeecho]

how many meters warning are you getting against the k band redflex with the stinger?

Hopefully you can post a video of your stinger in action against k band redflex

[GQPRO]

For the Redflex K band, the best range for my Stinger is about 300m and the min is about 100m (all faceing the travel and take the rear photo). So I think the officer can tune the Radar signal depend on the road, I found they tune it stronger on highway, so I also can get very good detection on highway.

[mikeecho]

That's quite good. My v1 only picks it up when I'm past it.
What sort of range do you get when driving towards the radar beam?

[GQPRO]

Yes, that why I change to Stinger from V1. But you can try mount the V1 "Vertically and PoP on", it should be much better and it can detect the Redflex before you pass it, but the False alert will more. In fact , the Stinger is much quieter than the V1 because of it's "False List function (with GPS)" make it almost no false alert .

[mikeecho]

I have it vertically, with pop on, it only alerts when i'm alongside the unit, but when approaching the radar beam i get 3 to 400 metres warning.

I've a thread over in photo enforcement.
http://www.radardetector.net/forums/photo-enforcement/69749-redflex-gosafe-agd340-radar-reception-range.html

[GQPRO]

May be your windshief effect your detection like my car. I also felt the different when I install the Stinger inside and outside the windshief.
For the V1 ,my best mounting position is the lower area of the left or right side windshief and make the RD face little angle down, it was a very different if I just put it the higher or middle area of the windshief for the Redflex. You can try mount it different area to see .

[corkguykev]

Does anyone know what K band frequencies the Stinger scans for?

[GQPRO]

I think it detect the K band as same as the other detector. My Stinger can detect the Redflex (+/- 24.100) and the old type photo radar ( +/- 24.125) .

[corkguykev]

Thanks for that info^. I hope to confirm this with the STI-R plus also when it gets here.

[tonytony]

I just post this in the other Redflux thread....
http://vimeo.com/21108152

[Rabbiter2]

So what's the detector?

[Rowan]

My country is just add a new Redflex k-band photo radar ? My V-1 can only detect it when I arriver the radar. Anyone can help ? Which radar detectors has the best detect range for it ?

Ive seen the REDLINE perform well, if you can get one to test it out before you buy you might be happy with the results

[Hunter]

The V1 is still your best bet.Those radars are pointed at an angle to the road so they are very hard to detect.When the RD goes off almost close to the van you must react instantly and brake.
you will only get a ticket if you pass that van speeding.The v1 gives you a few car lengths warning and enough time to jam on your brakes.

[forgewire]

The V1 is still your best bet.Those radars are pointed at an angle to the road so they are very hard to detect.When the RD goes off almost close to the van you must react instantly and brake.
you will only get a ticket if you pass that van speeding.The v1 gives you a few car lengths warning and enough time to jam on your brakes.
How many car lengths can you count before you can see the Redflex on second part of this video?
http://www.youtube.com/watch?v=VFrAJqP5z8Y