Stinger VIP 4.2.10

whitewiskers

Learning to Drive
General User
Newly Registered
Oct 5, 2013
38
16
wonder if Stinger do any proper road tests before releasing up dates :allears:
I would like to provide my experience so far with the VIP 4.2.10.

1) I did a "Remove false list data" followed by a "Reset to factory Defaults". The I turned off the system, waited and powered it up again.
2) Then I installed the VIP 4.2.10 update and went for a 700+ klms. trip.
The arrows went everywhere, such that I could not tell from where the radar was coming, EVEN when I knew what was the source, i.e. speed sign. The arrows bounced all over, front, rear, sides, front and rear together, sides together, even three quarter directions together. I seemed to receive however fewer BSM's etc. I did a "realign antennas" during that trip, turning off the system and then restarting it. It did not seemed to have made any improvement on that first day's trip.
The next day I did another drive and the arrows now are much steadier, more like they should be, pointing to the source and around as it is passed.
I made sure my other setting were as before I installed 4.2.10 from 4.0.52. Apples to apples, so to speak.

Can anyone tell me the functional difference between the "Realign Antenna" and the Front/Rear Designation" commands/buttons????

Comments appreciated, thanks.
 

nano

Premium Member
Premium Member
Intermediate User
Beginner User
General User
Newly Registered
May 21, 2011
283
296
Europe
I haven't installed the update yet, because I am planning to do a comparison test against MRCD with both FWs.
So I did a comparison between 4.0.52 and 4.2.10 at two different stationary MRCD spots. It seems that 4.2.10 does a little better on MRCD, however it is not much:

VIP_FW_difference.jpg
 

hawk

Learning to Fly
Beginner User
General User
Newly Registered
Dec 10, 2016
82
122
Florida
What does "realign antennas" do?
Here is the reply I received from new Stinger USA support team:

"Hello Xxx,

Our terminology (and spelling..) is not quite right for this menu option, so let me try and bring clarity:

Counter to what the name suggests, “Realign antennas’ internally calibrates the (electrical values of the) antennas and has nothing to do with switching the antenna orientation. In a future update we will reflect this, likely by renaming it “Recalibrate antennas”.

Recalibrating, by the way, should only be useful under some special scenarios (like when the antennas are being reinstalled in a new vehicle, while the previous ‘host’ vehicle had certain on-board radar systems), but doing a calibration shouldn’t cause any downsides either.

The option (to switch the orientation of the antennas) that you are looking for, can be found one setting further down (so the very last entry under ‘Settings’ > ‘Radar’), and is called “Front / Rear designation”.

Choosing this should list all (both) connected antennas (sequentially numbered), each with their current directional designation (front or rear) and each with a switch button.
Hitting “switch”, of course, will reverse the current directional designation for the corresponding antenna (so technically it would even be possible to designate both antennas as front, or both as rear).

Hope this helps, and sorry for the confusion!

If you have any further questions, please let us know.

Kind regards,


Malarie "
 

whitewiskers

Learning to Drive
General User
Newly Registered
Oct 5, 2013
38
16
Here is the reply I received from new Stinger USA support team:

"Hello Xxx,

Our terminology (and spelling..) is not quite right for this menu option, so let me try and bring clarity:

Counter to what the name suggests, “Realign antennas’ internally calibrates the (electrical values of the) antennas and has nothing to do with switching the antenna orientation. In a future update we will reflect this, likely by renaming it “Recalibrate antennas”.

Recalibrating, by the way, should only be useful under some special scenarios (like when the antennas are being reinstalled in a new vehicle, while the previous ‘host’ vehicle had certain on-board radar systems), but doing a calibration shouldn’t cause any downsides either.

The option (to switch the orientation of the antennas) that you are looking for, can be found one setting further down (so the very last entry under ‘Settings’ > ‘Radar’), and is called “Front / Rear designation”.

Choosing this should list all (both) connected antennas (sequentially numbered), each with their current directional designation (front or rear) and each with a switch button.
Hitting “switch”, of course, will reverse the current directional designation for the corresponding antenna (so technically it would even be possible to designate both antennas as front, or both as rear).

Hope this helps, and sorry for the confusion!

If you have any further questions, please let us know.

