man i wish all manufacturers used those can plugs they are awesome when your chasing can faults . yes sir service data is key . fords like the inhale then exhale on some modules and some bmw stuff is the same . if you haven’t got access to in build data and you just chuck a module on you can find yourself in a whole world of pain 🤪 great video my friend . i have had some cracking faults at work this week . always think to myself “oooo he would have loved this one “ 🤣🤣🤣🤣🤣
IS IT TRUE ,,,,,,,, THAT ASEWAVE IS COMING OUT IN THE NOT TO DISTANT FUTURE WITH THE TWO CHANNEL USCOPE . THANKS FOR ALL THE GREAT DIAGNOSTIC VIDEOS GREAT JOB AS ALWAYS .🙏👍👍👍
@@JohnDoesGarage I was about to mention Leolov too but you beat me to it. I saw Ivan from Pine Hollow Diagnostics use it. He said it was better than uScope. Obviously, considering that it has 2-channels and the uScope only has one.
When updating modules which have a tendency by updating them will sometimes brick them? Any manufacturer or model more prone to this problem? Probably no easy answer to this question. Thank you.
There are variables involved that is always there no matter if it’s a new module or updating one. The risk is always the same. Sometimes it’s something weird and unexpected like you are programming a module and someone opens the car door to ask you something and then the bus gets woke up and brinks the module because it’s a key off bus asleep programming event. The point was that yeah 99% of all programming events go completely smooth. That 1% is the ones that really hurt. You get paid $X to program this one module that’s $200 and while you are in there you see that this other one has an important update so you just do it and then part way through you find out someone unplugged your maintainer and battery voltage drops to low and not the module is dead and oh crap it’s $1,500. Yes there is crazy expensive modules out there. Price any module for a Nissan/Infinity for something 10 years 5 years old. So if you was only paid to do 1 module then only do that one but that 1% will bite you hard and the fault will be yours.
Valuable information that you give, is why we asked for reprogramming videos. Keep making them. Thank you.
Thank you. Another great video
man i wish all manufacturers used those can plugs they are awesome when your chasing can faults . yes sir service data is key . fords like the inhale then exhale on some modules and some bmw stuff is the same . if you haven’t got access to in build data and you just chuck a module on you can find yourself in a whole world of pain 🤪 great video my friend . i have had some cracking faults at work this week . always think to myself “oooo he would have loved this one “ 🤣🤣🤣🤣🤣
Interesting that you brought up the window tint. There is a lot of water used for the install of tint films. Moisture damage ?
I opened this one up and it was clean as well. I'm kinda thinking heat somehow has something to do with it.
IS IT TRUE ,,,,,,,, THAT ASEWAVE IS COMING OUT IN THE NOT TO DISTANT FUTURE WITH THE TWO CHANNEL USCOPE . THANKS FOR ALL THE GREAT DIAGNOSTIC VIDEOS GREAT JOB AS ALWAYS .🙏👍👍👍
I honestly have no idea. I’m not affiliated with aeswave or have ever talked to them lol. It would be nice though.
@@JohnDoesGarage I was about to mention Leolov too but you beat me to it. I saw Ivan from Pine Hollow Diagnostics use it. He said it was better than uScope. Obviously, considering that it has 2-channels and the uScope only has one.
Where did you hear the news about uScope coming out with a 2-channel scope in the not too distant future?
When updating modules which have a tendency by updating them will sometimes brick them?
Any manufacturer or model more prone to this problem?
Probably no easy answer to this question.
Thank you.
There are variables involved that is always there no matter if it’s a new module or updating one. The risk is always the same. Sometimes it’s something weird and unexpected like you are programming a module and someone opens the car door to ask you something and then the bus gets woke up and brinks the module because it’s a key off bus asleep programming event. The point was that yeah 99% of all programming events go completely smooth. That 1% is the ones that really hurt. You get paid $X to program this one module that’s $200 and while you are in there you see that this other one has an important update so you just do it and then part way through you find out someone unplugged your maintainer and battery voltage drops to low and not the module is dead and oh crap it’s $1,500. Yes there is crazy expensive modules out there. Price any module for a Nissan/Infinity for something 10 years 5 years old. So if you was only paid to do 1 module then only do that one but that 1% will bite you hard and the fault will be yours.