Modern Vespa

Part 1/4

I've made my own tool called VespaDiag for read and writing etc the MIUG4 ECU in models such as the GTS 300 HPE and MP3 310 and MotoGuzzi V7 850 E5 etc. Main page https://steelbytes.com/vespadiag/ (not to be confused with my unrelated VespaSnoop app)

Important:
for older MIU ECU such as in GTS 300 pre-HPE which have the black 3pin plug see DIY Diagnostic tool for injection Vespa's with MIU ECU
for non MIU ECUs that have the 6pin red diag plug see GUIDE: How to read Engine Fault Codes (OBD/OBD2)

So what is it?

It's and android app that can read DTC codes and show live data, but can also do stuff like read/write the main flash bin (which contains maps etc) and also read/write the eeprom (has the keys etc). Can also do active tests such as turn on/off the cooling fan or headlights etc. And reset 'adaptive params'

It uses an Android phone/tablet and a cheap usb <-> canbus adapter (easily found on amazon/aliexpress etc).

"But I an an iPhone user". I will not be making an iOS version. If you don't have an old Android in the back of a drawer then borrow a friend's phone or even buy a budget phone.

note: basic features like code reading is free, fancy features like writing the bin is a paid featured.

Part 2/4

Quick comments on the cable / hardware used:

Main page for the required cable see https://steelbytes.com/vespadiag/cable/

It uses an Android phone/tablet and a cheap usb <-> canbus adapter (easily found on amazon/aliexpress etc).

The phone:
The Android device has to support what is called USB host mode also called On-The-Go. Pretty much all modern Androids that have a USB-C connector will work but of course I can't guarantee that the cheapest burner will but I'd be surprised if it doesn't.

The adapter is called CANable. https://canable.io/ "An Open-Source USB to CAN Adapter". Very cheap (if you buy from the right site). It should work without updating it's firmware as mayorofnow mentions below but his info is still useful if you are having problems.

The plug is the standard 6pin red plug. Can be found cheaply prewired on the amazon/aliexpress, see the earlier link for the part number of the plug to search for.

Simply attach the prewired plug to the screw terminals on the canable and then plug into the phone and enjoy.

For those in the US, here are the specific Amazon items I'm using:

• UCAN microcontroller
• ISO 19689 socket
  

Microcontroller setup

1. Open the CANable V1 updater
2. Confirm that the most recent slcan firmware is the active one in the menu. (Right now, that's 9fddea4.)
3. Click Connect and update
4. Bridge the 3v3 and B0 contacts on the board and plug it into your computer.
5. Select the STM32F072 in the menu that appears.
6. Wait for the flash to complete, remove the wire, and unplug your microcontroller.
   

The microcontroller's schematics are available on GitHub. The H, L, and GND terminals are labeled on the underside of the board.

Socket wiring

With the socket facing you, and the latch tooth on top, here is the pinout from left to right, top to bottom:

Part 2b/4 Should not be needed but useful anyway. Also canable v1 has different firmware to canable v2.

Useful if you want to change from the canable(slcan) firmware to the candlelight(gs_usb) firmware. This is because they use different protocols over the usb part of the connection (and of course different code in my app for processing the raw packets)

In my testing the candlelight firmware is approx 25% faster. Reading/writing the main flash is the only time you'll notice the speed.

Part 3/4

What can you do with the main BIN file after reading it?

A bin is a file with the code (algorithms) and the maps and configuration settings. So yes you can edit the fuel and ignition maps etc but unless you have a lot of skill and ideally a dyno then probably not much fun. You can also upgrade / downgrade by using a bin from exactly the same part number.

I am not a tuning expert so I can't supply tweaked maps etc. You can buy a tuned bin from places like https://lebschik.at/ or https://www.buchsenfuchs.com/

Backup your BIN before editing

So how?

BIN files can be edited in software such as TunerPro (free) or WinOLS (not free?).

An XDF file is also needed. This is a description that tunerpro/winols uses to find and display the various maps with in the bin (they don't magically know where everything is inside the bin).

XDF are specific to each different version of the ecu firmware inside the bin. Things move around and change format with updates.

Although you can make your own XDF, I've made a lot of XDF that are freely available at https://steelbytes.com/vespadocs/BINs%20and%20XDFs/ Look for one that has the same first 4 digits of the firmware version eg 56BHEEBA and 56BGEEAX use the same XDF. Sometimes if the first two are the same but the next two are not it will still work, simply load it and see if it looks correct. The part number such as CM291706 doesn't matter.

Part 4/4

The EEPROM file:

Has the key codes in it and those can be modified etc. Also has the famous adaptive params (which contrary to popular internet 'wisdom' are not cleared by disconnecting the battery).

Backup your EEPROM before editing

DO NOT COPY THE EEPROM FROM ONE ECU TO ANOTHER EVEN IF THE SAME PART NUMBER. This will screw the calibration of the tps which is set in the factory to allow for minor manufacturing tolerance variations.

That's good to know.

I didn't like having a mystery microcontroller with mystery firmware on it. Gives me a little more peace of mind knowing that I've flashed an open source known entity that's been tested with VespaDiag.

Thanks for all the work you've done putting this together!

I tried with both a Pixel 7 Pro and a Pixel 10 Fold, and I couldn't get it to connect.

As you can see in the photo, the light is on and it's connected on both ends, but VespaDiag doesn't seem to recognize there's a CANable attached.

Help please! What should I try next?

What does VespaDiag show when you click connect? You don't need to connect to the bike to test the phone<->canable connection just press connect.

PS, I have tested with a 7Pro successfully

"No adapter"

Did you put on canable v1 or v2 firmware? your hardware is a v1 I think. There are two different links on the canable site for flashing

Alright, I think I have a better understanding now.

If I'm now understanding correctly, CANable is a brand of open source microcontroller (like Arduino or Raspberry Pi). And like Arduino, there are a bunch of knockoffs on places like Amazon that are easier to get than the original. One of those is UCAN.

CANable v1 and v2 use different chipsets. The UCAN uses the same chipset as CANable v1.

slcan and candleLight are software that runs on CANable (like Linux on Raspberry Pi). candleLight makes the board speak the SocketCAN protocol, which is available on desktop Linux, but not on Android. slcan is the software that's compatible with VespaDiag.

So I've flash the slcan firmware from the CANable V1 updater, and now it is connecting to my Pixel. I'll have to run downstairs another time to check my ECU.

Thanks for your help!

both canable/slcan and candlelight/gs_usb work with vespadiag. your problem is v1 vs v2 hardware/firmware mismatch.

I tried installing the UCAN build of candleLight and VD didn't see it.

Tried again with slcan for CANable v1 and VD saw it, so I edited my post.