Modis wont communicate

[cardoctor6455]

Had a 93 Buick Lesabre in the shop today for a Mil light. Tried scanning vehicle with MODIS Ultra and all I got was vehicle voltage too low error message and no communication. Had to break out the old brick in order to communicate. Has anyone ran into this issue before with the newer scanners on older vehicles?

[Steve6911]

Mike

Need a little bit more information. What version software are you running on the Modis? Do you have the VIN of the vehicle? Did you have external power hooked up to the GM OBDI adapter? And were you using the same cable, Key and adapter on the Brick as the Modis?

Steve

[Witsend]

Been Awhile, Any OBD1 have graphing ability?

I know when I used an old Solus (that I sold)it pretty much used the same OBD1 adapters as my MT2500 and that you always had to make sure you had to have a good battery or lighter socket connection from auxillary power wire and no green death at terminals of the OBD1 connector for it to communicate.
I can't even remember if the original Solus and later incarnations offered any graphing capability or not for OBD1 cars.
Where the OBD1 data pids can be viewed in text form on a MT2500, on a newer platform, can OBD1pids be displayed usefully in graph form?
If some OBD1 graphing capability is available and you want to use a newer platform than an MT2500 to use graphing, What is the latest Snap On Platform that you were still able to use the old MT2500 OBD1 connector set if you work on an OBD1 vehicle?
I think with OBD1 cars getting so few and far between, why would Snappy make a completely new proprietary design OBD1 connector set, and not allow you to still be able to use the trusty old ones from an older platform or MT2500?

[cardoctor6455]

Modis Is At 15.4 I Used The Gm 1 Adapter With The Da 4 Cable And The Da 5 Adapter. Ran Power Directly From Battery To Gm 1 Adapter. All I Got Was A No Communication And Vehicle System Voltage Too Low At Dlc Connector.

[Witsend]

Modis Is At 15.4 I Used The Gm 1 Adapter With The Da 4 Cable And The Da 5 Adapter. Ran Power Directly From Battery To Gm 1 Adapter. All I Got Was A No Communication And Vehicle System Voltage Too Low At Dlc Connector.
Reply With Quote

See if the voltage at the 10a fuse #8 (of relay center) maintains ignition voltage close to B+ (voltage drop out). A questionable ignition switch that drops ignition feed input voltage to the fuse the entire key travel (from bulb check through Crank ) it inputs your PCM and will definitely affect communication with a scantool. I think the lower right corner of my MT2500 screen even had a small V symbol flashing at times before mine dropped communication intermittently. Maybe the Modis Ultra is even more sensitive to marginal ignition Voltage than a MT2500.

[cardoctor6455]

I Was Able To Communicate With No Problem Using My Old Snap On "brick" Scanner.

[cardoctor6455]

Ok so I tried communicating with a 96 infinity i30 and I had the same issue . So basically I need to disregard using my modis on a anything prior to year 2000

[Modis500]

I too had an issue with this yesterday. 1999 Lexua RX300. Pulled codes with Modis Ultra 15.4, backed out to go to data, then got no comm. Then went to OBD Direct, and no comm. Then shut down car and tool at same time, and it took AWHILE to communicate in OBD Direct. Went back into scanner, and was hit or miss for communication. I'm going to be plugging into anything pre-99 just to confirm this and will put them into the Bug Report for 15.4 I started.


Tom

One note I forgot to add with this vehicle. The red led for power supply on the top of the tool was not solid red while plugged into the Lexus, it was flashing red/green very fast. Never noticed this on any other cars before, always a solid red.