Multiecuscan

Hello people.

I have a Fiat Punto mk2 1.2L 16v from 2000 and I bought 2 bluetooth ELM327 adapters (one is mini, another is normal).

So, I can't get a connection to multiecuscan. I removed the resistor that I'm told to remove (thanks to Alfaeddy) but nothing happened.
When I insert the elm on car's plug, the computer detects it and pairs it. I'm running Windows 8 and after it pairs it, it says it is not connected (I don't know if this is right or not). I go to settings in multiecuscan, trying the option "scan for interfaces" but it doesn't detect anything.
I suppose that the elm adapter (any of the 2 I have) should work on this car because on the site says it work.

I exclude the possibility of faulty elm adapter because I tried with another car and Torque application and it work very well. By the way, I tried Torque on this car an the application connect to elm adapter but then can't connect to car because of protocols. (I know that Torque doesn't have the right protocol but it connected to elm anyway)

If anybody can help me to figure this out I will be much appreciated. Thanks in advance.

I tried one more time today and I have news.

It seems that the mini BT elm is detected on computer and I think it works fine. First, I scan for interfaces and it appear, then I tried to connect to engine module (with registered version of MES) and it worked. I also tried to connect to body computer and other things but it doesn't connect because I believe it is related with the remotion of transistor (elm unmodified).

The other BT elm adapter, the bigger one, black with 4 screws, doesn't appear when I scan for interfaces (already paired with computer) and I removed the resistor on this one.

I liked to know why the bigger one doesn't appear and I tried successfully in another car.

So, I tried again the mini one and it didn't work. I discovered that it only works when in MES, with the option "show available com ports only" checked, it appear the port number that is assigned to elm. Example: Com port from adapter is COM4 but when the option is checked, COM4 doesn't appear in the box list.

Right now, my MES doesn't give any port at all. The list is empty if the option is checked.

Hi zafron

The bridge resistor you away!

Which driver do you have installed?
In this case, it is bad if you let Windows find the driver.
Or used on the enclosed CD
Take this here

http://www.ftdichip.com/Drivers/VCP.htm

Do you have the Latency Time of Com ports changed to 1.?

Greetings Eddy

Hello, thanks for replying.

I taught those drivers were only for usb interfaces, these are bluetooth. I will install those drivers then. I didn't change the latency time before because I didn't know how to do that. Now I know. I will try connecting again tomorrow.

I didn't understand the bridge resistor.

Hi zafron

Bridge resistor is the resistor to you as you write in the first post removed.
This connects the CAN high and low with each other

Therefore, this resistor makes even the CAN bus protocol engine problems

Despite the Bluetooth driver is required because your laptop really needs to process data, whether Bluetooth or usb

Latency Time

Control Panel / Device Manager / Comport Bluetooth Interface / Properties / Advanced / slider on one slide (before at 16)

Greetings Eddy

So I shouldn't have removed the resistor? Is the resistor necessary? I though the remotion of the resistor would allow to connect to can bus.

Hi

There is indeed correct, but only affects the CAN bus
To connect to the motor control of your Punto
is whether the resistor is inserted or removed.

Since engine, ABS, and Airbag your Punto 1.2 2000 will not be read with the CAN bus protocol.

Greetings Eddy

Today I tried again. I changed latency time to 1 but didn't work.

I tried to connect the bigger elm (resistor removed) with the application AlfaOBD and it worked. It connected to every module. In the other hand, the mini elm didn't connect. This last one continues to successfully connect with the engine module on PC (only when com port is seen in the list).

MES keeps to not detect the bigger elm. When I search for interfaces it says element not found, but in device manager it appears associated to a com port.

In conclusion, mini elm unmodified connects to engine in MES and nothing more; bigger elm modified connects only to alfaobd app and is not found on MES.

I got AlfaOBD and same thing happens. The mini elm only connects to engine and the bigger elm is not found on com port that it is.

I will put some photos of the mini elm on faulty elms topic so you could help me with the resistor and how to separate the two boards because they are soldered.

Thank you very much for everything.

Hi there

Yes, make time images of the ELM so I can see what you have changed

Greetings Eddy