pcmhacking.net

I can choose serial port only once. After incorrect selection and clicking to "Select device" the app wont respond at all. I won't be able to select the port anymore even after app restart. Removing the folder and clean unpacking helps only.

yoheer wrote:I can choose serial port only once. After incorrect selection and clicking to "Select device" the app wont respond at all. I won't be able to select the port anymore even after app restart. Removing the folder and clean unpacking helps only.

Bummer, it freezes completely, that's not good ...

Thank you!

There are 3 OBDLink MX devices!

Please, Please, Please always state the model and firmware version so we can clear this up!

1. MX v1 (STN1150)
2. MX v2 (STN1151)
3. MX+ (STN2255)

The MX+ is Bluetooth and works fine with PCMHammer, though Blue Tooth issues you may have.

My records show that I have tested (with help of users) both the v1 and v2 and they worked, unfortunately I didn't track enough details ... I don't know firmware version or who the user was that tested.

Then AaronC7 reported receive failures with his MX v2, send works perfect! ... We did 3tests,
1. Additional Bus Silence requests.
. . No help ... Gave up on this thought because send works flawlessly.

2. Reduced packet size in half and increased timeouts.
. . No help.

2. Reduced packet size and increased timeouts, 32 byte packets and maxed out timeouts ...
. . No help.

Nothing ever changed ...

As always I am willing to work with anyone willing to work with me ... Want to test, holler at me!
I really would like to get this chiseled in stone!

-Enjoy

Thanks to everyone that has helped make this happen.
I have been testing it out using VXDIAG VCX Nano GDS2 and it has been working great.

I have a reliable elm device that I would like to try out as well, is there a command line option or something I need to enable to test it out with this elm based adapter?

I'm using MX+ (STN2255) It works great. But too slow. About 15 min for full flash
Also i have Ford VCM2 clone. Dunno if it will...
And also I have ALL PRO usb adapter with 5.16 firmware. The app can't identify it as MX or allpro.

[06:40:17:193] PCM Hammer 019
[06:40:17:253] Voltage: 12.0V
[06:40:17:253] Elm ID: ELM327 v1.1 compatible
[06:40:17:269] Unable to initalize ObdLink or AllPro on COM7
[06:40:17:269] Unable to initialize ObdLink or AllPro on COM7
[06:40:17:568] Thanks for using PCM Hammer.

Debug Log:

[06:40:17:193] PCM Hammer 019
[06:40:17:193] ElmDevice initialization starting.
[06:40:17:206] TX:
[06:40:17:206] TX: AT Z
[06:40:17:238] AT Z ELM327 v1.1 compatible
[06:40:17:238] TX: AT E0
[06:40:17:248] AT E0 OK
[06:40:17:248] TX: AT S0
[06:40:17:248] ?
[06:40:17:253] TX: AT RV
[06:40:17:253] Voltage: 12.0V
[06:40:17:253] TX: AT I
[06:40:17:253] Elm ID: ELM327 v1.1 compatible
[06:40:17:253] Initializing PcmHacking.AllProDeviceImplementation
[06:40:17:253] TX: AT #1
[06:40:17:253] This is not an AllPro device.
[06:40:17:253] Determining whether PcmHacking.ScanToolDeviceImplementation is connected.
[06:40:17:253] TX: ST I
[06:40:17:269] This is not a ScanTool device.
[06:40:17:269] Unable to initalize ObdLink or AllPro on COM7
[06:40:17:269] System.NullReferenceException: Ссылка на объект не указывает на экземпляр объекта.
в PcmHacking.ElmDevice.<Initialize>d__4.MoveNext()
[06:40:17:269] Unable to initialize ObdLink or AllPro on COM7
[06:40:17:568] Loaded help.html from network.
[06:40:17:568] Loaded start.txt from network.
[06:40:17:568] Thanks for using PCM Hammer.
[06:40:17:583] Loaded credits.html from network.

yoheer wrote:I'm using MX+ (STN2255) It works great. But too slow. About 15 min for full flash

Unfortunately they are what they are ...

yoheer wrote:And also I have ALL PRO usb adapter with 5.16 firmware. The app can't identify it as MX or allpro.

That version seems odd ... I would expect something like 1.22.

yoheer wrote:[06:40:17:253] Elm ID: ELM327 v1.1 compatible

This also looks odd ... I would expect something like ELM327 v2.1.

There is something amiss electrically with the All Pro, however there is a work around ...
Get (buy or create) an OBDii Spliter cable (wye), hook both the MX+ and the All pro up to the bus and you may find the All pro now works a wonder!
Not 100% certian it works using the MX+, however I do know it works with other OBDLink devices.

You don't need to connect them both to the computer but you can ...

-Enjoy

Once I get settled after this move I'd like to give my MXv2 a go again and see if we can't figure out what the heck is/was going on with it.

aaronc7 wrote:Once I get settled after this move I'd like to give my MXv2 a go again and see if we can't figure out what the heck is/was going on with it.

I'm game.
IMO a bench harness is the next step ... Pretty simple.

My allpro requires 12v on 16pin for 100% functionality. I can show the log.
The problem is that it's obsolete 1.1 version. I haven't seen a newer versions of allpro. And I can't update it. There is no firmware on the web

Which devices are fast?

yoheer wrote:My allpro requires 12v on 16pin for 100% functionality. I can show the log.
The problem is that it's obsolete 1.1 version. I haven't seen a newer versions of allpro. And I can't update it. There is no firmware on the web

Which devices are fast?

J2534 devices are fast, the OBDX Pro is fast.

A BDM device is the fastest, it's not OBD though ...

Pin 16 is supposed to have full time +12v.

All Allpro's are obsolete.

Cheap solutions are just that ...

-Enjoy