So you're saying a technician is actually just a lowly apprentice? That makes sense![]()
So, what do you call someone who is or was:
1) a certified auto mechanic,
2) qualified aircraft jet engine mechanic,
3) not only computer literate, but designs them
4) industrial electrician
5) rough and finish carpenter
6) working with 18 Ghz stuff and knows phase matching
7) can still build with and understand vacuum tubes
8) understands what modern computer power does for radar
9) worked the plumbing and hvac and welding trades
10) author
11) too much more to list....
Jack of all trades? Or, master of none? Some?
This - in regards to Automotive repair, with the added caveat of the higher level of Master Mechanic. A "real" mechanic can diagnose what is wrong using observation and their brain. A technician may not be able to manage that on a consistent basis. This exactly why all these machines were designed was to fill the gap for technicians that could not consistently diagnose an issue. To me the most important skill a mechanic has is the ability to diagnose what is wrong, I.E. use their brain.
Some machine tells you what is wrong, and you replace it. rebuild a part (Alt, carb, pump...)? heaven forbid!
Geez, I always liked the term "Grease Monkey".I would classify myself as a mechanic. I never received the proper training to become a "technician"
. When I was in the Army, my official MOS or job was as follows: 63 Bravo-20- Light Wheel Vehicle MECHANIC-level 20. Whichj meant I could do Unit level maintenance and Support level maintenance.
Yeah, a computer diagnosed the problem & told him what part to change...![]()
being most of what I work on has NO computers....
That fancy scanner would be a paper weight
I know a gentlemen that has a ase sticker on his shop window but he used to bring automatic transmissions to me for rebuild. I never went to tech school.
Which just goes to show how useless those pieces of ASE wallpaper are..
Who makes this magic computer and where do I get one ?Yeah, a computer diagnosed the problem & told him what part to change...![]()
You can really tell who has NOT used automotive diagnostic tools to any extent.
The uninclined would believe some mythical machine exists that just spits out all the answers, like a magic8ball.
SNIP
EVERY time I've taken my newer cars to a dealership, and I can tall them EXACTLY what the issue is, it's always a patronizing "We have to wait to hook it up to the computer and do the diagnostics and you can come back tonight/tomorrow to pick it up" and at the end of the day, it's a **** shoot if they actually fixed what was wrong.
We call those "Isolated cases".
You're so good at diag, here's one for you. I had a 2007 Audi A3 1.9TDI in with an engine warning light on, no symptoms what so ever. Drove fine, revved up fine, no weird noises, no running problem, lack of power, lack of torque, lack of responsiveness, etc. For all intents and purposes, it was running perfectly.
The light wasn't a glitch, so what was it? You're so good that you can diagnose a car without the need for diag machines and diag time, tell me what was the problem with it.![]()

We call those "Isolated cases".
a 2007 Audi A3 1.9TDI in with an engine warning light on, no symptoms what so ever. Drove fine, revved up fine, no weird noises, no running problem, lack of power, lack of torque, lack of responsiveness, etc. For all intents and purposes, it was running perfectly.
The light wasn't a glitch, so what was it?
Now you sound like the person the brings a car in and say "It's broke, fix it."
Trouble shooting and diagnostics are based on DATA I'm good at interpreting data, I didn't way I was psychic.![]()
Many of the newer cars can throw codes when they appear to be operating correctly.
A lot of the time the computer through the sensors detect a small problem that might be on it's way to becoming a big one.

