cooked eml327 ? After attempting to change the baud rate

[antus]

Yeah that was the case for a long time. There would certainly still be a lot in the wild. It looks like the PIC18F25K80 is still in production. Certainly many members here including myself have tried to program ELMs (including clones) at some stage and found some commands just don't work on some devices, or work differently. I am sure at least one responded to the allpro extensions. By modern standards the elm code isn't that complicated and it can be re-implemented by someone who wants to legally create and sell a branded compatible device. Just ask Tazzi as its one of the several protocols he's implemented on the OBD XPro to give it such wide software support.

[04colyZQ8]

it might work, but most the elm clones now are allpro codebase hacked up with bits of it removed, or another codebase with different amounts of support for the elm command set and not running on the original pic mcu, and not with the original crystal speed. So absolutely try all this, but anything is possible with the hardware.

It was my understanding that the vast majority of the fake "ELM327" devices were using a hacked copy of V1.0 firmware (that was the original firmware, before the chips were read protected), and show V1.5,which was never an official release.
I don't see why someone COULDN'T be using something else though, so you may be right.

Mike

Yes it was version 1.5 before it cooked

[antus]

Yeah. Elm 1.5 never existed for real, and they are all different random things.
https://en.wikipedia.org/wiki/ELM327 "v1.5 Elm Electronics never made a v1.5"

It may be a 1.0, though they had many bugs.. or it may be something like this, then all bets are off even on what CPU it is:

See https://forscan.org/forum/viewtopic.php?t=1575

Known problems:

#1. Adapters reported as ELM327 v2.1. Main chip doesn't support a half of original ELM327 commands and logic.

<snip>

This problem may exist in adapters of any type (USB, BT, WiFi)

Update 2015-09-15:

It seems the people who developed this piece of bugs have changed version from v2.1 to v1.5. So new adapter behaves the same, but returns v1.5 instead of v2.1. Also some missing commands are not the most painful problem of this adapter. Main problem is that is has very simplified and incorrect functionality comparing to original ELM327. For example, it is optimized for OBDII communication. OBDII commands are usually 2 bytes long as maximum. So the adapter doesn't read more than 2 bytes from the command string. FORScan uses service protocols that may send much more. So if FORScan tries to send, for example, 3 bytes to a module, the adapter sends only 2 of them (3rd byte is either not sent or filled with zeros). As a result, module doesn't respond or returns error instead of expected answer.

More details in the thread above. Just a sample of things it could be. Anyway, you get the point.

[MudDuck514]

Yes it was version 1.5 before it cooked

I do not know if it has changed, but at least in the early days, PCMHammer specifically checked for v1.5 and excluded its use!

Mike

[antus]

Hahaha, I forgot about that. The code is still there, but then it was never possible to flash with any elm anyway as they don't support long enough packets. The blocking of 1.5 was because a lot of those clones couldn't even transmit a message long enough for just the change vin functionality, when other elms could.

https://github.com/LegacyNsfw/PcmHacks/ ... ion.cs#L92

[MudDuck514]

Hahaha, I forgot about that. The code is still there, but then it was never possible to flash with any elm anyway as they don't support long enough packets. The blocking of 1.5 was because a lot of those clones couldn't even transmit a message long enough for just the change vin functionality, when other elms could.

https://github.com/LegacyNsfw/PcmHacks/ ... ion.cs#L92

Yeah, I noticed after trying a BAFX Products device that uses a genuine chip (or at least a licensed version) as it reports as v1.4 or somesuch!

THAT is why I went ahead and purchased an OBDXPro VT V2 from Pete and Tazzi (not to mention to simply to support their efforts, as I have yet to use it for more than a scan tool!)

Mike