This is continued from my "sourcing parts" thread in Let's Talk FIAT.
I bought the multiplexed version of Multiecuscan from Gendan some time ago as I wanted the convenience of its operation and, maybe, run it on more than one device. I was caught out by the fact that, unlike my VCDS package, it's not really "plug and play". I am very interested in what computers let me do but very ignorant of how they, and their operating systems, work. So I found it quite easy to download the MES program into my laptop and use the simulation models but couldn't get the gear to "talk" to the car.
I have had a couple of half hearted attempts at getting it to work but gave up quite quickly as I had other things to do. Now, with a timing belt to do on both our Panda and my boy's Punto with the Punto over its service interval and the Panda due in a couple of months I really need it to work now. I am especially keen to see if any DTC's are stored before I lay a hand on them.
I've read quite a bit on the Forum about configuring the interface and MES's own guide and, slowly, as things have sunk in I've begun to understand some of it. So what did I do?
Ok, I started by waking up the laptop but not opening MES. Then plugged the interface into the USB on my laptop (runs windows 10) and then plugged the interface into the car (2010 Panda Dynamic Eco) and turned on the ignition switch but didn't fire up the engine. Computer "plinged" as it recognised the USB connected. Typed "Device Manager" into the search bar bottom left of screen and when that screen was displayed went down to "Ports (COM & LPT). Clicked to open and saw "USB Serial Device (COM3). Double clicked that open and went to "port setting" on the top banner. Clicked to open. Under "Bits per second" selected 115200 from the available drop down. Then clicked "advanced" box. This takes you to latency settings doesn't it? Well no! When you have the multiplexed interface it would seem it takes you to "FIFO buffers" whatever they are? Anyway the advice everyone gives about latency settings is to reduce them if you've got connection problems and, lo and behold, this page says "lower settings to correct connection problems! So I backed them off to the lowest settings on both sliders. Then clicked OK box on right upper side of the window. Clicked OK to close next window (USB Serial Device (COM3) Properties) and closed Device Manager.
So now I'm back on the laptop's desktop. Double click on my Multiecuscan icon and wake up the program. Bottom left corner of screen has "F9 Settings" box. Click on it. Settings box opens. Click on "Interfaces". Check box labeled "Interface type" - mine showed "CANtieCAR (USB/Bluetooth)" which is what it is, GREAT! Underneath is the "Serial Port" info box, mine showed COM3 (USB Serial Device), which was what I saw in the "Device Manager" earlier so I just left it alone and the speed, in the box to its right, showed 115200, again like I set up in the Device Manager, so I left that as it was too. Lastly click on the Test box above. A screen comes up with lots of "stuff" on it but at the bottom it says "OK! NO ERRORS FOUND!" I took it to mean all was OK so clicked the OK box bottom right. This goes back to the Settings box. I clicked OK again. Now we're back on the Multiecuscan home screen. Found my Panda model "Panda '03 1.2 8V. And selected "Scan" WOWEE! it did a whole vehicle scan and found lots of ECUs. Then clicked Scan DTC. The good news is that only one DTC was found. The bad news was that it was C1002 torque position sensor! I've erased it, but wouldn't like to bet on it not coming back!
Anyway, I can now carry on with the timing belt knowing that any DTC's that pop up afterwards are my fault!
So now I'm all good here I'm trying to get my head around this ECU reset procedure following the fitting of the new cambelt. The "Adjustments" box shows two distinct procedures "Self-adaptation reset" and "Phonic wheel learn reset". Do I need to do the Self-adaptation procedure before doing the Phonic Wheel reset? Or is the Phonic wheel learn reset all that is required? Anyone?
Thanks to everyone whose posts I've read, 'specialy Portland Bill who got me to thinking about the latence/FIFO buffers relationship and I hope this humble submission might be of help to any other poor soul who is stumbling blindly about, as I do, in this mad fantasy land which is called a computer!
Kindest regards to all
Jock
I bought the multiplexed version of Multiecuscan from Gendan some time ago as I wanted the convenience of its operation and, maybe, run it on more than one device. I was caught out by the fact that, unlike my VCDS package, it's not really "plug and play". I am very interested in what computers let me do but very ignorant of how they, and their operating systems, work. So I found it quite easy to download the MES program into my laptop and use the simulation models but couldn't get the gear to "talk" to the car.
I have had a couple of half hearted attempts at getting it to work but gave up quite quickly as I had other things to do. Now, with a timing belt to do on both our Panda and my boy's Punto with the Punto over its service interval and the Panda due in a couple of months I really need it to work now. I am especially keen to see if any DTC's are stored before I lay a hand on them.
I've read quite a bit on the Forum about configuring the interface and MES's own guide and, slowly, as things have sunk in I've begun to understand some of it. So what did I do?
Ok, I started by waking up the laptop but not opening MES. Then plugged the interface into the USB on my laptop (runs windows 10) and then plugged the interface into the car (2010 Panda Dynamic Eco) and turned on the ignition switch but didn't fire up the engine. Computer "plinged" as it recognised the USB connected. Typed "Device Manager" into the search bar bottom left of screen and when that screen was displayed went down to "Ports (COM & LPT). Clicked to open and saw "USB Serial Device (COM3). Double clicked that open and went to "port setting" on the top banner. Clicked to open. Under "Bits per second" selected 115200 from the available drop down. Then clicked "advanced" box. This takes you to latency settings doesn't it? Well no! When you have the multiplexed interface it would seem it takes you to "FIFO buffers" whatever they are? Anyway the advice everyone gives about latency settings is to reduce them if you've got connection problems and, lo and behold, this page says "lower settings to correct connection problems! So I backed them off to the lowest settings on both sliders. Then clicked OK box on right upper side of the window. Clicked OK to close next window (USB Serial Device (COM3) Properties) and closed Device Manager.
So now I'm back on the laptop's desktop. Double click on my Multiecuscan icon and wake up the program. Bottom left corner of screen has "F9 Settings" box. Click on it. Settings box opens. Click on "Interfaces". Check box labeled "Interface type" - mine showed "CANtieCAR (USB/Bluetooth)" which is what it is, GREAT! Underneath is the "Serial Port" info box, mine showed COM3 (USB Serial Device), which was what I saw in the "Device Manager" earlier so I just left it alone and the speed, in the box to its right, showed 115200, again like I set up in the Device Manager, so I left that as it was too. Lastly click on the Test box above. A screen comes up with lots of "stuff" on it but at the bottom it says "OK! NO ERRORS FOUND!" I took it to mean all was OK so clicked the OK box bottom right. This goes back to the Settings box. I clicked OK again. Now we're back on the Multiecuscan home screen. Found my Panda model "Panda '03 1.2 8V. And selected "Scan" WOWEE! it did a whole vehicle scan and found lots of ECUs. Then clicked Scan DTC. The good news is that only one DTC was found. The bad news was that it was C1002 torque position sensor! I've erased it, but wouldn't like to bet on it not coming back!
Anyway, I can now carry on with the timing belt knowing that any DTC's that pop up afterwards are my fault!
So now I'm all good here I'm trying to get my head around this ECU reset procedure following the fitting of the new cambelt. The "Adjustments" box shows two distinct procedures "Self-adaptation reset" and "Phonic wheel learn reset". Do I need to do the Self-adaptation procedure before doing the Phonic Wheel reset? Or is the Phonic wheel learn reset all that is required? Anyone?
Thanks to everyone whose posts I've read, 'specialy Portland Bill who got me to thinking about the latence/FIFO buffers relationship and I hope this humble submission might be of help to any other poor soul who is stumbling blindly about, as I do, in this mad fantasy land which is called a computer!
Kindest regards to all
Jock