When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
I received an email from range today so I thought I would share it.
The Diablo is PowerTeq's "branded" version of our product; it is the exact same thing it just looks a bit different. Our next version (Version 8.3) will have improvement fixes for 2017 models, correct.
I do not have an exact ETA for when this version will be out but it should be within the 4-6 weeks. We will post on our website that there is a new version available as well as on our social media pages so stay tuned!
We appreciate your patience and understanding!
Leandra
Range Technology | AFM Solutions for GM Cars, Trucks & SUVs
I have a 2016 Z06 and at least the first 8.2 revision didn't reliably work for it either although I have read the current 8.2 does. But I think I will wait until 8.3 is available to send mine in and I hope this is finally the CEL free version. When I use the Range I switch it on a few seconds after starting the engine and it works fine without setting a CEL.
When I first starting using the Range module in my 2016 Z06 the CEL errors at startup were very infrequent but after a couple of update flashes last December (airbag and some other update) I noticed the early 8.2 will almost always trigger an error at startup. I greatly prefer the Range to V4 mode issues but even version 8.3 could experience issues if startup activity is changed by future GM recalls and flash updates.
I can tell you that the beta version they sent me last week still did not fix the issue. I emailed them about it and have not heard back yet. I would not be too optimistic of the 4-6 weeks as it took them a few months between the two beta versions I've received. Had this one fixed the issue, I would have been more optimistic on the 4-6 weeks, but clearly there are still issues.
I can tell you that the beta version they sent me last week still did not fix the issue. I emailed them about it and have not heard back yet. I would not be too optimistic of the 4-6 weeks as it took them a few months between the two beta versions I've received. Had this one fixed the issue, I would have been more optimistic on the 4-6 weeks, but clearly there are still issues.
I do not have an exact ETA on when that will be released, our engineers are still in the finalizing stages with testing to make sure this next version will have the least amount of miscommunication issues as possible. It should be within the month.
What I can do is put you on an email list and notify you when it has been released
I email the beta team every couple weeks asking for an update, has been radio silence. I'll try again now, but the short answer is that I've heard nothing.
The technology range always update without time that we gotta know before. For a simple example the mostly I use in my macbook when the ios request to update, It was so bad because I have to make connection on quick internet exactly.
The technology range always update without time that we gotta know before. For a simple example the mostly I use in my macbook when the ios request to update, It was so bad because I have to make connection on quick internet exactly.
The technology range always update without time that we gotta know before. For a simple example the mostly I use in my macbook when the ios request to update, It was so bad because I have to make connection on quick internet exactly.
Sent them my regular email and finally got a response this time. Apparently I'm not the most problematic one they are testing with as they are not talking about me in the note below :-) But maybe this means they could be close to releasing a new beta unit.
Hi Ken,
We are definitely getting close.
Hopefully, the last rev (firmware revision) went out to a specific BETA tester with a particularly difficult vehicle. If all goes well with him, the engineers will determine if this change is the final step.
I speak with the BETA tester pool frequently and pass along the feedback to the engineers who then make the necessary changes. From what I have gathered, we are about there.
Thanks as always for your patience. We will contact those who need the next version first before anyone else.
Sent them my regular email and finally got a response this time. Apparently I'm not the most problematic one they are testing with as they are not talking about me in the note below :-) But maybe this means they could be close to releasing a new beta unit.
Hi Ken,
We are definitely getting close.
Hopefully, the last rev (firmware revision) went out to a specific BETA tester with a particularly difficult vehicle. If all goes well with him, the engineers will determine if this change is the final step.
I speak with the BETA tester pool frequently and pass along the feedback to the engineers who then make the necessary changes. From what I have gathered, we are about there.
Thanks as always for your patience. We will contact those who need the next version first before anyone else.
I wonder if "last rev" means 8.4 or they're referring to 8.3.x or something.
Not too sure, none of the betas I've received have been labeled and I haven't watched the LEDs on startup to see if they have been adjusting it or not....time will tell I guess.
^^ the mystery continues! I have been trying all the versions of Range on my 2016 since last year. I still have the occasional CEL on startup. On the bright side, a CEL is a lot less annoying than the limp-mode that last years versions induced. Still a mystery why some have problems an some do not. I have not added a switch yet to just do the hot start work around, as I am having a lot of fun in M. Range has been very nice about returns/upgrades--I am sure they will get this to work eventually.