Kind regards,


Malarie "
Thank you very much for getting back to us with this information. It would be much appreciated if, in the not-too-distant future, an operator's manual could be made available, so new and older hands would have a point of reference. This would allow for new system items to be included and explained at the time they are released. An electronic version of such a manual would allow for easier amendments.
Thanks again for your prompt reply.
 

jon5

PSL + (O / U)
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Oct 9, 2016
941
666
For what it's worth:
I've driven around 1000 miles on this version now.

1) It's much quieter at S-1F-1
1a) Unfortunately, this may be a result of a prior falselist bug rearing it's head where BSMs get falselisted. (and then so do LEOs)
2) Falselist appears to work again. I can't say for sure yet, but signals are staying falselisted. It may take another week for this bug to rear its head again. We'll see.
3) Sensitivity Level seems to make a strikingly large difference with respect to detection range now.
4) F-1 vs F+0, it does seem to filter GMs and Cadillacs. I haven't noticed much falsing from acuras, but that's always a mixed bag anyway. It definitely doesn't work on Honda odysseys still.
5) The spectrum analyzer seems a lot more consistent. I can finally actually see the distinct BSM signals from a single car - usually 4 or 5, when i get a punchthrough.
5a) This will probably be good for future filtering.

Overall, i'll take it. Even deep city driving is pretty dang quiet.
 

jdong

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Jun 5, 2013
6,782
9,248
This sounds promising. It's definitely a step in the right direction in the spirit of the 4.x releases.
 

mikedotd

Arrow enthusiast
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
May 6, 2012
2,829
3,935
New England
Does anyone else think the BSM filtering in v4.2.10 was a regression from v4.0.52?

Even with regular scan mode, BSM filtering set to the most filtering (all the way to the left) and sensitivity set to -2 mine is constantly alternating between alerting to and not alerting to BSM systems, while my other RD's remain quiet unless I'm on top of the source.

I actually turned K-band off and left that duty to my V1 until recently when I brought the V1 inside and replaced it with the Max360 to see if the lockup issue is actually fixed by the latest firmware update. I turned K-band back on the VIP as a backup to the Max360 incase it does lockup and man, my single antenna VIP just won't shut up.

After a week of running the Max360 (TSR off, Highway mode) I've had 2 BSM punch throughs. Today alone I had a Mercedes Benz and Honda set off the VIP while passing them, and the Max360 remained quiet.
 

hawk

Learning to Fly
Beginner User
General User
Newly Registered
Dec 10, 2016
82
122
Florida
Does anyone else think the BSM filtering in v4.2.10 was a regression from v4.0.52?
With BSM filtering set to the most filtering I experienced no improvement from v4.0.52 The directional arrows in v4.2.10 are definitely a regression from v4.0.52. Can't tell where the signal is coming from and that is why I rolled back to v4.0.52.
 

dinkydi

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Aug 23, 2011
5,499
1,192
back on the road again
totally agree with both comments above, we roll can back and forth :bang: , just left mine on the latest see no point , as you know here in OZ we have very low power k stuff and that is all farked as well no matter what FW is in, that's why i just leave it
 

jdong

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Jun 5, 2013
6,782
9,248
Compliments for the Max360 filtering… compared to Stinger VIP….. Wow, what happened over the years!
 

Shanetrain

PSL+10
Premium Member
Intermediate User
Beginner User
General User
Newly Registered
Aug 20, 2013
742
568
Does anyone else think the BSM filtering in v4.2.10 was a regression from v4.0.52?

Even with regular scan mode, BSM filtering set to the most filtering (all the way to the left) and sensitivity set to -2 mine is constantly alternating between alerting to and not alerting to BSM systems, while my other RD's remain quiet unless I'm on top of the source.

I actually turned K-band off and left that duty to my V1 until recently when I brought the V1 inside and replaced it with the Max360 to see if the lockup issue is actually fixed by the latest firmware update. I turned K-band back on the VIP as a backup to the Max360 incase it does lockup and man, my single antenna VIP just won't shut up.

After a week of running the Max360 (TSR off, Highway mode) I've had 2 BSM punch throughs. Today alone I had a Mercedes Benz and Honda set off the VIP while passing them, and the Max360 remained quiet.

