Autel OBD II Code MS300 Trouble
#1
Thread Starter
Member
Joined: Mar 2012
Posts: 152
Likes: 0
From: New York & Louisiana
2010 C300 Sport
Autel OBD II Code MS300 Trouble
Hey guys,
I got an OBD II, a Maxiscan MS300, today. I have had no problems with my car at all, but based on several recommendations, and the fact that it was only $21, I bought it.
For the last hour, try as I may, I cannot make it work.
It does receive power, so I know it is connected correctly, and after about a minute or two of scanning, all I get is "Link Error", and I have tried it in several key positions, but same results. Is it not compatible with the '09 C300, or is it me? Returning it to Amazon tomorrow is my next option if I cannot make it work.
Any comments will be appreciated.
I got an OBD II, a Maxiscan MS300, today. I have had no problems with my car at all, but based on several recommendations, and the fact that it was only $21, I bought it.
For the last hour, try as I may, I cannot make it work.
It does receive power, so I know it is connected correctly, and after about a minute or two of scanning, all I get is "Link Error", and I have tried it in several key positions, but same results. Is it not compatible with the '09 C300, or is it me? Returning it to Amazon tomorrow is my next option if I cannot make it work.
Any comments will be appreciated.
#2
I have looked into those and tried it on my Mercedes even though I had no codes and it worked. By worked I mean that it found no codes (when there weren't any) and there were no link errors. Maybe you got the bad one of the bunch. Make sure its plugged completely in and that you follow the procedure as closely as possible.
#3
Thread Starter
Member
Joined: Mar 2012
Posts: 152
Likes: 0
From: New York & Louisiana
2010 C300 Sport
I have looked into those and tried it on my Mercedes even though I had no codes and it worked. By worked I mean that it found no codes (when there weren't any) and there were no link errors. Maybe you got the bad one of the bunch. Make sure its plugged completely in and that you follow the procedure as closely as possible.
Amazing! Of the thousands they sell, I might have the only defective one. Well, the good news is I don't have any check engine light on...knock on wood
#4
Did you replace the ms300
I just read your posts about the MS300. I just purchased the same model and get the same "link error" on my 2006 C280. What did you end up doing? I am thinking of having Amazon replace my unit but wonder if it is just not compatible. It does work on my 2009 Honda Fit. Please help.
#5
You should have them replace it. Obd2 is standardized, so it should be compatible. The majority of the one star reviews on amazon are due to link errors so it's likely yours has the same problem.
#6
not necessarily..I dont know why, but I had a generic obd2 scanner and it worked on my e46 bmw but not on my w208 clk...that same obd worked on all my friends japanese and american vehicles, but not on the benz
#7
Not all (older) readers have "Can-Bus" capability. You may have lucked out that the e46 and all of your friends don't have car that require the can-bus version. I had a scanner that worked on my previous CLK, but would not read newer cars.
Trending Topics
#8
Same issue
i also have a maxiscan 300 works great on my 2000 Honda, my 2011 Honda and my 2004 Mazda. It will not link on my 2000 c230 kompressor. I have heard that there is a fuse that can be related, but have yet to solve the problem. My inspection is due next month so I will have to figure something out.
#10
I agree that the obd 2 sensor is poor quality, however it should still read. In fact, it did just after that post, leading me to believe I simply did not have a good connection initially. Ended up being a simple fix MAF sensor and Evap solenoid.
#11
Link Failure for Dummies
I had the same problem with the "Link Failure" message, but after reading this thread I tried it again - with the same result. Then it occurred to me that I could turn the ignition key one more notch without starting the car -- and voilą, it worked! It's wasn't the MS300's fault, just the user's! LOL!