I would like to provide my experience so far with the VIP 4.2.10.wonder if Stinger do any proper road tests before releasing up dates
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:I haven't installed the update yet, because I am planning to do a comparison test against MRCD with both FWs.
Here is the reply I received from new Stinger USA support team:What does "realign antennas" do?
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.Here is the reply I received from new Stinger USA support team:
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.
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.Does anyone else think the BSM filtering in v4.2.10 was a regression from v4.0.52?
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.
Thanks for the HD v6.1.6 file.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
Are you also running the latest beta FW4.2.201 in combination with the HD6.1.6? Can you comment on its performance?
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 messHowever I found out, that K-Band is turned on when encountering a GPS marked location. Deleting the complete GPS database solved the issue
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.