Uniden R1 is not responding, to MRCDK24.127 & K24.004GHZ.

[UnidenSupport]

Really? Interesting. That's the first report I've heard of MultaRadar in WI. Are you sure they're truly MultaRadar signals? My R3 falses to MRCD in certain areas even though we don't have MRCD in use here, so it can sometimes be a bit tricky to verify whether or not a K band source truly is MRCD or not.

That is not something I can say for sure. These are stationary cameras on overpasses and poles along the interstate that are spaced at quarter mile intervals. Before 1.46 I picked up nothing. on both 1.46 and 1.48 I get the MRCD alert.

 

[CobawLT2010]

Really? Interesting. That's the first report I've heard of MultaRadar in WI. Are you sure they're truly MultaRadar signals? My R3 falses to MRCD in certain areas even though we don't have MRCD in use here, so it can sometimes be a bit tricky to verify whether or not a K band source truly is MRCD or not.

They do have hard on for speeders in that area. I wouldn’t be surprised. I know shitcago has it though I haven’t been back there this year yet... and I’m pretty sure they are relatively new to the area.?

 

[UnidenSupport]

They do have hard on for speeders in that area. I wouldn’t be surprised. I know ****cago has it though I haven’t been back there this year yet... and I’m pretty sure they are relatively new to the area.?

It's not like this everywhere?

 

[CobawLT2010]

It's not like this everywhere?

No...

 

[dchemist]

It's not like this everywhere?

Come to Arkansas we can't even spell MRCD/MRCT (well I can but I'm from Texas).

 

[cihkal]

That is not something I can say for sure. These are stationary cameras on overpasses and poles along the interstate that are spaced at quarter mile intervals. Before 1.46 I picked up nothing. on both 1.46 and 1.48 I get the MRCD alert.

Keep in mind it could be MRCT rather than MRCD.

One thing that would be nice with a firmware update is if Uniden RDs would say MRCT or MRCD depending on the threat.

When you turn on MRCD you're actually turning on detection for MRCT and MRCD, but it's only reported as MRCD.

Chicago has stationary MRCT cameras for speed enforcement I regularly test against with my Pro M and R3. The Pro M picks them up as MRCT only, won't detect them with MRCD on. The R is very competitive to the M at picking these threats up on 1.46, but on 1.48 it's a little wonky.

I saved the FCCID on these cameras and posted about my findings in a thread in the testing section.

Some MRCD tech is used for things like RLCs as well, I see that too in Chicago and they're a different camera system.

Sent from my Pixel 3 using Tapatalk

 

[cihkal]

Come to Arkansas we can't even spell MRCD/MRCT (well I can but I'm from Texas).

You poor souls.

Sent from my Pixel 3 using Tapatalk

 

[dchemist]

You poor souls.

Sent from my Pixel 3 using Tapatalk

LoL

 

[yuhao]

MRCD, and low range as well, so it's hard to say how effective it is, I can only confirm that I pick them up.

Escort red line shows K-band 23.953GHZ, extreme challenge

 

[crabu2]

I still pick up all of the MRCD on 1.48 that I did on 1.46. granted, this is pretty much limited to short range speed sensors on the interstate in major cities where I am.

I think the short range with fw 1.48 got me a ticket today.

Dang WAZE routed me through Baltimore City. On the 1st speed cam, the R3 and Waze both alerted to it, so I was sure to make sure I was below the speed limit. The R3 picked it up as MRCD as I passed it. I passed a 2nd speed cam. Neither the R3 or Waze alerted, but the R3's MRCD alerted as I passed it... there was no time to slow down. Traffic was pretty heavy. so I'm hoping it didn't or wasn't able to grab my tag...

Post automatically merged: Mar 14, 2019

FW 1.48 is not something you should run if MRCD is a possibility. Stay with 1.46.

Based on what I read about 1.46, I'm not sure it would work better than 1.48 for me. I've got to deal with Ka, K and now MRCD.. RIght or wrong, I thought I read the 1.46 has a delay on K band.

 

[winterbrew]

MRCT detection range on 1.48 still seems as good as 1.46, although it initially alerts as K band, and switches back and forth between K band and MRCD alerts until you get closer. 1.46 alerts straight away as 'MRCD'

Plus, all three of MRCT's frequencies are above the R3's lower 24.050 hardware floor, so seems it is easier for it to detect MRCT

Can't speak for MRCD here, as we only have CT's.

 

[Heywood]

Based on what I read about 1.46, I'm not sure it would work better than 1.48 for me. I've got to deal with Ka, K and now MRCD.. RIght or wrong, I thought I read the 1.46 has a delay on K band.

The delay was when TSF was activated on K band with FW 1.46.

If you do not use TSF, the K band delay doesn’t apply.

I tested the effects of TSF on November 19/18.

@OBeerWANKenobi bench tested it as well.

 

[crabu2]

The delay was when TSF was activated on K band with FW 1.46.

If you do not use TSF, the K band delay doesn’t apply.

I tested the effects of TSF on November 19/18.

@OBeerWANKenobi bench tested it as well.

Hows the range on Ka and K band on 1.46, with TSF off? Hows it compare to 1.37?

Thanks!

 

[Heywood]

Hows the range on Ka and K band on 1.46, with TSF off? Hows it compare to 1.37?

Thanks!

Check the My October 3rd and November 19th testing thread in the testing section.




Sent from my iPhone using Tapatalk

 

[takheng]

Hi, I'm a Chinese user. Can you detect other radar manufactured by Dahua and Hikvision?
I own a Uniden R1 and R7. My Uniden R1 runs at firmware 1.50 and detect general narrow beam radar such as Dahua and Hikvision perfectly. But my Uniden R7 really hard to detect them at all. My R7 runs at firmware 1.33 and I've tried the latest 1.35, no magic.

 

[djkeczap]

MRCD, and low range as well, so it's hard to say how effective it is, I can only confirm that I pick them up.

@UnidenSupport and maybe you could do updates so that users from outside the US could use and not pay fines because nothing is detected except disturbances, car stores, etc.