Modern Vespa

I got the BIN file downloaded from my 2007 GTS 250ie, and unfortunately GuzziDiag's MIU1 XDF file isn't compatible (it's listed for a GTS 300 anyway). I was able to get ahold of a partially functioning XDF file though, and hope that this could be modified into something fully functioning.

See the attached for the BIN & XDF files.

I've made some progress in modifying the XDF file for my 2007 GTS 250. Comparing the working XDF file from a 300 (with the MIU1HW201 hardware), against my 250 (with the MIU1HW101 hardware) has shown that many tables have some or all values that are identical. I was able to then find the corresponding table in the 250's .BIN file, and create a partially functioning .XDF file. Many thanks to https://hexed.it, Excel's 'HEX2DEC' & 'DEC2HEX' functions, and a modernvespa forum member that PMed me their 300s' .BIN file.

See the attached for all fields that I have successfully mapped, and the corresponding .BIN (with software version 1224GA95) and .XDF files.

Now for the fun part: how the 250's tune (1224GA95) compares to the 300's (22A3GS14).

The description for each table is directly below the table in tiny italic font. I believe TPS % is the horizontal scale, while RPM is the vertical scale

Relatively small variations on the 300's fueling table, but the 250's ignition table doesn't even look like Piaggio tried below 3000 RPM. Also the ignition is WAY more advanced on the 300. I wonder if this is due to hardware changes other than the throttle body.

One more post for tonight. I would be interested if anyone else has any other software calibrations for the MIU1 ECUs. Post them here or send me a PM.

Awesome data, Thanks !!!
I am wondering if there is any chance you might have all the "Error/Fault Codes" for Piaggio/MP3 500 HPE Sport Advanced ???
Or maybe a link to dig into for myself, I have not been able to find more than about 26 which are listed in an old Service Manual ...

Sorry, nothing from me. Is it the MIU1 or MIU3 ECU

Not sure yet, have not picked it up yet, it's a 2021 MP3 500 HPE Sport Advanced, should it not have the most recent or newest ECU ??

I believe that's at least one generation ahead of the MIU3 ECUs. FWIW: the MIU1 ECU was only for a few years (2006-201?) and was replaced with the MIU1 ECUs. MIU1s have a metal side cover, MIU3s are plastic (at least on the Quasar motors, not sure about anything else).

Good day,

Your scooter is Euro 5, so it must have MIUG4 magnetti Marelli ECU and also Cable Euro 5 OBD2. So, a different connection (we have Fiat type OBD1)

Right now - as much as i know - there is no free software to read this ECU.

If anyone has any news about this matter let me know, because the MIUG4 ECU goes to new Vespa 300 HPE.

The 300's ignition table is incorrect in the above post. Here is what the corrected table looks like. Also FYI: there is a new .XDF available from GuzziDiag (GTS300 MIU1 V0.03) https://www.von-der-salierburg.de/download/GuzziDiag/

I've found a couple more hex values for the MIUHW101 XDF file (for early 250s):
RPM Limit Fuel off = 4CA8E
RPM Limit Fuel return = 4CA90

Niiice.

More thoughts about the 250 vs. 300's ECU... I'm still missing a few tables, but I'm not sure they exist in in the 250's software (more accurately, I'm not sure if the hardware version 101 supports the same parameters as version 201).

The flag & tables I haven't been able to map are:
- Enable LowRev Fuel Tables
- Lambda flag
- LowRev Table 1x16 (used for defining the RPM range in LowRev Tables)
- LowRev Fuel Table 1 16x16
- LowRev Fuel Table 2 16x16 (was all zeros in 300's BIN)
- TPS Airtemp correction Table 20x16
- Two of three TPS RPM Table 20x30s (there were two tables in the 300's BIN that were either all zero or one, so I'm betting that my already identified table is enough)
- TPS RPM Table 20x16
- Unknown 03 Table 16x16 (was all zeros in 300's BIN)
- RPM Table 1x20 (shouldn't be a problem not mapping this as long as RPM range stays)
- TPS RPM 04 20x20

Note how I can't seem to find anything regarding the LowRev Fuel items. What's interesting is that the 300's BIN has a toggle to turn on/off these tables... as if they were an afterthought or possibly added in the newer software. I bet that the 250's software never had this in the design, which is why I can't make anything match up.

Most of the other missing items are TPS related, again a strange coincidence.

Food for thought...

Thanks Andy, nice job.

Have in mind that the TPS RPM Table 20x16 which is after the TPS Enginetemp correction table 20x16, in the new 0.03 XDF, have the same address with the ignition table just it is with different(wrong) unit conversion. So just delete it, it is useless.

Greetings from Turkey. I was able to run it too. (piaggio xevo 250)
windows 8.1 tablet.

Last edited by salvation53 on Fri, 14 Jan 2022 20:36:40 +0000; edited 1 time

Hello,

I have a problem to Diagnose my Vespa GTS 250 with IAWDiag. I bought the proper CAN-Bus Adapter with a original FDTI Chip. I checked the Fiat Adapter which is wiried correct according to the wiring schemes posted in this thread. I downloaded all FDTI- Drivers on my Laptop (Windows 10). I tested the cable with the programm presented here, the cable test was succesfull. When I start IAW-Diag im not able to connect to any ECU plugged.
Ignition is on and all cables connect.
The connect-Button in the Programm is just displayed grey all other Buttons are black as normal. Has anyone a idea what I am doing wrong? Is there a driver I forgott to install?

Best-Wishes

Felix

Hello, today my JDiag m100 arrived and a problem came up. When I tried to diagnose my Vespa GTS 250 ABS I wasn´t able to read the fault codes. It accured always the message: U1600 Reception CAN line (Circuit interrupted or short-circuit). I also tired it on another Vespa GTS 250 with the same result. Eventhough I am not able to read fault codes, reading Live Data and all other Diagnose functions are working properly as supposed. Does anyone have a advise to solve this Problem?

Best wishes

Felix

Looks like you need to select the com port for the usb-serial connection.

What year is your bike? Are you sure it is a MIU1 ECU with the 250 ABS?

Also in my limited experience, I've found that GuzziDiag was more likely to work than IAWDiag

Thank you for your answer! I was able to solve the Problem with your advise. It´s a 2006 GTS ABS with a MIU1 ECU. IAWDiag is now working fine!

Hello,

I am having some trouble with ABS Module. The front brake of my bike has a poor performance doesn´t build enough pressure. Has anyone had this problem before? Is there a way to diagnose the ABS Module?

Felix

Hello. Does anyone know if it would be possible to diagnose a 2018 300GTS? The ecu number are 32M3G1. Thanks!

Pretty sure the above method with iawdiag will work with that ecu.

The Magneti Marelli 32M3G1 also called MIU M3G, MIU3G, MIU G3 and M3G. So this will work since IAWDIAG supports the MIU3G.

The .xdf mapping files for tunerpro are also available for your ecu.
https://oldskulltuning.com/marelli-32m3g1-miu-g3-tuning-with-tunerpro-xdf/
I don't know if it's worth the price since I edited the ecu .bin file myself (I'm using the BGM pro V2: https://www.scooter-center.com/en/variator-set-bgm-pro-v2-piaggio-250-300-ccm-quasar-gts250-gts300-gtv300-gts-i.e.super-300-gts-hpe-touring-300-gts-supersport-300-gts-hpe-supertech-300-gts-hpe-300-e4-m4a36m-bgm2311v2), but maybe it's a good start for some ecu finetuning.

Thanks alot for the answers.

Here's some free XDF files that might work

https://www.von-der-salierburg.de/download/GuzziDiag/#:~:text=500%20(1P0P)%20V1.03-,GTS300%20MIU1%20V0.03,-Fly%203V%20V1.01

Do you know the source of the 3 GTS files below the v1.03.
I know the v1.03 is the basefile for a 2014 MIU3G GTS, but the ones below are new for me. You posted a lot of tunerpro info in September 2021, are you the source?

Maybe it's an idea to make a clear list of available .xdf files and also when and how to use them to avoid incorrect use.

Sorry, I'm not sure where they came from. All the work I've done is for MIU1HW101 hardware, which I believe is for the first quasar motors (possibly all 250s, maybe some 300s). I don't know how to get in contact with GuzziDiag either... I'm sure they could help identify where some of these files originated.

I believe @native was responsible for the 0.03 changes to the "GTS300 MIU1 V0.03" file, which is for MIU1HW201 hardware.

the author can be found at https://www.guzzi-forum.de/ Theres a subforum dedicated to GuzziDiag

Going back to the beginning of this thread...I'm having trouble installing the FTDI VCP drivers for a KKL VAG-COM interface. Has anyone had success with the Windows XP driver?
Never mind. Computer is too old and slow. Seems to be working with a newer computer.

Maybe someone can help. I read everything I found and also all FAQs etc, but can't get data out of JPDIAG.

I have a KKL cable. The blue one with FTDI chip. LED turns on when connected to 12V.
Both tests work fine. 0V/12V on K-Line and test #2 gives OK as well.

I can work with IAWDIAG 0.5, read values, turn on fan etc.

I run both programs on a Win11 PC, and start JPDIAG in XP-mode and as administrator.
I can connect, and e.g. start the FAN, but more or less nothing else.

I can NOT READ any data, e.g. the data that's needed for registration.
I mainly need the program for TPS calibration, which of course doesn't work either.

Any idea what's going wrong?

BTW: The exact same model as I have with same software version etc is listed here: https://jpdiag.akress.com/modelselect.php
As I understood it, this is sent data from JPDIAG so I assume this ECU should work fine?!

I ran across this GuzziDiag guide from griso.org.

http://griso.org/GuzziDiag%20for%20V7-V9.pdf

Thank you very much for the clear and detailed diagram for the diagnostic cable, I used it to create a cable to read the Vespa's euro 4 to which we have fitted either 50cc or 80cc Malossi ecu's, wich are not readable with the original P.A.D.S. diagnostic reader from Piaggio.

With this cable and an universal OBD reader, I was able to read / delete all fault codes 👍

Does anyone know what ECU is used on 125ccm iGet engines? As far as I can understand, the ECU on these models is not on the throttle body but it is a separate unit behind the legshield / glovebox - it has no model or part numbers on it though. I tried connecting to my 2018 Vespa GTS 125 with jpdiag but it won't connect.

I could however connect to "Conti ABS" using the guzzidiag app and get both wheel speed sensor readings and read / clear faults in the ABS system.

I have a hunch: check the brand name on your ecu

some of the ECUs used in the 125/150 engines are not by Magneti Marelli. They are by EFI Technology S.r.l. https://efitechnology.eu/efi/?page_id=819 You can see the matching logo on some of the pics of the some piaggio ecus. It's a really stupid name as it's next to impossible google for. (There's some download stuff at that link - no idea)

I'm not sure that either guzzidiag/iawdiag or jpdiag support this brand.

Hello. I succesfully have the software up and running now. Thanks for this guide. 👍 Here are some of my inputs and contributions. To make connection easy I have build in an OBD connector in the glove compartment, and also added a charge plug. I have done it so it looks more or less standard equipment. I also found out, that the OBD protocol in the vespa's control unit is compatible with most multi-brand testers for cars, like a common Bosch tester. That opens up for a lot more acces to read and clear faults and view livedata. I currently are working on a custom map with a tuner. More info. on this will come soon.

/ Jimmy

A quick update on this one - decided to give it a try with Launch car scanner, connected it to my Vespa trough the Fiat Cable and it did connect successfully, showed the VIN number. The Launch scanner I used did not have Piaggio or any motorcycle database in it, but I tried using Fiat car menu to check for faults and it showed O2 sensor fault and I was able to delete it. Didn't have much more time to look what else could be done with it, I am thinking now that maybe these models have the old type connector but they can be scanned with different OBD scanners as the newer models.