Makes sense to me Diesel71. Glad you chimed in here. Thanks.
No more Injector Balance tests after 16.2? anyone else?
Collapse
X
-
Thanks for the reply however, this still doesnt work. Ive tried the work around before and is typically something i do on Kodiaks. However the pictures i showed and will give another example of show that I have no options for Ram to even choose what size it is. so here they are
Obviously I choose the make
make.jpg
Then choose year
year.jpg
once I choose year i can ONLY choose this selection for the 5th vin character. doesnt matter if i do an automatic id or a manual
5yhvin.jpg
If I do select that VIN character I get this only engine option for the 8th VIN character
8thvin.jpg
Thank you for the suggestion on the injector kill test. Yet another test which I have used in the past to diagnose dead misfires and an injector only partially contributing. My real end game is to get this problem solved though. im not a big fan of using work arounds on a piece of equipment I pay alot of money for. Dont by any means take my tone as a frustration towards you or anyone else in this thread. It just gets ridiculous when we pay this much money for stuff that doesnt work properly. (dont even get me going on how they messed up the injector coding option a few months back and it kepy putting in an ! in one of my characters.Comment
-
Blade, did you ever get any resolution for this problem? I'm on the fence about upgrading to 16.2. I purchased 15.2 to do PS 6.7 regens, then 15.4 broke the test. I got the same response from customer service that you apparently did. I was hoping 16.2 was going to fix what they broke, but seeing this I'm not sure it's worth the cost. Your right about cost vs function. For the money spent, I shouldn't have to decide which broken features are worse than othersComment
-
Who knows why the test goes missing in 16.2 for RAM Diesel. Maybe Bean Counters figured after an unfavorable court outcome, that having a static Injector Balance test on Diesel engines is considered to be too much of a expensive liability risk to take for potential engine damage that could result from Hydro static lock, since there is less TDC chamber volume on a Diesel than a gas engineLast edited by Witsend; 06-11-2016, 10:31 AM.Comment
-
Blade, did you ever get any resolution for this problem? I'm on the fence about upgrading to 16.2. I purchased 15.2 to do PS 6.7 regens, then 15.4 broke the test. I got the same response from customer service that you apparently did. I was hoping 16.2 was going to fix what they broke, but seeing this I'm not sure it's worth the cost. Your right about cost vs function. For the money spent, I shouldn't have to decide which broken features are worse than others
If Snap On can't give us more trouble free software, can't they at least find a way to give us this workaround?You can expect the reputation of your business to be no better than the cheapest item or service you are willing to sell. - WheelComment
-
One strength of the old brick - if they screwed up something with the latest update, you could just plug in last year's cartridge and get back to work - no problem. I've said it once and I'll say it again - it's too bad they can't figure out how to give you or allow you to keep multiple versions of the software on your tool. They need to do something - if they can't refrain from breaking previous software, which is becoming far more (too) frequent, then they need a plan such as this to keep us working. It is getting to the point where Snap on scanner users are becoming more and more reluctant to purchase updates for fear of losing present abilities. AS Scott stated, we should not have to choose.
If Snap On can't give us more trouble free software, can't they at least find a way to give us this workaround?Comment
-
This would actually be a fairly simple feature to implement, always booting to the most current bundle level when powering on the tool in the traditional way, and booting to a menu allowing the user to select which bundle to run when powering on while holding a specific button. Have requested this feature many, many times, but the request always seems to fall on deaf ears.
We could get back to work just by using an older update if something went wrong, and we could afford to be more patient with them while they fixed the screwup and one would be far less afraid to purchase an update, which would be money in their pocket. As it is, gone is the blind trust that we their customers held that next update would always be better, and it is now replaced with a paranoia that next update WILL break something - something important.You can expect the reputation of your business to be no better than the cheapest item or service you are willing to sell. - WheelComment
-
If they could implement something like this it would be a win - win situation.
We could get back to work just by using an older update if something went wrong, and we could afford to be more patient with them while they fixed the screwup and one would be far less afraid to purchase an update, which would be money in their pocket. As it is, gone is the blind trust that we their customers held that next update would always be better, and it is now replaced with a paranoia that next update WILL break something - something important.Comment
-
Yep, that is why this year I bought a couple of competitor's scanners instead of spending the money with Snap On, which I would have gladly done if they would have listened and fixed the things I've been complaining about since 10.4 came out. I keep coming back to this forum hoping things will change and they would start listening again, but guess it is time to move on and give my suggestions to a company who will appreciate them and leave Snap On in the past where they have chosen to belong - at least as far as diagnostic tools is concerned.You can expect the reputation of your business to be no better than the cheapest item or service you are willing to sell. - WheelComment
Comment