No more Injector Balance tests after 16.2? anyone else?

[Wheel]

They can't hear you (deaf ears).......

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.

[BMW JEDI]

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.

They can't hear you (deaf ears).......

[Wheel]

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.

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.

[BMW JEDI]

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?

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.

[Wheel]

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

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?

[Witsend]

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 engine

[Scott_65]

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

[Witsend]

FIATSCO (Fiat's-Chrysler Organization) probably soon gonna put the prophylactic on USA Cummins and start building them out of a Yugo plant named RAM for (Russian Agricultural Machinery)LMAO

[Chron]

Up until 2013, Ram Trucks were still classified as a Dodge by the VIN. The 2011 and 2012 Ram Trucks are currently located under the Dodge selection. The C/V selection is for the Ram Cargo Van.

[blades11b]

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.

[Witsend]

Makes sense to me Diesel71. Glad you chimed in here. Thanks.

Nice work around. Could save someone from getting on the the hook for a Pro Link Ultra for the next 5 years, and then you'll have to get 24" of concrete poured in your parking lot and get used to wearing a hernia truss.

[Crusty]

blades11b,
anytime you are scanning a 5500 you will need to id it as a 3500. a 5500 is considered a medium duty diesel even though its chassis and engine is the same as a light duty. id the vehicle as a 3500 and the auto id should give the right engine/vin/make, at that point you should be able to run your tests. I did not get a chance to check the 2012 today but will and report the findings.
In the mean time use the injector kill test and record the engine rpm during the test, cut out each injector and look for less rpm drop on a cylinder. the cylinder that drops less rpm during the test is not contributing as much. this may help diag a week injector/cylinder.

Makes sense to me Diesel71. Glad you chimed in here. Thanks.

[diesel71]

blades11b,
anytime you are scanning a 5500 you will need to id it as a 3500. a 5500 is considered a medium duty diesel even though its chassis and engine is the same as a light duty. id the vehicle as a 3500 and the auto id should give the right engine/vin/make, at that point you should be able to run your tests. I did not get a chance to check the 2012 today but will and report the findings.
In the mean time use the injector kill test and record the engine rpm during the test, cut out each injector and look for less rpm drop on a cylinder. the cylinder that drops less rpm during the test is not contributing as much. this may help diag a week injector/cylinder.

[blades11b]

Thanks for the reply! We may have a 2 part problem then. Ive had this problem for a while and didnt even think of it until now. I have never been able to select a Cummins engine with the Ram option. The following is what I get no matter what model.

year.jpg
With this selection i obviously choose the year

autorman.jpg
now i pick Auto or Manual (it doesnt work no matter which one I choose. it was the same way before the update as well

vinormodel.jpg
This is where things get funky, as you can see this is my only selection i can make. The current truck being used is a 5500 but it will do this no matter what dodge it is

engine.jpg
And when i choose it this the only vin selection i can make

[diesel71]

ill try and help here,
#1 always make sure you have chose the right make of vehicle especially on Chrysler diesel trucks. you can pick dodge or ram, if you pick the wrong one the scanner will still give the right vin/year/engine and work but some functional test will not be available.
#2 the dodge/ram 6.7 from 2007 threw 2012 did not have the cylinder performance test implemented in the ecm until 6/1/2010. a ecm update/flash was needed to make this test work, so its possible you are checking a vehicle that has an old calibration or needs the latest calibration flash.
#3 the test is called cylinder performance, it measures each cylinders contribution from the cam and crank signals, rotational speed. this is read as a percentage on the scanner. balance rates are only used on the duramax engines. balance rates are the percent of injector dwell time the ecm is making to balance the engine. a + means dwell time is being added and a - means dwell time is being subtracted to that certain injector.
I used this test 2 times today on a 2007 and 2008 dodge/ram 6.7. I was using the solus edge with 16.2 and they worked fine. I have a 2012 here that I will check on Monday. if the test is missing I will report it to the right people.
51318002.BMP

51318003.BMP