Missing and invalid data (Modis 8.2)

[phill57]

Just got my 8.2 update a couple of days ago.

Here is an error I ran accross today while scanning a 2000 Chev K3500 6.5 vin F 8600 GVW with a 4L80E transmission. I reported it via e-mail to Snap-On.

I might be loosing it but I seem to recall that there were more data PIDs available in the Transmission Data Mode. The first list shows a few PIDs but is missing some very important info. It shows RPM, APP %, Coolant temp and volts, VSS, Trans Fluid Temp, 1-2 solenoid ststus, 2-3 solenoid status and PRNDL SW status. (that's it)

What happened to TCC %, TCC Slip rate, Input speed, output speed, (different from VSS as that's on the TF case), pressure regulator control, (force motor)? there are quite a few others but these are the important ones. Also, the first data list should show the brake switch status and the cruise brake switch status. These items do not appear in the second Transmission list either as this is mostly transmission shift adapts. I am sure they were there before the update to 8.2?

Another problem that I noted on this same vehicle was when viewing the Engine data stream, the Brake switch status and the Cruise Brake switch status are shown. (The TCC stuff is not in here either), I noticed the Brake switch status would not change when applying the brake pedal, it shows open all the time but the Cruise Brake switch would change. Since I was trying to diagnose a TCC problem (did not seem to be engaging), I thought "there's my problem, the PCM thinks I have my foot on the brake so has disabled the TCC" I was about to diagnose the switch but I thought I would try my Tech2 and guess what? The Brake switch was changing state, just the modis not reporting it correctly. The tech2 shows all of the other data parameters and many more than the Modis.

Here is another issue. When I tried to view the Freeze Frame data for a P0236 code on this same vehicle, everything came up N/A. Also when I switched from a graph mode to a PID list mode I had a full screen of the same PID in my case it said Wastegate % down the whole list and the Modis was locked up. I had to shut it off and restart it. Seeemed to work fine after that?

Oh well, the fun begins.

[64 hardtop]

I also have the new 8.2 update version and think I would rather be back. My Modis is so slow and most of the time I have to reboot in order to get live data. It will display N/A Then after reboot I may get data after wasting alot of time. Freeze frame will display twice, first with no data and secondly with data. Whats up? Programming?

[Crusty]

I also have the new 8.2 update version and think I would rather be back. My Modis is so slow and most of the time I have to reboot in order to get live data. It will display N/A Then after reboot I may get data after wasting alot of time. Freeze frame will display twice, first with no data and secondly with data. Whats up? Programming?

YUP-!

[Joe Rappa]

Something is definitely wrong. It's not suppposed to do that. Call the Tech Line and see what they recommend. They might walk you through re-installing the software. Do you have a lot of files saved on the internal SD card? That can definitely slow it down.
Joe

[64 hardtop]

Nothing stored except what is installed when a "facelift" and upgrade is installed. I personally believe it's a programming error. Called Balco and spent several hours doing this then that, I'm just grateful that is works at all. I'm sure I could spend alot more money and not be any better. Just working with what I've got and waiting for another update to inprove my problems.

[Joe Rappa]

64,
I've got 2 Modis'. One came with 8.2, one came with 7.2 and has seen every update from then to now. Neither one is any slower than previous updates. The only time I have to reboot my modis to show data properly is when I'm fooling around in the Scanner Demo. when you come out of Demo Mode, you have to reboot the scanner.
If your Modis is slow, there's something wrong with it, and I can't see how it would be 8.2. It might be related to a faulty installation of 8.2(for whatever reason). 8.4 won't be out until October. That's a long time to wait for a fix that might not change anything.
What did Balco have you try? Just curious.
Joe

[64 hardtop]

To start with we redealer installed 8.2 Still a problem so Balco stepped me through reprogram, still a problem so they sent me a new scanner module. I know there is still a problem with my unit, but I've been on work overload and not able to get back on the dredded phone and call. They are great people at Balco and very helpful. Thanks

[MasterWrench]

I had my MODIS "face lift/rebuild/upgrade" done in December. I originally sent it in because of a problem with the scope module that was confirmed by my tech rep. They called my dealer and told me I needed to "upgrade" my original MODIS to the "Avenger" unit. They did this and did not replace the scope module. The other day I was using the ignition scope to look at a 5.0 Mercury Marquis. Standard ignition. It would not show cylinder 6 or 8 pattern in any mode I chose. My dealer swapped me out his scope module from his demo unit and still the same. Everything else seems to work fine. I was told there is only 90 day warranty on the rebuild that cost $1800 and that has past so now I guess I get to pay again to have it fixed. Add to this that my European software no longer works because it says that it has already been installed on another unit and will not reload on my rebuilt unit and I am lost about how to deal with this.....

[Crusty]

There is no way you could enter every function of the scope or scanner within 90 days even if you spent 8 hours a day 5 days a week to "road test" their rebuild.
It takes a while before you can recognize what failings are in there. I'll bet it wasn't right when you got it back (euro doesn't work) and won't with a new serial numbered unit unless they overide their software security (or send you a new instal card or disc to do so)
$1800 flushed. There is what is written in warranty AND THEN THERE IS WHAT IS RIGHT-!!
You followed their advice & directions and now you have just as many problems as you originally had, if not more-!
How can a company like SO treat people this way???

[patn]

Two questions/problems with the original post.
One the rear speed sensor doesn't exist on a 2000 K truck with a 4L80E. Hasn't since the mid '90s The early ones used it, and the C's use it, but not the K's. On some PCMs it's a replicated copy of the VSS on the Transfer Case, on others, the programming just pulls it from the VSS.
Second, all late GM's use the cruise brake switch as the input to control the TCC. That statement isn't completely true either, as on some later vehicles, brake switch is no longer a primary input for TCC control.
You said you had a Tech II. I never look for TCC in the main menu on my Tech II. It's got it's own menu.
I'm not saying I'm completely thrilled with the way that the new menus were always broken up either, but I am saying that I took it as Snap-On trying to reduce PID's to make the data streams faster and the system stabiler. Win-Win, especially since I tend to de-selected the majority of PIDS anyways.
I wouldn't give up my Tech II for anything, but I'd trade it before either my MODIS or my SOLUS. Both of which seem stabiler after both 7.4 and especially 8.2. I do have a second Gen MODIS though. Both platforms have their downfalls, and I like both of them better than EASE, which I have and is still a good program. The Snap-On Scanners are by far the most user friendly, but do sometimes lack the bi-directionals I want. That's why I have a Tech II.
Anyways, not trying to start anything, just what I thought of the whole thing. But, sometimes life goes better if we verify that the sensor actually exists before we start bitching about it...

[Steve6911]

The Snap-On Scanners are by far the most user friendly, but do sometimes lack the bi-directionals I want. That's why I have a Tech II.
Anyways, not trying to start anything, just what I thought of the whole thing. But, sometimes life goes better if we verify that the sensor actually exists before we start bitching about it...

It doesn’t sound like you are trying to start anything; this is a very good post with some great information. You stated that you have the Tech II due to lack of bi-directional controls, could you post some of the things you would like to see. Only way S.O. can improve thing is if they know exactly what we want.

Thanks
Steve

[patn]

To be fair, I don't have any one specific Bi-Directional control to point a finger at right now. Well, I do, but you can't add a bi-di that the factory tool doesn't have. Or can you? (Adapts for Ford 5R55W/S/N)

Anyway I used to have one that I pointed at (and pointed at and pointed at), but Snap-On finally fixed it with 7.4. That was clearing shift adapts on GM's. I've had the Tech II for a couple years now, and it was a real life saver on several 4T65's. I still use it quite heavily on GM's in prefference to my Snap-On platforms, but anymore it comes down to the mood I'm in and what I want to see. They each have their advantages.

I take that back, there is something I'd like. You just had me thinking GM cause of the Tech II stuff. It'd make my day to be able to program Chysler VIN's. Especially the locked ones, which they generally all are. I do a fair amount of programming, and it really sucks when I have to run up to the local dealer to get one coded. Kind of embarassing. By the way, as a precaution, get in the habit of checking Chrysler PCM VIN's. Make sure you always have a complete and correct one. It causes all sorts of wierd problems. I've even had one with shifting problems that fixing the VIN fixed.

I'll post more on the Tech II Bi-DI's as I run in to ones worth adding. I'm not even gonna try and claim that my memory's good enough to list off everytime I've switched tools...

Pat

[Steve6911]

On new/rebuilt Chrysler PCM's you CAN program the Vin # in with the brick, Solus, Solus Pro and the Modis. I do all the time, then use the Pass-thru-Pro to program in the lastest calibrations. As far as locked PCM's not not even sure that the DRB III can you that, I'll try to find out.

Steve

[Nick]

DRB 3 can't change a vin once it is entered. Once you enter a vin, the tool does ask you twice if you are sure. That is your only shot. If you enter it incorrectly, you need another ecu.

[patn]

I've never actually had a chance to use the DRB. All I really knew about the DRB's actuall VIN programming abilities was that the times I've needed it, the dealer we work with has been able to program it.
As to the Snap-On one. It wasn't there on the first couple I tried, but that's been a while. I'll check from now on.
Thanks,

Pat