Separate names with a comma.
Discussion in 'Stinger' started by Stinger, May 23, 2017.
New spotlist available!
Yeah. v4.0.x came out in December last year after the radar filtering re-write, then we got v4.0.50 in May 2017 improving laser. Hopefully we'll see a firmware release soon too. I have a feeling it's going to focus on touch controls for the VD20 display, but hopefully they're working on radar and laser fixes too.
Stinger engineering team was in Spain last months, most likely to improve MRCD detection, so I am positive to see improvements very soon.
Yep the MRCT range on this firmware is horrible.
Had very short notice on one last night, was not amused to say the least.
Sent from my iPhone using Tapatalk
Stinger is a more than a bit short of things atm, waiting patiently for this up date, wish they would change the deafening BSM warning
Funny enough I found the old 3.1.28 awesome while in NSW.
Sent from my iPhone using Tapatalk
Has anyone had any form of contact with stinger as of late? Appears they have stopped communicating with everyone they were in contact with, myself included.
Would be nice to get a response from them, to let us know what’s going on.
I have some serious issues with detection on my unit that I would like resolved with a software update, that they have been working on for the last 3 Years! It’s beyond a joke now.
I know some of u guys in the US it’s probably performs ok for your environment with high power K & KA, but here in Australia where we tackle low power K and GM BSM all the time it’s the worst.
That's usually what happens when they can't solve your problems when promising to fix them. Crickets.
Posted from my SM-N910T using the RDF Mobile App!
Think u might be onto something, but i don't think its inability to fix it, they are just unwilling to do so.
They probably spent all the R&D budget on this Freedom Laser and in the mean time ignored their core customer base's issues.
Stinger have had some talented engineers over the years and its noticeable in the lower firmware's, soon as 4.0.X come about it like it was developed by the work experience kid and was riddled with bugs and a heap of betas followed.
Now all we are left with is a 4.0.52 that barely detects low power radar, false's out KA band and has difficulty for some users to false list automatically plus lots of other weird and wonderful bugs.
I don't get on the forums a lot anymore, I would say my experience with stinger has contributed to that quite a bit.
Look what Stinger did to @mirage
Used him, chewed him up and dropped him.
Hope the same thing doesn't happen to @Vortex as that would be disappointing.
Not surprised you are off-put by Stinger.
I ran 4.0.52 in NSW and found it useless against their 34.8/34.9 KA as well as their MRCT cameras.
Also couldn't turn off K band high power, would still come through in low power K mode.
Downgraded to 3.1.28 and it magically fixed the MRCT range issues as well as the KA issues.
But 3.1.xx has it's own issues but at least there was protection.
Stinger has been extremely poor since the 3.1.30 and above firmware.
Sadly I'm forced to run 4.0.xx in my state due to the new KA bands (Which Stinger struggles with) but I'd downgrade to 3.0.14 in a heartbeat if I could.
At least 3.0.14 and 3.1.28 could detect Redflex and Gatso at decent range while also providing MRCT protection...
I've said it before and I'll say it again, they need to fork the firmwares.
One USA firmware that filters K band to high hell as well as KA, which will give the yanks their peace and range.
While EU/AU gets a firmware that is configured for detecting low powered K/K band photo radars and our KA bands without the KA filtering. (No false KA sources here.)
Send the engineers here for a week to log our BSM, to log Redflex while also logging the local Gatso/MRCT sources so they could improve their algo.
Would only set them back $6000 but would improve their product 100 fold...
But nah they rather ignore the issue, ignore our logs, ignore the local vendor, ignore their customers and yet they still want our money? HAH!
Considering the competition is starting to release remote units that are RDD proof or functional proof while having excellent BSM filtering AND great vendor customer support/willingness to beat the new Camera threats etc...
With all the new competition coming out you'd think Stinger would pull their finger out and reach out...
The Redflex cameras have been proven to be almost identical to the MRCT, (Especially the over the last 4 years) (Latest Gen uses 2 FMCW radars) while also being deployed in more countries then the MRCT units, this makes you wonder why everyone obsesses over the MRCD/T when it's less of a threat globally?
Why does Stinger continue to ignore it?
Why does Stinger continue to ignore their customers?
@beingaware I wasn't aware of the bad luck mirage had with Stinger. I don't follow Stinger much though, but I'm sad to hear that happened.
It seems like they're just failing hardcore and making it easy easy for the competition. Shame on them but they'll either change or dry up I guess.
Sent from my Pixel using Tapatalk
I'm over the update situation too I was really hoping it would improve in 2017 with the firmware releases early in the year but here we are and still nothing.
Sent from my iPhone using Tapatalk
Damn, I mean mine has issues for sure, chiefly the one where the false list and real K alerts come in and out. But that said, it’s basically the equal of my R3 plus arrows.
Maybe it’s because I’m in North America?
Tapatalk on iPhone X, 11.2.5
may be we will get a big surprise or they go the way of the DODO
I know they're actively working on something right now, but I'm not privy to what that something is.
If I had to guess, I'd say unless they're planning on entering another market they must be working on improving the regions they already support and fixing the common functionality like the VD-20 interface.
I know we have a bunch of customers from AU/NZ and US/CA on this forum, but we rarely hear from EU customers which I assume has the largest customer base. I wonder if that's because they're in non-english speaking countries and don't frequent english speaking forums or if the VIP works fine there.
The problems in Europe (specifically the Netherlands in my case) are the same, and have been the same since the introduction of their flag-ship detector DSI in 2005. We've been in discussion with them ever since. The VIP was really promising, basically an answer on all threats we have in Holland. And then the Dutch Government purchased new MultaRadar's and Gatso's and all the issues started again.
Speaking for myself: In the beginning I really tried to help them, but Stinger doesn't like input from their customer if you are not telling them the product is fantastic. After I ran a STI-R M-Edition head on to the VIP I owned all communication between me and them stopped.
The Dutch user forum (flitsservice.nl) is full of stories of people who aren't happy, and the situation there is similar to here.. they represent maybe 1% of all users, from what I hear from installers most customers aren't so happy with the current workings of the VIP.
I tend to keep an eye out for what they are doing, but their current silence is deafening.
thank you, it seems true leopards never change there spots,what year did they dutch government switch over to mrcd/ct etc
First reports of undetectable radars were from the beginning of 2013. We found out in a heartbeat that they switched to MultaRadar CD. Stinger was able to put a preliminary firmware out in a matter of weeks.
It then took at least 14 months to get the "low power" sound and a somewath stable detection you are all familiar with.
Then in December of 2014 the Dutch government switched to MRCT on all MRCD sets and shortly after that replaced all mobile gatso's and multaradar C's and CD's with CT. They came with software just before Christmas.. and after that the whole version 3 and 4 started.
For as far as my experience goes, Stinger never really nailed the MultaCT, but I sold my VIP just before the 3.0 release.
But looking back at the DSI era, it took years of nagging them (until 2010) before they updated my antenna to 2.0.14, fixing the 24 to 34 jump bug that was bothering us all since release. So there is a chance they have it all fixed in a year or two ;-)
[doublepost=1515957587,1515957256][/doublepost]Thank you, M4rk, for your information about European users concerns. It is a pity that things are not better closer to their (Stinger's) home base, but it appears we are all in the same boat ( it's not sinking, I hope!). As you say, all we can do is hope that there is a good fix in the makings and it will appear in our lifetime, or at least before too many current users sell their units in frustration.
about 2/3 years ago mrcd/mrct was introduced here in one of the States in Australia, one of ou Ozzie members who was badly effected had good contact with Stinger in getting the issue fixed and they worked well together his name was Wouter or similar sounding , then that dried up no more contact,he like you sold all his Stinger gear had enough chasing rainbows, i just cant understand how they stay in business, still think they have a great product but badly let themselves down, especially on there own turf EU