For those of you using evoscan/ecuflash: Has anyone tried using the elm327 bluetooth instead of the evoscan or tactrix cables? If so what were your results? Pros/Cons?

 

Unless you write your diagnostic software from scratch, it will not work.
The OBDII shall work according to ISO9141, but you will not get flashing, and many of MUT goodies.

 

acamus is probably right; it probably behaves like most of the other ELM devices, which are pretty much OBD-II only.

Does anyone make a wireless device that's a simple pin-for-pin passthrough? I'm envisioning something you'd plug into the car permanently, with a paired device that has an OEM-style OBD-II plug on it. No translation like the ELM gadgets do, just a primitive wireless version of an OBD-II extension cable.

 

None that I know of, but I was playing with the idea of to put BT key at the end of taktrix cable, but the taktrix drivers, that ECUFlash and EvoScan relies on, are not open source so I ended up rigth there.

 

Lately I have found open source library (libmut) that explains the connection protocol, so probably I will write some application that is capable of connecting via BT. I am thinking about using my celular/mobile phone to display the main params and calculate consumption.
I have to start digging info on HW, how to extend tactrix cable for BT support.

Hopefully some HW guru's can help how to couple e.g. default broadcom CSR implementation to tactrix cable.

 

Ok I have found
http://www.csrsupport.com/download/3...R-ds-001Pb.pdf
or
http://www.blue2bfree.com/cms/data/bluemore106.pdf
This should be sufficient, if I am not mistaken

 

As Hamish is not going to help here, and wants to sell OP2.0 and GPS Touchscreen

I have been started by CLanZer, his software shall work with virtual COM ports, and should work with BlueTooth.

BT module that I have taken can be configured for non standard baudrate.

The S35 register is index value of baudrate.

Register S35 = Baud * 0.004096
Example : 15625 * 0.004096 = 64
One can set 15625 baudrate using ATS35=64 command.

My plan is to use my cellular for wireless monitoring, until then I shall find flaws of HW design with CLanZer's MUTMonitor.
So I spent little time to draw a schematics. If anyone wants to follow my steps here it is, it is not tested yet,
I will report back once I have done more.

 

Finally I got the logging part working.
Here is the the BT logging hardware.
Hopefully CLanZer will modify his software soon to support it.
@Hamish, Even if you do not believe BlueTooth, it works as charm.

 

Amazing effort! Closet genius I say.

 

Thank you Mattjin, it is not exceptional at all. Patience and perseverance have a magical effect before which difficulties disappear and obstacles vanish. Even if I am not HW guru, I just persisted on my goal an applied all what is already available together.

 

Today I have borrowed one of generic OBD key. It is possible to get MUT communication (requests, commands and actuators with it)

Here is little how to
1. Open COM port of BT key, e.g. COM6 via HyperTerminal or write simple application
2. Set baudrate to 19200
3. Send ATSP0<CR><LF>
4. Wait for reply OK - (Bus Init..... OK)
5. Send A0<MUT ID><CR><LF> e.g. A032
6. Parse reply E0 <value> e.g. E0 80, so value is 0x80
7. Use formula to get the scaled value

Sure, the logging speed is slow, baudrate 10400, but the ELM based toys are really cheap.

 

any advances? logging speed and more?

 

id like to know as well