I’ve been using multi ECU Scan on the 500s successfully for some time. Now I’ve got a 500x I had to update to the latest version which now supports it.

I couldn’t connect to any module using the yellow ELM adapter so I tried it without an adapter and it connects to some but not others. Do you have to use one of the others for the 500x

Also getting this message when I try to do a proxy alignment.

Just off to bed but with MES unless you have the fully multiplexed version and hardware then the with ELM you have to have the right cable adapter for the required vehicle module connection.

I'm also trying to recall if some ELM interfaces (possibly older or later) have connection issues. To my knowledge all the recommended and sourced interfaces and cables from the MES web site approved suppliers have no issues.

As a first port of call check the following web page for your vehicle and the required protocol and adapter information.

http://www.multiecuscan.net/SupportedVehiclesList.aspx

I managed to find the 500x and some of them need to grey one which I don’t have. Only need the yellow one in the little 500.

I’ve looked at the UK distributor site and they have a WiFi elm module which will bypass any port problems on the PC although they are out of stock. I’ll buy some more cables first and try again. Thanks.

typecastboy any use? Ps your mailbox full again.

https://m.gendan.co.uk/product_FESGREY.html

Al D said:

typecastboy any use? Ps your mailbox full again.



https://m.gendan.co.uk/product_FESGREY.html

Click to expand...

Yes that’s the one. Some modules use another colour too. I’ve got 4 but not the other two so I’ll buy a new set. Having port problems after upgrading so I’m going to buy a genuine ELM with WiFi.

Just bought a complete new elm usb thingy and set of 6 cables. Proper one, not a cheap Chinese one so hopefully it will work.

Got my new set of cables and elm adapter and it works a treat now. Long list of error codes which shows me the problems.

Good to hear.

The major cause of issues for people (see MES Forum) is the use of just any old ELM device which is why it it recommended to go with one of the approved suppliers.

FYI I do have a list of some of the 500X (possibly specific DTCs codes) so if MES lists and does not detail the error then send me a PM and I'll see if it is in my list.

Just for reference for anyone else that comes across this, most ECUs connect using no adapter. Some, including the engine one use the gray adapter.

typecastboy said:

Just for reference for anyone else that comes across this, most ECUs connect using no adapter. Some, including the engine one use the gray adapter.

Click to expand...

Indeed. An ELM (or OBDLink interface contains TWO basic types of electrical communication protocols/hardarware support. Serial and CAN Bus.

https://en.wikipedia.org/wiki/ELM327#Protocols_supported_by_ELM327

Most of the MES adapters are associated with the old Serial comms where only two devices can be connected to each other and talk to each other at the same time. This means that if you have an engine ECU, ABS ECU and Airbag ECU that all use serial comms then each of them will be wired to a different pin on vehicle EOBD connector.

CANBus is a multidevice addressable communications network that allows multiple devices (nodes) to be connected to the same network. So a CAN based engine ECU, ABS ECU and AIrbag ECU can all coexist quit happily connected together so no adapter cables are required.

For CAN it is a little more complicated as there is CAN Hi and CAN Lo but we won't go there.