I have mentioned this a few times but U could ask stinger nicely if they will make u a custom bandlist (segmentation) file.

If u know ALL the police radar frequencies in your area eg 24.150, 24.125 and so on, they can make u a special file that ignores a lot the K junk.

I have asked stinger nicely for a tool to generate files like this as I think it could help the community get the very best out the VIP, version 4.2.10 is one of the best firmware they have produced.

I have also attached a later HD V6.1.6, that also might be worth a try
 

Attachments

mikedotd

Arrow enthusiast
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
May 6, 2012
2,829
3,935
New England
I have mentioned this a few times but U could ask stinger nicely if they will make u a custom bandlist (segmentation) file.

If u know ALL the police radar frequencies in your area eg 24.150, 24.125 and so on, they can make u a special file that ignores a lot the K junk.

I have asked stinger nicely for a tool to generate files like this as I think it could help the community get the very best out the VIP, version 4.2.10 is one of the best firmware they have produced.

I have also attached a later HD V6.1.6, that also might be worth a try
Thanks for the HD v6.1.6 file.

It would be nice if they allowed us to create band segmentation on K-band ourselves. After years of running a V1 w/YaV1 I've learned in my area I can comfortably mute K-band outside of the 24.075 - 24.195 range (out of the box muting), but I'm seeing the VIP alert inside that bandwidth to cars that my other RD's don't. With the police center frequencies being 24.125 and 24.150GHz, I don't feel comfortable setting up notch filters inside that box either. Not to mention when I'm driving in a new area I'd rather be annoyed than ticketed because the frequency is out of the box (and at least the V1 will still visually indicate a signal, rather than ignoring it completely).

The competition (V1, Escort, Radenso, Uniden) have figured out how to filter these BSM systems better than Stinger currently can, without resorting entirely on notch filters. The VIP has been less effective at filtering these BSM's, alternating between alerting and falselisting, while every other RD on the market will either alert, or not alert, no back and forth behavior unless you're crossing the threshold of signal strength. The VIP appears to have more than binary logic going on, and it's a completely annoying behavior.
 

hawk

Learning to Fly
Beginner User
General User
Newly Registered
Dec 10, 2016
82
122
Florida
I have also attached a later HD V6.1.6, that also might be worth a try
Thanks for the HD v6.1.6 file. I will give it a try with v4.2.10 and see if the directional arrow performance is any better. Will let you know.
 
Last edited:

nano

Premium Member
Premium Member
Intermediate User
Beginner User
General User
Newly Registered
May 21, 2011
283
296
Europe
I am also finding not a big difference in the new FW.

However I found out, that K-Band is turned on when encountering a GPS marked location. Deleting the complete GPS database solved the issue.

Can anyone confirm that Automute is disappeared? Strangly I can not find this anymore in the menu.

I have also attached a later HD V6.1.6, that also might be worth a try
Are you also running the latest beta FW4.2.201 in combination with the HD6.1.6? Can you comment on its performance?
 

dinkydi

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Aug 23, 2011
5,499
1,192
back on the road again
However I found out, that K-Band is turned on when encountering a GPS marked location. Deleting the complete GPS database solved the issue
yeh same here my spot list is triggered when it sees a genuine fixed gatso but not all of them just the odd ones, things are are just the usual mess
 

dinkydi

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Aug 23, 2011
5,499
1,192
back on the road again
Can anyone confirm that Automute is disappeared? Strangly I can not find this anymore in the menu.
automute still works fine only way to quieten bsm stuff

incorrectly said auto mute was meaning the manual mute apoliges
 
Last edited:

hawk

Learning to Fly
Beginner User
General User
Newly Registered
Dec 10, 2016
82
122
Florida
I have also attached a later HD V6.1.6, that also might be worth a try
My directional arrow performance seems much improved with HD v6.1.6 and firmware v4.2.10. Haven't driven all that much but, the improvement seems to warrant further testing.

Thanks again

UPDATE: Although the directional arrow performance was somewhat improved with HD v6.1.6 I was receiving too many k and BSM falses compared to firmware v4.0.52 even with car filter sensitivity set to -2. Rolled back to HD v6.1.1 and firmware v4.0.52.
 
Last edited: