Having BSM issues after firmware update? Ghosting?

[milaw]

Getting a lot of Ka with no one around.

 

[Deadhead1971]

Getting a lot of Ka with no one around.

Can you give us a little more detail ? The frequency would help; if you’re running an app, you may be able to go back and look. Some satellite dishes will set off a detector in certain Ka frequency ranges.

 

[Bloovy One]

Small data point to add:

Yesterday I was approaching and passing a Buick SUV in small L mode (no box filters, etc) and my Gen2 rejected it totally. This is new! I noticed the BSM indicator on the driver's mirror as I passed.

 

[Brainstorm69]

Small data point to add:

Yesterday I was approaching and passing a Buick SUV in small L mode (no box filters, etc) and my Gen2 rejected it totally. This is new! I noticed the BSM indicator on the driver's mirror as I passed.

Here's a video from today of me passing a Buick Enclave with no BSM PTs.

OTOH, I had a 7 bogey encounter with a Jeep Liberty Limited right after that.

So far, Hondas and Jeeps are punching through.

 

[RoadDogg]

I had three odd Ka frequencies yesterday at one time in an area that I drive that normally doesn’t set on my V1G2. I was in All-Bogeys mode. My Gen2 is definitely “chattier” against BSMs with the new update. Hondas and Acura’s around the 24.160 seem to trigger a high bogey count consistently which was not the case on 4.1019.

Sent from my iPhone using Tapatalk

 

[Kennyc56]

I asked @cihkal to try running L mode along with K verifier being turned off on his recent trip. He got banned before he could give us the results but he contacted me and let me know that he could tell a big difference with K verifier off and even in L mode he was getting way too many BSM falses. Once he turned it back on with L mode, all was good again. So it appears that K verifier is still working somewhat at least!

 

[samq45]

I asked @cihkal to try running L mode along with K verifier being turned off on his recent trip. He got banned before he could give us the results but he contacted me and let me know that he could tell a big difference with K verifier off and even in L mode he was getting way too many BSM falses. Once he turned it back on with L mode, all was good again. So it appears that K verifier is still working somewhat at least!

Its certainly doing something, I did the same thing and have the same result. The Hondas at 24.195 will come through with K verifier off, but not with it on.

It seem like the current Logic mode is similar to All bogies mode prior to the update.

I wonder if there is someone who did not update and can test against both firmwares.

 

[Bloovy One]

The idea that we weren't able to turn K-Verifier on or off, etc. is no longer a valid idea. It was suggested, but other details sort of ruled it out. The Ka SHBC changes affected the some K filters. They are releasing another firmware soon.

 

[MASI]

I wonder if there is someone who did not update and can test against both firmwares.

Amen, brother!
Better yet, run both V2 software versions side by side and see how each behaves under the exact same circumstances. We have wayyyyy to many varying subjective reports that can't be reconciled.

 

[westwind77]

They are releasing another firmware soon.

Just curious if there is an idea of what 'soon' happens to mean? Do you know if it is anticipated to be out before '21? I would guess they would want to test this new version very thoroughly as to not have a second version with issues. I am sure they want to correct this issue quickly, but VR does not seem to be a company that bends to 'forum pressure' easily. We may want the fix soon, but they may not want to give it to us until they are 100% sure the issue is solved, which is not a bad idea....just might not be as 'soon' as we think.....unless some insiders here happen to know better?

 

[Bloovy One]

I'm not in the position to answer this appropriately, but consider this:

VR was already going to work on another firmware after they released v4.1021. They have stuff they want to tweak and many features to add in the upcoming versions.

When they noticed that some customers were having issues, they looked into v4.1021 and found the reason.

Ohio's restrictions are interfering.

The feeling is that they want to address this issue quickly.
This behavior is highly dependant on the vehicle it's used in and the vehicles encountered. Some notice issues, some don't.

My impression is that we will see a new firmware before December, but I don't know their process and challenges so don't take my impression and run with it.

 

[gbriggs82]

It would be nice if they could add to ka band segment like redline


Sent from my iPhone using Tapatalk

 

[Deadhead1971]

It would be nice if they could add to ka band segment like redline


Sent from my iPhone using Tapatalk

Are you familiar with custom frequencies (CF) in the Valentine Connection App? The G2 scans so fast there is no performance boost with CFs but it can be used to screen / block Ka falses in certain areas like 34.4 +/-. That’s similar to segmentation on the escorts and unidens.

 

[Bloovy One]

It would be nice if they could add to ka band segment like redline

Can you explain what you mean?

The Gen1 was capable of precise segmenting the entire range of Ka.

The Gen2 "Custom Frequencies" does something similar but adds K-band as well.

 

[Bloovy One]

To elaborate here:

I don't have to choose segments 4, 5, and 6 and take what that gives me. (34.191 to 35.162)

I can tailor one single entry to 34.300 to 34.900 and get only the parts I want of 4, 5, and 6 all in one entry.
I can define 33.798 to 33.802 if I want. (That's a tiny 33.8 segment, don't do that!)

 

[gbriggs82]

Can you explain what you mean?

The Gen1 was capable of precise segmenting the entire range of Ka.

The Gen2 "Custom Frequencies" does something similar but adds K-band as well.

You know what I feel stupid I just realized that


Sent from my iPhone using Tapatalk

 

[westwind77]

VR was already going to work on another firmware after they released v4.1021. They have stuff they want to tweak and many features to add in the upcoming versions.

This behavior is highly dependant on the vehicle it's used in and the vehicles encountered. Some notice issues, some don't.

Whether they were working on another update already is irrelevant to the current issue (IMO), that is unless they already knew about the current issue and had corrected it in the future update they are working on (which I highly doubt was the case). If anything, trying to incorporate the fix into that future firmware would only further delay the release. This, again IMO, will end up being a firmware release to address the multi K BSM issue only, which is a good thing.

To my knowledge the vehicle it is being used in does not have anything to do with the multi K BSM issue. Power is power and as long as your vehicle does not have any type of BSM system it should not matter. My vehicle does not have any of the 'tech', and my G2 goes crazy to certain BSM equipped vehicles that it did not prior. That has nothing to do with my vehicle, that is solely on the G2 and the firmware that changed. On the flip side, could a G2 in a vehicle with its own BSM system cause the G2 to false less (when others are having more) - something like that could be possible (noise floor and all).

Going back to their other future updates, now that that have addressed the Ka I/O issue the other other potential improvement I see room for is having improved K band reaction time. Shy of that I am not really sure what 'many' features they would like to add into the unit as the apps available take care of anything possible you could ever want. The unit does not have GPS so there are limitations there on what they could add in regard to that. The only thing I could see them wanting to add is MRCT/D, but who knows if the G2 was even designed to be able to detect that, much like the R3....not designed for it but added as a request by owners. Who knows what VR has up there sleeves though!

Since adjusting my K-band announcement settings on JBV1 it is a lot more tolerable now with the BSM issue though.

The G2 is a great RD, 'glitches' happen, life is not perfect. I'm not in a rush for the fix, was just curious if I happened to miss a possible time frame for the release. I would rather they keep/test the fix longer to insure a proper solution.

 

[Rags]

Whether they were working on another update already is irrelevant to the current issue (IMO), that is unless they already knew about the current issue and had corrected it in the future update they are working on (which I highly doubt was the case). If anything, trying to incorporate the fix into that future firmware would only further delay the release. This, again IMO, will end up being a firmware release to address the multi K BSM issue only, which is a good thing.

To my knowledge the vehicle it is being used in does not have anything to do with the multi K BSM issue. Power is power and as long as your vehicle does not have any type of BSM system it should not matter. My vehicle does not have any of the 'tech', and my G2 goes crazy to certain BSM equipped vehicles that it did not prior. That has nothing to do with my vehicle, that is solely on the G2 and the firmware that changed. On the flip side, could a G2 in a vehicle with its own BSM system cause the G2 to false less (when others are having more) - something like that could be possible (noise floor and all).

Going back to their other future updates, now that that have addressed the Ka I/O issue the other other potential improvement I see room for is having improved K band reaction time. Shy of that I am not really sure what 'many' features they would like to add into the unit as the apps available take care of anything possible you could ever want. The unit does not have GPS so there are limitations there on what they could add in regard to that. The only thing I could see them wanting to add is MRCT/D, but who knows if the G2 was even designed to be able to detect that, much like the R3....not designed for it but added as a request by owners. Who knows what VR has up there sleeves though!

