Snapon Diagnostics Product Forums Diagnostic Home . Diagnostic Product Index . Customer Care        
Diagnostic SoftwareDiagnostic PlatformsAsk-a-Tech, Automotive Repair InformationTech Central
Go Back   Snapon Diagnostics Product Forums > Snap-on Diagnostic Products > Diagnostic Platforms > Solus/SOLUS PRO User Forum
Home Today's Posts Register Members List FAQ
Thank you for visiting Snap-on Diagnostics Product Forums.
You are currently NOT logged in to a registered account. Some functions of Snap-on Diagnostics Product Forums will not be available to you if your are not logged in as a registered member. For a limited time only, registrationto Snap-on Diagnostics Product Forums to Snap-on Diagnostics Product Forums is !! FREE !! Select the    **REGISTER NOW**    link to register for your FREE Snap-on Diagnostics Product Forums account!!

Reply
 
Thread Tools Display Modes
  #1  
Old 02-15-2018, 05:59 PM
Maui Maui is offline
Junior Member
 
Join Date: Feb 2018
Location: Makawao, Hawaii
Posts: 21
Maui Congratulations!  Your peers have given you enough reputation to put you into the fist level!

Default Solus will not communicate with any vehicle

Aloha to the forum,
New guy here, and of course I am in need of help.

I have owned this Solus scanner for about ten years now. (7.2)
For some unknown reason, it has stopped communicating with all vehicles.

The scanner seams as if it is working fine, IE. it boots, takes commands, says what key is required for the vehicle being accessed, and it can access trouble shooting/fast track, etc. It just can't connect to any vehicle.

Tried using all cables and keys on another SO scanner, all worked fine.

I understand that this is an old scanner, but I sure do like it. I own a Solus-pro, and a Modis, and neither preform at the speed that the Solus does.

I did a search on the subject and found little to no useful information. I have seen a few other reports about this condition, so I am not alone.

Anyone have any ideas on what might be the issue, and if it can be corrected?

Could this be an internal software time bomb that renders the scanner useless after a certain amount of time?

I did find where someone had tried rebooting the CF? card. Tried that, obviously it did not work.

Mahalo for any and all information.

aloha.
Reply With Quote
  #2  
Old 02-15-2018, 08:59 PM
Joe Rappa's Avatar
Joe Rappa Joe Rappa is offline
Snap-on DSD
 
Join Date: Aug 2007
Location: North Carolina
Posts: 1,774
Joe Rappa Made it to level 2!  Looks like you are on your way to becoming famous

Default

You've covered the things i would recommend trying.
On those old Solus' and Modis' that stopped communicating it found:
Bent pins on the 16 pin connector.
Bad 16 pin connector.
Bad Personality Key (but only when COM problem is related to that key)
Bad cable.
Bad scanner motherboard.

If you've tried all new external stuff, I'm afraid you may be out of luck.

Maybe someone else will have better suggestions for you.

Joe
__________________
"You don't build a reputation on what you're going to do"
Henry Ford
Reply With Quote
  #3  
Old 02-15-2018, 10:24 PM
Witsend Witsend is offline
Senior Member
 
Join Date: Nov 2012
Posts: 2,757
Witsend Made it to level 2!  Looks like you are on your way to becoming famous

Default

If you verified the cable and keys work fine in your other Snap On Scanners , it's time to just split it like a coconut .Let's Get Crackin
Reply With Quote
  #4  
Old 02-16-2018, 09:59 AM
Maui Maui is offline
Junior Member
 
Join Date: Feb 2018
Location: Makawao, Hawaii
Posts: 21
Maui Congratulations!  Your peers have given you enough reputation to put you into the fist level!

Default

Thank you for the quick replies.
I'm sorry, but I do not understand what is meant by "it's time to just split it like a coconut .Let's Get Crackin".

I suppose that the scanner has an internal issue that is beyond repair.

I must say that I am a little concerned about the build quality of this unit, and others that have followed, like the Pro and Modis.

This Solus might be old, but it has seen very little usage over the years. It was for personal use, and has never been in a commercial shop environment.

I didn't realize just how good this scanner was until I replaced it with the Pro and then the Modis. Long story why I ended up with both of those scanners, but the short version is the Solus went south so I purchased the Pro, then a few days later my old Sun lab scope went south.

Anyway, I'm not sure whether the Pro and the Modis have problems, (both were purchased used) but both scanners take what seems like a long time to boot, and both respond slowly to commands, compared to the Solus. Also, both of the Pro and the Modis do not go back one page at a time, but return to the main menu that you see when first loading the vehicle information each time the N button is selected. That is very annoying.

I can get the job done, which is the most important thing, but overall, I am disappointed in the performance, and software found in the newer models. I understand that versions 13.4 and 14.2 are considered old by todays standards, but I generally do not work on 4 or 5 year old vehicles.

I'm getting off topic, sorry.
Thanks again.

aloha.
Reply With Quote
  #5  
Old 02-16-2018, 10:06 AM
sbreland73's Avatar
sbreland73 sbreland73 is offline
Senior Member
 
Join Date: Jan 2009
Location: Rockwall, TX
Posts: 975
sbreland73 You made it!  You've done a great job ofearning reputation from your peers.  You now have secret access to a new hidden forum!

Default

Quote:
Originally Posted by Maui View Post
Thank you for the quick replies.
I'm sorry, but I do not understand what is meant by "it's time to just split it like a coconut .Let's Get Crackin".


aloha.
You'll have to overlook comments from this user, as they offer little to no value, other than entertainment.