The check engine light and the resulting codes point to a specific area of the engine, not an exact diagnosis. There are a number of parts and adjustments in each subsystem that can cause identical codes. You have to look at the codes as street signs pointing you in a certain direction.
Code accuracy is only as good as the programming .....
We call those "Isolated cases".
You're so good at diag, here's one for you. I had a 2007 Audi A3 1.9TDI in with an engine warning light on, no symptoms what so ever. Drove fine, revved up fine, no weird noises, no running problem, lack of power, lack of torque, lack of responsiveness, etc. For all intents and purposes, it was running perfectly.
The light wasn't a glitch, so what was it? You're so good that you can diagnose a car without the need for diag machines and diag time, tell me what was the problem with it.![]()
I am not the person you mention however; the symptoms sound like a loose fuel cap or perhaps low voltage on the battery?
Steve
Quote:
Originally Posted by Alchymist
Many of the newer cars can throw codes when they appear to be operating correctly.
Oh, you don't say?
Sarcasm becomes you.
Quote:
Originally Posted by Alchymist
A lot of the time the computer through the sensors detect a small problem that might be on it's way to becoming a big one.
Like a fault, maybe?
Is not a fault a problem ? Semantics.
Quote:
Originally Posted by Alchymist
The check engine light and the resulting codes point to a specific area of the engine, not an exact diagnosis. There are a number of parts and adjustments in each subsystem that can cause identical codes. You have to look at the codes as street signs pointing you in a certain direction.
You missed the point of my post entirely. Outlaw reckons he's always been able to diagnose a car from the off, which i think is nonsense. Either he's never had much in the way of car trouble and has little experience with cars in general or he's lying.
Perhaps.
Quote:
Originally Posted by Alchymist
Code accuracy is only as good as the programming .....
You're going outside reasonable limits now.
Perhaps not……Perhaps read the whole post in context?
__________________
:
////You missed the point of my post entirely. Outlaw reckons he's always been able to diagnose a car from the off, which i think is nonsense. Either he's never had much in the way of car trouble and has little experience with cars in general or he's lying.
Sarcasm becomes you.
Semantics
Perhaps not.
Maybe you need to read what I have written more carefully, before you start calling me a liar.
SNIP
It wasn't a fault in the programming, it was a fault in a component. Again, missing the point of my post, which was to point out that someone telling a customer they need to diagnose the fault properly is the right way to go about a repair, instead of going out into the car park, getting on your hands and knees and grabbing on a drivetrain component to determine it's shot.
Your saying you need more diagnostics than 1/2" or more of slop in a CV joint to realize it needs replaced? What, are you also going to check the odometer? 
There were no symptoms.
There are thousands of possibilities. The point i was making is that proper diagnosis is essential in any repair. You know as well as i do, having a lot of experience in this industry and in main dealers.
If a customer comes to me and specifically says they want their driveshafts replaced and authorises the repair, i will replace them. However, if they come to me and make me aware of a symptom and says "I think it's the driveshafts" i'm not going to throw a pair of 'shafts on it on that basis, and i will check it and make my own diagnosis.
You can't go to a dealer and expect them to replace something because you say what the problem part is, they (like anyone else who wants to do the job properly) must diagnose the fault themselves to make a correct repair and fix the problem.
Best believe if i was working at a dealer (like i am at the moment) and a car came to me with a suspected driveshaft issue i ain't going to get on my hands and knees out in the car park and shake the shaft to check it, the car has to come in for proper diagnosis.
Your saying you need more diagnostics than 1/2" or more of slop in a CV joint to realize it needs replaced? What, are you also going to check the odometer?
EDIT: Your right, just a difference of opinion.
Nope,
I would never write a car up with a direct diagnosis from a customer. I don't care if you were exactly right. The reason is; because what happens when I commit to doing the repair just as you ask it may not be all that is wrong. Has the part that failed caused other damage that is not apparent. Even on a repair as seeming simple as a flat tire, the rim could be bent, the flange could be rusted Etc.
You as a customer want to diagnose your car and bring it to shop for a repair, I frankly can't think of a shop that would work on your car in that situation.
Steve
Some how I don't thing we are communicating. If a customer came in and tossed you the keys and said ""Something is wrong fix it" I'm reasonably sure you would be asking for more info than that. My point about the CV joint job was that the mechanic looked at the odometer and concluded it couldn't possibly be worn out. Nothing wrong here!
My point is that good mechanics (or techs) don't ignore any information when being told about it. I don't expect you to write up a ticket based on that info alone, but it should give you a starting point and you should not patronize the customer. If the customer says there is a clunk in the front end you wouldn't start looking at the rear end first. If you are blowing them off, then I certainly wouldn't want to use your shop for my vehicles.
I have had customers complain about a noise and find something such as a bad sealed wheel bearing screaming away then gave them an estimate, did the repair and just to have them comeback as their issue was something else. After that I would go for a test drive with the customer to verify issues such as noises, but what does any of this have to do with the terminology employers want to use to describe their repair people.

You're so good at diag, here's one for you. I had a 2007 Audi A3 1.9TDI in with an engine warning light on, no symptoms what so ever. Drove fine, revved up fine, no weird noises, no running problem, lack of power, lack of torque, lack of responsiveness, etc. For all intents and purposes, it was running perfectly.

I'm not picking on anyone, but it does seem that diagnostics are fast becoming a lost art. It's become too easy to rely on the computer, but what happens when the computer is getting bad information? It seems to me that a GOOD mechanic/technician/whatever has to be a mix of the modern ASE guy and the old school unrefined "grease monkey".