Since adjusting my K-band announcement settings on JBV1 it is a lot more tolerable now with the BSM issue though.

The G2 is a great RD, 'glitches' happen, life is not perfect. I'm not in a rush for the fix, was just curious if I happened to miss a possible time frame for the release. I would rather they keep/test the fix longer to insure a proper solution.

Sounds like you already know all the answers. So when do you expect the firmware fixes to be released? I take it that you know the BSM issue will be fixed separately, so do you know if this separate release will be done prior to the firmware they are already working on, since you indicate they would not be able to recognize an issue and roll it into the current firmware project?

 

[Bloovy One]

Whether they were working on another update already is irrelevant to the current issue (IMO), that is unless they already knew about the current issue and had corrected it in the future update they are working on (which I highly doubt was the case). If anything, trying to incorporate the fix into that future firmware would only further delay the release. This, again IMO, will end up being a firmware release to address the multi K BSM issue only, which is a good thing.

Without getting into saying stuff I have no business saying; I was trying to say that they don't need to "spin up" a firmware process because they already have that running.

To my knowledge the vehicle it is being used in does not have anything to do with the multi K BSM issue. Power is power and as long as your vehicle does not have any type of BSM system it should not matter. My vehicle does not have any of the 'tech', and my G2 goes crazy to certain BSM equipped vehicles that it did not prior. That has nothing to do with my vehicle, that is solely on the G2 and the firmware that changed. On the flip side, could a G2 in a vehicle with its own BSM system cause the G2 to false less (when others are having more) - something like that could be possible (noise floor and all).

If I am trying to give a relevant answer to anyone that might read my post, I'm going to have to say that the vehicle does matter to some degree. It's not about the power supplied. Gen2 operates the same as long as it's getting 6 to 35 volts.

You don't have BSMs, I do. You have issues, I don't.
But, just as importantly, for some customers, It can solely be about the types of vehicles that are encountered. Not everyone encounters the same vehicles.

By the way, are you saying you have no BSM of any sort in your vehicle? I'm not talking only about the known BSM annoyance vehicles here. "Spread-spectrum" systems still broadcast.

Going back to their other future updates, now that that have addressed the Ka I/O issue the other other potential improvement I see room for is having improved K band reaction time. Shy of that I am not really sure what 'many' features they would like to add into the unit as the apps available take care of anything possible you could ever want. The unit does not have GPS so there are limitations there on what they could add in regard to that. The only thing I could see them wanting to add is MRCT/D, but who knows if the G2 was even designed to be able to detect that, much like the R3....not designed for it but added as a request by owners. Who knows what VR has up there sleeves though!

We will have to wait and see.

 

[westwind77]

Without getting into saying stuff I have no business saying; I was trying to say that they don't need to "spin up" a firmware process because they already have that running.

If I am trying to give a relevant answer to anyone that might read my post, I'm going to have to say that the vehicle does matter to some degree. It's not about the power supplied. Gen2 operates the same as long as it's getting 6 to 35 volts.

You don't have BSMs, I do. You have issues, I don't.
But, just as importantly, for some customers, It can solely be about the types of vehicles that are encountered. Not everyone encounters the same vehicles.

By the way, are you saying you have no BSM of any sort in your vehicle? I'm not talking only about the known BSM annoyance vehicles here. "Spread-spectrum" systems still broadcast.

We will have to wait and see.

Yes, VR has released prior updated (prior to this latest one), so there was no question they had 'the process' down. ID'ing the issue and fixing it was the area that needed focus. Comparing Escort and VR is not fair by any means, but we have seen Escort issues and it taking multiple firmware releases to finally fix the problem. I trust VR will get it in one shot though.

VR would not design their RD to work better (not overly false) only with vehicles that have BSM systems installed. You happen to be lucky that whatever BSM system is installed on your vehicle is causing the G2 not to behave as it should (as designed) in a vehicle without a BSM system. That, or you have not encountered the 'fun' offending vehicles yet. You are right, not everyone encounters the same vehicles. Different parts of the country have varying lifestyles/dealerships/availability. I would not expect everyone to have an experience similar to mine, but given enough road time some should appear.

Correct, my vehicle does not have any kind of BSM (or the like) systems installed.