Are your comm issues related to OBDII and/or Manufacture specific protocols? Is the no comm issue with ALL modules in a given vehicle, or just some?
__________________
S. Breland
Christian Brothers Automotive

"Intelligence is the ability to adapt to change." Stephen Hawking
Reply With Quote
  #6  
Old 02-16-2018, 10:18 AM
Witsend Witsend is offline
Senior Member
 
Join Date: Nov 2012
Posts: 2,757
Witsend Made it to level 2!  Looks like you are on your way to becoming famous

Default

Just saying take it apart carefully and see if it might have a cracked solder joint at one the serial data pins of connector or maybe something obvious you might be able to fix . Just messing with the Coconut business since you seem to be rubbing it in that you are in a nice Tropical Island of Hawaii saying Aloha to us while most of us are freezing are butts off up here cursing at corroded salt frozen bolts . Lol.Welcome to forum
Reply With Quote
  #7  
Old 02-16-2018, 03:22 PM
Maui Maui is offline
Junior Member
 
Join Date: Feb 2018
Location: Makawao, Hawaii
Posts: 21
Maui Congratulations!  Your peers have given you enough reputation to put you into the fist level!

Default

Quote:
Originally Posted by sbreland73 View Post
You'll have to overlook comments from this user, as they offer little to no value, other than entertainment.


Are your comm issues related to OBDII and/or Manufacture specific protocols? Is the no comm issue with ALL modules in a given vehicle, or just some?
Thanks for the response.

Good question on the OBD2. I have thought about trying the scanner on an older OBD1 system, but finding such a vehicle that's even capable of being read is not easy.

I think that there's an old Miata out in the yard that might work if it had a fresh battery, so I'll give that a try, and let you know if it will communicate with that. But the Miata is a pretty basic system, and iirc, it only has blink codes and no live data.

As for being isolated to one module, or vehicle goes...the answer is no. The scanner will not communicate with any OBD2 system at this time.
Reply With Quote
  #8  
Old 02-16-2018, 03:39 PM
Maui Maui is offline
Junior Member
 
Join Date: Feb 2018
Location: Makawao, Hawaii
Posts: 21
Maui Congratulations!  Your peers have given you enough reputation to put you into the fist level!

Default

Quote:
Originally Posted by Witsend View Post
Just saying take it apart carefully and see if it might have a cracked solder joint at one the serial data pins of connector or maybe something obvious you might be able to fix . Just messing with the Coconut business since you seem to be rubbing it in that you are in a nice Tropical Island of Hawaii saying Aloha to us while most of us are freezing are butts off up here cursing at corroded salt frozen bolts . Lol.Welcome to forum
Sorry if I offended, it was not my intension. And please do not take this the wrong way, but a guy really doesn't always know, or stop to think about what the weather might be like in other parts of the world.

Saying "aloha' is a habit, and it is not intended to be taken as any kind of a slam.

As for taking the scanner apart, been there and did that. No signs of smoke being released from any of those little components that make up the mother board.

I have a feeling that this is software related. I sure would like a chance to try a different CF card, but I have never seen one come up for sale.

mahalo for the replies, and aloha.
Reply With Quote
  #9  
Old 02-16-2018, 03:49 PM
Maui Maui is offline
Junior Member
 
Join Date: Feb 2018
Location: Makawao, Hawaii
Posts: 21
Maui Congratulations!  Your peers have given you enough reputation to put you into the fist level!

Default

One other thing that I just recalled. At times, this symbol " [V] " just like that, can be seen blinking in the lower right hand corner of the display screen.

Off to see if I can find an OBD1.

Update.
The scanner will not communicate with an OBD1 system as well.

Very strange that the scanner will preform all functions, except for linking up.

Oh well...such is life.

Thank you again for all of the replies, and information.

aloha.

Last edited by Maui; 02-16-2018 at 04:49 PM..
Reply With Quote
  #10  
Old 02-16-2018, 05:30 PM
kirkbarrow.garage kirkbarrow.garage is offline
Senior Member
 
Join Date: Jan 2015
Posts: 141
kirkbarrow.garage Congratulations!  Your peers have given you enough reputation to put you into the fist level!

Default

Quote:
Originally Posted by Maui View Post
Sorry if I offended, it was not my intension. And please do not take this the wrong way, but a guy really doesn't always know, or stop to think about what the weather might be like in other parts of the world.

Saying "aloha' is a habit, and it is not intended to be taken as any kind of a slam.

As for taking the scanner apart, been there and did that. No signs of smoke being released from any of those little components that make up the mother board.

I have a feeling that this is software related. I sure would like a chance to try a different CF card, but I have never seen one come up for sale.

mahalo for the replies, and aloha.

Hello Maui, you may not be aware of this, but the CF card is linked to the Solus in question and will come up with a red security error if you try another one.

To solve this, swap the daughter board AND CF card together from another unit ( if you find one ) and this should function correctly for you to check out the motherboards circuits and connections.

Hope this assists you to a final analysis
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



All times are GMT -7. The time now is 07:29 PM.


Reminder: Your participation in these areas of the site is solely at your own risk. The
information is only the opinion of the poster, is no substitute for your own research,
and should not be relied upon for business critical decisions or any other purpose.
Never assume that you are anonymous and cannot be identified by your posts.
We reserve the right to discontinue any users' use of any such public forum
for any reason. Please read the Terms of Service.

Snap-on is a trademark, registered in the United States and other countries, of Snap-on Incorporated. Other marks are marks of their respective holders.
©2009 Snap-on Incorporated. All rights reserved.